TPAC 2015: Suggested Agenda

Hello All,
The current meeting schedule has geolocation getting together on October 26 and 27.  We will not need the 2 full days, but we do have some items that need to be covered.  I may also be called into the Web & TV Interest Group meeting in the morning, so I am suggesting we have a little later start:

Monday, October 26:

10:30 AM - 12:30 PM:  Go over geofencing API and latest status on issue resolution.  See https://github.com/w3c/geofencing-api/issues.
12:30 - 2:00 PM:  Lunch
2:00 - 3:00 PM:  Next steps on DeviceOrientation

a)      Can it go to Last Call?

b)      Should the issues raised against the current spec be resolved?  See https://github.com/w3c/deviceorientation/issues.

c)       Future of DeviceOrientation.  Current proposal is that the API be redefined using the Generic Sensor API (https://github.com/w3c/sensors) and that DAP (Devices API Working Group) take up the work.
3:00 - 4:00 PM:  Revisit geofencing API discussion from morning if necessary.  All other business

Tuesday, October 27:

Morning (To be confirmed):  Joint meeting with Automotive Working Group
                The automotive WG is interested in discussing with the Geolocation WG on the applicability of the current Geoloc. API to the vehicular environment.  There is a thread on the automotive WG public mailing list discussing potential topics - see https://lists.w3.org/Archives/Public/public-automotive/2015Sep/0027.html.  Some potential topics are:

a.       API design style - is the Geoloc. API a good model?  {I am sure many in the web community will have strong opinions on this topic}

b.      Use of dead reckoning in the geoloc. API

c.       Any other areas of functional overlap between VehicleInterface and the Geolocation WG specs

Look forward to any feedback.

-Giri Mandyam, Geolocation WG Chair