Re: unify ancient attributes

BB> Well, I don't see similarity between @src and @href at least.
BB> @src = URI of resource to load and embed in the page (in place of owner element)
BB> @href = URI of resource that can be navigated to (for hyperlinks).

Wikipedia asserts,
that term 'hyperonim' means abstract general thing,
and term 'hyponim' means particular case of hyperonim
(don't mess up with 'holomin-meronin',
they are whole thing and physical part of thing accordingly).

In this terms,
'URI of resource' is hyperonim,
'to load and embed' and 'can be navigated' are hyponim.

If html-element has no _both_ hyponims simultaneously,
there is no any sense to distinguish hyponim in tag -
hyperonim specification is enough.

---

BB> Things like <caption> and <legend> do seem redundant.

Irony of fate:
i send new topic '<caption>=<legend>', just when i downloaded your letter :)

AS> I fear that his change would not be backwards compatible

New spec can allow both variant of names (old and new),
and can _recommend_ new variant.
This way mentioned in many documents of w3.org.

MC> You know this is gonna start another argument about backwards compatibility
MC> with SRC and current AT not supporting it right? You should probably pick
MC> another name in advance.

Excuse me, what is abbreviation 'AT' mean ?
And i don't understand cue, re-phrase, please.

RB> You seem to be posting from June 28th. If so, go long on Apple
RB> stock. :-). But seriously, you might want to check you system date.

I'm capable to connect to inet per 3 days (in average).
Mentioned event means, that i miss one session.

But this has one advantage: i have time to think.


Dmitry Turin
HTML6     (6.1.0)  http://html60.chat.ru
SQL4      (4.1.0)  http://sql40.chat.ru
Computer2 (2.0.3)  http://computer20.chat.ru

Received on Wednesday, 11 July 2007 13:31:03 UTC