Meeting minutes
Champions for issues
gaurav: I can champion issue 78 (datetimes)
gaurav: Can also champion issue 92 (significant digits)
jim: I will champion Issue 76: Ordered lists
Issue 94: Lack of concept URIs for CodableConcepts
https://
jim: Could put a curie into Coding.code, like in OBO
Issue 69: Shorten dot-compound property names? (Eric???)
https://
gopi: I will look into it.
Issue 92: Significant digits in decimal numbers
https://
gaurav: We need an executable example.
eric: If there's 15.00 in JSON, then if we care about those digits we'll need a custom JSON parser.
gaurav: The JSON data is recorded as a JSON number, not a string?
eric: Correct.
david: preprocessor could use a custom JSON parser to convert 15.00 from a number to a string or both.
eric: This is low priority. It's a problem that all JSON users have.
Issue 77: Simplifying primitive properties while still supporting FHIR extensions
https://
https://
eric: Ideally we should coordinate issue 77 w issue 93
eric: Three situations: root extension, element ext, and scalar/primitive ext, like string or boolean.
eric: We could duplicate _active to hide it if it is a modifier ext.
eric: My objective: if it is a non-mod ext, then you have both 'active' and '_active', while if it is a mod ext then you only get the '_active' property.
[[
[] fhir:active true ;
fhir: _active [
a fhir:Extension ;
fhir: index 0 ; # To retain ordering of multiple extensions
fhir: url "http://
fhir: valueDecimal 0.75
] .
. . .
# Ontology relationship:
fhir: active fhir:extensionProperty fhir:_active .
]]
eric: " fhir:active true inside if there's a modifying extension "
_: foo
ADJOURNED