Add registry details

docs/project-updates/posts/the-registry.md

@@ -0,0 +1,39 @@
+---
+draft: false
+date: 2023-12-31
+authors: [hyattzer]
+categories:
+  - General
+description: A new page about a registry was added 
+---
+
+# The Registry
+
+After [Introducting the Disc ID Project](https://discid.org/project-updates/2023/11/30/introducing-the-disc-id-project/), it became clear that more explanation was needed about the benefits of having disc-related data on a NFC tag embedded in the disc. If the data only exists on the disc there are a few use cases, such as more detailed identification of runs of discs you like and an easier method for identifying the specific details of a poorly marked disc (manufacturer, mold, plastic, etc.), but these aren't the most interesting.
+
+The more powerful benefits only become available once the unique identifier on the disc gets connected to other information available online. And that is where the registry comes in. 
+
+<!-- more -->
+
+**The basic concept**
+
+In a nutshell, the Registry would have the same data as the NFC tags embedded in the discs have. Then using the unique identifier, each disc would be associated with an account that becomes the owner of the disc. Initially each disc would be owned by the account of the manfucturer who produced it, but then ownership can be changed to a retailer or player account when they purchase the disc.
+
+**Extending the data**
+
+Once a disc is in the system, additional information can be attached to a disc beyond just who the owner is. There are a ton of details that could be tracked, but one of the simpler things is the status of the disc. A couple statuses that might be of interest include:
+
+- **STOLEN** - the owner is claiming the disc has been stolen and they want it back
+- **LOST** - the owner lost the disc and they would like it back
+- **ENJOY** - the owner kept shanking the disc deep in the woods and decided to gift it to the world after spending too much time searching (or they intentionally left that misbehaving piece of plastic to curse someone else)
+
+Anyone who scans that disc could see the status and act accordingly, including retailers who might be considering buying used discs for resale and can see if they are marked as stolen, for example.
+
+**More to explore**
+
+By having a Disc ID standard and manufacturers embedding the tags into discs, the foundation is set for the above benefits and features to be explored. But that may only be the start of the interesting applications of a registry like this.
+
+!!! discussion "Have your own ideas?"
+    Share your thoughts and ideas on what is possible with a disc registry built on the Disc ID standard in the discussion thread: [What could be built if a disc registry existed?](https://github.com/orgs/Disc-ID/discussions/3)
+
+For some more context on the concept you check out the [Registry](../../registry.md) page.

docs/registry.md

@@ -0,0 +1,28 @@
+---
+title: Registry
+description: Overview of the disc registry concept enabled by Disc ID
+hide:
+  - navigation
+---
+
+# Registry
+
+One major benefit Disc ID can bring to the industry includes a registry for discs that have embedded tags. In order to work, the tags must have a unique identifier for each disc which is currently included in the Disc ID proposed standard.
+
+At a very high level, the registry would likely consist of:
+
+- Database containing data from the tags embedded in the discs
+- Platform for managing authenticated accounts for various entities with different capabilities/permissions
+- API for accessing and managing entries in the database based on authenticated account details
+- Web, mobile and/or desktop software for managing inventory
+
+With these elements in place, discs can be added to the registry and ownership of them gets attached to a registry account. Manufacturers would add discs and ownership would be transferred to retailers or players when they purchase them.
+
+Establishing a registry would take some effort, but once it is available the following benefits could be possible:
+
+- **Ink-free disc ownership** - contact information can be stored and retrieved via the registry, or handled partly or entirely server-side, so discs don't need to be marked for ownership
+- **Stronger disc authenticity** - validating the authenticity of discs, especially special and limited runs, becomes easier and more reliable for collectors
+- **Stolen discs** - discs in the registry can have a stolen status associated with them, so retailers won't buy used ones that have been stolen
+- **Lost and found** - disc status can also be used to mark discs as lost, potentially with information about where they were lost, to help aid in recovery
+
+Although building a registry is currently outside of the scope of this project, more details about the concept will be shared as progress on the Disc ID specification continues.

mkdocs.yml

@@ -52,6 +52,7 @@ nav:
       - Data Maps: specifications/data-maps.md
       - NDEF: specifications/ndef.md
   - Implementations: implementations.md
+  - Registry: registry.md
   - Guides & Reference: guides-reference.md
   - About: about.md
 extra: