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

[TW]

I submitted the issue for the 2013 milestone.


2012/1/4 Roland, Perry (pdr4h) <pdr4h at eservices.virginia.edu>:
> 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.
>
> --
> 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