[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: XLink support
So. Armed with Eric's work http://www.balisage.net/Proceedings/vol7/html/Vlist01/BalisageVol7-Vlist01.html I've been looking at XLink support in DocBook in more detail. We have not done well. The extendedlink element has arc and locator children, but no resource child. Worse still, we've just about introduced a resource element for an entirely different purpose. And also, for an extended link that occurs inline <citetitle xlink:type="extended"> <xxx xlink:type="arc" ... /> ... the content of that extended link can be an arc, locator, and/or resource too. So it seems to me that either we need to allow arc/locator/resource more-or-less globally (with some Schematron; and with a solution to the resource problem) or we don't need them at all (but we do need something inside extendedlink, and we'd be making a backwards incompatilbe change). What's more, even if we allow them, they're a bit redundant because you'd have to say <arc xlink:type="arc">... Ugh... Be seeing you, norm -- Norman Walsh <ndw@nwalsh.com> | Reason's last step is the http://www.oasis-open.org/docbook/ | recognition that there are an Chair, DocBook Technical Committee | infinite number of things which | are beyond it.-- Pascal
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]