Skip to content
StandardsDigital, telecom and platformsStandards that apply
Digital, telecom and platforms

Digital, telecom and platforms: standards that apply

The 4 standards listed for digital, telecom and platforms in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.

Digital, telecom and platforms
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-0, NS-9, NS-11, NS-12.
  • Open standards: ITU-T X.1303bis Common alerting protocol (CAP 1.2); Common Alerting Protocol 1.2; 3GPP TS 23.041 Technical realisation of Cell Broadcast Service (public warning); NIST Cybersecurity Framework 2.0; NIS2 Directive (EU) 2022/2555; NIST SP 800-207 Zero Trust Architecture.
  • Data and feeds: ITU DataHub ICT indicators; World Development Indicators; WMO Alert Hub and Register of Alerting Authorities.
  • Couples with: Energy utilities and grids; Media and information; Finance, insurance and capital markets; Defence and civil protection.
Nexus Standards
4
NS-0, NS-9, NS-11
Open standards
6
named, never copied
Data and feeds
3
listed for reference
Couplings
4
with other areas
01NS-0

બંધારણ અને સિદ્ધાંતો

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000004.

નિયમText
NS0-P1Open · The standards, their registries, schemas, catalogues and reference tools are published in the canonical repository under the licences recorded in LICENSING.md. Participation in development is open to every community and stakeholder under GOVERNANCE.md. No standard depends on a proprietary artefact, product, account or mark to be applied.
NS0-P2Machine-readable first · Every normative element exists as data (registry, schema, clause) before it exists as prose; prose explains, data governs. A standard with no machine form is not a Nexus Standard.
NS0-P3Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone.
NS0-P4Verified, not asserted · Conformance is a claim with evidence: receipts, digests, signed attestations and observations (NS-11). A claim without evidence is recorded as a claim, never as a fact, and the supported claim level of the implementation bounds every statement it makes.
NS0-P5Zero trust · Authenticated is not authorised; entitled is not authorised; access is denied by default. Every verification, monitoring and enforcement path assumes no implicit trust between systems, tenants, sites or agents, and records who verified what under which mandate.
NS0-P6Real-time · Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so that an implementation can state exactly which version it conforms to at any instant.
NS0-P7Provenance everywhere · Every artefact records what it was derived from, who produced it, under which release and policy decision, and what corrected it (NS-3b, PROV-O profile). Corrections supersede; nothing is silently rewritten.
NS0-P8Honest · A UNI identifies and resolves; it never certifies. legalState defaults to review-required. Readiness, approval and production status are never implied by a standard, a status, a page, a score or a badge.
NS0-P9Nexus-aware · Standards address cross-domain interdependence (water, energy, food, health, biodiversity, climate and the sectors they touch) explicitly: an obligation can reference artefacts in another domain, and cascades are first-class.
NS0-P10Names are governed · Codes are never names. Public names follow the marks policy (governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md, section 7). A system or component is shown by its neutral display name and its UNI; the UNI may change with context (NS-9), and no name infringes anyone’s mark.
NS0-P11Community-owned development · Proposals, comments, decisions and versions of every standard are themselves artefacts with UNIs. The development process is specified (NS-13) and open, and authority to adopt is recorded, never assumed.
NS0-P12Fail closed · Missing evidence, a missing legal state, a missing policy decision or unavailable verification results in a refusal with a typed reason, never in a pass.

Read NS-0 in full

02NS-9

સંદર્ભિત UNI (તૈનાતીઓ, ઉદાહરણો, કાર્યક્રમ ઉદાહરણો)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.

નિયમText
NS9-R1Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve.
NS9-R2Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand.
NS9-R3The supported claim level, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context.
NS9-R4Closing a context shall not delete it: context.validUntil is set and the status becomes WITHDRAWN or SUPERSEDED સાથે supersededBy.
NS9-R5Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere.

Read NS-9 in full

03NS-11

ચકાસણી અને દેખરેખ (પુરાવા, પ્રમાણપત્રો, zero-trust અનુરૂપતા અવલોકન)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.

નિયમText
NS11-R1A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.
NS11-R2Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary.
NS11-R3Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).
NS11-R4Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs.
NS11-R5Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts.
NS11-R6Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth.

Read NS-11 in full

04NS-12

સૉફ્ટવેર, મોડેલ અને AI/ML કલાકૃતિઓ (પુરવઠા સાંકળ, મોડેલ કાર્ડ, ડેટાસેટ શીટ)

Status proposed · software, models and capability lifecycle; trust, authorisation and assurance · NXS-STD-ST-000012.

નિયમText
NS12-R1Each software release shall carry a bill of materials, a build attestation and signatures as evidence of the UNI version.
NS12-R2Each model shall carry a model card and each dataset a dataset sheet; both shall cite their sources by UNI.
NS12-R3Agents shall act under recorded mandates and shall be credited as agents; they shall not adopt or certify.
NS12-R4AI governance obligations shall be clauses bound to contextual UNIs and evaluated, not prose assurances.

Read NS-12 in full

05પ્રશ્નો

પ્રશ્નો અને જવાબો.

Are these all the rules for digital, telecom and platforms?
They are the rules stated by the listed standards. The principles of NS-0 bind every standard; clauses specific to the area, where needed, are written under NS-10 and evaluated under NS-11.
What does a rule identifier such as NS1-R5 denote?
The number of the standard and the number of the rule within it. Rule identifiers are stable so that clauses, attestations and publications can cite them.
ધોરણો

Shape the standards for digital, telecom and platforms.

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. બાહ્ય ધોરણો તેમનાં પોતાનાં લાઇસન્સ હેઠળ નામ, ક્રમાંક અને લિંક દ્વારા ટાંકવામાં આવે છે. તૃતીય-પક્ષ ડેટા, લાઇબ્રેરીઓ અને ફૉન્ટ તેમનાં પોતાનાં લાઇસન્સ જાળવે છે: તૃતીય-પક્ષ સૂચનાઓ જુઓ.