- From: Henning Schulzrinne <hgs@cs.columbia.edu>
- Date: Tue, 3 Mar 2009 10:23:20 -0500
- To: Andrei Popescu <andreip@google.com>
- Cc: Richard Barnes <rbarnes@bbn.com>, Alec Berntson <alecb@windows.microsoft.com>, "public-geolocation@w3.org" <public-geolocation@w3.org>
Please prove that the existing format is "hard to understand". The format is the result of long and considered deliberations; all you have offered is assertions. This "simple format" will actually make coding *harder* since applications now have to try to guess what parts of the mangled address are what semantic piece, picking apart text strings by commas and semicolons and dealing with exception cases. I thought the general idea of the semantic web was to move to better tagging, not more random bags of bits? Henning On Mar 3, 2009, at 10:10 AM, Andrei Popescu wrote: > > I understand this goal. However, I feel that this isn't as important > for our spec as providing a format that is easy to understand and code > against. As I mentioned in the email to Marc, we could provide an > appendix that shows how to convert to / from the IETF format. This > would be as a convenience to those Geolocation API implementers who > may have to deal with the IETF format as an input (or an output for > those specific usecases you mentioned). The users of the Geolocation > API should be offered something simpler. >
Received on Tuesday, 3 March 2009 15:23:59 UTC