Re: [Geopriv] "A Uniform Resource Identifier for Geographic Locations ('geo' URI)"
Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Sun, 25 February 2007 12:59 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLIyJ-0006hy-6e; Sun, 25 Feb 2007 07:59:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLIyI-0006eB-00 for geopriv@ietf.org; Sun, 25 Feb 2007 07:59:22 -0500
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HLIyF-0003kH-Hd for geopriv@ietf.org; Sun, 25 Feb 2007 07:59:21 -0500
Received: (qmail invoked by alias); 25 Feb 2007 12:59:12 -0000
X-Provags-ID: V01U2FsdGVkX18QAwYUf+YQJxOgaJCuEY837djFs7qz3AaH8Lu+3v MAJg==
Message-ID: <45E1881E.30102@gmx.net>
Date: Sun, 25 Feb 2007 13:59:10 +0100
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0b2 (Windows/20070116)
MIME-Version: 1.0
To: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
Subject: Re: [Geopriv] "A Uniform Resource Identifier for Geographic Locations ('geo' URI)"
References: <510638DF-0976-4CAE-B0E7-50914AA53214@cs.columbia.edu> <45E06DB0.5040401@gmx.net> <45E1728C.7010105@enum.at>
In-Reply-To: <45E1728C.7010105@enum.at>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: GEOPRIV <geopriv@ietf.org>, Christian Spanring <cspanring@gmail.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
Errors-To: geopriv-bounces@ietf.org
Hi Alex, in an abstract sense you either carry location information within a protocol or you annotate some data items with it. The encoding is another story that I leave aside. Now, when you carry location information between different end points you need to indicate what the semantics are. As an example might want to take a look at the SIP Location Conveyance draft, available at http://tools.ietf.org/id/draft-ietf-sip-location-conveyance-07.txt It, for example, describes * what happens if the receiver expects location information but does not get it * what happens if the receiver receives location information it does not understand (but is supposed to) * what the privacy and security implications are * to which entity the location information refers * who is supposed to process what and when If you add location information to a data model then you need to worry about things like * in which context is the data model used * privacy implications * protocols that shuffle around with the instance documents ('using protocols') Examples can be found with http://www.potaroo.net/ietf/all-ids/draft-daviel-html-geo-tag-05.txt and RFC 4119 Your document currently focuses on the encoding but omits the rest. Ciao Hannes Alexander Mayrhofer wrote: > Hannes Tschofenig wrote: > >> Section 6.2. reads a slightly different version of the not yet >> finished attempt to standardize >> http://www.potaroo.net/ietf/all-ids/draft-daviel-html-geo-tag-05.txt >> and Section 6.3 sounds like an incomplete SIP Location Conveyance >> approach. >> >> The argument of the document that existing mechanisms "don't provide a >> generic way to protocol independent location identification." seems >> pretty dubious given that the URI definition alone does not provide >> enough semantic (unless you read all the way through Section 6 where >> the semantic is hinted based on examples). >> > > Hannes, > > thanks for reading through it - i'd like to point out that this is a > first version of the draft, and of course we're happy about any > feedback. Our goal is now to find out whether this approach is > considered useful. > > Could you elaborate on why you think the URI definition does not provide > enough semantic information? Is it for a specific use case, or are you > unsure that the URI itself does not provide enough information for > identifying a certain location? > > thanks, > > Alex > _______________________________________________ Geopriv mailing list Geopriv@ietf.org https://www1.ietf.org/mailman/listinfo/geopriv
- [Geopriv] "A Uniform Resource Identifier for Geog… Henning Schulzrinne
- Re: [Geopriv] "A Uniform Resource Identifier for … Hannes Tschofenig
- Re: [Geopriv] "A Uniform Resource Identifier for … Hannes Tschofenig