> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/business-glossary/about-business-glossary.md). # About Business Glossary A business glossary is a collection of data terms described in clear and understandable language to everyone within an organization. It ensures consistency in communication by eliminating ambiguity in business terminology. Glossary terms can be linked to data objects, enabling experienced analysts to examine data assets contextually. Additionally, these terms can be used to classify data objects and enforce data security policies. Business Glossary Terms can be associated with cataloged data objects that include: * Schema * Tables * Table Columns * Files * File Columns * Report * Report Columns * Codes * API * API Attributes When business glossary terms are linked with Cataloged data objects, the term provides additional context and meaning to the data objects. Business terms serve a dual purpose of defining data objects and applying security policies to the data. This includes restricting access, masking sensitive information, and organizing data objects by classification (e.g., confidentiality or sensitivity). Additionally, governance roles can be established to ensure the quality of data objects. *** Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ovaledge.com/release8.3/business-glossary/about-business-glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.