Add examples and suggested values for <space type="hole|damage|decoration|indent|centering|ditto|field"/>
as discussed on the Markup list Re: encoding intentional hole in support of text (see e.g. http://lsv.uky.edu/scripts/wa.exe?A2=ind1607&L=markup&P=1277). To be discussed whether this belongs on the regular page for vacat, or a new page should be created.
Scott will poke around and will then reply to Markup again.
The correct link to Markup might be: https://lsv.uky.edu/scripts/wa.exe?A2=ind1607&L=MARKUP&P=R16310&I=-3&d=No+Match%3BMatch%3BMatches
As we discussed in the previous EDAG meeting, we're generally all in agreement that space with some kind of attribute seems to be the best way to do this; the important thing is to document if people know and want to mark the reason for the space, which would clarify the distinction between, e.g., a vacat and some formal feature of the support prior to the inscribing of the text. I'll email Markup in order to get some more examples and suggested vocabulary.
(Very) short prose added to the Guidelines page for vacat (other), along with several suggested values there.
Should we also add some suggested values to the schema, or is that best left completely open, do we think?
I wouldn't mind having these suggested values added to the schema, but on the other hand, I think it is ok to leave it open.
General consensus, at Feb. 20 EDAG, is that having at least some suggested values would be valuable. Addtionally these values would help to resolve questions raisedabout how to indicate indentation, etc., at FR79, since <space> allows for a number of attributes that cannot be placed on <lb>.
If we want to recommend a few values (and their definitions) to the ODD, I suggest values such as:
Last edit: BODARD Gabriel 2018-04-17
Will add a little more prose to make this clearer, re-paragraph a bit more to help clarify what we actually mean by
<space>
in EpiDoc