Namespaces
The DC-Government Application Profile uses terms from several namespaces:-
DCMI Metadata Terms
![[WWW]](/wiki/rightsidebar/img/moin-www.png)
http://dublincore.org/documents/dcmi-terms/
-
Endorsed Government metadata standards (UK, Australia, Denmark, Canada(Ontario), Finland)
-
The Usage Board has decided that any encoding scheme that has a URI defined in a non-DCMI namespace may be used. DCMI will not define these. Those so far considered for this application profile are indicated.
Format of entries:
This Application Profile is presented following the![[FTP]](/wiki/rightsidebar/img/moin-ftp.png){kind=small}
Dublin Core Application Profiles Guidelines produced by the CEN MMI-DC Workshop.
| Name of Term | A unique token assigned to the term. |
| Term URI | A Uniform Resource Identifier used to identify the term. |
| Label | A human-readable label assigned to the term. |
| Defined By | An identifier of a namespace, pointer to a schema, or bibliographic reference for a document within which the term is defined. |
| Source Definition | The definition of the term in the namespace in which the term was orginated. |
| DC-Gov Definition | The DC-Gov definition of the term. |
| Source Comments | Comments on the term from the namespace in which the term orginated. |
| DC-Gov Comments | DC-Gov comments about the term. |
| Type of term | The grammatical category of the term (e.g. "Element", "Element Refinement", or "Encoding Scheme"). |
| Refines | The described term semantically refines the referenced term. A refinement makes the meaning of the element narrower or more specific. It will share the meaning of the unrefined element but with a more restricted scope. |
| Refined By | The described term is semantically refined by the referenced term. |
| Encoding Scheme For | The described term, an encoding scheme, qualifies the referenced term. Using an encoding scheme will aid in the interpretation of an element value. These schemes include controlled vocabularies and formal notations or parsing rules. A value expressed using an encoding scheme will thus be a token selected from a controlled vocabulary (e.g., a term from a classification system or set of subject headings) or a string formatted in accordance with a formal notation (e.g., "2000-01-01" as the standard expression of a date). If an encoding scheme is not understood by a client or agent, the value may still be useful to a human reader.In some cases, encoding schemes not yet registered are indicated. These will be registered and/or approved by the DCMI Usage Board as DC Encoding Schemes in the future. |
| Has Encoding Scheme | The described term is qualified by the referenced encoding scheme. |
| Obligation | Indicates whether the element is required to always or sometimes be present. In this application profile the obligation can be: mandatory (M), mandatory if applicable (MA), strongly recommended (R) or optional (O). Mandatory ensures that some of the elements are always supported and mandatory if applicable means that this element must be supported if the information is available. An element with a mandatory obligation must have a value. The strongly recommended and the optional elements should be filled with a value if the information is appropriate to the given resource but if not, they may be omitted. |
| Occurence | Indicates any limit to the repeatability of the element. |
General notes regarding all elements
-
Either a Title or Identifier are mandatory (Identifier is mandatory if applicable).
-
If the record is expressed in a format (e.g., HTML) that allows each element/qualifier/scheme value to be assigned a language attribute (e.g., the HTML tag lang="en"), the use of the attribute is permitted for any or all DC elements as desired.
-
All elements may be used as unqualified. If using qualified Dublin Core, additional guidelines are given.
-
Any encoding scheme that has a URI defined in a non-DCMI namespace may be used: DCMI will not define these. A mechanism to register these is awaited. Where applicable a table has been created for each encoding scheme in a separate section following the main body of tables for elements and refinements.
DC-GAP Elements
| DC | CA | DK | NL | NZ | UK | FI | ||||
| Namespace | Element | DC-GOV Recom. | # uses conform DC-GOV | DCTERMS | GO-ITS | ? | OVERHEID | NZGLS | GOVTALK | JHS143 |
| DC | title | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | alternative | Rec | 3 | Y | Y | Y | ||||
| DC | creator | issue | 1 | D | D | Y | ||||
| DC | contributor | Rec | 3 | Y | Y | Y | ||||
| DC | publisher | Rec | 3 | Y | Y | Y | ||||
| DC | subject | issue | 2 | Y | N | Y | ||||
| DC | description | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | abstract | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | tableOfContents | Rec | 2 | Y | N | Y | ||||
| DC | date | issue | 2 | Y | N | Y | ||||
| DCTERMS | created | Rec | 2 | Y | N | Y | ||||
| DCTERMS | valid | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | available | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | issued | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | modified | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | dateCopyrighted | issue | 2 | Y | N | Y | ||||
| LOCGOV | dateCaptured | issue | 0 | N | N | N | ||||
| DC | type | Rec | 3 | Y | Y | Y | ||||
| DC | format | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | extent | Rec | 2 | Y | N | Y | ||||
| DCTERMS | medium | Rec | 2 | Y | N | Y | ||||
| DC | identifier | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | bibliographicCitation | Rec | 2 | Y | N | Y | ||||
| DC | source | Rec | 3 | Y | Y | Y | ||||
| DC | language | Rec | 3 | Y | Y | Y | ||||
| DC | relation | issue | 2 | Y | N | Y | ||||
| DCTERMS | isVersionOf | Rec | 2 | Y | N | Y | ||||
| DCTERMS | isFormatOf | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | hasFormat | Rec | 2 | Y | N | Y | ||||
| DCTERMS | isReplacedBy | Rec | 2 | Y | N | Y | ||||
| DCTERMS | replaces | Rec | 2 | Y | N | Y | ||||
| DCTERMS | isPartOf | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | hasPart | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | requires | Rec | 2 | Y | N | Y | ||||
| DCTERMS | isReferencedBy | Rec | 2 | Y | N | Y | ||||
| DCTERMS | references | Rec | 2 | Y | N | Y | ||||
| DC | coverage | Rec | 2 | Y | N | Y | ||||
| DCTERMS | spatial | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | temporal | Rec | 3 | Y | Y | Y | ||||
| DC | rights | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | audience | Rec | 3 | Y | Y | Y | ||||
| DCTERMS | educationLevel | Rec | 2 | Y | Y | Y |
Special DC Gov Elements
| DC | CA | DK | NL | NZ | UK | FI | ||||
| Namespace | Element | DC-GOV Recom. | # uses conform DC-GOV | DCTERMS | GO-ITS | ? | OVERHEID | NZGLS | GOVTALK | JHS143 |
| GO-ITS | version | issue | 1 | N | Y | N | N | |||
| GOVTALK | location | Prop | 1 | N | N | Y | ||||
| GO-ITS | mandate | Prop | 2 | N | Y | N | Y | |||
| GO-ITS | contact | issue | 1 | N | Y | N | N | |||
| NZGLS | function | Prop | 1 | N | N | Y | N | |||
| JHS143 | status | issue | 2 | N | N | Y | Y | |||
| JHS143 | audittrail | Prop | 1 | N | N | N | Y | |||
| OVERHEID | organsationType | Prop | 1 | N | Y | N | ||||
| OVERHEID | isRatifiedBy | Prop | 1 | N | Y | ? | ||||
| OVERHEID | accessibility | Prop | 1 | N | Y | ? | ||||
| OVERHEID | category | Prop | 1 | N | Y | N | ||||
| OVERHEID | nextVersionDue | Prop | 1 | N | Y | ? | ||||
| OVERHEID | updatingFrequency | Prop | 1 | N | Y | ? | ||||
| GOVTALK | addressee | Prop | 1 | N | N | Y |
Recommendation
| Prop | Proposed - Candidate element, once suggested, possibly adapted by DC-Government |
| Rec | Recommended by DC-government |
| issue | issue - There is an issue on this element which needs discussion to decide on recommendation or deprication |
| Depr | Depricated - Element is not compliant with DC |
Usage
| Y | Yes |
| N | No |
| D | Different from DC-Government AP |