Re: question on musicNotation

--001a11403a6a945fbc0550c6fa1a
Content-Type: text/plain; charset="UTF-8"

Hi Torsten,

First I will start by saying I don't know how to encode what you're asking
as that's not my field...

But if you haven't already heard of it, maybe the Music Encoding Initiative
might be of interest to you http://music-encoding.org/

It is inspired by the TEI and they apparently share a lot of the same or
similar features and XML structure but they aren't formally related.

I would venture to say that you would likely be able to write a TEI ODD
https://wiki.tei-c.org/index.php/ODD that could define a hybrid schema of
the two systems to allow for the best of both worlds..

Best,
Jack

On Tue, May 30, 2017 at 9:20 AM, Torsten Schassan <[email protected]> wrote:

> Dear colleagues,
>
> does anyone of you have (private) thoughts about how to improve the
> documentation (i.e. tagging) of musical notation?
>
>
> Right now we have:
>
> - musicNotation, which is member of modul.physDescPart and thus descendant
> of modul.msdescription
>
> - notatedMusic, which I considered to be a element to be used in
> transcriptions as member of model.globel but could -surprisingly- appear
> within <musicNotation> though
>
>
> In order to *describe* what kind of musical notation can be found I would
> rather elaborate on <musicNotation> instead of using notatedMusic within
> it. Opinions?
>
> In analogy to <stamp>, <watermark>, or <seal> I would think of new
> elements like <staff> and <clef> to describe what's there. Surely <term>
> would do the trick as well but would be less specific.
>
> In order to classify the notated music I would like to see @type defined
> for <musicNotation>.
>
> Considering the description in the Guidelines that "If a manuscript
> employs more than one notation, they must both be described within the same
> musicNotation element, for example as different list items." but realising
> that different notations may share the structure of different layouts or
> different forms of decoration, would it be feasible (though not backwards
> compatible) to propose something like:
>
> element musicNotationDesc
> { ...,
>    ( model.pLike+ | ( summary?, musicNotation+ ) )
> }
>
>
> Best, Torsten
>
>
> PS: BTW, ch. 14.3 lacks a space here: "notatedMusicprovides a way to
> signal ..."
>
>
> --
> Torsten Schassan - Digitale Editionen, Abteilung Handschriften und
> Sondersammlungen
> Herzog August Bibliothek, Postfach 1364, D-38299 Wolfenbuettel, Tel.:
> +49-5331-808-130 (Fax -165)
> Handschriftendatenbank* http://diglib.hab.de/?db=mss
>

--001a11403a6a945fbc0550c6fa1a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Torsten,<div><br><div>First I will start by saying I do=
n&#39;t know how to encode what you&#39;re asking as that&#39;s not my fiel=
d...</div><div><br></div><div>But if you haven&#39;t already heard of it, m=
aybe the Music Encoding Initiative might be of interest to you=C2=A0<a href=
=3D"http://music-encoding.org/">http://music-encoding.org/</a></div></div><=
div><br></div><div>It is inspired by the TEI and they apparently share a lo=
t of the same or similar features and XML structure but they aren&#39;t for=
mally related.=C2=A0</div><div><br></div><div>I would venture to say that y=
ou would likely be able to write a TEI ODD <a href=3D"https://wiki.tei-c.or=
g/index.php/ODD">https://wiki.tei-c.org/index.php/ODD</a>=C2=A0that could d=
efine a hybrid schema of the two systems to allow for the best of both worl=
ds..</div><div><br></div><div>Best,</div><div>Jack</div></div><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">On Tue, May 30, 2017 at 9:20 A=
M, Torsten Schassan <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]=
" target=3D"_blank">[email protected]</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">Dear colleagues,<br>
<br>
does anyone of you have (private) thoughts about how to improve the documen=
tation (i.e. tagging) of musical notation?<br>
<br>
<br>
Right now we have:<br>
<br>
- musicNotation, which is member of modul.physDescPart and thus descendant =
of modul.msdescription<br>
<br>
- notatedMusic, which I considered to be a element to be used in transcript=
ions as member of model.globel but could -surprisingly- appear within &lt;m=
usicNotation&gt; though<br>
<br>
<br>
In order to *describe* what kind of musical notation can be found I would r=
ather elaborate on &lt;musicNotation&gt; instead of using notatedMusic with=
in it. Opinions?<br>
<br>
In analogy to &lt;stamp&gt;, &lt;watermark&gt;, or &lt;seal&gt; I would thi=
nk of new elements like &lt;staff&gt; and &lt;clef&gt; to describe what&#39=
;s there. Surely &lt;term&gt; would do the trick as well but would be less =
specific.<br>
<br>
In order to classify the notated music I would like to see @type defined fo=
r &lt;musicNotation&gt;.<br>
<br>
Considering the description in the Guidelines that &quot;If a manuscript em=
ploys more than one notation, they must both be described within the same m=
usicNotation element, for example as different list items.&quot; but realis=
ing that different notations may share the structure of different layouts o=
r different forms of decoration, would it be feasible (though not backwards=
 compatible) to propose something like:<br>
<br>
element musicNotationDesc<br>
{ ...,<br>
=C2=A0 =C2=A0( model.pLike+ | ( summary?, musicNotation+ ) )<br>
}<br>
<br>
<br>
Best, Torsten<br>
<br>
<br>
PS: BTW, ch. 14.3 lacks a space here: &quot;notatedMusicprovides a way to s=
ignal ...&quot;<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
<br>
-- <br>
Torsten Schassan - Digitale Editionen, Abteilung Handschriften und Sondersa=
mmlungen<br>
Herzog August Bibliothek, Postfach 1364, D-38299 Wolfenbuettel, Tel.: <a hr=
ef=3D"tel:%2B49-5331-808-130" value=3D"+495331808130" target=3D"_blank">+49=
-5331-808-130</a> (Fax -165)<br>
Handschriftendatenbank* <a href=3D"http://diglib.hab.de/?db=3Dmss" rel=3D"n=
oreferrer" target=3D"_blank">http://diglib.hab.de/?db=3Dmss</a><br>
</font></span></blockquote></div><br></div>

--001a11403a6a945fbc0550c6fa1a--