[Geopriv] slides for daviel-HTML/HTTP drafts
Andrew Daviel <advax@triumf.ca> Mon, 10 December 2007 20:59 UTC
Return-path: <geopriv-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J1pjJ-0001mk-BM; Mon, 10 Dec 2007 15:59:57 -0500
Received: from geopriv by megatron.ietf.org with local (Exim 4.43) id 1J1pjI-0001mf-LF for geopriv-confirm+ok@megatron.ietf.org; Mon, 10 Dec 2007 15:59:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J1pjI-0001mX-B2 for geopriv@ietf.org; Mon, 10 Dec 2007 15:59:56 -0500
Received: from andrew.triumf.ca ([142.90.106.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J1pjG-00042Y-Bz for geopriv@ietf.org; Mon, 10 Dec 2007 15:59:56 -0500
Received: from localhost (localhost [127.0.0.1]) by andrew.triumf.ca (8.12.11.20060308/8.12.11) with ESMTP id lBAKxreO006099 for <geopriv@ietf.org>; Mon, 10 Dec 2007 12:59:53 -0800
Date: Mon, 10 Dec 2007 12:59:53 -0800
From: Andrew Daviel <advax@triumf.ca>
X-X-Sender: andrew@andrew.triumf.ca
To: geopriv@ietf.org
Message-ID: <Pine.LNX.4.64.0712101219400.2787@andrew.triumf.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Subject: [Geopriv] slides for daviel-HTML/HTTP drafts
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
Hannes suggested I do a brief presentation to the WG on Friday in Vancouver, but there wasn't time. Robert Sparks said as I'd put something together I might as well send it to the list. So here it is: http://geotags.com/geo/ietf70.pdf The robot at geotags.com was offline for an extended period but is running again. Currently using a modified HtDig with a Google map API replacing the somewhat braindead worldmap interface. Only geo.position and geo.region (= country + A1) from the previous drafts are indexed. The HTTP slide shows one potential implementation of the HTTP draft; I could put this together (working) today with a cellphone, GPS and laptop, but potentially it could be less devices (Nokia E810 plus cellphone using Bluetooth, or a single GPS-and-Web-enabled mobile device). For GPS read "any source of positioning data", e.g. a location server. The standard browser and local proxy can be replaced by a modified browser or one with a custom add-on. One of the authors has done this with mobile IE. The slide with drivebc.ca is just an example of a local traffic site with realtime road reports and cameras, that would be useful if it automatically centered on the driver's location. A couple of questions were raised about the HTML draft, viz. adding a LANG element (it was in an earlier draft), and allowing a by-reference element. Re. LANG, as the draft refers to legacy HTML documents, the charset and language of the metadata is by default that of the enclosing document, charset as defined in the HTTP response (or http-equiv tag) and language as defined in the <html> element. If authors bother. If it was desired to change the default on a per element basis, to add an alternate for e.g. LMK or A1-6, then as per W3C spec a LANG element could be added to META <meta name="geo.a3" lang="en" content="Munich"\> <meta name="geo.a3" lang="de" content="Munchen"\> <meta name="geo.a3" lang="it" content="Monaco"\> etc. This could be explicitly stated in the HTML draft. I dropped it because I thought it was adding more confusion. Re. reference, it would be possible to add a link element to a full PIDF XML document, as is currently done for stylesheets in HTML. I'm a bit reluctant to do this, because it opens up a can of worms about one Web document being an authoritative source of information for another, which might possibly be on another server or maintained by a different person. Also, historically this kind of linked document has not been well maintained - stylesheets often go missing, which a few years ago caused Netscape 4 to fail. Other browsers are more forgiving. refs. http://tools.ietf.org/html//draft-daviel-html-geo-tag-08 http://tools.ietf.org/html/draft-daviel-http-geo-header-05 -- Andrew Daviel, TRIUMF, Canada _______________________________________________ Geopriv mailing list Geopriv@ietf.org https://www1.ietf.org/mailman/listinfo/geopriv
- [Geopriv] slides for daviel-HTML/HTTP drafts Andrew Daviel