Meeting minutes
DICOM
DBooth: Could have optional VR for all elements, but require the VR if needed to disambiguous.
ericP: Could push the private stuff off into another bit of graph, saying that the value of the prop is a tuple, that is the type and the list of values (w/o standoffs). That would factor out the types.
… But can only do that w homogeneous lists.
… or go directly into the list from the prop, but also saying which elements are which types. Stating that as a separate statement about the property.
… That would assume homogeneity thruoughout the doc.
detlef: I think items in a list must have the same VR.
erich: In DICOM lists they are homogeneous.
detlef: There's a different construct for sequences, that can be heterogeneous.
detlef: Property range cannot change within a document.
ericP: Goal of factoring is to make the queries easier.
dbooth: Should we make VRs optional for properties that can be uniquely determined from the schema, and required for those that need disambiguation?
erich: one of the first things I need was to move everything to native xsd types.
dbooth: For transport, if the VRs are kept, but then discarded locally when used (if not needed), would that be a good approach?
detlef: That's what's normally done.
ericP: If you have the optional VR triples in a separate file, then you can just concatenate files if you want them.
dbooth: How would someone partition their triples that way?
ericP: They'd already have to know which private data elements they're using.
erich: DICOM versions change. Need to retain the version in RDF.
dbooth: What about including all the VRs in the transport format RDF, but local users can toss out VRs they don't need.
ericP: Beginning of the instance data could say what schema instance (with version) they are using.
dbooth: But what about having the instance data (for transport) include all the VR codes, with a standoff, and then local user could discard the VR codes they don't need?
erich: Would be a simple sparql query to strip off the VR code and extra standoff.
ACTION: EricP to create a top level issue for current DICOM proposals
ADJOURNED