Lists Home |
Date Index |
Notations and External Unparsed Entities provide a place to attach two
pieces of arbitrary semantics to an element, via an attribute declared of
type ENTITY or ENTITIES.
<object href="http://example.org/1.gif" />
can have this in the DTD:
<!NOTATION stdlink PUBLIC "xlink: show=new actuate=onLoad" >
<!ENTITY std_href SYSTEM "@href" NDATA stdlink>
LINKS ENTITIES "std_href"
The "LINKS" attribute has a list of linking entities to be used for this
The SYSTEM Identifier for the entity specifies a local attribute or child
element, the value of which is the remote target of the link.
The PUBLIC Identifier on the NOTATION specifies the sematics and behavior
associated with this link.
Those who love RDF and the Semantic Web can change the ad-hoc syntax I used
above for the system and public IDs into proper URIs.
Inspiration for this suggestion was provided by the "Datatypes for DTDs"
Downsides to this system:
1. It uses DTDs
2. It uses Notations
3. It requires a non-xml syntax to be created (to represent link behavour
and semantics, with is then stuffed into a Notation's Public ID)
>From: John Cowan <firstname.lastname@example.org>
>To: email@example.com (Wayne Steele)
>Subject: Re: [xml-dev] XLink/XHTML consensus?
>Date: Thu, 19 Sep 2002 17:07:52 -0400 (EDT)
>Wayne Steele scripsit:
> > I have an idea of a mechanism that would accomplish this, but it does
> > "Stupid DTD Tricks", which may be anethema to some.
> > Does anyone care? or are DTDs beyond the pale these days?
>Well, of course we care. Spill the beans already.
>John Cowan http://www.ccil.org/~cowan
> You tollerday donsk? N. You tolkatiff scowegian? Nn.
> You spigotty anglease? Nnn. You phonio saxo? Nnnn.
> Clear all so! `Tis a Jute.... (Finnegans Wake 16.5)
MSN Photos is the easiest way to share and print your photos: