Cart
[Home] [By Thread] [By Date] [Recent Entries]
Uche Ogbuji <uche.ogbuji@f...> wrote:
|> Given that, I have to say that I find the XHTML 2.0 specification's
|> decisions to support href on everything (as in <li href="#fish">fish</li>)
|> and to use the familiar object element for including foreign resources to
|> be painfully sensible,
| What am I missing here? What about the loud cries of "we need more than
| one link on an element"?
|
| "href" on any element is a straight-up loser.
I agree.
The basic problem with href and src is that they are not *links* at all.
They are locators, with a conflated actuation semantic ('href' implying
"replace", 'src' implying "embed".)
We may also note that bog-standard HTML *already* has one form of multiway
linkage: the <MAP> element. It so happens to be usable presently with
only one element type, <img>, but it still qualifies as a reasonable basis
for generalization, because the <MAP> element expresses the insight that
multiway linking needs independent structured description. So, if href
and src are to be retained for their locator+actuation function, it makes
sense to have a container element to aggregate them, and to attach the
aggregate to other elements by normal intra-document reference mechanisms.
|
