15:58:26 <RRSAgent> RRSAgent has joined #hcls
15:58:30 <RRSAgent> logging to https://www.w3.org/2024/11/21-hcls-irc
15:58:32 <dbooth> rrsagent, make logs public
15:58:45 <dbooth> Meeting: FHIR RDF
15:58:45 <dbooth> Chair: David Booth
16:06:55 <TallTed> TallTed has joined #hcls
16:10:40 <dbooth> Topic: What should a DICOM RDF file use as a primary subject?
16:10:40 <dbooth> #142
16:10:48 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/142
16:12:13 <dbooth> detlef: Suggest having instance IRI in the file.
16:12:36 <dbooth> ... The DICOM dir has relative path of files.
16:13:58 <dbooth> ... If we had a URI for each entity, then you can merge them easily.
16:14:30 <dbooth> ... I want this ability, regardless of what we use for subject URI.
16:14:53 <dbooth> erich: I like this idea
16:15:07 <dbooth> ... of the DICOM directory
16:15:38 <dbooth> ACTION:  Detlef to share an example in the issue
16:17:20 <dbooth> erich: dcm3j has the ability to do the DICOM dir
16:17:52 <dbooth> ... Keeping metadata on the files, what to think how to use linked web storage
16:18:23 <dbooth> ... If there's a concept of a DICOM dir, it might well w linked web storage.
16:19:17 <dbooth> ... When you do a GET on SOLID storage for a particular container, I see DICOM files, and I GET those
16:19:57 <dbooth> ... And it could give the RDF conversion of the image as an enrichment.
16:20:12 <dbooth> ericp: You conneg to RDF
16:22:54 <dbooth> erich: If there's an official RDF DICOM representation, then linked web storage gives a way to get to it.
16:24:29 <dbooth> ACTION: Erich to look into DICOM directories
16:38:04 <dbooth> Topic: How best to represent DICOM lists with missing elements, in FHIR RDF?
16:38:04 <dbooth> #141
16:38:11 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/141
16:38:58 <dbooth> AGREED: Option 10, though we have not yet decided on namespace for dcm: prefix.
16:40:45 <dbooth> Topic: Current work as it relates to prior DICOM RDF work #143
16:40:53 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/143
16:42:35 <dbooth> erich: This is just an RDF vocabulary of DICOM terms.  Just a URI space for those terms.  It's still maintained.
16:42:43 <dbooth> https://dicom.nema.org/medical/dicom/current/output/chtml/part16/chapter_d.html
16:43:12 <dbooth> erich: We can close this issue with no change.  No motivation for changing the namespace.
16:43:50 <dbooth> AGREED: No action needed. closing issue.
16:47:45 <dbooth> Topic: DICOM: How to handle InlineBinary and BulkDataURI?
16:47:45 <dbooth> #144
16:47:55 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/144
16:48:03 <dbooth> ACTION: Erich to look at how DICOM Web is handling this.
16:49:47 <dbooth> Topic: DICOM Private Data Elements in DICOM RDF #145
16:49:54 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/145
16:50:22 <dbooth> detlef: DICOM doesn't define how the private identifiers are assigned.
17:07:43 <dbooth> ericp: The "private creator 1" part is analogous to a URI, somehting like "IBM" or "Siemens"
17:08:36 <dbooth> ... The attribute tag, like "(0027,0010)" is like a bnode.
17:09:35 <dbooth> ADJOURNED
17:10:05 <dbooth> Present: Rob Hausam, Jim Balhoff, Detlef Grittner, Erich Bremer, EricP
17:10:23 <dbooth> rrsagent, draft minutes
17:10:25 <RRSAgent> I have made the request to generate https://www.w3.org/2024/11/21-hcls-minutes.html dbooth