Metanorma ISO document attributes

The standards agency publishing the standard. NOTE: Prior to 1.7.0, this field accepted comma-delimited values. NOTE: Prior to 2.7.0, this field accepted semicolon-delimited values. These are processed via CSV, recognising quote marks. This functionality is maintained in later versions, but other attributes of organisations are ignored (publisher_logo, pub-address, etc.)

The abbreviation of the publisher; if not provided, and the standards organisation is the home organisation of the standard, the SDO's abbreviation will already be available to Metanorma, and will be supplied.

The path to the logo of the publisher, specified as an image file; the numbers in the attribute align to the :publisher{_i}: attributes.

An organization sponsoring the publication of this document. NOTE: If a person needs to be nominated as the responsible party for a sponsoring organization, that person should be treated as a personal contributor (:surname{_i}:, :affiliation{_i}:, etc.), with a :role: attribute of enabler.

The path to the logo of the sponsoring organization, specified as an image file; the numbers in the attribute align to the :sponsor{_i}: attributes.

The copyright holder, if distinct from the publisher; can be multiple (semicolon-delimited: processed via CSV, recognising quote marks).. NOTE: Prior to 1.7.0, this field accepted comma-delimited values.

This attribute provides additional primary identifiers for the document, to be used alongside the native identifier generated from docnumber or docidentifier. It is intended for copublished standards with multiple primary identifiers. The list of identifiers is comma-delimited, and is specified as TYPE:VALUE; e.g. :docidentifier-additional: IDF:IDF 21, RFC:RFC 97.

The document edition.

The document version. The distinction between :edition: and :version: is specific to the SDO, but the overall trend is that :edition: corresponds to major versions, and are what corrigenda and amendments apply to, while :version: corresponds to minor versions and patches, including pre-publication versions (drafts). However, only :version: is used if the SDO uses semantic versioning throughout. Before :version: was added to Metanorma, :draft: fulfilled that function instead.

The date the document was last updated.

The ISBN-13 number of the document. This value is optional.

The ISBN-10 number of the document This value is optional.

The title of the document. If not supplied, the built-in AsciiDoc title (first line of document header) is used instead.

The title of the document in the language langcode. langcode is a ISO 639-1 code.

The title of the document in the language langcode, and of type type.

The title of the document in the language langcode, and of type type. Note: this was previously supported only in individual flavours.

The document type abbreviation; e.g. TN for "technical note". Can be used in document metadata, e.g. cover page. .

The status of the document; e.g. draft, published.

Also accepted: :docstage:

The document stage abbreviation; e.g. D for "draft". Can be used in document metadata, e.g. cover page. .

Whether the current document stage should be considered as published. Boolean. If not provided, and if there is no setting specific to the flavor, the default is that only the stage "published" is considered published.

Comma-delimited list of the statuses recognised as valid for this document, superseding the flavour's own repertoire in status validation. Normally set by a Metanorma taste rather than by authors: a taste that defines its own stages advertises through this attribute the base stages it maps them to, so that the underlying flavour does not report them as unrecognised.

The iteration of a stage, in case there have been multiple drafts (e.g. 2 on a CD: this is the second iteration through the CD stage).

Comma-delimited list of keywords associated with the document.

If present, reviewer notes will be rendered (otherwise those are suppressed). Is also ued as a legacy equivalent of :version:.

document identifier that the current document is a part of.

document identifier that the current document is a translation of.

The flavor of Metanorma used to compile the document; e.g. iso, nist, ogc. Needs to be a supported version of the document.

Also accepted: :flavor:

Legacy names: :mn-document-class:, :mn-flavor:

Alias of :document-class:

The output formats to generate for the document, comma-delimited; e.g. xml,presentation,html,doc,pdf. The formats supported vary for each flavor, but all flavors support xml (Semantic XML), presentation (Presentation XML), and one of html or pdf.

Legacy names: :mn-output-extensions:

(Optional) Directory in which images are located: all local image file locations are prefixed with this directory. Accepts a directory path.

Instructs Metanorma to not generate Word and HTML output, means only XML output will be generated.

Suppress document validation.

Terms (and symbols) are indexed automatically in postprocessing. See automatic terms indexing.

Output the bibliographic record describing the document as a Relaton XML file (with the suffix .rxl).

Legacy names: :mn-relaton-output-file:

