DCMI: DCMI Government Community

DCMI-Government Working Group

DC-GOV APPLICATION PROFILE

Available for comments until 20 February 2002. If you are a member of the DC-Government Mailing List, please send comments directly to the mailing list. If you are not a member of the mailing list and do not wish to join, please send comments directly to the working group chairs.

Title:	DC-GOV APPLICATION PROFILE
Creator:	Maewyn Cumming
Creator:	Andrew Wilson
Creator:	Palle Aagaard
Date Issued:	2001-02-12
Identifier:	http://dublincore.org/groups/government/profile-200202/
Replaces:	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 after agreement in DC Government WG.
Description of document:	This final draft proposes new qualifiers to the Dublin Core™ recommendation for making the Dublin Core™ Government Application profile. This draft proposal also suggests some encoding schemes connected to certain elements. This draft proposal assumes that the element "Audience" is functioning as the 16th Dublin Core™ element.

Element Qualifier Proposal: Date Acquired

Qualified element Namespace	http://purl.org/dc/terms
Qualified element Name	date
Element Qualifier Namespace	http://purl.org/dc/terms
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 import for resource discovery as well as ERM
Element Qualifier Encoding Schemes	ISO 8601
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 Security Classification

Qualified element Namespace	http://purl.org/dc/terms
Qualified element Name	rights
Element Qualifier Namespace	http://purl.org/dc/terms
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/terms
Qualified element Name	rights
Element Qualifier Namespace	http://purl.org/dc/terms
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	For describing which user-groups have access to the resource, e.g. public, e.g. internal, e.g. department.
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.

Element Qualifier Proposal: Subject Classification

Qualified element Namespace	http://purl.org/dc/terms
Qualified element Name	subject
Element Qualifier Namespace	http://purl.org/dc/terms
Element Qualifier Name	classification
Element Qualifier Label	Classification
Element Qualifier Status	Domain-specific: Dublin Core™ Government Application Profile
Element Qualifier Definition	Term or code from a controlled vocabulary or scheme designed to aid browsing and search by subject matter
Element Qualifier Comment	Typically taken from a high-level subject scheme or encoded classification system. Differs from Subject Keyword in that it requires a broad heading not a specific subject descriptor. It should be possible to use Keyword and Classification in conjunction. Data in this refinement can also be used as the basis of a 'push' system, to classify documents for current awareness services.
Element Qualifier Encoding Schemes	Local (e.g. national or agency) encoding schemes -e.g. category lists or classification schemes - can be used. No DCMI value qualifier is proposed for eGovernment.
Element Qualifier Examples	A user wants to perform a 'broader search'. This user is not familiar with proper names of classification schemes. It is possible to make a specific search input field - based on Subject Classification - at search engines, which then facilitates 'broader search'. This means the mentioned user can use such a field for 'broader search' without knowing anything about the names and nature of the schemes. Classification can be used to create dynamic browsing menus, of the type popularised by Yahoo. Electronic systems can identify the correct resources for each subject heading by locating it in this space. Combining a search on Classification values and other subject terms (metadata or free text) can give much more accurate search results.

Element Qualifier Proposal: Subject Keyword

Qualified element Namespace	http://purl.org/dc/terms
Qualified element Name	subject
Element Qualifier Namespace	http://purl.org/dc/terms
Element Qualifier Name	keyword
Element Qualifier Label	Keyword
Element Qualifier Status	Domain-specific: Dublin Core™ Government Application Profile
Element Qualifier Definition	Terms describing the specific subjects of the resource
Element Qualifier Comment	Will be used, in conjunction with subject classification. Will be terms or phrases. Can be used for coordinated indexing of resources.
Element Qualifier Encoding Schemes	Local (e.g. national or agency) encoding schemes -e.g. thesauri or controlled vocabularies - can be used. Uncontrolled terms can also be used. No DCMI value qualifier is proposed for eGovernment.
Element Qualifier Examples	A user wants to perform a narrow or 'specific search'. It is possible to make a specific search input field - based on Subject Keyword - at search engines, which then facilitates 'narrow search'. This mean the mentioned user can use such a field for 'narrow search' without knowing anything about the names and nature of the schemes.

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 lining 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 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.
Examples Scheme Example	A citizen want 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 situation For those who are going to have a child For those who shall use kindergarten For those who will know about schools For those who will take an education For those who are moving from home For those who need work-related information For those who need information about marriage and related For those who need information about elderly people and related For those who need information connected to death in the family and related Business situation For those who starts 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/terms
Element Name	type
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.
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.