Re: [Geopriv] HELD, Re: [Fwd: Minneapolis IETF Code Sprint]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Geopriv] HELD, Re: [Fwd: Minneapolis IETF Code Sprint]



Hi Julian, 

Thanks for reading the text on the webpage. I almost got the impression
that you would join us next time. 

The current implementations are based on previous versions of the HELD
draft (with respect to the URI scheme issue) and use the http: and
https: reference. We will update the code once the discussion around
this issue got finalized. 

With LoST (which also runs on top of HTTP) we luckily do not have this
URI scheme issue.

Ciao
Hannes

>-----Original Message-----
>From: geopriv-bounces at ietf.org 
>[mailto:geopriv-bounces at ietf.org] On Behalf Of ext Julian Reschke
>Sent: 24 August, 2008 19:18
>To: Hannes Tschofenig
>Cc: GEOPRIV
>Subject: [Geopriv] HELD, Re: [Fwd: Minneapolis IETF Code Sprint]
>
>Hannes Tschofenig wrote:
>> Another chance to get together and todo interop testing with GEOPRIV 
>> and ECRIT protocols.
>> 
>> Are there some new folks interested in joining?
>> 
>> Ciao
>> Hannes
>> 
>> PS: Information about our IETF#72 activities can be found here: 
>> http://geopriv.googlepages.com/
>> ...
>
>Ah, very interesting.
>
>Under "LIS Demonstration Page" I read:
>
>"The LIS includes an AJAX application that displays the 
>current position of the requestor of the page and give them an 
>opportunity to update access point locations based on where 
>they are.  JavaScript code in the demonstration page directs 
>the client's browser to send a HELD query to the LIS (asking 
>for civic location).  This request returns the user's location 
>as a PIDF-LO, and makes it available as a JavaScript DOM 
>object.  The browser pulls civic address information from this 
>structure and plots it on a map of the IETF venue.
>
>Also, since the LIS is manually provisioned (by users 
>providing AP locations), the demo page offers users an 
>interface for users to specify their location when location 
>information is missing or incorrect."
>
>The diagram below shows that the Web Server on the LIS uses 
>XMLHttpRequest to perform the HELD request.
>
>I'd like to understand how the syntax shown in the HELD examples in
><http://tools.ietf.org/html/draft-ietf-geopriv-http-location-de
>livery-08#section-11.1>:
>
>          GET heldrefs://lis.example.com:49152/location HTTP/1.1
>          Accept:application/held+xml,
>              application/xml;q=0.8,
>              text/xml;q=0.7
>          Accept-Charset: UTF-8,*
>
>can actually be used with XMLHttpRequest. It seems to me that 
>this requires that XmlHttpRequest somehow magically 
>understands the "heldrefs" URI scheme. How does that work?
>
>Best regards, Julian
>
>_______________________________________________
>Geopriv mailing list
>Geopriv at ietf.org
>https://www.ietf.org/mailman/listinfo/geopriv
>
_______________________________________________
Geopriv mailing list
Geopriv at ietf.org
https://www.ietf.org/mailman/listinfo/geopriv



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.