blockspec 0.1.0__tar.gz

blockspec-0.1.0/.github/workflows/conformance.yml

@@ -0,0 +1,153 @@
+# SPDX-License-Identifier: Apache-2.0 OR MIT
+name: conformance
+# Pushes to main only. A pull request branch then produces each check once,
+# from the pull_request run; a bare `push` would report the same job twice on
+# a pull request's head (kindspec/.github AGENTS.md §3.2).
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+env:
+  # The kindkit commit the validator and the runner come from. run_cases.py's
+  # docstring names the same commit; move them together.
+  KINDKIT_SHA: 6ebd80daba23e0d49a19e24b7ee4c85cedb926df
+
+jobs:
+  # The job id is the check's name, and a ruleset matches on it. Renaming it
+  # leaves a required check unreported (kindspec/.github AGENTS.md §3.2).
+  conformance:
+    runs-on: ubuntu-latest
+    steps:
+      # Pinned to commits, not tags, as rowspec does: a SHA cannot be
+      # re-pointed under us.
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          repository: kindspec/kindkit
+          ref: ${{ env.KINDKIT_SHA }}
+          path: .kindkit
+
+      # Each gate runs even when an earlier one is red, so one failure cannot
+      # hide whether the others ran.
+      - name: the case tree follows kindkit's convention and case-body schema
+        if: ${{ !cancelled() }}
+        run: python3 .kindkit/tools/validate_case_tree.py conformance/cases
+
+      - name: every case can fail, every refusal has a control, the floor holds
+        if: ${{ !cancelled() }}
+        run: python3 conformance/check_tree.py
+
+      # The anchor and merge branches of the schema, against synthetic bodies:
+      # good ones that must validate, broken ones that must each be rejected.
+      - name: the case-body schema accepts good bodies and rejects broken ones
+        if: ${{ !cancelled() }}
+        run: python3 conformance/schema_selftest.py .kindkit
+
+      # A run against nothing must be no verdict, exit 2, never a pass. The
+      # `reference` job below runs the tree against the implementation.
+      - name: the runner with no implementation reports no verdict
+        if: ${{ !cancelled() }}
+        run: |
+          set +e
+          PYTHONPATH=.kindkit python3 conformance/run_cases.py
+          code=$?
+          set -e
+          if [ "$code" -ne 2 ]; then
+            echo "expected exit 2 (no verdict), got $code"
+            exit 1
+          fi
+
+      # And a run against an implementation that returns nothing must fail
+      # every case, not some of them, of either kind.
+      - name: the runner fails every case against an empty implementation
+        if: ${{ !cancelled() }}
+        run: |
+          impl="$RUNNER_TEMP/empty_impl.py"
+          report="$RUNNER_TEMP/report.json"
+          printf 'def conform(text, queries):\n    return {"accept": True, "blocks": [], "leaves": [], "names": {}}\n' > "$impl"
+          printf 'def resolve(repo, queries):\n    return {"records": {}, "transclusions": {}}\n' >> "$impl"
+          set +e
+          PYTHONPATH=.kindkit python3 conformance/run_cases.py --impl "$impl" --report-json "$report" > /dev/null
+          code=$?
+          set -e
+          if [ "$code" -ne 1 ]; then
+            echo "expected exit 1 (cases failed), got $code"
+            exit 1
+          fi
+          python3 - "$report" <<'PY'
+          import json, sys
+          report = json.load(open(sys.argv[1]))
+          failed = {f["id"] for f in report["failures"]}
+          passed = [c for c in report["cases"] if c not in failed]
+          print(f"{len(report['cases'])} cases ran, {len(failed)} failed")
+          if passed:
+              sys.exit(f"cases that passed against an empty implementation: {passed}")
+          PY
+
+  # The tree against the reference implementation, reference/blockspec/. A
+  # job of its own, so `conformance` above keeps reporting on the tree alone.
+  # The mutation gate (`just mutants`) is not here: see AGENTS.md, Status.
+  reference:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+      # `just` is not on the runner image; without it every step below dies
+      # at exit 127, which looks from outside like checks that ran and failed.
+      # Pinned to a version, as the actions above are pinned to commits.
+      - name: install just
+        run: |
+          uv tool install rust-just==1.58.0
+          echo "$HOME/.local/bin" >> "$GITHUB_PATH"
+      - name: just is actually on PATH
+        run: just --version
+
+      # Each step runs even when an earlier one is red, so one failure cannot
+      # hide whether the others ran.
+      - name: lint and format
+        if: ${{ !cancelled() }}
+        run: just check
+
+      - name: the reference implementation passes every case in the tree
+        if: ${{ !cancelled() }}
+        run: just conform
+
+      - name: a second implementation, from the spec alone, passes the same tree
+        if: ${{ !cancelled() }}
+        run: just conform-alt
+
+      # The same run with its report read back, the reference/ import
+      # boundary, the kindkit pins, and the mutation gate's own checks.
+      - name: the test suite
+        if: ${{ !cancelled() }}
+        run: just test
+
+      # The action as a consumer runs it, on the checkout. It has to pass a
+      # good document and fail a refused one, or it cannot be trusted either way.
+      - name: make the action's two fixtures
+        if: ${{ !cancelled() }}
+        run: |
+          mkdir -p .action-test/good .action-test/bad
+          printf '# Title\n\nA paragraph.\n' > .action-test/good/a.md
+          printf '<div>raw</div>\n' > .action-test/bad/a.md
+      - name: the action passes a good document
+        if: ${{ !cancelled() }}
+        uses: ./
+        with:
+          paths: .action-test/good
+          install: .
+      - name: the action on a refused document
+        id: action-bad
+        if: ${{ !cancelled() }}
+        continue-on-error: true
+        uses: ./
+        with:
+          paths: .action-test/bad
+          install: .
+      - name: the action failed on the refused document
+        if: ${{ !cancelled() }}
+        run: test "${{ steps.action-bad.outcome }}" = failure

