Description Set Profiles

Transcription

1 Description Set Profiles Mikael Nilsson DC 2007, Singapore Aug 27-31, 2007 The Knowledge Management Research Group 1

2 DC Application Profiles - traditional definition A Dublin Core Application Profile (DCAP) is a declaration specifying which metadata terms an organization, information provider, or user community uses in its metadata. By definition, a DCAP identifies the source of metadata terms used whether they have been defined in formally maintained standards such as Dublin Core, in less formally defined element sets and vocabularies, or by the creator of the DCAP itself for local use in an application. Optionally, a DCAP may provide additional documentation on how the terms are constrained, encoded or interpreted for application-specific purposes. --CEN CWA 14855:2003 The Knowledge Management Research Group 2

3 Machine-readable constraints? XML Schema? Not applicable to RDF Not applicable to HTML Not applicable to... CEN Guidelines Not based on DCAM No support for Description Sets Needed something new Dublin Core Description Set Profile The Knowledge Management Research Group 3

4 Envisioned usages as a formal representation of the constraints of a Dublin Core Application Profile as configuration for databases as configuration for metadata editing tools etc. The Knowledge Management Research Group 4

5 Scope of a DSP spec Information model: Structural constraints on a description set: what descriptions may occur what properties may be used what ways might a value surrogate be given XML expression The Knowledge Management Research Group 5

6 Out of scope Human-readable documentation Definition of vocabularies Version control etc. The Knowledge Management Research Group 6

7 DC Application Profiles - new definition (in progress) A DCAM-conformant Application Profile ( DC Application Profile ) is packet of documentation which consists of: Functional requirements (mandatory) Domain model (mandatory) Description Set Profile (DSP) (mandatory) Usage guidelines (optional) Encoding syntax guidelines (optional) The Knowledge Management Research Group 7

8 The Knowledge Management Research Group 8

9 Application Profile Domain standards Foundation standards The Knowledge Management Research Group 9

10 First working draft Comments on DC-ARCHITECTURE Publication schedule not defined The Knowledge Management Research Group 10

11 Example: The book AP A book: a literal title a creator, described separately A creator a literal name The Knowledge Management Research Group 11

12 Statement template: literal title Description Template: Book Property: dcterms:title Literal value Language SES Statement template: creator Property: dcterms:creator Description reference: Creator Value URI Vocabulary Encoding Scheme Value string Language SES Statement template: literal name Description Template: Creator Property: foaf:name standalone:no Literal value Language SES The Knowledge Management Research Group 12

13 {{{#!DSP == Description template: Book == DT=(min="1" max="1" standalone="yes" identifier="book") Link === Title === ST=(max="1" type="literal" PC={ Definition A name given to the resource. LC=(LangC=(occurrence="optional") SESConstraint=(occurrence="disallowed") ) === Creator === ST=(max="1" type="nonliteral" PC={ Definition An entity primarily responsible for making the resource. NLC=(VURIConstraint=(occurrence="disallowed") VESConstraint=(occurrence="disallowed") VStringConstraint=(max="1" LangC=(occurrence="disallowed") SESConstraint=(occurrence="disallowed")) description="creator" ) == Description template: Creator == DT=(min="1" max="1" standalone="no" identifier="creator") === Name === ST=(max="1" type="literal" PC={ Definition A name for some thing. LC=(LangC=(occurrence="disallowed") SESConstraint=(occurrence="disallowed") ) }}} The Knowledge Management Research Group 13

14 The Knowledge Management Research Group 14

15 <?xml version="1.0"?> <DescriptionSetTemplate> <DescriptionTemplate maxoccur="1" minoccur="1"> <StatementTemplate maxoccur="1" type="literal"> <Property> <LiteralConstraint> <SyntaxEncodingSchemeOccurrence>disallowed</SyntaxEncodingSchemeOccurrence> <LanguageOccurrence>optional</LanguageOccurrence> </LiteralConstraint> </StatementTemplate> <StatementTemplate maxoccur="1" type="nonliteral"> <Property> <NonliteralConstraint descriptiontemplateid="creator"> <ValueURIOccurrence>disallowed</ValueURIOccurrence> <VocabularyEncodingSchemeOccurrence>disallowed</VocabularyEncodingSchemeOccurrence> <ValueStringConstraint maxoccur="1"> <SyntaxEncodingSchemeOccurrence>disallowed</SyntaxEncodingSchemeOccurrence> <LanguageOccurrence>disallowed</LanguageOccurrence> </ValueStringConstraint> </NonliteralConstraint> </StatementTemplate> </DescriptionTemplate> <DescriptionTemplate maxoccur="1" minoccur="1"> <StatementTemplate maxoccur="1" type="literal"> <Property> <LiteralConstraint> <SyntaxEncodingSchemeOccurrence>disallowed</SyntaxEncodingSchemeOccurrence> <LanguageOccurrence>disallowed</LanguageOccurrence> </LiteralConstraint> </StatementTemplate> </DescriptionTemplate> </DescriptionSetTemplate> The Knowledge Management Research Group 15

16 Putting DSPs to work The SHAME demo Takes DSP-XML Generates an RDF editor on the fly RDF conforms to DSP constraints The Knowledge Management Research Group 16