vscode-sxml icon indicating copy to clipboard operation
vscode-sxml copied to clipboard

Support for xinclude

Open raffazizzi opened this issue 2 years ago • 4 comments

Currently xinclude elements raise a validity error. Scholarly XML should process xi:include elements before validation.

raffazizzi avatar Aug 19 '22 18:08 raffazizzi

It looks like red-hat's xml plugin now can handle xinclude (on their preview build), although it seems it only goes one way: it validates included files, but still throws validation errors on the included files (when their root element is not "correct").

oscarlevin avatar Dec 12 '22 19:12 oscarlevin

Great! Yes, their extension is starting to cover a lot of ground without needing Java. My understanding is that what you described is the expected behavior for xinclude: the included fragments need to deal with their own validation. Oxygen XML editor (which is the software of reference in the TEI community) does the same thing. This can be dealt with at the user level by adding elements to <rng:start>

raffazizzi avatar Dec 12 '22 20:12 raffazizzi

This can be dealt with at the user level by adding elements to <rng:start>

Can you say more? Do you mean modifying the schema for the grammar and modifying it? Or is there a way to tell the editor to add elements to <start>?

oscarlevin avatar Dec 12 '22 20:12 oscarlevin

I mean that users would have to modify the schema and add elements to .

raffazizzi avatar Dec 12 '22 20:12 raffazizzi