15:05:10 RRSAgent has joined #hcls 15:05:14 logging to https://www.w3.org/2025/09/11-hcls-irc 15:05:15 rrsagent, make logs public 15:05:18 Meeting: FHIR RDF 15:05:21 Chair: David Booth 15:07:04 Topic: Issue 170 handle semantics of hash ids 15:07:12 https://github.com/w3c/hcls-fhir-rdf/issues/170 15:41:41 jim: SHould contained resources be identified the same way as Bundled resources? Our proposed resolution for issue 170 (contained) differs from how Bundles are handled currently. 15:41:44 tim: https://build.fhir.org/references.html#contained 15:41:44 Contained resources share the same internal id resolution space as the parent resource (for id attributes, see Narrative references). 15:41:44 When resolving references, references are resolved by looking through the 'container' resource - the one that contains the other resources. Since there are no nested contained resources, there is only one container resource. 15:41:57 tim: Fragment-only URL References to contained resources are never resolved outside the container resource. Specifically, resolution stops at the elements Bundle.entry.resource and Parameters.parameter.resource, but not at DomainResource.contained. To reference a contained resource in a different entry within a Parameters or Bundle (or anywhere else), the reference must include the containing resource. E.g. Observation/123#pat. 15:56:48 ericp: We need to make those absolute URIs 15:58:01 jim: For better robustness we have decided to output the hash ID appended to the parent URI, e.g.: . Also, the identifiers for contained do not follow exactly the same rules as the bundle examples (https://build.fhir.org/references.html#contained). If no parent URI (blank node?) just output as relative hash URI. 15:58:11 see issue: https://github.com/w3c/hcls-fhir-rdf/issues/170 15:59:11 ADJOURNED 15:59:30 present: David Booth, EricP, Erich Bremer, Tim Prudhomme, Jim Balhoff 15:59:39 rrsagent, draft minutes 15:59:40 I have made the request to generate https://www.w3.org/2025/09/11-hcls-minutes.html dbooth