Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 21 additions & 6 deletions TRADEMARK.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,14 +40,29 @@ Usage — the two-gates model:
*referential* use is free: it is a factual statement that your product talks
to TigerTag chips. It must never be presented as a seal, a badge of quality,
or an implication of affiliation.
- **Anyone** may also write *"Compatible with TigerTag"* **in plain text** on
the packaging, product page or manual of a product that reads or writes
TigerTag chips (a reader, a printer, software) — the descriptive use trademark
law tolerates: no logo, no stylised lettering, no *"official"* or
*"certified"*, and never on a chip or a consumable.
- Only a **certified partner** (see *TigerTag Certified*, listed in
[the certified-partner registry](https://wiki.tigersystem.io/certified-partners/))
may apply the mark **on a chip, an inlay, a carrier, a
label, a spool, a resin bottle or its packaging**, use the TigerTag name
**commercially as a product designation**, or **issue TigerTag+ signatures**
— TigerTag holds the private key. Applied to a product, the mark no longer
says *"this works with TigerTag"*; it says *"this **is** a TigerTag"* — an
assertion about origin, which is ours to make.
may reproduce the TigerTag **logo or name** ("TigerTag", "TigerTag+",
"TigerTag+ Certified") **on an RFID / NFC chip of any format** — chip, inlay,
sticker, label, card, key fob, carrier — or **on a spool, a resin bottle, a
refill or their packaging**, use the TigerTag name **commercially as a product
designation**, or **issue TigerTag+ signatures** — TigerTag holds the private
key. Applied to a product, the mark no longer says *"this works with
TigerTag"*; it says *"this **is** a TigerTag"* — an assertion about origin,
which is ours to make. Writing TigerTag data into a chip's memory stays free.
- **On products, the rules are the Connectivity Standards Alliance's for
Zigbee and Matter**: a certified product **must display** the mark and is
listed in the registry; certified chips, inlays, carriers and reader modules
are **TigerTag Compliant Platforms** and do not certify the product they go
into; the mark never goes into a product, company, domain, subdomain or
social-handle name; the licence is limited and revocable. The one deliberate
difference: Matter is reserved to members, while the TigerTag referential
tier stays open to everyone, because the protocol is.
- **Reselling changes nothing.** Official chips are manufactured by
TigerSystem and already carry the mark. Any distributor or reseller of
genuine chips may describe and list them as official TigerTag product; they
Expand Down
8 changes: 5 additions & 3 deletions docs/developers/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,11 @@ The governance is deliberately two-gated: **anyone** may implement the
protocol and say "compatible with TigerTag" — no permission, ever — and show
the TigerTag logo, unmodified, to say so: in your app, your documentation, your
store listing. That referential use is free. Only **certified partners**
(listed in the certified registry) may apply the mark **on a chip, carrier,
spool or packaging**, where it stops describing compatibility and starts
asserting origin, and only they may issue **TigerTag+ signatures** (TigerTag
(listed in the certified registry) may put the mark — logo **or name** — **on a
chip of any format (chip, inlay, sticker, label, carrier), a spool or its
packaging**, where it stops describing compatibility and starts asserting
origin; plain-text *"Compatible with TigerTag"* on the box of a compatible
reader, printer or app stays free, and only they may issue **TigerTag+ signatures** (TigerTag
holds the private key). The trademark gate is marketing; the signature gate
is technical; **neither restricts the protocol by one line** — an uncertified
chip works perfectly, it just can't prove its origin.
Expand Down
6 changes: 3 additions & 3 deletions docs/products/tigertag-plus-certified.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,9 +58,9 @@ The byte-level layout — chip type ids, the 64-byte signature area at pages
## Who is certified

The authoritative list of manufacturers allowed to put the mark on a product is
the [certified partners registry](../certified-partners.md). A logo on a chip,
a carrier, a spool or its packaging is only authorized for the makers on that
page.
the [certified partners registry](../certified-partners.md). The TigerTag logo
or name on a chip of any format, a carrier, a spool or its packaging is only
authorized for the makers on that page.

---

Expand Down
6 changes: 3 additions & 3 deletions docs/products/tigertag.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,12 +85,12 @@ Who may say what, when a chip is for sale:
| **TigerSystem** | the chips it manufactures | **official** — made by us | yes — it applies the mark |
| **Any reseller or distributor** | those same genuine chips | **official** — the goods are | yes — the mark is already on them |
| **A third party TigerSystem has audited** | anything it built — chips, inlays, carriers, a device, an app | **certified** — granted, audited, listed, withdrawable | yes, on the product |
| **Anyone making their own chip** | their own compatible chip | *"compatible with TigerTag"* — and with **TigerTag+** if it verifies signatures. Never *"certified"*, which only TigerSystem grants | in their app, docs and store listing — **never on the chip, carrier, spool or packaging** |
| **Anyone making their own chip** | their own compatible chip | *"compatible with TigerTag"* — and with **TigerTag+** if it verifies signatures. Never *"certified"*, which only TigerSystem grants | in their app, docs and store listing; *"Compatible with TigerTag"* in plain text on a compatible device's box — **never the logo or the name on the chip (any format), carrier, spool or packaging** |

That last distinction is the whole trademark policy, and it is narrower than it
looks. Saying your product *talks to* TigerTag is a fact about your product,
and showing the logo to say so is free. Putting the mark **on** a chip is a
statement about **who made it** — it stops meaning "this works with TigerTag"
and showing the logo to say so is free. Putting the mark — logo or name —
**on** a chip of any format is a statement about **who made it** — it stops meaning "this works with TigerTag"
and starts meaning "this *is* a TigerTag". Only that second use needs written
authorization. See [TRADEMARK.md](../../TRADEMARK.md).

Expand Down
9 changes: 6 additions & 3 deletions i18n/fr/developers/README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
sourceHash: dbd78eb2f02db455a2f9d0c54788c50a84b2c83b37d02e49d90f48adbd504d71
sourceHash: 88f0499b9f2d256540c7d6eeb20351af9670b38bde5f3f53b982955732a3ea85
sourcePath: docs/developers/README.md
---

Expand Down Expand Up @@ -46,9 +46,12 @@ implémenter le protocole et dire « compatible avec TigerTag » — sans
autorisation, jamais — et afficher le logo TigerTag, non modifié, pour le dire :
dans votre application, votre documentation, votre fiche en boutique. Cet usage
référentiel est libre. Seuls les **partenaires certifiés** (listés dans le
registre des certifiés) peuvent apposer la marque **sur une puce, un support,
registre des certifiés) peuvent apposer la marque — logo **ou nom** — **sur une
puce de quelque format que ce soit (puce, inlay, sticker, étiquette, support),
une bobine ou un emballage**, où elle cesse de décrire une compatibilité pour
affirmer une origine, et eux seuls peuvent émettre des **signatures TigerTag+**
affirmer une origine ; la mention en texte seul « Compatible with TigerTag » sur
la boîte d'un lecteur, d'une imprimante ou d'une application compatibles reste
libre, et eux seuls peuvent émettre des **signatures TigerTag+**
(TigerTag détient la clé privée). La porte de la marque relève du marketing ;
la porte de la signature relève de la technique ; **aucune des deux ne
restreint le protocole d'une seule ligne** — une puce non certifiée fonctionne
Expand Down
7 changes: 4 additions & 3 deletions i18n/fr/products/tigertag-plus-certified.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
sourceHash: a441174f740b32338860a4b6a58babca49eed24ed8af7f05cf26e06f55cda504
sourceHash: e35244386df439d1c2c49dc5f9e8f384ea5b8f2bc1dfe8b8e90b4a7c73b8e5bd
sourcePath: docs/products/tigertag-plus-certified.md
---

Expand Down Expand Up @@ -68,8 +68,9 @@ signature de 64 octets aux pages `0x18`–`0x27` — est spécifiée dans

La liste faisant foi des fabricants autorisés à apposer la marque sur un
produit est le [registre des partenaires certifiés](../certified-partners.md).
Un logo sur une puce, un carrier, une bobine ou son emballage n'est autorisé
que pour les fabricants figurant sur cette page.
Le logo ou le nom TigerTag sur une puce de quelque format que ce soit, un
carrier, une bobine ou son emballage n'est autorisé que pour les fabricants
figurant sur cette page.

---

Expand Down
8 changes: 4 additions & 4 deletions i18n/fr/products/tigertag.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
sourceHash: dcfd1f98e794efef047aae6a14e78111ee8b126a62fb971e7d7913a851120144
sourceHash: 76ef763ccd1b41e1b5203fc1f2abe006e5e2b492e129510932ab728b6a57ae4e
sourcePath: docs/products/tigertag.md
---

Expand Down Expand Up @@ -95,13 +95,13 @@ Qui a le droit de dire quoi, lorsqu'une puce est mise en vente :
| **TigerSystem** | les puces qu'il fabrique | **officiel** — c'est nous | oui — c'est lui qui appose la marque |
| **Tout revendeur ou distributeur** | ces mêmes puces authentiques | **officiel** — la marchandise l'est | oui — la marque est déjà dessus |
| **Un tiers audité par TigerSystem** | tout ce qu'il a fabriqué — puces, inlays, carriers, un appareil, une application | **certifié** — accordé, audité, référencé, retirable | oui, sur le produit |
| **Quiconque fabrique sa propre puce** | sa propre puce compatible | *« compatible with TigerTag »* — et avec **TigerTag+** s'il vérifie les signatures. Jamais *« certified »*, que seul TigerSystem accorde | dans son application, sa documentation et sa fiche produit — **jamais sur la puce, le carrier, la bobine ou l'emballage** |
| **Quiconque fabrique sa propre puce** | sa propre puce compatible | *« compatible with TigerTag »* — et avec **TigerTag+** s'il vérifie les signatures. Jamais *« certified »*, que seul TigerSystem accorde | dans son application, sa documentation et sa fiche produit ; « Compatible with TigerTag » en texte seul sur la boîte d'un appareil compatible — **jamais le logo ni le nom sur la puce (quel que soit son format), le carrier, la bobine ou l'emballage** |

Cette dernière distinction constitue toute la politique de marque, et elle est
plus étroite qu'il n'y paraît. Dire que votre produit *dialogue avec* TigerTag
est un fait sur votre produit, et montrer le logo pour le dire est libre.
Apposer la marque **sur** une puce est une affirmation sur **qui l'a
fabriquée** : elle cesse de signifier « ceci fonctionne avec TigerTag » pour
Apposer la marque — logo ou nom — **sur** une puce, quel que soit son format,
est une affirmation sur **qui l'a fabriquée** : elle cesse de signifier « ceci fonctionne avec TigerTag » pour
signifier « ceci *est* un TigerTag ». Seul ce second usage demande une
autorisation écrite. Voir [TRADEMARK.md](../../TRADEMARK.md).

Expand Down
Loading