14:58:50 <RRSAgent> RRSAgent has joined #hcls
14:58:54 <RRSAgent> logging to https://www.w3.org/2023/06/22-hcls-irc
14:58:58 <dbooth> rrsagent, make logs public
14:59:05 <dbooth> Meeting: FHIR RDF
14:59:11 <dbooth> Chair: David Booth
15:04:54 <dbooth> Topic; Concept IRIs
15:05:27 <dbooth> gaurav: https://jira.hl7.org/browse/UP-406 is now queued for implementation
15:06:12 <dbooth> gaurav: Also looking at coding system, to find IRI stems for all of them.  Found the publisher field.  We cannot always ignore HL7 publisher field, because sometimes they're referencing external vocabs.
15:06:24 <dbooth> ... But good for most.
15:07:10 <dbooth> ... If I filter out everything that's a draft or retired, that leaves 755 code systems and 424 naming systems.
15:07:28 <jose-cdbtr> jose-cdbtr has joined #hcls
15:12:19 <dbooth> gaurav: next step may be 1. figure out the number of systems needing IRI stems.  That will scope the work.
15:12:50 <dbooth> ... Another option: 2. Make larger and large change requests for adding the IRI stems.
15:13:13 <dbooth> ... From that approach, maybe we should come up with a short list of the ones most needing IRI stems.
15:13:39 <dbooth> dbooth: Sounds like a good start.
15:15:56 <dbooth> ... Maybe ramp up to 10-20 next
15:17:12 <dbooth> Topic: fhir:link missing from MedicationStatement.subject #121
15:17:37 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/121
15:24:01 <dbooth> eric: The problem is that the root node is a blank node, so it doesn't have a base URL for creating the subject URL.
15:26:09 <jose-cdbtr> jose-cdbtr has left #hcls
15:27:50 <dbooth> eric: We could make them relative URLs, so wherever people put them, they'll work.
15:31:40 <dbooth> ... Or we could use example.org
15:33:37 <dbooth> eric: If we use relative URL, for a patient, it will become "../Patient/123"
15:35:28 <dbooth> dbooth: example.org seems like a less risky approach.
15:35:45 <dbooth> eric: Examples are not set up to be an imitation FHIR server, because they're all in the same dir.
15:36:17 <dbooth> ... But we could put them into their own directories -- 190 directories.
15:37:41 <dbooth> eric: The XML and JSON examples could also be set up that way.
15:40:49 <dbooth> dbooth: Seems like it's worth raising an issue with FHIR in general.
15:41:45 <dbooth> ACTION: DBooth to ask on zoom about putting the examples in subdirectories
15:46:56 <dbooth> Topic: datatype for xhtml #119
15:47:04 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/119
15:47:19 <dbooth> eric: We decided to adopt the xhtml literal type.
15:48:08 <dbooth> ACTION: Jim and Deepak to implement the xhtml literal type
15:49:48 <dbooth> jim: Will get a PR ready
15:50:02 <dbooth> dbooth: Lets' bundle multiple PRs in to the same Jira ticket
15:53:38 <dbooth> Topic: align Reference with canonical
15:53:38 <dbooth> #120
15:53:46 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/120
15:53:52 <dbooth> (replaces issue 70)
15:54:02 <dbooth> eric: Inclined toward option 2
15:54:58 <dbooth> dbooth: Should solicit more community input before going with option 1.
15:59:40 <dbooth> ... or 2
16:02:44 <dbooth> s/option 2/option 1/
16:10:05 <dbooth> eric: If I get a bundle, that link is useful.
16:11:07 <dbooth> ... One of the observations in the bundle may have an abs url, and another in the bundle may have only a fragment.  I want to know if they point to the same thing.
16:11:31 <dbooth> Present: Gaurav Vaidya, Jim Balhoff, Rob Hausam, David Booth, EricP
16:15:24 <dbooth> dbooth: Need to first find out if the vertical bar can appear after the hash.    That will determine whther it is always an IRI.
16:17:34 <dbooth> ACTION: eric to look for a canonical with a vertical bar and frag ID
16:21:55 <dbooth> ACTION: eric to ask on zulip about hash and vertical bar in a canonical
16:21:59 <dbooth> ADJOURNED
16:22:03 <dbooth> rrsagent, draft minutes
16:22:04 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/22-hcls-minutes.html dbooth