Embedding taxonomy

TRADEMARK.md

@@ -0,0 +1,45 @@
+# Trademark Policy for User Context Protocol™ (UCP)
+
+This document describes the trademark policy for the "User Context Protocol" (UCP) project.
+
+"User Context Protocol" is a trademark of LiveRamp Holdings, Inc.
+
+---
+
+## Purpose
+
+LiveRamp supports the open development of the User Context Protocol and encourages its adoption across the advertising and marketing ecosystem.  
+To protect the integrity and trust of the UCP brand, we maintain control over its trademarks while allowing fair use in accurate references, compatibility statements, and community-driven implementations.
+
+This policy explains how the trademarks may be used in connection with the project, its specifications, and derived works.
+
+---
+
+## 1. Permitted Uses
+
+You **may** use the "User Context Protocol" or "UCP" name in the following ways without prior written permission:
+
+- **Accurate Reference:** To refer to the protocol itself, its open-source repository, or official specification (e.g., "This SDK implements the User Context Protocol").
+- **Compatibility Statements:** To describe interoperability, provided the statement is accurate and not misleading (e.g., "Compatible with UCP v1.0").
+- **Educational or Informational Contexts:** In blogs, articles, research papers, and presentations referring to the protocol.
+
+In all cases, the name must be used only as a reference to the standard or project — not to suggest ownership, endorsement, or sponsorship by LiveRamp.
+
+---
+
+## 2. Restricted Uses
+
+You **may not**:
+
+- Use "User Context Protocol," or confusingly similar names in the name of your company, product, or service (e.g., "UCP AI Suite" or "User Context Labs") without permission.
+- Use the trademarks in a way that implies official status, endorsement, or partnership with LiveRamp.
+- Alter, stylize, or combine the trademarks with your own branding in a way that could confuse users about the source of the project.
+- Use the trademarks to market modified versions of the protocol or specification as if they were the official standard.
+
+If you create a derivative or modified protocol, you must rename it to avoid confusion (e.g., "Extended Context Protocol (ECP) based on UCP").
+
+---
+
+## 3. Proper Attribution
+
+When referring to the project, please use the correct name and attribution line: