ISSUE-36: Should the API expose location resolvers?

location resolvers

Should the API expose location resolvers?

State:
CLOSED
Product:
GeoAPI V2
Raised by:
Matt Womer
Opened on:
2009-07-20
Description:
From: http://lists.w3.org/Archives/Public/public-geolocation/2008Jun/0079.html
"locationResolvers - I feel strongly that this does not belong in the
specification. I still haven't heard a good argument as to why this
belongs. Do we see any examples of this in any other like
specifications? IMO, this should be handled behind the scenes as the
burden shouldn't on the developer to determine who the resolvers are.
And speaking as one of the possible resolvers, there is a lot more
that goes on behind the scenes than just sending an enumerated list of
Radio IDs and signal strengths"

More: http://lists.w3.org/Archives/Public/public-geolocation/2008Sep/0008.html

Potential Resolutions: http://lists.w3.org/Archives/Public/public-geolocation/2008Jun/0139.html
http://lists.w3.org/Archives/Public/public-geolocation/2008Jun/0095.html
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

No additional notes.

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 36.html,v 1.1 2017/05/30 09:54:28 carine Exp $