Skip to content
StandardsVisualisation, figures and mapsRecords and schemas
Visualisation, figures and maps

Visualisation, figures and maps: records and schemas

How the artefacts of visualisation, figures and maps are identified, described and resolved: the scope, the record, the categories, the schemas and the catalogue entries of the applicable standards, each keyed by a UNI (Unique Nexus Identifier).

Visualisation, figures and maps
What this area is built from, with the data and feeds its records read marked.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-1, NS-5, NS-11.
  • Open standards: Web Content Accessibility Guidelines (WCAG) 2.2; C2PA Technical Specification; OGC API – Features (map data source); Schema.org ImageObject.
  • Data and feeds: Natural Earth vector data; NASA GIBS WMTS imagery layers; Our World in Data grapher and catalogue.
  • Couples with: Geospatial and Earth observation; Accessibility and inclusion; Verified intelligence and transparency.
01عمل

The process.

Record explorer · schema, example, crosswalkNexus Standards registry

Artefact record (NS-1) · 32 fields · 12 required

  • uni required stringThe UNI (Unique Nexus Identifier), NS-1 grammar, without @version.
  • displayAlias stringPublic Registry short form (NX-R-47092) shown next to the UNI during the transition.
  • registryState enumPublic registry state; corrections keep the UNI and add a version.
  • legacyUni stringDotted UNI v0 this record replaces, for crosswalk (for example data.eo.stac.catalogue).
  • title required string
  • description string
  • scope required string
  • category required string
  • region string
  • domain stringDOMAIN segment code from the domains register (NS-1 v0.2); present when the identifier carries it.
  • sector stringSECTOR segment code from the sectors register (NS-1 v0.2).
  • environment enumENV segment code (NS-1 v0.2).
  • contextName stringNS-16 context name: the identifier without CAT and SERIAL; derived, never allocated.
  • systemId stringFunctional system class id (systemId) from the Nexus Standards register#scopes when scope is a SYSTEM.
  • status required enum
  • currentVersion string
  • versions array
    • version string
    • date string
    • gitSha string
    • digest string
    • note string
  • creators required array
    • name string
    • type enum
    • affiliation string
    • orcid string
    • ror string
  • publisherRef required stringEntity reference of the publishing institution (registry/governance.yaml#bodies); the institution stays publisher of record for institutional artefacts.
  • publicationDate required string
  • language string
  • keywords array
  • rights required object
    • license stringSPDX licence identifier or expression, or a LicenseRef- string for a licence that has no SPDX identifier.
    • rightsHolderRef string
    • accessRight enum
    • embargoDate string
  • legalState required enum
  • claimCeiling required enum
  • locations required array
    • kind enum
    • value string
    • digest string
  • relatedIdentifiers array
    • relation enum
    • identifier string
    • identifierType enum
  • supersededBy string
  • workPackageId string
  • directiveRefs arrayReferences to the recorded decisions or policies under which the artefact was produced.
  • notes string
  • context objectNS-9: this record is a deployment, instance or programme instance of the concept ofUni, in a context.
    • ofUni string
    • domains arrayids from the domains register
    • sectors arrayids from the sectors register
    • jurisdictions array
    • hostRef string
    • environment enum
    • validFrom string
    • validUntil string
    • conformsTo arrayNexus Standard ids and the external standards register ids this context claims; evidence per NS-11

Example record · NXS-STD-ST-000001

{ "uni": "NXS-STD-ST-000001", "title": "Nexus Standards NS-1 - the UNI and artifact catalog", "scope": "STD", "category": "ST", "status": "DRAFT", "currentVersion": "0.1.0", "creators": [ { "name": "Global Centre for Risk and Innovation (GCRI)", "type": "Organizational" } ], "publisherRef": "GCRI", "publicationDate": "2026-10-15", "rights": { "license": "CC-BY-4.0", "accessRight": "open" }, "legalState": "LEGAL_REVIEW_REQUIRED", "claimCeiling": "INTEGRATED", "locations": [ { "kind": "repoPath", "value": "standards/NS-1-identifier-and-artifact-catalog.md" }, { "kind": "repoPath", "value": "registry/nexus-standards.yaml" } ], "workPackageId": "LEGAL-NAME-ARCHITECTURE-001" }
Field crosswalk: Schema.org JSON-LD, DataCite, Zenodo, CodeMeta
Record fieldSchema.orgDataCiteZenodoCodeMetaماخذ
uniidentifier (PropertyValue, propertyID urn:nexus:uni)alternateIdentifier (alternateIdentifierType NXS)metadata.related_identifiers[] (scheme other)identifierمسودہ
titlenametitles[].titlemetadata.titlenameمسودہ
descriptiondescriptiondescriptions[].description (Abstract)metadata.descriptiondescriptionمسودہ
scope·subjects[] (subjectScheme nexus-scope)metadata.keywords[]·مسودہ
categoryadditionalTypetypes.resourceTypeGeneralmetadata.upload_type / publication_type / image_typeapplicationCategoryregistry
regionspatialCoveragegeoLocations[].geoLocationPlacemetadata.locations[]·مسودہ
statuscreativeWorkStatus··developmentStatusمسودہ
currentVersionversionversionmetadata.versionversionمسودہ
versions·relatedIdentifiers (IsNewVersionOf, IsPreviousVersionOf)versions (concept DOI)·مسودہ
creatorscreator / authorcreators[]metadata.creators[]authorمسودہ
publisherRefناشرناشرmetadata.publisher (Zenodo)ناشرمسودہ
publicationDatedatePublishedpublicationYear; dates[] (Issued)metadata.publication_datedatePublishedمسودہ
languageinLanguagelanguagemetadata.language·مسودہ
keywordskeywordssubjects[]metadata.keywords[]keywordsمسودہ
rights.licenselicenserightsList[].rightsIdentifier (SPDX)metadata.licenselicenseمسودہ
rights.accessRightconditionsOfAccess·metadata.access_right·مسودہ
legalState····مسودہ
claimCeiling····مسودہ
locationsurl / contentUrl / codeRepositoryalternateIdentifiers[] (URL)files[] / metadata.related_identifiers[]codeRepository / downloadUrlمسودہ
relatedIdentifiersisPartOf / citation / isBasedOnrelatedIdentifiers[] (relationType)metadata.related_identifiers[]isPartOf / referencePublicationمسودہ
supersededBy·relatedIdentifiers[] (IsObsoletedBy)metadata.related_identifiers[] (isObsoletedBy)·مسودہ
workPackageId····مسودہ
directiveRefs·relatedIdentifiers[] (References)metadata.related_identifiers[] (references)·مسودہ
context····مسودہ

Rows marked registry are taken from the category mappings to Zenodo and DataCite in the registry; rows marked draft are an editorial mapping to the public schemas and are not part of the registry.

Record explorerthe artefact record schema with example records from the standards catalogue (scope STD). A record describes an artefact and its provenance.

Nexus Standards
3
NS-1, NS-5, NS-11
Open standards
4
named, never copied
Data and feeds
3
listed for reference
Couplings
3
with other areas
02Identifier

Identifiers under scope STU

STU is the system scope Visual composition and workflows. An artefact of this area is identified as NXS-STU-<CAT>-<SERIAL>, with an optional region segment for regional artefacts; serials are allocated only by the catalogue.

UNI anatomy · parse, resolve, citeNexus Standards registry
prefixNXSfixedscope<SCOPE>32 codescat<CAT>38 artefact, 9 record codesregion<REGION>ISO 3166-1 or M49serial<SERIAL>six digits, allocatedversion@<VERSION>semver or record version

Illustrative identifier pattern. With script enabled, a UNI can be entered and each segment is checked against the registry, resolved to its record where one is published, and expressed as a URN, a resolver link and a citation.

UNI anatomyThe NS-1 grammar segment by segment, with the scope and category codes of the registry. Resolution links to the resolver; no identifier is allocated on this page.

The form above is a pattern; codes classify artefacts and are not product names.

03The record

Content of a catalogue record

Field setاقدار
Required fieldsuni, title, scope, category, status, creators, publisherRef, publicationDate, rights, legalState, claimCeiling, locations
StatusesDRAFT, PUBLISHED, SUPERSEDED, WITHDRAWN
Rights statesLEGAL_REVIEW_REQUIRED, APPROVED, RESTRICTED, PROHIBITED
Assurance levelsFIXTURE_VERIFIED, IMPLEMENTATION_COMPLETE, INTEGRATED, LAB_OBSERVED
04Embedding

Embedding of the UNI in the artefact

SurfaceHow
sourceFileheader comment: Nexus-UNI: <uni>
markdownfront matter uni: or first line Nexus-UNI: <uni>
datasetmetadata sidecar <file>.uni.json with the record, or a uni key in STAC or DataCite metadata
figurecaption suffix [<uni>] and image metadata
httpApiresponse header X-Nexus-UNI: <uni>
htmlPage<meta name="nexus-uni" content="<uni>"> and data-nexus-uni on the component root
cmscontent metadata field _nexus_uni (validated), rendered as the nexus-uni meta tag and the X-Nexus-UNI header
panelevery projected record carries uni in the panel’s provenance and links it to the resolver
05Record kinds

Record kinds and artefact categories

Artefacts use categories mapped to Zenodo and DataCite resource types; records of the data fabric use record kinds (NS-3). The two lists share no code.

کوڈRecord kind (NS-3)
OBObservation fact
SRSource release
INIndicator definition
MEMeasure definition
BDBoundary version
CTChronotope version
CRCorrection record
APAnalytical product record
SUSubject (place, asset, organisation)
06اسکیمے

Machine-readable schemas

  • nexus-artifact-record.v1.json
  • nexus-attestation.v1.json
  • nexus-clause.v1.json
  • nexus-policy.v1.json
  • nexus-proposal.v1.json
  • nexus-subject-passport.v1.json
07فہرست

Catalogue entries of the applicable standards

Records in the standards scope, with their status and rights state.

UNITitleCategoryحیثیتRights state
NXS-STD-ST-000011Nexus Standards NS-5 – figures, maps and visualisationSTمسودہunder review
08سوالات

سوالات و جوابات۔

Who allocates UNIs for visualisation, figures and maps artefacts?
The catalogue responsible for scope STU, through the reference command-line tool. Serials are not entered by hand (NS1-R2).
What does the resolver return?
An HTML landing page for browsers or JSON for machines, for published records that are not restricted (NS-7).
معیارات

Shape the standards for visualisation, figures and maps.

Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.

حیثیت اور استعمال۔ Nexus Standards مجوزہ معیارات ہیں جو NS-13 کے تحت ایک کھلے عمل کے ذریعے تیار کیے گئے اور رضاکارانہ استعمال کے لیے شائع کیے گئے ہیں؛ یہ سند، اعتماد نامہ یا ضابطہ جاتی منظوری نہیں، اور انہیں اختیار کرنا عالمی معیارات کونسل کا اور ہر ملک میں اس کی قومی معیارات کونسل کا فیصلہ ہے۔ ایک UNI (Unique Nexus Identifier) کسی دستاویز کی شناخت کرتا ہے؛ اس کی تصدیق نہیں کرتا۔ معیار ساز اداروں اور ان کے معیارات کے نام ان کے نگرانوں کی ملکیت ہیں اور صرف دستاویزات کی شناخت کے لیے استعمال کیے گئے ہیں؛ یہاں کسی بیرونی معیار کا متن نقل نہیں کیا گیا۔ Nexus Standards یہاں مذکور کسی معیار ساز ادارے سے وابستہ، اس کا تائید یافتہ یا اس سے سند یافتہ نہیں۔

لائسنس: معیارات کے متن، رجسٹریوں، اسکیموں اور ڈیٹا کے لیے CC BY 4.0؛ حوالہ جاتی کوڈ کے لیے Apache-2.0۔ بیرونی معیارات کا حوالہ ان کے نام، نمبر اور لنک کے ساتھ ان کے اپنے لائسنسوں کے تحت دیا جاتا ہے۔ فریقِ ثالث کا ڈیٹا، لائبریریاں اور فونٹس اپنے اپنے لائسنس رکھتے ہیں: فریقِ ثالث کے نوٹس دیکھیں۔