Re: Update on MusicXML Use Cases

Hi Joe, All,

Great update to the use cases! I have minor questions/suggestions:

1) We don't have the most trivial use cases, such as *Composer wants to
create notation for a composition.* True, everyone seem to have a good
common understanding of these simple use cases, so maybe it's superfluous,
and would bloat the document too much. Perhaps a paragraph could specify
that the omission is intentional?

2) *MC3: Arranger/performer wants to convert existing printed sheet music
into digital sheet music [...] PF would like to work with the music in a
notation application to adapt it or prepare a digital edition.*
* I feel there's a confusion going on between roles: in the described
example the person is basically taking up an editor/publisher role.

3) *MP5: Engraver wants detailed control over non-semantic formatting for
printed output, while allowing for more flexible rendering on arbitrary
devices e.g. mobile screens*
* EN may also want detailed control of over some non-semantic formatting
elements for for digital output as well as printed (e.g. positions of
accidentals and dots in a chord, beam angles, etc). Furthermore, EN also
wants _some_ control over elements that can break due to reflow, and _some_
control over where systems can break even when it's non-semantic, e.g.
breaking at a particular point is highly discouraged, but possible if
that's the only option.

4) According to the position that had been formed in the message of the W3C
Community Development Team on 11 Sept 2015, the title and content of the
document should be technology-agnostic:
*"We believe document format discussions are best driven by use cases,
expressed*








*in terms of the needs and actions of different classes of users, as well
as thenature and contents of the documents involved. Many of the
discussions so farhave been framed in terms of technology choices
like MusicXML vs. MEI, XML vs.JSON, or IEEE 1599 vs. SMIL. We would like to
begin re-framing these discussionsto clearly identify user needs and
document contents served by specificfeatures in these technologies, rather
than on whether we should pick technologyA vs. technology B. Eventually we
can shift to finding technical solutions thatsatisfy the use cases we deem
worth addressing, in the context of this group’scharter."*
Perhaps they could be called Music Notation Format Use Cases, and Music
Notation Format Technical Requirement respectively.

Best
Zoltan






On Sun, Apr 3, 2016 at 7:35 PM, Joe Berkovitz <joe@noteflight.com> wrote:

> Hello CG,
>
> In preparation for the discussion of use cases and other substantive
> questions at this week's upcoming meeting in Frankfurt, I've undertaken a
> major rewrite of this document:
>
> https://www.w3.org/community/music-notation/wiki/MusicXML_Use_Cases
>
> The main changes are as follows:
>
> - I have reworked all the use cases into short narratives or stories
> describing specific user roles pursuing a musical goal.
>
> - I have rewritten the section on Document Content to propose a starting
> point for thinking about what kinds of content that the standard might
> handle going forward.
>
> - I have added a new section on Document Profiles to propose a possible
> path for resolving the tension between faithful representation of human
> documents and semantic completeness/consistency.
>
> - I have excised some of the quasi-use-cases in the former section on
> Technical Requirements and turned them into bona fide stores.  The
> remainder of that section is now located in a new Wiki page located here:
>
>
> https://www.w3.org/community/music-notation/wiki/MusicXML_Technical_Requirements
>
> I will be continuing to work on the above Technical Requirements during
> the coming week and will let the CG know as this occurs.
>
> Finally, I should also take pains to point out that not everything in
> these documents reflects a full concensus from the Chairs. There are some
> viewpoints which are my own, and I've tried to label these as "proposals";
> my hope that these will be helpful in our making progress together.
>
> Of course not all of us will be in Frankfurt, so I look forward to
> discussion on the list as well as in person.
>
> Best,
>
> .            .       .    .  . ...Joe
>
> Joe Berkovitz
> President
> Noteflight LLC
>
> +1 978 314 6271
>
> 49R Day Street
> Somerville MA 02144
> USA
>
> "Bring music to life"
> www.noteflight.com
>

-- 
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.