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.

Sign up for GitHub

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

Jump to bottom

The new definition of db._any causes validation errors #167

Closed
ndw opened this issue Jul 23, 2020 · 1 comment
Closed

The new definition of db._any causes validation errors #167

ndw opened this issue Jul 23, 2020 · 1 comment

Comments

@ndw
Copy link
Contributor

ndw commented Jul 23, 2020

Allowing DocBook elements to occur inside db._any leads to attribute type conflicts with ID/IDREF attributes. The motivation for the change to db._any was really to allow HTML in there. We even added a db._nodb pattern for the any-but-DocBook case.
@ndw
Copy link
Contributor Author

ndw commented Oct 24, 2020

This is a regression that has to be fixed, and has been fixed, so I'm closing this.

@ndw ndw closed this as completed Oct 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ndw