# Naming Standards & Validation Rules

## Term

A **Term** is a business definition used in the Business Glossary to provide business context for data assets.

<table><thead><tr><th width="235.00006103515625">Validation Rule</th><th>Details</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>No</td></tr><tr><td>Maximum Length</td><td>Not specified</td></tr><tr><td>Allowed Characters</td><td>Alphabets (A–Z, a–z), Numbers (0–9), Spaces</td></tr><tr><td>Disallowed Characters</td><td>Dot (.), Comma (,), configured concatenation delimiter, and special characters such as <code>! @ # $ % ^ &#x26; * _ + : ; &#x3C; > ? / \ " '</code></td></tr><tr><td>Start Character Restriction</td><td>Must start with an alphabet or number</td></tr><tr><td>Regex based Validation </td><td>Rejects names that contain special characters, start with special characters, or include dots, commas, or configured concatenation delimiters.</td></tr></tbody></table>

#### Examples

**Valid Examples**

* Customer Revenue
* AccountBalance
* Trade Volume 2024
* LoanAmount

**Invalid Examples**

* Customer.Revenue → Contains dot
* Revenue,Total → Contains comma
* Profit\@Margin → Contains special character
* \#Revenue → Starts with special character

#### System Behavior on Validation Failure

* Prevents saving the Term
* Displays a validation error message
* Requires correction before saving

#### Best Practices

* Use meaningful and business-friendly names
* Avoid special characters and unnecessary symbols
* Follow organizational naming standards
* Maintain consistent naming conventions across domains

## Business Glossary&#x20;

A **Business Glossary** is a structured collection of business terms organized under domains, categories, and subcategories. Business Glossary names must follow standardized naming rules to maintain consistency and system compatibility.

#### Validation Rules

<table><thead><tr><th width="233.39996337890625">Property</th><th>Value</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>No</td></tr><tr><td>Maximum Length</td><td>Not specified</td></tr><tr><td>Allowed Characters</td><td>Alphabets (A–Z, a–z), Numbers (0–9), Spaces</td></tr><tr><td>Start Character Rule</td><td>Name must start with an alphabet or number</td></tr><tr><td>Disallowed Characters</td><td>Dot (<code>.</code>), Comma (<code>,</code>), configured concatenation delimiter, and special characters such as <code>! @ # $ % ^ &#x26; * _ + : ; &#x3C; > ? / \ " '</code></td></tr><tr><td>Validation Notes</td><td>The system rejects names containing restricted special characters or names starting with special characters</td></tr></tbody></table>

#### Examples

**Valid Examples**

* Enterprise Glossary
* Finance Data 2024
* Customer Insights
* Data Governance

**Invalid Examples**

* `.Glossary` → Starts with a disallowed character
* `Customer@Glossary` → Contains restricted special character
* `Data,Governance` → Contains comma
* `#BusinessGlossary` → Starts with a special character

#### System Behavior on Validation Failure

* The system prevents saving the Business Glossary.
* Validation error messages are displayed.
* Correct the name before proceeding.

#### Best Practices

* Use meaningful and standardized business names.
* Avoid special characters and unnecessary symbols.
* Maintain naming consistency across domains.
* Validate naming standards before bulk operations or integrations.

## Subcategory

A Subcategory is a logical grouping under a Category that organizes related business terms within a domain. Subcategory names must follow standardized naming rules to maintain consistency and system compatibility.

#### Validation Rules

<table><thead><tr><th width="235">Property</th><th>Value</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>No</td></tr><tr><td>Maximum Length</td><td>Not specified</td></tr><tr><td>Allowed Characters</td><td>Alphabets (A–Z, a–z), Numbers (0–9), Spaces</td></tr><tr><td>Start Character Rule</td><td>Name must start with an alphabet or number</td></tr><tr><td>Disallowed Characters</td><td>Dot (<code>.</code>), Comma (<code>,</code>), configured concatenation delimiter, and special characters such as <code>! @ # $ % ^ &#x26; * _ + : ; &#x3C; > ? / \ " '</code></td></tr><tr><td>Validation Notes</td><td>The system rejects names containing restricted special characters or names starting with special characters</td></tr></tbody></table>

#### Examples

