AEON GP Document v1

Convention identifier: aeon.gp.document.v1

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:

aeon:header

Example:

aeon:header = {
  encoding = "utf-8"
  mode = "strict"
  convention = "aeon.gp.document.v1"
}

Metadata Container

All document metadata is stored in a document object.

aeon:header = {

  encoding = "utf-8"
  mode = "strict"

  document = {
    title = "Weather Report"
    author = "Alice"
  }

}

This keeps metadata separate from processing fields.

Metadata Fields

Identity

document = {
  title = "Weather Report"
  subject = "Daily rainfall observations"
  description = "Observation notes recorded during coastal storm"
}

Fields:

Authorship

document = {
  author = "Alice"
  contributors = ["Bob","Carol"]
}

Fields:

Copyright and Rights

document = {
  copyright = "© 2026 Alice Example"
  license = "CC-BY-4.0"
}

Fields:

Document Lifecycle

document = {
  created = 2026-03-08T18:00:00Z
  modified = 2026-03-08T18:45:00Z
}

Fields:

Classification

document = {
  labels = ["weather","storm","coastal"]
  tags = ["rainfall","field-notes"]
}

Fields:

Namespace Metadata

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

document = {
  ns = "aeon"
}

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:

type@{ns="aeon"} = "document"
status@{ns="workflow"} = "approved"
kind@{ns="media"} = "image"

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

Privacy and Handling

document = {
  privacy = "internal"
}

Example values:

The exact semantics may be defined by profiles.

Content Format

document = {
  format = "report"
}

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.

build@{format="semver"}:sep["."] = ^1.0.0
date@{format="ymd"}:sep["-"] = ^2026-03-07
location@{format="geo:lat,lon"}:sep[","] = ^"37.8136,144.9631"

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

document = {
  generation = "ai-assisted"
}

Example values:

This can help downstream consumers evaluate provenance.

Robot Handling

document = {
  robots = "noindex"
}

Examples:

• index

• noindex

• noai

• noarchive

This mirrors common web document conventions.

Cache Hints

document = {
  cache = "no-store"
}

Examples:

• cache

• no-cache

• no-store

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

Reference Information

document = {
  reference = "doc-2026-031"
}

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:

document = {
  language = "en-AU"
}

If multiple languages appear, list the primary language first.

document = {
  language = ["en","fr"]
}

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.

document = {
  location = {
    country = "AU"
    region = "Victoria"
    city = "Melbourne"
  }
}

Using ISO-style identifiers where possible improves interoperability.

Recommended standards:

If precise location matters:

document = {
  location = {
    country = "AU"
    city = "Melbourne"
    coordinates = {
      lat = -37.8136
      lon = 144.9631
    }
  }
}

Example Complete Header

aeon:header = {

  encoding = "utf-8"
  mode = "strict"
  convention = "aeon.gp.document.v1"

  document = {
    title = "Weather Report"
    subject = "Storm observation"
    description = "Field notes from coastal storm"

    author = "Alice"
    contributors = ["Bob"]

    ns = "aeon"

    language = "en-AU"

    location = {
      country = "AU"
      region = "Victoria"
      city = "Melbourne"
    }

    copyright = "© 2026 Alice"
    license = "CC-BY-4.0"

    created = "2026-03-08T18:00:00Z"
    modified = "2026-03-08T18:45:00Z"

    labels = ["weather","storm"]

    privacy = "internal"

    format = "report"

    generation = "ai-assisted"

    robots = "noindex"
    cache = "no-store"

    reference = "doc-2026-031"
  }

}

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.