Meta is a record about the document, not about the content concerning the world. Except for the document structure records (DOC, BODY, END), all of them go in the HEAD of the document. Besides Meta, the HEAD also holds the document-wide evidence Edge SOURCE and its QUALIFIER.

Layout

TAG WORD          000K KKKC CCCC LLLL      Sections 14 and 15 (0x1C0L~0x1FFL)
[Length extension TAG]
Payload           Raw value, or an embedded Value or Reference record
  • Meta has no Issuer form. Meta is a common specification that all Issuers follow, and only GEUL defines it.
  • LLLL is the total WORD count including the TAG WORD, minus 1. A Codec not in the table is Reserved.

Payload forms

FormWhenExamples
Raw valueWhen the form is fixed to one. It does not rely on other record CodecsDOC-* length, SPEC-VERSION, ISSUER-KEY
Embedded ValueWhen choosing among several forms. The Value TAG tells the formPROFILE, EFFECTIVE-*, times, content hash
Embedded ReferenceWhen pointing at a target such as a person, organization, tool, or documentDOC-ID, AUTHOR, CO-AUTHOR, RECORDED-BY, SIGNED-OFF, the signer of SIGNATURE
NoneA 1 WORD markerBODY, END
  • An embedded record is not an independent record and belongs to its Meta. Each finds its boundary by its own Length, and the position after reading the last record must coincide exactly with the end of the Meta.
  • Whether a Meta may appear only once or several times in a document is set by the “Count” of each Codec document.

Classes

Meta numbers run on from 0x1C0L without Reserved gaps. The bits of the number do not indicate the class. The class is known from the range table below.

ClassDirect codesWhat it covers
structure0x1C0L~0x1C4LDocument boundary and length
declaration0x1C5L~0x1CALInterpretation declarations
provenance0x1CBL~0x1D0LWho, when, where
lineage0x1D1L~0x1DDLWhat it came from and how
policy0x1DEL~0x1E3LHow it is handled
IMPORT0x1E4LImports an external document
verification0x1E5L~0x1E9LWhether it can be trusted
Reserved (verification only)0x1EAL~0x1FFL
  • The verification class is the records in Section 15 with C >= 5, that is, w >= 0x1E50. With this, the verification class is known without a codebook and is removed from the content hash.
  • The trailing Reserved range 0x1EAL~0x1FFL is verification only. A new Meta outside verification cannot be placed before verification, and if placed in the trailing Reserved range it is excluded from the content hash.
  • The structure, declaration, and IMPORT classes are not read from bits. The decoder knows them from a built-in number table.
  • Meta required for interpretation: structure, declaration, IMPORT. If removed, the records cannot be read or the interpretation changes. Every decoder must handle them. These Codecs belong to the GEUL core codebook.
  • Meta that does not change interpretation: provenance, lineage, verification, policy. If removed, the content of the statements stays the same. Only the material for trust judgment and handling disappears.
  • Evidence is written not as Meta but with the evidence Edge SOURCE and QUALIFIER. Evidence for an individual record goes in the BODY, and the origin of the whole document goes in the HEAD as a SOURCE with Target 0 (document).

Structure

The Meta structure class (Codec 0x1C0L~0x1C4L) sets the boundary and length of the document. The unit of GEUL data is one document.

DOC-*                  ← HEAD starts
  declaration, provenance, lineage, verification, policy, IMPORT Meta
  document-wide SOURCE and its QUALIFIER
BODY                   ← BODY starts
  Reference, Value, Edge
END                    ← closes the document
  • Every document is opened by DOC-1WORD/2WORD/4WORD, which specifies the total length. A decoder can skip the whole document at once with this length.
  • BODY and END are 1 WORD records with no Payload. END is required.
  • Documents do not nest. Other documents are pointed at with IMPORT.
  • If the HEAD (Meta, the document-wide SOURCE and its QUALIFIER) is empty, BODY is omitted. BODY may appear only once per document.

The whole document structure is in document.

CodecNameMeaning
0x1C0L~0x1C2LDOC-1WORD / 2WORD / 4WORDOpens the document, specifying the total length
0x1C3LBODYEnds the HEAD and opens the BODY
0x1C4LENDCloses the document

