Skip to content

Commit c66c1dc

Browse files
BenGlutBenGlut
committed
docs: trademark — no logo or name on a chip of any format; CSA rules on products
Aligns the wiki with the RFID guide's TRADEMARK.md and CERTIFICATION.md: - the TigerTag logo or name (TigerTag, TigerTag+, TigerTag+ Certified) on an RFID / NFC chip of any format, a spool, bottle, refill or their packaging is reserved to certified partners; - "Compatible with TigerTag" in plain text on the packaging of a compatible reader, printer or software stays free (nominative use); - on products the rules are the Connectivity Standards Alliance's (Zigbee / Matter): mandatory display, registry listing, Compliant Platform for components, no mark in product / domain / handle names, revocable licence; the referential tier stays open because the protocol is. English and French pages updated together; French source hashes refreshed.
1 parent a5c73b0 commit c66c1dc

7 files changed

Lines changed: 46 additions & 25 deletions

File tree

‎TRADEMARK.md‎

Lines changed: 21 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -40,14 +40,29 @@ Usage — the two-gates model:
4040
*referential* use is free: it is a factual statement that your product talks
4141
to TigerTag chips. It must never be presented as a seal, a badge of quality,
4242
or an implication of affiliation.
43+
- **Anyone** may also write *"Compatible with TigerTag"* **in plain text** on
44+
the packaging, product page or manual of a product that reads or writes
45+
TigerTag chips (a reader, a printer, software) — the descriptive use trademark
46+
law tolerates: no logo, no stylised lettering, no *"official"* or
47+
*"certified"*, and never on a chip or a consumable.
4348
- Only a **certified partner** (see *TigerTag Certified*, listed in
4449
[the certified-partner registry](https://wiki.tigersystem.io/certified-partners/))
45-
may apply the mark **on a chip, an inlay, a carrier, a
46-
label, a spool, a resin bottle or its packaging**, use the TigerTag name
47-
**commercially as a product designation**, or **issue TigerTag+ signatures**
48-
— TigerTag holds the private key. Applied to a product, the mark no longer
49-
says *"this works with TigerTag"*; it says *"this **is** a TigerTag"* — an
50-
assertion about origin, which is ours to make.
50+
may reproduce the TigerTag **logo or name** ("TigerTag", "TigerTag+",
51+
"TigerTag+ Certified") **on an RFID / NFC chip of any format** — chip, inlay,
52+
sticker, label, card, key fob, carrier — or **on a spool, a resin bottle, a
53+
refill or their packaging**, use the TigerTag name **commercially as a product
54+
designation**, or **issue TigerTag+ signatures** — TigerTag holds the private
55+
key. Applied to a product, the mark no longer says *"this works with
56+
TigerTag"*; it says *"this **is** a TigerTag"* — an assertion about origin,
57+
which is ours to make. Writing TigerTag data into a chip's memory stays free.
58+
- **On products, the rules are the Connectivity Standards Alliance's for
59+
Zigbee and Matter**: a certified product **must display** the mark and is
60+
listed in the registry; certified chips, inlays, carriers and reader modules
61+
are **TigerTag Compliant Platforms** and do not certify the product they go
62+
into; the mark never goes into a product, company, domain, subdomain or
63+
social-handle name; the licence is limited and revocable. The one deliberate
64+
difference: Matter is reserved to members, while the TigerTag referential
65+
tier stays open to everyone, because the protocol is.
5166
- **Reselling changes nothing.** Official chips are manufactured by
5267
TigerSystem and already carry the mark. Any distributor or reseller of
5368
genuine chips may describe and list them as official TigerTag product; they

‎docs/developers/README.md‎

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,11 @@ The governance is deliberately two-gated: **anyone** may implement the
3838
protocol and say "compatible with TigerTag" — no permission, ever — and show
3939
the TigerTag logo, unmodified, to say so: in your app, your documentation, your
4040
store listing. That referential use is free. Only **certified partners**
41-
(listed in the certified registry) may apply the mark **on a chip, carrier,
42-
spool or packaging**, where it stops describing compatibility and starts
43-
asserting origin, and only they may issue **TigerTag+ signatures** (TigerTag
41+
(listed in the certified registry) may put the mark — logo **or name** — **on a
42+
chip of any format (chip, inlay, sticker, label, carrier), a spool or its
43+
packaging**, where it stops describing compatibility and starts asserting
44+
origin; plain-text *"Compatible with TigerTag"* on the box of a compatible
45+
reader, printer or app stays free, and only they may issue **TigerTag+ signatures** (TigerTag
4446
holds the private key). The trademark gate is marketing; the signature gate
4547
is technical; **neither restricts the protocol by one line** — an uncertified
4648
chip works perfectly, it just can't prove its origin.

‎docs/products/tigertag-plus-certified.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -58,9 +58,9 @@ The byte-level layout — chip type ids, the 64-byte signature area at pages
5858
## Who is certified
5959

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

6565
---
6666

‎docs/products/tigertag.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -85,12 +85,12 @@ Who may say what, when a chip is for sale:
8585
| **TigerSystem** | the chips it manufactures | **official** — made by us | yes — it applies the mark |
8686
| **Any reseller or distributor** | those same genuine chips | **official** — the goods are | yes — the mark is already on them |
8787
| **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 |
88-
| **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** |
88+
| **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** |
8989

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

‎i18n/fr/developers/README.md‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
sourceHash: dbd78eb2f02db455a2f9d0c54788c50a84b2c83b37d02e49d90f48adbd504d71
2+
sourceHash: 88f0499b9f2d256540c7d6eeb20351af9670b38bde5f3f53b982955732a3ea85
33
sourcePath: docs/developers/README.md
44
---
55

@@ -46,9 +46,12 @@ implémenter le protocole et dire « compatible avec TigerTag » — sans
4646
autorisation, jamais — et afficher le logo TigerTag, non modifié, pour le dire :
4747
dans votre application, votre documentation, votre fiche en boutique. Cet usage
4848
référentiel est libre. Seuls les **partenaires certifiés** (listés dans le
49-
registre des certifiés) peuvent apposer la marque **sur une puce, un support,
49+
registre des certifiés) peuvent apposer la marque — logo **ou nom** — **sur une
50+
puce de quelque format que ce soit (puce, inlay, sticker, étiquette, support),
5051
une bobine ou un emballage**, où elle cesse de décrire une compatibilité pour
51-
affirmer une origine, et eux seuls peuvent émettre des **signatures TigerTag+**
52+
affirmer une origine ; la mention en texte seul « Compatible with TigerTag » sur
53+
la boîte d'un lecteur, d'une imprimante ou d'une application compatibles reste
54+
libre, et eux seuls peuvent émettre des **signatures TigerTag+**
5255
(TigerTag détient la clé privée). La porte de la marque relève du marketing ;
5356
la porte de la signature relève de la technique ; **aucune des deux ne
5457
restreint le protocole d'une seule ligne** — une puce non certifiée fonctionne

‎i18n/fr/products/tigertag-plus-certified.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
sourceHash: a441174f740b32338860a4b6a58babca49eed24ed8af7f05cf26e06f55cda504
2+
sourceHash: e35244386df439d1c2c49dc5f9e8f384ea5b8f2bc1dfe8b8e90b4a7c73b8e5bd
33
sourcePath: docs/products/tigertag-plus-certified.md
44
---
55

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

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

7475
---
7576

‎i18n/fr/products/tigertag.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
sourceHash: dcfd1f98e794efef047aae6a14e78111ee8b126a62fb971e7d7913a851120144
2+
sourceHash: 76ef763ccd1b41e1b5203fc1f2abe006e5e2b492e129510932ab728b6a57ae4e
33
sourcePath: docs/products/tigertag.md
44
---
55

@@ -95,13 +95,13 @@ Qui a le droit de dire quoi, lorsqu'une puce est mise en vente :
9595
| **TigerSystem** | les puces qu'il fabrique | **officiel** — c'est nous | oui — c'est lui qui appose la marque |
9696
| **Tout revendeur ou distributeur** | ces mêmes puces authentiques | **officiel** — la marchandise l'est | oui — la marque est déjà dessus |
9797
| **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 |
98-
| **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** |
98+
| **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** |
9999

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

0 commit comments

Comments
 (0)