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

FW: Added schemaLocation to SPARQL protocol WSDL

From: Jonathan Marsh <jonathan@wso2.com>
Date: Fri, 12 Oct 2007 09:38:48 -0700
To: "'WS-Description WG'" <www-ws-desc@w3.org>
Cc: "'Lee Feigenbaum '"
Message-ID: <00be01c80cee$5e4fffb0$1aefff10$@com>

A note to ourselves to update the test suite with the final wsdl when it becomes available...

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

-----Original Message-----
From: Lee Feigenbaum [mailto:figtree@gmail.com] On Behalf Of Lee Feigenbaum
Sent: Wednesday, October 10, 2007 9:25 PM
To: 'RDF Data Access Working Group'; Jonathan Marsh
Subject: Added schemaLocation to SPARQL protocol WSDL

In a message of many, many moons ago, Jonathan wrote to this list about 
the WSDL file that defines the SPARQL protocol, suggesting that we add 
schemaLocation attributes to our XSD import elements, to aid in 
processors that use the schemaLocation as a hint for finding the schema 
(such as processors involved in the WSDL 2.0 test suite).

In a recent off-list mail conversation with Jonathan, he noted (w/ 
permission to post this publicly):

"""
Not sure I'm able to provide a general best practice guideline, but 
AIUI, this is the situation:
1) schemaLocation is always treated as a hint, and doesn't preclude 
acquiring a schema for a namespace in some other way.  Thus adding it 
seems harmless enough.
2) schemaLocation provides benefit for implementations without a full 
schema resolver.
3) The sparql-protocol-query.wsdl as you publish it and the 
sparql-protocol-query.wsdl as it appears in our test suite differ 
slightly (schemaLocation attributes).  This is an issue for ongoing 
maintenance, in which we'd prefer that you were able to publish your 
wsdl directly into our test suite without any modification whatsoever.
4) Maintenance of the WSDL test suite will lie with the upcoming WS Core 
WG, so the test suite isn't necessarily frozen in its current state, and 
could continue to be used by vendors to verify that they support all the 
features used by sparql-protocol-query.wsdl - a good thing for sparql 
interop IMO.
5) However, the sparql-protocol-query.wsdl hasn't changed significantly 
in the last 16 months, so manual maintenance is also tractable.
"""

Apologetically, we didn't address this issue until now, but given this 
advice we've decided to accomnodate the suggestion. I've added explicit 
schemaLocations to all of the DAWG WSDL and XML schemas that import 
schemas. For the moment, the change is only in the local editors' copies 
of the files, but it will reach /TR/ space when we next publish, which 
should be within a few weeks.

Jonathan, thanks for the implicit and extended patience, and please let 
us know if you have further comments or concerns.

Lee
Received on Friday, 12 October 2007 16:39:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:47 GMT