14:49:55 RRSAgent has joined #hcls 14:49:55 logging to https://www.w3.org/2022/06/30-hcls-irc 14:49:59 rrsagent, make logs public 14:50:05 Meeting: FHIR RDF 14:50:10 Chair: David Booth 15:02:30 Topic: Concept IRIs 15:06:39 gaurav: Need slides for meeting on July 7 15:06:47 dbooth: Old slides are here: https://docs.google.com/presentation/d/19Xd8i6mK-fhgoCPF3q9BvUu1RFmUxrGCOzWKbfVN5J4/edit#slide=id.g1280217e6c0_0_19 15:09:51 ACTION: gaurav to determine which MeSH Coding.system URI is correct, and file a bug report if one is wrong. 15:17:20 Example here: https://github.com/gaurav/UTG/blob/28b2c022e619809ada2d3152bca8f5d9e6eea997/input/sourceOfTruth/external/v3/codeSystems/cs-v3-snomed-CT.xml#L14-L18 15:18:21 rob: On line 16 it should not say CodeSystem, because it isn't a CodeSystem, but maybe an IdentifierSystem. 15:18:59 ... But in general seems like the right approach. 15:19:42 ... There's been a decision not to move everything in there, but need to discuss. 15:20:21 eric: Only a few code systems have specified their own IRI stems (SNOMED and MeSH). 15:21:11 ... But we could in HL7 define placeholder IRI stems, for use until the vocabulary authority chooses something else. 15:23:32 gaurav: Also for NamingSystem, we've used "other" so far, because it's a controlled vocabulary on line 39 15:23:34 https://github.com/gaurav/UTG/blob/28b2c022e619809ada2d3152bca8f5d9e6eea997/input/sourceOfTruth/external/v3/namingSystems/v3-snomed-CT.xml#L38-L42 15:25:32 Present: David Booth, EricP, Gaurav Vaidya, Jim Balhoff, Rob Hausam 15:26:23 gaurav: If we use "uri", that's already being used for the System URI, such as on line 34. 15:26:50 rob: Might need a different way to distinguish them. 15:30:49 gaurav: Got any examples of non-ascii codes? Rob: No 15:32:31 rob: Should also consider with FHIR should allow Code Systems and/or codes to be a broader unicode range (to allow concept IRIs) 15:33:00 rob: "other" (on line 39) should only be used if it is not a URI. 15:38:00 ACTION: gaurav to create slides to further explain concept IRIs and issues 15:38:45 [[ 15:38:48 https://confluence.hl7.org/display/VOC/Meetings+and+Calls+Details 15:38:48 Online Meeting Link: https://join.freeconferencecall.com/vocab 15:38:48 Online Meeting ID: vocab 15:38:53 3:30pm Boston time 15:38:58 July 7 15:39:00 ]] 15:40:11 eric: Interested in non-ascii, because hospitals in china probably won't use ascii. 15:40:53 rob: Even if we had the IRI stem, would URI encoding be okay? 15:41:26 eric: Not optimal. If you put one of these IRIs into a browser, it will do the right thing with the IRI. 15:41:53 eric: Could be an issue if someone rolled their own HTTP library. 15:42:33 jim: The core issue of why we don't URL encode, they won't match other uses of the concept IRIs. 15:42:47 rob: FHIR should be compatible with the general sem web standards. 15:43:58 Topic: References lack a type arc, issue 95 15:44:14 https://github.com/w3c/hcls-fhir-rdf/issues/95# 15:46:55 Eric commented: https://chat.fhir.org/#narrow/stream/291844-FHIR-Validator/topic/Requiring.20the.20type.20of.20a.20Reference/near/287238355 15:47:30 ACTION: Eric to follow up w Lloyd about that question 15:49:59 Topic: Properties with both scalar and object range: fhir:value inside of fhir:value #102 15:50:31 jim: Cannot have a property be both a datatype property and an object property. 15:51:03 jim: I think it's an RDF serialization issue. 15:52:52 dbooth: Need to determine: 1. Is this a problem? 2. Is this the only place this problem shows up? 15:54:08 eric: This issue is the result of both hoisting of scalars and de-currying. 15:55:15 ACTION: Jim to find in the spec why this is a problem. 15:56:19 jim: Out the next two Thursdays. 15:57:15 ADJOURNED 15:57:23 rrsagent, draft minutes 15:57:23 I have made the request to generate https://www.w3.org/2022/06/30-hcls-minutes.html dbooth