14:58:22 <RRSAgent> RRSAgent has joined #hcls
14:58:26 <RRSAgent> logging to https://www.w3.org/2025/07/17-hcls-irc
14:58:27 <dbooth> rrsagent, make logs public
14:58:32 <dbooth> Meeting: FHIR RDF
14:58:37 <dbooth> Chair: David Booth
15:02:14 <ericP> ericP has joined #hcls
15:02:23 <ericP> present+
15:03:07 <eBremer> eBremer has joined #hcls
15:03:15 <eBremer> present+
15:04:39 <dbooth> Topic: DICOM
15:05:36 <dbooth> detlef: Re UIR for private elements.  I put a proposal in issue 145
15:06:15 <dbooth> ... I think you can just use the element name.  Create  a URI from these two elements.
15:06:34 <dbooth> ... But to search it, you need to go back to the private creator ID and the ID of that element.
15:06:49 <dbooth> ... But since we don't use the URI for anything else, it's okay.
15:07:21 <dbooth> erich: I'll try that in my code.
15:07:31 <dbooth> detlef: I'll be out next week.
15:08:01 <dbooth> detlef: then I'll be out until returning Aug 21.
15:08:49 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/145
15:08:56 <dbooth> Topic: Issue 120
15:12:19 <dbooth> ericP: Both uri and canonical primitive datatypes extend URI.
15:12:50 <dbooth> dbooth: We realized that generating a fhir:link shoudl happen every time a primitive URI type is generated.
15:13:45 <dbooth> ericP: There is still an asymmetry because REference is s composite datatype, but canoncial is a primitive datatype.;
15:15:04 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/120
15:23:21 <dbooth> tim: This is where fhir:link is used (as different properties with the same name)
15:23:21 <dbooth>  "TestScript.metadata.capability.link: Links to the FHIR specification" ,
15:23:21 <dbooth> "GraphDefinition.link: Links this graph makes rules about" ,
15:23:21 <dbooth> "DeviceDefinition.link: An associated device, attached to, used with, communicating with or linking a previous or new device model to the focal device" ,
15:23:23 <dbooth> "Person.link: Link to a resource that concerns the same actual person" ,
15:23:23 <dbooth> "Bundle.entry.link: Links related to this entry" ,
15:23:25 <dbooth> "Bundle.link: Links related to this Bundle" ,
15:23:27 <dbooth> "DiagnosticReport.media.link: Reference to the image or data source" ,
15:23:29 <dbooth> "TestScript.metadata.link: Links to the FHIR specification" ,
15:23:31 <dbooth> "Patient.link: Link to a Patient or RelatedPerson resource that concerns the same actual individual" ,
15:23:33 <dbooth> "URI of a reference" .
15:23:59 <dbooth> tim: If you are adding an RDF fhir:link, you should not do it where the other kind of link is used.
15:24:59 <dbooth> ericP: How about calling it fhir:n instead of fhir:link?
15:30:49 <dbooth> jim: Here is an example generated from the current code I think: https://www.hl7.org/fhir/medicationdispense0306.ttl.html
15:31:35 <dbooth> [[
15:31:36 <dbooth> fhir:medication [
15:31:36 <dbooth>      fhir:reference [
15:31:36 <dbooth>        fhir:reference [ fhir:v "#med0303" ] ; #    Linked to a RESOURCE Medication
15:31:36 <dbooth>        fhir:display [ fhir:v "Alemtuzumab 10mg/ml (Lemtrada)" ]
15:31:38 <dbooth>      ]
15:31:40 <dbooth>   ] ; #
15:31:42 <dbooth> ]]
15:33:50 <dbooth> dbooth: If we put our fhir:link directly under capital R Reference, then there is the possibility that the other FHIR folks could put their own link property there, and we would have a clash.
15:34:01 <dbooth> ... If so, could we distinguish them by type?
15:44:26 <dbooth> jim: Need to put the version in the query string for fhir:canonical
15:45:20 <dbooth> AGREED: generate a fhir:link as a sibling of fhir:v in each primitive uri object.
15:47:33 <dbooth> AGREED: as a special case, the version needs to be moved to a query string in canonical
15:53:05 <dbooth> ericP: I'll also proto the fhir:n option
15:56:11 <dbooth> Topic: 169 Make R5 (and R6) HAPI parser/serializer for FHIR RDF easier to find
15:56:18 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/169
15:56:32 <dbooth> ericP: I was waiting until the shex and example fixes were done.
15:56:51 <dbooth> ... I'll make the PR after those are done, to get the right version into HAPI
15:57:09 <dbooth> tim: The java core library does this to produce the spec.  Does HAPI use the core one?
15:57:42 <dbooth> ericP: No, they do two different things.  The one for the spec does pretty printing, keeping comments, etc.
15:58:02 <dbooth> jim: The core parser does not parse any more.  Not used.  It only serializes.
15:58:46 <dbooth> jim: There are round trip tests for RDF, but they're disabled.
15:59:58 <dbooth> dbooth: We should make sure the HAPI round tripping works.
16:01:28 <dbooth> ericP: It parses JSON, serializes as turtle, parses as turtle.  Then it compares both of those objects for equality.
16:03:04 <dbooth> ... It failed on a bunch of things because of the core POJOs regarding contained.  The operator equals test requires the same order of elements in a list.
16:03:33 <dbooth> ... But that is fixed now by James Agnew.
16:05:32 <dbooth> tim: Issue for next week maybe https://github.com/w3c/hcls-fhir-rdf/issues/167
16:12:51 <dbooth> present: Tim Prudhomme, EricP, Jim Balhoff, Detlef Grittner, Erich Bremer, David Booth
16:12:57 <dbooth> ADJOURNED
16:13:04 <dbooth> rrsagent, draft minutes
16:13:05 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/17-hcls-minutes.html dbooth