To the extent possible under law, the editors have waived all copyright
and related or neighboring rights to this work.
In addition, as of 21 March 2018,
the editors have made this specification available under the Open Web Foundation Agreement Version 1.0,
which is available at http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0.
Parts of this work may be from another specification document. If so, those parts are instead covered by the license of that specification document.
Abstract
This specification defines a standard for sticker compatibility from multiple vendors.
By following this specification, implementors can ensure they meet the expectations of sticker consumers.
A standard allow producers to supply tools that help ensure maximum compliance and enjoyability.
Introduction
This section is non-normative.
1. Types of Stickers
1.1. Square Sticker
A square sticker must be represented by a square with sides that should measure 5.08 centimeters, and must remain within 1 millimeter tolerance.
These tolerances allow for square stickers with sides that measure between 4.98 and 5.18 centimeters.
1.2. Hexagon Sticker
A hexagon sticker must be represented by a regular hexagon where the largest diagonals should measure 5.08 centimeters, and which must remain within 1 millimeter tolerance.
The sticker must be oriented with a vertex positioned at the top.
These tolerances allow for diagonals measuring between 4.98 and 5.18 centimeters.
2. On Non-conforming Stickers
This section is non-normative.
When you exchange stickers, you may be given a sticker that does not conform to this specification.
If this is the case, thank them for the time spent on designing and printing the sticker.
Acknowledgements
The editor would like to thank
Jason Denizac,
Yoshua Wuyts,
Máirín Duffy,
and Max Ogden
for their contributions to this specification.
Conformance
Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
in the normative parts of this document
are to be interpreted as described in RFC 2119.
However, for readability,
these words do not appear in all uppercase letters in this specification.
All of the text of this specification is normative
except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
Examples in this specification are introduced with the words “for example”
or are set apart from the normative text with class="example", like this:
This is an example of an informative example.
Informative notes begin with the word “Note”
and are set apart from the normative text with class="note", like this:
