14:55:42 RRSAgent has joined #hcls 14:55:46 logging to https://www.w3.org/2025/10/02-hcls-irc 14:55:47 rrsagent, make logs public 14:55:51 Meeting: FHIR RDF 14:55:54 Chair: David Booth 15:03:44 Topic: R6 triage 15:04:57 dbooth: I think #172 (Issues with using FHIR R5 ShEx) can be done after R6, because it does not affect the validity of any FHIR RDF data. It only affects ShEx usability and precision. 15:04:57 https://github.com/w3c/hcls-fhir-rdf/issues/172 15:05:51 AGREED 15:06:27 dbooth: Similarly, I think #177 (OWL polymorphic types + references), #178 (OWL punning issues) and #179 (OWL hierarchy fixes) can be done after R6, because they do not affect the validity of any FHIR RDF data. They only affects OWL usability and precision. 15:06:27 https://github.com/w3c/hcls-fhir-rdf/issues/177 15:06:27 https://github.com/w3c/hcls-fhir-rdf/issues/178 15:06:27 https://github.com/w3c/hcls-fhir-rdf/issues/179 15:07:30 tim: It includes both bug fix and improvement 15:10:52 ... already implemented fixes for these. 15:12:05 tim: These changes also implement the fhir:link --> fhir:l 15:13:02 dbooth: Can we approve #177 for inclusion in R6? 15:14:00 dbooth: the fhir:l change needs to be in R6 15:18:06 AGREED: the fhir:l change needs to be in R6 15:19:35 AGREED: Other than the fhir:l change, 177, 178 and 179 could wait until after R6 15:22:02 AGREED: 167 and 168 can be done after R6 15:23:34 dbooth: Also #171 (Add a documentation page for all the IRI prefixes currently on THO) after R6? I think it can be an "informative" addition, rather than normative/authoritative. 15:23:34 https://github.com/w3c/hcls-fhir-rdf/issues/171 15:25:36 jim: There are some hard-coded URIs for LOINC and MeSH, but they don't use the IRI stems in THO 15:27:20 dbooth: I think THO repo can update independently of the FHIR core versioning 15:27:22 ken: Yes, that's the intent. 15:27:41 AGREED: #171 can be after R6 15:28:30 Topic: Issue 120: Syntax of added fhir:l links 15:28:30 dbooth: At 15:28:30 https://github.com/w3c/hcls-fhir-rdf/issues/120#issuecomment-3342077572 Tim replied: "Yes and we should recommend here that they SHOULD be generated, but not specify how." 15:28:30 dbooth: Should we specify the URI syntax in the rdf.html page? 15:30:33 tim: For References, they should be constrained by the Reference types, e.g., for Patient, "Patient" should be in the link. 15:31:03 ... But for URIs the literals should just be turned links directly. 15:34:47 dbooth: We'll specify the location of where the fhir:l links go, but what about the syntax of those links? 15:36:21 AGREED: Yes, specify what the syntax SHALL be 15:37:03 dbooth: And that will include the special case for canonical, from pipe to query string, 15:37:20 Topic: Scheduling extra calls 15:37:20 dbooth: Nov 1 R6 deadline is rapidly approaching. Should we schedule more FHIR RDF calls? Add Mondays at 11am Boston time? 15:39:20 AGREED: Add Tuesdays 11am Boston time 15:42:46 Topic: Issue 120 15:43:15 tim: Might be able to do HAPI changes after R6 deadline 16:02:10 Topic: FHIR Ontology 16:02:36 ken: This work on the FHIR ont could be helpful to us, because the FHIR data model has been critical in our ont. 16:02:58 ... Would be really helpful to have a powerpoint presentation on it. 16:03:16 ... What are the objectives and mission of this work? 16:03:45 ericp: Slides I did for SWAT4LS might be helpful? 16:05:03 ACTION: DBooth to send Ken previous status slides 16:05:43 tim: Also copy me 16:12:42 Topic: Yellow schemas 16:13:13 ACTION: Dbooth to create an issue to add Turtle to XML column on datatypes page 16:16:31 AGREED: Add fhir:l to Reference yellow schema 18:02:40 dbooth has joined #hcls 18:20:04 Present: Ken Lord, Eric Jahn, Jim Balhoff, Erich Bremer, Detlef Gritner, EricP, David Booth, Tim Prudhomme 18:37:30 ADJOURNED 18:37:35 rrsagent, draft minutes 18:37:37 I have made the request to generate https://www.w3.org/2025/10/02-hcls-minutes.html dbooth