dcr guidelines
Handbook: Table of Contents
- ► Governing Board committees: Membership & Finance ◘ Nominations & Bylaws
- ► Technical Board committees: Usage ◘ Standards & Liaisons ◘ Community Specifications ◘ Infrastructure Advisory Committee (IAC)
- ► Advisory Board committees: Conferences & Meetings ◘ Education & Outreach
- ► Management: Executive ◘ Directorate
Contents |
Forms of DCMI Community Specifications
-
- Community Specifications may take a number of forms including documents that define a required (conforming) practice, a recommended practice or a guide to best practices.
DCMI Community Specifications: Core Requirements
In order to be published with the status of a DCMI Community Specification:
- a specification must have a home in an active[1] DCMI Community or Task Group open to interested members of the public (example (now closed): DCMI Collection Description Community);
- NOTE: a specification that has a home in a body other than a DCMI Community or Task Group (e.g., W3C) may be proposed and subsequently designated a "Recommended Resource" (for example, W3C "Dublin Core to PROV Mapping" [2])
- the specification must be vetted and approved in open discussion using a JISCMAIL list (example: DC-COLLECTIONS mailing list;
- the drafts of a future DCMI Community Specification must be posted for discussion on wiki.dublincore.org (or dublincore.org);
- the end result must be published on dublincore.org (Example: Collections Application Profile);
- any vocabulary published as a DCMI Community Specification must be published as a human-readable document and a machine-readable serialization (eg, RDF, OWL) on dublincore.org (example: Collection Description Type Vocabulary);
- the URIs used in any RDF vocabulary published as a DCMI Community Specification must be PURLs. Starting in July 2014, the PURL namespace for a Community Specification will be http://purl.org/dc/community/{prefix}. The RDF schema must be published on the DCMI website (example: Collection Description Type Vocabulary) and the PURLs must be configured with DCMI as maintainer (example: http://purl.org/cld/cdtype/).
- the document must clearly and consistently be named and referenced as a DCMI Community Specification.
Committee Support for Task Groups
The Community Specifications Committee will endeavor to help Task Groups with:
- Formatting a Web document in DCMI style and pushing it to dublincore.org;
- Creating an RDF schema;
- Creating PURLs and redirecting them correctly to the schema;
- Expeditiously shepherding a candidate Community Specification through the vetting and publication process.
Committee Vetting of Candidate Community Specifications
@@@