[MEI-L] @dur on <fTrem> and <bTrem>

[Roland, Perry (pdr4h)]

Noted, and anticipated.  Hence, the word "perhaps".  :)

I probably should have said that schematron rules can be written to control this situation *when it is not desirable to allow it.*

--
p.


__________________________
Perry Roland
Music Library
University of Virginia
P. O. Box 400175
Charlottesville, VA 22904
434-982-2702 (w)
pdr4h (at) virginia (dot) edu
________________________________________
From: mei-l-bounces at lists.uni-paderborn.de [mei-l-bounces at lists.uni-paderborn.de] on behalf of Johannes Kepper [kepper at edirom.de]
Sent: Saturday, January 07, 2012 2:23 AM
To: Music Encoding Initiative
Subject: Re: [MEI-L] @dur on <fTrem> and <bTrem>

Am 04.01.2012 um 20:09 schrieb Roland, Perry (pdr4h):

> Adding @dur on <fTrem> and <bTrem>, or more precisely, making them members of the att.duration.musical and att.augmentdots classes, is ok with me.
>
> Doing so would make these elements consistent with the <chord> element; that is, as an encoding shortcut, @dur can be placed on the <fTrem> or <bTrem> parent element instead of on the child <note> or <chord> elements.
>
> But, because these attributes can't be disallowed on the child elements (they're needed when <note> and <chord> occur outside of <fTrem> and <bTrem> of course), it will be valid for @dur and @dots to occur in either or both places.  Perhaps schematron rules could be created that disallow @dur and @dots on the child elements when they exist on the parent.

I wonder if we really want to disallow these attributes on the child elements. I have no access to Read etc. currently, but if I remember correctly, at least one of them allows chords to contain notes with differing length. I'm not sure if I would like to follow this argumentation, but I don't think that MEI should disallow such a situation. I'm perfectly happy to address this in the Guidelines and make sure that this would be a rather uncommon and unexpected situation, but although Schematron certainly can suppress @dur within chords and trems, I wouldn't recommend it.

Just my two drachma…
Johannes

>
> --
> p.
>
> __________________________
> Perry Roland
> Music Library
> University of Virginia
> P. O. Box 400175
> Charlottesville, VA 22904
> 434-982-2702 (w)
> pdr4h (at) virginia (dot) edu
> ________________________________________
> From: mei-l-bounces at lists.uni-paderborn.de [mei-l-bounces at lists.uni-paderborn.de] on behalf of TW [zupftom at googlemail.com]
> Sent: Wednesday, January 04, 2012 11:41 AM
> To: Music Encoding Initiative
> Subject: [MEI-L] @dur on <fTrem> and <bTrem>
>
> Does anything speak against having @dur on <fTrem> and <bTrem>, like
> on <chord>?  If no, I'd add a feature request to the issue tracker.
>
> Thomas
>
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l


_______________________________________________
mei-l mailing list
mei-l at lists.uni-paderborn.de
https://lists.uni-paderborn.de/mailman/listinfo/mei-l