Erik> apart from that, i cannot imagine what the hard parts should
Erik> be, but maybe i am a bit to naive. anyway, i would be very
Erik> happy to be pointed to a list of potential problems before i
Erik> get started.
I seem to recall that there are parts of the infoset that XInclude
needs that an XSLT processor never gets to see, as they aren't in the
XPath Data Model. But my memory is rather vague on this.

if anybody could mention if this really is the case, i would be most
grateful. http://www.w3.org/TR/xinclude/#infoset to me looks as if the
"must" parts are all satisfied by the infoset view of xslt, whereas the
"may" parts ("include history" and "language" properties) definitely are
a problem. but they are optional.

and while i am at asking questions about xinclude (i am sorry for this
being a complete non-xslt question): is anybody aware of a test suite
for xinclude? there are some exotic things in there (handling notations,
for example) and it would be good to have a set of test files and
expected results. http://www.w3.org/XML/Test/XInclude/ talks about being
a conformance test suite for the "Candidate Recommendation", but that is
probably good enough. any other test suites that anybody would know of?