Public Beta
Declare

Write your vendor declaration

One document says what your print business is and can make, in the vocabulary — vendor-declaration/1. Fill it in here, validate it, download it, put it on your own domain at /.well-known/ptpge/declaration.json, and claim your identity. Nothing you type is stored on ptpge.org; the draft stays in this browser.

For print businesses without a tool that writes the document for them. If your MIS, web-to-print or an implementation such as a Vendor Profile builder already writes declaration.json, use that — the document is the same.

1 · Identity
What kind of vendor (pick all that apply)
2 · Capability — production lines One line per press or press family: its technology, what it prints on, which colour modes, what it finishes in-house. The declaration needs at least one.
Certifications and print standards held (optional)
3 · Offerings — the product templates you make A product template from the specification, the line that makes it, and the part of the template you accept — what you make, never what it costs (prices belong to an implementation, not to the declaration). Offerings may be empty — identity and capability alone is a valid declaration.
4 · The document
Your identity mark (ptpge-id/1)


  

Then

  1. Put the file on your domain at https://<domain>/.well-known/ptpge/declaration.json (served as application/json).
  2. Claim the identity on ptpge.org/adopt — the register checks that the file is there and validates; nothing is copied.
  3. Change the file whenever your capability changes; the register re-checks weekly.

This page writes the document; it does not host it, price anything, match requests or list you anywhere. Those are services implementations offer on top of the specification.