aas-submodel-validate 0.1.0__tar.gz

aas_submodel_validate-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,127 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install ruff==0.16.3
+      - run: ruff check .
+      - run: pip install -e .
+      - name: the generated rule table matches its generator
+        run: python tools/extract_smt_rules.py --check
+      - name: the vendored official material matches its recorded hashes
+        run: python tools/vendor_template.py --check
+      - name: readers the battery-passport extractors import
+        run: pip install openpyxl pymupdf
+      - name: the battery-passport indexes agree with themselves
+        run: python tools/battery_data_check.py
+      - name: the battery rule table matches its generator
+        run: python tools/extract_battery_rules.py --check
+
+  test:
+    name: py${{ matrix.python }} ${{ matrix.label }} on ${{ matrix.os }}
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - { os: ubuntu-latest, python: "3.9" }
+          - { os: ubuntu-latest, python: "3.10" }
+          - { os: ubuntu-latest, python: "3.11" }
+          - { os: ubuntu-latest, python: "3.12" }
+          # aas-core3.0's own CI matrix stops at 3.12, so this row is the
+          # floor dependency's first verdict on 3.13 -- a failure here is
+          # information, not noise.
+          - { os: ubuntu-latest, python: "3.13" }
+          # pyproject declares aas-core3.0>=1.1.4, so 1.1.4 exactly is what
+          # this row runs: a floor test that floats stops testing the floor.
+          - { os: ubuntu-latest, python: "3.11", pin: "aas-core3.0==1.1.4", label: "floor" }
+          # Windows is where an unclosed ZIP handle keeps files locked, and
+          # where a checkout could hand the suite different bytes than the
+          # ones whose hashes were recorded.
+          - { os: windows-latest, python: "3.11" }
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python }}
+      - run: pip install -e ".[dev]"
+      - if: matrix.pin
+        run: pip install "${{ matrix.pin }}"
+      - run: pytest -q
+      - name: every rule id fired somewhere
+        run: python tools/rule_coverage.py --check
+      # Also in the lint job, deliberately: this one runs on every OS in
+      # the matrix, and end-of-line damage is a property of the checkout,
+      # not of the commit. A hash verified only where the file was written
+      # verifies nothing about the machine that unpacks it.
+      - name: the vendored bytes survived this checkout
+        run: python tools/vendor_template.py --check
+
+  wheel:
+    # The failure this exists for: a wheel that installs but is missing the
+    # vendored template, so the tool works from a checkout and its NOTICE
+    # lies about what it ships. Nothing in the test suite (editable install)
+    # would notice.
+    name: installed wheel
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install build
+      - run: python -m build --wheel --outdir dist/
+      - name: the wheel must carry the vendored template and not the corpus
+        run: |
+          python - <<'PY'
+          import glob, sys, zipfile
+          names = set(zipfile.ZipFile(glob.glob("dist/*.whl")[0]).namelist())
+          required = [
+              "aas_submodel_validate/data/smt/02004/2.0.1/template.json",
+              "aas_submodel_validate/data/smt/02004/2.0.1/sha256sums.txt",
+              "aas_submodel_validate/data/smt/02003/2.0.1/template.json",
+              "aas_submodel_validate/data/smt/02003/2.0.1/sha256sums.txt",
+              "aas_submodel_validate/data/smt/02035-2/1.0/template.json",
+              "aas_submodel_validate/data/smt/02035-2/1.0/sha256sums.txt",
+          ]
+          missing = [n for n in required if n not in names]
+          if missing:
+              sys.exit("missing from the wheel: %s" % missing)
+          strays = sorted(n for n in names if "corpus" in n or n.startswith("tests/"))
+          if strays:
+              sys.exit("the wheel carries test material it should not: %s" % strays[:5])
+          print("wheel carries the template, and no corpus")
+          PY
+      - name: no distribution carries what it must not
+        # The same check the release runs. Here on every push, because a
+        # release line first exercised on the day of the release is one
+        # that dies on the day of the release.
+        run: python tools/check_distributions.py
+      - name: the single file builds twice to the same bytes and answers
+        run: |
+          python tools/build_zipapp.py -o dist/smtv.pyz --check
+          python tools/build_zipapp.py -o /tmp/again.pyz
+          cmp dist/smtv.pyz /tmp/again.pyz
+      - name: install into a clean environment and smoke-test
+        run: |
+          python -m venv /tmp/v
+          /tmp/v/bin/pip install --quiet dist/*.whl
+          /tmp/v/bin/smtv --version
+          /tmp/v/bin/aas-submodel-validate --rules > /dev/null

aas_submodel_validate-0.1.0/.github/workflows/dco.yml

@@ -0,0 +1,29 @@
+# Every pull-request commit must carry a Signed-off-by line — the Developer
+# Certificate of Origin, explained in CONTRIBUTING.md. Checked here rather
+# than trusted, for the same reason everything else in this repository is.
+name: dco
+
+on: pull_request
+
+permissions:
+  contents: read
+
+jobs:
+  signoff:
+    name: every commit certifies its origin
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: look for Signed-off-by on each commit in the range
+        run: |
+          missing=0
+          for sha in $(git rev-list --no-merges \
+              "${{ github.event.pull_request.base.sha }}..${{ github.event.pull_request.head.sha }}"); do
+            if ! git log -1 --format=%B "$sha" | grep -Eq '^Signed-off-by: .+ <.+@.+>'; then
+              echo "::error::commit $sha has no Signed-off-by line (git commit -s; see CONTRIBUTING.md)"
+              missing=1
+            fi
+          done
+          exit "$missing"

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

@@ -0,0 +1,104 @@
+# Runs when a version tag is pushed. Proves the tree green, builds the
+# wheel, the sdist and the single file, proves the single file
+# reproducible by building it twice, attaches everything to a GitHub
+# Release with the checksums beside it -- for the air-gapped audience,
+# "the hash on the release page is the hash of the file I carried in" is
+# the entire trust story -- and then publishes the same bytes to PyPI.
+#
+# Until pypi.org trusts this repository for this project, the publish job
+# fails visibly, on purpose, without touching the GitHub Release above.
+name: release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: the tag and the version agree
+        # Three places say the version -- the package, the tag and the
+        # CHANGELOG -- and a release where they disagree is one nobody
+        # can cite later.
+        run: |
+          pip install -e ".[dev]"
+          v="$(python -c 'import aas_submodel_validate as m; print(m.__version__)')"
+          [ "$GITHUB_REF_NAME" = "v$v" ] || { echo "tag $GITHUB_REF_NAME != version $v"; exit 1; }
+          heading="$(grep -m1 "^## $v — " CHANGELOG.md)" || { echo "CHANGELOG has no heading for $v"; exit 1; }
+          case "$heading" in
+            *unreleased*) echo "CHANGELOG still says: $heading"; exit 1 ;;
+          esac
+          echo "$heading" | grep -qE ' — [0-9]{4}-[0-9]{2}-[0-9]{2}$' \
+            || { echo "CHANGELOG heading carries no date: $heading"; exit 1; }
+
+      - name: everything must be green first
+        # The readers the battery extractors import are installed here
+        # too, not only in CI. Without them that gate reports a skip and
+        # passes -- so a release would have run a weaker check than every
+        # push that led to it, which is the wrong way round.
+        run: |
+          pip install openpyxl pymupdf
+          make check
+
+      - name: build the wheel and the sdist
+        run: |
+          pip install build
+          python -m build
+
+      - name: no distribution carries what it must not
+        # Nothing this repository does not track, and not the
+        # requirements indexes -- asked of what the archives contain.
+        run: python tools/check_distributions.py
+
+      - name: build the single file twice; the hashes must match
+        run: |
+          python tools/build_zipapp.py -o dist/smtv.pyz --check
+          python tools/build_zipapp.py -o /tmp/again.pyz
+          cmp dist/smtv.pyz /tmp/again.pyz
+          echo "reproducible: yes"
+
+      - name: one checksum file beside them
+        run: cd dist && shasum -a 256 * > SHA256SUMS && cat SHA256SUMS
+
+      # The publisher below uploads exactly these bytes; nothing is rebuilt.
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+          if-no-files-found: error
+
+      - name: attach them to a GitHub Release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          gh release create "$GITHUB_REF_NAME" dist/* \
+            --title "$GITHUB_REF_NAME" \
+            --notes "See CHANGELOG.md. Verify what you download: \`shasum -a 256 -c SHA256SUMS\`. The .pyz needs only a Python — \`python smtv.pyz your-submodel.aasx\`; it reaches no network and neither does the tool."
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist
+      - name: only the wheel and the sdist go to PyPI
+        run: mkdir up && cp dist/aas_submodel_validate-*.whl dist/aas_submodel_validate-*.tar.gz up/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: up

aas_submodel_validate-0.1.0/CHANGELOG.md

@@ -0,0 +1,49 @@
+# Changelog
+
+## 0.1.0 — 2026-09-04
+
+First release: 125 rules, 123 of them across three IDTA templates — *Handover
+Documentation* 2.0.1, *Technical Data* 2.0.1 and *Digital Battery
+Passport part 2* 1.0 — of which 86 are generated from the vendored
+official template files. The `meta` channel
+relays aas-core3.0's metamodel verification rather than restating it;
+four input forms are read (.aasx with XML or JSON payload, environment
+.json/.xml, bare Submodel .json); XML arrives in whichever encoding the
+parser reads — UTF-8 or UTF-16, marked or not — and is decoded that way
+before the DTD refusal looks at it, so the refusal covers what the
+parser covers; every finding carries a remedy
+sentence; and the official example is pinned by name — defects and all.
+What this reader takes in is bounded whichever way a document arrives —
+one document at 64 MiB, a container's parts at 64 MiB each and 256 MiB
+together, and a container's directory of names at 16 MiB, which is a
+different kind of cost: a ZIP is indexed whole before any of it is read,
+so it falls on how many names an archive declares rather than on what its
+entries hold — and what it refuses to read, it does not judge: `summary.complete`
+in the JSON report and a clause on the terminal summary say when the
+counts describe less than the whole input. `summary.judged` says the
+sharper thing beside it — whether anything reached the rules at all — and
+an input that was refused rather than judged leaves by the could-not-run
+exit code, 2, where it used to leave by the code for a verdict. Both
+fields are additive, so `schemaVersion` stays 1.
+IDTA 02035-2 shares 02004's submodel identifier, so `--profile` chooses
+which of the two answers and SMT-D2 reports the choice; without the flag
+02004 answers. `rulesChecked` in the JSON report counts every registered
+rule, so it counts all 125 whichever template answered.
+Two rules read the battery passport against Regulation (EU) 2023/1542
+rather than against a template, from a table generated out of the
+requirements indexes published in `data/battery-passport/`: `BAT-R2`
+names a submodel identifier two published templates claim and this tool
+has a table for neither of, and `BAT-R8` reports an element the template
+permits to be absent that a legal reading requires of every battery
+category. Eight further disagreements are known and not reported,
+because whether the law requires them depends on a category no rule here
+reads; the report counts them rather than keeping quiet about them. Both
+rules are warnings — two published readings of applicability exist and
+this pack cannot yet be told which to answer for.
+
+The JSON report's shape is written down in `docs/report-schema.md`, and
+carries two more fields: `toolVersion`, because the shape's number and
+the producer's are different numbers and a defect report needs the
+second; and `options`, because the flags move the verdict — the same file
+comes back `ok` under one set and not another — and two reports that did
+not say which run they were could not be compared.

aas_submodel_validate-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,69 @@
+# Contributing
+
+## Certify your commits (DCO)
+
+Every commit needs a sign-off line:
+
+```
+Signed-off-by: Your Name <you@example.com>
+```
+
+`git commit -s` writes it for you; `git commit --amend -s` repairs a
+forgotten one. The line certifies the [Developer Certificate of
+Origin 1.1](https://developercertificate.org/) — that you wrote the change
+or otherwise have the right to submit it under this project's licence. That
+is the whole deal: you keep your copyright, your contribution arrives under
+Apache-2.0 like everything here (inbound = outbound), and the project keeps
+a provenance trail it can show anyone who asks — which, for a tool courting
+a standards body, someone eventually will. There is no CLA and no paperwork;
+a certificate of origin is a statement of fact, not a transfer of rights.
+
+Pull requests are checked for the line automatically.
+
+The certificate, verbatim:
+
+```
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.
+```
+
+## Adding a rule
+
+A rule is born red: commit a fixture that violates it and one that does
+not, watch the violation test fail, then implement. Every rule carries a
+`fix` sentence — what to change so the finding stops being reported, not
+the requirement restated in the imperative — and every rule id must fire
+somewhere in the suite. Match by semanticId, never by idShort
+(docs/divergences.md explains why, with the template's own words).

aas_submodel_validate-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 2026 Wooyong Lee (dev365code)
+
+   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.

aas_submodel_validate-0.1.0/MANIFEST.in

@@ -0,0 +1,17 @@
+# A downstream packager who unpacks the sdist and runs pytest must find a
+# runnable suite -- so conftest, the builders, the vendored corpus and the
+# tools the tests import all ship, not just the test_*.py files setuptools
+# would include on its own.
+graft tests
+graft tools
+graft docs
+graft .github
+include Makefile MANIFEST.in
+include CONTRIBUTING.md SECURITY.md NOTICE THIRD_PARTY.md CHANGELOG.md
+global-exclude __pycache__/* *.pyc
+recursive-exclude tests .rule-coverage.json
+
+# Working notes are not part of the distribution.
+exclude CLAUDE.md AGENTS.md
+prune .claude
+exclude docs/findings.md docs/audits.md

aas_submodel_validate-0.1.0/Makefile

@@ -0,0 +1,48 @@
+# Everything CI's lint and test gates run, runnable before you push, because a
+# gate that exists in one place and not the other fails quietly in the
+# dangerous direction. tests/test_ci_parity.py holds the two in step.
+
+RUFF_VERSION := 0.16.3
+PYTHON       ?= python3
+export PYTHONPATH := $(CURDIR)/src:$(CURDIR)/tests
+
+.PHONY: help check test lint fix dev generated vendored exercised
+
+help:
+	@echo "make check   everything CI runs: lint, gates, the test suite"
+	@echo "make test    the test suite alone"
+	@echo "make lint    ruff, pinned to the version CI uses"
+	@echo "make generated  the generated rule table still matches its generator"
+	@echo "make vendored   the vendored official material matches its hashes"
+	@echo "make exercised  every rule id fired somewhere in the suite"
+	@echo "make fix     ruff --fix, for what it can correct itself"
+	@echo "make dev     install the pinned dev tools"
+
+check: lint generated vendored battery-data test exercised
+
+generated:
+	$(PYTHON) tools/extract_smt_rules.py --check
+
+vendored:
+	$(PYTHON) tools/vendor_template.py --check
+
+exercised:
+	$(PYTHON) tools/rule_coverage.py --check
+
+battery-data:
+	$(PYTHON) tools/battery_data_check.py
+	$(PYTHON) tools/extract_battery_rules.py --check
+
+lint:
+	@$(PYTHON) -m ruff --version | grep -q "$(RUFF_VERSION)" \
+		|| { echo "ruff $(RUFF_VERSION) required (make dev)"; exit 1; }
+	$(PYTHON) -m ruff check .
+
+test:
+	$(PYTHON) -m pytest -q
+
+fix:
+	$(PYTHON) -m ruff check --fix .
+
+dev:
+	$(PYTHON) -m pip install --user "ruff==$(RUFF_VERSION)" "pytest>=7" "aas-core3.0>=1.1.4,<2"

aas_submodel_validate-0.1.0/NOTICE

@@ -0,0 +1,19 @@
+aas-submodel-validate
+Copyright 2026 Wooyong Lee
+
+This distribution contains material from the IDTA submodel-templates
+repository (https://github.com/admin-shell-io/submodel-templates),
+licensed under the Creative Commons Attribution 4.0 International
+License (CC BY 4.0, https://creativecommons.org/licenses/by/4.0/):
+
+  - src/aas_submodel_validate/data/smt/02004/2.0.1/template.json
+    (IDTA 02004-2-0-1 Handover Documentation template, unmodified)
+  - src/aas_submodel_validate/data/smt/02003/2.0.1/template.json
+    (IDTA 02003 2.0.1 Technical Data template, unmodified)
+  - src/aas_submodel_validate/data/smt/02035-2/1.0/template.json
+    (IDTA 02035-2 1.0 Digital Battery Passport part 2, Handover
+    Documentation template, unmodified)
+
+Copyright for that material: Industrial Digital Twin Association (IDTA)
+and the template's contributors. See THIRD_PARTY.md for the pinned
+revision and verification hashes.