[OASIS Issue Tracker] Commented: (SAF-9) Versioning

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/SAF-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27232#action_27232 ] 

Jeffrey Vaught commented on SAF-9:
----------------------------------

Consensus is to address as follows:
o	schema namespace to distinguish between different versions of the spec.  There is already verbiage that covers this in the Spec preamble, so likely nothing additional needed.
o	element versions 
        - needed for "class" types, but not instances like Prescription & Symptom.
        - SymptomType, PrescriptionType, Syndrome, and Protocol should have an extra element "Version".  Referencing those, we would add an attribute version="x".  If absent, the latest version is assumed.


> Versioning
> ----------
>
>                 Key: SAF-9
>                 URL: http://tools.oasis-open.org/issues/browse/SAF-9
>             Project: OASIS Symptoms Automation Framework (SAF) TC
>          Issue Type: Task
>            Reporter: Jeffrey Vaught
>            Assignee: Vivian Lee
>            Priority: Critical
>
> Some data types in the specification may benefit from version numbering, other than that implicit in the element type URI. 
> Notes
> Nov 5, 2009 - 
> •	Vivian: Could use namespaces in Spec for versioning.
> •	Paul: Version the entities themselves (in the catalog), ie: Protocol type or example, URI:Av1, URI:Av2.  
> •	Jeff: Needed for compatibility between newer/older releases (but doesn't preclude using namespaces).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira