 |
|
|
2008/9/12 Michael Good <musicxml@g...>:
> Last year I asked some questions on the xml-dev list about creating an
> XSD version of the MusicXML 2.0 DTD as a first step towards a "General
> MusicXML" format. Yesterday, we released the XSD version of the
> MusicXML 2.0 format. It is available at:
>
> http://www.recordare.com/xsd/
>
> So far our experience with it has been very good overall, especially
> for the goal of making applications more reliable. We have tested
> dozens of applications against the XSD definition and in nearly every
> case we have found some problems in XSD validation that had otherwise
> eluded the application developers. I think this will really help in
> making a more reliable experience for MusicXML users. It should also
> better enable some new applications using XQuery and XML data binding
> tools.
One improvement you might like to do is to make all elements and
complex types global ("garden of eden" style) - this exposes the types
to schema-aware xslt and xquery, and arguably helps the maintenance of
the schema.
--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
