> For the complete documentation index, see [llms.txt](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/event-driven-architecture/event-governance-the-foundation-of-successful-event-driven-architecture/day-2-14-topic-naming-standard.md). # Day 2/14 Topic Naming Standard Day 2 of 14: A practical guide to designing a structured Topic Naming Standard based on your enterprise conceptual data model to ensure event consistency. **An event is a snapshot of data**. In the Event-Driven Architecture (EDA) paradigm, events are packaged as messages transmitted among systems via event mesh or data mesh. This means that an event is a reflection of data at a specific point in time. **The topic name serves as the event’s logical signature** with a one-to-one mapping. The Topic Naming standard provides guidelines to ensure the consistency and reliability of all events within the organization. It promotes interoperability between different systems and products, making events easier to replicate, process, reuse, and log. From a governance perspective, event topic name design must align with the naming standard. **A well-defined naming standard should be based on the organization’s conceptual data model**, which outlines high-level business concepts and objects (e.g., product, account, arrangement) from the organization’s core business process and operations perspective. A well-defined naming standard should include two parts: a **mandatory part** and an **optional part**. The mandatory part should include at least four fields: information domain, information subdomain, message type, and schema version. Larger organizations’ Topic Naming Standards may include more than four layers of Information domain. ## 🚀 Let's Connect Beyond GitBook! If you found this article helpful, you can find more of my technical insights, daily discussions, and deep dives across these platforms: * **Read more of my work:** Check out my articles on [dev.to](https://dev.to/stephen_tsoi_5b2c4055f3a9) and [Hashnode](https://stephentsoi.hashnode.dev/). * **Join the daily conversation:** Connect with me directly on [LinkedIn](https://www.linkedin.com/in/stephen-tsoi-16309730/). *** #### 📬 Stay Ahead of the Curve Enjoyed this piece? I break down complex technical topics into bite-sized, actionable insights every week. 👉 **Subscribe to my** [**LinkedIn Newsletter**](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7487299517642612736) to never miss an update and get the latest articles delivered straight to your feed! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/event-driven-architecture/event-governance-the-foundation-of-successful-event-driven-architecture/day-2-14-topic-naming-standard.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.