http://tei.oucs.ox.ac.uk/EEBO/ lists some places where TCP EEBO texts have identified stage directions inside poetry. Thus:
<l>Then such cheape stage-ware) to vnfold our Scene,</l>
<l>And without vaile to Open what we meane</l>
<l>Behold. <stage n="*" place="margin">Here the vp<lb rend="hidden" type="hyphenInWord"/>per part of the <hi>Scene</hi> open'd; when straight appear'd a Heauen, and all the <hi>Pure Artes</hi> sitting on two semi<lb rend="hidden" type="hyphenInWord"/>circular ben<lb rend="hidden" type="hyphenInWord"/>ches, one a<lb rend="hidden" type="hyphenInWord"/>boue another: who sate thus till the rest of the <hi>Prologue</hi> was spoken, which being ended, they descended in order within the <hi>Scene,</hi> whiles the Musicke plaid</stage> Our Poet knowing our free hearts</l>
<l>Has here inuited Heau'n and All the Artes</l>
<l>To entertayne His Theater, and does bring</l>
<l>What he prepar'd for our Platonique King:</l>
where the stage direction comes in the margin (image attached). To support this, we could add <stage>
to model.phrase, and make it a member of att.placement.
Wouldn't this be better encoded as a <note place="margin"> (which could of course contain a <stage>) ?
That could work, I agree, for the example I gave. but why force the things into the procrustean bed of a <note>, just to get placement? what downside is there to allow @place on <stage>?
Last edit: James Cummings 2013-11-09
stage should definitely claim membership in att.placement.
I've no problem with adding &stage> to att.placement, but I don't believe any other change is necessary -- it's already permitted as a child of <l>
I note en passant that membership in att.placement is really just a specialised kind of rendition information.
I agree with Lou that it makes sense to add <stage> to att.placement, but not sure why we would want to add it to model.phrase.
adding 'stage' to att.placement accepted by Council. adding it to model.phrase rejected until new evidence is offered.
Council in Oxford 2013-11 agreed that stage could have @place; Sebastian to implement and document.
I think there is a reasonable example of a stage direction that needs placement by no other features of <note> from the WWP corpus
The Innocent Mistress, 1697:
Syd, this looks like a good example: can you provide a page image?
I am not sure why "inset-left" isn't just normal rendition like the rest of the string? looks like indentation at first blush.
Diff:
Diff:
Council meeting 11/13 debated at length, and eventually agreed to this; seeing that
<stage>
can have note-like properties, of being out of the main reading order of text, and thus @place makes sense for them. Implement, but make sure discussed in main guidelines.Has this been completed?
yes, its been implemented. duly closing