[OASIS Issue Tracker] Updated: (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:all-tabpanel ]

Jeffrey Vaught updated SAF-9:
-----------------------------

    Proposal: 
Vivian's proposal:
After some experiment, I think the best solution to this issue is to modify the "ProtocolType_Type" from simpleType to complexType that contains simpleContent. See below:

old:
   <xsd:simpleType name="ProtocolType_Type">
        <xsd:restriction base="xsd:anyURI"/>
    </xsd:simpleType>

new:
    <xsd:complexType name="ProtocolType_Type">
        <xsd:simpleContent>
            <xsd:extension base="xsd:anyURI">
                <xsd:attribute name="version" type="xsd:string" use="optional"/>
            </xsd:extension>
       </xsd:simpleContent>
    </xsd:complexType>   


The java class after tooling for Syndrome_Type in terms of XML is the same, cause it only reference to 
        element name="AssociatedProtocols" type="{http://docs.oasis-open.org/symptoms/symptoms_v1}ProtocolType_Type";

But the variable of associatedProtocols has changed from List<String> ==> List<ProtocolTypeType>.

WRT to section 4.1.1 element "AssociatedProtocols" in the spec V10:
...
     </Urgency>
    <Signature>xsd:string</Signature>
    <AssociatedProtocols>xsd:anyURI</AssociatedProtocols>*
</Syndrome>

My guess (need to see it on the wire) is the value of xsd:anyURI should look the same, but element name might show the version attribute, something like this:

   <AssociatedProtocols version=01>xsd:anyURI</AssociatedProtocols>








> 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