Re: ';' parameter in segments

Roy (et al),

Is there any URI scheme which defines the semantics of parameters, or
are they in disuse in this aspect? 

On Fri, Mar 01, 2002 at 11:49:59AM -0800, Roy T. Fielding wrote:
> > 2. Parameters are opaque to the "receiver" of an uri. For comparision,
> >   and especially for resolving uris, parameters are treated as part
> >   of the path segment.
> It depends on the resolver.  "http" treats them as opaque.
> > 3. An authority for the uri, what you call "service", is free to
> >   use parameters however it likes in matching uris to resources and
> >   vice versa. (follows from opacity)
> It depends on the resolver.  "http" treats them as opaque.
> > 4. Queries are different from parameters as:
> >    - queries on base uris do not take part in resolving references
> >      when the reference has a non-empty path.
> >    - queries can be setup by a client (HTML forms)
> It depends on the resolver.  "http" treats them as opaque.  Most HTTP
> servers separate the query information from the path before determining
> the handler for the resource identified by the host and path.
> Yes, that is one of the reasons they exist.  However, there is no global
> parameter meaning in URI space.  What that means is that each server has
> to tell the client what URI(s) to use in order to access the source, which is
> why the dav:source property exists.  Whether that URL is an added parameter
> to the dynamic URI, a separate hierarchical space on the same server, or
> a separate server altogether (as is common is staging environments) is
> completely specifiable by the resource owner's server and thus doesn't
> require any special convention in the URI syntax.

Mark Nottingham, Research Scientist
Akamai Technologies (San Mateo, CA USA)

Received on Friday, 1 March 2002 15:25:58 UTC