Lists Home |
Date Index |
- From: "Simon St.Laurent" <firstname.lastname@example.org>
- To: Paul Prescod <email@example.com>, firstname.lastname@example.org
- Date: Mon, 17 May 1999 09:04:46 -0400
At 04:36 AM 5/17/99 -0500, Paul Prescod wrote:
>> I figured BEHAVIOR would be an ordinary attribute - say, "popup" instead of
>> "popup()", which the style sheet or other app-specific gizmo then converts
>> to "popup()" as appropriate, knowing what the context was supposed to be.
>> Sort of like a selector for CSS Action Sheets, if they get off the ground.
>You probably know this already but: you can use any attribute as a
>selector. And if you use your own attribute name then you can namespace it
>to avoid accidental name/semantic clashes.
Er... yes... but isn't XLink about providing a list of attributes we can
use reliably with _any_ set of documents to build hypertexts? I _could_
create my own 'behavior'-like attribute, but knowing that everyone has
access to the same behavior attribute at least provides me with the ability
to perform selection on any XLink-conformant spec. I may not know what
they mean, but at least I can test it and find out.
I'm starting to wonder if it isn't time to wait and see what the next
(supposedly soon) draft says. As John Simpson said, this is up there with
entrail-interpretation. Not being an ancient Roman priest, I'm not very
good at that.
XML: A Primer / Building XML Applications (June)
Sharing Bandwidth / Cookies
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)