Meeting minutes
Issue 146
erich: It would need the SOP instance ID to make a reusable URI for it
detlef: An example: http://
(Discussing the bnode object in the list in the example Erich provided at the beginning of issue 146.)
erich: Maybe could use <urn:oid:somethingrandom/
Maybe use a relative URI like: Maybe relative URI like: <dcm:30060080/0>
erich: That's similar to my suggestion after it is expanded w the base URI
dbooth: Yes.
eric: Or we could go with a simpler solution that would allow users to choose their own URI namespace for it, which would not guarantee that indpendent users would detect the same object.
dbooth: If you use bnodes, then RDF cannot link them automatically even though, using DICOM knowledge, two bnodes are intended to represent the same thing.
ACTION: Erich to try this in his converter, w URN
erich: I'm also working on a SHACL representation of DICOM
dbooth: Relative URIs only exist at the syntactic level, for example in Turtle. RDF itself has no notion of relative URIs. They are immediately converted to absolute URIs (using whatever base URI is currently applicable) when a Turtle document is loaded into a triple store.
dbooth: In summary, if we leave those list item identifiers as bnodes, then two independent users who load the same file and understand DICOM could infer that those two first items in that list are actually the same thing, but the triplestore would not know to join them for you automatically.
ADJOURNED