FW: Added schemaLocation to SPARQL protocol WSDL

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
=20

-----Original Message-----
From: Lee Feigenbaum [mailto:[email protected]] 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=20
the WSDL file that defines the SPARQL protocol, suggesting that we add=20
schemaLocation attributes to our XSD import elements, to aid in=20
processors that use the schemaLocation as a hint for finding the schema=20
(such as processors involved in the WSDL 2.0 test suite).

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

"""
Not sure I'm able to provide a general best practice guideline, but=20
AIUI, this is the situation:
1) schemaLocation is always treated as a hint, and doesn't preclude=20
acquiring a schema for a namespace in some other way.  Thus adding it=20
seems harmless enough.
2) schemaLocation provides benefit for implementations without a full=20
schema resolver.
3) The sparql-protocol-query.wsdl as you publish it and the=20
sparql-protocol-query.wsdl as it appears in our test suite differ=20
slightly (schemaLocation attributes).  This is an issue for ongoing=20
maintenance, in which we'd prefer that you were able to publish your=20
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=20
interop IMO.
5) However, the sparql-protocol-query.wsdl hasn't changed significantly=20
in the last 16 months, so manual maintenance is also tractable.
"""

Apologetically, we didn't address this issue until now, but given this=20
advice we've decided to accomnodate the suggestion. I've added explicit=20
schemaLocations to all of the DAWG WSDL and XML schemas that import=20
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=20
should be within a few weeks.

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

Lee