15:03:48 RRSAgent has joined #hcls 15:03:48 logging to http://www.w3.org/2016/04/19-hcls-irc 15:03:50 RRSAgent, make logs world 15:03:50 Zakim has joined #hcls 15:03:52 Zakim, this will be HCLS 15:03:52 ok, trackbot 15:03:53 Meeting: Semantic Web Health Care and Life Sciences Interest Group Teleconference 15:03:53 Date: 19 April 2016 15:04:35 Chair: David Booth 15:05:20 Sajjad_Hussain has joined #hcls 15:05:40 Topic: ShEx generation 15:06:08 harold: I submitted a reasonably complete shex generated. Ball is now in Grahame's court. 15:06:46 ... Made some changes to references, where there is a choice of person or organization. 15:06:56 ... Since the type is a URI, how do you record that fact in shex? 15:07:06 ... We made a proposal on that. 15:07:23 ... Shex gives you a choice of a simple URI or a shape. 15:08:52 { a [fhir:PatientReference]?, fhir:uri.id @?, fhir:uri.extension @*, fhir:uri.value (xsd:anyURI OR @) } 15:09:49 fhir:Observation.subject ( @ OR @ OR @ OR @ )?, 15:11:35 { fhir:uri.id @?, fhir:uri.extension @*, fhir:uri.value xsd:string? } 15:14:14 { a [fhir:PatientReference]?, fhir:uri.id @?, fhir:uri.extension @*, fhir:uri.value (xsd:anyURI OR @)? } 15:15:03 ericP2 has joined #hcls 15:17:55 https://hl7-fhir.github.io/observation-example.ttl.html 15:18:50 The snippet: 15:18:50 [[ 15:18:51 fhir:Observation.subjectReference [ 15:18:51 fhir:reference ; 15:18:52 fhir:Reference.reference [ fhir:value "Patient/example" ] 15:18:54 ]; 15:18:56 ]] 15:20:06 eric: Should we use URIs for RDF linkage or a string? A string would require an additional step to connect it. 15:20:14 ... I favor relative URIs. 15:21:05 tony: We discussed having both the string and a URI. 15:21:27 ... And the URI may be the same as the string. 15:22:02 ... We discussed using reference.link for the URI. 15:25:29 eric: XML schema for FHIR XML treats a patient ref and a provider ref identically -- no validation beyond the fact that it is a reference. 15:25:40 [[ 15:25:42 15:25:46 ]] 15:25:58 (well that didn't work, but...) 15:27:04 eric: We can be more specific in RDF about the type. We can do much better validation than that. 15:27:39 @dbooth -- is the formated paste key "The snippet:"? 15:28:09 q+ 15:28:12 ... But we may have to do that modally: one shex that enforces that; one that doesn't. Validating a FHIR resource in isolation would use the looser one; validating a collection of resources together could use the stricter one. 15:28:54 q- 15:29:28 harold: One thing disconcerting: the URI shape and patient ref shape do not line up well with what grahame was publishing as the emitted RDF. 15:30:01 ... Observation.subject has been turned into observation.subject.reference 15:30:17 Tony has joined #HCLS 15:31:55 ... Grahame's RDF says fhir:Observation.subjectReference 15:32:14 https://hl7-fhir.github.io/observation-example.ttl.html near the bottom 15:34:19 lloyd: Guessing it's a bug in his code 15:34:58 15:36:11 harold: Could that equally well say 15:37:06 lloyd: Three styles of URL. 1. It could be a full URL. 2. Local -- same server; 3. Contained reference, which would not have "Patient/" 15:38:18 ... The first two require "Patient/" in them. 15:39:34 dbooth: Next-to-last path segment in the URI? 15:39:55 lloyd: Yes, or fourth-to-last if you are doing version-specific references. 15:40:22 eric: Then you need to know that the versions are not using those strings. 15:40:53 ... Then you could parse from the right to figure it out. 15:42:09 ... We could make them all look liked contained if when converting to FHIR RDF, you have a ref to Patient/example, then you add a triple giving the type. 15:45:26 dbooth: Should we have another stricter shex to check the type of the referent? 15:48:22 ... If we make one, would it be an alternate download? As a separate tab? 15:49:15 ... Would the type arc be required in RDF? 15:50:10 lloyd: You can easily write a regex. Do we really want to? 15:51:31 dbooth: Inclined to leave out the type arc from the reference. 15:53:27 ... Seems like it might require messy parsing to include the type arc in every reference. 15:55:20 ... Also a convenient delineation to have the type arc only when you have the actual resource object. 15:57:43 tony: Validate after you pull in that other resource. 15:59:10 ISSUE: Should a type arc be required for the target of a reference? 15:59:10 Created ISSUE-21 - Should a type arc be required for the target of a reference?. Please complete additional details at . 15:59:24 ISSUE: Should a type arc be allowed for the target of a reference? 15:59:24 Created ISSUE-22 - Should a type arc be allowed for the target of a reference?. Please complete additional details at . 16:03:49 ACTION: harold to make a dir on github for shex 16:03:49 Created ACTION-53 - Make a dir on github for shex [on Harold Solbrig - due 2016-04-26]. 16:03:57 Topic: 5pm call 16:04:15 tony and harold cannot make it; eric is at risk. 16:04:26 dbooth: I'll cancel the 5pm call. 16:04:30 ADJOURNED 16:05:15 rrsagent, draft minutes 16:05:16 I have made the request to generate http://www.w3.org/2016/04/19-hcls-minutes.html dbooth 16:06:54 Present: David Booth, Lloyd McKenzie, EricP, Harold Solbrig, Sajjad Hussain, Tony Mallia 16:07:10 rrsagent, draft minutes 16:07:10 I have made the request to generate http://www.w3.org/2016/04/19-hcls-minutes.html dbooth