sca-c-cpp message

Subject: RDDL docs for new namespaces

From: Bryan Aupperle <aupperle@us.ibm.com>
To: sca-c-cpp@lists.oasis-open.org
Date: Fri, 16 Jan 2009 09:26:25 -0700

Since we are adding namespaces as part of the WSDL mapping, we have to have RDDL documents that describe each of the new namespaces. Attached are drafts. Please look them over for any errors.

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park, NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

Title: [OASIS Specification Title]

Service Component Architecture (SCA) C++ Namespace

January ??, 2009

Introduction

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

Namespace URI Versioning Policy

It is the intent of the OASIS SCA C and C++ Technical Committee that the SCA C++ 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 Draft, results in non-backwardly compatible changes from a previously published Committee Draft.

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 C++ Namespace

Normative Reference:

Resource Title Service Component Architecture Client and Implementation Model Specification for C++ Version 1.1

Title:

Service Component Architecture Client and Implementation Model Specification for C++ Version 1.1

Stage:

Committee Draft 02

Date:

?? January 2009

This version:

http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-cppcni-1.1-spec-cd02.pdf

Previous version:

N/A

Technical Committee

Service Component Architecture / C and C++

Chair(s):

Bryan Aupperle

Editors:

Bryan Aupperle, David Haney, Pete Robbins

Additional Formats:

Editable Source

HTML

Comments list:

Submit comments sca-c-cpp-comment@lists.oasis-open.org

Comments Archive:

http://lists.oasis-open.org/archives/sca-c-cpp-comment/

XML Schema(s):

Resource Title Service Component Architecture C++ WSDL Extension Schema Version 1.1

Related Namespaces

SCA Namespace

Title: [OASIS Specification Title]

Service Component Architecture (SCA) C Namespace

January ??, 2009

Introduction

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

Namespace URI Versioning Policy

It is the intent of the OASIS SCA C and C++ Technical Committee that the SCA C 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 Draft, results in non-backwardly compatible changes from a previously published Committee Draft.

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 C Namespace