@hyperscale0/udl 3.0.2 → 3.2.0

package/LICENSING.md

@@ -1,50 +0,0 @@
-# Licensing
-
-The code in this repository is Copyright 2026 Hyperscale LLC and is licensed
-under the GNU Affero General Public License version 3 only
-(`AGPL-3.0-only`). The full text is in [`LICENSE`](./LICENSE).
-
-## What the AGPL asks of you
-
-Two obligations matter in practice.
-
-**If you distribute a copy in object form**, modified or not, you make its
-Corresponding Source available under the same license.
-
-**If you run a modified copy as a network service**, section 13 applies: the
-users interacting with it over the network get an offer of the source of the
-version you are running. Running UDL unmodified behind your own service does
-not trigger this. Changing the parser, the validator, or the canonical
-serializer and then serving that change does.
-
-Using `@hyperscale0/udl` as a library inside your own program is a combined
-work under the AGPL. If that does not fit how you ship, take the commercial
-license instead.
-
-## Commercial license
-
-Hyperscale LLC sells a commercial license to organisations that cannot accept
-the AGPL, for the usual reasons: a proprietary product that links the library,
-a hosted service you will not open, a procurement policy that refuses copyleft.
-It grants the same code under ordinary commercial terms with no source
-obligation.
-
-Ask through <https://hyperscale0.ai>.
-
-## The license covers code, not marks
-
-"Hyperscale" and "UDL" are trademarks of Hyperscale LLC. A copyright license
-says nothing about trademarks in either direction, so
-[`TRADEMARKS.md`](./TRADEMARKS.md) draws that boundary.
-
-## The format is not the implementation
-
-UDL the format is separate from this implementation of it. The JSON Schema in
-[`spec/`](./spec) is data describing a format, and anyone may write their own parser, validator,
-or serializer against them, in any language, under any license, without
-touching this code.
-
-What you may then say about it is a trademark question, not a copyright one.
-[`TRADEMARKS.md`](./TRADEMARKS.md) has the rule: claim compatibility with a UDL
-version only when your implementation passes that version's published
-conformance cases unmodified.

package/TRADEMARKS.md

@@ -1,35 +0,0 @@
-# Trademarks
-
-"Hyperscale" and "UDL" are trademarks of Hyperscale LLC.
-
-The AGPL covers the code in this repository and nothing else. It grants no
-rights to the marks, and it never mentions them: a copyright license says
-nothing about trademarks either way. This file draws that boundary so nobody
-has to guess where it sits.
-
-What that means in practice:
-
-- **Yes.** Say your project uses UDL, reads UDL, or is compatible with UDL.
-  Say it in your README, your docs, your talk, and your package description.
-  Fork this repository and keep the notices intact.
-- **Yes.** Publish a UDL implementation in another language, and name it in a
-  way that describes what it does: `udl-rs`, `udl-parser`, `python-udl`.
-- **No.** Name your project, company, or product in a way that suggests
-  Hyperscale LLC published it or endorses it. `@hyperscale0/*` on npm and the
-  `hyperscale0` GitHub organisation are ours.
-- **No.** Use the marks or our logo in a way that implies affiliation,
-  sponsorship, or certification we have not given.
-
-## Claiming compatibility
-
-An independent implementation may say it "implements UDL version X" or "passes
-the UDL conformance suite version X" only while it passes the published
-conformance cases for that version, unmodified. The cases in
-[`test/language.spec.ts`](./test/language.spec.ts) are the whole test: no skipped case, no edited
-expectation, no local change to the document mutations.
-
-That claim is a statement about your implementation, so keep the marks out of
-its name and off its logo, and do not present it as endorsement or
-certification by Hyperscale LLC. We certify nothing; the suite does.
-
-If you are unsure, open an issue and ask. Nobody has ever regretted asking.