Alex,
Thanks for spending the time to think through these issues. Your
changes (and non-changes), and the reasoning behind them, all make
sense. +1 from the Canadian judge.
-Ron
Alex Yiu wrote:
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
|