RE: problem with pattern attribute definition?

Thank you for the comment.  The Working Group this issue as a CR125 [1].

The latest editors draft [2] and schema [3] properly indicates that pattern
is optional, defaulting to the "in-out" MEP.

Unless you let us know otherwise within 2 weeks, we will assume you agree
with the resolution of this issue.

[1] http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR125
[2]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-
type=text/html;%20charset=utf-8#InterfaceOperation_XMLRep
[3] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.xsd


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

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
> Behalf Of Amelia A Lewis
> Sent: Thursday, December 07, 2006 10:36 AM
> To: www-ws-desc@w3.org
> Subject: problem with pattern attribute definition?
> 
> 
> Heylas,
> 
> So, the pattern AII is REQUIRED (2.4.2 ed copy, bullet 3).  But if it
> *doesn't exist*, we supply a default value (2.4.2.2, final sentence).
> 
> If that's the way that we always describe defaults (required attribute,
> which if it isn't there has a value anyway), then our description is
> really painfully awkward.  Is this a consequence of describing the "XML
> representation" via the infoset?  Is it boneheaded of me to think that if
> I see "the pattern attribute information item is required" that @pattern
> will always appear on operation?
> 
> Heh.  Can XPath retrieve the value of a defaulted attribute?  That's not
> apropos of much of anything, mind.
> 
> Amy!
> --
> Amelia A. Lewis
> Senior Architect
> TIBCO/Extensibility, Inc.
> alewis@tibco.com