Loading ...
Sorry, an error occurred while loading the content.

4465Re: [rest-discuss] Client-composed URI paths

Expand Messages
  • Mark Baker
    Jun 14, 2004
      On Mon, Jun 14, 2004 at 09:10:56PM -0700, S. Mike Dierken wrote:
      > > So I think the question is: do we need another standard for clients
      > > to transform user data into the *path* section? In a way customized
      > > to each REST application?
      > >
      > > My first guess is no, but I'd like to hear potential uses first. Why
      > > would you want to compose such a URI path? Why *wouldn't* you want to
      > > do the same thing with a URI query?
      > I'd like a general mechanism for constructing a request - regardless of URI
      > path, URI query terms, request headers, etc. I'd settle for complete access
      > to the request method and the URI.

      RDF Forms is intended to be such a mechanism ... or at least it will be
      once I finish everything in the todo list. As is, it just tries to do
      what HTML forms can do.


      Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
    • Show all 23 messages in this topic