If set, do not use the relaton or iev gem functionality to look up ISO and IEV references online, nor the cache of relaton and iev searches.

Override the publication date used for the bibliographic cutoff, instead of deriving it from the document's own date attributes. Accepts a date (YYYY, YYYY-MM, or YYYY-MM-DD); the value none (or false) disables the cutoff entirely, so references resolve to their latest editions and current status.

If set, use the relaton and iev gem functionality to look up ISO and IEV references online, but do not use the cache of relaton and iev searches.

Use the local Relaton and iev search caches to override the global relaton and iev search caches. If a directory name is given for the attribute, that name overrides relaton as the cache name.

Use the local Relaton and iev search caches to the exclusion of the global relaton and iev search caches. If a directory name is given for the attribute, that name overrides relaton as the cache name.

If set, delete and reinitialise the cache of Relaton searches.

Allows specification of an external bibliographic file to be imported. The value of the field is the file name. If the format also needs to be specified, this is done as file=PATH/TO/FILE,format=FORMAT. Valid formats are follows.

bibtex

The BibTeX format. Currently, only this is supported as a format, all other formats will raise an error.

Allows specification of multiple external bibliographic files to be imported. The different bibliographic sources are differentiated through the value of the {id} identifier.

:relaton-data-source-bib1: PATH/TO/FIRST/FILE
:relaton-data-source-bib2: PATH/TO/SECOND/FILE

If set to false, do not sort the bibliography; references are left in document order. Sorting is on by default.

Sort bibliographies in the document according to criteria set by the flavor Default: true. .

Override the publisher sort ranking for the bibliography, one attribute per publisher. The attribute-name suffix {abbrev} is the publisher's abbreviation; the value is the sort rank (lower sorts earlier) followed by the publisher's full name, separated by a colon ({rank}: {name}). A reference is matched to a publisher by its abbreviation (case-insensitive) or its name; matched publishers sort in the given rank order, followed by other standards, then other references. This is the mechanism a Metanorma taste uses to set a house bibliographic sort order: the taste configuration compiles to these document attributes. Because they are ordinary document attributes, an author can equally set them directly in a single document to override the sort order for that document alone.

:sort-biblio-OIML: 1: International Organization of Legal Metrology
:sort-biblio-ISO: 2: International Organization for Standardization
:sort-biblio-IEC: 3: International Electrotechnical Commission

Override the default configuration of Relaton Render selectively, with attributes from the named configuration YAML file. See Relaton Render specification for description of the configuration file format. We recommend you inspect the configuration compiled into the flavor gem (lib/relaton/render/config.yml) and include modifications of that in the override config file.

Do not translate Asciimath in the document to MathML.

Legacy names: :mn-keep-asciimath:

By default, MathML in the Metanorma XML has equivalent AsciiMath added to it in a comment. This AsciiMath can be used as an accessibility alternative to the MathML expression. The generation of this AsciiMath can be suppressed.

(Defaults to asciimath) The default language for stem:[...] and [stem] blocks expressions in the document. (AsciiMath, MathML, or LaTeX). For example, if you want the stem expressions in your document to be interpreted as LaTeX by default, use :stem: latexmath.

Read more about mathematical expressions.

Sets the formatting options for the number:[] command in the document. Please refer to the dedicated section at numbers for usage.

:number-presentation: notation=e,exponent_sign=plus,precision=4

Sets the formatting options for the number:[] command in the document as profile {NAME}. Please refer to the dedicated section at numbers for usage.

:number-presentation-profile-3: notation=scientific,exponent_sign=nil,decimal=","

Sets the formatting options for numbers contained in formulas. Please refer to the dedicated section at numbers in formulas.

Name of YAML language template file. Use if you wish to output an standard in a language that's not supported out of the box. For more on how to customize localization, see Localization.

Two-letter code (ISO 639-1) of the language the document is written in. Defaults to en.

The script of the document (ISO 15924). Defaults to Latn. Must be supplied as Hans for Simplified Chinese.

The locale of the document (currently expected to be a two-letter country code, ISO 3166-1 alpha-2).

File containing predefined text of document, in Metanorma XML. The document predefined text needs to follow the structure described in Predefined text; compare examples of Metanorma predefined text files such as that in ITU .

