Repository navigation
docs(domain): cite both TS 119 612 versions - #407
Open
LKSNDRTMLKV wants to merge 1 commit into
Open
LKSNDRTMLKV wants to merge 1 commit into
LKSNDRTMLKV wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #385.
trusted_listcited ETSI TS 119 612 V2.3.1, and V2.4.1 had since been published. This re-reads the clauses the module relies on against both versions, and corrects what the re-read found.The two versions
Compared word for word, the two versions differ only in wording, cross-references and the schema attachment. None of it is in a clause this module reads: the service type URIs (clause 5.5.1), the status values (clause 5.5.4 and Annex D.5), the status history (clauses 5.5.5 and 5.6) and the retention rule (clauses 5.3.12 and 5.4.6). ETSI's own listing shows V2.4.1 as the latest.
The citation is not simply moved to V2.4.1. Implementing Regulations (EU) 2025/1945 and 2025/1946, which the module's header cites, name V2.3.1 in their lists of referenced standards. Only the trusted-list template of Implementing Decision (EU) 2015/1505, as amended by Implementing Decision (EU) 2025/2164, names V2.4.1. So the module and the register row now cite both, and say which act names which.
What the re-read found wrong
TrustServiceStatuscalled clauses 5.5.1.2 and 5.5.1.3 both nationally defined. Clause 5.5.1.2 is the Regulation's non-qualified service types. It also leftdeprecatedbynationallawout of the statuses it sets aside.TrustServiceHistoryattributed the rule that history is kept even when a service's present status would not require it to a note to clause 5.5.1. It is in clause 5.4.6.Pinned and tested
trusted_list/mod.rsoffUNPINNED_LEGACY, which can only shrink, so the entry is removed and the stale-inventory guard confirms it.looks_qualifiednaming convention to every service type the standard lists: the thirteen of clause 5.5.1.1 must read as qualified, and the other thirty-nine must not. Changing the helper to accept any suffix endingQCfails it onTSA/TSS-QC.The register
The ETSI TS 119 612 row now reads
V2.3.1 and V2.4.1, read on 2026-10-06. It staysNofor conformance: the standard defines the list a scheme operator publishes, and this crate consumes lists, so there is no conformance class for it to claim.just checkis green: 1708 tests, plus the plugin suites.