The schemas
The vocabulary is used in five kinds of document. Two say what a company is and offers; two carry one deal between a buyer and a printer; one puts the identity on a checkout line. Each has a schema with a permanent URI. A document carries its owner; the schema carries none.
| Document | Who writes it | What it holds | Schema |
|---|---|---|---|
| Vendor declaration | a printer, or its MIS | identity · capability · offerings — published at /.well-known/ptpge/declaration.json | ptpge.org/v1/schemas/vendor-declaration/1 |
| Supplier catalogue | a paper or equipment maker | the maker's series and models, in the vocabulary — published at /.well-known/ptpge/catalogue.json | …/schemas/supplier-catalogue/1 |
| Request | a buyer or an agent | a configuration and a quantity, asked of one or many vendors | …/schemas/request/1 |
| Quote | a printer, in answer to a request | price · quantity · delivery · validity, for one configuration | …/schemas/quote/1 |
| UCP manifest | a storefront | the PTPGE identity on a checkout line | …/schemas/ucp-manifest/1 |
Status: draft — all five JSON Schemas are published (2026-10-10): vendor-declaration/1, supplier-catalogue/1, request/1, quote/1 and ucp-manifest/1. A quote repeats the request's fingerprint, so the two can be matched by anyone; a UCP manifest points at the declaration instead of repeating it. The rule they set: what a document says about products and options, it says with term URIs, not labels; a press is a supplier plus the maker's model designation; an offering is a product template plus, per variable, the values accepted. Today ptpge.org checks that a declaration or catalogue is reachable at its known path and carries its identity; validation against the schema follows, on ptpge.org and on the open MCP server.