Not sure how this is going to help. You still end up with an HTTP URI with no clear semantic meaning other than an HTTP resource.
EHL
> -----Original Message-----
> From: John Cowan [mailto:
cowan@...]
> Sent: Thursday, June 25, 2009 6:03 PM
> To: Eran Hammer-Lahav
> Cc: Xiaoshu Wang;
apps-discuss@...;
www-tag@...; URI
> Subject: Re: URI for abstract concepts (domain, host, origin, site,
> etc.)
>
> Eran Hammer-Lahav scripsit:
>
> > Without passing judgment on your proposal, it is clearly not
> something
> > that can be accomplished within a short time frame. I have a very
> > specific need to indicate a document describes "a host" which is a
> > combination of domain, port, and potentially protocol. I just need to
> > say it formatted as a URI.
>
> A simple approach would be to use a data: URI (see RFC 2397) of the
> form
> "data:application/uri,
http://www.ccil.org". I proposed this for a
> related
> purpose during the Great XML Namespace Debate, but it didn't get
> traction.
>
> --
> Your worships will perhaps be thinking John Cowan
> that it is an easy thing to blow up a dog?
>
http://www.ccil.org/~cowan> [Or] to write a book?
> --Don Quixote, Introduction
cowan@...
