Remove unnecessary changes.

.circleci/config.yml

@@ -1,101 +0,0 @@
-version: 2
-jobs:
-  build:
-    docker:
-      - image: martinthomson/i-d-template:latest
-    resource_class: small
-    working_directory: ~/draft
-
-    steps:
-      - run:
-          name: "Print Configuration"
-          command: |
-            xml2rfc --version
-            gem list -q kramdown-rfc
-            echo -n 'mmark '; mmark --version
-
-      - restore_cache:
-          name: "Restoring cache - Git"
-          keys:
-            - v2-cache-git-{{ .Branch }}-{{ .Revision }}
-            - v2-cache-git-{{ .Branch }}
-            - v2-cache-git-
-
-      - restore_cache:
-          name: "Restoring cache - References"
-          keys:
-            - v1-cache-references-{{ epoch }}
-            - v1-cache-references-
-
-      # Workaround for https://discuss.circleci.com/t/22437
-      - run:
-          name: Tag Checkout
-          command: |
-            if [ -n "$CIRCLE_TAG" ] && [ -d .git ]; then
-              remote=$(echo "$CIRCLE_REPOSITORY_URL" | \
-                       sed -e 's,/^git.github.com:,https://github.com/,')
-              git fetch -f "$remote" "refs/tags/$CIRCLE_TAG:refs/tags/$CIRCLE_TAG" || \
-                (echo 'Removing .git cache for tag build'; rm -rf .git)
-            fi
-
-      - checkout
-
-      # Build txt and html versions of drafts
-      - run:
-          name: "Build Drafts"
-          command: make
-
-      # Update editor's copy on gh-pages
-      - run:
-          name: "Update GitHub Pages"
-          command: |
-            if [ "${CIRCLE_TAG#draft-}" == "$CIRCLE_TAG" ]; then
-              make gh-pages
-            fi
-
-      # For tagged builds, upload to the datatracker.
-      - deploy:
-          name: "Upload to Datatracker"
-          command: |
-            if [ "${CIRCLE_TAG#draft-}" != "$CIRCLE_TAG" ]; then
-              make upload
-            fi
-
-      # Archive GitHub Issues
-      - run:
-          name: "Archive GitHub Issues"
-          command: "make archive || make archive DISABLE_ARCHIVE_FETCH=true && make gh-archive"
-
-      # Create and store artifacts
-      - run:
-          name: "Create Artifacts"
-          command: "make artifacts CI_ARTIFACTS=/tmp/artifacts"
-
-      - store_artifacts:
-          path: /tmp/artifacts
-
-      - run:
-          name: "Prepare for Caching"
-          command: "git reflog expire --expire=now --all && git gc --prune=now"
-
-      - save_cache:
-          name: "Saving Cache - Git"
-          key: v2-cache-git-{{ .Branch }}-{{ .Revision }}
-          paths:
-            - ~/draft/.git
-
-      - save_cache:
-          name: "Saving Cache - Drafts"
-          key: v1-cache-references-{{ epoch }}
-          paths:
-            - ~/.cache/xml2rfc
-
-
-workflows:
-  version: 2
-  build:
-    jobs:
-      - build:
-          filters:
-            tags:
-              only: /.*?/

.github/CODEOWNERS

@@ -1,3 +0,0 @@
-# Automatically generated CODEOWNERS
-# Regenerate with `make update-codeowners`
-draft-marchan-kdl2.md

.gitignore

@@ -1,3 +1,5 @@
+/target
+Cargo.lock
 *.html
 *.pdf
 *.redxml

.note.xml

@@ -1,4 +1,4 @@
 <note title="Discussion Venues" removeInRFC="true">
 <t>Source for this draft and an issue tracker can be found at
-    <eref target="https://github.com/jyasskin/kdl"/>.</t>
+    <eref target="https://github.com/kdl-org/kdl"/>.</t>
 </note>

CONTRIBUTING.md

