[
Lists Home |
Date Index |
Thread Index
]
Well looking things over I think I was wrong about the spec, my
understanding for the last couple years has been very molded by
"Universal Resource Identifiers - Axioms of Web Architecture",
http://www.w3.org/DesignIssues/Axioms.html , the part which I felt was
relevant here was from
http://www.w3.org/DesignIssues/Axioms.html#query
to quote:
"An important case is the treatment of the question mark in HTML
forms. There is a convention that infformation returned from HTML
forms is returned by encoding it and appending it to the URI. The
question mark within the URI is used to separate the basic URI from
parameters which are appended to it to perform an operation. A typical
use is for a search, and the string following the question mark is
often known as a query string.
When a query string and fragment identifier are used, the function
evaluated on dereferencing a URL
http://foo/bar?baz#frag
Is
select(get( "foo", "query("bar","baz")), "frag")
where
* query (resource, querystring) is evaluated by the resource "bar"
* "bar" is opaque to all except the server "foo" ;
* "baz" is a format understood by client and by the resource "foo/bar";
* get(server, restofuri) is executed by the client engine which
understands "foo" but not "bar"
* select(fragmentid, resource) is evaluated on the client by the
resource's handling code
"
That is to say that the resource and the querystring are two things
that are seperate from each other, the two parameters of the function
query - of which one parameter, querystring is optional.
We can have a resource without a querystring.
Don't really feel that we can have a querystring without a resource,
unless we do some clever argumentation removed from the facts on the
ground.
Cheers,
Bryan Rasmussen
On 12/9/05, Jim Ancona <jim@anconafamily.com> wrote:
> bryan rasmussen wrote:
> > The querystring, despite sometimes usage, is not according to
> > specification for referring to different resources.
> >
> > This http://www.location.org/US/MA?city=Boston
> >
> > refers to US/MA
> >
> > city=Boston is a property of US/MA.
>
> What in the specification causes you to say that? According to RFC 3986,
> Section 3.4:
>
> The query component contains non-hierarchical data that, along with
> data in the path component (Section 3.3), serves to identify a
> resource within the scope of the URI's scheme and naming authority
> (if any).[1]
>
> I read that as saying that the query part participates in identifying a
> resource just as much as the path does.
>
> Perhaps you were thinking of the fragment identifier (the part after the
> '#')? Section 3.5 of the spec says:
>
> The fragment identifier component of a URI allows indirect
> identification of a secondary resource by reference to a primary
> resource and additional identifying information. The identified
> secondary resource may be some portion or subset of the primary
> resource, some view on representations of the primary resource, or
> some other resource defined or described by those representations.
>
> To me, that sounds closer to what you were saying.
>
> Jim
>
> [1] - http://www.ietf.org/rfc/rfc3986.txt
>
|
