인용
NS-16, clause 1. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-1
1. The pattern (NS16-R1 to NS16-R4)
Context name NXS-<SCOPE>[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>] NXS-GRX-WAT-CAN Artifact UNI NXS-<SCOPE>-<CAT>[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]-<SERIAL>[@<VERSION>] NXS-GRX-AR-WAT-CAN-000012@1.0.0 Context record NXS-<SCOPE>-DP|PR[-<DOMAIN>][-<SECTOR>][-<REGION>][-<ENV>]-<SERIAL> NXS-GRX-DP-WAT-CAN-000001
- NS16-R1 One name, many artefacts. Everything about one context carries the same context name and differs only in CAT and SERIAL: the article
NXS-GRX-AR-WAT-CAN-000012, the dataset NXS-GRX-DS-WAT-CAN-000004, 보고서 NXS-GRX-RP-WAT-CAN-000002, the dashboard figure NXS-GRX-FG-WAT-CAN-000009, the deployment NXS-GRX-DP-WAT-CAN-000001, the clause NXS-GOV-CL-WAT-CAN-000003 (a clause's scope is its issuer, its context segments its subject). - NS16-R2 The name is derived, the UNI is allocated. A context name is never minted and never typed with a serial; it is computed from a UNI by dropping CAT and SERIAL. Writing
NXS-GRX-WAT-CAN-000012 (no CAT) is an error, as is inventing a serial. - NS16-R3 Segments are codes, not words.
WAT, CAN, WUT, PRD come from the registries (domains.yaml, sectors.yaml, regions.yaml, nexus-standards.yaml#identifier.environments); a jurisdiction label a form already holds (ISO 3166-1 alpha-2, GLOBAL, a regional label) maps to a REGION only through registry/jurisdictions.yaml, never by guess. A new domain or sector is a proposal under NS-13 before any artefact uses it. Prose spells the meaning next to the code on first use: "NXS-GRX-WAT-CAN (the data system, water, Canada)". - NS16-R4 Most specific true context, nothing more. An artefact carries only the segments that are true of all of it. A Canada-wide water article is
…-WAT-CAN-…; a utilities-only article adds WUT; a global water method carries WAT alone; an artefact about two countries carries the M49 region that contains both or no REGION, with the countries in context.jurisdictions 또는 기록의 keywords. A segment is never added for search engine reasons.
인용
NS-16, clause 2. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-2
2. 논문 및 간행물(AR, PP, RP, TN, WP, BK, CP, PS, PO)(NS16-R5부터 NS16-R8까지)
| 지표 | Carries | 예시 |
|---|
| Front matter (Markdown, HTML head, DOCX core properties) | uni, contextName, version, publisherRef, license | uni: NXS-GRX-AR-WAT-CAN-000012, contextName: NXS-GRX-WAT-CAN |
| 표제부 | title; the UNI line under it in the document's identifier style; the context name as a chip | "Water observations for Canadian basins" · NXS-GRX-AR-WAT-CAN-000012@1.0.0 · 칩 NXS-GRX-WAT-CAN |
| Running header or footer | 버전이 포함된 UNI | NXS-GRX-AR-WAT-CAN-000012@1.0.0 · page 3 |
| Citation (NS-2) | UNI, version, publisher, date, resolver URL | … NXS-GRX-AR-WAT-CAN-000012@1.0.0. https://nexustandards.com/uni/NXS-GRX-AR-WAT-CAN-000012 |
| Data and figures inside | each cited by its own UNI and version in the caption or table note | Figure 2 NXS-GRX-FG-WAT-CAN-000009@1, data NXS-GRX-DS-WAT-CAN-000004@2 |
| WordPress | _nexus_uni meta, <meta name="nexus-uni">, data-nexus-uni on the article root, slug derived from the title (never from the UNI) | /water-observations-canadian-basins/ |
- NS16-R5 An article's UNI is minted when the draft is created, not when it is published; the record is DRAFT until publication and never changes identifier.
- NS16-R6 A new edition that changes claims is a new version (
@2.0.0) 이며, 번역본은 다음을 갖춘 버전입니다. language set; a new article is a new serial. - NS16-R7 Every number, figure, dataset and model the article relies on is cited by UNI and version; a claim without a citable record carries the NS-0 P6 wording ("not observed", "estimated", "declared").
- NS16-R8 The article never names the system by a brand word; it names it by display name (
NXS-GRX) and context name, with the meaning spelled on first use.
인용
NS-16, clause 3. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-3
3. 문서, 표준, 정책 및 조항 (DC, ST, PC, CL, TN, DL) (NS16-R9에서 NS16-R11까지)
- NS16-R9 First line of every Markdown document:
Nexus-UNI: <uni>; a context-specific document also carries the context name in its title block (NS-4). Standards themselves have no context segments (they are STD-scope and global). - NS16-R10 A policy or clause carries the issuer as SCOPE and the subject context as segments:
NXS-GOV-PC-WAT-CAN-000001 는 캐나다의 물 거버넌스 정책이며, 그 appliesTo 및 subjects 선택자는 동일한 영역과 관할권을 나열하며, 표준 검증기는 세그먼트와 선택자 간의 불일치를 거부합니다. - NS16-R11 A clause's attestations (
NXS-NSF-AT-…)는 자체 맥락 구간을 갖지 않습니다. 증명서 안의 대상 UNI 가 이를 담습니다.
인용
NS-16, clause 4. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-4
4. Code, schemas, migrations and models (SW, SV, SC, MG, WF, MD) (NS16-R12 to NS16-R15)
| 지표 | Carries | 예시 |
|---|
| 원본 파일 헤더, 1행 또는 2행 | // Nexus-UNI: <uni> (the module's own UNI, scope of the owning system, no context segments) | // Nexus-UNI: NXS-GRX-SW-000004 |
| Context-specific module (a Canada water adapter) | the module UNI with segments | // Nexus-UNI: NXS-GRX-SW-WAT-CAN-000001 |
| Package manifest | nexus.uni, nexus.contextName | "nexus": { "uni": "NXS-GRX-SW-000004" } |
| JSON Schema | $id carries the repository path; x-nexus-uni carries the UNI | "x-nexus-uni": "NXS-STD-SC-000002" |
| SQL 마이그레이션 | -- Nexus-UNI: <uni> 2번째 줄 | -- Nexus-UNI: NXS-GOV-MG-000001 |
| Model card, dataset sheet (NS-12) | uni, contextName, training-data UNIs | NXS-GRX-MD-WAT-CAN-000002 |
| Container image, SBOM, build attestation | the UNI as an OCI annotation org.nexus.uni and in the SBOM externalReferences | |
| Git | commit trailer Nexus-UNI: <uni> when a commit introduces or versions an artefact (optional, recommended) | |
- NS16-R12 A code module's UNI identifies the module, not its deployments; a deployment is an NS-9 context record (
DP) 그 context.ofUni is the module or system UNI, and the deployment's context name (NXS-GRX-WAT-WUT-CAN-PRD) is what operators, dashboards and incident records use. - NS16-R13 The header UNI is checked by the repository validator against the catalogue; a header naming a UNI the catalogue does not hold fails CI.
- NS16-R14 Configuration keyed by context uses the context name as the key (
contexts["NXS-GRX-WAT-CAN"]), 자유 서술형 라벨이 아니어야 구성, 기록, 페이지가 하나의 문자열로 연결됩니다. - NS16-R15 Identifiers in code are strings validated by the NS-1 library (
parseNxsId); code never builds a UNI by concatenation except through formatNxsId with a serial the fabric returned.
인용
NS-16, clause 5. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-5
5. 데이터와 기록 (DS, EV; NS-3 기록 유형) (NS16-R16에서 NS16-R18까지)
- NS16-R16 맥락에 관한 데이터셋은 맥락 세그먼트를 포함합니다:
NXS-GRX-DS-WAT-CAN-000004. NS-3 레코드는 고유한 문법을 유지합니다(NXS-GRX-OB-CAN-000042@3): record kinds carry REGION and may carry DOMAIN and SECTOR; the dataset lists its records' UNIs in the STAC, DCAT and PROV-O crosswalks (NS-3b). - NS16-R17 Every table or file that stores records has a
uni column or field holding the full UNI and, where it helps queries, a context_name column derived from it; the derivation is a function of the UNI, never a second source of truth. - NS16-R18 데이터로부터 렌더링된 지도 타일, 그림 또는 산출물에는 렌더링에 사용된 데이터의 UNI(NS-5)와 자체 UNI가 부여됩니다. 출처 이력 UNI가 없는 타일은 임시 고정물로 간주되며 그렇게 표시됩니다.
인용
NS-16, clause 6. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-6
6. APIs and services (SV) (NS16-R19 to NS16-R22)
| 지표 | Carries |
|---|
| Response header | X-Nexus-UNI: <uni of the primary record>; X-Nexus-Context: <context name> when the response is scoped to a context |
| Response body | uni 모든 기록에서; contextName on every list scoped to a context; never a derived score without the UNIs it came from |
| 요청 | 컨텍스트 필터는 컨텍스트 이름 또는 그 구성 요소를 사용합니다(?context=NXS-GRX-WAT-CAN 또는 ?domain=WAT®ion=CAN); 자유 서술형 라벨은 허용되지 않음 |
| 해석기 | GET /uni/<uni> landing page or JSON; GET /ctx/<contextName> every published record of the context, newest first, by CAT |
| OpenAPI | x-nexus-uni on the document and on every operation that serves a catalogued record |
| 오류 | RFC 9457 problem with uni 및 contextName 알려진 경우 입력한 코드(UNI_INVALID, UNI_NOT_IN_CATALOG, CONTEXT_UNKNOWN) |
- NS16-R19 A service's own UNI (SV) is in its health response; a service deployed for a context reports the deployment context record UNI (
DP)와 맥락 이름이 다음에 /ready. - NS16-R20 API는 호출자의 주소, 언어 또는 테넌트로부터 맥락을 도출하지 않습니다. 맥락은 요청 또는 레코드에 명시적으로 포함되어야 합니다.
- NS16-R21 특정 컨텍스트로 범위가 한정된 목록 엔드포인트는 해당 컨텍스트 이름과 정확히 일치하는 레코드를 반환하며, 다음의 경우에는
?include=narrower, of names that extend it (NXS-GRX-WAT-CAN 포함 NXS-GRX-WAT-WUT-CAN); never the reverse. - NS16-R22 Writes that create a catalogued artefact return
201 with the allocated UNI and the X-Nexus-UNI header; when the fabric is unavailable the response carries the typed uniAllocation state and the record stays DRAFT (NS-10/11 Commons adoption).
인용
NS-16, clause 7. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-7
7. Interfaces: pages, rooms, dashboards and passports (NS16-R23 to NS16-R27)
| 요소 | 규칙 |
|---|
| Page head | <meta name="nexus-uni">, <link rel="canonical"> to the resolver landing page, JSON-LD identifier |
| 이동 경로 | display name → context name chips in segment order → artefact: NXS-GRX › WAT › CAN › Article 000012 |
| Identifier line | the full UNI with version in monospace, copy action, link to /uni/<uni> |
| Context chip | NXS-GRX-WAT-CAN, one chip, links to /ctx/<contextName>; 마우스를 올리면 각 구간을 풀어서 보여 줍니다. |
| Room panel | every row shows its UNI (or its typed pending state) and its supported claim level; a context panel is titled by the context name |
| Passport (NS-15) | identity section: SU UNI first, then the contexts (DP, PR) the subject belongs to, each as a context chip |
| 필터 | 세그먼트별로 등록부 레이블(Domain: Water; Region: Canada)을 사용하며, 자유 서술은 사용하지 않습니다 |
| Empty state | "No record is catalogued for NXS-GRX-WAT-CAN" with the typed reason, never a blank |
- NS16-R23 UI는 맥락에 대해 점수, 배지, 순위 또는 "실시간" 상태를 표시하지 않으며, 기록과 해당 UNI, 기록된 상태만 표시합니다(NS-0 P6).
- NS16-R24 A context chip is where a context is named; free-text labels ("Canada water programme") are titles, never identifiers, and never appear without the chip.
- NS16-R25 Tokens, type and both themes follow the UI kit; the identifier line uses the kit's monospace token; the chip uses the identifier style, never a brand colour.
- NS16-R26 Every exported figure, CSV, PDF or image from a dashboard carries the UNIs of what it shows in its metadata and footer.
- NS16-R27 Search indexes the UNI, the context name and each segment with its registry label, so that "Canada water" and
NXS-GRX-WAT-CAN find the same records.
인용
NS-16, clause 8. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-8
8. Worked example: the data system's water work in Canada
| Thing | UNI | Context name | Where it shows |
|---|
| The data system | NXS-GRX-SV-000001 (서비스) | NXS-GRX | system pages, health |
| Canadian water utilities production deployment | NXS-GRX-DP-WAT-WUT-CAN-PRD-000001 | NXS-GRX-WAT-WUT-CAN-PRD | 운영실, /ready, incident records |
| 캐나다 수자원 관측 데이터셋 | NXS-GRX-DS-WAT-CAN-000004@2 | NXS-GRX-WAT-CAN | STAC, DCAT, 데이터셋 페이지 |
| One observation record | NXS-GRX-OB-CAN-000042@3 | NXS-GRX-CAN | record API, evidence lists |
| 물 리스크 방법 카드 | NXS-GRX-MD-WAT-000002 | NXS-GRX-WAT | method registry |
| 조 | NXS-GRX-AR-WAT-CAN-000012@1.0.0 | NXS-GRX-WAT-CAN | nexustandards.com, citation, Zenodo deposit |
| Figure in the article | NXS-GRX-FG-WAT-CAN-000009@1 | NXS-GRX-WAT-CAN | caption, export footer |
| 캐나다 상수도 운영자를 위한 정책 | NXS-GOV-PC-WAT-WUT-CAN-000001 | NXS-GOV-WAT-WUT-CAN | Commons, 룸 패널 |
| Clause: observation coverage | NXS-GOV-CL-WAT-CAN-000003 | NXS-GOV-WAT-CAN | Commons, evaluation |
| Attestation of the clause on the deployment | NXS-NSF-AT-000017 | none (subject carries the context) | passport policy section, room panel |
Reading any row: the display name tells which system, the chip tells where and about what, the UNI tells which artefact and version, the resolver tells what is recorded about it.
인용
NS-16, clause 9. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-9
9. Conformance (NS-14)
| 단계 | 요구 사항 |
|---|
| NS-16 Basic | R1, R2, R3, R9, R12, R13, R15, R19, R22, R23 |
| NS-16 Standard | 기본 항목에 R4부터 R8, R10, R14, R16, R17, R20, R21, R24, R27을 추가 |
| NS-16 Full | 모든 규칙 |
A consumer declares its level in registry/consumers.yaml; VERIFIED needs NS-11 attestations by a mandated evaluator (the repository validator and the API contract validator are the evaluators of R9, R13, R19 and R22).
인용
NS-16, clause 10. NXS-STD-ST-000015@0.1.0. https://nexustandards.com/standards/ns-16/#nx-c-10
10. 미결 사항
- NS16-O1 whether record kinds (NS-3) may carry DOMAIN and SECTOR in production allocations, or REGION only (fabric key change in nexus-foundry SQL 2033).
- NS16-O2 the
/ctx/ resolver's treatment of restricted records (count only, or omit). - NS16-O3 subdivision jurisdictions (ISO 3166-2,
CA-ON)를 다섯 번째 구간으로 할지 기록 전용으로 할지 정합니다. 결정될 때까지는 기록 전용입니다. - NS16-O4 (resolved 2026-10-16) how jurisdiction labels already held by forms reach the REGION segment: through
registry/jurisdictions.yaml (alpha-2, GLOBAL 및 지역 라벨을 alpha-3 또는 M49로 변환하며, EU는 의도적으로 제외), 소비자가 벤더링하고 드리프트 테스트를 수행합니다.
변경 이력
Versions from the catalogue; entries from the changelog that name this document.
| 버전 | Date | 비고 |
|---|
0.1.0 | 2026년 10월 16일 | current version in the catalogue |
변경 이력에는 NS-16을 명시한 항목이 없습니다.