HAMON — Licensing ================= Copyright (c) 2026 Universidad de Alicante. The software was written by Patricia Garcia-Iasci and David Rizo. The standard and the ICCCM'26 paper it accompanies are the work of Patricia Garcia-Iasci, Johannes Hentschel, Fabian C. Moss and David Rizo. Authorship and ownership are different things: the citation under "Attribution" below is what both licences require of you. HAMON is a standard plus its reference implementation, so it is released under two licences — one for software, one for the specification and its data. Pick the one that matches the file you are using. Software Apache License 2.0 LICENSES/Apache-2.0.txt Specification & data CC BY 4.0 LICENSES/CC-BY-4.0.txt Software (SPDX: Apache-2.0) --------------------------- hamonpy/ the Python reference implementation, incl. generated ANTLR parsers and the CLI tools/ build, release and validation scripts verovio-hamon/ build scripts site/, ICCCM26/ the code that builds them Apache-2.0 is a software licence: unlike Creative Commons it handles source vs binary distribution and grants patent rights explicitly, which is what an implementable standard needs. Specification and data (SPDX: CC-BY-4.0) ---------------------------------------- grammar/ the normative EBNF and the JSON schema antlr/ the .g4 grammars conformance/ the corpus and the golden output fixtures/ the fixture corpus documentation/ prose documentation mei-customization/ the ODD files use-cases/ the worked examples (prose; any bundled third-party corpus keeps its own licence — see below) Attribution ----------- Both licences require attribution. Cite: Garcia-Iasci, P., Hentschel, J., Moss, F. C., & Rizo, D. (2026). Bridging harmonic representations through a multi-modal encoding. International Conference on Computational and Cognitive Musicology (ICCCM 2026). https://digital.musicology.org/icccm-2026/ Third-party material -------------------- Corpora and datasets that HAMON reads are NOT covered by the licences above. They belong to their authors and keep their own terms — see the `license` field of each entry in `datasets/manifest.json`, and any `LICENSE-*` file bundled alongside an extract in `use-cases/`. `datasets/` ships a manifest only, never the payloads. No warranty ----------- The Work is provided "as is", without warranty of any kind. See the warranty and liability sections of the two licence texts.