Summary

  • RFC 9676 separates a continuing legal work from its version-and-language expression and its publisher-and-format manifestation; a bare work name does not select all three.
  • A resolver may normalize an incomplete citation, match it heuristically and default to the best most recent expression. That is a retrieval policy, not proof of the text in force for a particular actor and date.
  • Defensible automation must retain the requested name, catalogue state, match rule, expression, manifestation, exact bytes, authenticity evidence, legal-status source and final decision as separate receipts.

The audit retrieved the wrong kind of right answer

A compliance team reopens a two-year-old decision. Its archive contains a persistent urn:lex name, not a dead web address. The resolver accepts the name and returns a polished official-looking document in the user’s language. The dashboard turns green: reference resolved.

The document may be exactly what the resolver should return today and still be the wrong evidence for the audit. The work may have been amended after the decision. The preferred-language expression may not have governed the original proceeding. The PDF may be a later consolidation rather than the manifestation actually consulted. A partition request may have fallen back to the whole instrument. None of those possibilities makes the persistent name defective. They show why persistence and temporal precision are different properties.

RFC 9676 is designed to keep a source of law identifiable across locations, publishers, versions and formats. It succeeds by refusing to make a location the identity. But a system that compresses name, version, file and legal effect into one “resolved” status throws away the architecture’s most useful distinction.

An identifier for a class, not one immutable file

The general form begins with urn:lex, a jurisdiction element and a local name. Within the local name, RFC 9676 defines a compact hierarchy:

local-name = work ["@" expression] ["$" manifestation]

The work is the continuing intellectual creation. For a source of law, it includes the original and amended forms over time. Its elements can name the issuing or proposing authority, the type of measure, identifying details and an annex. A work-level name can intentionally stand for the wider family: original text, annexes, later versions, official languages and published formats.

That is the first limit on inference. A bare work URN can be a perfectly valid stable citation while being insufficient for a time-bound decision. It answers “which source?” before it answers “which realization of that source?” Persistence is achieved partly by allowing the work identity to survive changes that would make a URL or file hash obsolete.

The expression narrows the work to a version and, where needed, a language. RFC 9676 describes versions in terms of the period during which the text is considered in force or effective. A new expression can follow an amendment, correction of a publication error, or the start or end of a period in which a particular partition has effect. Each official-language realization can receive its own expression identifier.

The manifestation narrows again. It records the publisher or editorial source, format, optional component and feature. XML and PDF manifestations may embody the same expression. An anonymized judgment and a fuller publication may differ as manifestations. If a publisher’s domain changes, an already assigned manifestation name remains unchanged even when the old object is no longer reachable; a new manifestation is needed for the new publisher identity.

One persistent legal work can therefore have many time-bound expressions, and one expression can have many manifestations. “The URN resolved” does not tell an auditor which layer the request actually specified.

The registrar controls names, not every proposition about law

RFC 9676 gives the jurisdictional registrar a substantive coordination role. An adopting country or organization identifies a registrar, establishes its jurisdiction structure, registers a jurisdiction code, defines the primary local-name elements, publishes normalization rules, prevents collisions and maintains authoritative registries for naming components. Issuing authorities assign names within their domains and supply the formal parameters needed for uniqueness.

This is not a decorative function. Poor normalization or duplicate assignment would destroy the namespace’s value. Accurate point-in-time representations of government bodies matter because institutions change names, merge, split and move within administrative hierarchies. Persistence depends on institutions accepting long-lived responsibility.

But scheme authority is scoped. Defining the identifier for a statute is not the same act as enacting it. Maintaining an authority-name catalogue is not adjudicating whether a measure applied to a dispute. Marking a jurisdiction code obsolete is not repealing every law named beneath it. A registrar can authoritatively answer how a LEX name is built without becoming the universal source for every legal consequence associated with the document.

That boundary matters in product design. A field labelled “verified by registrar” can reasonably mean that the name conforms to the jurisdiction’s construction rules and exists in its catalogue. It should not silently expand to “currently binding”, “authentic text”, “applicable to this company” or “approved by a court”. Each of those needs a different source of authority.

Resolution includes judgement calls

The RFC’s resolution architecture is distributed. DNS information helps route a request toward the competent resolution service, whose knowledge base contains catalogue entries or transformation rules. The resolver then maps the persistent name to one or more online locations.

Legal citations rarely arrive as perfect machine identifiers. They are abbreviated, mistyped, translated, copied from prose or extracted by software. RFC 9676 is realistic about that condition. It recommends normalization, exact catalogue search and then an iterative or heuristic approach to incomplete references. Context that a human supplies effortlessly may be missing from the string.

The resolver can also process a partition identifier. If it can retrieve the requested provision, it should do so; otherwise it may return the entire document. When the request supplies no more specific expression, the RFC recommends selecting the best, most recent version and providing available manifestations and items.

Those behaviours improve usefulness, but they make a binary success flag inadequate. A result can come from an exact match or a partial heuristic. “Best” can depend on catalogue state. “Most recent” can mean a text adopted, published, commenced or consolidated on different dates. A partition-specific request can become a whole-document result. Multiple manifestations can be available, with different publishers, formats and editorial features.

