Data attributes (was: Stylesheets considered limiting)

[james anderson]

the situation described below is a case where a namespace prefix is well used
to ensure unambiguous naming. if one uses the notation or entity name as the
name prefix it awards the same expressive power as the implicit qualification
of data attributes.

W. Eliot Kimber wrote:
> 
> ...
> 
> Not necessarily. What if I have this situation:
> 
> <!NOTATION MyQuery PUBLIC "">
> <!NOTATION GIF PUBLIC "" >
> <!ENTITY mygif SYSTEM [ width="640" height="480" ]>
> 
> ...
> <Query notation="MyQuery" icon="mygif">find something</Query>
> 
> Here, the notation of the element governs the query--the graphic it
> references is just presentation stuff in this case. So I can't put the
> entity's attributes on the element as well--they represent two different
> semantic domains, that of the query (represented by the element) and that
> of the graphic, represented by the entity.  Without data attributes and the
> ability to specify them as part of an entity declaration, I cannot keep
> these two domains clearly and unambiguously separate.


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)