14:50:41 RRSAgent has joined #hcls 14:50:41 logging to https://www.w3.org/2022/06/23-hcls-irc 14:50:49 rrsagent, make logs public 14:50:57 Meeting: FHIR RDF 14:51:01 Chair: David Booth 15:01:59 Topic: Concept IRIs 15:02:53 gaurav: Posted to zulip, but no response yet: https://chat.fhir.org/#narrow/stream/194616-terminology-.2F-utg/topic/Meeting.20with.20UTG.20group.20to.20discuss.20incorporating.20IRI.20stems 15:04:07 Present: David Booth, Gaurav Vaidya, Dagmar 15:06:33 Present+ Jim Balhoff, EricP 15:09:35 Topic: FHIR RDF Playground 15:10:15 eric: More than half way through the implementation of the last feature we need for R5. 15:10:38 ... Q: Preprocessor works in tandem w the @context generator. 15:11:16 ... Last feature is to change properties like fhir:valueQuantity to fhir:value (and have the type in the RDF type). 15:12:22 dbooth: preprocessor needs to break apart that single property into two pieces of information? 15:14:39 eric: yes. 15:15:45 dbooth: hope to make the preprocessor as stable as possible, so that most tweaking can be done to the @context 15:17:30 eric: The content model in the JSON-LD @context needs to know what type it is. 15:18:59 Topic: Issues list 15:29:59 dbooth: Looking at issue 95: https://github.com/w3c/hcls-fhir-rdf/issues/95 15:31:10 eric: we should push back to the larger FHIR community to say the type property SHOULD be included if the reference URL is not relative. Would prefer a MUST. 15:32:04 eric: Does their validator deference to find out the type? 15:32:35 ... Validation would ensure that it is the right type. 15:33:38 ACTION: DBooth to ask the FHIR community about requiring a type property when a ref is an absolute URI 15:40:17 Issue 93: How should modifier extensions be handled in R5? 15:43:39 Issue 70: FHIR rdf representation does not pass shex - canonical URL properties need metadata 15:43:46 dbooth: Closing this, because it will be caught by shex validation in the build process, so we will address then if it is still an issue. 16:04:43 In issue 77 (Simplifying primitive properties while still supporting FHIR extensions) https://github.com/w3c/hcls-fhir-rdf/issues/77 The issue of connecting FHIR extension element "_foo" to element "foo" does not necessarily have to be addressed in the preprocessor, because it is a static relationship -- it does not depend on the instance data -- so it could be included in the ontology instead of being generated in the instance data. 16:12:29 ADJOURNED 16:12:35 rrsagent, draft minutes 16:12:35 I have made the request to generate https://www.w3.org/2022/06/23-hcls-minutes.html dbooth