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.

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

Document MuseScore schema #3

Open
infojunkie opened this issue Nov 28, 2024 · 2 comments
Open

Document MuseScore schema #3

infojunkie opened this issue Nov 28, 2024 · 2 comments

Comments

@infojunkie
Copy link
Owner

...ideally using XSD and use that to validate output MSCX files instead of invoking the mscore executable.

@infojunkie
Copy link
Owner Author

One crazy idea is to use an LLM to analyze the 1000s of MSCX files in the MuseScore repo, to produce an XSD that matches them all. It would also be great to produce some invalid MSCX files to ensure those are not matched.

find -name '*.mscx' | while read "f"; do cat "$f" >> all-the-musescore-files.mscx; done

@infojunkie
Copy link
Owner Author

infojunkie commented Dec 11, 2024

I fed the MSCXs to XMLSpy and got the attached XSD. Some areas need massaging:

  • The software was too eager to create choice elements where plain strings are expected
  • It got severely confused by all the combinations of Note sub-elements

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant