RE: [sdo] Initial RDDL docs.

[Bryan Aupperle <aupperle@us.ibm.com>]

With the correct template this time:


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

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

"Mary McRae" <mary.mcrae@oasis-open.org>
Sent by: Mary McRae <marypmcrae@gmail.com>

12/09/2008 04:44 PM

Please respond to
<mary.mcrae@oasis-open.org>

To	Bryan Aupperle/Raleigh/IBM@IBMUS
cc
Subject	RE: [sdo] Initial RDDL docs.

Hi Bryan,
 
 Please note proper
template is here:
http://docs.oasis-open.org/templates/rddl.html
 
Thanks!
 
Mary
 
From: Bryan Aupperle [mailto:aupperle@us.ibm.com]
Sent: Tuesday, December 09, 2008 3:55 PM
To: sdo@lists.oasis-open.org
Subject: [sdo] Initial RDDL docs.
 

Here is a first pass at the RDDL docs (one for each namespace).


Please review for accuracy (lots of opportunity for cut/paste 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 Data Objects Java(SDO Java) Namespace

December 16, 2008

Introduction

This document describes version 3.0 of the SDO Java 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 SDO Technical Committee that the SDO 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 SDO Java Namespace

Normative Reference:

Resource Title Service Data Objects for JavaVersion 3.0

Title:

Service Data Objects for Java Version 3.0

Stage:

Committee Draft 01

Date:

16 December 2008

This version:

http://docs.oasis-open.org/opencsa/sdo/sdo-java-3.0-spec-cd01.html

Previous version:

N/A

Technical Committee

Service Data Objects

Chair(s):

Ron Barack, Frank Budinsky

Editors:

Frank Budinsky

Additional Formats:

Editable Source

PDF

Comments list:

Submit comments sdo-comment@lists.oasis-open.org

Comments Archive:

http://lists.oasis-open.org/archives/sdo-comment/

XML Schema(s):

Resource Title Service Data Object Java Schema Version 3.0

Related Namespaces

SDO Namespace

SDO XML Namespace

=

Title: [OASIS Specification Title]

Service Data Objects (SDO) Namespace

December 16, 2008

Introduction

This document describes version 3.0 of the SDO 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 SDO Technical Committee that the SDO 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 SDO Namespace

Normative Reference:

Resource Title Service Data Objects Version 3.0

Title:

Service Data Objects Version 3.0

Stage:

Committee Draft 01

Date:

16 December 2008

This version:

http://docs.oasis-open.org/opencsa/sdo/sdo-core-3.0-spec-cd01.html

Previous version:

N/A

Technical Committee

Service Data Objects

Chair(s):

Ron Barack, Frank Budinsky

Editors:

Frank Budinsky

Additional Formats:

Editable Source

PDF

Comments list:

Submit comments sdo-comment@lists.oasis-open.org

Comments Archive:

http://lists.oasis-open.org/archives/sdo-comment/

XML Schema(s):

Resource Title Service Data Object Schema Version 3.0

Related Namespaces

SDO XML Namespace

=

Title: [OASIS Specification Title]

Service Data Objects XML Types(SDO XML) Namespace

December 16, 2008

Introduction

This document describes version 3.0 of the SDO XML 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 SDO Technical Committee that the SDO 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 SDO XML Namespace

Normative Reference:

Resource Title Service Data Objects Version 3.0

Title:

Service Data Objects Version 3.0

Stage:

Committee Draft 01

Date:

16 December 2008

This version:

http://docs.oasis-open.org/opencsa/sdo/sdo-core-3.0-spec-cd01.html

Previous version:

N/A

Technical Committee

Service Data Objects

Chair(s):

Ron Barack, Frank Budinsky

Editors:

Frank Budinsky

Additional Formats:

Editable Source

PDF

Comments list:

Submit comments sdo-comment@lists.oasis-open.org

Comments Archive:

http://lists.oasis-open.org/archives/sdo-comment/

XML Schema(s):

Resource Title Service Data Object XML Schema Version 3.0

Related Namespaces

SDO Namespace

=