MNX identifier/file format #305
Replies: 2 comments 1 reply
-
Pros of .json (plain text) Pros of .mnx (plain text) Pros of .mnxz (compressed) I lean towards:
|
Beta Was this translation helpful? Give feedback.
-
I think we should encourage the compressed format as the primary choice for end users. To that end, why not use The compressed format has the advantage of being smaller and potentially able to include multiple files in the container (e.g. images, etc.), hence I believe it should be the default option for most users. The plain text format is mainly useful to developers. |
Beta Was this translation helpful? Give feedback.
-
Discussing file formats/extensions. Related to #301
Looking at:
.json
-- works fine for MNX but doesn't identify it as different from any other .json file (like ".xml" for musicxml).mnx
-- the same JSON file but something you can click on to launch in a music editor. (like ".musicxml" for MusicXML).mnxz
-- the JSON file compressed version (probably GZ but still undecided (like ".mxl" in MusicXML)Also looking at putting the version (in some format) at a top-level tag that identifies the JSON as specifically MNX:
Discussed at co-chairs meeting 21 June 2023. Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions