Meeting minutes
Issue 76: How should list ordering be preserved in R5
https://
eric: When we designed FHIR RDF R4, I pushed for an explicit index. But I hadn't looked hard at the use cases. Now it seems there aren't many use cases that need ordering.
eric: JSON-LD 1.1 tooling handles ordered lists, including framing for going from RDF back to JSON.
{
"resourceType": "Patient",
"id": "example",
"name": [ # Outer list
{
"family": "Chalmers",
"given": [ # Inner list
"Peter",
"James"
]
}
]
}
ACTION: Jim to make an example of FHIR JSON list going to and from RDF
Issue 77: Simplifying primitive properties while still supporting FHIR extensions
eric: We want: 1. Non-mod ext and mod ext to be represented the same. 2. We want mod ext property to be hidden, to avoid wrong interpretations. 3. Because the original value is hidden with a mod ext, the original value must be duplcated in all of the extensions.
eric: Proposed option 3 in issue 93.
david: Seems like this would satisfy the desire to be able to easily query primitive properties when they have non-mod ext.
… We still need to test this with JSON-LD 1.1, going to and from RDF.
… We also need to compare this with what happens with non-primitive properties.
ACTION: Eric to work out JSON-LD to RDF round tripping for issue 77 and 93, and also compare with treatment of non-primitive properties
gaurav: James Champion is emitting FHIR RDF.
david: This will also affect preprocessing.
ADJOURNED