Community
Participate
Working Groups
Add support for XML validation based upon RelaxNG schemas.
I've heard similar requests before. I'm not sure we will ever provide this directly, but, ideally, we should provide enough infrastructure that others could "plugin" this sort of validation if they'd like. And, to be honest, some examples, or justification of use-case would be helpful. (such as, exactly why is this important?). And, again, if anyone tries this and has suggestions for how we can improve infrastructure to allow it, that'd be best. I'll mark as "help wanted" to acknowledge we (core WTP teams) have no plans nor resource to implement this ... but, again, if infrastructure is insufficient, it'd be great to know that.
This is comment on importance of Relax NG support. RelaxNG is more convenient for authoring document-oriented (for data-oriented documents there are different opinions on the issue) document types. Many new OASIS XML document formats are specified in RelaxNG. Among them are: - Docbook 5.0 (see docbook.org. There is also XSD but it is non-authoritative representation) - OASIS OpenDocument 1.0 and 1.1 (http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office) Also Relax NG is an ISO standard (and XSD is not AFAIR). This makes it quite likely that ISO produced or government produced xml formats will be defined using Relax NG. Possibly this is the reason why OASIS OpenDocument uses Relax NG. So lack of Relax NG support will make it difficult to use WTP in cases when usage of ISO standards is mandated for the project.
Thanks Constantine. The "helpwanted" status still stands, but I'll raise the priority to P2 just to acknowledge your observations.
I've heard a few requests for Relax. Someone emailed me a while back about graphical editor support too. Our lack of support for this standard is simply due to our low bandwidth. If there are any Relaxians out there who'd like to help I'd be happy to walk you thru the code and facilitate your efforts to provide an alternative to the beast that is XML Schema.
Marking as a duplicate to resolve. The work is being done around bug 281529. *** This bug has been marked as a duplicate of bug 281529 ***