- الرمز
NS-9- العنوان
- معرّفات UNI السياقية (عمليات النشر، والنُّسخ، ونُسخ البرامج)
- الإصدار
- 0.1.0
- الحالة
- مقترح
- التاريخ
- catalogue 2026-10-16 · circulated 17 October 2026
- Unique Nexus Identifier
NXS-STD-ST-000005- نطاق المسؤولية
- الثقة
- المصدر
standards/NS-9-contextual-uni.mdat2cbe0d41b5f8
مسودة عمل تمهيدية، متداولة للمراجعة وإبداء الملاحظات. غير مخصصة للتنفيذ. أعدّها وعمّمها سعيد ولدبيگي، كبير الرعاة في Nexus Standards (saeed@therisk.global)، 17 أكتوبر 2026. مجال المراجعة التقنية: TR-02. هذه الوثيقة ليست معيارًا من Nexus Standards؛ وقد تتغير دون إشعار، ولا يجوز تنفيذها أو الاعتماد عليها أو الاستشهاد بها بوصفها معيارًا من Nexus Standards. ولا يحدد مرحلتها إلا مجلس المعايير العالمي ولجانه التقنية وفق NS-13. ويُدعى المتلقون إلى تقديم تعليقاتهم مع أسبابها الداعمة، والإخطار بأي حقوق براءات اختراع يعلمون بها. انظر إشعار التعميم.
- الحالة
- مقترح
- المالك
- منظومة الثقة والضمان
A system, component, product or service exists once as a concept and many times in context: the early-warning system deployed for Kenya's water sector, the same system for a Sahel food-security programme, a data product published for an African region, a command room instance for one host city. NS-9 gives each context its own UNI, so that a page, a passport, a report, a policy, a clause or a monitoring record can name exactly which deployment it is about, while the concept keeps one UNI and the public name never changes with context and never infringes a mark.
استشهد
NS-9, clause 1. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-11. Grammar (unchanged)
لا يضيف NS-9 أي مقطع إلى قواعد NS-1. UNI السياقي هو معرّف عادي وفق NS-1 فئته فئة سياقية ويحمل مقطع REGION فيه الجغرافيا:
NXS-<SCOPE>-DP[-<REGION>]-<SERIAL> a deployment or instance of a system or component NXS-<SCOPE>-PR[-<REGION>]-<SERIAL> a programme or engagement instance (a pathway run in a context) NXS-EWS-DP-KEN-000001 deployment 1 of the early-warning system in Kenya NXS-EWS-DP-M011-000003 deployment 3 of the early-warning system in Western Africa (UN M49 011) NXS-GRX-DP-000002 a global deployment of the data system (no region) NXS-GCR-PR-COL-000001 GCRI programme instance 1 in ColombiaWith NS-1 grammar v0.2 a contextual UNI also carries the domain, sector and environment of the context as segments, so the identifier alone names the context: NXS-GRX-DP-WAT-WUT-CAN-PRD-000001 is production deployment 1 of the data system for Canadian water utilities, and its context name NXS-GRX-WAT-WUT-CAN-PRD (the identifier without CAT and SERIAL) is the name every page, article, dataset and dashboard about that deployment carries (NS-16). The context object below stays the record of truth: finer jurisdictions, several domains or sectors, the host and the validity window live there, and the segments in the identifier are the primary ones.
DP (deployment or instance) and PR (programme instance) are new artefact categories in registry/nexus-standards.yaml#categories (append-only, NS1-R3). Zenodo and DataCite mappings are other/Other: a deployment is catalogued, not deposited, unless its evidence is published separately.
استشهد
NS-9, clause 2. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-22. The context record
A contextual record is an NS-1 record (schema v1.1) with a context object:
| المجال | المعنى |
|---|---|
context.ofUni | The concept the context instantiates: the system, component, product or programme UNI (required). The record also carries relatedIdentifiers[IsPartOf, <ofUni>]. |
context.domains | Nexus domains from registry/domains.yaml (water, energy, food, health, biodiversity, climate and the others the ecosystem covers), one or more. |
context.sectors | Sectors from registry/sectors.yaml (one or more). |
context.jurisdictions | ISO 3166-1 alpha-2 country codes and, where relevant, subdivision codes (ISO 3166-2) or INTL for international. |
context.hostRef | المؤسسة أو المدينة المضيفة أو المستأجر أو البرنامج الذي يشغّل السياق (مرجع الكيان من السجلات القانونية للجهة المستهلكة). |
context.environment | production, staging, lab أو fixture; the environment never raises a supported claim level. |
context.validFrom / context.validUntil | When the context is live; a closed context keeps its record. |
context.conformsTo | The Nexus Standards and external standards (registry/external-standards.yaml ids) this context claims and evidences (NS-11, NS-14). |
REGION in the identifier is the primary geography (one country or one M49 region); finer or multiple jurisdictions go in context.jurisdictions. The identifier is allocated by the consumer's catalogue for the SCOPE (NS1-R2); the catalogue is append-only.
استشهد
NS-9, clause 3. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-33. Resolution and display
/uni/NXS-EWS-DP-KEN-000001resolves to the deployment's landing page: the concept it instantiates, its domains, sectors, jurisdictions, host, environment, conformance claims with evidence state, and the records (NS-3) it produces.- The display name is the concept's neutral public name plus a context phrase from the name architecture standard, for example "Early Warning · Kenya · Water". The context phrase is derived from the record, never hand-typed, and never composes a geographic term with a protected mark in a way the name architecture forbids (NS0-P10).
- Every page, passport, report and monitoring record about the deployment carries the contextual UNI (NS1-R5), and a
X-Nexus-UNIheader ornexus-unimeta tag names it.
استشهد
NS-9, clause 4. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-44. Policies, clauses and monitoring
A policy or clause (NS-10) binds to a contextual UNI, not to a name: "clause C applies to NXS-EWS-DP-KEN-000001". Verification and monitoring services (NS-11) observe a contextual UNI and record conformance per context. A command room or commons instance is itself a context (DP under the STU أو CMD scope) so that what it enforces is identifiable.
استشهد
NS-9, clause 5. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-55. القواعد
| القاعدة | النص |
|---|---|
NS9-R1 | سجل سياق واحد لكل عملية نشر أو نسخة برنامج؛ ويحتفظ المفهوم بمعرّف UNI; context.ofUni مطلوب ويجب أن يُحَلّ. |
NS9-R2 | Context identifiers are allocated by the catalogue for their SCOPE, never derived from names or typed by hand. |
NS9-R3 | A context's supported claim level, legal state and conformance evidence are its own; they are never inherited from the concept or from another context. |
NS9-R4 | إغلاق السياق لا يحذفه أبدًا؛ context.validUntil يتم تعيينه وتصبح الحالة WITHDRAWN أو SUPERSEDED مع supersededBy. |
NS9-R5 | تتبع أسماء العرض في السياق معيار بنية الأسماء؛ ومعرّف UNI، لا الاسم، هو المفتاح في كل مكان. |
استشهد
NS-9, clause 6. NXS-STD-ST-000005@0.1.0. https://nexustandards.com/standards/ns-9/#nx-c-66. Adoption
Domains and sectors registers (registry/domains.yaml, registry/sectors.yaml) are populated from the ecosystem coverage study (research/ECOSYSTEM_COVERAGE.md). First contexts to catalogue: the foundry's tenant deployments and command rooms, the Global Risks Forum (GRF) host cities and national hubs, the Global Centre for Risk and Innovation (GCRI Canada) programmes per country, the Global Risks Alliance (GRA) capital-readiness engagements. Each consumer records its contexts in its own catalogue under its scopes.
سجل التغييرات
Versions from the catalogue; entries from the changelog that name this document.
| الإصدار | التاريخ | ملاحظة |
|---|---|---|
0.1.0 | 16 أكتوبر 2026 | current version in the catalogue |
- 0.2.0 – 2026-10-16 دستور NS-0؛ وصيغت NS-2 وNS-4 وNS-5 وNS-9 وNS-10 وNS-11 وNS-12 وNS-13 وNS-14 (PROPOSED). الفئات DP وPR وCL وAT؛ ومخطط السجل v1.1 مع سياق NS-9؛ ومخططات البنود والسياسات والإقرارات والمقترحات.