> 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/data-catalog/naming-standards-and-validation-rules.md).

# Naming Standards & Validation Rules

Data Catalog Objects represent technical metadata assets used for data discovery, governance, lineage, and analytics. These objects include Databases, Tables, Table Columns, Files, File Columns, Reports, Report Columns, APIs, API Attributes, and Codes.

### Validation Rules

| Property              | Value                                                                       |
| --------------------- | --------------------------------------------------------------------------- |
| Blank Allowed         | Yes (null allowed)                                                          |
| Maximum Length        | Not explicitly specified                                                    |
| Allowed Characters    | Alphabets, Numbers, Spaces, and any characters except disallowed characters |
| Disallowed Characters | Comma (,) and configured concatenation delimiter                            |
| Pattern Validation    | No strict regex validation enforced                                         |
| Null Value Behavior   | Validation is skipped when the value is null                                |

#### Examples

**Valid Examples**

* Customer Database
* Sales Table 2024
* Employee Report
* API Response Data
* File Column Name
* PII Code

**Invalid Examples**

* Data,Object → Contains comma
* Table|Column → Contains configured delimiter
* Code,Value → Contains comma

#### System Behavior on Validation Failure

* The system prevents saving the object when validation fails.
* Validation error messages are displayed.
* Correct the object name before proceeding.
* If the value is null, validation is skipped.

#### Best Practices

* Use meaningful and descriptive object names.
* Maintain consistent naming conventions across objects.
* Avoid commas and configured delimiters.
* Follow organizational metadata naming standards.
* Use standardized names for better search and governance visibility.

***

Copyright © 2026, 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 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://docs.ovaledge.com/data-catalog/naming-standards-and-validation-rules.md?ask=<question>&goal=<endgoal>
```

`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.