- From: Marcos Caceres <marcosc@opera.com>
- Date: Tue, 03 Aug 2010 10:05:50 +0200
- To: Dominique Hazael-Massieux <dom@w3.org>
- CC: public-geolocation <public-geolocation@w3.org>, Robin Berjon <robin@berjon.com>, Hari Kumar G <harig@opera.com>, "frederick.hirsch" <frederick.hirsch@nokia.com>
On 8/3/10 9:25 AM, Dominique Hazael-Massieux wrote: > (adding Frederick Hirsch, editor of the document referenced below) > > Le mardi 03 août 2010 à 07:34 +0200, Marcos Caceres a écrit : >> In the widgets space, we are starting to see fragmentation wrt the >> feature string UA's use to enable geolocation. >> >> My personal opinion is to use a simple and version-less namespace, like >> the ones currently used for XML namespaces: >> http://www.w3.org/ns/geolocation-api > > FWIW, the Device APIs and Policy Working Group has started a couple > weeks ago to draft a document where device APIs (incl. geolocation) > features get defined: > http://dev.w3.org/2009/dap/features/ > > The proposed resulting URI for geolocation based on the current draft > would be http://www.w3.org/ns/apis/geolocation (but that's obviously a > strawman proposal). I'm of the preference that each API spec should define its own feature string. Otherwise, the DAP features spec will never reach REC. Having the DAP feature doc define the rules for constructing the URIs is very useful, however. -- Marcos Caceres Opera Software
Received on Tuesday, 3 August 2010 08:06:39 UTC