W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > June 2004


From: Mark Baker <distobj@acm.org>
Date: Wed, 16 Jun 2004 14:09:01 -0400
To: public-rdf-dawg-comments@w3.org
Message-ID: <20040616180901.GA669@markbaker.ca>


I like the UC&R document very much, however I think it's missing a very
important requirement; forms.

Requirement 3.8, if accepted, will permit a query to be encoded into a
URI, which is terrific.  But what's needed in addition to this, I
believe, is a means to a) associate the encoded query with a "base URI",
and b) specify the URI encoding.  This will permit a whole URI to be
constructed upon which GET can be invoked.  For example, in my work on
RDF Forms[1], this would suffice;

<Indexable rdf:about="uri" rf:queryType="application/x-dawg-query-uri"/>

(where rf:queryType is something I've been thinking about, but hasn't
yet made it into the spec)

So I'd like to see a new requirement, something like this;

] 3.8.1 Declare queryable resources
] A means must be provided for a resource to be declared as queryable,
] and accepting of a particular encoding of a query, so that the client
] will have all the information it needs to construct the full URI

Forms have broader scope than simply GETtable URIs of course; for
example, POST or PUT based state transitions can also be declared with
one (see "Container" in RDF Forms, which is used for POST).  But I don't
know if that part of forms would fall under the charter of DAWG.

FWIW, it seems to me that a separate forms deliverable would be
desirable, as it seems quite separable from the protocol and query


 [1] http://www.markbaker.ca/2003/05/RDF-Forms/

Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Received on Wednesday, 16 June 2004 14:08:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:05 UTC