Skip to content

Commit ed066b6

Browse files
committed
feat: clarify and add more TEI types
Signed-off-by: Pavel Shukhman <[email protected]>
1 parent 2981f2a commit ed066b6

File tree

1 file changed

+48
-8
lines changed

1 file changed

+48
-8
lines changed

discovery/readme.md

Lines changed: 48 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -150,17 +150,57 @@ Example:
150150
urn:tei:uuid:cyclonedx.org:443:d4d9f54a-abcf-11ee-ac79-1a52914d44b1
151151
```
152152

153+
#### EAN/UPC
153154

154-
#### Other types to be defined
155+
Where the `unique-identifier` is a EAN/UPC.
155156

156-
- EAN
157-
- GS1
158-
- STD
157+
Syntax:
158+
159+
```text
160+
urn:tei:eanupc:<domain-name>:<domain-port>:<ean/upc-number>
161+
````
162+
163+
Example:
164+
```text
165+
urn:tei:eanupc:cyclonedx.org:443:1234567890123
166+
```
167+
168+
#### GTIN
169+
170+
Where the `unique-identifier` is a [GTIN](https://www.gs1.org/standards/id-keys/gtin).
171+
172+
Syntax:
173+
174+
```text
175+
urn:tei:gtin:<domain-name>:<domain-port>:<gtin-number>
176+
````
177+
178+
Example:
179+
```text
180+
urn:tei:gtin:cyclonedx.org:443:0234567890123
181+
```
182+
183+
#### ASIN
184+
185+
Where the `unique-identifier` is a [ASIN](https://sell.amazon.com/blog/what-is-an-asin).
186+
187+
Syntax:
188+
189+
```text
190+
urn:tei:asin:<domain-name>:<domain-port>:<asin-identifier>
191+
````
192+
193+
Example:
194+
```text
195+
urn:tei:asin:cyclonedx.org:443:B07FZ8S74R
196+
```
159197

160-
Note that if an identifier, like EAN, is used for multiple different products then this
161-
EAN code will not be unique for a given product and should not be used as an identifier.
162-
In this case, the vendor is recommended to create a separate identifier for each unique
163-
product sold by other means, like UUID or hash.
198+
Note that if an identifier, like EAN, is used for multiple different product releases
199+
then this EAN code will not be unique for a given product. While this case is supported
200+
by TEA, the vendor is recommended to create a separate TEI for each unique product sold,
201+
like UUID or hash. In any case, the vendor SHOULD minimize the number of distinct product
202+
releases returned per TEI. Preferable situation is to have a single product release
203+
per TEI.
164204

165205
### TEI resolution using DNS
166206

0 commit comments

Comments
 (0)