Re: [xml-dev] Re: Can XLink be fixed?
by Tim Bray other posts by this author
Aug 15 2002 8:22PM messages near this date
Re: [xml-dev] Re: Can XLink be fixed?
|
Re: [xml-dev] Re: Can XLink be fixed?
Simon St.Laurent wrote:
> >Having said that, I think that certain HTML idioms, such as
> >
> ><img src="URL of picture" alt="local text" longdesc="URL of text">
> >
> >are really bad markup design and aren't worth grandfathering. Why
> >bad? Suppose you want to have descriptions (long or short) in more
> >than one language, and suppose you want to provide multiple sizes of
> >the picture, etc;
>
> The URI people keep telling me that's a job for content-negotiation,
Perhaps, but content-negotiation is kind of a blunt instrument and isn't
going to help you with for example different picture resolutions or
expert-vs-introductory level material or a lot of other things.
I think that if for any X, you want to use markup to represent it, then
if you're really sure there's only going to be one of them, attributes
are OK, but if there's a chance there's going to be more than one, then
elements are the way to go. This is one of the motivators for the
design of the complex XLink.
> I guess
> there's a good question about whether the longdesc resource is just a
> representation of the same resource identified by the src attribute...
> How deep do you really want to go with this?
Without going very deep, the current way IMG is done just feels like bad
markup design for a bunch of fairly obvious reasons.
> >in fact, while you can argue about the appropriate
> >uses of elements and attributes almost forever, this is a good
> >example of how not to use attributes.
>
> > I dunno about that, unless maybe we want to get into requiring all
> URI-containing values to be child elements rather than elements. I
> don't see any reason that src and longdesc don't both qualify as
> metadata about the img element, though I'm sure I could come up with
> something vaguely plausible.
I've never found it very helpful to agonize over what's metadata and
what isn't. I think there are simpler decision procedures: want
white-space normalization? Use an attribute. Possibly multiple
occurrences? Use an element. I don't think whether or not it might be
a URI is part of the argument. -Tim
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>
Thread:
Rick Jelliffe
Henry S. Thompson
Norman Walsh
Norman Walsh
Paul Prescod
Simon St.Laurent
Norman Walsh
Simon St.Laurent
Robin Berjon
=?iso-8859-1?Q?Bill_de_h=D3ra?=
Simon St.Laurent
Paul Prescod
Simon St.Laurent
Robin Berjon
Simon St.Laurent
Simon St.Laurent
Norman Walsh
Simon St.Laurent
Norman Walsh
Simon St.Laurent
Simon St.Laurent
Simon St.Laurent
J. David Eisenberg
Norman Walsh
J. David Eisenberg
Robin Berjon
Norman Walsh
Simon St.Laurent
Norman Walsh
Simon St.Laurent
Simon St.Laurent
Simon St.Laurent
Simon St.Laurent
Shane McCarron
Simon St.Laurent
Joe English
Norman Walsh
Simon St.Laurent
Keith W. Boone
Arjun Ray
Arjun Ray
Rick Jelliffe
Simon St.Laurent
Simon St.Laurent
Tim Bray
Simon St.Laurent
Tim Bray
Simon St.Laurent
Elliotte Rusty Harold
Simon St.Laurent
Lars Marius Garshol
Bob DuCharme
Elliotte Rusty Harold
Didier PH Martin
Elliotte Rusty Harold
Simon St.Laurent
Elliotte Rusty Harold
Norman Walsh
Tim Bray
Simon St.Laurent
Tim Bray
Simon St.Laurent
Simon St.Laurent
Simon St.Laurent
Ann Navarro
Simon St.Laurent
Elliotte Rusty Harold
Simon St.Laurent
Simon St.Laurent
Elliotte Rusty Harold
Simon St.Laurent
John Cowan
Rick Jelliffe
Simon St.Laurent
John Cowan
Simon St.Laurent
John Cowan
Simon St.Laurent
Mike Champion
Didier PH Martin
John Cowan
Mike Champion
Simon St.Laurent
Norman Walsh
Tim Bray
Simon St.Laurent
Rick Jelliffe
Norman Walsh
Masayasu Ishikawa
John Cowan
Jeff Rafter
|