generally in {A,E}BNF, if one literal is a prefix of another,
the longer one is specified first, otherwise the shorter one
will always match, either causing a spurious error or a parsing
ambiguity, unless using a parser architecture which automatically
resolved local ambiguities by collecting alternatives.
this is something the rest of the KDL and KQL specs do well,
but it seems this case slipped through the cracks.
Fixes: https://github.com/kdl-org/kdl/issues/461
* Initial conversion to Internet-Draft.
* Setup repository for draft-marchan-kdl2 using https://github.com/martinthomson/i-d-template
* Remove unnecessary changes.
* Tweak source to make the I-D build.
* Fix zkat's name. Guess at their preferred initials.
* Separate links where linking text equals the anchor.
This works around https://github.com/cabo/kramdown-rfc/issues/249.
* Replace horizontal rules with subsections.
RFCXML v3 doesn't include horizontal rules.
* Use ~~~kdl instead of `` for strings with significant whitespace.
That compiles to <sourcecode> which preserves sequences of spaces.
* Give breadcrumbs to the RFC format definitions.
* Point contributors to https://author-tools.ietf.org/.
For if installing the dependencies is inconvenient.
* Separate a code block from adjacent text.
* Remove a workflow that overwrites customized files.
* Remove the 'archive' workflow.
* Use "Term ({{term}})" uniformly instead of just when the term matches the anchor.
* Fix the instructions for preserving the RFCXML.
* Remove the default copyright notice until the spec is relicensed.
* Take the IETF licensing details out of CONTRIBUTING.md.
Fixes: https://github.com/kdl-org/kdl/issues/306
In the specifications of KQL and JiK, replace the
usage of 'tag' with 'type annotation', as that is
the term in the main KDL specification.
lolbinarycat
lolbinarycat
Bram Gotink
Jeffrey Yasskin
Lars Willighagen
Romain Delamare
Kat Marchán
Jihchi Lee