- From: Zoltan Komives <zoltan.komives@tido-music.com>
- Date: Thu, 7 Apr 2016 10:46:24 +0100
- To: James Ingram <j.ingram@netcologne.de>
- Cc: public-music-notation-contrib@w3.org, Joe Berkovitz <joe@noteflight.com>, Michael Good <mgood@makemusic.com>
- Message-ID: <CADGv7xpMuvuUgTSakGJic2h9Ubgu1i7ndqAZ4bBu1JNd6DPFpg@mail.gmail.com>
Hi James, All, I am firmly on the position that the requirement analysis should be strictly technology-agnostic (that is, even XML should be expelled from our language for the time being, even if for practical reasons this will probably end up being the carrier format). I think, when we are not sure what we want, the best practice is to describe and explain ideas in great detail first, and when they are fully understood, names will fall out naturally. However, doing the other way around will unavoidably lead to misnomers (and in my opinion also restricts creative thinking). But this is just my two pennies. Zoltan On Thu, Apr 7, 2016 at 10:01 AM, James Ingram <j.ingram@netcologne.de> wrote: > > I think its important to define codename(s) for the standard(s) this group > is trying to create. These names need not be the name(s) of the final > standard(s), but we need something to work with. Since these names are not > to be considered final, I don't think we need to worry too much about > getting them right. That can be left for later. > > Maybe we could decide tomorrow how many codenames we need, and what they > should be. Here are my suggestions.: > > I think we need to define *two* standards, since we are considering two > different scenarios: > > Scenario 1: An interchange format that can be used by applications that > CREATE scores. This will be a development of MusicXML. Suggested codename: > *MintXML* (Music INTerchange XML) -- I'd like to keep the look and feel > of the parent standard's name. Also, I like the hidden reference to > indivisible *int*s... :-) > > Scenario 2: A score format that can be USED by various applications > (printing, on the web etc.). I think this should be SVG extended to contain > MIDI information. Suggested codename: *SVG-MIDI*. > > Looking forward to seeing you all tomorrow! > > All the best, > James > https://github.com/notator > http://james-ingram-act-two.de > > -- www.tido-music.com Tido Enterprise GmbH (Amtsgericht Leipzig, HRB 29529), Talstrasse 10, 04103 Leipzig, Germany. Disclaimer: The information in this e-mail including any attachments is confidential and may be legally privileged. If you have received this message in error, please contact the sender immediately and delete this message and any copies from your computer and network. The unauthorized use, distribution, copying or alteration of this e-mail and any attachments is strictly forbidden.
Received on Thursday, 7 April 2016 09:47:13 UTC