AEON GP Document v1

Convention identifier: aeon.gp.document.v1

Status

Draft document metadata convention

Purpose

aeon.gp.document.v1 defines a standard vocabulary for document-level metadata.

This metadata describes:

• authorship
• origin
• lifecycle
• classification
• discoverability
• machine handling hints

The convention applies to metadata stored inside the AEON header.

Location

Document metadata lives inside:

Example:

Metadata Container

All document metadata is stored in a document object.

This keeps metadata separate from processing fields.

Metadata Fields

Identity

Fields:

Authorship

Fields:

Copyright and Rights

Fields:

Document Lifecycle

Fields:

Classification

Fields:

Namespace Metadata

The ns field declares a semantic namespace for document-level labels or document identity.

Namespaces qualify interpretation within a named semantic domain and reduce ambiguity between similar labels.

When namespace labels are needed on individual values, the same key may be used as binding metadata:

The ns label is descriptive only. It does not create a schema namespace, import mechanism, or lookup rule by itself.

Privacy and Handling

Example values:

The exact semantics may be defined by profiles.

Content Format

Examples:

• report
• message
• dataset
• contract
• log
• configuration

This field describes the conceptual type of document.

The format key may also be used as binding metadata when a document value carries a known representation pattern.

In this form, format labels the representation pattern. It does not require validation unless a schema, profile, processor, or another convention defines that validation.

Generation Metadata

Example values:

This can help downstream consumers evaluate provenance.

Robot Handling

Examples:

• index
• noindex
• noai
• noarchive

This mirrors common web document conventions.

Cache Hints

Examples:

• cache
• no-cache
• no-store

This field is advisory and intended for systems distributing AEON documents.

Reference Information

Examples:

• internal id
• document reference number
• archival identifier

Language Metadata

The language field identifies the natural language used in the document.

Use BCP-47 language tags.

Examples:

If multiple languages appear, list the primary language first.

Location Metadata

The location field indicates the geographic context of the document.

This may represent:

• where the document was created
• where the subject matter applies
• geographic relevance

Location should be structured rather than a free string.

Using ISO-style identifiers where possible improves interoperability.

Recommended standards:

If precise location matters:

Example Complete Header

Design Goals

The document convention aims to provide:

• human-readable metadata
• machine-readable classification
• interoperability across tools
• minimal structural complexity
• clear separation from domain data

It is intentionally flexible so that different domains can extend or interpret the fields according to their needs.

The document convention describes the document itself. It does not model the document's domain data.

Relationship to Other Conventions

This convention complements the AEON ecosystem:

Summary

aeon.gp.document.v1 provides a lightweight but structured vocabulary for describing AEON documents themselves, allowing tools and systems to understand authorship, classification, lifecycle, and handling policies without interfering with the document’s actual data structure.