Re: FW: Assertion required for property <constraint>

John,

Just to close the loop on this one, both of these assertions are not 
required since element declarations and type definitions have different 
symbol spaces in XSD. This is the content of CR020. [1] 

The assertions are replaces by notes.

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

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" <jmarsh@microsoft.com> 
Sent by: public-ws-desc-comments-request@w3.org
03/16/2006 06:20 PM

To
<kaputin@uk.ibm.com>, <woden-dev@ws.apache.org>
cc
<public-ws-desc-comments@w3.org>
Subject
FW: Assertion required for property <constraint>






Thanks for your comment.  The WS Description Working Group tracked this 
issue as a CR007 [1].  The Working Group agreed to fix this per [2].  This 
resolution is reflected in the latest draft [3].
 
Unless you let us know otherwise by 13 April, we will assume you agree 
with the resolution of this issue.
 
[1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR007
[2] http://lists.w3.org/Archives/Public/www-ws-desc/2006Feb/0016.html
[3] 
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-type=text/html;%20charset=utf-8#references-definitions
 
 [  Jonathan Marsh  ][  jmarsh@microsoft.com  ][  
http://spaces.msn.com/auburnmarshes  ]
 
 
 

From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On 
Behalf Of John Kaputin (gmail)
Sent: Saturday, January 21, 2006 12:40 AM
To: www-ws-desc@w3.org
Cc: woden-dev@ws.apache.org
Subject: Assertion required for property <constraint>
 
See - Part 1, 3.1.3 References to Element Declarations and Type 
Definitions

The assertions include the following rule from this section about the 
'element' attribute of  <fault>, <input> and <output>:
Schema-0020. An element attribute information item MUST NOT refer to a 
global xs:simpleType or xs:complexType definition.? 

I think there's a similar assertion that needs to be captured in the next 
paragraph:
A constraint attribute information item MUST NOT refer to a global 
xs:element definition. 

....although the text needs to be corrected to reflect that constraint is 
a child element of <property>, not an attribute, and it's the QName within 
<constraint> that must not refer to a global xs:element declaration.

regards,
John Kaputin