00:27:03 RRSAgent has joined #hcls 00:27:07 logging to https://www.w3.org/2024/06/28-hcls-irc 00:27:10 rrsagent, make logs public 00:27:26 rrsagent, bye 00:27:26 I see no action items 00:27:37 RRSAgent has joined #hcls 00:27:37 logging to https://www.w3.org/2024/06/28-hcls-irc 00:27:44 rrsagent, make logs public 00:30:08 Meeting: FHIR RDF 00:30:08 Chair: David Booth 00:30:08 Topic: DICOM 00:30:08 erich: Changed my RDF generation from DICOM to match what we've discussed. 00:30:09 erich: Want to be able to do an HTTP Range request for part of the data. 00:30:09 eric: How often would you need a smarter server, that understands range requests on multiple axes, specific to images? 00:30:12 erich: With 50 lines of zip code I could pull out tiles from the client. 00:30:14 ... Open seadragon knows how to ask for a minimum set of tiles. 00:30:16 ... Server can return back the layers and tiles. 00:30:18 erich: These are 2D images, not 3D. 00:30:20 eric: Some have converted these OIDs into URNs. Benefit of that? 00:30:22 s/eric/erich/ 00:30:24 eric: Not much practical difference 00:30:26 dbooth: They're more recognizable as URNs 00:30:30 eric: Use/mention issue. If I say "I'm IDed by this URL", then I hav eboth a birthdate and a content link, which seems silly. 00:30:33 eric: Advantage of having as an IRI is it can be the subject of a triple. 00:30:35 erich: Might also use dcm:Modality instead of dcm:0080060. 00:30:37 detlef: the name is 1:1 with the number. THe number is used in data transfer because it is fixed length. 00:30:40 https://github.com/w3c/hcls-fhir-rdf/issues/141 00:30:42 detlef: Should we use xsd datatypes or DICOM types? 00:30:44 .... Talked w colleague who came up with option 9. He likes dicom datatypes very much. 00:30:46 ... You could have custom types that are subtypes of xsd:string 00:30:48 ... They behave like string. 00:30:50 ... If they are actually numbers, you have to cast them to add them. 00:30:52 .. But the backend uses SQL92 00:30:54 ... Could he create a schema to make to XML 00:30:56 erich: i like dicom datatypes, because it keeps aligned w dicom. 00:31:00 ... But xsd are better for SPARQL 00:31:01 ... Also times need different cases converted to xsd. 00:31:03 ... XSD types make it easier to use in SPARQL, though the custom types may be better for data transfer to others. 00:31:06 detlef: Some want to interpret the data without the schema. Maybe have VR optionally included? 00:31:10 erich: Like about 5: Similar to DICOM JSON. But don't like that it creates a lot of extra triples i don't use. 9c makes efficient sparql. I'd favor 9c and 10. 00:31:11 https://github.com/w3c/hcls-fhir-rdf/issues/141 00:31:13 https://dicom.nema.org/medical/dicom/current/output/html/part16.html 00:31:15 Date: 26-Jun-2024 00:31:41 Present: David Booth, Gaurav Vaidya, Detlef Grittner, Erich Bremer, EricP 00:31:49 ADJOURNED 00:31:57 rrsagent, draft minutes 00:31:59 I have made the request to generate https://www.w3.org/2024/06/28-hcls-minutes.html dbooth 00:32:47 Meeting: FHIR RDF 00:33:18 rrsagent, draft minutes 00:33:20 I have made the request to generate https://www.w3.org/2024/06/28-hcls-minutes.html dbooth 00:33:27 Chair: David Booth 00:33:39 rrsagent, draft minutes 00:33:40 I have made the request to generate https://www.w3.org/2024/06/28-hcls-minutes.html dbooth