Re: LC 121 text for IgnoreUnexpected

Dave,

I agree with the spirit of this text. I am concerned that this is not a 
precise definition and different vendors may implement it differently, 
which would cause interop problems. I believe we need a definition that is 
as precise as the text of the XML Schema spec. This boils down to spelling 
out the algorithm in the same level of detail as the algorithm for 
validation.

Arthur Ryman,
Rational Desktop Tools Development

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
intranet: http://labweb.torolab.ibm.com/DRY6/



"David Orchard" <dorchard@bea.com> 
Sent by: www-ws-desc-request@w3.org
07/20/2005 07:42 PM

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

Subject
LC 121 text for IgnoreUnexpected






A proposal for some text of the IgnoreUnexpected, basically a change to 
sentences #1 and #2
 
The "ignoreExpected" property set to "true" indicates that a processor
should not fault when processing messages that contain _unexpected
items_.  _Unexpected items_ are attributes and elements that are not
permitted by the schema for a particular element.  _Unexpected items_ may 
appear in
any namespace including the targetNamespace of a known schema, as well
as in a namespace for which no schema is currently known.  _Unexpected
items_ includes the descendents of the item, such any child elements,
attributes and content.
 
Explanation of changes
The second sentence in the "ignoreUnknown" reads "_Unexpected items_ are 
attributes and elements not defined by
the schema for a particular element."
 
Clearly we have to distinguish between the "unknown", ie not defined by 
the schema, and the known but not allowed elements/attributes.
 
The goal is to:
1) Add an effective <xs:any namespace="##any"/> everywhere in the schema, 
2) Add an effective anyAttribute everywhere in the schema,
3) change all the maxOccurs="unbounded".
 
Cheers,
Dave