provide a statement identifier #4
Description
Karen Coyle (26.07.2014)
I wanted to mention, though, that a DCMI Review Board document on
the SWAP discovered an "discrepancy" in that design that you may or may
not have uncovered as well. [1] Although the Review Board concluded that
SWAP was non-conformant with the DSP, my view is that the DSP itself has
an issue.
The DSP was originally developed as an XML encoding. Because XML
provides a certain amount of structure (this is my interpretation), the
statement templates are not assigned an identifier but are a list of
RDF-defined properties, each of which has its own identifier and related
constraints. However, in an RDF environment this would mean that each
property could be used only once in a DSP (or in the open world, only
once, period). I give an example, using the BIBFRAME profile that
follows the DSP, here [2]. Therefore, a change to the DSP is needed,
IMO, that would provide a statement identifier so that the same property
could be used in more than one description template.
In schematic terms, this means that rather than:
DSP:id
Description1:id
property1:id
property constraints
Description2:id
property1:id
property constraints
You need to have
DSP:id
Description1:id
Statement1:id
property1:id
constraints
Description2:id
Statement2:id
property1:id
constraints
And then the validation is done on the statements as a graph, not the
individual properties. (OK, I'm not sure that is exactly right, but it's
Saturday morning... if nothing else, we should all think about this.)
[1] http://dublincore.org/usage/reviews/2009/swap/ see section beginning
"discrepancy"
[2]
http://listserv.loc.gov/cgi-bin/wa?A2=ind1407&L=bibframe&T=0&X=1D8E3D2E6CEB438AB8&Y=lists%40kcoyle.net&P=359