sca-assembly message

Subject: SCA-Assembly XML Schema Files

From: Dieter Koenig1 <dieterkoenig@de.ibm.com>
To: sca-assembly@lists.oasis-open.org
Date: Tue, 16 Dec 2008 14:15:40 +0100

I uploaded a revision of the SCA-Assembly XML Schema files to the OASIS TC site:
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/document.php?document_id=30399
containing the following XML Schema artifacts:
- sca.xsd
- sca-binding-sca.xsd
- sca-contribution.xsd
- sca-core.xsd
- sca-definitions.xsd
- sca-implementation-composite.xsd
- sca-implementation-java.xsd
- sca-interface-java.xsd
- sca-interface-wsdl.xsd

This set covers resolutions for issues Assembly-60 and Assembly-32, and some XML Schema formatting -- it therefore addresses the TC Action Item
id=2008-10-30-6 status=pending Karmarkar do the detailed work to implement the resolution to Assembly-60
Note that these files have not yet been copied back into the SCA-Assembly spec.

Kind Regards

Dieter König

Senior Technical Staff Member, WebSphere Process Server Architect
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions



Phone:	+49-7031-16-3426	IBM Deutschland
E-Mail:	dieterkoenig@de.ibm.com	Schönaicher Str. 220
		71032 Böblingen
		Germany


IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Erich Baier Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294

----- Forwarded by Dieter Koenig1/Germany/IBM on 16.12.2008 13:43 -----

From:	Anish Karmarkar <Anish.Karmarkar@oracle.com>
To:	Dieter Koenig1/Germany/IBM@IBMDE
Date:	16.12.2008 10:18
Subject:	Re: Fw: SCA-Assembly Issue 60: Documentation element in SCDL

