fn:parse-xml: xinclude

[ChristianGruen]

We should allow XInclude processing to be enabled/disabled, as it can potentially lead to memory leaks.

[ndw]

Where does fn:parse-xml say that XInclude is ever performed? The only mention I see of XInclude is, somewhat amusingly, in fn:unparsed-text.

I'm not opposed to an option to enable it, but I don't think it should happen by default.

[ChristianGruen]

Where does fn:parse-xml say that XInclude is ever performed? The only mention I see of XInclude is, somewhat amusingly, in fn:unparsed-text.

Good that you mention this. It seems that at least two processors (namely, Saxon and BaseX) have enabled it, but I didn’t check why.

[michaelhkay]

We have a bit of a problem with parse-xml() on Saxon because it uses parsing options that are set globally at configuration level, and that's often inappropriate. XInclude certainly won't be enabled by default, but it will be affected by global settings.

[ChristianGruen]

XInclude certainly won't be enabled by default, but it will be affected by global settings.

You are obviously right (and I was wrong); it was a -xi CLI option that enabled the XInclude processing.