spec-up-t 0.11.1

package/single-file-test/spec.md

@@ -0,0 +1,536 @@
+Spec-Up Example
+==================
+
+**Specification Status:** Draft
+
+**Latest Draft:**
+  [https://identity.foundation/spec-up](https://identity.foundation/spec-up)
+
+Editors:
+~ [Daniel Buchner](https://www.linkedin.com/in/dbuchner/)
+
+Participate:
+~ [GitHub repo](https://github.com/decentralized-identity/spec-up)
+~ [File a bug](https://github.com/decentralized-identity/spec-up/issues)
+~ [Commit history](https://github.com/decentralized-identity/spec-up/commits/master)
+
+------------------------------------
+
+## Abstract
+
+Let's face it, other tools and generators for writing technical specifications aimed at standards bodies or industry groups are cumbersome, underwhelming, and lack the features you might want in a technical specification document. Spec-Up's goal is to deliver you a better spec-writing experience with far less effort and tedium than other tools in the ecosystem. Spec-Up is a simple tool that auto-generates great specs from markdown. The version of markdown Spec-up uses contains all the same features you might expect from common implementations, like GitHub, but adds much more, including notice blocks, complex tables, charts, advanced syntax highlighting, UML diagrams, etc.
+
+## Getting Started
+
+Using Spec-Up is easy peasy lemon squeezy:
+
+1. `npm install spec-up`
+2. Create a `specs.json` file **in the root folder of your repository** to specify configuration values used in the generation of your spec documents. The values in your `specs.json` file include things like where your spec's markdown files are located, where to output the generated spec document, and various metadata values used in rendering, such as the title, logo, and repo links for each of your specs. The following are the required/optional fields supported in the `specs.json` config file:
+
+    - **`spec_directory`** _(STRING, required)_ - You must specify the **repo-root-relative** location of your spec's markdown file directory. You ****MUST**** name your spec's markdown file `spec.md` and locate it in your `spec_directory` for the tool to automatically find and use it for rendering. If you want to use a different name for the markdown file, or you have multiple markdown files you would like the tool to assemble into one document, you must specify them using the optional`markdown_paths` field described below. See the "multi-file" example in the spec-up repo.
+    - **`title`** _(STRING, required)_ - You must add a title for your spec, which will be rendered in the generated document's H1 text and page title.
+    - **`markdown_paths`** _(ARRAY, optional)_ - If you want to name your spec's markdown file something other than `spec.md`, or you have multiple files you would like assembled into a single output document, you must specify their paths as array entries in the order you would like them assembled. The paths in this array are assumed to be based on the `spec_directory` you specified, so _DO NOT_ repeat the full root relative path. 
+    - **`katex`** _(BOOLEAN, optional)_ - To enable TeX support via KaTeX, set this property to `true`. After rendering, be sure to copy the `fonts/` subdirectory, containing the necessary web fonts.
+    - **`output_path`** _(STRING, optional)_ - If you want the generated spec document to be output to a different location than the `spec_directory` you specified (e.g. the project root for GitHub Pages publishing) you can specify another root relative path (use `./` for root), and the tool will write the document file there instead.
+3. In your main node.js file, drop in this bad boy: `require('spec-up')()`
+
+Boom! That's it. Spec-Up will auto-detect modifications to files in your `spec_directory` and auto-generate your spec's updated HTML document every time you save a change.
+
+**Usage**
+
+If your `spec.json` and `package.json` and `package-lock.json` files are in working order and in the root folder of the repo from which it will be deployed, Spec-up can be called by command line (from the root of your repo) in three different modes:
+
+|command|behavior|
+|---|---|
+|`npm run edit`|after rendering, this will stay running and the `gulp` library will watch the source files in your spec directory/ies for changes and re-render any time you save a file. Opening these rendered files in a browser and refreshing them will keep you up to date.|
+|`npm run render`|this renders the site once and does not keep a gulpy watch on the underlying files.|
+|`npm run dev`|this enables debugging features.|
+
+## Table of Contents
+
+<-- You see that beautiful TOC over there to your left? (tap the header link to slide it out on mobile) Yeah, you don't need to do a damn thing, that just magically appears based on your use of `h2`, `h3`, and `h4` headings.
+
+## Term References
+
+### Definition Lists
+
+Many specs may want to include a section for terminology references, and Definition Lists are a great way to do that. Here's how to leverage Spec-Up's automatic term reference features via Definition List markup:
+
+<pre>
+[[def: Term 1, Term One]]:
+~ This is the first term we will define.
+
+[[def: Term 2, Term Two]]:
+~ This is the second term, but not the last.
+
+[[def: Term 3, Term Three]]:
+~ This is the last term, because you know what they say: third term's the charm!
+</pre>
+
+[[def: Term 1, Term One]]:
+~ This is the first term we will define.
+
+[[def: Term 2, Term Two]]:
+~ This is the second term, but not the last.
+
+[[def: Term 3, Term Three]]:
+~ This is the last term, because you know what they say: third term's the charm!
+
+Now let's refer to some of the terms defined above to show how the auto-linking of terms works: [[ref: Term 1]], [[ref: Term Two]], [[ref: Term 3]]. Additionally, as long as you define your terms using Definition Lists (as seen in the markdown above), you will be able to hover any reference to a term to see a tooltip with its definition.
+
+### Table-defined Terms
+
+You can also reference table-oriented terms and definitions which are decomposed into heading-titled attributes in distinct cells:
+
+<pre>
+Variable           | Default Value | Max Value
+------------------- | -------------- | ---------
+[[def: Variable 1]] | 123          | 9999
+</pre>
+
+Variable            | Default Value | Max Value
+------------------- | ------------- | ---------
+[[def: Variable 1]] | 123           | 9999
+
+
+Anytime you add a definition of a term in the first column of a table, like [[ref: Variable 1]], it will link to the cell and display a tooltip with the entire set of row values when you hover the term.
+
+### External Term References
+
+It is possible to include references to terms from external spec-up generated specifications. To include a source you would like to pull references from include an `external_specs` array in your spec config. The value should be a key/value object where the key is used in the external reference below and the value is the URL of the external spec. 
+
+::: example
+```json
+{
+  "specs": [
+    {
+      ...
+      "external_specs": [
+        {"PE": "https://identity.foundation/presentation-exchange"}
+      ]
+    }
+  ]
+}
+```
+:::
+
+To include an external term reference within your spec use the following format `[[xref: {title}, {term}]]` where `{title}` is the title given to the spec in the config and `{term}` is the term being used. For example using the PE spec given in the example above [[xref: PE, Holder]]
+
+## Blockquote
+
+> To be, or not to be, that is the question: 
+Whether 'tis nobler in the mind to suffer
+The slings and arrows of outrageous fortune,
+Or to take arms against a sea of troubles
+And by opposing end them. To die—to sleep,
+No more;
+
+## Notices
+
+<pre>
+::: note Basic Note
+  Check this out.
+:::
+</pre>
+
+::: note Basic Note
+  Check this out.
+:::
+
+::: note
+  Here's another.
+:::
+
+::: note
+  And one more!
+:::
+
+::: note Basic Note
+  One last note!!!
+:::
+
+<pre>
+::: issue Issue Notice
+  I take issue with that, kind sir.
+:::
+</pre>
+
+::: issue Issue Notice
+  I take issue with that, kind sir.
+:::
+
+<pre>
+::: warning Warning Notice
+  Houston, I think we have a problem
+:::
+</pre>
+
+::: warning Warning Notice
+  Houston, I think we have a problem
+:::
+
+
+<pre>
+::: todo Really Important
+  Get this done!
+:::
+</pre>
+
+::: todo Really Important
+  Get this done!
+:::
+
+
+<pre>
+::: example Code Example
+  Put your code block here
+:::
+</pre>
+
+::: example Code Example
+```json
+// Some comment in JSON
+{
+  "foo": "bar",
+  "baz": 2
+}
+```
+:::
+
+## Content Insertion
+
+Use the following format to pull in content from other files in your project:
+
+<pre>
+This text has been inserted here from another file: &#91;&#91;insert: ./single-file-test/assets/test.text&#93;&#93;
+</pre>
+
+This text has been inserted here from another file: [[insert: ./single-file-test/assets/test.text]]
+
+You can even insert content within more complex blocks, like the JSON object below which is being pulled in and rendered in a syntax-highlighted example block:
+<pre>
+::: example Code Example
+```json
+&#91;&#91;insert: ./single-file-test/assets/test.json&#93;&#93;
+```
+:::
+</pre>
+
+::: example Code Example
+```json
+[[insert: ./single-file-test/assets/test.json]]
+```
+:::
+
+
+## Tables
+
+<pre>
+Stage | Direct Products | ATP Yields
+----: | --------------: | ---------:
+Glycolysis | 2 ATP ||
+^^ | 2 NADH | 3--5 ATP |
+Pyruvaye oxidation | 2 NADH | 5 ATP |
+Citric acid cycle | 2 ATP ||
+^^ | 6 NADH | 15 ATP |
+^^ | 2 FADH2 | 3 ATP |
+**30--32** ATP |||
+[Net ATP yields per hexose]
+</pre>
+
+Stage | Direct Products | ATP Yields
+----: | --------------: | ---------:
+Glycolysis | 2 ATP ||
+^^ | 2 NADH | 3--5 ATP |
+Pyruvaye oxidation | 2 NADH | 5 ATP |
+Citric acid cycle | 2 ATP ||
+^^ | 6 NADH | 15 ATP |
+^^ | 2 FADH2 | 3 ATP |
+**30--32** ATP |||
+[Net ATP yields per hexose]
+
+<pre>
+|--|--|--|--|--|--|--|--|
+|♜|  |♝|♛|♚|♝|♞|♜|
+|  |♟|♟|♟|  |♟|♟|♟|
+|♟|  |♞|  |  |  |  | |
+|  |♗|  |  |♟|  |  | |
+|  |  |  |  |♙|  |  | |
+|  |  |  |  |  |♘|  | |
+|♙|♙|♙|♙|  |♙|♙|♙|
+|♖|♘|♗|♕|♔|  |  |♖|
+</pre>
+
+|--|--|--|--|--|--|--|--|
+|♜|  |♝|♛|♚|♝|♞|♜ |
+|  |♟|♟|♟|  |♟|♟|♟ |
+|♟|  |♞|  |  |  |  |  |
+|  |♗|  |  |♟|  |  |  |
+|  |  |  |  |♙|  |  |  |
+|  |  |  |  |  |♘|  |  |
+|♙|♙|♙|♙|  |♙|♙|♙ |
+|♖|♘|♗|♕|♔|  |  |♖ |
+
+## Sequence Diagrams
+<pre>
+```mermaid
+sequenceDiagram
+  Alice ->> Bob: Hello Bob, how are you?
+  Bob-->>John: How about you John?
+  Bob--x Alice: I am good thanks!
+  Bob-x John: I am good thanks!
+  Note right of John: Bob thinks a long<br/>long time, so long<br/>that the text does<br/>not fit on a row.
+
+  Bob-->Alice: Checking with John...
+  Alice->John: Yes... John, how are you?
+```
+</pre>
+
+```mermaid
+sequenceDiagram
+  Alice ->> Bob: Hello Bob, how are you?
+  Bob-->>John: How about you John?
+  Bob--x Alice: I am good thanks!
+  Bob-x John: I am good thanks!
+  Note right of John: Bob thinks a long<br/>long time, so long<br/>that the text does<br/>not fit on a row.
+
+  Bob-->Alice: Checking with John...
+  Alice->John: Yes... John, how are you?
+```
+
+## Flows
+
+<pre>
+```mermaid
+graph TD
+  A[Start] --> B{Is it?}
+  B -->|Yes| C[OK]
+  C --> D[Rethink]
+  D --> B
+  B -->|No| E[End]
+```
+</pre>
+
+```mermaid
+graph TD
+  A[Start] --> B{Is it?}
+  B -->|Yes| C[OK]
+  C --> D[Rethink]
+  D --> B
+  B -->|No| E[End]
+```
+
+## Charts
+
+<pre>
+```chart
+{
+  "type": "pie",
+  "data": {
+    "labels": [
+      "Red",
+      "Blue",
+      "Yellow"
+    ],
+    "datasets": [
+      {
+        "data": [
+          300,
+          50,
+          100
+        ],
+        "backgroundColor": [
+          "#FF6384",
+          "#36A2EB",
+          "#FFCE56"
+        ],
+        "hoverBackgroundColor": [
+          "#FF6384",
+          "#36A2EB",
+          "#FFCE56"
+        ]
+      }
+    ]
+  }
+}
+```
+</pre>
+
+```chart
+{
+  "type": "pie",
+  "data": {
+    "labels": [
+      "Red",
+      "Blue",
+      "Yellow"
+    ],
+    "datasets": [
+      {
+        "data": [
+          300,
+          50,
+          100
+        ],
+        "backgroundColor": [
+          "#FF6384",
+          "#36A2EB",
+          "#FFCE56"
+        ],
+        "hoverBackgroundColor": [
+          "#FF6384",
+          "#36A2EB",
+          "#FFCE56"
+        ]
+      }
+    ]
+  }
+}
+```
+
+## Syntax Highlighting
+
+<pre>
+```json
+{
+  "@context": "https://www.w3.org/ns/did/v1",
+  "id": "did:example:123456789abcdefghi",
+  "authentication": [{
+    "id": "did:example:123456789abcdefghi#keys-1",
+    "type": "RsaVerificationKey2018",
+    "controller": "did:example:123456789abcdefghi",
+    "publicKeyPem": "-----BEGIN PUBLIC KEY...END PUBLIC KEY-----\r\n"
+  }],
+  "service": [{
+    "id":"did:example:123456789abcdefghi#vcs",
+    "type": "VerifiableCredentialService",
+    "serviceEndpoint": "https://example.com/vc/"
+  }]
+}
+```
+</pre>
+
+
+```json
+{
+  "@context": "https://www.w3.org/ns/did/v1",
+  "id": "did:example:123456789abcdefghi",
+  "authentication": [{ 
+    "id": "did:example:123456789abcdefghi#keys-1",
+    "type": "RsaVerificationKey2018",
+    "controller": "did:example:123456789abcdefghi",
+    "publicKeyPem": "-----BEGIN PUBLIC KEY...END PUBLIC KEY-----\r\n"
+  }],
+  "service": [{
+    "id":"did:example:123456789abcdefghi#vcs",
+    "type": "VerifiableCredentialService",
+    "serviceEndpoint": "https://example.com/vc/"
+  }]
+}
+```
+
+## TeX Math Equations
+
+When the `katex` option is enabled, the KaTeX math engine is used for TeX rendering. You can find a list of supported features and examples here: https://katex.org/docs/supported.html.
+
+$$\begin{pmatrix}x_2 \\ y_2 \end{pmatrix} = 
+\begin{pmatrix} A & B \\ C & D \end{pmatrix}\cdot
+\begin{pmatrix} x_1 \\ y_1 \end{pmatrix}$$
+
+$$\def\arraystretch{1.5}
+   \begin{array}{c:c:c}
+   a & b & c \\ \hline
+   d & e & f \\
+   \hdashline
+   g & h & i
+\end{array}$$
+
+$$
+\underbrace{a+b+c}_{\text{Note: such math, much wow.}}
+$$
+
+## Tab Panels
+
+<tab-panels selected-index="0">
+  <nav>
+    <button type="button">First Tab</button>
+    <button type="button">Second Tab</button>
+  </nav>
+
+  <section>
+
+```json
+{
+  "foo": "foo",
+  "baz": 1
+}
+```
+
+  </section>
+  <section>
+
+```json
+{
+  "foo": "bar",
+  "baz": 2
+}
+```
+
+  </section>
+</tab-panels>
+
+## Fancy Links
+
+Spec-Up automatically upgrades the links of certain sites, like GitHub. GitHub is the only supported site with Fancy Links right now, but we'll be adding more as we go.
+
+### GitHub
+
+- **Issues**
+  - Source: `https://github.com/decentralized-identity/presentation-exchange/issues/119`
+  - Render: https://github.com/decentralized-identity/presentation-exchange/issues/119
+- **Pull Requests**
+  - Source: `https://github.com/decentralized-identity/sidetree/pull/863`
+  - Render: https://github.com/decentralized-identity/sidetree/pull/863
+- **Releases**
+  - Source: `https://github.com/decentralized-identity/sidetree/releases/tag/v0.9.1`
+  - Render: https://github.com/decentralized-identity/sidetree/releases/tag/v0.9.1
+- **Projects**
+  - Source: `https://github.com/decentralized-identity/sidetree/projects/1`
+  - Render: https://github.com/decentralized-identity/sidetree/projects/1
+
+## External Spec References
+
+You can reference external specifications from IETF, W3C, and WHATWG as follows: 
+
+1. Anywhere in your document you want to referece an external specification, use the `spec`-prefixed custom token format: `[[spec:RFC4122]]`
+2. Wherever in your document you want to print out all your external specification references, use the `spec` custom token format _without any spec name_: `[[spec]]`
+  - If you want to split up your references into groups (e.g. normative vs informative), just make sure to use dash-delimited unique reference grouping string in your custom tokens: `[[spec-norm:RFC4122]]`, `[[spec-inform:RFC4122]]`, `[[spec-foo:RFC4122]]`, etc.
+  - To print out a custom group's references, just include the grouping string for a given set of references in a custom token _without any spec name_: `[[spec-norm]]`, `[[spec-inform]]`, `[[spec-foo]]`.
+
+Here are a set of example references that are distributed among the reference groups `spec`, `spec-norm`, `spec-inform`:
+
+- [[spec:RFC3548]] (`[[spec:RFC3548]]`)
+- [[spec:RFC7518]] (`[[spec:RFC7518]]`)
+- [[spec-norm:DID-CORE]] (`[[spec-norm:DID-CORE]]`)
+- [[spec-norm:DID-SPEC-REGISTRIES]] (`[[spec-norm:DID-SPEC-REGISTRIES]]`)
+- [[spec-inform:RFC6901]] (`[[spec-inform:RFC6901]]`)
+- [[spec-inform:RFC7230]] (`[[spec-inform:RFC7230]]`)
+
+### Default References
+
+This is what is printed out when you include the `[[spec]]` custom token in your Markdown:
+
+[[spec]]
+
+
+### Normative References
+
+This is what is printed out when you include the `[[spec-norm]]` custom token in your Markdown:
+
+[[spec-norm]]
+
+### Informative References
+
+This is what is printed out when you include the `[[spec-inform]]` custom token in your Markdown:
+
+[[spec-inform]]

package/spec/header.md

@@ -0,0 +1,20 @@
+## Status
+
+This is the first public review draft of the ToIP Glossary. It is also the first version published using the [Spec-Up specification editing utility](https://identity.foundation/spec-up/) developed by the [Decentralized Identity Foundation](http://identity.foundation/).
+
+## Copyright Notice
+
+This specification is subject to the **OWF Contributor License Agreement 1.0 - Copyright**
+available at
+[https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owf-contributor-license-agreement-1-0-copyright](https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owf-contributor-license-agreement-1-0-copyright).
+
+These terms are inherited from the [Technical Stack Working Group](https://wiki.trustoverip.org/display/HOME/Technology+Stack+Working+Group) at the Trust over IP (ToIP) Foundation. [Working Group Charter](https://trustoverip.org/wp-content/uploads/TSWG-2-Charter-Revision.pdf)
+
+
+## Terms of Use
+
+These materials are made available under and are subject to the [OWF CLA 1.0 - Copyright & Patent license](https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owf-contributor-license-agreement-1-0-copyright-and-patent). Any source code is made available under the [Apache 2.0 license](https://www.apache.org/licenses/LICENSE-2.0.txt).
+
+THESE MATERIALS ARE PROVIDED “AS IS.” The Trust Over IP Foundation, established as the Joint Development Foundation Projects, LLC, Trust Over IP Foundation Series ("ToIP"), and its members and contributors (each of ToIP, its members and contributors, a "ToIP Party") expressly disclaim any warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to the materials. The entire risk as to implementing or otherwise using the materials is assumed by the implementer and user.
+
+IN NO EVENT WILL ANY ToIP PARTY BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES OF ACTION OF ANY KIND WITH RESPECT TO THESE MATERIALS, ANY DELIVERABLE OR THE ToIP GOVERNING AGREEMENT, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, AND WHETHER OR NOT THE OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

package/spec/introduction.md

@@ -0,0 +1,32 @@
+
+[//]: # (Pandoc Formatting Macros)
+
+[//]: # (::: introtitle)
+
+[//]: # (Introduction)
+
+[//]: # (:::)
+
+## Introduction
+
+The ToIP Glossary is a deliverable of the ToIP Concepts and Terminology Working Group. Its purpose is to promote shared understanding of terms and concepts across the many different working groups, communities, enterprises, and ecosystems who are collaborating to develop and deploy decentralized digital trust infrastructure.
+
+Contributions and feedback are encouraged from any stakeholder in this area of terminology.
+
+## Linking to this Glossary
+
+This glossary is designed to be both human and machine readable. All terms are listed alphabetically; acronyms are listed separately and linked to the fully expanded terms. Document authors can link directly to any term using standard web links and anchors following this syntax:
+
+  `https://trustoverip.org/ctwg-main-glossary#term:xxxxx`
+
+Where `xxxxx` is the term as it appears in the glossary, with any spaces are replaced by en-dashes (hyphens). For example, a link to the term `self-certifying identifer` would be:
+
+  `https://trustoverip.github.io/ctwg-main-glossary#self-certifiying-identifier`
+
+A specification document written using the [Decentralized Identity Foundation](http://identity.foundation/)'s open source [Spec-Up editor](https://identity.foundation/spec-up/) may create special external references to terms in this glossary using the Spec-Up `xref` tag following this syntax:
+
+  `[[xref: glossary, xxxxx]]`
+
+  Where `glossary` is the text label the document author assigns to the URL of a Web-accessible glossary, and `xxxxx` is the term as it appears in that glossary, with any spaces are replaced by en-dashes (hyphens). For example, a Spec-Up external reference to the term `self-certifying identifer` using the label `toip` for this glossary would look like this:
+
+  `[[xref: toip, self-certifying-identifier]]`

package/spec/referenced_glossaries.md

@@ -0,0 +1,24 @@
+## Referenced Glossaries
+
+[//]: # (Pandoc Formatting Macros)
+
+[//]: # (# Normative references)
+
+[//]: # (::: { #nrm:pdf2 .normref label="ISO 32000-2" })
+
+[//]: # (ISO 32000-2, *Document management --- Portable Document Format --- Part 2: PDF 2.0*)
+
+[//]: # (:::)
+
+The following glossaries were used as sources for some of the definitions in the ToIP Glossary. All source glossaries are cited in the definitions of each term.
+
+| Short Name | Source Glossary | URL |
+|------------|-----------------|-----|
+| Wikipedia | Wikipedia | https://www.wikipedia.org/ |
+| eSSIF-Lab | eSSIF-Lab Glossary | https://essif-lab.github.io/framework/docs/essifLab-glossary |
+| NIST-CSRC | NIST Computer Security Resource Center Glossary | https://csrc.nist.gov/glossary/ |
+| PEMC IGR | Kantara Privacy Enhancing Mobile Credentials Implementors Guidance Report | https://kantarainitiative.org/download/pemc-implementors-guidance-report/ |
+| W3C DID | W3C Decentralized Identifiers (DIDs) 1.0 | https://www.w3.org/TR/did-core/#terminology |
+| W3C VC | W3C VC Data Model 1.1 | https://www.w3.org/TR/vc-data-model/#terminology |
+| Ethereum | Ethereum.org Glossary | https://ethereum.org/ |
+| Merriam-Webster | Merriam-Webster Dictionary | https://www.merriam-webster.com/dictionary/ |

package/spec/term-definitions/term-1.md

@@ -0,0 +1,9 @@
+[[def: term 1, term one, Term One]]
+
+~ Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum faucibus volutpat justo, sed ornare velit.
+
+~ Refs examples: [[ref: Term 2]], [[ref: Term Two]], [[ref: Term 3]].
+
+~ Xref examples: [[xref: PE, Holder]], [[xref: test-1, Aal]], [[xref: test-2, Abac]]
+
+~ Donec aliquam et ligula id congue. Sed eu urna et tellus placerat viverra. Quisque ut posuere magna, nec accumsan augue. Nullam mauris tortor, semper finibus elementum maximus, imperdiet in felis. Suspendisse quis imperdiet nibh, eget ultrices justo. Pellentesque vitae malesuada justo. Vestibulum quis scelerisque lectus, non rutrum odio. Aenean leo orci, semper non massa sed, facilisis ornare ipsum. Morbi at sem orci. Integer eros mi, faucibus sed lorem id, pharetra imperdiet nisl. Integer viverra enim vel luctus lobortis. Ut turpis tellus, consequat nec lectus et, dictum elementum nunc. Integer rhoncus venenatis molestie. Donec egestas condimentum ligula in porttitor. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos.

package/spec/term-definitions/term-2.md

@@ -0,0 +1,3 @@
+[[def: term 2, term two, Term Two]]
+
+~ Pellentesque suscipit ipsum varius, mattis diam in, elementum nunc [[ref: Term 1]], [[ref: Term Three]], [[ref: Term 3]], [[ref: Term 4]]. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Donec placerat, elit sed tempor viverra, magna ligula porttitor tortor, eget suscipit erat enim vel nisl. Integer vel urna in quam viverra dignissim at in orci. Aliquam erat volutpat. Nam vitae neque nibh. In sollicitudin felis vitae ex finibus, in eleifend lectus efficitur. Vestibulum enim ex, condimentum nec accumsan ut, vestibulum at lacus. Maecenas non vulputate ante. Sed porttitor et eros sit amet venenatis.

package/spec/term-definitions/term-3.md

@@ -0,0 +1,3 @@
+[[def: term 3, term three, Term Three]]
+
+~ Nam euismod augue sed tempus imperdiet. Pellentesque ac porta ipsum, sed sodales leo. Suspendisse molestie est sit amet est porta, sit amet molestie dolor pharetra. Duis porta mollis sem vel aliquam. Maecenas laoreet turpis nunc, vitae mattis urna auctor ac. Donec mattis quis urna nec porta. Sed sit amet viverra ligula. Vivamus vitae sem sodales, malesuada dui sit amet, viverra lectus. Integer ullamcorper molestie ante, in blandit nunc tempus auctor.

package/spec/term-definitions/term-4.md

@@ -0,0 +1,3 @@
+[[def: term 4, term four, Term Four]]
+
+~ Sed lorem nunc, ultricies nec nibh eu, bibendum sollicitudin arcu. Nullam porttitor condimentum elit ac commodo. Aenean ac augue quis arcu congue aliquam vitae in massa. Aliquam erat volutpat. Curabitur lobortis, sapien vitae mattis dignissim, risus augue iaculis risus, sed tempus sapien ex nec massa. Integer quis maximus nunc. Nunc ultrices sapien erat, at congue augue mattis sit amet. Aliquam condimentum luctus nunc, ut euismod augue commodo in.

package/spec/terms_and_definitions.md

@@ -0,0 +1,10 @@
+
+[//]: # (Pandoc Formatting Macros)
+
+[//]: # (Portable Document Format)
+
+[//]: # (blank)
+
+[//]: # (: file format defined by ISO 32000-2)
+
+## Terms & Definitions