Difference between revisions of "DC Application Profile"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
==DC Description Set Profile== | ==DC Description Set Profile== | ||
A Description Set Profile (DSP) basically consists of Templates and Constraints. Templates are to express structures and Constraints limit those structures. | 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 [http://www.dublincore.org/documents/2008/03/31/dc-dsp/ | DCMI] shows the basic structure of a DSP: | |||
[[Image:dsp-uml.png]] | |||
===Constraints=== | ===Constraints=== | ||
Revision as of 12:24, 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:
Constraints[edit]
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