Re: [sca-assembly] Re: Problem with Posted XSDs and RDDL file for the SCAAssembly CD05

[Mike Edwards <mike_edwards@uk.ibm.com>]

Mary,

OK, for the first part, I have attached
a corrected version of the RDDL file to this email.

I would be grateful if you could replace
the existing RDDL file with this new one.



Moving on the the question of the problem
with the file:

http://docs.oasis-open.org/opencsa/sca-assembly/sca-1.1-cd05.xsd


what do you propose that we should do
with this?

The SCA Assembly specification CD05
is correct (it shows this XSD without the funny whitespace character)
- surely we don't need to vote a CD06
just for this one change?

Will a vote to replace that one file
do?
eg replace the file with one called
"sca-1.1-cd05a.xsd" for example?

The namespace is broken at the moment,
so there is no point to keeping the files as they are - they are unusable.


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

From:	Mary McRae <mary.mcrae@oasis-open.org>
To:	Mike Edwards/UK/IBM@IBMGB
Cc:	tc-admin@oasis-open.org, "OASIS Assembly" <sca-assembly@lists.oasis-open.org>
Date:	04/03/2010 15:37
Subject:	[sca-assembly] Re: Problem with Posted XSDs and RDDL file for the SCA Assembly CD05

---

Hi Mike,

  While I can update the RDDL file, I can't overwrite
the schema since it's the one that was approved by the TC and is authoritative.
While not a substantive change, the TC is going to have to issue a new
version to update.

  In the interim you could place a draft copy in kavi along with a
note on your homepage that it will be corrected in the next CD.

Mary

On Mar 4, 2010, at 9:48 AM, Mike Edwards wrote:


Mary, 

It has been brought to our attention that there is a technical fault with
one of the XSDs posted to the OASIS site 
which causes a problem when trying to view any of the SCA Assembly XSDs.

The problem occurs when viewing the XSDs linked from the RDDL file here:

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

when viewing this file: 

http://docs.oasis-open.org/opencsa/sca-assembly/sca-1.1-cd05.xsd

a problem is reported. 

It turns out that this problem is caused by an extraneous white space character
in the file: 

   <include schemaLocation="sca-binding-ws-1.1-cd04.xsd"/>
   <include schemaLocation="sca-binding-ws-callback-1.1-cd04.xsd"/

   ><include schemaLocation="sca-binding-jms-1.1-cd04.xsd"/>
   <include schemaLocation="sca-binding-jca-1.1-cd04.xsd"/>
  
   <include schemaLocation="sca-binding-sca-1.1-cd05.xsd"/>
   <include schemaLocation="sca-binding-ejb-1.1-cd01.xsd"/>

Note the misplaced ">" at the beginning of the 3rd line.

This fault appears to prevent proper viewing of any of the other XSD files
linked from the 
RDDL, for the reason that all the other files depend on the one with the
fault. 

There is a fixed version of the XSD file that removes the fault.  It
is attached to this note. 

I would be grateful if you could replace the faulty file with this corrected
version     


There is unfortunately also a technical fault with the RDDL file itself
for the SCA Assembly namespace. 

There is a link to the "Service
Component Architecture Policy Intent Definitions Version 1.1
" 
which has the hyperlink value: 

http://docs.oasis-open.org/opencsa/sca-assembly/sca-policy-1.1-intents-definitions-cd03.xsd

Unfortunately, thetarget file is an XML file not an XSD, so the hyperlink
should read: 

http://docs.oasis-open.org/opencsa/sca-assembly/sca-policy-1.1-intents-definitions-cd03.xml

I would be grateful if you could replace the faulty RDDL file with this
corrected version:     


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

<sca-1.1-cd05.xsd><sca-1.1-rddl-200912.html>

---

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

Title: OASIS Service Component Architecture / Assembly (SCA-Assembly) Specification

Service Component Architecture (SCA) Namespace

January 25, 2010

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

The pattern of the SCA Assembly namespace URI is:

     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 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 05

Date:

12 January 2010

This version:

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

Previous version:

http://www.oasis-open.org/committees/download.php/30701/sca-assembly-1.1-spec-cd03.pdf

Technical Committee

Service Component Architecture / Assembly

Chair(s):

Martin Chapman, Mike Edwards

Editors:

Michael Beisiegel, Khanderao Khand, Anish Karmarkar, Sanjay Patil, Michael Rowley

Additional Formats:

Editable Source

HTML

Comments list:

Submit comments sca-assembly-comment@lists.oasis-open.org

Comments Archive:

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

XML Schemas:

Resource Title Service Component Architecture Schema Version 1.1

Resource Title Service Component Architecture Core Schema Version 1.1

Resource Title Service Component Architecture Definitions Schema Version 1.1

Resource Title Service Component Architecture Policy Schema Version 1.1

Resource Title Service Component Architecture Policy Intent Definitions Version 1.1

Resource Title Service Component Architecture WSDL Interface Schema Version 1.1

Resource Title Service Component Architecture C Interface Schema Version 1.1

Resource Title Service Component Architecture C++ Interface Schema Version 1.1

Resource Title Service Component Architecture Java Interface Schema Version 1.1

Resource Title Service Component Architecture SCA Binding Schema Version 1.1

Resource Title Service Component Architecture Web Service Binding Schema Version 1.1

Resource Title Service Component Architecture Web Service Binding Callback Protocol Policy Assertion Version 1.1

Resource Title Service Component Architecture JMS Binding Schema Version 1.1

Resource Title Service Component Architecture JCA Binding Schema Version 1.1

Resource Title Service Component Architecture EJB Binding Schema Version 1.1

Resource Title Service Component Architecture Composite Implementation Schema Version 1.1

Resource Title Service Component Architecture BPEL Implementation Schema Version 1.1

Resource Title Service Component Architecture C Implementation Schema Version 1.1

Resource Title Service Component Architecture C++ Implementation Schema Version 1.1

Resource Title Service Component Architecture Java Implementation Schema Version 1.1

Resource Title Service Component Architecture Contribution Schema Version 1.1

Resource Title Service Component Architecture C Contribution Schema Version 1.1

Resource Title Service Component Architecture C++ Contribution Schema Version 1.1

Resource Title Service Component Architecture Java Contribution Schema Version 1.1