W3C home > Mailing lists > Public > public-ws-addressing@w3.org > September 2005

FW: LC305: notational conventions proposal

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Tue, 20 Sep 2005 23:17:05 -0700
Message-ID: <37D0366A39A9044286B2783EB4C3C4E8208172@RED-MSG-10.redmond.corp.microsoft.com>
To: "W3C WS-Addressing Public List" <public-ws-addressing@w3.org>
The WS Description group, in dealing with issue LC305 [1] about
synchronizing the notational conventions between WSDL 2.0 and
WS-Addressing, adopted the proposal below that affect the WSDL specs.  I
took an action to request the editorial changes represented by parts 1
and 5 below in the WS-Addressing Core CR specification.

 

[1] http://www.w3.org/2002/ws/desc/5/lc-issues/#LC305

 

________________________________

From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of Jonathan Marsh
Sent: Friday, September 09, 2005 10:46 AM
To: www-ws-desc@w3.org
Subject: LC305: notational conventions proposal

 

This issue proposes that we say in the pseudo-schema notational
conventions that extensibility points are not indicated, aligning with
WS-A which has that statement.

 

It appears to me that with such a statement, there would only be minor
abuse of the notational conventions, which is easily corrected.
Illustrating elements and attributes in another namespace (e.g.
xs:schema, wsoap:protocol) does not appear to be in conflict with the
general statement that extensibility points are not explicitly
indicated.  WS-A uses a convention of "xs:any" for a container which can
contain arbitrary element content, which seems better in-line with the
notational conventions than WSDL's "other extensibility elements"
annotation.  There is no convention to indicate mixed content (needed by
<wsdl:documentation>), so a local self-explanatory "extension" to the
notational conventions seems reasonable.  I also found a few errors that
need to be corrected.

 

Proposal:

1)     Reword WS-A Core section 1.1: "Pseudo schemas do not include
extensibility points for brevity." --> "For brevity, pseudo-schemas do
not indicate the existence of extensibility points."

2)     Likewise add the statement above to WSDL 2.0 Core section 1.4.8.

3)     Change pseudo-syntax in WSDL 2.0 Core section 3: "other extension
elements" -->"xs:any".

4)     Change pseudo-syntax in WSDL 2.0 Core section 5: "extension
elements" --> "mixed content".  This isn't strictly permitted by the
notational conventions, but is a self-explanatory.

5)     Consider adding pseudo-schema notation sample to WS-A.

6)     Add BNF-pseudo schema notation explanation, or a reference, to
Adjuncts.

7)     Correct typo in 5.6.3: wsoap:mepDefault="xs:anyURI ?" -->
wsoap:mepDefault="xs:anyURI"?.

8)     Correct typo in 5.8.3 and 5.1: wsoap:mep="xs:anyURI"? -->
wsoap:mep="xs:anyURI".

 

--  Jonathan Marsh  --  jmarsh@microsoft.com
<mailto:jmarsh@microsoft.com>   --
http://spaces.msn.com/members/auburnmarshes/
<http://spaces.msn.com/members/auburnmarshes/>   --

 
Received on Wednesday, 21 September 2005 06:17:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:09 GMT