Meeting minutes
Concept IRIs
gaurav: Need slides for meeting on July 7
dbooth: Old slides are here: https://
ACTION: gaurav to determine which MeSH Coding.system URI is correct, and file a bug report if one is wrong.
rob: On line 16 it should not say CodeSystem, because it isn't a CodeSystem, but maybe an IdentifierSystem.
… But in general seems like the right approach.
… There's been a decision not to move everything in there, but need to discuss.
eric: Only a few code systems have specified their own IRI stems (SNOMED and MeSH).
… But we could in HL7 define placeholder IRI stems, for use until the vocabulary authority chooses something else.
gaurav: Also for NamingSystem, we've used "other" so far, because it's a controlled vocabulary on line 39
gaurav: If we use "uri", that's already being used for the System URI, such as on line 34.
rob: Might need a different way to distinguish them.
gaurav: Got any examples of non-ascii codes? Rob: No
rob: Should also consider with FHIR should allow Code Systems and/or codes to be a broader unicode range (to allow concept IRIs)
rob: "other" (on line 39) should only be used if it is not a URI.
ACTION: gaurav to create slides to further explain concept IRIs and issues
https://confluence.hl7.org/display/VOC/Meetings+and+Calls+Details Online Meeting Link: https://join.freeconferencecall.com/vocab Online Meeting ID: vocab 3:30pm Boston time July 7
eric: Interested in non-ascii, because hospitals in china probably won't use ascii.
rob: Even if we had the IRI stem, would URI encoding be okay?
eric: Not optimal. If you put one of these IRIs into a browser, it will do the right thing with the IRI.
eric: Could be an issue if someone rolled their own HTTP library.
jim: The core issue of why we don't URL encode, they won't match other uses of the concept IRIs.
rob: FHIR should be compatible with the general sem web standards.
References lack a type arc, issue 95
https://
Eric commented: https://
ACTION: Eric to follow up w Lloyd about that question
Properties with both scalar and object range: fhir:value inside of fhir:value #102
jim: Cannot have a property be both a datatype property and an object property.
jim: I think it's an RDF serialization issue.
dbooth: Need to determine: 1. Is this a problem? 2. Is this the only place this problem shows up?
eric: This issue is the result of both hoisting of scalars and de-currying.
ACTION: Jim to find in the spec why this is a problem.
jim: Out the next two Thursdays.
ADJOURNED