keneanung

Done:

• Use ccache to speed up builds
• Document SDK installation on windows (Done by Vadi)
• Add automated coverity scans
• Check Windows MinGW 5.3 issues (see Mudlet/Mudlet#1176)
• Fix technical debts:
  • Correct file count for lcf
  • Remove sourced-in zziplib code
  • Update boost
• Install updated 7-zip (see https://www.cisecurity.org/advisory/a-vulnerability-in-7-zip-could-allow-for-arbitrary-code-execution_2018-049/)

xslim

Usage

• https://rawgit.com/xslim/90fa66bc74d8884aac83/raw/matches.yml

niquola

FHIR JSON+ format

Design of FHIR formats, to be honest, was essentially driven by XML and Object Oriented implementations. Not so much attention was given to design idiomatic JSON format. JSON and other JSON like formats like yaml, edn, avro are very popular in avantе-garde of programmers, some modern databases now could understad JSON as first-class data-structures, that’s why i think, good design for it is strictly required for FHIR adoption. I would like list some problems with current JSON format and propose solutions.