A more detailed view for the benefit of technical editors...
Here is another, slightly simplified, way to view the _current_ DCAM
Description Set Model (using Python-esque indentation):
Group: Description Set
Group: Description
Slot: Described Resource URI
Group: Statement
Slot: Property URI
Group: Literal Value Surrogate, a type of Value Surrogate
Slot: Value String
Slot: Syntax Encoding Scheme URI
Slot: LanguageTag
Group: Non-Literal Value Surrogate, a type of Value Surrogate
Slot: Value URI
Slot: Value Encoding Scheme URI
Slot: Value String
Slot: Syntax Encoding Scheme URI
Slot: LanguageTag
The above view already simplifies away the soon-to-be-obsoleted underlying
distinction between plain and typed RDF literals [2].
What I propose to replace this with is:
Group: DescriptionSet
Group: Description
Slot: DescribedResourceURI / DescribedResourceID
Group: LiteralValuePattern
Slot: PropertyURI
Slot: LiteralValue
Slot: LanguageTag
Slot: SyntaxEncodingSchemeURI
Group: NonLiteralValuePattern
Slot: PropertyURI
Slot: ValueURI / ValueID
Slot: SKOSConceptSchemeURI
Slot: ValueLabel
Slot: LanguageTag
Slot: SyntaxEncodingSchemeURI
Picture the visual diagram with:
-- nested enclosing boxes for the Groups
-- little boxes for Slots nested inside the Groups. These are the boxes
("fields") that get filled in with data values.
Tom
[1] http://dublincore.org/documents/abstract-model/
[2] http://www.w3.org/2011/rdf-wg/track/issues/80
> My proposal is that the entities of the DCMI Abstract Model (plus
> DC-TEXT) be limited to the following entities:
>
> -- Grouping constructs
> DescriptionSet
> Description
> LiteralValuePattern
> NonLiteralValuePattern
>
> -- Syntactic slots
> DescribedResourceURI / DescribedResourceID
> PropertyURI
> ValueURI / ValueID
> LiteralValue
> ValueLabel
> LanguageTag
> SyntaxEncodingSchemeURI
> SKOSConceptSchemeURI
--
Tom Baker <[log in to unmask]>
|