DCMI: DCMI Government Community

DCMI-Government Working Group

Title:	DC-GOV non DCMI terms
Creator:	Maewyn Cumming
Creator:	Andrew Wilson
Creator:	Palle Aagaard
Date Issued:	2001-03-14
Identifier:	http://dublincore.org/groups/government/DCMI-gov-proposal-2002-04-18.html
Replaces:	none
Is Replaced By:	Not Applicable
Latest version:	http://dublincore.org/groups/government/profile-200111/
Status of document:	This is a Dublin Core™ Metadata Initiative Government Working Group final draft proposal for submitting to the DCMI Usage Board
Description of document:	Dublin Core™ is already being used by practically all governments that are attempting to improve access to their information. However, though seen as the ideal starting point, it is not sufficient for our varied and specialised needs. This final draft: proposes new terms, some of which will be included in the Dublin Core™ Government Application Profile. suggests some encoding schemes connected to certain elements. assumes that the element "Audience" is functioning as the 16th Dublin Core™ element. The future "DC-DOV Application Profile" is intended to be used by governments who will set up their own national metadata Application Profile using Dublin Core™.

Element Qualifier Proposal: Date Acquired

Qualified element Namespace	http://purl.org/dc/elements/1.1/
Qualified element Name	date
Element Qualifier Name	acquired
Element Qualifier Label	Acquired
Element Qualifier Status Domain-specific:	Dublin Core™ Government Application Profile
Element Qualifier Definition	Date on which the resource was received into the organisation
Element Qualifier Comment	This qualifier is important for resource discovery as well as ERM
Element Qualifier Encoding Schemes	W3CDTF
Element Qualifier Examples	In a resource discovery process (Search & Retrieval) for resources in a specific agency, users (e.g. journalist) can have a need for knowing exactly when the agency was aware of the content of a specific resource.The status of a resource can change when it is submitted by one authority to another (e.g. in legislative procedures) without necessarily any change being made to the content of that resource.

Element Qualifier Proposal: Rights SecurityClassification

Qualified element Namespace	http://purl.org/dc/elements/1.1/
Qualified element Name	rights
Element Qualifier Name	securityClassification
Element Qualifier Label	Security Classification
Element Qualifier Status Domain-specific:	Dublin Core™ Government Application Profile
Element Qualifier Definition	The classification allocated to the resource indicating its official security status
Element Qualifier Comment	This classification is part of the description of the resource. In a resource discovery context it is vital information for the user about the possibility for access to the resource.
Element Qualifier Encoding Schemes	Local (e.g. national or agency) encoding schemes can be used. Free text can be used. No DCMI value qualifier is proposed.
Element Qualifier Examples	Will be needed e.g. on intranets where resources with a variety of classifications will be stored but also on metadata databases designed to indicate that an information resource exists even if it is not actually available to the public. This can be needed to meet access to information legislation requirements. A citizen-user finds by search a reference to a classified resource. The classification status tells the user why access is not possible. A non-citizen-user, e.g. employed in an agency, finds by search a reference to a security classified resource. This user can have a need to see how the resource is security classified.

Element Qualifier Proposal: Rights Access Rights

Qualified element Namespace	http://purl.org/dc/elements/1.1/
Qualified element Name	rights
Element Qualifier Name	accessRights
Element Qualifier Label	Access Rights
Element Qualifier Status Domain-specific:	Dublin Core™ Government Application Profile
Element Qualifier Definition	Defining which user-groups can access the resource
Element Qualifier Comment	Element Qualifier Comment For describing which user-groups have access to the resource, e.g. public, e.g. internal, e.g. department. Can contain information on the resource's status regarding access for users under any information access or privacy laws or regulation. Note that this differs from the official security marking given in the 'security classification' refinement. But 'Access Rights' can be related to 'Security Classification'.
Element Qualifier Encoding Schemes	Local (e.g. national or agency) encoding schemes can be used. Free text can be used. No DCMI value qualifier is proposed.
Element Qualifier Examples	A user finds by search a reference to a resource. If the user can not access the resource, the user can see who can. A user, particularly in a government information situation, may be looking specifically for items only available to a particular user group, or denied to a user group.

Scheme Proposal for: Element Audience

Element Namespace	http://purl.org/dc/terms
Element Name	Audience
Element Label	Audience
Scheme Name	Life-cycle
Scheme Definition	A category of user for whom the resource is intended
Scheme Status	Domain-specific: Dublin Core™ Government Application Profile
Scheme Comment	Creators and publishers of government resources can explicitly state the category of user for whom the resource is intended. Can also be used for automatic linking into a menu at a public information web-site. These web-sites can be arranged according to a 'life-situation' ("what to do when I have a child?", "what to do when I will get married?" etc.). The 'life-situation' or 'life-cycle' perspective is often used in connection with public information.
Values of Encoding Scheme	Local (e.g. national or agency) encoding schemes for the 'Life-cycle' can be used. Only a DCMI Scheme name is proposed for eGovernment at the moment.
ExamplesScheme Example	A citizen wants to find public information about rules for schools. A citizen's parent is dead. What to do then? Business has to be closed. What to do then? Web-related public information is by some government agencies arranged according to a 'life-cycle' approach. Below is examples of some life-situations for citizens and for business. These life-situations are arranged in a scheme called 'Life-cycle': Citizen situations For those who are going to have a child For those who shall use kindergarten For those who need to know about schools For those entering education For those who are leaving home For those who need work-related information For those who need information about marriag For those who need information about elderly people For those who need information connected to death in the family Business situation For those starting a business· For those who need information about relations with government For those who are closing down

DCMI Type Vocabulary

Scheme Proposal for: Element Type

Element Namespace	http://purl.org/dc/elements/1.1/
Element Name	Element Name Type
Element Label	Element Label Type
Scheme Name	Aggregation-level
Scheme Definition	The resource's level or position in a hierarchy. Shows the extent to which the resource is part of a larger resource or collection
Scheme Status	Domain-specific: Dublin Core™ Government Application Profile
Scheme Comment	Used for describing the resources. If it is e.g. a single document or e.g. the access to a complete library. The definition of the value 'collection' is similar to same value in the original "DCMI Type Vocabulary". DC Gov. WG have contacted the "Type vocabulary group" for a briefing on types, but have not got an answer yet.
Values of Encoding Scheme	Document (a single document, e.g. a letter) Folder (a 'case'-file) Volume (a subdivision of a file or folder - MoReq definition) Bibliographic item· Collection (e.g. an archive, a library)
Examples	When the user by search finds references to resources, the user will get information about if it is e.g. the reference to a single page (e.g. web-page) or the homepage of a complete library