15:02:38 RRSAgent has joined #hcls 15:02:38 logging to http://www.w3.org/2016/04/26-hcls-irc 15:02:40 RRSAgent, make logs world 15:02:40 Zakim has joined #hcls 15:02:42 Zakim, this will be HCLS 15:02:42 ok, trackbot 15:02:43 Meeting: Semantic Web Health Care and Life Sciences Interest Group Teleconference 15:02:43 Date: 26 April 2016 15:07:12 hsolbrig has joined #hcls 15:07:42 Topic: Prep for Montreal 15:07:42 https://app.box.com/s/k7i68oyi6vg54pk8ebq8leue4e1v3j83 15:10:22 dbooth: discuss Michael's slides this afternoon 15:11:18 http://wiki.hl7.org/index.php?title=201605_Declarative_Mapping 15:15:06 Ken Lord's topic he wishes to discuss: 15:15:09 https://lists.w3.org/Archives/Public/public-semweb-lifesci/2016Apr/0004.html 15:15:56 thomas: concerns about a FHIR-specific mapping language 15:18:15 dbooth: Objections to giving Ken a brief time slot in Monteal? 15:19:51 Topic: ShEx examples 15:20:02 harold: i put some ShEx examples on the site 15:20:22 ... Some of grahame's examples do not match the spec. 15:20:38 ... Also need to get eric to put these into the ShEx validators 15:20:42 https://github.com/w3c/hcls-fhir-rdf/tree/gh-pages/examples 15:21:08 Tony has joined #HCLS 15:24:47 dbooth: Next steps for ShEx examples? 15:25:09 harold: Need to work with grahame on references. 15:26:10 http://hl7-fhir.github.io/medicationexample1.ttl.html 15:27:00 http://hl7-fhir.github.io/allergyintolerance-example.ttl.html 15:27:21 Topic: FHIR References 15:27:34 rhausam has joined #HCLS 15:27:39 https://github.com/w3c/hcls-fhir-rdf/blob/gh-pages/examples/AllergyIntolerance.shex 15:34:40 The JSON looks like this: 15:34:41 [[ 15:34:48 "patient": { 15:34:48 "reference": "Patient/example" 15:34:48 }, 15:34:50 ]] 15:39:14 tony: In the shex, there should be one more level of reference. A fhir:Reference has a reference property and a display property: http://hl7-fhir.github.io/references.html 15:41:41 https://github.com/w3c/hcls-fhir-rdf/blob/gh-pages/examples/Reference.shex 15:44:47 Differences in Grahame's model -- sb. fhir:Reference.link vs. fhir:refernce 15:45:32 tony: we added a fhir:Reference.link instead of grahame's fhir:reference to point to the referenced object. 15:48:31 15:48:35 15:48:50 Michael VDZ argues for leaving it on the top namespace 15:48:56 EricP: WHy do we have something different in RDF than in JSON XML 15:49:11 michael: Better to put it at the top level of the fhir: namespace, like grahame does it: fhir:reference . 15:49:50 15:49:57 15:50:03 eric: What if we use a relative URI? 15:50:03 15:50:09 15:51:17 eric: Is a FHIR processor expected to recognize http://fhir.example/Patient/example and Patient/example as referring to the same resource? 15:52:42 ... Will it treat them as identical? Will it try to serialize them the same way? 15:53:32 mvdzel has joined #HCLS 15:53:35 ... If there is an expectation that everything is resolved against the base, then those would be serialized the same way. 15:54:17 dbooth: Need to be able to round-trip 15:57:35 dbooth: Anything in double-quotes is a literal in RDF. 15:59:37 I have to leave - I've got another meeting. Will see you at the afternoon meeting today... 16:00:38 dbooth: because of the round-tripping requirement, I think we need to maintain the relative URIs 16:02:39 dbooth: Canonical FHIR JSON does not define a way to normalize references; therefore relative URIs need to stay relative and abs URIs need to stay abs. 16:03:44 ISSUE: Do we need a fhir:reference (name TBD) whose value is an RDF URI of the referent? 16:03:44 Created ISSUE-23 - Do we need a fhir:reference (name tbd) whose value is an rdf uri of the referent?. Please complete additional details at . 16:05:10 ISSUE: Must absolute and relative references be round tripped as is? 16:05:10 Created ISSUE-24 - Must absolute and relative references be round tripped as is?. Please complete additional details at . 16:05:50 eric: i.e., do we need to maintain the distinction between relative and absolute references? 16:06:58 ... when round-tripping? 16:08:06 ACTION: dbooth to ask Grahame and Lloyd 16:08:06 Created ACTION-54 - Ask grahame and lloyd [on David Booth - due 2016-05-03]. 16:08:19 Topic: 5pm call 16:08:57 Who can make it? dbooth, harold, eric, rob 16:11:05 Topic: Michael's presentation in Montreal 16:13:24 https://app.box.com/s/k7i68oyi6vg54pk8ebq8leue4e1v3j83 16:13:41 michael: I don't know what the @base URI should be 16:13:54 ... Might not have one if FHIR is being submitted 16:15:08 michael: Also fhir-net-api puts 'Component' in the names 16:18:05 dbooth: RDF does not have relative URIs, but certain RDF serializations do. in contrast, the FHIR model and FHIR JSON and FHIR XML do have relative URIs. 16:21:17 michael: rdfDotNet always generates xsd: prefix instead of xs: . 16:21:31 dbooth: We decided to standardize on using xs: 16:27:54 michael: Question about bundle reference. Should it just point to the referenced MedicationOrder object, instead of embedding it? 16:28:32 dbooth: how will it impact round tripping? 16:32:51 bye have to go, will add some more examples to the slides and tty in Montreal 16:48:42 ADJOURNED 16:48:48 Chair: David Booth 16:49:55 Present: Tony Mallia, Michael Van Der Zel, EricP, Rob Hausam, David Booth, Thomas Lukasik 16:50:03 rrsagent, draft minutes 16:50:03 I have made the request to generate http://www.w3.org/2016/04/26-hcls-minutes.html dbooth 17:10:01 TallTed has joined #hcls 19:05:36 Zakim has left #hcls 21:05:11 hsolbrig has joined #hcls 21:06:13 dbooth has joined #hcls 21:11:23 rhausam has joined #HCLS 21:14:04 { a [fhir:PatientReference]?, fhir:uri.id @?, fhir:Reference.link @?, fhir:Reference.reference @? } 21:17:21 { a [fhir:PatientReference]?, fhir:Element.id @?, fhir:Element.extension @*, fhir:Reference.link @?, fhir:Reference.reference @? fhir:Reference.display @? } 21:18:28 http://piratepad.net/ericP 21:24:01 Topic: ======== 5pm Teleconference =========== 21:24:18 Topic: FHIR References 21:29:04 # Grahame is generating: 21:29:04 fhir:AllergyIntolerance.patient [ 21:29:04 fhir:l ; 21:29:04 fhir:Reference.reference [ fhir:value "Patient/example" ] 21:29:05 ]; 21:29:05 21:29:45 AGREED: Change fhir:reference to fhir:link to avoid confusion. 21:30:32 AGREED: We prefer fhir:link (at top level of FHIR namespace) instead of fhir:Reference.link, because fhir:Reference.link misrepresents itself as a property of fhir:Reference 21:31:03 # Grahame should be generating: 21:31:03 fhir:AllergyIntolerance.patient [ 21:31:03 fhir:link ; 21:31:03 fhir:Reference.reference [ fhir:value "Patient/example" ] 21:31:04 ]; 21:37:29 Present+ David Booth, EricP, Harold Solbrig, Rob Hausam 21:45:39 harold: I like having a type arc on a reference, which is specific about the target type, such as fhir:PatientReference instead of a generic fhir:Reference . 22:06:06 AGREED: If we include a type arc on a reference (such as the object of fhir:AllergyIntolerance.patient) it should be specific to the target type, such as fhir:PatientReference instead of fhir:Reference 22:06:39 rrsagent, draft minutes 22:06:39 I have made the request to generate http://www.w3.org/2016/04/26-hcls-minutes.html dbooth 22:13:56 dbooth: Still need to decide whether the type arc on a reference should be required, optional or not used. 22:13:59 ADJOURNED 22:14:04 rrsagent, draft minutes 22:14:04 I have made the request to generate http://www.w3.org/2016/04/26-hcls-minutes.html dbooth 23:00:07 dbooth has joined #hcls