Cart
[Home] [By Thread] [By Date] [Recent Entries]
Paul Prescod writes: > "Simon St.Laurent" wrote: > > That said, I think something like Erik Wilde's proposal of looking > > at XLink as an abstraction and permitting the mapping of components > > from other vocabularies into that abstraction works well. > > > > Link harvesters shouldn't need a whole lot of training to figure out > > that "href==(xlink:href xlink:type='simple') in XHTML." This is a > > pretty easy transformation. > > That solution is fine for a vocabulary as widely deployed as XHTML. > But how do I communicate that Docbook's linking elements are "really" > XLinks in disguise? Or TEI? Or ... > > I think that there needs to be a way to make that declaration out of > line. Perhaps in something like CSS. Perhaps in the schema. Perhaps in > something new altogether. Yes, it's yet-another-packaging-problem, and no one wants to go near packaging. For now, RDDL seems like a good place to put this information, as does a MIME Content-type registration. ------------- Simon St.Laurent - SSL is my TLA http://simonstl.com may be my URI http://monasticxml.com may be my ascetic URI urn:oid:1.3.6.1.4.1.6320 is another possibility altogether
|