Template for how to present localized numbers. The localization template string is in the following form: :localize-number: +++#,##0.### ###+++ TIP: See Number localization for how numbers are localized in Metanorma.

Comma-delimited list of values, relating to name as semantic metadata about the document. Stored in the document under //metanorma-extension/semantic-metadata/{name}, with repeating tags for each value.

Comma-delimited list of values, relating to name as presentation metadata about the document. Stored in the document under //metanorma-extension/presentation-metadata/{name}, with repeating tags for each value.

The following instances of generic metadata are applicable to all flavors of Metanorma; other instances are specific to flavors, and are documented there:

This document is to be compiled without adding initial document boilerplate to it. This is used for compiling Metanorma AsciiDoc boilerplate documents themselves.

Specify how the document type is to be rendered. This overrides the language-specific internationalization of the supplied document type, and is used in Metanorma tastes, to override the base flavor document type rendering.

Specify a custom character set for Unicode "Private Use Area" (PUA) character codepoints

Specify height and width of the publisher logo, for each of the standard output formats of Metanorma. The publishers are read in the same sequence for logo attributes as they are for publisher names and abbreviations, and the numbering includes the primary publisher of the document as the first publisher (for which a logo typically does not need to be specified.)

Specify the characters to be used as bullets for unordered lists, as a comma-delimited list of strings, each string corresponding to a deeper level of list. The bullet list rotates once the list is exceeded. NOTE: Custom unordered list bullets are only processed for PDF output.

Delimiter between the line heading giving the number of an annex, and the title of the annex (Metanorma XML, default <br/><br/>) .

Presentation XML Liquid template for middle title (document title at the start of the main section of the document) (Metanorma XML, default "<p class='zzSTDTitle1'>{{ doctitle }}</p>") . Refer to Default metadata values for the typical values that can be used in metadata-driven Liquid templates under Metanorma.

Add the Unicode character as an icon in front of the label for all admonitions of type {type}; overrides any value given in admonition-icon under the i18n internationalization file . If the admonition type contains spaces, replace them with underscores in the attribute name: an admonition of type Safety Precautions is matched by :presentation-metadata-admonition-icon-safety_precautions: .

Whether the details element in HTML (used for collapsible examples) should be open or closed for HTML documents. Defaults to true, and corresponds to <details open="open"> vs <details>. .

The URI to which this standard is published.

The URI to which the (Metanorma) XML representation of this standard is published.

The URI to which the HTML representation of this standard is published.

The URI to which the PDF representation of this standard is published.

The URI to which the DOC representation of this standard is published.

The URI to which the Relaton XML representation of this standard is published.

The year which will be claimed as when the copyright for the document was issued.

The date on which the publication of the standard was announced by the issuing authority.

The date on which the document was announced as forthcoming.

The date on which the standard was issued (authorised for publication by the issuing authority).

The date on which the standard was published (distributed by the publisher).

The date on which the standard became active.

The date on which the first version of the standard was created.

The date on which the current version of the standard was updated.

The date on which the current version of the standard was corrected, without that correction amounting to a distinct update.

The date on which the standard was obsoleted/revoked.

The date on which the standard was reviewed and approved by the issuing authority.

The date on which the standard was last renewed without any changes in content.

The date on which the unpublished standard was last circulated officially as a preprint. For standards, this is associated with the latest transition to a formally defined preparation stage, such as Working Draft or Committee Draft.

The date on which the standard was last accessed by the compiler of the bibliography; e.g. for a cited online resource, the date on which the document author viewed the resource.

An arbitrary date in the production of the standard. Content of the attribute should be a token, giving the type of date, then space, then the date itself. Multiple dates can be added as :date_2:, :date_3:, etc.

The date on which the voting process starts for this document.

The date on which the voting process ends for this document.

The name of the relevant editorial group. The document attribute name for editorial groups varies by flavor, and there can be multiple types of editorial group, each with its own document attribute; see Contributor metadata: Groups for the value for each flavor.

The identifier of the editorial group.

The type of the editorial group. Typically this is used as the abbreviation prefixed to the editorial group number.

The agency that the editorial group lies under, if it is other than the home agency (the publisher of the document). Only needed for multiple editorial groups.

The abbreviation of the agency that the editorial group lies under. In most flavors, the abbreviation of the SDO is already available for lookup in Metanorma, and users need not provide this attribute.

The logo of the editorial group, specified as an image file.

Comma-delimited list of committee types to be recognized for the document. Overrides the preset committee types set for the flavor. .

The organization authoring the standard. This document attribute **should not** be provided if the authoring organization is identical to the publishing body, as its value is automatically set to that of :publisher:. Use :corporate-author: **only when** a standard is authored or co-authored by an agency distinct from the publishing body, and only the publishing agency is credited as the publisher. Multiple agencies can be specified as corporate authors (similar to :publisher:). The first agency specified is expected to be the publishing body. Use :corporate-author_2:, :corporate-author_3:, etc. for additional agencies. NOTE: For personal authors, use :fullname: or :surname: and :givenname: instead.

The full name of a person who is a contributor to the document. A second person is indicated by using a numeric suffix: :fullname:, :fullname_2:, fullname_3:, &c. The same convention applies to all the following attributes. (This and the other personal name attributes are not displayed in all standards.)

The surname of a person who is a contributor to the document.

The given name(s) of a person who is a contributor to the document.

The initials(s) of a person who is a contributor to the document.

Credentials of the person, appearing after their name in Metanorma flavour-specific contexts.

The credentials of the person (e.g. "PhD, F.R.Pharm.S"); these are often displayed inline with the person's name.

The role of a person who is a contributor to the document. By default, they are coded as an editor; they can also be represented as an author, or (if they are the responsible party for a sponsoring organization) enabler. Is meant to draw from the constrained vocabulary of Relaton: author, editor, adapter, translator, performer, realizer, publisher, distributor, owner, authorizer, enabler, subject; see Relaton specification.

A more detailed description of the role of a person who is a contributor to the document.

The organization that a person who is a contributor to the document is affiliated with.

The abbreviation of the organization that a person who is a contributor to the document is affiliated with.

The subdivision of the organization that a person who is a contributor to the document is affiliated with. The subdivisions can be multiple (semicolon-delimited: processed via CSV, recognising quote marks), and they can also be hierarchical, with multiple levels of subdivision (comma-delimited, from larger to smaller) ; the different hierarchical levels can optionally be prefixed with type and a colon.

The logo of the organization that a person who is a contributor to the document is affiliated with, specified as an image file.

The position of the person within the organization.

The organizational address of a person who is a contributor to the document. Mutually exclusive with street/city/region/country/postcode.

The street component of the organization address of a person who is a contributor to the document.

The city component of the organization address of a person who is a contributor to the document.

The region component of the organization address of a person who is a contributor to the document.

The country component of the organization address of a person who is a contributor to the document.

The postcode component of the organization address of a person who is a contributor to the document.

The URI of a person who is a contributor to the document.

The email of a person who is a contributor to the document.

The phone number of a person who is a contributor to the document.

The fax number of a person who is a contributor to the document.

The subdivision of the organization that is responsible for this document. The subdivisions can be multiple (semicolon-delimited: processed via CSV, recognising quote marks), and they can also be hierarchical, with multiple levels of subdivision (comma-delimited, from larger to smaller) ; the different hierarchical levels can optionally be prefixed with type and a colon.

The abbreviation of the subdivision of the organization that is responsible for this document.

The address of the organization responsible for this document, if it overrides the default.. The number of this and subsequent attributes aligns with the number of :publisher{_i}:

:pub-address: 1 Infinity Loop + \
California + \
United States of America

NOTE: As of 2.7.0, if :publisher: is semicolon-delimited, instead of using numbered attributes, this and subsequent publisher attributes are ignored.

The phone number of the organization responsible for this document, if it overrides the default.

The fax number of the organization responsible for this document, if it overrides the default.

The email of the organization responsible for this document, if it overrides the default.

The URI of the organization responsible for this document, if it overrides the default.

The address, phone number, fax number, email, URI of an organization sponsoring this document.

See :sponsor-address{_i}:

See :sponsor-address{_i}:

See :sponsor-address{_i}:

See :sponsor-address{_i}:

The subdivision of the organization that is sponsoring this document. The subdivisions can be multiple (semicolon-delimited: processed via CSV, recognising quote marks), and they can also be hierarchical, with multiple levels of subdivision (comma-delimited, from larger to smaller) ; the different hierarchical levels can optionally be prefixed with type and a colon.

The organisation that authorised this document.

The path to the logo of the authorizing organization, specified as an image file; the numbers in the attribute align to the :authorizer{_i}: attributes .

The address, phone number, fax number, email, URI of an organization authorizing this document.

See :authorizer-address{_i}:

See :authorizer-address{_i}:

See :authorizer-address{_i}:

See :authorizer-address{_i}:

The subdivision of the organization that is authorizing this document. The subdivisions can be multiple (semicolon-delimited: processed via CSV, recognising quote marks), and they can also be hierarchical, with multiple levels of subdivision (comma-delimited, from larger to smaller) ; the different hierarchical levels can optionally be prefixed with type and a colon.

Semicolon-delimited listing of fonts to be used for this document, in addition to the fonts predefined for the flavour.

Valid values are font names supported by Fontist. The full font name listing is available from the Fontist Formulas repository.

NOTE: This is currently only used in PDF generation.

:fonts: Euphemia
:font-license-agreement: agree-to-terms

The response to the license agreement prompt by fontist for the fonts specified in :fonts:.

Valid values are:

no-install-fonts

(default) do not install any additional fonts, even when listed in :fonts:.

agree-to-terms

agree to all terms of the fonts that will be installed in an unattended manner.

continue-without-fonts

do not warn if a font is not available on the system.

Font for body text; will be inserted into CSS, overriding the default set for the particular Metanorma flavour.

Font for headers; will be inserted into CSS, overriding the default set for the particular Metanorma flavour.

Font for monospace; will be inserted into CSS, overriding the default set for the particular Metanorma flavour.

SCSS stylesheet to use for HTML output. Defaults to built-in stylesheet for the particular Metanorma flavour. Overriding is not recommended.

Legacy names: :htmlstylesheet:

CSS stylesheet to use for HTML output, inserted after the built-in stylesheet for the particular Metanorma flavour, and can be used to override it.

Legacy names: :htmlstylesheet-override:

HTML template for cover page. Defaults to built-in template for the particular Metanorma flavour. Overriding is not recommended.

Legacy names: :htmlcoverpage:

HTML template for introductory section. Defaults to built-in template for the particular Metanorma flavour. Overriding is not recommended.

Legacy names: :htmlintropage:

JavaScript scripts for HTML output. Defaults to built-in scripts for the particular Metanorma flavour. Overriding is not recommended.

JavaScript scripts for HTML output. Inserted after any built-in scripts for the particular Metanorma flavour, and can be used to override them.

JavaScript scripts for HTML to PDF output. Defaults to built-in scripts for the particular Metanorma flavour. Overriding is not recommended.

PDF document page size. Can be used to override the page size in built-in stylesheet for the particular Metanorma flavour. Valid values are: Letter, letter, A4 or a4.

Letter

letter

A4

a4

XSLT stylesheet to use for PDF output. Defaults to built-in stylesheet for the particular Metanorma flavour. Overriding is not recommended.

Legacy names: :pdfstylesheet:

XSLT stylesheet to use for PDF output, inserted after the built-in stylesheet for the particular Metanorma flavour, and can be used to override it.

Legacy names: :pdfstylesheet-override:

Primary SCSS stylesheet to use for Word output. Defaults to built-in stylesheet for the particular Metanorma flavour. Overriding is not recommended.

Legacy names: :wordstylesheet:

Secondary SCSS stylesheet use for Word output. Defaults to built-in template for the particular Metanorma flavour. Overriding is not recommended.

Legacy names: :standardstylesheet:

CSS stylesheet to use for Word output, inserted after the built-in stylesheet for the particular Metanorma flavour, and can be used to override it.

Legacy names: :wordstylesheet-override:

Header and footer file for Word output. Defaults to built-in template the particular Metanorma flavour. Overriding is not recommended.

Word template for cover page. Defaults to built-in template for the particular Metanorma flavour. Overriding is not recommended.

Legacy names: :wordcoverpage:

Word template for introductory section. Defaults to built-in template for the particular Metanorma flavour. Overriding is not recommended.

Legacy names: :wordintropage:

Word CSS selector for unordered lists in supplied stylesheets. Defaults to value for built-in stylesheet. Overriding is not recommended.

Word CSS selector for ordered lists in supplied stylesheets. Defaults to value for built-in stylesheet. Overriding is not recommended.

Comma-delimited list of image locations, for images to be included on the (PDF) cover page. All image locations are relative to the source document. Currently only supported for BSI, ITU, JIS, Plateau. If the supplied image(s) is to replace the cover page(s) of the document in its entirety, and already includes title information, add the attribute :presentation-metadata-full-coverpage-replacement: true (supported for all flavours).

Same, for images to be included on the (PDF) inside cover page. Currently only supported for BSI.

Same, for images to be included on the (PDF) Table of Contents side page. Currently only supported for BSI.

Same, for images to be included on the (PDF) back page. Currently only supported for BSI, JIS.

Encode all images in Metanorma XML and HTML output as inline data-URIs. Defaults to true..

Set the maximum permitted size of a Data URI-encoded image, in bytes. Defaults to 13981013 bytes (size of the Base-64 encoding of a 10 MB image). If set to 0, no maximum is enforced..

Encode all attachments in Metanorma XML as inline data-URIs. Defaults to true..

Profile of the 0 software library to apply for SVG validation and repair. See SVG Profiles for the available profile values. Metanorma by default uses the metanorma profile by default, except for IETF, which uses svg_1_2_rfc.

Format to generate PlantUML diagrams as. Legal values are png, svg. Defaults to png..

png

svg

Override the default rendering style of internal cross-references to other locations in the document. Available styles as follows:

short

(default) the clause type and number is used as the cross-reference.

Example of a cross-reference rendered in the "short" style

"Clause 3.1.2"

basic

the title of the clause is used as the cross-reference.

Example of a cross-reference rendered in the "basic" style

"Other considerations"

full

combines the title with the clause type/number cross-reference.

Example of a cross-reference rendered in the "full" style

"Clause 3.1.2, Other considerations"

idmetanorma-standoc ≥ v2.2.7

the cross-reference is to be rendered as the target anchor identifier (or any identifier aliasing the anchor).

Example of a cross-reference rendered in the "id" style

The following cross-reference:

[[my-anchor]]
=== My title
...

=== Another place
<<my-anchor>>

Renders the cross-reference as:

"my-anchor"

Override the default rendering style of cross-references to bibliographic entries . The legal values for such override are drawn from General citation style types.

Override the default rendering style of source references to bibliographic entries . The legal values for such override are drawn from General citation style types.

(optional) Base identifier pattern for ModSpec instances throughout the document. The attribute value provides a prefix that will be removed from all ModSpec instance identifiers used to cross-reference ModSpec instances. The specification of the pattern only affects the rendering of cross-references, not the underlying XML representation of the ModSpec instances. See more details at ModSpec identifier base.

(optional) A comma-delimited list of Metanorma block names, which should have numbering suppressed throughout the document. Typically will be used for sourcecode fragments: :block-unnumbered: sourcecode.

Apply “smart quotes” and other auto-formatting to the XML output (and hence the downstream outputs). Available values below:

• " and ' followed by space, with optional punctuation intervening, are treated as closing,

and converted to smart closing quotes ” and ’.

• " and ' preceded by space, with optional punctuation intervening, are treated as opening,

and converted to smart opening quotes “ and ‘.

• Midword apostrophes are treated as closing: Sana'a becomes Sana’a.
• Initial apostrophes before numerals are treated as closing: '80s becomes ’80s.
• There are many possible exceptions to these default rules, such as initial apostrophes

(fish ’n’ chips), and quote pairs used to illustrate the punctuation (Use smart quotes (" ")). For such cases, use either real smart quotes (the literal characters “ ” ‘ ’) or the Asciidoc ASCII codes, "` `", '` `'

The smart quotes converted by Metanorma postprocessing are specifically those of English. Other languages' smart quotes will need to be entered as the correct characters.

NOTE: :smartquotes: is a document-wide toggle. To keep specific runs of text as straight quotes while the rest of the document remains smart-quoted — for example, literal characters quoted from a specification, such as PDF string-delimiter operators — use 1.

true

(default) Smart quotes are not applied to the following type of text:

• text in source code;
• text in pseudo-code;
• text in monospace.

false

The AsciiDoc default is used to generate smart quotes: "` `", '` `'. The rules for smart formatting follow the sterile gem, and are given in smart_format_rules.rb. In particular:

Number of table of contents levels to render. Accepts an integer value. (default: 2). Can be overridden with output-specific options (htmltoclevels, doctoclevels).

Number of table of contents levels to render in HTML output; used to override :toclevels: for HTML output. Accepts an integer value. (default: 2). Formerly :htmltoclevels:.

Number of table of contents levels to render in Microsoft Word "DOC" output; used to override :toclevels: for Word DOC output. Accepts an integer value. (default: 2). Formerly :doctoclevels:.

Number of table of contents levels to render in PDF output; used to override :toclevels: for PDF output. Accepts an integer value. (default: 2)

Introduce table of contents for figures. No attribute value needed. Only numbered and/or captioned figures are included. Disabled if given the value false.

Introduce table of contents for tables. No attribute value needed. Only numbered and/or captioned tables are included. Disabled if given the value false.

Introduce table of contents for examples. No attribute value needed. Only numbered and/or captioned examples are included. Disabled if given the value false.

Introduce table of contents for requirements, recommendations, and permissions. No attribute value needed. Only numbered and/or captioned requirements, recommendations, and permissions are included. Disabled if given the value false.

If present, long strings in table cells are broken up on rendering, to help tables fit within the page width. No attribute value needed.. The current behaviour is: strings are broken by zero-width spaces; words are broken up every 10 characters on punctuation (e.g. URIs on / ), and every 20 characters if there is no punctuation in the word, in order to deal with very narrow columns. (Because the break is zero-width, it will not be visible unless it coincides with the end of a column.)

Initial delimiter for markup inserted in sourcecode

Final delimiter for markup inserted in sourcecode

Whether to use a source highlighter for sourcecode; default value is true

Provided a source highlighter is being used, whether to display line numbers; default value is false

(optional) The document is rendered in “bare form” -- without the cover page, boilerplate, or introductory text expected of a complete document. This is typically used for HTML output, e.g. clauses as standalone documents, or document attachments.

(optional) All media paths in the XML path are relative to the given directory; used when the Metanorma XML file to be processed is not necessarily in the same directory as the source Metanorma AsciiDoc file, and the media file paths are given as relative and not absolute file locations (and are not encoded as data URIs via :data-uri-image:).

Filter from error log all warnings at the given severity level or above it. See Validation for valid values.

Filter from error log all warnings belonging to one of the named categories; comma-delimited. See Validation for valid values.

Filter from error log all warnings with the identifiers of individual errors to exclude (comma-delimited). See Error ID. .

Specify encryption of PDF output.

true

Applies encryption to PDF output.

false

Do not encrypt PDF output. (default)

Specify encryption strength.

256

Use 256-bit AES keys (default)

128

Use 128-bit AES keys.

Specify user password needed to open the encrypted PDF document. The attribute value sets the user password.

Specify owner password to bypass restrictions on encrypted PDF document. The attribute value sets the owner password.

Allow content to be copy-pasted from the PDF document.

true

Content can be copy-pasted from the PDF document. (default)

false

Content cannot be copy-pasted from the PDF document.

Allow content of the PDF document to be edited.

true

Content of the PDF document can be edited. (default)

false

Content of the PDF document cannot be edited.

Allow inserting, deleting, or rotating pages in the PDF document.

true

Inserting, deleting or rotating pages in the PDF document is allowed. (default)

false

Inserting, deleting or rotating pages in the PDF document is disallowed.

Allow annotations and signatures to be added to the PDF document.

true

Annotations and signatures can be added to the PDF document. (default)

false

Annotations and signatures cannot be added to the PDF document.

Allow PDF document to be printed, physically or to a file.

true

PDF content can be printed, physically or to a file. (default)

false

PDF content cannot be printed, physically or to a file.

Allow PDF document to be printed in high quality.

true

PDF content can be printed in high quality. (default)

false

PDF content cannot be printed in high quality.

Allow forms to be filled in the PDF document.

true

Forms in the PDF document can be filled in. (default)

false

Forms in the PDF document are read-only, they cannot be filled in.

Allow text and graphics extraction from the PDF document for accessibility purposes.

true

Text and graphics can be extracted from the PDF document. (default)

false

Text and graphics cannot be extracted from the PDF document.

Specify encryption of the metadata stream.

true

The PDF metadata stream will be encrypted. (default)

false

The PDF metadata stream will not be encrypted.