Re: An Anchor attribute question:
"Daniel W. Connolly" <connolly@hal.com>
Errors-To: listmaster@www0.cern.ch
Date: Thu, 2 Jun 1994 16:05:33 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <9406021402.AA17122@ulua.hal.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: connolly@hal.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: "Daniel W. Connolly" <connolly@hal.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
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
In message <199406021352.AA15799@oit.gatech.edu>, Michael Mealling writes:
>
>My example would be more like this:
>
>See <A URN="URN:IANA:IETF:rfc/822"> The Format for Internet Messages</A>
>for more information.
>
>
>I guess my question would be more along the lines of: is the HREF
>in your example required or optional?
According to the DTD, HREF is optional -- mostly because there's
no way to express in SGML the sentiment "either the NAME attribute
or the HREF attribute must be present."
>From the HTML spec:
http://info.cern.ch/hypertext/WWW/MarkUp/Elements/A.html
All attributes are optional, although one of NAME and HREF is necessary
for the anchor to be useful.
It's reasonable to change that to say:
All attributes are optional, although one of NAME, HREF, or URN is necessary
for the anchor to be useful.
Whereas in the near term, an A tag with a URN attribute
but no HREF attribute is useless to most of the community,
I suggest that you use the URN for the lasting name, but for the
benefit of existing clients, you include a redundant
HREF.
Dan