-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for xinclude #28
Comments
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"). |
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 |
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 |
I mean that users would have to modify the schema and add elements to . |
Currently xinclude elements raise a validity error. Scholarly XML should process xi:include elements before validation.
The text was updated successfully, but these errors were encountered: