Re: Requirements Matrix and Architectural Proposals

Hello Joe,

some thoughts/questions on your architectural proposals:

- One of the central points of MusicXML "redesign" should be turning it 
from an exchange format into a notation standard for both storage *and* 
manipulation of musical data. This is said between the lines ("can be 
incrementally modified / styled and highlighted programmatically") but 
could be emphasized.

- It is definitely the right way to go towards well-established 
standards, such as CSS and DOM. But although these are general 
standards, their usage is strongly related to the Web/Javascript world 
and they currently have less support in the native (Java, C++) world. I 
think browsers and native platforms should be well balanced in the new 
format.

- Question about Multiple rendering styles: "... This requirement states 
that the semantic data for a document may be associated with multiple 
styles, both within a given document and over a span of time."
Could you give an example?

- Concerning performance/visual styling: If we want to make the 
distinction between performance and visual appearance (and I think we 
should), we should also separate them in the format. The easiest but 
probably not the best way would be using a naming convention for 
distinguishing performance and visual attributes (properties).

Best regards,
Dominik Hörnel

-- 

capella-software AG
An der Söhrebahn 4
34320 Söhrewald
Tel. +49 (0)5608-3923
Fax. +49 (0)5608-4651
E-Mail: info@capella.de <mailto:info@capella.de>
Internet: www.capella.de <http://www.capella.de>
capella ist bei Facebook! <https://www.facebook.com/capella.Musiksoftware>

Registergericht: Amtsgericht Kassel, HRB 15433
Aufsichtsrat: Dr. Jutta Bott (Vorsitzende)
Vorstand: Dr. Dominik Hörnel


Am 06.04.2016 um 14:52 schrieb Joe Berkovitz:
> Hi Group,
>
> To stimulate discussion in Frankfurt (and, of course, on this list) I 
> have published a couple of documents:
>
> 1. A Requirements Matrix now sets forth a set of intermediate 
> requirements in various categories, These are derived from the 
> already-published User Stories and are explicitly traced back to them. 
> This list is still in a rather crude state (and is not prioritized or 
> fully scoped) but I found it helpful to make and to think about:
>
> https://www.w3.org/community/music-notation/wiki/Requirements_Matrix
>
> 2. The former "Technical Requirements" document is now retitled 
> "Architectural Proposals" (as there are a set of technical 
> requirements in the Requirements Matrix):
>
> https://www.w3.org/community/music-notation/wiki/Architectural_Proposals
>
> These proposals are an expression of my present opinion. They 
> certainly don't reflect a concensus viewpoint -- at least not yet! -- 
> but are intended as a starting point for thinking. I've published 
> these thoughts in an unsanctioned state because I believe this is a 
> good point in time for us to be discussing approaches and issues that 
> have not been addressed to date in MusicXML, MEI or elsewhere.
>
> In many cases, my starting point for some proposal is some idea that 
> has been quite successful in other realms, notably in Web and W3C 
> standards. I have this orientation not because I think everything 
> useful happens online or in a browser, but because the Web has given 
> rise to an explosion of document exchange, expressivity and 
> portability. In turn, this explosion has forced certain important 
> problems in document modelling and structure to be considered and 
> addressed. I think the solutions can be made completely portable 
> across OSs, online/offline contexts, and programming languages, as 
> they have elsewhere. Of course, many problems remain, and some of them 
> will be specific to music -- but not all of them.
>
> Both documents are now linked from the main Wiki page.
>
> .            .       .    .  . ...Joe
>
> Joe Berkovitz
> President
> Noteflight LLC
>
> +1 978 314 6271
>
> 49R Day Street
> Somerville MA 02144
> USA
>
> "Bring music to life"
> www.noteflight.com <http://www.noteflight.com>

-- 
Mit freundlichen Grüßen
Dr. Dominik Hörnel

capella-software AG
An der Söhrebahn 4
34320 Söhrewald
Tel. +49 (0)5608-3923
Fax. +49 (0)5608-4651
E-Mail: info@capella.de <mailto:info@capella.de>
Internet: www.capella.de <http://www.capella.de>
capella ist bei Facebook! <https://www.facebook.com/capella.Musiksoftware>

Registergericht: Amtsgericht Kassel, HRB 15433
Aufsichtsrat: Dr. Jutta Bott (Vorsitzende)
Vorstand: Dr. Dominik Hörnel