Download
Application made with Mono 2.0, compatible with .Net Framework 2.0. It allows to load and modify xml, xsd and xsl docs and perform theirs validation, also using an embedded browser. Also, it allows to apply xsl to xml and to validate xml with xsd.
Project Samples
License
GNU General Public License version 2.0 (GPLv2)Follow XmlValidator
Other Useful Business Software
EHS Software and Management System
ERA Environmental Software Solutions develops web-based EHS management software for small, medium, and large manufacturers needing to comply with federal, provincial, and state regulations, monitor their air, water, and waste emissions and other environmental outputs, author and manage Safety Data Sheets (SDS) in more than 40 languages, or standardize their Health and Safety procedures for incident and inspection tracking, training delivery, and audit management. The platform also supports comprehensive reporting for programs like TRI, Tier II, Title V, NEI, and NPRI. Companies across the automotive, aerospace, general manufacturing, and paints and coatings industries, to name a few, rely on ERA’s all-in-one, SOC 2 Type II certified SaaS for complete coverage of their EHS needs.
Rate This Project
Login To Rate This Project
User Reviews
-
@oscarand: I like your tool. It's easy to use and serves its purpose well. Anyway, I found that it doesn't support some xpath expressions. Given this xml input: <root> <test><id>3000</id></test> <test><id>3000</id></test> <test><id>3000</id></test> <test><id>3002</id></test> <test><id>3002</id></test> <test><id>3005</id></test> </root> And the following xpath: (/root/test[id=3002]/id)[1] The tool doesn't return any result. (It should return '3002'). Do you plan to support this kind of xpath expressions in a future release? Thanks!
-
This would be a good tool, however, when validating xml against an xsd, I get a message: "Error - The element cannot contain text. Content model is empty". But it does not tell me anywhere what Node or Element has the error. I finally found which node by manually figuring it out. This tool should always show what node/element the error occurred on, but it doesn't. I forced other errors too, and many errors do not tell you what node the error occurred on. For example, add any attribute to an element, that isn't allowed in the xsd, and you get an error, but it does not tell you what Node/Element the error is in. Otherwise, this looks like it would be a good tool.
-
Limited to 64 KB
-
Bad handling. Limited to 64 KB. Cannot be used when XSD > 64 KB
-
Great app, precisely what I needed without the extra fat! Thanks
