[public-geolocation] <none>

Andrei,
  After looking at the geolocation API spec more closely, I was hoping we could clarify the watchPosition() process. Does the 2 step flow below imply the watchPosition() first fires a 'single shot' request to get the current location, and then listens to updates?
The watchPosition() takes one, two or three arguments. When called, it must immediately return and then asynchronously start a watch process defined as the following set of steps:

 1.  Acquire a new Position<http://dev.w3.org/geo/api/spec-source.html#position> object. If successful, invoke the associated successCallback with a Position<http://dev.w3.org/geo/api/spec-source.html#position> object as an argument. If the attempt fails, and the method was invoked with a non-null errorCallback argument, this method must invoke the errorCallback with a PositionError<http://dev.w3.org/geo/api/spec-source.html#position-error> object as an argument.
 2.  Acquire a new Position<http://dev.w3.org/geo/api/spec-source.html#position> object and invoke the appropriate callback every time the implementation determines that the position of the hosting device has changed.
Thanks,
    Alec