If we included the clarification, which I think we should, we should
point out that http://schemas.xmlsoap.org/wsdl/2004-08-24.xsd
is NOT a NSURI, but a
schema location.
Something along the lines of
It should be noted that the examples provided
in this
specification adopt the Schema
whose namespace URI is
http://schemas.xmlsoap.org/wsdl/ and which can be found at location
"http://schemas.xmlsoap.org/wsdl/2004-08-24.xsd"
for
[WSDL 1.1], as it incorporates fixes for
known errors
and is the Schema
selected
by the WS-I BP 1.1 Errata (October 25, 2005).
Alexandre Alves wrote:
Hi,
Resending updated proposal.
Problem Description:
Incompatible WSDL schema versions and BPEL
examples.
Proposal:
As kindly pointed out by TC, WS-I has kept
the same WSDL URI and just
referenced a different WSDL schema which fixes the extensibility
problem we were
facing. So the BPEL examples in the spec are no longer invalid in
regards to
WS-I compliance. Hence, there is nothing to fix in the BPEL spec, aside
from
adding a possible clarification.
I am including a clarification in this
proposal, but I am open to not
having a clarification at all and closing the issue with no change.
----
Change section 3:
With respect to [WS-I Basic Profile] (Basic
Profile 1.1) all BPEL
implementations SHOULD be configurable such that they can participate
in Basic
Profile 1.1 compliant interactions. A BPEL implementation MAY allow the
Basic
Profile 1.1 configuration to be disabled, even for scenarios
encompassed by the
Basic Profile 1.1. At the time this specification was completed, the
WSDL v2.0
work was ongoing and not ready for consideration for WS-BPEL v2.0.
Future
versions of WS-BPEL may provide support for WSDL v2.0.
By:
With respect to [WS-I Basic Profile] (Basic
Profile 1.1) all BPEL
implementations SHOULD be configurable such that they can participate
in Basic
Profile 1.1 compliant interactions. A BPEL implementation MAY allow the
Basic
Profile 1.1 configuration to be disabled, even for scenarios
encompassed by the
Basic Profile 1.1. At the time this specification was completed, the
WSDL v2.0
work was ongoing and not ready for consideration for WS-BPEL v2.0.
Future
versions of WS-BPEL may provide support for WSDL v2.0.
It should be noted that the examples provided
in this
specification adopt the Schema
"http://schemas.xmlsoap.org/wsdl/2004-08-24.xsd"
for
[WSDL 1.1], as it incorporates fixes for
known errors
and is the Schema
selected by the WS-I BP 1.1 Errata (October
25, 2005).
----
Rgds
-----Original Message-----
From: Alexandre Alves [mailto:]
Sent: Tuesday, November 22, 2005 1:23 PM
To:
Cc: Danny van der Rijn; Francisco Curbera
Subject: [wsbpel] Issue - 195 - Proposal to
vote
Hi,
Indeed WS-I BP 1.1 errata
(http://www.ws-i.org/Profiles/BasicProfile-1.1-errata.html),
err07,
references updated XSDs that fixes the
problem.
Problem Description:
Incompatible WSDL schema versions and BPEL
examples.
Proposal:
Replace all WSDL URIs in specification to
reference to
http://schemas.xmlsoap.org/wsdl/2004-08-24.xsd,
thus conforming to WS-I
BP 1.1 (latest errata).
Specifically, change:
- At section 2. Notational Conventions,
replace
* wsdl -
"http://schemas.xmlsoap.org/wsdl/"
For
* wsdl -
"http://schemas.xmlsoap.org/wsdl/2004-08-24.xsd"
Add the following paragraph to the end of the
section:
'Particularly, the Schema
"http://schemas.xmlsoap.org/wsdl/2004-08-24.xsd"
is being
adopted for
[WSDL 1.1], as it incorporates fixes for
known errors and is the Schema
selected by WS-I BP 1.1 Errata (October 25,
2005).'
- At section 6.4 Document Linking, replace
'...and to
"http://schemas.xmlsoap.org/wsdl/"; when importing
WSDL 1.1
documents...'
For
'...and to
"http://schemas.xmlsoap.org/wsdl/2004-08-24.xsd";
when
importing WSDL 1.1 documents...'
- Change all WSDL document examples:
Replace default namespace of definitions to
xmlns="http://schemas.xmlsoap.org/wsdl/2004-08-24.xsd"
-----Original Message-----
From: Yaron Goland
Sent: Monday, March 21, 2005 11:04 AM
To: Francisco Curbera
Cc: Danny van der Rijn;
Subject: Re: [wsbpel] Issue 195: Incompatible
WSDL schema versions and
BPEL examples
The only problem is that 'fixing' our
examples means that our examples
won't work with the Schema specified in the
WSDL 1.1 spec which is a
required part of our charter.
The good news is that WS-I is aware of this
mess and is actively
working
on an errata for BP 1.1 that will fix it. The
errata will require that
extension points be placed at both the top
and bottom of the WSDL file.
This errata will therefore make our existing
examples legal with both
WSDL 1.1 and BP 1.1.
For the moment I would recommend that we do
nothing and see if WS-I is
able to get out the errata before we finish
up.
Yaron
Francisco Curbera wrote:
> If the issue is that our examples do not
comply with the BP 1.1
(including
> its endorsed WSDL schema) then we need
to fix them, since that was
part of
> the resolution of issue 72 (now updated
I believe to support BP
1.1
instead
> of BP 1.0). seems like a good task for
the editors.
>
> Paco
>
>
>
>
>
>
>
Danny van
> der
>
>
>
Rijn
To:
>
>
>
<
> cc:
>
>
>
> Subject:
Re: [wsbpel]
Issue 195:
> Incompatible WSDL schema versions and
BPEL examples
>
>
>
>
>
03/15/2005
> 05:46
>
>
>
> PM
>
>
>
>
>
>
>
>
> +1
>
> Tony Fletcher wrote:
> This issue has been added to
the wsbpel issue list with a status
of
> "received". The
status will be changed to "open" if the TC
accepts it
> as identifying a bug in the
spec or decides it should be
accepted
> specially. Otherwise it will
be closed without further
consideration
> (but will be marked as
"Revisitable")
>
>
> The issues list is posted as a
Technical Committee document to
the
> OASIS WSBPEL TC pages on a
regular basis. The current edition,
as a
> TC document, is the most
recent version of the document entitled
in
> the "Issues" folder
of the WSBPEL TC document list - the next
posting
> as a TC document will include
this issue. The list editor's
working
> copy, which will normally include
an issue when it is announced,
is
> available at this constant
URL.
>
>
> Issue 195:
Incompatible WSDL schema versions and BPEL examples
> Status: received
> Date added: 4 Mar 2005
> Categories: Syntax and
validation
> Date submitted: 04 March 2004
> Submitter: Yaron Y. Goland
> Description: For details on
this issue please refer to
>
http://www.goland.org/Tech/wsdl11mess.htm. The good news is that
> there is an errata coming out
for WS-I BP 1.1 and apparently
there is
> some possibility that this
gratuitous incompatibility will be
fixed.
> Submitter's proposal: For now
we just track this issue and see
if
> WS-I manages to fix it before
we finish up. Otherwise we will
have to
> pick which of the WSDL
versions to support.
> Links:
http://www.goland.org/Tech/wsdl11mess.htm
> Changes: 4 Mar 2005 - new
issue
>
>
>
> Best Regards,
> Tony
>
>
> |------------------------+
-------------------------------------|
> |(Embedded image moved to|Tony |
|
> |file: pic06128.gif) |Fletcher |
|
>
|
|Technical|
|
>
|
|Advisor |
|
>
|
|Choreolog|
|
> | |y
Ltd. |
|
>
|
|68, |
|
>
|
|Lombard |
|
>
|
|Street, |
|
>
|
|London |
|
>
|
|EC3V 9L J|
|
>
|
|UK |
|
>
|------------------------+---------+------------------------------------
-|
>
|
|Phone: |+44 (0) 1473 729537
|
>
|------------------------+---------+------------------------------------
-|
>
|
|Mobile: |+44 (0) 7801 948219
|
>
|------------------------+---------+------------------------------------
-|
>
|
|Fax: |+44 (0) 870 7390077
|
>
|------------------------+---------+------------------------------------
-|
>
|
|Web: |www.choreology.com
|
>
|------------------------+---------+------------------------------------
-|
>
Cohesions(tm)
|
|
>
-------------------------------------|
> Business
transaction |
|
> management software
for |
|
> application
coordination |
|
>
-------------------------------------|
>
Work:
|
|
>
tony.fletcher@choreology
|
|
>
.com
|
|
>
-------------------------------------|
> Home:
|
|
>
-------------------------------------|
>
>
>
>
>
>
>
>
>
------------------------------------------------------------------------
>
>
>
------------------------------------------------------------------------
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
---------------------------------------------------------------------
To unsubscribe, e-mail:
For additional commands, e-mail:
---------------------------------------------------------------------
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
