sca-assembly message

Subject: RE: [sca-assembly] XSDs for Main SCA Namespace - Updated Namespace

From: Bryan Aupperle <aupperle@us.ibm.com>
To: sca-assembly@lists.oasis-open.org
Date: Thu, 12 Mar 2009 10:26:13 -0600

Argh. Wrong attachment. This is the correct one.

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

"Martin Chapman" <martin.chapman@oracle.com>

03/12/2009 10:59 AM

To	Bryan Aupperle/Raleigh/IBM@IBMUS
cc
Subject	RE: [sca-assembly] XSDs for Main SCA Namespace - Updated Namespace

I’m confused as the attachment is about the C namespace. Am I missing something?

From: Bryan Aupperle [mailto:aupperle@us.ibm.com]
Sent: 11 March 2009 19:39
To: sca-assembly@lists.oasis-open.org
Subject: Re: [sca-assembly] XSDs for Main SCA Namespace - Updated Namespace

Here is a RDDL doc using the current template for the updated namespace.

My question is do we need to add information on the other specs that contribute to the namespace? If we need to, I am willing to do the work.

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

Mike Edwards <mike_edwards@uk.ibm.com>
03/05/2009 05:18 PM

To
"OASIS Assembly" <sca-assembly@lists.oasis-open.org>

cc
"OASIS Policy" <sca-policy@lists.oasis-open.org>, "OASIS BPEL" <sca-bpel@lists.oasis-open.org>, "OASIS CPP" <sca-c-cpp@lists.oasis-open.org>, "OASIS Java" <sca-j@lists.oasis-open.org>, "OASIS Bindings" <sca-bindings@lists.oasis-open.org>

Subject
[sca-assembly] XSDs for Main SCA Namespace - Updated Namespace

Folks,

Following the request from the BPEL TC that we update the namespace for the main SCA namespace, I have done this and built a new set
of XSDs for all the TCs, which are included in the ZIP file here:

Note the following:

1) namespace is now http://docs.oasis-open.org/ns/opencsa/sca/200903

2) check the files that you own carefully - I have changed things such as
- copyright notices
- references to the name(s) of other SCA XSD files

- I have also had to make corrections to several files which had XML/XSD errors in them
including the binding-ws, binidng-jms and the c/cpp files

The files now all have uniform and consistent filenames, as agreed.

Enjoy!

Yours, Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
Email: mike_edwards@uk.ibm.com

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

[attachment "sca-xsds-2009-03.zip" deleted by Bryan Aupperle/Raleigh/IBM] ---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Title: [OASIS Specification Title]

Service Component Architecture (SCA) Namespace

March 10, 2009

Introduction

This document describes version 1.1 of the SCA 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-Assembly Technical Committee that the SCA 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 namespace

Normative Reference:

Resource Title Service Component Architecture Assembly Model Specification Version 1.1

Title:

Service Component Architecture Assembly Model Specification Version 1.1

Stage:

Committee Draft 03

Date:

10 March 2009

This version:

http://docs.oasis-open.org/opencsa/sca-assembly/sca-assembly-1.1-spec-cd03.pdf

Previous version: