Notation References and Addressability

Hi Raff,

While I see a clear relationship between this work and the use case in
question, I wonder if it's best not to get too involved in comparing the
merits of specific APIs at this point.

There could be many APIs that support addressability. Some might be web
services like yours; others might be DOM APIs that operate locally. What is
interesting is the nature of the "pointer" that is being dereferenced.

When I think of addressability and the Web, I tend to think in terms of
pointers (stable references from one document to another, for example the
#fragment notation used in HTML documents). There are many possible APIs
that can be used to dereference such pointers, but I think deciding the
nature and structure of a "pointer" is a bigger question than the API
mechanism. We can figure it out better once we understand all the things
people want to do with pointers.

.            .       .    .  . ...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 Wed, Nov 25, 2015 at 3:11 PM, Raffaele Viglianti <
raffaeleviglianti@gmail.com> wrote:

> Hello all.
>
> On Wed, Nov 25, 2015 at 2:56 PM, Joe Berkovitz <joe@noteflight.com> wrote:
>>
>>
>> *Musicologist, within one document, wants to reference a specific
>> element, range or position of a work in the same or a different document
>> using some kind of anchor construct. *
>>
>> By the way, the fact that this case is "Musicologist" doesn't mean that
>> no other roles would want to do this same thing -- just that the use case
>> came up while thinking about musicological tasks.
>>
>
> Related to this point, I wanted to mention that the Enhancing Music
> notation Addressability (EMA) project has defined a URL scheme and API to
> "address" (or reference) a specific portion of music notation based on the
> notions of measure, staff, and beat (with the aim of making the scheme
> independent of a specific representation format).
>
> We have a first draft of the API here:
> https://github.com/umd-mith/ema/blob/master/docs/api.md
> And we have an example implementation that works on MEI documents (demo:
> http://mith.us/ema/omas )
> The API aims at being format-independent, so implementations can also be
> written for MusicXML and the new format that will result from this working
> group.
>
> Since referencing a specific portion of music notation seems to be an
> interest of this group, I would be curious to hear what you think of this
> approach.
>
> All the best,
> Raff Viglianti
>
>