14:57:56 RRSAgent has joined #hcls 14:58:00 logging to https://www.w3.org/2025/09/25-hcls-irc 14:58:01 rrsagent, make logs public 14:58:07 Meeting: FHIR RDF 14:58:10 Chair: David Booth 15:11:39 Topic: Issues list 15:11:40 https://github.com/w3c/hcls-fhir-rdf/issues 15:24:11 dbooth: Should the shex and/or owl be considered normative? 15:26:08 s/normative/authoritative/ 15:27:29 AGREED: View shex as authoritative iff FHIR views xml schema as authoritative 15:28:30 dbooth: What about owl? 15:28:52 gaurav: owl should be authoritative unless it conflicts 15:29:22 detlef: Might be hard to get owl to a reliable level 15:31:43 ericp: shex is authoritative for content model, owl is authoritative for inference, rdf page describes the mapping that shex gives you .... 15:32:02 ... Like in W3C you need two independent impls 15:32:25 ... I don't think any format pages for FHIR have made the claim that you only need to read one page. 15:33:32 ... Format pages give a flavor of what to do, and additional rules, but a valid doc is almost entirely defined by the schema, modulo semantics that need to be expressed in prose 15:34:51 dbooth: So a valid piece of fhir rdf needs to conform to rdf page prose, shex and owl 15:35:16 ericp: But anything that conforms to the shex will conform to the owl. 15:38:18 tim: https://github.com/w3c/hcls-fhir-rdf/issues/176 15:38:32 tim: They want to make R6 as backward and forward compatible as possible. 15:39:12 ... If we were to make changes to the OWL or shex after R6, that would break usage of OWL or shex, then that would go against the idea of it being "normative" maturity level. 15:39:36 ... That's why I thought, for R6, we should ensure that any new changes would be backward and forward compatible. 15:39:54 ericp: If we make something inconsistent, can we do bug fixes? 15:40:22 tim: I think so. Look at what was done for R5. They did new releases, like v4.01 15:41:54 dbooth: If something in the spec is mutually inconsistent, it would have to be fixable. 15:42:21 tim: Shex doesn't have a full representation of valueset bindings. 15:42:46 ... If we add that, technically it adds constraints to previous versions, but it's more consistent w FHIR. 15:43:47 tim: We're changing fhir:link to fhir:l . That's a big change. Should get that into R6, and not change it after R6. 15:48:11 ericp: Adding constraints to shex breaks existing invalid RDF. 15:48:21 dbooth: agreed. 15:48:48 tim: The real breaking changes are things like fhir:link to fhir:l , and any turtle serializations. 15:51:10 AGREED: Focus on turtle changes and consequent shex and owl for R6, and other shex and owl enhancements are lower priority for R6 15:53:09 dbooth: Needing update: examples (Jim done, but not yet PR), shex, owl, HAPI. 15:54:16 tim: I can do the shex and the owl generation. 15:56:19 ericp: I tried to do a test suite with a few FHIR resources with some datatypes and exploit most of the struct def functionality. 16:02:36 ADJOURNED 16:15:22 TallTed has joined #hcls 16:42:46 Present: Eric Jahn, Erich Bremer, EricP, Jim Balhoff, Gaurav Vaidya, David Booth, Detlef Grittner, Tim Prudhomme 16:42:53 rrsagent, draft minutes 16:42:55 I have made the request to generate https://www.w3.org/2025/09/25-hcls-minutes.html dbooth 16:43:24 i/ADJOURNED/ericp: I can do HAPI 16:43:28 rrsagent, draft minutes 16:43:29 I have made the request to generate https://www.w3.org/2025/09/25-hcls-minutes.html dbooth 16:44:30 s/consequent shex and owl/consequent shex and owl changes/ 16:44:41 rrsagent, draft minutes 16:44:43 I have made the request to generate https://www.w3.org/2025/09/25-hcls-minutes.html dbooth