W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2005

LC124 - openContentStyle proposal

From: <paul.downey@bt.com>
Date: Thu, 21 Jul 2005 14:10:18 +0100
Message-ID: <2B7789AAED12954AAD214AEAC13ACCEF2709E4FD@i2km02-ukbr.domain1.systemhost.net>
To: <www-ws-desc@w3.org>


Following today's F2F discussion, herein a proposal for a 'hook' to 
describe the method for describing evolvable content [1]: 


WSDL 2.0 to provide an openContentStyle property whose value
is of type anyURI. WSDL 2.0 provides 2 (possibly 3) predefined
values:

  - Strict validation (default)
    http://www.w3.org/@@@@/@@/wsdl/ignoreNone

  - Ignore content indicated by the PSVI notKnown flag: 
    http://www.w3.org/@@@@/@@/wsdl/ignoreUnknowns

  [[ - Ignore content which at any point is not expected [2]:

    http://www.w3.org/@@@@/@@/wsdl/ignoreUnexpected
  ]]

An unrecognised an openContentStyle value could be taken 
as a fault (as with MEPs) or indication to default to ignoreNone.


the following options for syntax follows our previous discussion 
[3] and proposal [4] for an ignoreUnknowns flag: 

1) define openContentStyle as a property for *one* of our components, either the:
	a) {description}
    b) {interface}
    c) {element declaration}
    d) {binding}
    e) {endpoint}
   
   surfacing as an attribute in the WSDL namespace in the
   <description>, <interface>, <types>, <endpoint> elements.

2) the openContentStyle is defined on {description} and then engaged by our adding
   an ignoreUnknowns='true|false" on *one* of <interface>, <types> or <endpoint> elements.


1a)/2a) above options, except we define a defaulting rule that a missing value on the
     {endpoint}, defaults to the value on the {types}, then the {binding}, then {element
     declaration}, {interface} finally resorting to the {description}.  
	 Or we identify a subset of that chain, e.g. just {endpoint} then {element declaration}.
     
     It would be an error to supply a different openContentStyle or ignoreUnknowns
     values on different components within a single chain of defaulting. i.e the
     default may be overridden on the endpoint or the types, but a non-default
     value on the types cannot be overridden on the endpoint.

3) define a Feature "http://www.w3.org/2004/08/wsdl/feature/openContentStyle"
   with a property "http://www.w3.org/2004/08/wsdl/feature/openContentStyle/value"
   to contain the processing style value. Engaged anywhere, following standard F&P rules
   for inheritance.


Paul

[1] http://www.flickr.com/photos/psd/27410949/
[2] http://lists.w3.org/Archives/Public/www-ws-desc/2005Jul/0116.html
[3] http://lists.w3.org/Archives/Public/www-ws-desc/2005Jul/att-0015/20050630-ws-desc-minutes.html#item04
[4] http://lists.w3.org/Archives/Public/www-ws-desc/2005Jun/0097.html
Received on Thursday, 21 July 2005 13:10:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:36 GMT