Validation is not issuance
A valid syntax and checksum only show that an identifier is well formed. They do not prove that GSEIN issued it, that it belongs to an entity, or that an entity is active.
GSEIN 1.0 · PUBLIC DRAFT
A standard others can test independently
The GSEIN 1.0 draft defines one canonical identifier syntax and a portable conformance corpus for implementations in any language.
- Published version
- 1.0.0-draft
- Checksum-valid example
- GSEIN-8293-1049-5820-75
Canonical syntax
Four fixed groups, one check pair.
A GSEIN contains a 12-digit allocation body followed by two ISO/IEC 7064 MOD 97-10 check digits. The allocation body carries no country, industry, or entity-type meaning.
GSEIN-8293-1049-5820-75
ISO/IEC 7064 MOD 97-10
Conformance profiles
One corpus, two portable checks.
Checksum profile
Compute the two check digits from each 12-digit payload and verify every valid payload vector.
Parser profile
Normalize accepted representations to their canonical form and reject malformed inputs with the specified reason.
Implementation resources
Download the normative test data.
The JSON corpus and its JSON Schema are public, versioned artifacts. Public copies are tested byte-for-byte against the canonical repository sources.
GSEIN 1.0 vectors
Valid payloads, accepted representations, and required rejection cases.
gsein-v1-vectors.json
Corpus JSON Schema
Machine-readable structure and constraints for validating the vector file.
gsein-v1-vectors.schema.json
Draft material remains open to review. Changes to normative behavior require a new version and updated conformance vectors.