Re: ok if URIs for SPARQL interface etc. ends with paren? (serviceDescription)

-------- Original Message --------
 > From: Dan Connolly <>
 > Date: 6 October 2005 21:46
 >
 > According to latest word from the WSDL WG, the (standard) URI for our
 > interface will be...
 > http://www.w3.org/2005/08/sparql-protocol-query/#wsdl.interface(SparqlQuery)
 >
 > i.e. something that can't be used as a qname in RDF/XML nor turtle.
 >
 > Is that good enough? I need to say within the next week or so if not.

It is unfortunate but the only show-stopper would be it can't be used as a 
property in RDF/XML and it isn't going to be a property in all probability 
(now someone will prove me wrong on this).

	Andy

@prefix sparql:
<http://www.w3.org/2005/08/sparql-protocol-query/#wsdl.interface(SparqlQuery)> .

 >
 >
 > I can't think if any show-stopper reason why not, though it sure isn't
 > pretty.
 >
 > For details, the thread starts with
 > http://lists.w3.org/Archives/Public/public-ws-desc-comments/2005Sep/0009
 > and culminates with
 > http://lists.w3.org/Archives/Public/public-ws-desc-comments/2005Oct/0013
 >
 >
 > This is mostly related to serviceDescription, which we've postponed.
 >  http://www.w3.org/2001/sw/DataAccess/issues#serviceDescription
 >
 > But by the time we (or somebody like us) pick it up, it'll be too late
 > to give technical input on WSDL 2.0.
 >
 > --
 > Dan Connolly, W3C http://www.w3.org/People/Connolly/
 > D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E