W3C home > Mailing lists > Public > www-ws-desc@w3.org > January 2007

Re: Clarify 'scope' of {element declarations} and {type definitions} re SparqlQuerySimplified-1G

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Tue, 9 Jan 2007 15:53:28 -0500
To: woden-dev@ws.apache.org
Cc: "John Kaputin" <KAPUTIN@uk.ibm.com>, woden-dev@ws.apache.org, www-ws-desc@w3.org
Message-ID: <OF640B5172.9B47ECC3-ON8525725E.0070F55D-8525725E.00723D06@ca.ibm.com>

As we discussed on the Woden telecon, the component model should create 
ElementDeclaration and TypeDefinition components for all the element and 
type definitions that are contained in any schema (inlined, imported, or 

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

"John Kaputin (gmail)" <jakaputin@gmail.com> 
01/09/2007 08:02 AM
Please respond to

woden-dev@ws.apache.org, "John Kaputin" <KAPUTIN@uk.ibm.com>
Clarify 'scope' of {element declarations} and {type definitions} re 

I would like clarification the WSDL 2.0 testcase SparqlQuerySimplified-1G 
and which schema element declarations should be present in the {element 
declarations} property of the Description component. I think I had a 
conversation about this issue with Jonathan and Arthur driving out to 
Niagra Falls at the July interop.

The baseline component model interchange format for this testcase includes 
an element declaration whose namespace is not inlined or imported within 
the WSDL document's <types> element.

Baseline sparql-protocol-query.canonical.wsdlcm contains this item:

        <elementDeclarationComponent xml:id="c22">

This element declaration is defined in a schema which is imported by the 
<xs:schema> element inlined within the <types> element of 
sparql-protocol-query.wsdl. However, the namespace 
http://www.w3.org/1999/02/22-rdf-syntax-ns# is not xs:imported directly 
within the <types> element. 

According to Part 1, section 3.1 Using W3C XML Schema Description 
Schema-0016 "A WSDL 2.0 document MUST NOT refer to XML Schema components 
in a given namespace unless an xs:import or xs:schema element information 
item for that namespace is present ..."

In implementing Woden, I interpreted this to mean that {element 
declarations} and {type definitions} only contain schema components whose 
namespace is inlined or imported directly within the <types> element. The 
Woden sparql-protocol-query.canonical.wsdlcm file refects this, in that 
the element declaration mentioned above is not present (and Woden is 
failing the testcase accordingly).

However, it may be that the intention of the WSDL 2.0 authors is that ALL 
global element declarations and type definitions referenceable by XML 
Schema MUST be included in {element declarations} and {type definitions}, 
regardless of whether they are inlined or imported directly within <types> 
or whether they are 'nested' imports within those directly inlined or 
imported schemas, and that assertions like Schema-0016 only apply when 
WSDL 2.0 components like InterfaceFault and InterfaceMessageReference 
resolve their 'element' QNames to ElementDeclarations (but not to the 
contents of {element declarations} and {type definitions} themselves).

Can someone from the working group please explain which interpretation is 

John Kaputin
Received on Tuesday, 9 January 2007 20:53:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:07:04 UTC