RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

RFC 5022, "Media Server Control Markup Language (MSCML) and Protocol", September 2007


Errata ID: 1244
Status: Rejected
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Rejected by: Nevil Brownlee
Date Rejected: 2011-03-28

Section p.29 says:

   Attributes of <variable>:

   o  type - required, no default value: Specifies the major type format
      of the spoken variable to be played.  Allowable values are "dat"
      (date), "dig" (digit), "dur" (duration), "mth" (month), "mny"
      (money), "num" (number), "sil" (silence), "str" (string), "tme"
      (time), and "wkd" (weekday).

   o  subtype - optional, no default value: Specifies the minor type
      format of the spoken variable to be played.  Allowable values
      depend on the value of the corresponding "type" attribute.
      Possible values are "mdy", "ymd", and "dmy" for dates, "t12" and
      "t24" for times, "gen", "ndn", "crd", and "ord" for digits, and
      "USD" for money.

It should say:

< see Notes >


The RFC here underspecifies many important details necessary
to be specified precisely to ensure interoperability:

a) What is the intended range of values for "wkd" ?
I guess, it may be "0", ..., "6" .
Or is it "1", ..., "7" ??
(Textual values make no sense -- or at least would make
implementations overly complicated requiring an any-language
to any-languange translation facility -- because the value
needs to be played out in the intended language according
to effective preferences.)

b) What are "gen", "ndn", "crd", and "ord" ?
No details are given to explain these abbreviations, and
most RFC readers will not be accustomed either to them.
I guess that "ord" might mean 'ordinal', "crd" be
'cardinal', and perhaps "gen" for 'generic', but "ndn" ?
The semantics need to be specified carefully for interoperability!

c) Another instance of overly US-centric thinking is the single "USD"
for money. To ensure wide-spread applicability and maintainability
of the protocol, the RFC should better apply the standard method
of incorporating the applicable 'official' registry by *reference*,
which in this case is the list of monetary units and their
internationally agreed-upon / assigned three-character
abbreviations from the ISO 4217 Maintenance Agency.
Authors comment: This is an Informational RFC, not a Standards Track one.

Report New Errata