|
| 1 | +--- |
| 2 | +layout: conference |
| 3 | +title: "Statement on the use of generative AI" |
| 4 | +permalink: "/conference/2026/ai-statement/" |
| 5 | +tag: MEC2026 |
| 6 | +id: statement-ai |
| 7 | +--- |
| 8 | +<!-- |
| 9 | +<img src="/images/conference/2026/banner.jpg" class="img-responsive" style="margin-bottom: 1em" alt="Music Encoding Conference banner showing scenes from Clerkenwell, London"> |
| 10 | +--> |
| 11 | +<div class="mec2025-page"> |
| 12 | + |
| 13 | + <h2>Statement on the use of generative AI in submissions for MEC 2026</h2> |
| 14 | + <p> |
| 15 | + We recognize that authors of academic works use a variety of tools in the research on |
| 16 | + which they report, and to prepare the report itself, from simple ones to very sophisticated |
| 17 | + ones. We note that tools may generate useful and helpful results, but also errors or |
| 18 | + misleading claims. Knowing which tools were used is relevant to evaluating |
| 19 | + and interpreting academic works. |
| 20 | + </p> |
| 21 | + <p> |
| 22 | + In view of this, we |
| 23 | + </p> |
| 24 | + <ol> |
| 25 | + <li> |
| 26 | + require authors to report in their work any significant use of software tools, such as |
| 27 | + instruments and software that go beyond word processors or typesetters; we now include |
| 28 | + in particular text-to-text generative AI among those that should be reported. |
| 29 | + </li> |
| 30 | + <li> |
| 31 | + remind all colleagues that by signing their name as an author of a contribution, they |
| 32 | + each individually take full responsibility for all its contents, irrespective of how |
| 33 | + the contents were generated. If use of generative AI results in inappropriate |
| 34 | + language, plagiarized content, errors, mistakes, incorrect references, or misleading content, |
| 35 | + and that output is included in academic works, it is the responsibility of the author(s). This |
| 36 | + may affect acceptance of your submission. |
| 37 | + </li> |
| 38 | + <li> |
| 39 | + do not accept generative AI language tools as an author; instead authors should refer to (1). |
| 40 | + </li> |
| 41 | + </ol> |
| 42 | + |
| 43 | + <p> |
| 44 | + This statement is an adapted version of the |
| 45 | + <a href="https://blog.arxiv.org/2023/01/31/arxiv-announces-new-policy-on-chatgpt-and-similar-tools/">arXiv |
| 46 | + policy for authors’ use of generative AI language tools</a>. |
| 47 | + We reserve the right to amend this statement as discussions continue and evolve. |
| 48 | + </p> |
| 49 | + |
| 50 | +</div> |
0 commit comments