Edit AP: prefinalisation : harmonize the use if xml id amongst language : FRBNumber TLCReference Doc Number for institutional reference

SUMMARY

Nowadays, we add the interinstitutional reference in a leg through prefinalization we put its value as the xml id value for the TCL , like this :

<TLCReference href="http://eur-lex.europa.eu/procedure/DE/2025_143" name="procedureReference" shortForm="2025/143/NLE" showAs="2025/0143 (NLE)" xml:id="procedure_2025_143"/>

So for an interinstitutional reference of "2025/143/NLE" we have the xml id "procedure_2025_143" and this in any languages version. This then help with the language alignment where we have the same id for the same elements

It is not the case yet for the institutional reference , where it gets a random id, for instance :

<TLCReference href="http://publications.europa.eu/resource/authority/document-identifier-format/COM_NUMBER" name="identifier" shortForm="COM/2025/161" showAs="COM(2025) 161" xml:id="ecGaDFdYb2IPwfuAV"/> so in this case "ecGaDFdYb2IPwfuAV" and it will be different in all linguistic version.

The goal of this ticket would be to apply the same logic as interinstitutional reference.

So if an act receive the institutional reference of COM(2025) 161 , the xml id of the TLCReference would be :

As a more complète output , taking into account all metadata which are based on this xml id , we would then have :

<FRBRnumber refersTo="~COM_2025_161" value="COM(2025) 161"/>

...

<TLCReference href="http://publications.europa.eu/resource/authority/document-identifier-format/COM_NUMBER" name="identifier" shortForm="COM/2025/161" showAs="COM(2025) 161" xml:id="COM_2025_161"/>

...

<docNumber refersTo="~COM_2025_161" xml:id="ecltbH325HZ2d2WB6">COM(2025) 161 <inline name="version" xml:id="echDVYh5famkoCNPn">final</inline></docNumber>

Doing this , the institutional, like the interinstitutional reference will have the same id amongst languages.

ACCEPTANCE CRITERIAS / GOALS

Prefinalization still works
the xml id assigned to the TCL reference for "identifier" is now based on its value and follow the pattern of "TYPE_YEAR_Number" , like "COM_2025_161", so it's not random anymore

Edited Sep 05, 2025 by Jean-Christophe WILLAIN