Detailed rules are in document.

Declaration

The Meta declaration class (Codec 0x1C5L~0x1CAL) is interpretation declarations. A declaration changes the interpretation rules, so every decoder must handle it. The scope of a declaration is that document.

  • SPEC-VERSION determines how the remaining records are read, so it holds a plain integer with no embedded Value. GEUL v1 is 0x0001 (record 1C51 0001).
  • DOC-ID is a DOC-POINTER (Issuer, document ID, version 0) pointing at the document itself. A codec document uses CODEC-POINTER (Issuer, codec ID, version 0). If absent, the document is unnamed and can be pointed at only by its content hash.
  • There is no document name address. A human-readable title is attached with a statement LABEL (publication addresses and version lists).
CodecNameMeaning
0x1C5LSPEC-VERSIONThe specification edition followed. A single integer
0x1C6LPROFILEThe applied profile
0x1C7LDOC-IDThe identifier of this document. A DOC-POINTER (version 0) pointing at itself. A codec document uses CODEC-POINTER (version 0)
0x1C8LEFFECTIVE-FROMThe effective date of this version. If absent, the publication time
0x1C9LEFFECTIVE-UNTILThe end of the validity period of this version (time-limited law). If absent, until the next version takes effect
0x1CALDEFAULT-LANGUAGEThe default language

Provenance

The Meta provenance class (Codec 0x1CBL~0x1D0L) records who created and recorded the document, and when.

  • The author, the recorder, and their times follow git’s author and committer model (AUTHOR and CREATED-AT, RECORDED-BY and RECORDED-AT).
  • Removing provenance does not change the content of the statements. Only the material for trust judgment disappears.
  • Source material is not in this class. The origin of the whole document is written in the HEAD, and the origin of an individual record in the BODY, with the evidence Edge SOURCE. The corresponding range in the source text, the acquisition time, and the source-text hash are QUALIFIERs attached to that SOURCE (page P304 and section P958, retrieval date P813, checksum P4092).
  • If properties attached to a source (source-text range, acquisition time) were kept as Meta, it could not be decided which source they belong to when there are several sources. So they are written as QUALIFIERs that take the SOURCE as Target.
CodecNameMeaning
0x1CBLAUTHORThe author (Reference)
0x1CCLCO-AUTHORThe co-author
0x1CDLCREATED-ATCreation time
0x1CELMODIFIED-ATModification time
0x1CFLRECORDED-BYThe recorder
0x1D0LRECORDED-ATRecording time
  • Source material is written not as Meta but as the evidence Edge SOURCE in the HEAD (Target 0), and the source-text range, acquisition time, and source-text hash are written as QUALIFIERs attached to that SOURCE.

Lineage

The Meta lineage class (Codec 0x1D1L~0x1DDL) records what the document came from and how. Lineage follows git’s commit model, and the unit corresponding to a commit is the document.

  • The content hash points at one complete copy of the document content (git commit id). It is the SHA-256 from the opening record (DOC-*) up to just before END, and records of the verification class (C >= 5 in Section 15, w >= 0x1E50) are excluded from the computation.
  • The version ID is a 2 WORD integer numbered from 1 in publication order within a named document. 0 means no version is written.
  • Lineage Meta points at versions by content hash. The PARENT inside a document also enters the hash, so the content hash becomes a hash chain linking the whole history.
  • History is not erased. A correction is issued as a new version. A pointer that changes, like a branch, is not placed in the document.
  • DELTA-BASE and DELTA-REMOVE are a format that stores a version as a diff against a base version. A version is always defined as a snapshot.

Revision rules are in document.

Lineage follows git’s commit model. The unit corresponding to a commit is the document.

