You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, <note>s can contain paragraphs and other "component-level elements", but cannot contain openers or closers; however, there are cases where footnotes are certainly signed. For example, from The Lyon in Mourning:
Here, you can see a footnote denoting editorial intervention by Robert Forbes who (to prove authenticity) signs the note. It's important for the project that we capture which notes had been signed (and by whom), but this encoding is invalid:
<note>
<p>Here ended Belfinlay's Hand-writing &
<lb/>what follows I took from the Mouth of
<lb/>Capn Donald Roy MacDonald.</p>
<closer>
<signed>Robert Forbes, A:M</signed>
</closer>
</note>
At present, the content model of <note> is macro.specialPara, which "defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements." That content model is:
It's used by a whole host of elements, though, so I'm not sure whether it makes more sense to special-case <note> (and add model.divBottomPart to its content model) or if it ought to be part of macro.specialPara (which is used by things like <quote> and <item> which I could imagine containing closers and signed, but I don't have any examples at hand).
The text was updated successfully, but these errors were encountered:
At the moment,
<note>
s can contain paragraphs and other "component-level elements", but cannot contain openers or closers; however, there are cases where footnotes are certainly signed. For example, from The Lyon in Mourning:Here, you can see a footnote denoting editorial intervention by Robert Forbes who (to prove authenticity) signs the note. It's important for the project that we capture which notes had been signed (and by whom), but this encoding is invalid:
At present, the content model of
<note>
is macro.specialPara, which "defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements." That content model is:It's used by a whole host of elements, though, so I'm not sure whether it makes more sense to special-case
<note>
(and add model.divBottomPart to its content model) or if it ought to be part of macro.specialPara (which is used by things like<quote>
and<item>
which I could imagine containing closers and signed, but I don't have any examples at hand).The text was updated successfully, but these errors were encountered: