OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

opencsa-liaison message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: Proposal for including pointers to previous versions of spec/schemain the RDDL file


Per our decision to allow RDDL documents to contain links to previous 
schemas that use the same NS (as long as they were used by OASIS CS or 
International Standard), I have modified the RDDL template/sample. The 
new doc is attached. There are only two changes from the one at [1] and 
they are "s/CD/CS/" + date change. Per our decision, we won't have 
previous schemas used for CDs in the RDDL.

This fulfills my AI.

-Anish
--


[1] 
http://lists.oasis-open.org/archives/opencsa-liaison/200807/msg00014.html
Title: OASIS Service Component Architecture / Assembly (SCA-Assembly) Specification
http://www.oasis-open.org
  www.oasis-open.org About OASIS OASIS Members Join OASIS OASIS News OASIS Events Members Only XML Cover Pages XML.org  

Service Component Architecture / Assembly (SCA-Assembly) Specification

September 24, 2008

Introduction

This document describes version 1.1 of the SCA-Assembly namespace. It also contains a directory of links to related resources using the Resource Directory Description Language (RDDL) 2.0.

Namespace URI Versioning Policy

The pattern of the SCA Assembly namespace URI shall be:

     http://docs.oasis-open.org/ns/opencsa/sca/yyyymm

Where yyyymm is the century, year and month chosen by the TC for that version of the namespace URI.

It is the intent of the OASIS SCA Assembly Technical Committee that the SCA Assembly namespace URI will not change arbitrarily with each subsequent revision of the corresponding WSDL or XML Schema documents but rather change only when a subsequent revision, published in conjunction with a Committee Specification, results in non-backwardly compatible changes from a previously published Committee Specification.

Under this policy, the following are examples of backwards compatible changes that would not result in assignment of a new namespace URI:

  • addition of new global element, attribute, complexType and simpleType definitions
  • addition of new operations within a WSDL portType or binding (along with the corresponding schema, message and part definitions)
  • addition of new elements or attributes in locations covered by a previously specified wildcard
  • modifications to the pattern facet of a type definition for which the value-space of the previous definition remains valid or for which the value-space of the preponderance of instance would remain valid
  • modifications to the cardinality of elements for which the value-space of possible instance documents conformant to the previous revision of the schema would still be valid with regards to the revised cardinality rule

Related Resources for SCA Assembly

Normative Reference:

SCA Assembly v1.1

XML Schema for SCA Assembly:

sca-1.1-schema-200803.xsd

sca-core-1.1-schema-200803.xsd

sca-binding-1.1-schema-200803.xsd

sca-interface-java-1.1-schema-200803.xsd

sca-interface-wsdl-1.1-schema-200803.xsd

sca-implementation-java-1.1-schema-200803.xsd

sca-implementation-composite-1.1-schema-200803.xsd

sca-implementation-bpel-1.1-schema-200803.xsd

sca-definitions-1.1-schema-200803.xsd



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]