Difference between revisions of "Versioning"

From Metadata-Registry
Jump to: navigation, search
(Versioning for Vocabularies)
(JP's notes on versioning:)
Line 40: Line 40:
 
#Vocabulary schema names will contain version information
 
#Vocabulary schema names will contain version information
 
#Schema name versioning will only change if the version change would break backward compatibility
 
#Schema name versioning will only change if the version change would break backward compatibility
 +
 +
 +
===F2F Meeting Editions===
 +
Most control over externally managed vocabularies in terms of versioning will be at a policy level. Services may be developed to manage "slurping" processes when terms change externally, and we should maintain sequenced copies of the concept schemes to be able to track changes over time and reflect those to vocabulary users.

Revision as of 11:48, 14 October 2005

Versioning for Vocabularies

At this point it seems relevant to gather information about the issue:

  • I've requested information from Rebecca Guenther and Eric Childress about the administrative information around the LC vocabularies and DDC (respectively) that might help us manage terms in our vocabularies.
  • Some beginnings of consensus:
  • URIs should be stable so long as the semantics of the term/concept do not change
  • Non-semantic changes might be:
    1. Additions of broader, narrower or related terms
    2. Changes in definition for clarification, correction of typos or grammar, etc.
    3. Addition of definition or scope note when none is present
    4. Change in term status
    5. Addition of other information (references, etc.)
  • Semantic changes, requiring a change in URI, might include:
    1. Term splitting or consolidation
    2. Semantic changes in definition
    3. [Possibly] changes in hierarchical relationships (only when there's no definition and the hierarchy placement is the only semantic clue?) [Not sure how we would enforce this]

JP's notes on versioning:

  • Some potential versioning requirements:
  1. must be able to allow people/services to create dependencies on a 'versioned' snapshot of a particular SKOS/OWL representation of a vocabulary and it's relationships
  2. must be able to encode the version 'number' in the above snapshot
  3. individual values in a vocabulary may be created, updated, or deprecated, but not deleted
  4. URIs of individual values won't contain version information
  5. Namespaces of vocabulary schemas won't be versioned
  6. Vocabulary schema names will contain version information
  7. Schema name versioning will only change if the version change would break backward compatibility


F2F Meeting Editions

Most control over externally managed vocabularies in terms of versioning will be at a policy level. Services may be developed to manage "slurping" processes when terms change externally, and we should maintain sequenced copies of the concept schemes to be able to track changes over time and reflect those to vocabulary users.