# Naming Standards & Validation Rules

## Data Product Domain

A **Data Product Domain** groups related data products by business or functional area. Data Product Domain names must follow standardized naming rules to maintain consistency and system compatibility.

#### Validation Rules

<table><thead><tr><th width="234.99993896484375">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**

* Sales Analytics
* Marketing Data
* Finance Insights
* CustomerDomain

**Invalid Examples**

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

#### System Behavior on Validation Failure

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

#### Best Practices

* Align names with business or functional areas.
* Use intuitive and meaningful names.
* Maintain consistency across domains.

## Data Product

A Data Product is a curated dataset designed for business consumption, analytics, and reporting.

#### Validation Rules

<table><thead><tr><th width="234.199951171875">Property</th><th>Value</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>No</td></tr><tr><td>Max 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: <code>! @ # $ % ^ &#x26; * _ + : ; &#x3C; > ? / \ " '</code></td></tr><tr><td>Start Character Restriction</td><td>Name must start with an alphabet or number</td></tr><tr><td>Regex / Notes</td><td>Disallows special characters and names starting with special characters. Rejects dot (.), comma (,), and configured concatenation delimiter.</td></tr></tbody></table>

#### Valid Examples

* Customer Insights 2024
* Revenue Dashboard
* Sales Report
* ProductAnalytics
* 2024 Revenue

#### Invalid Examples

* Product#1 → Contains special character
* Revenue,Data → Contains comma
* Data/Product → Contains restricted symbol
* Product\@Data → Contains special character
* .Product → Starts with disallowed character
* \#Data → Starts with special character

#### System Behavior on Validation Failure

* Prevents saving the Data Product.
* Displays a validation error message.
* Requires correction before saving.

#### Best Practices

* Use business-friendly and descriptive names.
* Avoid unnecessary abbreviations and special characters.
* Maintain consistent naming standards across Data Products.

***

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/release8.1/data-products/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.