-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expansion in scope of notes #8
Comments
Let's say basicdoc.
I wonder what sort of constraints are actually helpful. For example, a table inside a note inside a table seems to be the wrong thing to allow. Maybe we want a restricted set to be available within these specific types of notes.
I think we either do indentation or restrict them within a table to enforce indentation. ISO and IEC Directives, for example, use a "bordered container" to differentiate them against content text.
This I think depends on the usage of the author. Un-bordered "lists" could usually be implemented as definitions lists instead of needing a table.
I suppose we need a convention on how to name things within a Note. Let me ask the ISO Editor and revert on this. |
BTW, NOTEs/EXAMPLEs are not meant to contain everything. The ISO Editor previously stated (which is documented on metanorma.com) that NOTEs/EXAMPLEs can contain:
The only restriction is that they shall be purely informative statements of facts, therefore no requirements, recommendations or permissions are allowed (see DP2, 2018, 24.5 and 25.5). They are supposed to provide supplementary information; the documents shall be usable without NOTEs/EXAMPLEs. |
@opoudjis from ISO:
=> Tables/Figures should not be sub-elements of NOTE/EXAMPLE.
=> They are numbered as independent elements within the document. If you want a table/figure in NOTE/EXAMPLE it should be through a reference.
=> Tables cannot contain other tables. Figures should not belong to tables.
=> Table and Figures must ALWAYS be numbered as first level elements: e.g. Table X, Figure X. |
From ISO on table borders inside NOTE/EXAMPLEs:
|
@opoudjis this is now actionable. |
Tables and figures will be permitted within notes and examples in basicdoc. They will be excluded in standoc. Notes will include: formulas, lists, blockquotes. |
We allow source code within notes, but we cannot allow it to be captioned, just as we do not when source code is within tables. Adding note to labelled_ancestor(), the list of blocks that do not allow their descendants to have their own caption. |
Have tested in ISO: the blocks within a note are coloured in HTML as a single block In Word, lists and blockquotes are in smaller font, formulas and sourcecode are not. None of them are indented. |
We will indent non-paragraphs contained within notes in Word. We will try to enforce smaller font in formulas and sourcecode within notes. |
Until now, notes have been restricted to being runs of paragraphs, and they can appear attached underneath any other block.
Recent feedback obtained by ISO is that notes and examples should be treated the same, as containing any number of different blocks, including:
As it happens, the Asciidoctor format will permit this kind of embedding in its multi-block notes, so notes looking like that will be converted successfully into XML. However there is no provision in the Metanorma grammar for this, and there is no provision in rendering.
Taking account of such notes will generate a lot of work, which must not be underestimated, and it cannot proceed until the following questions are resolved.
The text was updated successfully, but these errors were encountered: