Naming, marks and intellectual property: standards that apply
The 2 standards listed for naming, marks and intellectual property in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.
- Nexus Standards: NS-0, NS-1, NS-9.
- Open standards: Open Definition 2.1; The Open Source Definition; SPDX License List; REUSE Specification; Creative Commons Attribution 4.0 International.
- Data and feeds: SPDX License List JSON; Wikidata Query Service.
- Couples with: Identification (the UNI); Data and datasets; Open standards development.
- Nexus Standards
- 3
- NS-0, NS-1, NS-9
- Open standards
- 5
- named, never copied
- Data and feeds
- 2
- listed for reference
- Couplings
- 3
- with other areas
| قاعدہ | Text |
|---|---|
NS0-P1 | Open · 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-P2 | Machine-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-P3 | Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone. |
NS0-P4 | Verified, 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-P5 | Zero 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-P6 | Real-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-P7 | Provenance 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-P8 | Honest · 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-P9 | Nexus-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-P10 | Names 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-P11 | Community-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-P12 | Fail 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. |
سیاقی UNIs (تعیناتیاں، مثالیں، پروگرام کی مثالیں)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| قاعدہ | Text |
|---|---|
NS9-R1 | Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve. |
NS9-R2 | Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand. |
NS9-R3 | The 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-R4 | Closing a context shall not delete it: context.validUntil is set and the status becomes WITHDRAWN or SUPERSEDED کے ساتھ supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
سوالات و جوابات۔
Are these all the rules for naming, marks and intellectual property?
What does a rule identifier such as NS1-R5 denote?
Around naming, marks and intellectual property.
Shape the standards for naming, marks and intellectual property.
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۔ بیرونی معیارات کا حوالہ ان کے نام، نمبر اور لنک کے ساتھ ان کے اپنے لائسنسوں کے تحت دیا جاتا ہے۔ فریقِ ثالث کا ڈیٹا، لائبریریاں اور فونٹس اپنے اپنے لائسنس رکھتے ہیں: فریقِ ثالث کے نوٹس دیکھیں۔