MEI Validation

The current MEI file being viewed or edited in Neon is also validated against the MEI schema. This can be seen in the display panel.

The file is validated against the MEI 5.0.0-dev schema using xml.js. When the MEI file passes, the text "VALID" will appear in green. When it does not, the text "INVALID" will appear in red. Clicking on "INVALID" will download the log file from the validation detailing what in the MEI file did not pass validation and why.

Validation is run whenever the MEI file is modified or loaded into Neon. This is partially to ensure the user is using a valid file, but also to quickly catch if Neon creates an invalid file through an editor action. This is not supposed to occur. If it does, please create an issue detailing what occurred. Also include the contents of the validation log file in the issue.

NOTE: The MEI file generated by the mei-encoding job in Rodan is in MEI 4.0.0. Therefore, when the file is loaded into Neon, Neon would validate it as "INVALID" because of the version difference. But as soon as the user makes a change to the file, Neon will regenerate the file in version MEI 5.0.0-dev and validate it as "VALID".

Validate MEI Schema:

Here is the link to how to use Oxygen to validate an MEI schema: https://github.com/music-encoding/music-encoding#using-oxygen-to-build-mei