Re: [wsbpel] Re: Issue 34 - some schema followup

[Prasad Yendluri <pyendluri@webmethods.com>]

Alex,

>I would suggest a change to the schema of the proposal in Issue 34: making that attribute optional.
>
>If it is clear that the QName of the child EII of the addressing container (eg , somens:BareURI) will not conflict with any other addressing >scheme, then the user certainly has the choice of not using the 'reference-scheme' attribute.

Did you really mean "any other addressing scheme" above? That implies to me a there a default (assumed) addressing scheme. If that is really the case how is that determined? Derived from the QName of the child EII somehow? Can you clarify?

Thanks, Prasad


------- Original Message --------

Subject:	Re: [wsbpel] Re: Issue 34 - some schema followup
Date:	Wed, 30 Jun 2004 12:01:07 -0700
From:	Alex Yiu <alex.yiu@oracle.com>
To:	Ron Ten-Hove <Ronald.Ten-Hove@Sun.COM>, wsbpel@lists.oasis-open.org
CC:	ygoland@bea.com, Satish Thatte <satisht@microsoft.com>, Martin Chapman <martin.chapman@oracle.com>, "Monica J. Martin" <Monica.Martin@Sun.COM>, Francisco Curbera <curbera@us.ibm.com>, Alex Yiu <alex.yiu@oracle.com>
References:	<D78C42C1ADD5CF41AE3B60B03C39D1CD024E28F0@RED-MSG-52.redmond.corp.microsoft.com> <40D75D20.4060403@bea.com> <40D7991C.80101@sun.com>

Hi, all TC members,

After talking to some more people at Oracle, here is a clarification on how 'reference-scheme' attribute can be used.

For example, a service reference scheme (e.g. WSMD) uses WSDL 1.1/20 service element as a reference. It is possible that some other reference scheme (e.g. a future addressing group) may use wsdl11:service/wsdl20:service element as a reference but in a slightly different way. In such a case this attribute will be helpful to disambiguate the scheme and its semantics.

I would suggest a change to the schema of the proposal in Issue 34: making that attribute optional.

If it is clear that the QName of the child EII of the addressing container (eg , somens:BareURI) will not conflict with any other addressing scheme, then the user certainly has the choice of not using the 'reference-scheme' attribute.

Regarding to the mixed="true" suggestion, making it mixed will require us to specify what happens if the content is indeed mixed -- i.e. has both CII and EII. It  may unnecessarily complicate the picture. Defining the new element/type for bare URI just seems simpler.

The schema would look like this after the change:
----------------------------------------------------
<xs:element name="service-ref" type="tns:ServiceRefType" />
<xs:complexType name="ServiceRefType">
    <xs:sequence>
        <xs:any namespace="##other" processContents="lax" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
<xs:attribute name="reference-scheme" type="xs:anyURI" use="optional"/>
</xs:complexType>
----------------------------------------------------

I hope this make sense to you guys!
Thanks!

Regards,
Alex Yiu