[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: FW: [stdsreg] Standards Registry Metadata Definition, v1.5
After the call and things that were discussed, I have slightly modified the message that I tried to send yesterday. Below you will find the tentative mapping I have made for the Standards Registry Metadata Definition v1.5, with changes that were discussed yesterday. Makx. -------------------------------------------------------------------- SDO acronym DC.Creator or Publisher (needs best practice guidance) SDO's Committee/subcommittee/working group DC.Creator or Publisher (needs best practice guidance) Committee's URL DC.Creator or Publisher, or maybe DC.Relation? Committee Contact name DC.Contributor Document title DC.Title Document number DC.Identifier (could be the URI to the resource if available electronically, or a catalogue number otherwise) Scope/abstract/problem space DC.Description.Abstract Taxonomy/classification DC.Subject with SCHEME qualifier (Diffuse, ICS?) Keywords DC.Subject Current status (no draft | draft | final) DC.Type with private SCHEME qualifier Action date DC.Date (note that for various phases, qualifiers for Date could be used, e.g. DC.Date.Created, DC.Date.Accepted, DC.Date.Issued) Referenced standards DC.Relation.References Equivalent standards (?) DC.Relation with private element refinement qualifier, e.g. DC.Relation.Equivalent (please note that there is activity in the DC-Accessibility group that also looks at issues related to 'equivalent' resources, e.g. one resource in two version for different impairments - although it would be maybe bizarre to look at Windows and UNIX as different impairments :-) Superceded standards DC.Relation.Replaces Previous versions DC.Relation.Replaces or IsVersionOf Format DC.Format Rights DC.Rights Price (There is no element for this in DC and none is planned; is this information not too unstable to include in the metadata record?) Available from (There is no element for this in DC, although there are proposals to include it in some form in cases where the resource is only available in non-digital form, including books and museum artefacts) One additional element that may be required is DC.Language (the language of the resource - I think some standards bodies publish standards in more than one language). Would this also be a type of 'equivalent standard'? -------------------------------------------------------------------- Concerning the SDO contact table: SDO name SDO acronym SDO address SDO phone SDO fax SDO E-mail SDO URL SDO Contact These elements describe the committee - this is not a type of 'resource' that DC currently supports. There is a working group in DCMI (DC-Agents) that works on this. Hope this helps, Makx -------------------------------------------------------------------- Makx Dekkers e-mail: mail@makxdekkers.com tel: +352 2636 0150 fax: +352 2636 0151 GSM: +352 021 199910
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC