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

# Naming Standards & Validation Rules

A **Classification** defines categories for labeling and organizing data based on sensitivity, usage, or governance requirements.

#### Validation Rules

<table><thead><tr><th width="235">Property</th><th>Value</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>Yes</td></tr><tr><td>Maximum Length</td><td>Not explicitly specified</td></tr><tr><td>Allowed Characters</td><td>Alphabets (A–Z, a–z), Numbers (0–9), Spaces, and all characters except disallowed ones</td></tr><tr><td>Disallowed Characters</td><td>Comma (,) and configured concatenation delimiter</td></tr><tr><td>Validation Notes</td><td>Validation applies only when a value is provided. If the value is null, the system skips validation.</td></tr></tbody></table>

#### Valid Examples

* Sensitive Data
* Public Classification
* Internal Use Only
* Confidential2024

#### Invalid Examples

* Data,Classification → Contains comma
* Class|Type → Contains configured delimiter

#### System Behavior

* Prevents saving the Classification if validation fails
* Displays a validation error message
* Skips validation when the value is null

#### Best Practices

* Use clear and meaningful classification levels
* Maintain consistent naming conventions across the organization
* Avoid commas and configured delimiters
* Use standardized governance terminology

***

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 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/governance-catalog/data-classifications/naming-standards-and-validation-rules.md?ask=<question>&goal=<user_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.