Skip to content
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

Open
raffazizzi opened this issue Aug 19, 2022 · 4 comments
Open

Support for xinclude #28

raffazizzi opened this issue Aug 19, 2022 · 4 comments

Comments

@raffazizzi
Copy link
Owner

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

@oscarlevin
Copy link
Collaborator

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").

@raffazizzi
Copy link
Owner Author

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>

@oscarlevin
Copy link
Collaborator

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>?

@raffazizzi
Copy link
Owner Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants