With pleasure. :)
I'll post again with more information and feedback, when I've got enough
of
it covered to make a release.
> It was decided to add this back in December. However, several WG members
> have since had a change of heart. So I have a feeling that it may not
> survive.
That would make at least one XML hacker slightly happier.
> My own belief is that having the "string" location term is sufficient, and
> sufficiently robust, to do any addressing you'd want to do into a CDATA
> section.
That's a belief I share.
> If we do want to allow addressing into some construct that the DOM doesn't
> support, it's incumbent on the XLink side to request new functionality from
> the DOM folks.
Then I see something that seems highly important: a method in the
Document
interface for returning the element with a given ID. Something like
this:
Element getElementWithID(in wstring id);
You've very likely already thought of and discussed this, so it would be
nice to hear what is likely to happen in this area. (I could subclass
the
Document object and the DOM builder in the Python DOM implementation to
get
this information, but it seems pointless if the DOM is going to include
it.)
--Lars M.