ecrit@ietf.org
[Top] [All Lists]

Re: [Ecrit] [Fwd: Re: [Uri-review] IETF ECRIT Working Group: LoST URISch

Subject: Re: [Ecrit] [Fwd: Re: [Uri-review] IETF ECRIT Working Group: LoST URIScheme --- Review Needed]
From: Henning Schulzrinne
Date: Sat, 3 Feb 2007 15:06:13 -0500
I share Brian's concern; this seems like a real stretch. If all you want to do is retrieve a boundary polygon, a plain HTTP request, with appropriate XML content type, seems much easier to implement, for all parties concerned.

Previously, we had numerous instances where features were deferred since there was no immediate need based on our charter and requirements documents. Now, we suddenly, at the last minute, invent new requirements that are fanciful at best.

Henning

On Feb 2, 2007, at 4:01 PM, Brian Rosen wrote:

Again, why would you imagine a browser being built that would have that behavior? This is very bizarre behavior at that, specifically knowing that this "sbref" parameter means invoke LoST, and if you get a URI, render some
kind of positive indicator.  Where is the specification for that? Why
wouldn't you use some form of "href=urn:service.pizza.pizza-hut/ someparam"
for that if you define that kind of behavior in some future spec?

I don't think LoST is the kind of protocol that gets put in a URI.

Brian

-----Original Message-----
From: Andrew Newton [mailto:andy@xxxxxx]
Sent: Friday, February 02, 2007 3:47 PM
To: Ted Hardie
Cc: ECRIT
Subject: Re: [Ecrit] [Fwd: Re: [Uri-review] IETF ECRIT Working Group: LoST
URIScheme --- Review Needed]


On Feb 2, 2007, at 3:13 PM, Ted Hardie wrote:
To make it work, I have to
combine the two with something like:

<html><head><title>Advice</title><head>
<body>
If you are thinking of hurting yourself, <a href="lost://
referringserver.example.com/
parameter=urn:service:counselling.suicide"> GET HELP</a>!  Don't
try to get through
it alone!<p>
</body>
</html>

"Parameter" needs a better name, obviously, but you get the idea.
With that
functionality, there is enough there to give the teen a referral to
an appropriate
counselling service.

I also thought up the case where a LoST URL could point to a specific
service boundary reference.  Put into a web page, it could allow
Pizza Hut to express their service area:

<a href="lost://pizzahut.example/sbref=UUID">Click here to see if you
are in our service area</a>

-andy

_______________________________________________
Ecrit mailing list
Ecrit@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ecrit


_______________________________________________
Ecrit mailing list
Ecrit@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ecrit


_______________________________________________
Ecrit mailing list
Ecrit@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ecrit

<Prev in Thread] Current Thread [Next in Thread>