Integrating XPointer and XLink

Writing an XLink system is less demanding Creating systems which merely process XLinks and arcs is pretty simple stuff. Lightweight algorithms and a touch of creativity can deal with the toughest stuff XLink demands. XPointer requires a detailed understanding of XPath, plus a set of mechanisms for rising above a node-only approach. This isn't very easy, except in the simplest cases.
A complete XLink system, however, should include XPointer Making XLink 'really work,' in any way that rises above simple links or maybe inline extended links, requires a mechanism for referencing start and end points. Without that, what's the point?
Fragment identifiers as general problem We don't normally use fragment identifiers on graphic or sound files, but that could be some amazingly great stuff!