**Valid Examples**

* Customer Segments
* Retail Banking
* Sales Data 2024
* AccountDetails

**Invalid Examples**

* `.Segments` → Starts with a disallowed character
* `Customer@Group` → Contains restricted special character
* `Sales,Data` → Contains comma
* `#Retail` → Starts with a special character

#### System Behavior on Validation Failure

* The system prevents saving the Subcategory.
* Validation error messages are displayed.
* Correct the name before proceeding.

#### Best Practices

* Use clear and descriptive names.
* Avoid special characters and unnecessary symbols.
* Maintain consistency across the hierarchy.
* Follow organizational naming conventions.

## Category

A Category groups Subcategories and Terms within a Domain to organize related business concepts. Category names must follow standardized naming rules to maintain consistency and system compatibility.

#### Validation Rules

<table><thead><tr><th width="235">Property</th><th>Value</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>No</td></tr><tr><td>Maximum Length</td><td>Not specified</td></tr><tr><td>Allowed Characters</td><td>Alphabets (A–Z, a–z), Numbers (0–9), Spaces</td></tr><tr><td>Start Character Rule</td><td>Name must start with an alphabet or number</td></tr><tr><td>Disallowed Characters</td><td>Dot (<code>.</code>), Comma (<code>,</code>), configured concatenation delimiter, and special characters such as <code>! @ # $ % ^ &#x26; * _ + : ; &#x3C; > ? / \ " '</code></td></tr><tr><td>Validation Notes</td><td>The system rejects names containing restricted special characters or names starting with special characters</td></tr></tbody></table>

#### Examples

**Valid Examples**

* Financial Data
* Customer Management
* Sales Data 2024
* AccountDetails

**Invalid Examples**

* `Customer.Revenue` → Contains dot
* `Data,Category` → Contains comma
* `Profit@Margin` → Contains restricted special character
* `Sales#2024` → Contains restricted symbol
* `#Finance` → Starts with a special character
* `@Category` → Starts with a special character

#### System Behavior on Validation Failure

* The system prevents saving the Category.
* Validation error messages are displayed.
* Correct the name before proceeding.

#### Best Practices

* Use clear and descriptive names.
* Avoid special characters and unnecessary symbols.
* Maintain consistency across the hierarchy.
* Follow organizational naming conventions.

## Global Domain

A Global Domain represents the top-level grouping used to organize Categories and Subcategories in the Business Glossary. Global Domain names must follow standardized naming rules to maintain consistency and system compatibility.

#### Validation Rules

<table><thead><tr><th width="235.00006103515625">Property</th><th>Value</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>No</td></tr><tr><td>Maximum Length</td><td>Not specified</td></tr><tr><td>Allowed Characters</td><td>Alphabets (A–Z, a–z), Numbers (0–9), Spaces</td></tr><tr><td>Start Character Rule</td><td>Name must start with an alphabet or number</td></tr><tr><td>Disallowed Characters</td><td>Dot (<code>.</code>), Comma (<code>,</code>), configured concatenation delimiter, and special characters such as <code>! @ # $ % ^ &#x26; * _ + : ; &#x3C; > ? / \ " '</code></td></tr><tr><td>Validation Notes</td><td>The system rejects names containing restricted special characters or names starting with special characters</td></tr></tbody></table>

#### Examples

**Valid Examples**

* Enterprise Data
* Risk Management
* Finance Domain 2024
* CustomerInsights

**Invalid Examples**

* `Domain.Name` → Contains dot
* `Data,Domain` → Contains comma
* `Risk@Data` → Contains restricted special character
* `Sales#Domain` → Contains restricted symbol
* `#Domain` → Starts with a special character
* `@Global` → Starts with a special character

#### System Behavior on Validation Failure

* The system prevents saving the Global Domain.
* Validation error messages are displayed.
* Correct the name before proceeding.

#### Best Practices

* Use clear and descriptive names.
* Avoid special characters and unnecessary symbols.
* Maintain consistency across domains.
* Follow organizational naming conventions.
* Validate names before bulk uploads or integrations.

\ <br>

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions: 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:

```
GET https://docs.ovaledge.com/business-glossary/naming-standards-and-validation-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.