Difference between revisions of "DC Application Profile"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
A Description Set Profile (DSP) basically consists of Templates and Constraints. Templates are to express structures and Constraints limit those structures. The following graphic from [http://www.dublincore.org/documents/2008/03/31/dc-dsp/ DCMI] shows the basic structure of a DSP: | A Description Set Profile (DSP) basically consists of Templates and Constraints. Templates are to express structures and Constraints limit those structures. The following graphic from [http://www.dublincore.org/documents/2008/03/31/dc-dsp/ DCMI] shows the basic structure of a DSP: | ||
[[Image:dsp-uml.png | | [[Image:dsp-uml.png|thumb|Structure of DSP from http://www.dublincore.org/documents/2008/03/31/dc-dsp/]] | ||
Revision as of 12:36, 7 November 2008
This page is to summarize the DC specifications and concepts of DC Metadata profiles and howto create them.
DC Description Set Profile[edit]
Resources, properties and values are given in a Description set which can be defined in a Description Set Profile (DSP). A Description Set Profile (DSP) basically consists of Templates and Constraints. Templates are to express structures and Constraints limit those structures. The following graphic from DCMI shows the basic structure of a DSP:
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127
Constraints[edit]
The right part of the graphic shows the different kinds of constraints that can occur in a DSP.
Constraints are used to define limitations on
- resources e.g. only resources of type foaf:person are allowed
- properties e.g. a person has a property called foaf:name
- two ways: giving an explicit list of allowed properties, requiring the property to be a sub-property of a given property
- values e.g. the value of a special property must be a Literal