----------------------------------------+-----------------------------------
Reporter: alexander.mayrhofer@nic.at | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: geo-uri | Version:
Severity: Active WG Document | Keywords:
----------------------------------------+-----------------------------------
Currently, the draft says that query strings should be ignored by a client
application, and they are not specified in the ABNF. Comments from the URI
review list indicated that this should be changed.
The options are as follows:
a) keep the text as currently in the draft (not specified in the ABNF, but
recommends clients to ignore if given)
b) remove the offending text
c) add query strings to the ABNF
Note that adding query strings to the ABNF would create a huge area of
interesting things to consider, like encoding, structure of parameters,
etc.
Also, semantically it is very unclear how a query string would be applied
to the resource - since the resource is a geographic location, it would be
hard to figure how one would apply those query strings to the location
that is referred to in the URI.
The recommendation by the Author is therefore to go for b)
--
Ticket URL: <http://trac.tools.ietf.org/wg/geopriv/trac/ticket/12>
geopriv <http://tools.ietf.org/geopriv/>
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