CodecNameMeaning
0x1D1LPARENTThe content hash of the immediately preceding version. If several, a merge
0x1D2LDERIVED-FROMDerived from material of another lineage
0x1D3LGENERATED-BYThe generating agent (person, model, rule engine)
0x1D4LTRANSFORMED-BYThe conversion tool and its source version (commit digest)
0x1D5LCHERRY-PICKED-FROMThe original version of an imported change
0x1D6LREVERTSThe version that was reverted
0x1D7LREPLACESThe version that was rewritten. The original version is not deleted
0x1D8LSQUASHED-FROMThe original versions merged into one
0x1D9LMESSAGEThe reason for a change. One per language
0x1DALTAGAn immutable name given to a version
0x1DBLDELTA-BASEThis file is a diff against a base version
0x1DCLDELTA-REMOVEThe list of LOCAL IDs to remove in the diff
0x1DDLNEXT-LOCAL-IDThe LOCAL ID to assign next. Placed in the version-list document
  • History is not erased. A correction is issued as a new version.
  • A pointer that changes, like a branch, is not placed in the document. The repository and the index manage it.

Verification

The Meta verification class (Codec 0x1E5L~0x1E9L) records the material for judging whether the document can be trusted: the public key of a self-issued Issuer, signatures, confirmation of the right to contribute, confidence, and the verdict on the whole document.

  • The verification class is excluded from the content hash computation. So putting a signature inside the document, or adding several signatures, does not change the content hash (the same approach as git gpgsig).
  • The verification class is the records in Section 15 with C >= 5, that is, w >= 0x1E50, so the hash can be computed without a codebook. The trailing Reserved range 0x1EAL~0x1FFL is also verification only and is excluded from the hash.
  • Node-level and record-level verdicts are carried by the TOULMIN Edge VERDICT (0x118L).
CodecNameMeaning
0x1E5LISSUER-KEYThe signature algorithm and public key of a self-issued Issuer
0x1E6LSIGNATUREA signature over the content hash. Algorithm, signer, signature
0x1E7LSIGNED-OFFConfirmation of the right to contribute
0x1E8LCONFIDENCEConfidence
0x1E9LVERDICTThe verdict on the whole document (Pass, Review, Fail)
  • The verification class is excluded from the content hash computation. So putting a signature inside the document, or adding several signatures, does not change the content hash.

Policy

The Meta policy class (Codec 0x1DEL~0x1E3L) sets how the document is handled: license, scope of disclosure, privacy level, retention period, consent, and usage restrictions.

  • A policy does not change interpretation; it sets how to handle the document.
  • The original license of a work inside a byte sequence is recorded with LICENSE.
CodecNameMeaning
0x1DELLICENSELicense
0x1DFLACCESSScope of disclosure
0x1E0LPRIVACYPrivacy level
0x1E1LRETENTIONRetention period
0x1E2LCONSENTScope and basis of consent
0x1E3LUSAGEUsage restrictions
  • A policy does not change interpretation; it sets how to handle the document.

IMPORT

The Meta IMPORT class (Codec 0x1E4L) imports an external document under an IMPORT ID. The only Codec is IMPORT-DOC (0x1E4L).

  • IMPORT imports only documents. Targets inside the imported document are pointed at by the BODY Reference EXTERNAL-POINTER-* (IMPORT ID, LOCAL ID) (Reference).
  • If a version ID is given, it binds to that edition; if 0, to the latest edition at interpretation time. Published documents state the version.
  • The HEAD of the imported document is not imported. Reference and Value records are copied, not imported.
TAG WORD          0001 1110 0100 LLLL      IMPORT-DOC (0x1E4L)
[Length extension TAG]
Document          DOC-POINTER record (Issuer, document ID, version ID). A codec document uses CODEC-POINTER
IMPORT ID         The rest. An integer of the shortest width
  • Only IMPORT-DOC (0x1E4L) is used. IMPORT imports only documents. Targets inside the imported document are pointed at by EXTERNAL-POINTER-* (IMPORT ID, LOCAL ID) in the BODY.
  • If a version ID is given, it binds to that edition; if 0, to the latest edition at interpretation time. Published documents state the version.
  • The same IMPORT ID is not assigned twice in one document.
  • The HEAD of the imported document is not imported. Targets of that document are interpreted as that document declares.

Example: import the latest version of document 0x0000000000000002 of Issuer 0x00000002 as IMPORT ID 1.

1E4A 0418 0000 0002 0000 0000 0000 0002 0000 0000 0001