Re: Minutes, 18 January 2007 WS Description WG telcon

I'd like to comment on the discussion of CR 118.

The current design of the spec is that we do NOT have formal assertions 
for constraints that are enforced by the XML Schema. That just means we 
don't have formal assertion numbers. We still DO have statements in the 
spec. The schema is normative and implements the constraints stated in the 
spec. 

The question of APIs for the component model is beyond the scope of the 
spec. An implementation is not forced to serialize the component model and 
run an XML schema validator. It simple must enforce all the constraints 
stated by the spec, many of which happen to checked via schema validation.

One possible way forward is to leave the formal assertions in (and add 
others) but assign them a type of "schema". At present we have several 
types of constraint, e.g. "document" and "component". The document 
constraints are typically thngs that deal with import and include, i.e. 
cannot be stated in terms of the component model. A "schema" assertion 
would simple be an assertion that is enforced by the nromative WSDL 2.0 
XSD. However, for this to be implemented, we would have to go over the 
spec and add assertions for all the schema constraints.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca



"Jonathan Marsh" <jonathan@wso2.com> 
Sent by: www-ws-desc-request@w3.org
01/18/2007 01:34 PM

To
"'www-ws-desc'" <www-ws-desc@w3.org>
cc

Subject
Minutes, 18 January 2007 WS Description WG telcon






Enclosed.
 
Jonathan Marsh - http://www.wso2.com - 
http://auburnmarshes.spaces.live.com
 
 

Received on Friday, 19 January 2007 14:48:32 UTC