Pete Johnston wrote:
>
> So, just so that everyone is on the same page, we're referring to the
> document
>
> http://dublincore.org/documents/2008/03/31/dc-dsp/
Thanks, Pete.
>
> If you want to limit the statements within a description to a maximum of
> one statement referencing one of three named properties, then I _think_
> this could be achieved using a single statement template specifying
>
> - a maximum occurrence constraint (6.2 in the DSP doc) of "1"; and
> - a property list constraint (6.4.1 in the DSP doc) listing the three
> properties
Great, I was hoping this kind of technique could work. It now occurs to
me that maybe I could create a few sample "patterns" that would help
people who are thinking about APs -- this could be one of them.
>
> The title and subtitle properties are both properties of the same
> resource. In the DCAM/RDF models, there is no notion of "elements" being
> contained in a "wrapper element".
>
> I don't think the DSP constraint model (as currently proposed - it is
> still a draft) allows for the specification of the sort of constraint
> where the presence of a statement referencing property B is dependent on
> the presence within the same description of a statement referencing
> property A.
>
> As Diane suggests, such a limitation could still be specified in a
> human-readable guideline which implementers then use as the basis for
> checking such a constraint in their tools.
But could we have something like:?
description: titlePlusSubtitle
statement: title (min=1, max=1)
statement: subtitle (min=0, max=1)
It seems that this would work for a very simple case, but I can imagine
more complex cases that wouldn't work so well. This is also a problem in
XML schema, as I recall. Perhaps it would be enough to know that a
metadata set uses both title and subtitle *when appropriate*. (I happen
to be painfully aware of this one because it often ends up making a
difference when trying to identify the same bibliographic entity under
different metadata conventions.)
OK, so here's another question:
Let's say my AP has a date value, I'll call it "dateOfPublication", and
it can be either a plain string or it can be typed, using one or more
standard types. Do I therefore have multiple dateOfPublication
statements? e.g.
description: dateOfPublication
statement: dateOfPublicationString
statement: dateOfPublicationTyped [with URIs for relevant types? or
is each one a separate statement?]
Oh, now I remember, we had this discussion a while back related to
something Jon posted. I don't remember a resolution...
--
-----------------------------------
Karen Coyle / Digital Library Consultant
[log in to unmask] http://www.kcoyle.net
ph.: 510-540-7596 skype: kcoylenet
fx.: 510-848-3913
mo.: 510-435-8234
------------------------------------
|