@@ -15,3 +15,21 @@ repository constitutes Contributions to the IETF Standards Process
 You agree to comply with all applicable IETF policies and procedures, including,
 BCP 78, 79, the TLP, and the TLP rules regarding code components (e.g. being
 subject to a Simplified BSD License) in Contributions.
+
+
+## Mechanics
+
+Contributions can be made by creating pull requests.
+The GitHub interface supports creating pull requests using the Edit (✏) button.
+
+
+## Building the Specification
+
+Formatted text and HTML versions of the spec can be built using `make`.
+
+```sh
+$ make
+```
+
+Command line usage requires that you have the necessary software installed.  See
+[the instructions](https://github.com/martinthomson/i-d-template/blob/main/doc/SETUP.md).

LICENSE.md

@@ -1,4 +1 @@
-# License
+This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/ or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA.
-
-See the
-[guidelines for contributions](https://github.com/jyasskin/kdl/blob/main/CONTRIBUTING.md).

QUERY-SPEC.md

@@ -110,7 +110,7 @@ Then the following queries are valid:
 ## Full Grammar
 
 Rules that are not defined in this grammar are prefixed with `$`, see [the KDL
-grammar](https://github.com/kdl-org/kdl/blob/main/SPEC.md#full-grammar) for
+grammar](https://kdl-org.github.io/kdl/#go.draft-marchan-kdl2.html#full-grammar) for
 what they expand to.
 
 ```

README.md

@@ -46,16 +46,16 @@ package {
 
 For more details, see the [overview below](#overview).
 
-There's a living [specification](SPEC.md), as well as various
+There's a living [specification](https://kdl-org.github.io/kdl/#go.draft-marchan-kdl2.html), as well as various
 [implementations](#implementations). You can also check out the [FAQ](#faq) to
 answer all your burning questions!
 
 The current version of the KDL spec is
-[KDL 2.0.0](https://github.com/kdl-org/kdl/blob/2.0.0/SPEC.md). For legacy KDL,
+[KDL 2.0.0](https://kdl-org.github.io/kdl/#go.draft-marchan-kdl2.html). For legacy KDL,
 please refer to the [KDL 1.0.0
 spec](https://github.com/kdl-org/kdl/blob/2.0.0/SPEC_v1.md). All users are
 encouraged to migrate. [Migration is forward-and-backward-compatible and
-safe](https://github.com/kdl-org/kdl/blob/2.0.0/SPEC.md#compatibility), and can
+safe](https://kdl-org.github.io/kdl/#go.draft-marchan-kdl2.html#compatibility), and can
 be automated.
 
 In addition to a spec for KDL itself, there are specifications for [a KDL Query
@@ -400,7 +400,7 @@ SDLang is an excellent base, but I wanted some details ironed out, and some
 things removed that only really made sense for SDLang's current use-cases, including
 some restrictions about data representation. KDL is very similar in many ways, except:
 
-* The grammar and expected semantics are [well-defined and specified](SPEC.md).
+* The grammar and expected semantics are [well-defined and specified](https://kdl-org.github.io/kdl/#go.draft-marchan-kdl2.html).
   This was the original impetus for working on KDL, followed by details that
   seemed like they could be improved.
 * There is only one "number" type. KDL does not prescribe representations, but

SPEC_v1.md

@@ -22,7 +22,8 @@ simultaneously. For example, `node "foo"` is a valid node in both versions, and
 should be represented identically by parsers.
 
 KDL v2 is designed such that for any given KDL document written as KDL
-1.0 or [KDL 2.0](./SPEC.md), the parse will either fail completely, or, if the
+1.0 or [KDL 2.0](https://kdl-org.github.io/kdl/#go.draft-marchan-kdl2.html),
+the parse will either fail completely, or, if the
 parse succeeds, the data represented by a v1 or v2 parser will be identical.
 This means that it's safe to use a fallback parsing strategy in order to support
 both v1 and v2 simultaneously. For example, `node "foo"` is a valid node in both