[
Lists Home |
Date Index |
Thread Index
]
Ann Navarro wrote:
> At 07:01 PM 8/19/2002 +0200, Erik Wilde wrote:
>> so what about defining an xlink data model in terms of infoset
>> extensions, referencing it in xhtml and defining an xhtml-happy syntax
>> for it, and then going ahead and defining a css3 module for link
>> formatting?
> That's been toyed with in some corners, and looks like a possibility I'd
> at least be interested in looking over in more detail.
i think this would be the best way to go, in terms of genericity (is
there such a word?) and extensibility. have additional semantic modules
define their data model in terms of infoset contributions (perhaps
depending on other modules), and then make these contributions
accessible through the usual methods (xpath, dom, css).
the problem is that this would be a pretty long way to go:
- define a clean way to specify infoset contributions
- define an xlink data model as infoset contributions
- extend xpath, css, dom, ... for dealing with infoset contributions
- define a css module for formatting links
- define xhtml in terms of these mechanisms
and you're set! it's that easy!
cheers,
erik wilde - tel:+41-1-6325132 - fax:+41-1-6321035
mailto:net.dret@dret.net - http://dret.net/
computer engineering and networks laboratory
swiss federal institute of technology (eth)
* try not. do, or do not. there is no try. *
|
