Extra version markers in Approved Recommendations

[strogonoff]

In 1173, under Approved Recommendations, there is this entry:

–   ITU-T H.783 (V2) (05/2019): Digital signage: Audience measurement services

• The “V2” part appears nowhere on https://www.itu.int/rec/T-REC-H.783.
• Other recommendations do not specify this version marker: e.g., in the same issue recommendation H.846 has four previous versions, but does not say “V5”.
• Recommendations already have versions specified as year & month for disambiguation.

Since this additional version marker doesn’t seem to be an actual property of ITU recommendation model, isn’t used consistently in OB issues, and is redundant, can we omit it from deliverables?

(In future, once (if) we port recommendation metadata fully, we may be able to infer recommendation version number and show it in OB issues for all recommendations.)

[ronaldtse]

@strogonoff I'm pretty sure the "(V2)" part is an invalid representation. That said, there is no standard representation of an ITU document identifier. We can omit it from the deliverable.

BTW, Relaton-ITU provides the full ITU document metadata model.

But please keep this issue open so I can deal with it officially.

[ronaldtse]

(In future, once (if) we port recommendation metadata fully, we may be able to infer recommendation version number and show it in OB issues for all recommendations.)

We probably don't want this because we cannot assume we can get ALL the versions of the document, unless the version number is provided by them...

[strogonoff]

That said, there is no standard representation of an ITU document identifier.

It’s a bit messy, though from what I observed all recommendations have a code, a title, and a version (year & month). Title varies across versions, so to be more precise it looks like this:

Recommendation {
  code: <prefix>.<major>.<minor>
  versions:
    -  { year: <YYYY>, month: <MM>, title: <string> }
}

(In future, once (if) we port recommendation metadata fully, we may be able to infer recommendation version number and show it in OB issues for all recommendations.)

We probably don't want this because we cannot assume we can get ALL the versions of the document, unless the version number is provided by them...

Well, I believe all of them can be found on pages such as https://www.itu.int/rec/T-REC-H.846, but it is a bit confusing since the page also lists auxiliary documents related to specification.

[ronaldtse]

It maybe slightly incorrect to call them "versions", the new documents are technically "new editions" of the standard.

Well, I believe all of them can be found on pages such as https://www.itu.int/rec/T-REC-H.846, but it is a bit confusing since the page also lists auxiliary documents related to specification.

There is no guarantee that they will all be provided like this one :wink: