Re: unify ancient attributes

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

@action seems similar as @href, but I'm not sure. Even XForms still
uses @action:

@data I haven't used enough to have an opinion on.

I do like the underlying concept though, that we have one language
construct for doing a particular thing. Things like <caption> and
<legend> do seem redundant. But then there is the whole overloading
argument Karl summarised:
I assume it applies to attributes just as much as elements.

On 7/6/07, Maurice Carey <> wrote:
> On 6/28/07 4:23 AM, "Dmitry Turin" <> wrote:
> > Good day.
> >
> > Attributes SRC, ACTION, DATA, HREF have sense as address, i.e. designate the
> > same.
> > So i offer to use single name (for example, SRC) in all cases,
> > and abolish names HREF, ACTION, DATA.
> > To replace whole tag by a file (<img src= >)
> > or to inform, where to take a file (<a href= >), depends of tag (instead of
> > attribute).
> I absolutely love this idea. I was teaching basic html to someone years ago
> and they essentially said the same thing.
> Lol, I'll always remember him saying "html gets the job done, yeah, but when
> you're writing it, if you think about it, it's really kind of stupid."
> You know this is gonna start another argument about backwards compatibility
> with SRC and current AT not supporting it right? You should probably pick
> another name in advance.
> --
> ::   thyme online ltd
> ::   po box cb13650  nassau  the bahamas
> ::   website:
> ::   tel: 242 327-1864  fax: 242 377 1038

Received on Thursday, 5 July 2007 15:24:40 UTC