RE: interchange issue: empty properties vs. absent properties

Actually, maybe this is just a bug in Woden.
MultipleInlineSchemas-1G\retrieveItems.wsdlcm contains:

 

<messageContentModel>#none</messageContentModel>

<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
<mailto:jmarsh@microsoft.com>   ][  http://spaces.msn.com/auburnmarshes
<http://spaces.msn.com/auburnmarshes>   ]