15:04:52 <RRSAgent> RRSAgent has joined #hcls
15:04:56 <RRSAgent> logging to https://www.w3.org/2025/08/07-hcls-irc
15:04:56 <dbooth> Meeting: FHIR RDF
15:05:00 <dbooth> Chair: David Booth
15:06:02 <dbooth> Topic: Handle semantics of hash ids
15:06:03 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/170
15:10:09 <TallTed> TallTed has joined #hcls
15:11:37 <dbooth> dbooth: Looks good, but I wonder if it is safe to use  a relative URI there.  Does the base need to be set specially for it, or not?
15:17:55 <dbooth> tim: They're relative to the server
15:20:44 <dbooth> (Jim looked at the the FHIR documentation for IDs, and verified that it seems safe to use relative URIs.
15:22:34 <dbooth> dbooth: We lose visual  correspondence between the Turtle and the JSON
15:27:47 <dbooth> Present: EricP, Erich Bremer, Jim Balhoff, Tim Prudhomme, David Booth
15:33:55 <dbooth> ericP: Round tripping, those relative URIs will no longer be relative.
15:34:37 <dbooth> ... The root can be chopped off when round tripping, and to check it, you would have to verify that the base matches.
15:37:16 <dbooth> dbooth: What if the base doesn't match, when someone makes FHIR RDF?
15:45:54 <dbooth> tim: https://build.fhir.org/bundle.html#references
15:45:54 <dbooth> Resolving relative references against a RESTful base.
15:45:54 <dbooth> If the Bundle entry containing the reference does not have a fullUrl that matches the [RESTful URL regex] and the Bundle is a batch or transaction and the entry.request.method is POST, PUT or PATCH
15:45:54 <dbooth> take the base URL of the server that is the target of the batch/transaction and append the relative reference to it (e.g., transaction is being posted to "https://fhir.somewhere.org", then the expanded reference would be "https://fhir.somewhere.org/Patient/123"
15:45:56 <dbooth> Follow the steps for Resolving absolute references above
15:46:08 <dbooth> tim: Note that the rules for resolving references in contained resources are the same as those for resolving references in the resource that contains the contained resource. I.e. the fullUrl of the containing resource is used when determining the base for relative references, etc.
15:54:03 <dbooth> ericP: The HAPI parser of FHIR RDF can ignore those absolute URIs, and it can just use the fhir:v value that references the ID.
15:57:43 <dbooth> AGREED: To Jim's proposed solution.
15:58:25 <dbooth> Present+ Gaurav Vaidya
15:59:31 <dbooth> Topic: IRI stems
16:00:01 <dbooth> gaurav: Making spreadsheet.  Next time to add IRI stems, should to multiple at once.
16:00:10 <dbooth> https://docs.google.com/spreadsheets/d/1w0Mbkt9C9HSMg4_L9pGNDVoYzV1NzCuKbkfpnTBI56I/edit?gid=0#gid=0
16:04:09 <dbooth> dbooth: Looks good
16:04:31 <dbooth> ... And I like how you put the rationale in the assigner.display column.
16:06:46 <dbooth> gaurav: UT465 , a minor change was proposed (to change "MUST" to "SHALL")
16:06:58 <dbooth> https://jira.hl7.org/browse/UP-465
16:14:04 <dbooth> AGREED: Spreadsheet looks okay
16:16:19 <dbooth> ADJOURNED
16:17:03 <dbooth> Topic: Next meeting
16:17:25 <dbooth> Detlef is out until Aug 21.   EricP is at risk all of Aug.
16:17:30 <dbooth> ADJOURNED AGAIN
16:17:37 <dbooth> rrsagent, draft minutes
16:17:38 <RRSAgent> I have made the request to generate https://www.w3.org/2025/08/07-hcls-minutes.html dbooth
16:18:24 <dbooth> rrsagent, make logs public