The resolver should therefore emit a reconstruction record: original input, normalized form, exact or heuristic match, rejected candidates, catalogue version, selected work and expression, language, manifestation, partition handling, destination, redirects and retrieval time. Otherwise the application cannot later explain why the green result was green.

Current is not the same as correct for the event date

The most dangerous shortcut is temporal. A bare work name resolved today can reasonably lead to the current consolidated expression. An investigation into a transaction from two years ago needs a different question: which expression had the relevant legal effect then, and what text did the decision-maker actually rely on?

A later amendment may not apply retroactively. A correction can alter a publication without changing the underlying policy. Different partitions can commence on different dates. A language version can have its own official status. An annulment or judicial decision may alter effect without changing the identifier family. Catalogue ingestion can lag the legally operative event.

No generic resolver can infer all of that from persistence alone. The request must carry an as-of date or explicit expression where the use case is temporal. The result must cite the competent legal-status source and its freshness. If the system cannot obtain that evidence, “status unknown” is more honest than silently treating the latest file as the governing text.

Historical reproducibility adds a second requirement. It is not enough to resolve the same work name later. The system should preserve the expression, manifestation, exact bytes, hash, provenance and catalogue snapshot used for the original decision. Otherwise an audit can prove that a stable citation survived while failing to prove what the original process actually read.

Authenticity sits outside the LEX specification

RFC 9676 makes a particularly important disclosure in its Security Considerations: document authenticity is not supplied by the LEX specification. It belongs to other security and trust mechanisms, such as digital signatures and encryption.

That does not make LEX insecure. It prevents the naming layer from claiming evidence it does not produce. A syntactically valid URN proves syntax. A catalogue entry proves what that catalogue records. DNS routing proves how the query was directed. HTTPS protects a transport connection to a named endpoint under its trust model. A hash preserves byte identity relative to another trusted hash. A digital signature supports claims defined by the key, signature scope, verification policy and time.

None of those alone proves that a parliament enacted the text, that an official gazette promulgated it, that a court treated it as controlling, or that it applied to the actor and date in question. Conversely, an authentic signed file can still be the wrong historical expression. Authenticity and temporal applicability are separate receipts.

A mature evidence chain should preserve at least ten states: syntax, assignment, resolution, retrieval, authenticity, expression, manifestation, legal status, operational decision and observed outcome. The temptation is to jump from the third state to the eighth. That jump is where a discovery tool becomes an unacknowledged legal oracle.

Persistence depends on institutions and succession

URN rhetoric can make persistence sound mathematical. RFC 9676 is more grounded: identifier persistence depends on the durability of the institutions that assign and administer names. Jurisdiction codes are designed not to be renamed; they can become obsolete rather than disappear. Responsibility is delegated among CNR, jurisdictional registrars and issuing authorities.

Institutional durability is therefore part of the operating model. Catalogues need stewardship, export and succession. Resolver delegation needs monitoring. Government reorganizations must not cause old authority names to be rewritten out of history. Publisher-domain changes should create new manifestations rather than silently replace provenance. Obsolete jurisdiction entries must remain resolvable for archives.

The continuity plan should assume that any one resolver, catalogue operator or publisher can fail. A persistent name with no portable catalogue, no mirrored rules and no preserved manifestations becomes a durable label attached to an unavailable memory. The namespace is strongest when institutions can change without destroying the evidence that earlier institutions maintained.

An evidence record fit for automation

For a new decision, store the literal input and whether it named a work, expression or manifestation. Record the registrar and construction rules under which the name was assigned. Capture resolver identity, catalogue revision, normalization, match method and alternatives. Then record selected version, language, publisher, format, component, feature, URL, retrieved bytes, hash and timestamp.

Add authenticity evidence separately. Add the legal-status source separately, including the jurisdiction, relevant time, commencement or amendment basis and any uncertainty. Finally record the rule and human or machine actor that used the evidence, the action taken, and the observed consequence.

This may look expensive beside a single URL field. It is cheaper than discovering later that every audit retrieves the latest text and calls it history. The storage burden is small compared with the cost of a deadline, denial, payment, filing or enforcement action made under the wrong expression.

The standard remains narrow enough to be useful

RFC 9676 is an Informational Independent Submission, not an IETF Standards Track specification and not IETF consensus. Its publication does not prove that any jurisdiction has adopted it. Adoption becomes visible when registrars publish rules, issuing authorities assign names, catalogues expose state, resolvers answer queries and applications rely on the results.

That restraint matches the better Internet tradition described by Heng Lu’s minimum-specification and running-code principles. A common identifier format can coordinate independent institutions without pretending to replace their legal systems. A published document is a coordination artifact; implemented assignment and resolution are operational facts. Even implementation proves use of the naming system, not the correctness of every proposition made about the named law.

The test is simple. Keep the LEX receipt as strong as it is. If the string names a work, say work. If the resolver chose the latest expression, say that. If the file came from a particular publisher, preserve the manifestation. If authenticity or legal effect was established elsewhere, cite that separate evidence. A persistent name then becomes what it should be: a durable join key across records, not a verdict disguised as a citation.

Sources