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

Considering Information from XSD and DTD #4

Open
themetalone opened this issue May 11, 2016 · 2 comments
Open

Considering Information from XSD and DTD #4

themetalone opened this issue May 11, 2016 · 2 comments
Assignees
@themetalone
Labels
enhancement

Comments

@themetalone
Copy link
Collaborator

At the moment LeXeMe assumes either one or arbitary many elements while merging. This information is contained in the definition schematas. LeXeMe should use those information to improve the quality of the merge
@themetalone themetalone self-assigned this May 11, 2016
@themetalone
Copy link
Collaborator Author

For XSD this might be easier as for DTD because of the XSD's XML structure that can easily parsed

@maybeec
Copy link
Owner

maybeec commented Jun 2, 2016

havin a short look at google shows, that there are ready to use solutions for DTD parsers for Java.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@themetalone themetalone

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@maybeec @themetalone