Re: Restructuring the "Use Cases" Wiki page

Hi Christopher,

I just reviewed your edit -- thanks, I think it probably makes sense, and
there was certainly a divide of sorts between the Developer "use cases" and
all the others, in terms of the nature of the role. As long as you didn't
delete or substantially alter items, this rearrangement works for me.

...Joe



.            .       .    .  . ...Joe

*Joe Berkovitz*
President

*Noteflight LLC*
49R Day Street / Somerville, MA 02144 / USA
phone: +1 978 314 6271
www.noteflight.com
"Your music, everywhere"

On Sun, Nov 29, 2015 at 3:52 PM, Antila, Christopher <christopher@antila.ca>
wrote:

> Greetings to the Music Notation list!
>
>
> After reviewing the list of suggested use cases, I realized the
> information on that page could be structured in a way that guides our
> discussion more helpfully. Following the wiki spirit, I went ahead and
> reogranized the page, and now I would like to explain my changes and
> invite community members to make your own revisions.
>
> Just to be sure everyone has it, here's a link to the wiki page in
> question:
> https://www.w3.org/community/music-notation/wiki/MusicXML_Use_Cases
>
> Although I intend to modify the page contents, so far I have restricted
> my changes to structure and organization. The goal was to separate out
> four distinct concerns I saw, all of which are related to describing the
> use cases of a symbolic music notation representation. To that end, the
> four sections describe:
>
> 1.) "User Roles" assumed by people using music notation;
> 2.) "User Actions" performed by people who have assumed a role;
> 3.) "Technical Requirements and Considerations"; and
> 4.) "Progress Notes" about what has and has not yet been considered.
>
> As above, this involved changing only the structure of the
> document---with one exception. I removed the "developer" user role,
> meaning specifically that I removed the "Developer" line from the "User
> Roles" section, but all related concerns are still represented in the
> section about techincal requirements. This helps to clarify that User
> Roles are musical people and that User Actions are part of a musical
> activity. Our Technical Requirements fall out of the musical activities
> we decide are in our scope, and our Technical Considerations help
> software developers use the encoding format.
>
> By no means do I suggest that I've come upon the best solution, or that
> I properly categorized everything. If you have suggestions, please feel
> free to edit the wiki, and post to the list so we know what you've done!
>
>
> Thank you,
> Christopher
>
>