Hi everyone,
The TC Process requires that the schema be maintained as a separate file and
that the separate file is the normative version. If the CD is to be uploaded to
docs.oasis-open.org I'll require the schema as a separate file; if you're just
uploading to Kavi then I'll require the schema when you move forward with public
review.
http://www.oasis-open.org/committees/process-2008-02-05.php#specQuality
Regards,
Mary
> -----Original Message-----
> From: Patil, Sanjay [mailto:]
> Sent: Friday, March 07, 2008 11:51 AM
> To:
> Subject: RE: [sca-bpel] NEW ISSUE: SCA-BPEL XML Schema
>
>
> Thanks a bunch to Dieter for putting together the schema proposal.
>
> Note that the CD drafts [1] we approved on the 1/17/08 conf-call [2] do
> not include the schema either inline in the specification text or as a
> separate file.
>
> Do the TC members think it as important to conduct the CD approval vote
> once again with a new set of drafts that include the schema? I
> personally do. At the minimum, I would be hesitant to publish the CD
> drafts without the schema to the OASIS doc repository.
>
> On a side note - I think having the schema inline (in the
> specifications) may be sufficient for the CD versions. For the later
> stages (PR/CS/OS), we could publish the schema file separately.
>
> -- Sanjay
>
> [1]
> http://www.oasis-open.org/apps/org/workgroup/sca-bpel/download.php/26773
> /sca-bpel-draft-1.1-spec-WD-05.doc
> [2] http://lists.oasis-open.org/archives/sca-bpel/200801/msg00027.html
>
>
>
> > -----Original Message-----
> > From: Dieter Koenig1 [mailto:]
> > Sent: Friday, Mar 07, 2008 5:38 AM
> > To:
> > 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
