W3C home > Mailing lists > Public > www-ws-desc@w3.org > May 2006

RE: interchange issue: empty properties vs. absent properties

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Wed, 31 May 2006 13:09:42 -0400
To: "Jonathan Marsh" <jmarsh@microsoft.com>
Cc: "Jonathan Marsh" <jmarsh@microsoft.com>, www-ws-desc@w3.org, www-ws-desc-request@w3.org
Message-ID: <OF4328EE6E.BCBF2E79-ON8525717F.005CFFC1-8525717F.005E4CC9@ca.ibm.com>

I just fixed this id-null error,

You should never be seeing empty arrays. The schema requires at least one 
child, (minOccurs = 1 is the default) e.g. 

        <xs:complexType name="ElementDeclarationComponents">
                                The sequence is sorted by the key of 
                        <xs:element name="elementDeclarationComponent"
maxOccurs="unbounded" />

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: www-ws-desc-request@w3.org
05/24/2006 02:31 PM

"Jonathan Marsh" <jmarsh@microsoft.com>, <www-ws-desc@w3.org>

RE: interchange issue: empty properties vs. absent  properties

Actually, maybe this is just a bug in Woden. 
MultipleInlineSchemas-1G\retrieveItems.wsdlcm contains:
<elementDeclaration ref="id-null" /> 
There is no element declaration with id-null, so the result is invalid.
The canonicalization stylesheet strips the ref, which raised the issue 
below.  I think this should be a validation error, but it doesn?t seem to 
be.  I?m making @ref a required attribute of <elementDeclarations/> to 
address this.

From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On 
Behalf Of Jonathan Marsh
Sent: Wednesday, May 24, 2006 10:23 AM
To: www-ws-desc@w3.org
Subject: interchange issue: empty properties vs. absent properties
The spec equates an empty property and an absent property.  I?m finding a 
few places in the interchange format where Woden generates an empty 
property, e.g. <elementDeclarations/>, while I simply omit this element.
Seems like the simplest solution would be to canonicalize such that empty 
properties (which may be all empty elements with no attributes) away ? 
i.e. delete them during canonicalization.  Does that sound reasonable?
 [  Jonathan Marsh  ][  jmarsh@microsoft.com  ][  
http://spaces.msn.com/auburnmarshes  ]
Received on Wednesday, 31 May 2006 17:09:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:58 UTC