> DCTermsChangesActions

• FrontPage
• RecentChanges
• FindPage
• HelpContents

• Edit
• View
• Diffs
• Info
• Subscribe
• Raw
• Print

• AttachFile
• DSP2XML
• DeletePage
• LikePages
• LocalSiteMap
• SpellCheck

Changes to DCTERMS definitions and comments - FROZEN COPY

This file: http://dublincore.org/usageboardwiki/DCTermsChangesActions - edit DCTermsChangesActionsDone

NOTE: This file summarizes decisions taken in Barcelona regarding the proposal http://dublincore.org/usageboardwiki/DCTermsChanges

Barcelona proposal: http://dublincore.org/usage/meetings/2007/03/barcelona/DCTermsChanges.pdf

• Audience = ok

• Alternative=(has a typo)=ok

• TableofContents=ok

• Abstract=ok

• Created=ok

• Valid=ok

• Available=ok

• Issued=ok

• Modified=ok

• Extent=(need to correct comment)=ok

• Medium=no changes

• IsVersionOf=ok

• HasVersion=ok with first revised definition, with adding "A related resource that is" at the beginning

• IsReplacedBy=ok, change which to that (and be consistent with DCTERMS - ACTION: do a which hunt Tom))

• Replaces=ok

• IsRequiredBy=no (change to make parallel with Requires) "A related resource that requires the described resource to support its function, delivery, or coherence"

• Requires= change to "A related resource that is required by the described resource to support its function, delivery, or coherence" - drop 'content'

• IsPartOf=change to "A related resource in which the described resource is physically or logically included."

• HasPart= change to "A related resource that is included either physically or logically in the described resource."

• IsReferencedBy= change to "A related resource that references, cites, or otherwise points to the described resource."

• References=change to "A related resource that is referenced, cited, or otherwise pointed to by the described resource."

• IsFormatOf= change to "A related resource that is substantially the same as the described resource, but in another format"

• HasFormat=change to "A related resource that is substantially the same as the pre-existing described resource, but in another format."

• conformsTo: AGREED: approved

• spatial: AGREED: approved

• temporal: AGREED: approved

• mediator: AGREED: definition approved, comment should be a list in this case:

• In an educational context, a mediator might be a parent, teacher, teaching assistant, or care-giver

• dateAccepted: AGREED: approved

• ACTION 2007-03-17: delete "freestanding property label" (Tom)

• dateCopyrighted: AGREED: change defintion to "Date of copyright."

• ACTION 2007-03-17: delete "freestanding property label" (Tom)

• dateSubmitted: AGREED: approved

• ACTION 2007-03-17: delete "freestanding property label" (Tom)

• educationLevel:

• AGREED: change the definition. remove "audience" in the definition, and replace it with "a class of entity" and remove "its", so it reads: "A class of entity, defined in terms of progression through an educational or training context, for whom the resource is intended."

• JUSTIFICATION: parallel construction

• accessRights:

• AGREED: change comment to: "Access Rights may include information regarding access or restrictions based on privacy, security or other policies."

• this substitutes policies for regulations

• bibliographicCitation: AGREED: approved

• license: AGREED: remove comment

• JUSTIFICATION: we don't say anything about value URI in any other comment AND it's an application profile issue as to whether or not a value has a URI, therefore we don't need the Creative Commons example

• rightsHolder: AGREED: remove comment

• provenance: AGREED: approved

• instructionalMethod: AGREED: approved

• accrualMethod: AGREED: approved

• accrualPeriodicity: AGREED: approved

• accrualPolicy: AGREED: approved

• LCSH: AGREED: change definition: "The set of concepts defined by the Library of Congress Subject Headings"

• MESH, LCC, DDC, UDC AGREED: change definition to start: "The set of concepts..."

• DCMIType

• AGREED: change to "A set of concepts used to categorize the nature or genre of the resource."

• ACTION 2007-03-17: Tom to add a change note that there was systematic change "content of the resource"

• IMT:

• AGREED: change definition to "Set of concepts defined by IANA used to indicate the media type of the resource"

• ISO639-2:

• AGREED: change to "The set of three-letter codes listed in ISO639-2 for the representation of names of languages"

• ISSUE: we recognize a set of concepts for language, however, interpreting the ISO639-2 as a set of concepts would break the namespace policy because ISO639-2 is a set of strings (defined by ISO and us).

• ACTION 2007-03-17: Joe will draft a document discussing issues related to principles and purpose of UB decision-making (context: decision to define ISO639-2 as a set of codes - see http://dublincore.org/usageboardwiki/DCTermsChangesActions).

• RFC1766:

• AGREED: change to "The set of tags, constructed according to RFC 1766, for the identification of languages"

• URI:

• AGREED: change to "The set of identifiers constructed according to the generic syntax for Uniform Resource Identifiers, as defined by the IETF"

• ISSUE: because of the way RFCs work, they change and take on a different number

• Point: AGREED: change to "the set of points in space defined by their geographic coordinates according to the DCMI Point Encoding Scheme"

• ISO3166: AGREED: change to "The set of codes listed in ISO 3166-1 for the representation of names of countries"

• Box: AGREED: change to "the set of regions in space defined by their geographic coordinates according to the DCMI Box Encoding Scheme"

• TGN: AGREED: change to "the set of places defined by the Getty Thesaurus of Geographic Names"

• Period: AGREED: change to "the set of time intervals defined by their limits according to the DCMI Period Encoding Scheme"

• W3CDTF: AGREED: change to "set of dates and times constructed according to the W3C Date and Time Formats Specification"

• RFC3066:

• AGREED: change to "The set of tags, constructed according to RFC 3066, for the identification of languages"

• AGREED: add comment "RFC 3066 has be obsoleted by RFC 4646"

• NEW TERM

• RFC4646

• AGREED: add definition "The set of tags, constructed according to RFC 4646, for the identification of languages"

• NLM:

• AGREED: change to "The set of concepts defined by the National Library of Medicine Classification"

• ACTION 2007-03-17: Tom change all encoding schemes to follow the LCSH change in definition

• ACTION 2007-03-17: Tom to find "uses a controlled vocabulary", report to list, and remove from comments.

• NOTE: if interoperability is operationalized as keeping current encoding schemes already in our namespace, then we should add new terms to keep it up to date.

• QUESTION: Do we need "qualifies statements"? [e.g., p. 57]

• AGREED: remove "qualifies" statements and discuss encoding schemes in application profiles only, not in dcterms

• JUSTIFICATION: this kind of information belongs in an application profile

• QUESTION: do we want to now formally declare subproperty relationships for contributor, subject, and relation?

• AGREED: yes for contributor and relation; no for subject [p. 41]

• JUSTIFICATION: for contributor and relation = clarifies semantics

Immutable page (last edited 2007-06-23 13:35:31 by TomBaker)