License and trademark
This page explains what may be reused, what the project name protects, and which uses imply an official relationship. It is a project policy, not legal advice; organizations with a legal question should consult their own counsel.
Quick reference
| Material | Current license |
|---|---|
| Source code, packages, examples, adapters, gateway, and website implementation | Apache-2.0 unless a file states otherwise |
| Specification and explanatory documentation | Intended to use CC BY 4.0; until a file carries its own notice, the repository's Apache-2.0 terms control |
| Code samples in documentation | The same terms as repository code; they may be used directly in an application |
| "Pling", "Page Intelligence", and the π project mark | Use to refer accurately to the project; do not imply official, sponsored, or certified status |
Source code
The source code in this repository is licensed under the Apache License 2.0 unless a file carries a different notice. This includes the packages, examples, adapters, gateway code, and website implementation.
The license permits commercial and non-commercial use, modification, and distribution. It also includes an express patent grant. If you distribute a modified build, keep the required notices and identify your changes. The NOTICE file must remain with distributions that include it.
The software is provided without warranty. A successful test run, demonstration, or conformance check does not create a warranty, service-level agreement, or security certification.
Specification and explanatory text
The project intends the protocol specification and explanatory documentation to be reusable under Creative Commons Attribution 4.0 (CC BY 4.0). That license would allow sharing and adaptation, including commercially, when attribution is preserved and modifications are indicated.
Until a specification or documentation file carries its own explicit license notice, the repository's Apache-2.0 license remains controlling. Do not infer a separate grant from this page alone. Contact the maintainers if the applicable notice is unclear before republishing a modified specification.
Code samples inside documentation follow the repository code license and may be used in an application without attribution beyond what Apache-2.0 requires.
The Pling name and marks
"Pling", "Page Intelligence", and the π project mark identify this project and its official distributions. This page does not claim a registered trademark; trademark rights can exist through use even when no registration is recorded.
You may use the names to refer accurately to the project, compare implementations, report defects, or describe compatible software. You may not use the name, logo, or visual identity to suggest that a fork, product, service, or deployment is official, sponsored, or certified when it is not.
A fork should make its origin clear and should not remove notices that identify the upstream project. It may state that it implements the Pling Surface protocol; it may not present itself as "Pling" or use the official mark as its own product identity.
Conformance is not certification
The 0.1 Surface protocol is a public draft. There is no certification mark, paid conformance program, or official register of approved implementations. The repository contains conformance helpers and test vectors, but passing them does not grant permission to use the project name as a certification.
If a conformance or compatibility program is created later, its criteria, fees if any, appeal process, and permitted claims must be published before the program is announced.
Third-party software
Packages depend on third-party libraries under their own licenses. A distribution should preserve the license and notice information required by those dependencies. The repository lockfile identifies resolved versions; it is not a substitute for a dependency-license review in a regulated or high-risk deployment.
Examples, customer applications, and third-party models are not relicensed by this project merely because they use Pling. Their own terms continue to apply.