Meeting minutes
R6 changes
tim: Getting jira ticket ready
… Biggest change is Concept IRIs for CodeableConcepts
dbooth: Suggest the examples have comments saying "# Optional"
… Also suggest one jira ticket for all changes.
ericp: For modularization, could have one top-level OWL file that imports all of the others.
ACTION: Tim to make a W5 issue, and add to Jira ticket to fix it.
AGREED: add a top-level class W5 and top-level object property, for W5 ont.
AGREED: Fix W5 ont as described in issue 234
AGREED: We will not gen the modifier ont, as described in issue 229
ericp: Propose we clarify that using a resource like Observation, the user must be aware of the status.
AGREED: clarify that using a resource like Observation, the user must be aware of the status.
tim: Re issue 194, rendering of bundles. An example showed a Bundle that has a ref to two different versions of the same Patient. They were merged in the Turtle, which is wrong.
ACTION: Tim to get clarification on URIs to disambiguate those two different version.
AGREED: Fix the bundle example having two separate Patient versions, according to the clarification that Tim gets on zulip
RDF Lists
dbooth: I suggest we allow the R4 style as optional, but keep the RDF List style as required.
… And allow them both on orderMeaning properties and non-orderMeaning properties.
… and optionally include the fhir:index
… But would that approach cause a problem with the property names?
tim: would need to add that to the shex
… I could make an extended version of the shex to allow that
dbooth: We have a fundamental dichotomy between being OWL friendly or SPARQL friendly out of the box.
… I would be uncomfortable backtracking on our decision to use RDF List for ordering.
ericp: They previously said "ordering must be retained because it might be important". But now they are changing to the opposite default, saying "order does not matter EXCEPT if orderMeaning is set"
tim: And it's only set for 6 elements.
ericp: So HAPI "equals" operator code will have to be rewritten.
tim: Shex generator is not always generating the shapes in a deterministic order.
… I fixed it in my branch, and noticed that you did also.
ericp: Back to design decisions, we could use OLO for those 6 cases.
… Part of the motivation for using RDF lists was marketing, to look more like the JSON.
dbooth: We need broader input if we are going to change to the OWL-friendly style.
ACTION: dbooth to create jira ticket for R6 changes in issue 176.
ADJOURNED