Looks good to me. Thanks! Can you send this out to the list? I'm at another f2f (at SAP/Walldorf) and may not be able to attend today's assembly call. But will try. -Anish -- Dieter Koenig1 wrote: > Hi Anish, thank you for looking at the schema files. I made changes > corresponding to your three points - if this is ok then I'll upload the > files. > > Re 1): Done - I added the include for sca-implementation-bpel.xsd to > sca.xsd > > Re 2): Done - Actually, I was confused here. The resolution in >http://www.osoa.org/jira/browse/ASSEMBLY-60. has <documentation> because > this is what I copied over from BPEL at the F2F meeting. The issue itself > has <description> which is why I used that. I am happy to go back to > <documentation> in order to comply with the resolution. > > Re 3): Done - I "reactivated" <anyAttribute> and <description> in this way > (please let me know if you agree): > >  > <complexType name="ComponentService"> > <complexContent> > <restriction base="sca:Service"> > <sequence> > <element ref="sca:description" minOccurs="0" maxOccurs=" > unbounded"/> > <element ref="sca:interface" minOccurs="0"/> > <element name="operation" type="sca:Operation" minOccurs="0" > maxOccurs="unbounded"/> > <element ref="sca:binding" minOccurs="0" maxOccurs=" > unbounded"/> > <element ref="sca:callback" minOccurs="0"/> > <any namespace="##other" processContents="lax" minOccurs="0" > maxOccurs="unbounded"/> > </sequence> > <attribute name="name" type="NCName" use="required"/> > <attribute name="requires" type="sca:listOfQNames" use=" > optional"/> > <attribute name="policySets" type="sca:listOfQNames" use=" > optional"/> > <anyAttribute namespace="##other" processContents="lax"/> > </restriction> > </complexContent> > </complexType> > >  > <complexType name="ComponentReference"> > <complexContent> > <restriction base="sca:Reference"> > <sequence> > <element ref="sca:description" minOccurs="0" maxOccurs=" > unbounded"/> > <element ref="sca:interface" minOccurs="0"/> > <element name="operation" type="sca:Operation" minOccurs="0" > maxOccurs="unbounded"/> > <element ref="sca:binding" minOccurs="0" maxOccurs=" > unbounded"/> > <element ref="sca:callback" minOccurs="0"/> > <any namespace="##other" processContents="lax" minOccurs="0" > maxOccurs="unbounded"/> > </sequence> > <attribute name="name" type="NCName" use="required"/> > <attribute name="autowire" type="boolean" use="optional"/> > <attribute name="target" type="sca:listOfAnyURIs" use="optional > "/> > <attribute name="wiredByImpl" type="boolean" use="optional" > default="false"/> > <attribute name="multiplicity" type="sca:Multiplicity" use=" > optional" default="1..1"/> > <attribute name="requires" type="sca:listOfQNames" use=" > optional"/> > <attribute name="policySets" type="sca:listOfQNames" use=" > optional"/> > <anyAttribute namespace="##other" processContents="lax"/> > </restriction> > </complexContent> > </complexType> > > Attachments (must be renamed from "*.zipbin" to "*.zip") > (See attached file: SCA XML Schema Files.zipbin)(See attached file: SCA XML > Schema Dummy Files Required for Validation.zipbin) > > Kind Regards > > Dieter König > > Senior Technical Staff Member, WebSphere Process Server Architect > IBM Software Group, Application and Integration Middleware Software > WSS Business Process Solutions > > > > > > Phone: +49-7031-16-3426 IBM Deutschland (Embedded > image moved > to file: > pic29584.gif) > > E-Mail: dieterkoenig@de.ibm.com Schönaicher Str. 220 > > 71032 Böblingen > > Germany > > > > > > IBM Deutschland > Research & > Development > GmbH / > Vorsitzender des > Aufsichtsrats: > Martin Jetter > Geschäftsführung: > Erich Baier > Sitz der > Gesellschaft: > Böblingen / > Registergericht: > Amtsgericht > Stuttgart, HRB > 243294 > > > > > > |------------> > | From: | > |------------> > >-------------------------------------------------------------------------------------------------------------------------------------------------| > |Anish Karmarkar <Anish.Karmarkar@oracle.com> | > >-------------------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | To: | > |------------> > >-------------------------------------------------------------------------------------------------------------------------------------------------| > |Dieter Koenig1/Germany/IBM@IBMDE | > >-------------------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | Date: | > |------------> > >-------------------------------------------------------------------------------------------------------------------------------------------------| > |09.12.2008 09:01 | > >-------------------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | Subject: | > |------------> > >-------------------------------------------------------------------------------------------------------------------------------------------------| > |Re: Fw: SCA-Assembly Issue 60: Documentation element in SCDL | > >-------------------------------------------------------------------------------------------------------------------------------------------------| > > > > > > Thanks for the reminder. Sorry it took so long. Got stuck in my inbox :-( > Thanks for fix the schema. I know it had a lot of minor problems. > > Three comments: > > 1) sca.xsd has the sca-implementation-bpel.xsd missing > 2) I don't particularly care about this, but the resolution recorded at >http://www.osoa.org/jira/browse/ASSEMBLY-60has "documentation" element > whereas sca-core.xsd has a 'description' element. > 3) ComponentService and ComponentReference are derived by restriction. > If I remember my schema correctly, the content model for derivation by > restriction needs to be repeated. Since in these two cases the > <anyAttribute> and <description> is not repeated, therefore not allowed. > These two types needs to include both <anyAttribute> and <description> > elements. > > Unfortunately, I won't be able to attend tomorrow's call. I have to > attend the JCP Exeucutive Committee call at the same time. Please feel > free to send either your schema + my comments OR the updated schema to > the TC (or upload it). > > Thanks again. > > -Anish > -- > > Dieter Koenig1 wrote: >> Hi Anish, did you have a chance to look into this one? >> >> I am happy to make additional changes if needed. Otherwise, if the XML >> Schema artifacts look ok for you, we might "return" them to the TC such >> that Action Item id=2008-10-30-6 can be closed. I would then upload them > as >> a single zip file to the OASIS web site's "Documents" page - category >> "Working Drafts". >> >> Note again that I did the changes for Issue-32 here as well. >> >> Thanks >> Kind Regards >> >> Dieter König >> >> Senior Technical Staff Member, WebSphere Process Server Architect >> IBM Software Group, Application and Integration Middleware Software >> WSS Business Process Solutions >> > > > > > >> Phone: +49-7031-16-3426 IBM Deutschland > (Embedded > image moved > to file: > pic32504.gif) > >> E-Mail: dieterkoenig@de.ibm.com Schönaicher Str. 220 > > >> 71032 Böblingen > > >> Germany > > > > > > >> IBM Deutschland > >> Research & > >> Development > >> GmbH / > >> Vorsitzender des > >> Aufsichtsrats: > >> Martin Jetter > >> Geschäftsführung: > >> Erich Baier > >> Sitz der > >> Gesellschaft: > >> Böblingen / > >> Registergericht: > >> Amtsgericht > >> Stuttgart, HRB > >> 243294 > > >> >> ----- Forwarded by Dieter Koenig1/Germany/IBM on 08.12.2008 11:35 -----. >> > >> From: Dieter Koenig1/Germany/IBM > > >> To: Anish Karmarkar <Anish.Karmarkar@oracle.com> > > >> Date: 08.11.2008 13:31 > > >> Subject: Re: SCA-Assembly Issue 60: Documentation element in SCDL > > >> >> >> >> Hi Anish, thanks for the feedback. Attached are the SCA XML Schema files >> that I edited. >> >> As indicated in my previous note, I renamed the files (and corresponding >> imports/includes), and already added the changes YOU need to do for Issue >> 32. As a result, all files can be validated consistently. >> >> Additional general notes: >> 1. I renamed the new element "documentation" to "description" - this was >> the original intent of issue 60 and not noted when the resolution > proposal >> was discussed at the F2F >> 2. I fixed the compatibility issue by moving the "any" element wildcard >> from "CommonExtensionBase" back to individual complex types (at the end > of >> the sequence) - the "CommonExtensionBase" has now only the "description" >> element and the "anyAttribute" attribute wildcard >> 3. Note that it can still not be used as a base for "SCAPropertyBase" as >> the latter has the "mixed" attribute and the "any" with namespace >> "##any" (which would make it ambigous) - so I did not touch the Property >> definitions >> 4. I also added an "include" for sca-policy to sca-definitions.xsd (this >> was apparently needed) >> >> Done (added common extension base to complex type definitions): >> sca-contribution.xsd >> sca-core.xsd >> sca-definitions.xsd >> >> Done without content change (formatting only - the type definitions > already >> inherit the description): >> sca.xsd >> sca-binding.xsd >> sca-implementation-composite.xsd >> sca-implementation-java.xsd >> sca-interface-java.xsd >> sca-interface-wsdl.xsd >> >> Not considered here (owned by other TCs) - however, many type definitions >> will also inherit the description automatically: >> sca-binding-jms.xsd >> sca-binding-sca.xsd >> sca-binding-webservice.xsd >> sca-implementation-c.xsd >> sca-implementation-cpp.xsd >> sca-interface-c.xsd >> sca-interface-cpp.xsd >> sca-policy.xsd >> >> If these changes are ok for you, what is the next step? Shall I take the >> artifacts and copy them back to the >> "sca-assembly-1.-spec-wd-09.doc" (creating revision 10) - if so then I > need >> the "WRITE LOCK" for the spec from the editing team! >> >> Attachments (must be renamed from "*.zipbin" to "*.zip" - I remember some >> problems with the zip extension when sending files to Oracle ...): >> 1. The main attachment "SCA XML Schema Files.zip" contains all edited > files >> - these need to go back to the spec. >> (See attached file: SCA XML Schema Files.zipbin) >> 2. The second attachment "SCA XML Schema Dummy Files Required for >> Validation.zip" contains dummy files and an edited sca-policy.xsd in > order >> to let all files validate consistently - if you unzip all into the same >> folder then you are able to validate. >> (See attached file: SCA XML Schema Dummy Files Required for >> Validation.zipbin) >> >> Kind Regards >> >> Dieter König >> >> Senior Technical Staff Member, WebSphere Process Server Architect >> IBM Software Group, Application and Integration Middleware Software >> WSS Business Process Solutions >> > > > > > >> Phone: +49-7031-16-3426 IBM Deutschland > (Embedded > image moved > to file: > pic17495.gif) > >> E-Mail: dieterkoenig@de.ibm.com Schönaicher Str. 220 > > >> 71032 Böblingen > > >> Germany > > > > > > >> IBM Deutschland > >> Research & > >> Development > >> GmbH / > >> Vorsitzender des > >> Aufsichtsrats: > >> Martin Jetter > >> Geschäftsführung: > >> Erich Baier > >> Sitz der > >> Gesellschaft: > >> Böblingen / > >> Registergericht: > >> Amtsgericht > >> Stuttgart, HRB > >> 243294 > > >> >> >> >> > >> From: Anish Karmarkar <Anish.Karmarkar@oracle.com> > > >> To: Dieter Koenig1/Germany/IBM@IBMDE > > >> Date: 30.10.2008 07:50 > > >> Subject: Re: SCA-Assembly Issue 60: Description elements in SCDL > > >> >> >> >> >> Dieter, >> >> Thanks for doing this. This is very good. >> I have just one question/quibble: >> >> The CommonExtensionBase contains the element wildcard and every other >> element is an extension of CommonExtensionBase. This means that the >> wildcard is at the start of the sequence. The existing schema has the >> wildcard at the end of the sequence. This may result in backward compat >> issues. >> One way around this would be to not include the <any ...> in >> CommonExtensionBase, but instead included it in every element decl (I >> know this is a pain, but don't know of a way around it if the wildcard >> is to be at the end of the sequence). >> >> >> -Anish >> -- >> >> Dieter Koenig1 wrote: >>> Hi Anish, I started working on the XML Schema updates for Issue 60 as >>> discussed at the Boston F2F (F2F minutes: >>> >http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/29634/SCA%20Assembly%20minutes%202008-09-30.html> >>> ). >>> >>> Before I even got to the changes, I tried to establish a base that >>> *validates* correctly ... in order to do so, I renamed the files and >>> already added the changes you need to do for Issue 32. I also did some >>> minor formatting. >>> >>> Attached is one of the files which I would like to show you in order to >>> make sure I am on the right track :-) >>> (See attached file: sca-core.xsd) >>> After the preparation mentioned above, I introduced the new >>> "CommonExtensionBase" complex type which is then used as extension base >> for >>> most other complex types. An exception is the Property stuff which only >>> allows for attribute extensions - I consider adding the documentation >>> element there directly. >>> >>> Please let me know if you think I should continue this way with the > other >>> SCA-Assembly XML Schema artifacts or if I already went too far (the >> trouble >>> is that this update is already hard to compare against the original) ... >>> >>> Many thanks in advance! >>> >>> Kind Regards >>> >>> Dieter König >>> >>> Senior Technical Staff Member, WebSphere Process Server Architect >>> IBM Software Group, Application and Integration Middleware Software >>> WSS Business Process Solutions >>> >> >> >> >> >>> Phone: +49-7031-16-3426 IBM Deutschland >> (Embedded >> image moved >> to file: >> pic06263.gif) >> >>> E-Mail: dieterkoenig@de.ibm.com Schönaicher Str. 220 >> >>> 71032 Böblingen >> >>> Germany >> >> >> >> >> >>> IBM Deutschland >>> Research & >>> Development >>> GmbH / >>> Vorsitzender des >>> Aufsichtsrats: >>> Martin Jetter >>> Geschäftsführung: >>> Erich Baier >>> Sitz der >>> Gesellschaft: >>> Böblingen / >>> Registergericht: >>> Amtsgericht >>> Stuttgart, HRB >>> 243294 >> >>> ------------------------------------------------------------------------ >>> >> >> >> ------------------------------------------------------------------------ >> >> >> ------------------------------------------------------------------------ >> > > > ------------------------------------------------------------------------ >