16:07:06 RRSAgent has joined #hcls 16:07:06 logging to http://www.w3.org/2015/12/01-hcls-irc 16:07:08 RRSAgent, make logs world 16:07:08 Zakim has joined #hcls 16:07:10 Zakim, this will be HCLS 16:07:10 I do not see a conference matching that name scheduled within the next hour, trackbot 16:07:11 Meeting: Semantic Web Health Care and Life Sciences Interest Group Teleconference 16:07:11 Date: 01 December 2015 16:08:21 Topic: FHIR RDF 16:08:22 http://wiki.hl7.org/index.php?title=File:FHIR_RDF_Sample_side_by_side_comparisons.pdf 16:09:14 Present: David Booth, Eric P, Darrel Woelk, Harold Solbrig, Tony Mallia 16:13:06 Tony has joined #HCLS 16:14:16 Topic: Orlando HL7 Meeting 16:14:32 Will be there: Harold, David 16:14:38 Will not be there: Tony 16:15:06 Topic: FHIR RDF 16:15:23 http://wiki.hl7.org/index.php?title=File:FHIR_RDF_Sample_side_by_side_comparisons.pdf 16:16:33 Tony: Diagram on line 134 16:16:55 ... CodeableConcept has Codings, and a Coding has code. 16:17:20 ... The blue lines say that ConceptBase is a superclass of CodeableConcept, Coding and code. 16:19:57 ... Since a ConceptBase has an object property to CodingBase, which has an object property from Coding, therefore Coding and code have a ConceptBase.coding relationship to CodingBase . 16:24:54 ACTION: Tony to update the ConceptBase etc diagram with annotations 16:24:54 Error finding 'Tony'. You can review and register nicknames at . 16:25:16 ACTION: DBooth to work with Tony on further refining the diagram 16:25:16 Created ACTION-39 - Work with tony on further refining the diagram [on David Booth - due 2015-12-08]. 16:30:18 Topic: FHIR References 16:30:28 http://wiki.hl7.org/index.php?title=File:FHIR_RDF_Sample_side_by_side_comparisons.pdf 16:30:44 line 834 16:35:36 DBooth: Line 50 is inferred from 849, but I do not think this is a kind of inference that OWL can do. 16:37:36 ... I don't think line 850 should be required on the wire for FHIR RDF: fhir:Reference.link 16:38:18 eric: the problem is that the value on line 849 is in quotes. 16:38:56 dbooth: Is that datatype sufficiently restricted that we can make that a URI instead of a string? 16:39:30 harold: Not all URIs will be directly dereferenceable. 16:40:31 ... The notion of the URI as a string is a useful abstraction, because there may be additional machinery that turns the string into a URI node. 16:42:19 dbooth: Two separate issues: 1. whether it is a string or a URI node in RDF; 2. whether that URI is dereferenceable in RDF. 16:42:45 eric: Third issue is whether you can identify the appropriate node in the graph that you get back. 16:43:17 s/whether you can/how to/ 16:43:51 ... What comes back is a blank node -- not a named URI. 16:44:16 ... Some people object to using the same URI for a named graph and a distinguished URI within that graph. 16:44:49 tony: The file that is returned is not equivalent to the root object. 16:45:07 eric: My old XSLT turns bundles into atoms. 16:49:15 https://hl7-fhir.github.io/allergyintolerance.html 16:49:31 https://hl7-fhir.github.io/allergyintolerance-definitions.html#AllergyIntolerance.patient 16:49:42 https://hl7-fhir.github.io/references.html#Reference 16:50:05 https://hl7-fhir.github.io/references-definitions.html#Reference.reference 16:51:31 But the definition describes it as a URL. 16:53:02 [[ A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. 16:53:02 ]] 16:57:11 dbooth: It seems like it would be useful to have line 849 be an RDF URI node (instead of string). Would there be harm in doing so? 16:59:55 Eric: Some zealots would object to using a URI node for the dereferenceable thing and the patient record. 17:07:50 dbooth: I do not see how we could derive a new (different) URI on line 850 from the URI on line 849, because the URI on line 849 is explicitly permitted to have fragIDs already. 17:10:34 eric: If the root node is a blank node, there are other things inside that are relative to it, which are identified by fragIDs. That implies that FHIR already made the decision for us, to use the same URI for the endpoint and the root node. 17:12:25 tony: When we drill into FHIR bundles, that may help us to sort this out. 17:13:36 ISSUE: Should fhir:Reference.reference->value be a string or an RDF URI node? 17:13:36 Created ISSUE-16 - Should fhir:reference.reference->value be a string or an rdf uri node?. Please complete additional details at . 17:17:44 ISSUE: Should the rdf:types be explicit on the wire or inferred? 17:17:44 Created ISSUE-17 - Should the rdf:types be explicit on the wire or inferred?. Please complete additional details at . 17:18:58 dbooth: I like having the rdf:types there, because they are convenient. If they are not there, then a reasoner must be run before manipulating the RDF. 17:19:21 eric: Propose making it optional, but make the XSLT generate it as a teaching aid. 17:20:59 harold: I think type will be required if we are dealing with extensions. 17:21:17 eric: When you get XML or JSON, the top says "I'm a patient". 17:23:44 Topic: Afternoon call 17:23:55 tony: I cannot make it today 17:24:06 dbooth: Let's cancel it today. 17:24:14 ADJOURNED 17:24:18 rrsagent, draft minutes 17:24:18 I have made the request to generate http://www.w3.org/2015/12/01-hcls-minutes.html dbooth 17:25:34 Chair: David Booth 17:25:36 rrsagent, draft minutes 17:25:36 I have made the request to generate http://www.w3.org/2015/12/01-hcls-minutes.html dbooth 18:36:36 Zakim has left #hcls