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
In BSI we encountered numbered list items split into separate rows. The understanding back then is that such practice is ad-hoccery and does not require a semantic encoding.
This is dirty: it is a table, with two distinct table headings, but it is also a list.
If it is underlyingly a list, it is a list with two different labels for two different hierarchical levels. We do already allow lists to have titles; we could allow the nested first list to have a label too, and then have it carry over implicitly. So:
.Targets for productive capacity (area A)
. increased value addition in natural resource-based industries
+
--
.Indicator
** industry, value added (constant 2000 USD)
--
which parses, right now, as:
<ol id="_b56b9ef3-4961-b505-1aad-8ebe735adabc" type="arabic">
<name>Targets for productive capacity (area A)</name>
<li><p id="_c2237243-bbab-d5a6-0b62-1bfb6a295a80">increased value addition in natural resource-based industries</p>
<ul id="_268ddabd-c682-060e-9141-9391c1ebd3f8">
<name>Indicator</name>
<li><p id="_79a89c53-721d-2620-3e78-cac8ad59d716">industry, value added (constant 2000 USD)</p>
</li>
</ul>
</li>
</ol>
I could take a render=table attribute, look for the titles in the two nested columns, and read the desired ordered list labels from Presentation XML (I've just added them there as li/@label attributes.) So yes, it is (now) doable. I don't consider this high priority though...
In BSI we encountered numbered list items split into separate rows. The understanding back then is that such practice is ad-hoccery and does not require a semantic encoding.
However, this is now officially an ISO sanctioned practice:
https://www.iso.org/ISO-house-style.html
I wonder if there is something semantic we can do about it.
BSI issue:
The text was updated successfully, but these errors were encountered: