Meeting minutes
Issue 120
tim: w3c/
ericp: Should we say something about the fact that FHIR uses it's own idea of resolving relative URIs?
AGREED: Insert "(relative or absolute IRI)" in the yellow schema mention of "Direct RDF link" part
AGREED: link "IRI" to https://
AGREED: Link the word "relative" to https://
AGREED: The yellow schema in github #120 is good, modulo the above tweaks
Issue 177: Fix OWL polymorphic types + references
dbooth: The fhir:l for the canonical type is generated by the general case of generating a fhir:l for any kind of uri datatype.
dbooth: What should be said about the base for the fhir:l ?
tim: The base should be whatever FHIR server you are using.
jim: In the java code, if the lower-case reference has a slash in it, and it's not an URN or http URI or starts with a hash, then it's assumed to be relative to the current FHIR server
tim: the canonical datatype gets constrained by a Reference type. So want to add shex and OWL restrictions to indicate that.
ericp: btw, ShExGenerator changes are all the matches for /fhir:link/ in https://
ericp: The shex changes to restrict canonical will be hard.
AGREED: The shex and OWL enhancements for the canonical datatype look good
tim: Also need more Reference restrictions for CodeableReference
AGREED: OWL and shex changes as proposed in #177 look right for CodeReference
Issue 178: OWL punning issues
tim: Object properties are punned, and some gen the same name as classes, e.g., code and date.
… The annotations get applied to the class
ericp: We could strip the annotations off the punned names
… Could disambiguate by putting a special prefix on datatypes
tim: Could do something like http...fhir/datatypes#code
ADJOURNED