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

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

Expand Messages
  • Jeff Bone
    Jun 15, 2004
      On Jun 14, 2004, at 5:55 PM, Neil Kandalgaonkar wrote:

      > In HTML, aren't the vast majority of URIs just provided in links?

      Yes - explicit ones. We're talking about having the servers specify
      generation rules for whole classes of valid URI, not merely passing out
      explicit lists of them.

      > Do you mean forms? Because, of course, that's a good standard for
      > transforming client data into the query section of a URI.
      >
      > 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?

      Whether it's in the query or the path is somewhat orthogonal to the
      desire to express URI generatively. The preference for having such a
      mechanism that works both with path parts and query parts is driven
      mostly by caching concerns, otherwise somewhat by a resource modeling
      philosophy that says conceptual hierarchy in the model should be
      expressed as such in URI.

      Cf., w/ caveat that this is purely my own (and early, not recently
      revisited) thoughts on this:

      http://rest.blueoxen.net/cgi-bin/wiki.pl?GenerativeNaming

      and

      http://rest.blueoxen.net/cgi-bin/wiki.pl?NamingIsntNavigating

      Also check out Mark Nottingham's related thoughts on a WSDL approach to
      this:

      http://www.mnot.net/blog/2004/04/16/generative

      and

      http://www.mnot.net/blog/2003/12/07/webdesc

      jb
    • Show all 23 messages in this topic