Processing model for notes
We've run into a problem with the placement of notes. In the EEBO TCP texts note elements are recorded inline. They nearly always carry a
@place= "margin" attribute. For a variety of reasons I moved the notes to a separate back element, leaving a ref element as a placeholder with a @target attribute that points the note.
Thus in the following toy example
<note xml:id="A20069-e123" place ="margin"><w>this</w>...</note>
we end up with
<ref xml:id="A20069-e123-a" corresp="A20069-e123-b"target = "#A20069-e123-b">
in the original location of the note, while the note appears somewhere in
<back> <div type="notes"> <note xml:id="A20069-e123-b" corresp="A20069-e123-a" place="margin"><w>this</w>...</note> </div>
When I did this I assumed that it would be a trivial matter to adjust the Processing Model. Am I right in this or is it harder ( as one of my colleagues argues)? In the inline notation,
<note place="margin"> triggers a processing instruction to do something with the
<note> , i.e. display it in the margin.
If the note is at the end, one needs a processing instruction for
<ref>, which would say "go to the place marked by the
@target attribute, pick up the note and then process it, display it in the margin in the location of the
ref attribute." So there is just one additional step.
Am I right on this, or is this not as straightforward as I think?