Re: An Anchor attribute question: (Michael Mealling)
Date: Thu, 2 Jun 1994 15:54:35 +0200
Message-id: <>
Precedence: bulk
From: (Michael Mealling)
To: Multiple recipients of list <>
Subject: Re: An Anchor attribute question:
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: text/plain; charset=US-ASCII
Content-Type: text/plain; charset=US-ASCII
Mime-Version: 1.0
Mime-Version: 1.0
X-Mailer: ELM [version 2.4 PL23]
X-Mailer: ELM [version 2.4 PL23]
Daniel W. Connolly said this:
> In message <>, Michael Mealling writes:
> >After looking over the current spec and picking apart the unstated but
> >possibly implied differences between HREF and URN, I have a question:
> > 
> >CAN <A URN="value"> mean retrieve the page that has this Uniform Resource
> >Name once it has been resolved into a URL?
> Sounds reasonable.
> >Is this the intended meaning and if so can that intended meaning be changed
> >in order to accomodate URN->URL resolution?
> Could you rephrase your question in terms of example markup
> and client-server interactions?
> Off the top of my head, this seems like a resonable usage:
> 	See <A HREF=""
> 		URN="URN:EITF:rfc/822>The Format for Internet
> 		Messages</a> for more info.
> Clients that grok URNs can use the URN attribute, and other clients
> can use the ftp: address.
> This still strikes me as something of a hack, but it's a reasonable
> hack in the near term.

My example would be more like this:

See <A URN="URN:IANA:IETF:rfc/822"> The Format for Internet Messages</A>
for more information.

Then the client would take the URN and hand it off to its favorite
URC server and get back a set of URLs (how we represent a set of 
choices to the user is another question) which the user can select or
have the client select. Then the client would take the selected URL
and do it's normal operations on it.

I guess my question would be more along the lines of: is the HREF
in your example required or optional?


<HR><A HREF="">
<ADDRESS>Michael Mealling</ADDRESS>