Re: VRML Geolocation request

Jan Hardenbergh ([email protected])
Wed, 12 Apr 95 23:49:00 E

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: [email protected]: "(no subject)"
Previous message: Brygg Ullmer: "Re: VRML Geolocation request"
Maybe in reply to: Jim Terhorst: "VRML Geolocation request"
Next in thread: Chris Hand: "Re: VRML Geolocation request"

> On Wed, 12 Apr 1995, Chris Hand wrote:
> > > all you folks building VRML pages. What i need is:
> > > 1) the URL for your site
> > > 2) The approximate latitude and longitude of the physical
> > > location of your site
> >
> > It would be a trivial extension to the protocol to do this automatically
> > (something I often wished was included in HTTP)... the server gives out
> > its long/lat on request.
> >
> > Then you can make these maps automatically.
>
> There's an HTTP extensions mechanism proposal at
>
<URL:http://www.ics.uci.edu/pub/ietf/http/draft-kristol-http-extensions-00.t
xt>
> >
> This is seen as preferable to adding "X-" headers when one wishes to
> extend the capabilities of HTTP - it also gives the browser and server
> the power to negotiate based on capabilities. (i.e. "Can you do this?"
> "No, I can't" "Then I won't waste time and bandwidth sending you this
> info.")
>
> But I suppose for the time being there's nothing wrong with encoding it
> as X-Geolocation: 118 24 34 21 34 43 or something, while we're
> experimenting. I think at this point one should look at Mark Pesce's CP
> proposal, at <URL:http://hyperreal.com/~mpesce/www.html>.

We could also do this by convention - either establish a relative URL
latlong.txt
or putting META data in the specified URL.

http://info.cern.ch/hypertext/WWW/MarkUp/html-spec/L2Pindex.html#META