W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > March 2006

RE: Relax IRI style cardinality [was Belated comments on SPARQL Protocol for RDF 25 January 2006 LC WD]

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Thu, 16 Mar 2006 15:32:15 -0800
Message-ID: <37D0366A39A9044286B2783EB4C3C4E801F21714@RED-MSG-10.redmond.corp.microsoft.com>
To: "Hugo Haas" <hugo@w3.org>
Cc: <public-ws-desc-comments@w3.org>

Thanks for your comment.  The WS Description Working Group tracked this
issue as a CR013 [1].  The Working Group adopted the fix suggested in
[2].

Unless you let us know otherwise by 13 April, we will assume you agree
with the resolution of this issue.

[1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR013
[2] http://lists.w3.org/Archives/Public/www-ws-desc/2006Feb/0062.html

 [  Jonathan Marsh  ][  jmarsh@microsoft.com  ][
http://spaces.msn.com/auburnmarshes  ]


> -----Original Message-----
> From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-
> comments-request@w3.org] On Behalf Of Jonathan Marsh
> Sent: Friday, February 17, 2006 10:34 AM
> To: public-ws-desc-comments@w3.org
> Cc: Hugo Haas
> Subject: Relax IRI style cardinality [was Belated comments on SPARQL
> Protocol for RDF 25 January 2006 LC WD]
> 
> 
> Proposing the relevant part of Hugo's mail as a CR issue.
> 
> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
On
> Behalf Of Hugo Haas
> Sent: Tuesday, February 14, 2006 2:39 AM
> To: www-ws-desc@w3.org
> Subject: Belated comments on SPARQL Protocol for RDF 25 January 2006
LC
> WD
> 
> Following Jonathan's email[6], I looked at the WSDL 2.0 use made in
> SPARQL Protocol for RDF:
> 
>     SPARQL Protocol for RDF
>     W3C Working Draft 25 January 2006
>     http://www.w3.org/TR/2006/WD-rdf-sparql-protocol-20060125/
> 
> ...
> 
> - "The sequence MUST contain only local element children. These child
>   elements MAY contain the nillable attribute, and the attributes
>   minOccurs and maxOccurs MUST have a value 0 or 1."
> 
>   This one is more of a problem. Having more than one element in the
>   instance data with the same local name is something that we have
>   never allowed as we wanted to be sure we could reconstruct the
>   instance data accurately. We actually have another related
>   restriction: "The sequence MUST NOT contain multiple children
>   elements declared with the same local name."
> 
>   The problem is that if you have whttp:location="{b}" and the
>   instance data is "<a><b>2</b><b>1</b></a>", we do not know which b
>   element we are talking about. This is a limitation of our syntax.
> 
>   So they actually can't do that. The problem comes from the
>   maxOccurs="unbounded" of the default-graph-uri and named-graph-uri
>   attributes.
> 
>   It turns out that their use does not have the micro-syntax problem
>   as default-graph-uri and named-graph-uri will be serialized as query
>   parameters, but it is not very simple to allow IMO.
> 
>   It looks like this actually was already in their first draft and we
>   missed it in our first review. We should probably engage in a
>   discussing with the DAWG as I don't see any simple fix.
> 
> ...
> 
> Cheers,
> 
> Hugo
> 
>   1.
>
http://www.w3.org/TR/2006/WD-rdf-sparql-protocol-20060125/#query-binding
> s-http
>   2.
>
http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060106/#_http_x-www-form-
> urlencoded
>   3.
> http://www.w3.org/TR/2006/WD-rdf-sparql-protocol-20060125/#SparqlQuery
>   4.
>
http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060106/#_operation_iri_st
> yle
>   5.
>
http://www.w3.org/TR/2006/WD-rdf-sparql-protocol-20060125/#query-binding
> s-soap
>   6. http://lists.w3.org/Archives/Member/w3c-ws-desc/2006Feb/0004.html
> --
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Thursday, 16 March 2006 23:33:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:32 GMT