- From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
- Date: Thu, 4 Jun 2009 17:07:20 +0200
- To: Doug Turner <doug.turner@gmail.com>, Max Froumentin <maxfro@opera.com>
- CC: Andrei Popescu <andreip@google.com>, public-geolocation <public-geolocation@w3.org>
+1 to drop it Marcin Hanclik ACCESS Systems Germany GmbH Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465 Mobile: +49-163-8290-646 E-Mail: marcin.hanclik@access-company.com -----Original Message----- From: public-geolocation-request@w3.org [mailto:public-geolocation-request@w3.org] On Behalf Of Doug Turner Sent: Thursday, June 04, 2009 4:54 PM To: Max Froumentin Cc: Andrei Popescu; public-geolocation Subject: Re: updated editor's draft of the Geolocation API specification On Jun 4, 2009, at 9:46 AM, Max Froumentin wrote: > Hi Andrei, > > On 4. juni. 2009, at 12.49, Andrei Popescu wrote: >> I've just updated the editor drafts of the Geolocation API spec: > > I notice that RFC2119 is not in the bibliography, even though > there's a link to it in the spec. > >> I'd like to take the opportunity to remind you to consider the >> question in the following email: >> >> http://lists.w3.org/Archives/Public/public-geolocation/2009Jun/0000.html >> >> and express your opinion. I would like to close this issue asap and >> move the spec to the next stage. We are already behind schedule. > > For what it's worth, I am in also favour of not including the > additional sentence. For the reasons you mention, but also because > prose of the form "this specification doesn't mandate a way to... > however one way might be...", although not strictly contradictory, > very often leads to confusion. Secondly, the particular time-scoping > solution mentioned suggests awkward user interaction, and might > influence implementers the wrong way. +1 drop this from the spec. Doug ________________________________________ Access Systems Germany GmbH Essener Strasse 5 | D-46047 Oberhausen HRB 13548 Amtsgericht Duisburg Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda www.access-company.com CONFIDENTIALITY NOTICE This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited. If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.
Received on Thursday, 4 June 2009 15:08:30 UTC