RE: [sca-bpel] ISSUE 19: SCA-BPEL XML Schema

http://www.osoa.org/jira/browse/BPEL-19

-----Original Message-----
From: Dieter Koenig1 [mailto:dieterkoenig@de.ibm.com]
Sent: Saturday, March 08, 2008 6:54 AM
To: sca-bpel@lists.oasis-open.org
Cc: Patil, Sanjay
Subject: [sca-bpel] NEW ISSUE: SCA-BPEL XML Schema

Resubmitting the new issue about the missing SCA-BPEL XML Schema - please

add *this* one to JIRA.

I fixed the <element name="multiReference"> and added a couple of comments

in the XML schema.

============================================================

TARGET:

SCA Client and Implementation Model Specification for WS-BPEL - Committee

Draft 01.

DESCRIPTION:

The SCA-BPEL XML Schema (namespace "

http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801") is missing.

Moreover, a number of minor XML Schema related changes are needed - see (1)

- (4) in the proposal below.

PROPOSAL:

The XML Schema for the SCA-BPEL constructs needs to be made available as a

standalone artifact (see attached file) and as an Appendix chapter in the

spec - see below, something along the lines of the following ...

(See attached file: sca-bpel.xsd)

A. XML Schema

<?xml version="1.0" encoding="UTF-8"?>

<!--

-->

<schema xmlns="http://www.w3.org/2001/XMLSchema"

�� targetNamespace="http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801"

�� xmlns:sca-bpel="http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801"

�� xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable"

�� xmlns:sref="http://docs.oasis-open.org/wsbpel/2.0/serviceref"

�� elementFormDefault="qualified">

��

�� <import namespace="

http://docs.oasis-open.org/wsbpel/2.0/process/executable"

�� schemaLocation="

http://docs.oasis-open.org/wsbpel/2.0/OS/process/executable/ws-bpel_executable.xsd

"/>

��

�� <import namespace="http://docs.oasis-open.org/wsbpel/2.0/serviceref"

�� schemaLocation="

http://docs.oasis-open.org/wsbpel/2.0/OS/serviceref/ws-bpel_serviceref.xsd

"/>

�� <!-- WS-BPEL extension attribute for a variable representing an SCA

property -->

�� <attribute name="property" type="bpel:tBoolean"/>

�� <!-- WS-BPEL extension element for a variable representing an SCA

multi-valued reference -->

�� <element name="multiReference">

�� <complexType>

�� <simpleContent>

�� <extension base="string">

�� <attribute name="partnerLinkType" type="QName"/>

�� <attribute name="partnerRole" type="NCName"/>

�� <attribute name="multiplicity" type="sca-bpel:Multiplicity"

use="optional" default="1..n"/>

�� </extension>

�� </simpleContent>

�� </complexType>

�� </element>

�� <simpleType name="Multiplicity">

�� <restriction base="string">

�� <enumeration value="0..n"/>

�� <enumeration value="1..n"/>

�� </restriction>

�� </simpleType>

�� <!-- WS-BPEL extension attribute for a partner link associated with an

SCA multi-valued reference -->

�� <attribute name="multiRefFrom" type="bpel:BPELVariableName"/>

��

�� <element name="serviceReferenceList">

�� <complexType>

�� <sequence>

�� <element ref="sref:service-ref" minOccurs="0" maxOccurs="

unbounded"/>

�� </sequence>

�� </complexType>

�� </element>

</schema>

In addition, the following changes should be made in the spec:

(1) The SCA-BPEL namespace on line 195 is wrong, it should be:

�� <extension namespace="

http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801"

instead of

�� <extension namespace="http://www.osoa.org/xmlns/sca/bpel/1.0"

(2) The XML Schema syntax for the serviceReferenceList (lines 250-257)

definition should have the orange background (used for syntax) instead of

the grey background (used for examples).

(3) The multiRefFrom attribute should reuse the type defined for BPEL

variable names - in line 266, use

�� <partnerLink ... sca-bpel:multiRefFrom="bpel:BPELVariableName" />

instead of

�� <partnerLink ... sca-bpel:multiRefFrom="xs:NCName" />

(4) The BPEL service-ref element is defined in the namespace associated

with the prefix "sref:", so the XPath expression in line 288 should be

�� count($vendors/sref:service-ref)

instead of

�� count($vendors/bpel:service-ref)

and in line 301

�� <from>$vendors/sref:service-ref[$idx]</from>

instead of

�� <from>$vendors/bpel:service-ref[$idx]</from>

Kind Regards

��

�Dieter K�nig�� Mail: dieterkoenig@de.ibm.com�� IBM Deutschland Entwicklung GmbH��

��

�Senior Technical Staff Member�� Tel (office): (+49) 7031-16-3426�� Vorsitzender des Aufsichtsrats:��

�� Martin Jetter��

��

�Architect, Business Process�� Fax (office): (+49) 7031-16-4890�� Gesch�ftsf�hrung: Herbert Kircher��

�Choreographer��

��

�Member, Technical Expert Council�� Tel (home office): (+49) 7032-201464� Sitz der Gesellschaft: B�blingen��

��

�� Sch�naicher Strasse 220, 71032�� Registergericht: Amtsgericht��

�� B�blingen, Germany�� Stuttgart, HRB 243294��

��

� From:�� "Patil, Sanjay" <sanjay.patil@sap.com>��

��

� To:�� Dieter Koenig1/Germany/IBM@IBMDE, <sca-bpel@lists.oasis-open.org>��

��

� Date:�� 07.03.2008 17:26��

��

� Subject:�� RE: [sca-bpel] NEW ISSUE: SCA-BPEL XML Schema��

��

Shouldn't the� <element name="multiRefFrom"> in the schema be� <element

name="multiReference"> ?

-- Sanjay

> -----Original Message-----

> From: Dieter Koenig1 [mailto:dieterkoenig@de.ibm.com]

> Sent: Friday, Mar 07, 2008 5:38 AM

> To: sca-bpel@lists.oasis-open.org

> Subject: [sca-bpel] NEW ISSUE: SCA-BPEL XML Schema

> TARGET:

> SCA Client and Implementation Model Specification for WS-BPEL

> - Committee

> Draft 01.

> DESCRIPTION:

> The SCA-BPEL XML Schema (namespace

> "http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801") is missing.

> Moreover, a number of minor XML Schema related changes are

> needed - see (1)

> - (4) in the proposal below.

> PROPOSAL:

> The XML Schema for the SCA-BPEL constructs needs to be made

> available as a

> standalone artifact (see attached file) and as an Appendix

> chapter in the

> spec - see below, something along the lines of the following ...

> (See attached file: sca-bpel.xsd)

> A. XML Schema

> <?xml version="1.0" encoding="UTF-8"?>

> <schema xmlns="http://www.w3.org/2001/XMLSchema"

> targetNamespace="http://docs.oasis-open.org/ns/opencsa/sca-bpe

> l/200801"

> xmlns:sca-bpel="http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801"

> xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable"

>�� xmlns:sref="http://docs.oasis-open.org/wsbpel/2.0/serviceref"

>�� elementFormDefault="qualified"

>�� attributeFormDefault="unqualified">

>�� <import namespace="

> http://docs.oasis-open.org/wsbpel/2.0/process/executable"

>�� schemaLocation="

> http://docs.oasis-open.org/wsbpel/2.0/OS/process/executable/ws

> -bpel_executable.xsd

> "/>

>�� <import

> namespace="http://docs.oasis-open.org/wsbpel/2.0/serviceref"

>�� schemaLocation="

> http://docs.oasis-open.org/wsbpel/2.0/OS/serviceref/ws-bpel_se

> rviceref.xsd

> "/>

>�� <attribute name="multiRefFrom" type="bpel:BPELVariableName"/>

>�� <attribute name="property" type="bpel:tBoolean"/>

>�� <element name="multiRefFrom">

>�� <complexType>

>�� <simpleContent>

>�� <extension base="string">

>�� <attribute name="partnerLinkType" type="QName"/>

>�� <attribute name="partnerRole" type="NCName"/>

>�� <attribute name="multiplicity"

> type="sca-bpel:Multiplicity"

> use="optional" default="1..n"/>

>�� </extension>

>�� </simpleContent>

>�� </complexType>

>�� </element>

>�� <simpleType name="Multiplicity">

>�� <restriction base="string">

>�� <enumeration value="0..n"/>

>�� <enumeration value="1..n"/>

>�� </restriction>

>�� </simpleType>

>�� <element name="serviceReferenceList">

>�� <complexType>

>�� <sequence>

>�� <element ref="sref:service-ref" minOccurs="0" maxOccurs="

> unbounded"/>

>�� </sequence>

>�� </complexType>

>�� </element>

> </schema>

> In addition, the following changes should be made in the spec:

> (1) The SCA-BPEL namespace on line 195 is wrong, it should be:

>�� <extension namespace="

> http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801"

> instead of

>�� <extension namespace="http://www.osoa.org/xmlns/sca/bpel/1.0"

> (2) The XML Schema syntax for the serviceReferenceList (lines 250-257)

> definition should have the orange background (used for

> syntax) instead of

> the grey background (used for examples).

> (3) The multiRefFrom attribute should reuse the type defined for BPEL

> variable names - in line 266, use

>�� <partnerLink ... sca-bpel:multiRefFrom="bpel:BPELVariableName" />

> instead of

>�� <partnerLink ... sca-bpel:multiRefFrom="xs:NCName" />

> (4) The BPEL service-ref element is defined in the namespace

> associated

> with the prefix "sref:", so the XPath expression in line 288 should be

>�� count($vendors/sref:service-ref)

> instead of

>�� count($vendors/bpel:service-ref)

> and in line 301

>�� <from>$vendors/sref:service-ref[$idx]</from>

> instead of

>�� <from>$vendors/bpel:service-ref[$idx]</from>

> Kind Regards

> DK

---------------------------------------------------------------------

To unsubscribe from this mail list, you must leave the OASIS TC that

generates this mail.� You may a link to this group and all your TCs in

OASIS

at:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

sca-bpel message