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
I believe that <floatingText> should claim membership of model.divTopPart (alongside elements like <opener>).
Use case:
I'm encoding a letter where there is a list written before the <opener> material. One might want to encode it as:
<div>
<head>A Heading</head>
<list>
<item>Item 1</item>
<item>Item 2</item>
<!-- many more -->
</list>
<opener>
<dateline><placeName>Newcastle</placeName>, <date>25 October 2024</date></dateline>
<salute>Dear Sir,</salute>
</opener>
<p>Please buy me the things on the list above.</p>
<closer>
<salute>With great regard,</salute>
<signed>James</signed>
</closer>
</div>
This of course won't be valid, since once you have a <list> you can't have something from further down the content model of <div> like model.common or model.global, for example an <opener> here or just a <salute> by itself.
I am not going to propose that we open up model.divTopPart to all sorts of other elements, as that way lies madness and ambiguous content models... However, given that it is easy to encounter other letters and similar documents which have embedded before the main content structural elements which could be seen as texts which interrupt the main text being encoded, I do think making <floatingText> available here is a suitable solution. i.e. in the case of the above:
<div>
<head>A Heading</head>
<floatingText>
<body>
<list>
<item>Item 1</item>
<item>Item 2</item>
<!-- many more -->
</list>
</body>
</floatingText>
<opener>
<dateline><placeName>Newcastle</placeName>, <date>25 October 2024</date></dateline>
<salute>Dear Sir,</salute>
</opener>
<p>Please buy me the things on the list above.</p>
<closer>
<salute>With great regard,</salute>
<signed>James</signed>
</closer>
</div>
To do this we would add <floatingText> to model.divTopPart and thus it would become a member of model.divTop.
There is another possibility which is to add it to the content model of <opener>. (It exists in <postscript> but not in <closer>.)
The text was updated successfully, but these errors were encountered:
I believe that
<floatingText>
should claim membership of model.divTopPart (alongside elements like<opener>
).Use case:
I'm encoding a letter where there is a list written before the
<opener>
material. One might want to encode it as:This of course won't be valid, since once you have a
<list>
you can't have something from further down the content model of<div>
like model.common or model.global, for example an<opener>
here or just a<salute>
by itself.I am not going to propose that we open up model.divTopPart to all sorts of other elements, as that way lies madness and ambiguous content models... However, given that it is easy to encounter other letters and similar documents which have embedded before the main content structural elements which could be seen as texts which interrupt the main text being encoded, I do think making
<floatingText>
available here is a suitable solution. i.e. in the case of the above:To do this we would add
<floatingText>
to model.divTopPart and thus it would become a member of model.divTop.There is another possibility which is to add it to the content model of
<opener>
. (It exists in<postscript>
but not in<closer>
.)The text was updated successfully, but these errors were encountered: