ISO/IEC JTC 1/SC 34N0758
ISO/IEC JTC 1/SC 34
Information Technology --
Document Description and Processing Languages
| TITLE: | NP for Technical Report - Information Technology - Topic Maps - Expressing Dublin Core Metadata using Topic Maps |
| SOURCE: | Mr. Steve Pepper |
| PROJECT: | NP Dublin Core in Topic Maps: Information Technology - Topic Maps - Expressing Dublin Core Metadata using Topic Maps |
| PROJECT EDITOR: | Mr. Steve Pepper |
| STATUS: | New Work Item Proposal (NP) |
| ACTION: | For SC34 ballot and JTC1 for information and circulation |
| DATE: | 2006-05-31 |
| DISTRIBUTION: | National bodies |
| REFER TO: | N0758b - 2006-05-31 - Ballot due 2006-08-31: NP for Technical Report - Information Technology - Topic Maps - Expressing Dublin
Core Metadata using Topic Maps N0759 - 2006-08-31 - Supporting materials: NP for Technical Report - Information Technology - Topic Maps - Expressing Dublin Core Metadata using Topic Maps |
| REPLY TO: |
Dr. James David Mason (ISO/IEC JTC 1/SC 34 Secretariat - Standards Council of Canada) Crane Softwrights Ltd. Box 266, Kars, ON K0A-2E0 CANADA Telephone: +1 613 489-0999 Facsimile: +1 613 489-0995 Network: [email protected] http://www.jtc1sc34.org |
PROPOSAL FOR A NEW WORK ITEM
|
Date of presentation of proposal:
|
Proposer: |
|
Secretariat: |
ISO/IEC JTC 1/SC 34 N 0758 |
A proposal for a new work item shall be submitted to the secretariat of the ISO/IEC joint technical committee concerned with a copy to the ISO Central Secretariat.
Presentation of the proposal - to be completed by the proposer Guidelines for proposing and justifying a new work item are given in ISO Guide 26.
|
Title |
|
Scope This proposed standard specifies a method for expressing Dublin Core metadata using Topic Maps. |
|
Purpose and justification The Dublin Core Metadata Initiative (DCMI) has produced one of the most successful vocabularies for expressing document metadata and is in widespread use on the World Wide Web, as well as among libraries, and in many other areas. ISO 13250 Topic Maps is a standard for representing metadata and thus a candidate to be used as the representation format for Dublin Core metadata. Furthermore, topic maps conforming to ISO 13250 can be regarded as document that themselves often require to be described using metadata. The most natural way of doing this would be to use Topic Maps to express such metadata. As of today, there is no generally accepted and standard method in which to express Dublin Core metadata using Topic Maps. The purpose of this Technical Report is to specify a standard method for doing so. Having such a standard method would lead to the interoperability among topic maps and increased awareness of the utility of ISO 13250. |
|
Programme of work If the proposed new work item is approved , which of the following
document(s) is (are) expected to be developed? |
|
Relevant documents to be considered None |
|
Cooperation and liaison World Wide Web Consortium Dublin Core Metadata Initiative |
|
Preparatory work offered with target date(s) Preparatory work: dc.xtmm and dc.ltmm (XTM and LTM templates for Dublin Core metadata) found in JTC 1/SC34 N 0759 compressed ZIP file Target date (TR): 2007-12 |
|
Signature: |
|
Will the service of a maintenance agency or registration authority be
required? No Are there any known requirements for coding? No Are there any known requirements for cultural and linguistic
adaptability? No Does the proposed standard concern known patented items? No |
Comments and recommendations of the JTC 1 Secretariat
- attach a separate page as an annex, if necessary|
Comments with respect to the proposal in general, and
recommendations thereon: |
Voting on the proposal
- Each P-member of the ISO/IEC joint technical committee has an obligation to vote within the time limits laid down (normally three months after the date of circulation).|
Date of circulation: |
Closing date for voting: |
Signature of Secretary: G. Ken Holman |
|
NEW WORK ITEM PROPOSAL - PROJECT ACCEPTANCE CRITERIA |
||
|
Criterion |
Validity |
Explanation |
|
A Business Requirement |
||
|
A.1 Market Requirement |
Essential _X_ |
Users of ISO/IEC 13250 require a standardized method for expressing Dublin Core metadata using Topic Maps. |
|
A.2 Regulatory Context |
Essential ___ |
|
|
B. Related Work |
||
|
B.1 Completion/Maintence of current standards |
Yes ___ |
|
|
B.2 Commitment to other organization |
Yes ___ |
|
|
B.3 Other Source of standards |
Yes ___ |
|
|
C. Technical Status |
||
|
C.1 Mature Technology |
Yes _X_ |
Many topic maps have been published by many organizations and a number of attempts have been made to express Dublin Core metadata, so considerable experience has been gained. |
|
C.2 Prospective Technology |
Yes ___ |
|
|
C.3 Models/Tools |
Yes ___ |
|
|
D. Conformity Assessment and Interoperability |
||
|
D.1 Conformity Assessment |
Yes ___ |
|
|
D.2 Interoperability |
Yes _X_ |
The method for expressing Dublin Core using Topic Maps should be interoperable with the equivalent method for expressing Dublin Core using RDF currently under development. Interoperability will be achieved by establishing a liaison between SC34 and the W3C. |
|
E. Cultural and Linguistic Adaptability |
Yes _X_ |
It is a requirement that this standard will support multiple languages and the Unicode character encoding. The Dublin Core metadata sets are defined as abstract metadata elements that can be given different names in different natural languages. The Topic Maps model also supports multiple languages and the Unicode character set. |
|
F. Other Justification |
Notes to Proforma
A. Business Relevance. That which identifies market place relevance in terms of what problem is being solved and or need being addressed.
A.1. Market Requirement. When submitting a NP, the proposer shall identify the nature of the Market Requirement, assessing the extent to which it is essential, desirable or merely supportive of some other project.
A.2 Technical Regulation. If a Regulatory requirement is deemed to exist - e.g. for an area of public concern e.g. Information Security, Data protection, potentially leading to regulatory/public interest action based on the use of this voluntary international standard - the proposer shall identify this here.
B. Related Work. Aspects of the relationship of this NP to other areas of standardization work shall be identified in this section.
B.1 Competition/Maintenance. If this NP is concerned with completing or maintaining existing standards, those concerned shall be identified here.
B.2 External Commitment. Groups, bodies, or fora external to JTC1 to which a commitment has been made by JTC for cooperation and or collaboration on this NP shall be identified here.
B.3 External Std/Specification. If other activities creating standards or specifications in this topic area are known to exist or be planned, and which might be available to JTC1 as PAS, they shall be identified here.
C. Technical Status. The proposer shall indicate here an assessment of the extent to which the proposed standard is supported by current technology.
C.1 Mature Technology. Indicate here the extent to which the technology is reasonably stable and ripe for standardization.
C.2 Prospective Technology. If the NP is anticipatory in nature based on expected or forecasted need, this shall be indicated here.
C.3 Models/Tools. If the NP relates to the creation of supportive reference models or tools, this shall be indicated here.
D. Conformity Assessment and Interoperability
D.1 Indicate here if Conformity Assessment is relevant to your project. If so, indicate how it is addressed in your project plan.
D.2 Indicate here if Interoperability is relevant to your project. If so, indicate how it is addressed in your project plan.
E. Cultural and Linguistic Adaptability Indicate here if cultural and linguistic adaptability is applicable to your project. If so, indicate how it is addressed in your project plan.
F. Other Justification Any other aspects of background information justifying this NP shall be indicated here.