Meeting minutes
ShEx for FHIR RDF
adeel: Want to use python for shex validation of FHIR.
eric: Doesn't yet have the ExTEND stuf, though it is in the works
… It is needed for the latest FHIR RDF stuff.
… Typescript/JS library handles it though. That would be the best starting point at the moment.
adeel: If we add attributes from other ontologies, would it throw an error?
eric: As written yes, it is all closed shapes. It's geared toward interchange, such as into HAPI.
… But if your use case is shex plus some stuff, I might be able to put a switch in the ShexJS implementation to ignore the closed-ness of shapes.
Updating Harold's tutorial on SNOMED with FHIR RDF
daniel: Found the latest files.
dbooth: First step is to update the github materials
… Suggest forking R4 to make R5.
avanti: I might be able to help on this also
jim: I can also help on OWL pieces.
HAPI
eric: Still working on shex for jena, which is needed for it.
Validation parser for FHIR RDF
eric: Wait until after I have the HAPI stuff done, then ask Grahame if the other code is still useful.
SNOMED / FHIR RDF tutorial (more)
daniel: looking at some of the new examples, not sure if it is correct.
jim: R4 example has root node that is IRI, but in R5 it's a blank node. Should look into it.
eric: I think the R5 behavior is correct. Guessing that Grahame was appending the id to the resource source.
dbooth: Daniel, does this change matter?
daniel: Not really.
eric: But a named node would be more usable.
ACTION: Jim to look into fixing this
ADJOURNED