Le mar 03/08/2004 � 16:04, NESTING, DAVID M (SBCSI) a �crit : > In a future revision it might also be helpful to see a note disambiguating the > definition of "resource" between the HTTP and URI RFCs, as the latter suggests the > query string operates *on* the resource while in HTTP, the query string (also?) > helps *identify* the resource.
FWIW, the on-going revision of the URI RFC (2396) does indeed incorporate this change: http://gbiv.com/protocols/uri/rev-2002/rfc2396bis.html#query reads "The query component contains non-hierarchical data that, along with data in the path component, serves to identify a resource within the scope of the URI's scheme and naming authority (if any)." Dom -- Dominique Haza�l-Massieux - http://www.w3.org/People/Dom/ W3C/ERCIM mailto:[EMAIL PROTECTED]
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e=2E?=
