-
Notifications
You must be signed in to change notification settings - Fork 56
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.
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
Namespace for MusicXML #266
Comments
Unfortunately, MusicXML 3.1 does not have a standard XML namespace. Adding a namespace in a future version would make future MusicXML files incompatible with current MusicXML files and could break a lot of applications. However, an individual application could add a namespace, and modify a local version of the schema accordingly. |
Ok, thanks. Do you have a preference or a suggestion for what namespace could be used? |
@josteinaj At the moment I do not have a suggestion. I do see the value in adding a suggested namespace for applications to use when MusicXML is mixed with other vocabularies. To help us consider this for MusicXML 3.2, would you be willing to join the W3C Music Notation Community Group? You can join by going to our homepage at https://www.w3.org/community/music-notation/ and clicking the "Join Or Leave This Group" button. Please do join on behalf of NLB or DAISY as appropriate. If you have any issues while joining, please let me know. Thanks! |
Hi. Sorry for the late reply. I wouldn't have much to contribute to the group personally, and I don't really have time for it either. My only suggestion at this point is to define a namespace so that it's easier to have it flowing through systems together with other content. |
@josteinaj I was mistaken. While doing our initial update to MusicXML 4.0, I see that we already have specified this in MusicXML 3.1:
|
That's perfect, thanks! |
Is there a namespace that can be used for MusicXML, in case I want to mix it with other XML vocabularies? Maybe something like
http://www.w3.org/2017/MusicXML
?The text was updated successfully, but these errors were encountered: