metanorma-cc 1.4.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 56fef26c5b91b3bee1ea7a6ee062a171358e56ab8e64745d81b9ff16ede6f32d
+  data.tar.gz: 66eef153e867f2e5854c207059efa4bca7ffc1d5753a990f191711b1092ecf0e
+SHA512:
+  metadata.gz: 4296a74e2a8118436c957b6838230b7aaeda4dd8ee6a3319f4b9653c6557b847e01c2ca0bf8419b3bae30f09000b823a4a2cc2013a67302acea7c1e96c7a7a52
+  data.tar.gz: 36dd42a00a2eb5ba70264ea0871a936f6174dbf3ec1938047f063e21a1dbe70439853445a3c418a6d72d63dee2c20b969781cd14b9d5107cfaf17dd23c70708b

data/.github/workflows/macos.yml

@@ -0,0 +1,39 @@
+# Auto-generated by Cimas: Do not edit it manually!
+# See https://github.com/metanorma/cimas
+name: macos
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    paths-ignore:
+      - .github/workflows/ubuntu.yml
+      - .github/workflows/windows.yml
+
+jobs:
+  test-macos:
+    name: Test on Ruby ${{ matrix.ruby }} macOS
+    runs-on: macos-latest
+    continue-on-error: ${{ matrix.experimental }}
+    strategy:
+      fail-fast: false
+      matrix:
+        ruby: [ '2.6', '2.5', '2.4' ]
+        experimental: [false]
+        include:
+          - ruby: '2.7'
+            experimental: true
+    steps:
+      - uses: actions/checkout@master
+      - name: Use Ruby
+        uses: actions/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          architecture: 'x64'
+      - name: Update gems
+        run: |
+          sudo gem install bundler --force
+          bundle install --jobs 4 --retry 3
+      - name: Run specs
+        run: |
+          bundle exec rake

data/.github/workflows/ubuntu.yml

@@ -0,0 +1,53 @@
+# Auto-generated by Cimas: Do not edit it manually!
+# See https://github.com/metanorma/cimas
+name: ubuntu
+
+on:
+  push:
+    branches: [ master ]
+    tags:
+      - '*'
+  pull_request:
+    paths-ignore:
+      - .github/workflows/macos.yml
+      - .github/workflows/windows.yml
+
+jobs:
+  test-linux:
+    name: Test on Ruby ${{ matrix.ruby }} Ubuntu
+    runs-on: ubuntu-latest
+    continue-on-error: ${{ matrix.experimental }}
+    strategy:
+      fail-fast: false
+      matrix:
+        ruby: [ '2.6', '2.5', '2.4' ]
+        experimental: [false]
+        include:
+          - ruby: '2.7'
+            experimental: true
+    steps:
+      - uses: actions/checkout@master
+      - name: Use Ruby
+        uses: actions/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          architecture: 'x64'
+      - name: Update gems
+        run: |
+          gem install bundler
+          bundle install --jobs 4 --retry 3
+      - name: Run specs
+        run: |
+          bundle exec rake
+      - name: Trigger dependent repositories
+        if: github.ref == 'refs/heads/master' && matrix.ruby == '2.6'
+        env:
+          GH_USERNAME: ${{ secrets.PAT_USERNAME }}
+          GH_ACCESS_TOKEN: ${{ secrets.PAT_TOKEN }}
+        run: |
+          curl -LO --retry 3 https://raw.githubusercontent.com/metanorma/metanorma-build-scripts/master/trigger-gh-actions.sh
+          [[ -f ".github/workflows/dependent_repos.env" ]] && source .github/workflows/dependent_repos.env
+          for repo in $DEPENDENT_REPOS
+          do
+            sh trigger-gh-actions.sh $ORGANISATION $repo $GH_USERNAME $GH_ACCESS_TOKEN $GITHUB_REPOSITORY "{ \"ref\": \"${GITHUB_REF}\" }"
+          done

data/.github/workflows/windows.yml

@@ -0,0 +1,41 @@
+# Auto-generated by Cimas: Do not edit it manually!
+# See https://github.com/metanorma/cimas
+name: windows
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    paths-ignore:
+      - .github/workflows/macos.yml
+      - .github/workflows/ubuntu.yml
+
+jobs:
+  test-windows:
+    name: Test on Ruby ${{ matrix.ruby }} Windows
+    runs-on: windows-latest
+    continue-on-error: ${{ matrix.experimental }}
+    strategy:
+      fail-fast: false
+      matrix:
+        ruby: [ '2.6', '2.5', '2.4' ]
+        experimental: [false]
+        include:
+          - ruby: '2.7'
+            experimental: true
+    steps:
+      - uses: actions/checkout@master
+      - name: Use Ruby
+        uses: actions/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          architecture: 'x64'
+      - name: Update gems
+        shell: pwsh
+        run: |
+          gem install bundler
+          bundle config --local path vendor/bundle
+          bundle install --jobs 4 --retry 3
+      - name: Run specs
+        run: |
+          bundle exec rake

data/.gitignore

@@ -0,0 +1 @@
+.DS_Store

data/.hound.yml

@@ -0,0 +1,3 @@
+ruby:
+  Enabled: true
+  config_file: .rubocop.yml

data/.rubocop.yml

@@ -0,0 +1,10 @@
+# This project follows the Ribose OSS style guide.
+# https://github.com/riboseinc/oss-guides
+# All project-specific additions and overrides should be specified in this file.
+
+inherit_from:
+  - https://raw.githubusercontent.com/riboseinc/oss-guides/master/ci/rubocop.yml
+AllCops:
+  TargetRubyVersion: 2.3
+Rails:
+  Enabled: true

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at ronald.tse@ribose.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,11 @@
+Encoding.default_external = Encoding::UTF_8
+Encoding.default_internal = Encoding::UTF_8
+
+source "https://rubygems.org"
+git_source(:github) { |repo| "https://github.com/#{repo}" }
+
+gemspec
+
+if File.exist? 'Gemfile.devel'
+  eval File.read('Gemfile.devel'), nil, 'Gemfile.devel' # rubocop:disable Security/Eval
+end

data/LICENSE

@@ -0,0 +1,25 @@
+BSD 2-Clause License
+
+Copyright (c) 2018, Ribose
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/README.adoc

@@ -0,0 +1,61 @@
+= metanorma-cc: Metanorma processor for CalConnect standards
+
+image:https://img.shields.io/gem/v/metanorma-cc.svg["Gem Version", link="https://rubygems.org/gems/metanorma-cc"]
+image:https://github.com/metanorma/metanorma-cc/workflows/macos/badge.svg["Build Status (macOS)", link="https://github.com/metanorma/metanorma-cc/actions?workflow=macos"]
+image:https://github.com/metanorma/metanorma-cc/workflows/ubuntu/badge.svg["Build Status (ubuntu)", link="https://github.com/metanorma/metanorma-cc/actions?workflow=ubuntu"]
+image:https://github.com/metanorma/metanorma-cc/workflows/windows/badge.svg["Build Status (Windows)", link="https://github.com/metanorma/metanorma-cc/actions?workflow=windows"]
+image:https://codeclimate.com/github/metanorma/metanorma-cc/badges/gpa.svg["Code Climate", link="https://codeclimate.com/github/metanorma/metanorma-cc"]
+image:https://img.shields.io/github/issues-pr-raw/metanorma/metanorma-cc.svg["Pull Requests", link="https://github.com/metanorma/metanorma-cc/pulls"]
+image:https://img.shields.io/github/commits-since/metanorma/metanorma-cc/latest.svg["Commits since latest",link="https://github.com/metanorma/metanorma-cc/releases"]
+
+_Formerly known as_ `asciidoctor-csd`, `metanorma-csd`.
+
+== Functionality
+
+This gem processes http://asciidoctor.org/[Asciidoctor] documents following
+the Metanorma model for generating CalConnect Standards.
+
+The gem currently inherits from the https://github.com/metanorma/metanorma-standoc
+gem, and aligns closely to it. Refer to https://metanorma.com[] for guidance.
+
+== Usage
+
+The preferred way to invoke this gem is via the `metanorma` script:
+
+[source,console]
+----
+$ metanorma --type cc a.adoc                   # output HTML and PDF
+$ metanorma --type cc --extensions html a.adoc # output just HTML
+$ metanorma --type cc --extensions pdf a.adoc  # output just PDF
+$ metanorma --type cc --extensions xml a.adoc  # output Metanorma XML
+----
+
+The gem translates the document into Metanorma XML format, and then
+validates its output against the CC Metanorma XML document model; errors are
+reported to console against the XML, and are intended for users to
+check that they have provided all necessary components of the
+document.
+
+The gem then converts the XML into output formats such as HTML and PDF.
+
+=== Installation
+
+If you are using a Mac, the https://github.com/metanorma/metanorma-macos-setup
+repository has instructions on setting up your machine to run Metanorma
+scripts such as this one. You need only run the following in a Terminal console:
+
+[source,console]
+----
+$ bash <(curl -s https://raw.githubusercontent.com/metanorma/metanorma-macos-setup/master/metanorma-setup)
+$ gem install metanorma-cc
+----
+
+== Documentation
+
+See https://www.metanorma.com/author/cc/[Author CalConnect documents with Metanorma CC].
+
+== Examples
+
+* Example documents are avalable at the https://github.com/metanorma/mn-samples-cc[mn-samples-cc] repository.
+* Document templates are available at the https://github.com/metanorma/mn-templates-cc[mn-templates-cc] repository.
+

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "asciidoctor/csd"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/rspec

@@ -0,0 +1,18 @@
+#!/usr/bin/env ruby
+  
+# This file was generated by Bundler.
+#
+# The application 'rspec' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+require "pathname"
+ENV["BUNDLE_GEMFILE"] ||= File.expand_path(
+  "../../Gemfile", Pathname.new(__FILE__).realpath
+)
+
+require "rubygems"
+require "bundler/setup"
+
+load Gem.bin_path("rspec-core", "rspec")
+

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/docs/navigation.adoc

@@ -0,0 +1,8 @@
+---
+items:
+- title: Introduction
+  items:
+    - { title: Quickstart, path: quickstart/ }
+---
+
+= Navigation

data/docs/quickstart.adoc

@@ -0,0 +1,368 @@
+= Quickstart Guide for Metanorma-CSD
+
+Start using Metanorma-CSD to author CalConnect docs in these steps:
+
+. Get Metanorma running on your machine
+. Fetch and compile an example Metanorma-CSD document
+. Modify the document to fit your goals while keeping it valid AsciiCSD
+
+This guide assumes proficiency with the terminal,
+and uses the Docker option of running Metanorma
+(there’re other
+https://www.metanorma.com/overview/getting-started/[options of installing Metanorma],
+too).
+
+
+== Get Metanorma running on your machine
+
+Assuming you have Docker installed, it’s as easy as:
+
+[source,console]
+--
+docker pull ribose/metanorma
+--
+
+
+== Fetch and compile an example Metanorma-CSD document
+
+We’re going to use the vCard Format Specification sample document here.
+Clone the Metanorma-CSD repository and change into the directory with the example:
+
+[source,console]
+--
+git clone https://github.com/metanorma/metanorma-csd.git
+cd /spec/examples/
+--
+
+To compile the document, run the Docker container as follows:
+
+[source,console]
+--
+docker run -v "$(pwd)":/metanorma/ -w /metanorma ribose/metanorma metanorma -t csd -x xml,html,pdf,doc rfc6350.adoc
+--
+
+NOTE: If you use Metanorma-CLI instead of Docker,
+http://metanorma.com:4001/software/metanorma-cli/docs/usage/[see how to use the metanorma executable to compile documnts].
+
+
+== Write valid AsciiCSD
+
+A Metanorma-CSD is a file in AsciiDoc format with certain extensions
+specific to Metanorma as a whole and Metanorma-CSD in particular.
+(We call the format AsciiCSD for short.)
+
+
+=== AsciiDoc basics
+
+NOTE: Skip this section if you’re already familiar with AsciiDoc syntax.
+
+==== Inline formatting
+
+[source,asciidoc]
+--
+*bold emphasis*, _italic emphasis_, `monospace / code snippet`
+"`Typographic double quotes`", '`typographic single quotes`'
+Subscript: H~2~O; superscript: E=mc^2^
+--
+
+==== Sections, anchors and references
+
+[source,asciidoc]
+--
+== Section 1
+
+Content (see <<anchor>>)
+
+== Section 2
+
+=== Section 2.1
+
+[[anchor]]
+==== Section 2.2
+
+Content 2.2. http://www.calconnect.org/[CalConnect]
+--
+
+==== Lists and blocks
+
+[source,asciidoc]
+--
+* Unordered list item 1
+* Unordered list item 2
+
+. Ordered list item 1
+. Ordered list item 2
+
+Definition list:
+
+stem:[w]:: is the mass fraction of grains with defects in the test sample;
+stem:[m_D]:: is the mass, in grams, of grains with that defect;
+mag:: is the mass, in grams, of the aggregated test sample.
+--
+
+==== Tables, figures, footnotes
+
+A rather complex table:
+
+[source,adoc]
+----
+[[tableD-1]]
+[cols="<,^,^,^,^",headerrows=2]
+.Repeatability and reproducibility of husked rice yield
+|===
+.2+| Description 4+| Rice sample
+| Arborio | Drago footnote:[Parboiled rice.] | Balilla | Thaibonnet
+
+| Number of laboratories retained after eliminating outliers | 13 | 11 | 13 | 13
+| Mean value, g/100 g | 81,2 | 82,0 | 81,8 | 77,7
+|===
+----
+
+Images (figures) and footnotes:
+
+[source,adoc]
+----
+[[figureC-1]]
+.Typical gelatinization curve
+image::images/rice_image2.png[]
+footnote:[The time stem:[t_90] was estimated to be 18,2 min for this example.]
+----
+
+
+==== Admonition blocks, quotes & code listings
+
+Admonitions (notes, warnings, cautions, etc.) and examples:
+
+[source,adoc]
+----
+NOTE: It is unnecessary to compare rice yield across years.
+
+[example]
+5 + 3 = 8
+----
+
+Block quotes:
+
+[source,adoc]
+----
+[quote,ISO,"ISO7301,clause 1"]
+_____
+This Standard gives the minimum specifications for rice (_Oryza sativa_ L.)
+_____
+----
+
+Source code:
+
+[source,adoc]
+----
+[source,some-lang]
+------
+function () -> {}
+------
+----
+
+
+=== Extensions to AsciiDoc
+
+==== Document header & custom AsciiDoc attributes
+
+`:docnumber:`: CalConnect document number, as allocated by TCC.
+
+`:status:`: The status of the document can be one of:
+
+* proposal
+* working-draft
+* committee-draft
+* draft-standard
+* final-draft
+* published
+* withdrawn
+
+`:doctype:`: The type of the document can be one of:
+
+* standard
+* directive
+* guide
+* specification
+* report
+* amendment
+* technical-corrigendum
+
+`:technical-committee:`, `:technical-committee_N:` (where N is a positive integer):
+Technical committee; there can be more than one.
+
+`:draft:`: Enables comments in Word and XML.
+
+`:local-cache-only:`: Used with Metanorma under Docker to ensure bibliographic entries
+do not get unnecessarily fetched all the time.
+
+
+==== Foreword & Introduction
+
+Foreword must be put before the first real section/clause (the `==` one).
+
+----
+[[foreword]]
+.Foreword
+The Calendaring and Scheduling Consortium ("`CalConnect`") is global non-profit
+organization with the aim to facilitate interoperability of technologies across
+user-centric systems and applications...
+----
+
+Introduction comes after Foreword and is unnumbered (actually "`0`"):
+
+----
+[[introduction]]
+:sectnums!:     <== disables display of section number
+== Introduction
+
+<<ISO8601>> has been the international standard for date and time representations
+and is applied widely, including in the <<RFC5545>> and <<RFC6350>> standards
+...
+
+:sectnums:      <== re-enables display of section number
+----
+
+NOTE: Some ISO standards display Introduction section numbers (the "`0`") if there are
+too many sub-sections.
+
+
+==== Normative references & bibliography
+
+What is a normative vs informative reference?
+
+* A change to a normative reference requires updating of the document;
+* A change to an informative reference should not trigger a change in the document.
+
+
+Clause 2 must be this:
+
+----
+[bibliography]
+== Normative references
+
+* [[[ISO3696,ISO 3696]]], _Water for analytical laboratory use -- Test methods_
+----
+
+Last section must be this:
+
+----
+[bibliography]
+== Bibliography
+
+* [[[ISO5609,ISO 5609]]], _Soil for laboratory analysis -- Test methods_
+----
+
+NOTE: the Bibliography is identical in usage with the IETF RFC section "`Informative references`".
+
+
+==== Citations
+
+In a CSD you often want to cite external or internal references.
+
+Internal:
+[source,adoc]
+----
+[[dog-food]]
+== Dog food
+
+Dogs love food, not only bones. Mine especially loves eating Oreo's.
+
+== Living with your dog
+
+My dog, Cookie, loves to eat cookies (see <<dog-food>>).
+
+----
+
+
+External (remember to add the reference!):
+
+[source,adoc]
+----
+The quality requirements on wheat are described in <<ISO7301>>.
+
+In particular, those for bread wheat (T. aestivum) are given in
+<<ISO7301,clause=5.6>>.
+----
+
+
+==== Terms and definitions
+
+This must be clause 3.
+
+[source,adoc]
+----
+[[tda]]                      <= anchor if you want it
+[source=ISO8601-1]           <= allows inheriting terms and definitions from
+another document
+== Terms, definitions, symbols and abbreviations   <= can combine T&D and S&A
+
+=== Terms and definitions    <= the real T&D clause
+
+[[term-explicit]]            <= anchor if you want it
+==== explicit form           <= term item
+
+date and time representation that uses designator symbols to delimit
+time scale components
+----
+
+
+==== Term entry in T&D
+
+The structure is strict; the following illustrates the complete structure of a term entry.
+
+In the term source (`[.source]`), all content after the reference and the "`comma`" is about "`modifications`" to the original definition.
+
+[source,adoc]
+----
+[[paddy]]                  <= anchor
+=== paddy                  <= term
+alt:[paddy rice]           <= alternative term
+alt:[rough rice]           <= second alternative
+deprecated:[cargo rice]    <= deprecated term
+domain:[rice]              <= domain
+
+rice retaining its husk after threshing  <= definition
+
+[example]              <= example
+Foreign seeds, husks, bran, sand, dust.
+
+NOTE: The starch of waxy rice consists almost entirely of amylopectin. <= note
+
+[.source]
+<<ISO7301,section 3.2>>, The term "cargo rice" is shown as deprecated, <= source
+and Note 1 to entry is not included here.
+----
+
+
+==== Term entry sourced from IEC Electropedia (IEV)
+
+In the `[.source]`, a termbase such as the IEC Electropedia ("`IEV`") can be used, such as:
+
+[source,adoc]
+----
+[.source]
+<<IEV,clause "113-01-01">>, the term "space-time" is further explained
+in a new Note 2 to entry.
+----
+
+References to the specific IEC 60500 documents (where IEV terms came
+from) are automatically added to the Bibliography.
+
+
+==== Annex
+
+Annexes have to be placed before the "`Bibliography`".
+
+[source,adoc]
+----
+[[AnnexA]]
+[appendix,subtype=informative]
+== Example date and time expressions, and representations
+...
+----
+
+
+== Where next?
+
+* https://www.metanorma.com/overview/[Learn more about Metanorma]