blockspec-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,93 @@
+# SPDX-License-Identifier: Apache-2.0 OR MIT
+# Publishes to PyPI through a Trusted Publisher (OIDC), so no token is stored.
+# PyPI trusts this repository, this workflow file by name and the `pypi`
+# environment; changing any of those breaks publication instead of publishing
+# from somewhere unexpected.
+name: release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  # The gate runs first and publication depends on it, so a release cannot
+  # skip the suite.
+  gate:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+      - name: install just
+        run: |
+          uv tool install rust-just==1.58.0
+          echo "$HOME/.local/bin" >> "$GITHUB_PATH"
+      - run: just check
+      - run: just tree
+      - run: just conform
+      - run: just conform-alt
+      - run: just test
+
+  build:
+    needs: gate
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+      - run: uv build
+
+      # The tag is the version. PyPI publication cannot be undone.
+      - name: the tag must match the built version
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          built=$(ls dist/*.tar.gz | sed -E 's/.*blockspec-(.*)\.tar\.gz/\1/')
+          if [ "$tag" != "$built" ]; then
+            echo "::error::tag v$tag does not match built version $built"
+            exit 1
+          fi
+
+      - name: action.yml must pin the version being released
+        run: |
+          pinned=$(grep -oE 'blockspec==[0-9]+\.[0-9]+\.[0-9]+' action.yml | head -1 | cut -d= -f3)
+          built=$(ls dist/*.tar.gz | sed -E 's/.*blockspec-(.*)\.tar\.gz/\1/')
+          if [ "$pinned" != "$built" ]; then
+            echo "::error::action.yml pins blockspec==$pinned but this release is $built"
+            exit 1
+          fi
+
+      - name: the built wheel actually works
+        run: |
+          uv run --with dist/*.whl --no-project python - <<'PY'
+          import importlib.metadata, os, subprocess, sys, tempfile
+          import blockspec
+          meta = importlib.metadata.version("blockspec")
+          assert blockspec.__version__ == meta, (blockspec.__version__, meta)
+          d = tempfile.mkdtemp()
+          with open(os.path.join(d, "bad.md"), "w") as f:
+              f.write("<div>raw</div>\n")
+          r = subprocess.run([sys.executable, "-m", "blockspec", "check", "--format", "github", d],
+                             capture_output=True, text=True)
+          assert r.returncode == 1, r
+          assert "[raw-html]" in r.stdout, r.stdout
+          print("wheel", meta, "refuses a bad document and annotates it")
+          PY
+
+      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2

blockspec-0.1.0/.gitignore

@@ -0,0 +1,49 @@
+# Dependencies
+node_modules/
+.venv/
+venv/
+__pycache__/
+*.egg-info/
+
+# Build output
+dist/
+build/
+target/
+*.o
+*.so
+*.dylib
+
+# IDE / editor
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Personal scratch (never committed)
+working/
+
+# Environment
+.env
+.env.local
+
+# Test / coverage
+coverage/
+*.out
+*.coverprofile
+htmlcov/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+
+# rowspec
+.cache/
+mutant_impl.py
+.venv/
+
+# prereg 3's cited rehearsal evidence includes .out files; keep them
+!spike/results/prereg3/rehearsals/**/*.out

blockspec-0.1.0/DESIGN-BRIEF.md

@@ -0,0 +1,149 @@
+<!-- SPDX-License-Identifier: CC-BY-4.0 -->
+# blockspec — design brief
+
+Carried forward from the research and build that produced rowspec 0.1.0. Nothing
+here is a specification; it is the state a fresh design pass should start from,
+so that pass argues about the open questions rather than rediscovering the
+settled ones.
+
+---
+
+## 0. Settle this before anything else
+
+Every substantive defect found while building rowspec was found by **two
+independent implementations disagreeing** — an author who had written the
+reference, and an author forbidden to read it, each measured against the same
+fixture tree. That found uncaught crashes, three stale-value bugs, an illegal
+`#REF!` shape, a valid file being wrongly refused, and a §6 violation present in
+*both* implementations at once.
+
+**A format that does not exist yet has nothing to disagree with.**
+
+And the discipline cannot be added later: rowspec's second implementation
+drifted 117 cases behind the moment nothing ran it, and nobody noticed until it
+was wired into CI as a hard gate.
+
+So the first decision of the blockspec pass is a *process* decision, not a
+format one: **how does this format get an adversary from day one?** Plausible
+answers include writing the conformance suite before any implementation,
+commissioning two implementations in parallel from the same prose, or treating
+an existing document processor as the second opinion. Pick deliberately.
+
+## 1. Decided, with the measurement
+
+**The canonical artifact is UTF-8 text, one document per file, hand-editable.**
+Forced by git rather than by taste: a serialized AST loses the merge experiment
+badly, and the Pandoc AST loses the *archival* experiment outright.
+
+**The in-memory model is an AST with an attribute triple on every node**
+(`id`, `classes`, `key=value`), Pandoc-shaped. It is derived and disposable, and
+is never committed.
+
+**A prose block gets NO minted id.** This is the sharpest difference from
+rowspec, and it is measured, not aesthetic:
+
+    corpus           minlen  prose blocks  dup in file
+    rust-book            40          2938    0 (0.0%)
+    obsidian-help        40          2526   16 (0.6%)
+
+From `research/design-findings/D8-identity.md` §3.3 (kindspec/research
+`0d64e6a`), whose figures are the committed harness output
+`experiments/D8-identity/results-e4.txt`, measured at the corpus commits D8 §3
+pins. That table is reproducible from kindspec/research#7 (`16e4765`) onward.
+
+A prose block of ≥40 characters is unique within its file in 100.0% of
+rust-book's 2,938 prose blocks and 99.4% of obsidian-help's 2,526. **Code and
+raw HTML are not** — raw-HTML blocks in rust-book duplicate within a single file
+at 22.6% at ≥40, the threshold of the table above (23.6% is the same
+measurement at the script's default ≥20).
+
+The residual ambiguity is *detectable at resolve time*: the resolver reads the
+whole file and sees two matches, so it becomes a loud error rather than a silent
+wrong answer. Minted ids have no such property.
+
+**The tree is not sufficient.** Comments, annotations and tracked changes
+provably do not nest. Anything spanning structure must live in **standoff** with
+stable anchors. Those anchors are quotes held in the referrer, not attributes
+written into the file (D8 §6 and §7.3), so standoff does not disqualify
+markdown. An earlier version of this brief said it did, following D5 §0 item 5;
+`docs/adjudications/0001-syntax.md` §1 explains why that premise no longer
+holds. The attribute triple above is a property of the in-memory model and
+does not depend on the syntax. Under the profile below, only `id` is ever
+filled, from an authored name or a heading slug; `classes` and `key=value` are
+always empty, because the profile has no syntax for them.
+
+**The syntax is a pinned CommonMark 0.31.2 block-level profile**, not djot.
+Authored names use D8 §7.2's region marker: `<!-- #name -->` for the next
+block, and `<!-- #name:begin -->` / `<!-- #name:end -->` for a span. Decided
+by `docs/adjudications/0001-syntax.md` (blockspec#3), with the owner's answer
+that a blockspec document must render and edit correctly in today's markdown
+tools as the deciding input. The decision depends on blockspec#4 as that
+document states: it reverses if #4 needs typed attributes in the file, or a
+block boundary that needs new syntax. That document also records the reversal
+cost.
+
+**A block is a top-level node; an anchor resolves a leaf.** A list, a block
+quote and a table are each one block, and the blocks partition the document.
+Stage 1 of a quote anchor resolves the leaf (paragraph, heading, code block,
+HTML block, table or thematic break, at any depth) that holds the anchored
+text. A region marker names the next sibling node in its container. GFM pipe
+tables are in the profile, with a blank line or their container's edge on both
+sides; a table touching a non-blank line above or below is refused. Decided by `docs/adjudications/0002-block.md` (blockspec#4), which
+measured anchoring under real edits for each choice and records the reversal
+cost of each.
+
+**Do not reuse rowspec's syntax.** *"One syntax is a trap; one MODEL, several
+grammars is the sound version."* JATS learned this in 2003 and encoded the
+lesson architecturally.
+
+## 2. Open, and genuinely undecided
+
+**Quote-anchoring's failure modes.** Anchoring to content means an edit to the
+content moves the anchor. The 40-character measurement says collisions are rare
+and detectable; it does not say what happens when an anchored block is *edited*
+rather than duplicated.
+
+Decided by `docs/adjudications/0003-anchors.md`: an anchor lands only where
+every witness agrees, and is loud otherwise. Four edit shapes that the bytes
+cannot tell from legitimate edits remain, and that document names them.
+Pre-registration 4 measured its refusals on real history as too high
+(`0003-anchors/replay-verdict.md`), and `0004-anchor-refusals.md` narrows
+two of its rules; pre-registration 5 measured 0004's rules on held-out history
+refusing 2.9% of comments on surviving text, within its 5% bar (`0004-anchor-refusals/replay-verdict.md`).
+
+**What is the merge failure this format prevents?** rowspec has a specific,
+demonstrated one: two branches insert rows, git merges cleanly, the total is 480
+where the truth is 660. **blockspec does not yet have its equivalent, and should
+not be built until it does.** If prose has no silent-wrong-merge of comparable
+severity, that is a finding, and the honest response is a smaller format or
+none.
+
+The spike (blockspec#2) has since returned a binding FOUND, under an owner
+ruling that overrides frozen rules of its pre-registration (`spike/LOG.md`
+§34–§35), and blockspec#2 is closed. `spike/README.md` says what the verdict
+rests on.
+
+## 3. The method that must carry over
+
+- The **conformance suite is the deliverable**; the spec exists so the suite has
+  something to check.
+- **The suite is not written by whoever writes the implementation.** A standing
+  role, not a review step.
+- **The mutation gate**: deliberately break the implementation, and the suite
+  must notice. A surviving mutant is a failure, and so is a *stale* one whose
+  pattern no longer matches — because a check that quietly stopped running is
+  the failure this project keeps finding in itself.
+- **Measure before deciding.** Every rowspec question settled by reading was
+  wrong at least once; every one settled by measuring both implementations first
+  was right.
+- **Cell counts lie.** Corpus frequency is inflated by replication and fill-down;
+  the unit that matters is a *distinct authored expression*.
+
+## 4. Where the prior work lives
+
+The research, experiments and findings that produced the above are in
+[kindspec/research](https://github.com/kindspec/research):
+`design-findings/D5-document-models.md` (syntax and model),
+`design-findings/D8-identity.md` (the uniqueness measurements), `DESIGN.md` (the
+overall verdict); and in rowspec's own `docs/rationale.md` (what was measured,
+and what was measured and found wanting). Cite them by path and commit.

blockspec-0.1.0/LICENSE

@@ -0,0 +1,87 @@
+blockspec is licensed per directory, on the same split as rowspec. This is
+deliberate, not an oversight.
+
+  SPEC.md, docs/            CC-BY-4.0
+  conformance/cases/        CC0-1.0
+  conformance/*.py          MIT
+  reference/, tests/,
+  tools/                    Apache-2.0 OR MIT
+  justfile, pyproject.toml,
+  uv.lock                   Apache-2.0 OR MIT
+  README.md, AGENTS.md, CHANGELOG.md,
+  DESIGN-BRIEF.md           CC-BY-4.0
+  .editorconfig,
+  .gitattributes,
+  .gitignore                Apache-2.0 OR MIT
+  .github/workflows/,
+  action.yml                Apache-2.0 OR MIT
+  LICENSE, NOTICE           CC0-1.0
+  LICENSES/                 each text under its own terms, copied verbatim
+  spike/*.md                CC-BY-4.0
+  spike/harness/            MIT
+  spike/harness/plant_cases/  CC0-1.0
+  spike/harness3/           MIT
+  spike/ruling/             MIT
+  spike/results/            CC-BY-4.0, except corpus text (below)
+  spike/results/prereg3/    CC-BY-4.0, except corpus text and third-party
+                            excerpts (below)
+
+A path ending in "/" covers everything below it, subdirectories included. A
+"*" matches within one directory. Where two rows cover the same path, the more
+specific one applies: spike/harness/plant_cases/ is CC0-1.0 inside the MIT
+spike/harness/, and spike/results/prereg3/ keeps its own row and its own
+exceptions inside spike/results/.
+
+The rows for SPEC.md, docs/, conformance/, reference/ and tests/ are decided
+ahead of the files: those paths may be empty, and the split applies to whatever
+lands there.
+
+CORPUS TEXT IN spike/results/
+
+The spike measures third-party corpora, and its results carry their text,
+spike/results/prereg3/ included. In spike/results/prereg2/export/packets/ and
+spike/results/prereg3/export/packets/, every .md file in a packet other than
+QUESTIONS.md is a whole file copied from a corpus: before.md and after.md, or
+in a merge packet base.md, leg-a.md, leg-c.md and after.md. Each packet's packet.json
+quotes from them. The exception is the plant packets, whose text the harness
+generates (spike/harness/prereg2_plants.py, spike/harness3/prereg3_plants.py).
+Other result files quote shorter excerpts where they report a block, a quote
+or a target, merge-arm-candidates.jsonl and cheap-arm/anchors-silent-wrongs.txt
+among them. The corpora and their pins are named where each result was
+produced: spike/LOG.md and spike/PRE-REGISTRATION-2.md section 6.2, which
+prereg 3 keeps (spike/PRE-REGISTRATION-3.md section 1).
+
+That text is not this project's work and is not offered under CC-BY-4.0. It
+stays under its upstream terms, whatever they are at the pin it was taken
+from. NOTICE lists each corpus, its pins and the licence its tree holds there.
+The CC-BY-4.0 row covers what this project wrote around it: the records,
+figures, prompts, questions and plant texts.
+
+THIRD-PARTY EXCERPTS IN spike/results/prereg3/
+
+The rehearsal evidence under spike/results/prereg3/rehearsals/, the archives
+included, quotes synthetic test text. That text is taken from the docstrings
+of CPython 3.13 standard-library modules, as rendered by pydoc (the rehearsal
+builder, rehearsals/tools/build.py, lists the modules). The pydoc output links
+to docs.python.org/3.13. A few docstrings link to docs.python.org/3.11 in their
+own text. These excerpts are Copyright (c) the Python Software Foundation and
+contributors, and they keep their own licence, the Python Software Foundation
+License Version 2 (https://docs.python.org/3.13/license.html), whose text is
+in LICENSES/PSF-2.0.txt. That file is the Python 3.13 distribution's own
+licence file, /usr/lib/python3.13/LICENSE.txt from Debian's
+libpython3.13-stdlib 3.13.5-2+deb13u5, copied verbatim. The excerpts are not
+offered under CC-BY-4.0. The builder used no other outside source. The plant
+texts, prompts and harness output are this project's own.
+
+Full texts are in LICENSES/.
+
+WHY THE SPLIT
+
+The point of this project is independent implementations. That makes the
+reusability of the SPEC and the FIXTURES more important than the licence on any
+reference code.
+
+CommonMark embeds its conformance examples inside a CC-BY-SA spec document, so
+vendoring the test cases arguably vendors share-alike prose. These fixtures are
+meant to be vendored: copy them into an implementation in any language, under
+any licence, without obligation.

blockspec-0.1.0/LICENSES/Apache-2.0.txt

@@ -0,0 +1,73 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+
+     (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
+
+     (b) You must cause any modified files to carry prominent notices stating that You changed the files; and
+
+     (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
+
+     (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
+
+     You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!)  The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.