Normalizing references to recommendations in annexed lists: “According to” vs. “Complement to”

[strogonoff]

In the Lists Annexed section, most items relate to some ITU recommendation or another (see snipped below).

It would help to normalize this relation in the new OB data format being developed (#5).

However, the relationships seem to be expressed in two different forms: “according to” and “complement to”. Is there a semantic difference?

If there is no meaningful difference between the two phrasings,

• we will link recommendations in a simpler way, via a relation of general kind, in the new OB data format,
• documents generated from the new OB data format will use consistent unified phrasing (e.g., “in accordance with” and just that, no “complement”).

Here is an excerpt illustrating different types of recommendation relationships in “lists annexed”:

1002:: List of Country or Geographical Area Codes for non-standard facilities in telematic services (Complement to ITU-T Recommendation T.35 (02/2000)) (Position on 15 April 2012)

1001:: List of the national authorities designated to assign ITU-T Recommendation T.35 terminal provider codes (Position on 1 April 2012)

1000:: Service Restrictions (Recapitulatory list of service restrictions in force relating to telecommunications operation) (Position on 15 March 2012)

994:: Dialling Procedures (International prefix, national (trunk) prefix and national (significant) number) (In accordance with ITU-T Recommendation E.164 (11/2010)) (Position on 15 December 2011)

991:: Call-Back and alternative calling procedures (Res. 21.PP-2006)

980:: List of Telegram Destination Indicators (In accordance with ITU-T Recommendation F.32 (10/1995)) (Position on 15 May 2011)

978:: List of Telex Destination Codes (TDC) and Telex Network Identification Codes (TNIC) (Complement to ITU T Recommendations F.69 (06/1994) and F.68 (11/1988)) (Position on 15 April 2011)

[ronaldtse]

Thanks @strogonoff , pending reply. However, I suggest we treat each of these items as purely "Titles" of the documents.

For example, "Mobile Network Codes (MNC) for the international identification plan for public networks and subscriptions (According to Recommendation ITU-T E.212 (09/2016)) (Position on 15 December 2018)" is a section given within the "ITU OB 1162", that is considered an "Annex of ITU OB".

i.e. the ITU OB contains two parts: the "numbered issues" and an "annex".