Re: proposal of DOCTYPE change of MusicXML -- AW: Co-chair meeting minutes: April 25, 2024 [via Music Notation Community Group]

Michael (Good) once related to me (so he can clarify) that the name “MusicXML” was not accepted as a trademark for being too  generic as a term, given the many other Music + XML works going on at the time.   I am surprised though that MakeMusic’s wordmark had trouble going through — it is quite distinctive (I think beautiful) and really ties into the other MakeMusic products, which is why it’s not a great community logo even if it could be publicly used.

Best,
Myke

-----
Michael Scott Asato Cuthbert
music21 creator / co-founder ArtusiMusic.com / founder DH Lab at MIT
New email: michael.asato.cuthbert@gmail.com




> On May 3, 2024, at 12:46, Samuel Bradshaw <samuel.h.bradshaw@gmail.com> wrote:
> 
> According to https://tmsearch.uspto.gov/ , Recordare held the trademark for "MusicXML," but it's since been abandoned.
> 
> <Screenshot 2024-05-03 at 4.44.54 PM.png>
> 
>> On Apr 29, 2024, at 1:44 AM, Andrew Hankinson <andrew.hankinson@gmail.com> wrote:
>> 
>> I guess that depends on the specifics of the transfer of MusicXML to the w3c CG.
>> 
>> I note that the initial press release says that Recordare transferred “development” of MusicXML to the CG, but it never outright states that it transferred ownership.
>> 
>> https://www.musicxml.com/makemusic-transfers-musicxml-development-to-w3c/
>> 
>> So who currently owns MusicXML?(trademarks, copyright, etc).
>> 
>> Andrew
>> 
>>> On 29 Apr 2024, at 09:03, pavel.studeny@email.cz wrote:
>>> 
>>> Agreed, since https://musicxml.org/ doesn't have much other meaningful content, it should be doable to transfer the ownership.
>>> Pavel
>>> 
>>> ---------- Původní e-mail ----------
>>> Od: Reinhold Hoffmann <reinhold@notation.com>
>>> Komu: 'Music Notation Community Group' <team-community-process@w3.org>, public-music-notation@w3.org
>>> Datum: 26. 4. 2024 5:12:09
>>> Předmět: Re: proposal of DOCTYPE change of MusicXML -- AW: Co-chair meeting minutes: April 25, 2024 [via Music Notation Community Group]
>>> 
>>> Hi, 
>>> 
>>> Thanks for the minutes. 
>>> 
>>> With reagrds to 
>>> 
>>> "Myke proposes that the DOCTYPE system identifier for MusicXML should move 
>>> from www.musicxml.org to a URL within w3c.github.io/musicxml, since the 
>>> latter is under the control of the CG, while the former (quite rightly) 
>>> remains under the stewardship of MakeMusic. We welcome community feedback on 
>>> this issue, so please share your thoughts here." 
>>> 
>>> I would like to object. 
>>> 
>>> Reasons: 
>>> - this is a MusicXML protocol change which requires code changes of the 
>>> programs which use MusicXML. I am not sure what it means to downwards 
>>> compatibilities. At least for some time both doctypes need to co-exist. 
>>> - the URL www.musicxml.org is a neutral URL which reflects "MusicXML" where 
>>> w3c.github.io/musicxml is not 
>>> - "github" adds another kind of company dependancy to the protocol which 
>>> should definitely be avoided 
>>> - There should be a difference of "who hosts the URL" vs "the name of the 
>>> URL itself" 
>>> - if MakeMusic is not willing to host www.musicxml.org any longer, they 
>>> should hand it over to community 
>>> 
>>> Ideally, the hoster should be w3.org but I am not sure if this change can be 
>>> managed. 
>>> 
>>> My 2 cents... 
>>> 
>>> Thanks 
>>> 
>>> Regards, 
>>> 
>>> Reinhold 
>>> 
>>> 
>>> -----Ursprüngliche Nachricht----- 
>>> Von: W3C Community Development Team [mailto:team-community-process@w3.org] 
>>> Gesendet: Donnerstag, 25. April 2024 23:32 
>>> An: public-music-notation@w3.org 
>>> Betreff: Co-chair meeting minutes: April 25, 2024 [via Music Notation 
>>> Community Group] 
>>> 
>>> MNX 
>>> 
>>> 
>>> 
>>> Adrian has been working on some issues opened by Yuriy Kravets: 
>>> 
>>> 
>>> 
>>> 
>>> #334: There were several key names in the specification that used hyphens 
>>> rather than camel case; Adrian has now fixed this. A few values remain that 
>>> contain hyphens, and Adrian plans to fix these in due course. Adrian has 
>>> also updated the MNX converter where needed to handle these changes. 
>>> 
>>> 
>>> 
>>> #335: This required adding an enumeration for the showValue value for 
>>> tuplets (inner, none, both) 
>>> 
>>> 
>>> 
>>> #333: The staffSymbol object was missing the value none for its enumeration; 
>>> this has now been added. 
>>> 
>>> 
>>> 
>>> 
>>> Myke pointed out that it might be preferable to have more specific values 
>>> than "none" for enumerations, since "none" can be a special keyword in 
>>> several languages (typically equating to "null", "unknown", or "undefined"). 
>>> We spent some time discussing possible approaches to this, and agreed that 
>>> in principle we should use a more specific value than "none". Adrian will 
>>> review the other enumerations and see which others should be modified. 
>>> 
>>> 
>>> 
>>> Adrian has also been working on the MNX viewer, and it can now handle some 
>>> more notations, including accidentals, repeat barlines, and so on. 
>>> 
>>> 
>>> 
>>> MusicXML 
>>> 
>>> 
>>> 
>>> Myke proposes that the DOCTYPE system identifier for MusicXML should move 
>>> from www.musicxml.org to a URL within w3c.github.io/musicxml, since the 
>>> latter is under the control of the CG, while the former (quite rightly) 
>>> remains under the stewardship of MakeMusic. We welcome community feedback on 
>>> this issue, so please share your thoughts here. 
>>> 
>>> 
>>> 
>>> Next meeting 
>>> 
>>> 
>>> 
>>> The next co-chairs' meeting will be in three weeks, on Thursday 16 May 2024. 
>>> 
>>> 
>>> 
>>> ---------- 
>>> 
>>> This post sent on Music Notation Community Group 
>>> 
>>> 
>>> 
>>> 'Co-chair meeting minutes: April 25, 2024' 
>>> 
>>> https://www.w3.org/community/music-notation/2024/04/25/co-chair-meeting-minu 
>>> tes-april-25-2024/ 
>>> 
>>> 
>>> 
>>> Learn more about the Music Notation Community Group: 
>>> 
>>> https://www.w3.org/community/music-notation 
>>> 
>>> 
>>> 
>>> 
>