15:05:32 RRSAgent has joined #hcls 15:05:32 logging to http://www.w3.org/2016/08/23-hcls-irc 15:05:34 RRSAgent, make logs world 15:05:34 Zakim has joined #hcls 15:05:36 Zakim, this will be HCLS 15:05:36 ok, trackbot 15:05:37 Meeting: Semantic Web Health Care and Life Sciences Interest Group Teleconference 15:05:37 Date: 23 August 2016 15:05:38 Topic: Join the W3C Semantic Web for Healthcare and Life Sciences community group 15:05:48 please join: https://www.w3.org/community/hclscg/ 15:07:16 Topic: Review of remaining FHIR/RDF work 15:08:02 http://wiki.hl7.org/index.php?title=RDF_for_Semantic_Interoperability#Deliverables_and_Editors 15:11:59 Sajjad has joined #hcls 15:14:16 grahame's editing policy: http://wiki.hl7.org/index.php?title=RDF_for_Semantic_Interoperability#Edits_to_the_FHIR_RDF.2Fontology_pages 15:17:10 eric worked on this page: http://w3c.github.io/hcls-fhir-rdf/spec/rdf.html 15:17:37 as a potential new version of https://hl7-fhir.github.io/rdf 15:32:10 https://hl7-fhir.github.io/ 15:39:38 eric: I propose renaming the ontology page to Linked Data. 15:48:54 dbooth: The proposal: 1. rename ontology-module.html to linked-data-module.html 2. change the title to "FHIR Linked Data Module". 15:49:32 ... 3. On the FHIR home page, put links to RDF and Ontology pages in the Linked Data module box 15:51:00 eric: Another proposal: rename the title of page https://hl7-fhir.github.io/rdf to match the XMl and JSON pages: "RDF Representation of Resources" 15:52:41 eric: Regarding deliverable 4. Formal specification of FHIR/RDF http://w3c.github.io/hcls-fhir-rdf/spec/ 16:30:22 Present: Rob Hausam, David Booth, Eric P, Harold Solbrig 16:30:25 Chair: David Booth 16:30:29 ADJOURNED 16:30:33 rrsagent, draft minutes 16:30:33 I have made the request to generate http://www.w3.org/2016/08/23-hcls-minutes.html dbooth 21:26:27 RRSAgent has joined #hcls 21:26:27 logging to http://www.w3.org/2016/08/23-hcls-irc 21:26:29 RRSAgent, make logs world 21:26:29 Zakim has joined #hcls 21:26:31 Zakim, this will be HCLS 21:26:31 ok, trackbot 21:26:32 Meeting: Semantic Web Health Care and Life Sciences Interest Group Teleconference 21:26:32 Date: 23 August 2016 21:26:34 Topic: How to name the resource root when its location is unknown? 21:26:43 https://github.com/w3c/hcls-fhir-rdf/issues/18 21:30:41 dbooth: potential options: blank node, relative URI, or skolem URI 21:30:51 ... A relative URI looks like <> 21:31:54 eric: i favor <> (the base URI) 21:32:17 GET http://a.example/some/path -> <> a fhir:Foo; fhir:identifier [ ... ] 21:32:32 grahame: That would allow only one unidentified URI in scope at at time? 21:32:54 rdf:type fhir:Foo . 21:33:09 fhir:identifier [ ... ]. 21:33:46 grahame: If I have two unidentified resources in the same graph then this would not work. 21:33:53 GET http://a.example/some/path -> a fhir:Foo; fhir:identifier [ ... ] 21:33:59 rdf:type fhir:Foo . 21:34:03 fhir:identifier [ ... ]. 21:34:53 q+ 21:35:03 tlukasik_ has joined #HCLS 21:36:39 dbooth: I'm against relative URI because they don't exist at the RDF level. In RDF *every* URI is absolute. 21:37:47 grahame: this example is different: http://hl7-fhir.github.io/parameters-example.ttl.html 21:38:21 Grahame has joined #hcls 21:38:55 ....Eric made me do it.... 21:39:58 dbooth: i think a blank node would be best aligned with the RDF model. A relative URI would become absolute when interpreted as RDF, and I'm concerned that it would not round trip well 21:41:03 rhausam has joined #HCLS 21:41:18 grahame: XML and JSON forms do not include the address of the content. The RDF form does. That's why we say that the Turtle is for reasoning, rather than interop. 21:42:10 dbooth: We haven't nailed down what constitutes round tripping. 21:42:30 grahame: For xml and json we say that the canonical form must be identical. 21:44:39 ISSUE: Define canonical FHIR RDF https://github.com/w3c/hcls-fhir-rdf/issues/34 21:44:40 Created ISSUE-39 - Define canonical fhir rdf https://github.com/w3c/hcls-fhir-rdf/issues/34. Please complete additional details at . 21:46:24 eric: Do we need to specify how the root node should be named? 21:47:36 grahame: If we say that it is a URI, but might not be unique, then if people merge data that could be a problem. 21:48:43 dbooth: I.e., if a relative URI is used <> then different data might accidentally use the same URI and users would not realize it. 21:50:19 eric: An advantage of a relative URI is that they can do sparql queries using that node and its name is stable. 21:52:11 grahame: We could put a warning in the spec. 21:54:19 dbooth: in round tripping RDF-->XML/JSON-->RDF, I don't want my URIs disappearing. 21:54:54 grahame: There's no place to put that URI in the XML or JSON 21:57:00 dbooth: We might agree to let the user decide whether to use relative, abs or blank node. 21:57:26 dbooth: What should we put in the examples? 21:57:37 eric: Relative URIs 21:57:54 dbooth: still against relative URIs in the examples. 21:58:19 dbooth: Prefer blank node used in the examples. 22:01:30 Eric agrees to blank node 22:02:50 AGREED: In the examples, we will use a blank node for the root node of the resource 22:04:20 i/I have made the request/Topic: ================== 5pm Call ================= 22:04:43 ls 22:04:49 s/ls// 22:05:19 Present: EricP, David Booth, Harold Solbrig, Rob Hausam 22:10:41 Present+ (5pm_call) Thomas_Lukasik David_Goodall Grahame_Grieve David_Booth EricP Rob_Hausam 22:24:39 rrsagent, draft minutes 22:24:39 I have made the request to generate http://www.w3.org/2016/08/23-hcls-minutes.html dbooth 22:27:50 ACTION: Eric to draft warning text about using relative URIs for the root node 22:27:50 Created ACTION-67 - Draft warning text about using relative uris for the root node [on Eric Prud'hommeaux - due 2016-08-30]. 22:27:59 ADJOURNED 22:28:02 rrsagent, draft minutes 22:28:02 I have made the request to generate http://www.w3.org/2016/08/23-hcls-minutes.html dbooth 22:32:09 dbooth has joined #hcls 22:32:21 Present+ Brian Scheller 22:32:31 rrsagent, draft minutes 22:32:31 I have made the request to generate http://www.w3.org/2016/08/23-hcls-minutes.html dbooth