[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: ebBP 4/1/2005: Comment re: Specification Version (wd10-schema 2/22)
To clarify two related questions we've received about versioning, I'd like to suggest these proposed changes to Section 4.6.4 in the technical specification and an annotation change in the schema. We are also harmonizing the examples in the technical specification to the schema, so changes will arise there as well. Comments and updates welcome. Thanks. We will discuss on Tuesday, 5 April 2005. =========================================================================================================== Technical specification Section 4.6.4 Versioning Change from: The ebBP technical specification supports three types of versioning: · Versioning of schema by namespace (where minor variant versions within a namespace are handled by different URLs for schema location). The namespace URL always contains the most up-to-date schema. · Versioning by specification Versioning of the artifact instances such as to track differences or group similarities........ Change to: The ebBP technical specification supports three types of versioning: * Versioning of schema by namespace (where minor variant versions within a namespace are handled by different URLs for schema location). The namespace URL always contains the most up-to-date schema. * Versioning by the ebBP technical specification (such as ebBP v2.0) * Versioning of the artifact instances such as to track differences or group similarities BPSS schema Change from: - <#> <xsd:element name="*ProcessSpecification*"> - <#> <xsd:annotation> <xsd:documentation>Root element of a process specification document that has a globally unique identity. The process specification element can specify the version of the technical specification used and the BPSS instance version related to the target BPSS (schema).</xsd:documentation> </xsd:annotation> - <#> <xsd:complexType> - <#> <xsd:complexContent> - <#> <xsd:extension base="*ProcessSpecificationType*"> - <#> <xsd:attribute name="*specificationVersion*" type="*xsd:NMTOKEN*" use="*optional*"> - <#> <xsd:annotation> <xsd:documentation>Is the version of the Process Specification. Note: This attribute was added in v2.0.</xsd:documentation> </xsd:annotation>.......................... </xsd:complexType>.......................... </xsd:element> Change from: - <#> <xsd:element name="*ProcessSpecification*"> - <#> <xsd:annotation> <xsd:documentation>Root element of a process specification document that has a globally unique identity. The process specification element can specify the version of the technical specification used and the BPSS instance version related to the target BPSS (schema).</xsd:documentation> </xsd:annotation> - <#> <xsd:complexType> - <#> <xsd:complexContent> - <#> <xsd:extension base="*ProcessSpecificationType*"> - <#> <xsd:attribute name="*specificationVersion*" type="*xsd:NMTOKEN*" use="*optional*"> - <#> <xsd:annotation> <xsd:documentation>Is the version of the Process Specification. Also reference ProcessSpecificationType. Note: This attribute was added in v2.0.</xsd:documentation> </xsd:annotation>.......................... </xsd:complexType>.......................... </xsd:element>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]