Nexus Standards · Legal

Trademark and Name Use Policy · version 1.0, effective 20 October 2026

Trademark and Name Use Policy

The standards are openly licensed; their names are not. Anyone may refer to a Nexus Standard by name, identifier and version, and state accurately what an implementation does. A name composed into a product or company name, or any graphic mark, needs written permission. No use may imply certification, accreditation, endorsement or official status.

01Overview

Summary

Name useLegal
  1. Referential usefree
  2. Names in products, companies or domainswritten permission
  3. Graphic marks, seals, badgeswritten permission
  4. Statements implying approval or endorsementnot permitted
  5. Version1.0
  6. Effective date20 October 2026
  7. Last updated20 October 2026
  8. Contactcontact@therisk.global

GCRI Canada · Secretariat of the Nexus Standards

02Section 1

Purpose

  • 1.1 The names of the Nexus Standards identify the standards and the open process that produces them. They are protected to prevent confusion about the origin and status of a document, a product or a claim, not to restrict use of the standards, which are openly licensed.
  • 1.2 This Policy sets out the uses of the names that are free, the uses that require written permission and the uses that are not permitted.
03Section 2

Names covered

NameUseStatus
Nexus StandardsThe standards programme and its publicationsUsed as a name of the programme; no registration is claimed
NXSThe scope prefix of the programme and its identifier notationUsed as a name of the programme; no registration is claimed
Names of the programme sites, councils, committees and working groupsThe bodies and programme areas of the Nexus StandardsUsed as names of the programme
Identifiers of the standards (for example NS-0) and UNI (Unique Nexus Identifier) codesCatalogue codes that identify documents and artifactsIdentifiers, like DOI prefixes or ISBNs; free to use as notation

GCRI Canada administers these names as Secretariat on behalf of the programme. The word Nexus on its own is in common use, and no exclusive right in it is claimed. The registered-trademark symbol is not used with any of these names.

04Section 3

Uses that need no permission

  • 3.1 Referring to a Nexus Standard by its name, identifier, version and link, in any medium, including in academic, journalistic, policy and commercial writing.
  • 3.2 Stating that a product, dataset or method implements clauses of, or is derived from, a named Nexus Standard, with its identifier and version, provided the statement is accurate and the supporting evidence is published.
  • 3.3 Using identifiers and UNI codes as notation, and quoting or adapting the text of a standard under CC BY 4.0 with attribution.
  • 3.4 A National Standards Council naming its national profile, edition or derivative standard with its own name and crediting the Nexus Standard from which it is derived.
  • 3.5 Stating accurately that a person or organisation participates in a working group, committee or council, in the capacity recorded.
05Section 4

Uses that require written permission

  • 4.1 Composing Nexus Standards, NXS or the name of a programme body into the name of a product, service, company, event, publication series, domain name, repository or social-media account.
  • 4.2 Any graphic mark, emblem, seal or badge that refers to the Nexus Standards, or that could suggest conformance, approval or membership.
  • 4.3 Using a Nexus name for a national derivative standard, which the Secretariat permits on request unless a clear risk of confusion exists.
06Section 5

Uses that are not permitted

  • 5.1 Stating or implying that a Nexus body has certified, accredited, approved or endorsed a product, organisation, person or national decision; no Nexus body certifies or accredits.
  • 5.2 Describing a Nexus Standard as an official, governmental or intergovernmental standard, or implying government or intergovernmental endorsement that is not recorded.
  • 5.3 Describing an implementation as conforming to a Nexus Standard without published evidence, or describing a derivative that departs from a normative requirement as conforming rather than derived.
  • 5.4 Using a Nexus name in a way that is false, misleading or likely to cause confusion about the source or status of a document, product or service, or that disparages the programme or its participants.
07Section 6

Wording of conformance statements

SituationAccepted wording
An implementation with published test evidenceImplements clauses derived from NS-n version X, with the number of clauses passed, the test suite version and the date
A national adoption without changeAdopted in the country as NS-n version X
A national adoption with a profileAdopted in the country with a national application profile, identified by its UNI
A national derivative standardNational standard derived from NS-n version X
08Section 7

Names of other bodies

  • 7.1 The Nexus Standards name other standards bodies and their standards only to identify them and their documents. No emblem or mark of any other body is shown, and no mark of another body forms part of a Nexus name.
  • 7.2 Organisations that support the programme are acknowledged in a separate acknowledgement and are never presented as issuers, authors or approvers of a standard.
09Section 8

Requesting permission

  • 8.1 Requests are sent to the Secretariat at contact@therisk.global, describing the proposed use, the name concerned, the product or activity and the territories. The Secretariat acknowledges a request within fourteen days.
  • 8.2 Permission is given in writing, free of charge, for a defined use, and may be withdrawn if the use changes or causes confusion. Permission granted to an organisation ends when its participation in the programme ends, unless the permission states otherwise.
10Section 9

Reporting misuse and enforcement

  • 9.1 Suspected misuse may be reported to contact@therisk.global. The Secretariat first asks the user to correct the use, and allows a reasonable period to do so.
  • 9.2 Where misuse continues, GCRI Canada may require that the use cease and may take the steps the law permits. Rights in the names are reserved.
  • 9.3 This Policy may be amended; the amended Policy is published on this page with a new effective date.
11Questions

Questions and answers.

May a company say that its software implements a Nexus Standard?
Yes, if the statement is accurate, names the standard with its identifier and version, and is supported by published test evidence. It may not say or imply that the software is certified, approved or endorsed.
NRNexus Reports gateway · GW-STD

Contribute to Nexus Reports from this page.

Nexus Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

Nexus Standards
Nexus Standards

Permission and questions

Requests for permission and questions about the names of the Nexus Standards may be sent to the Secretariat, GCRI Canada, at contact@therisk.global, subject: Trademark.

Status and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artifact; it does not certify it. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.

Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.