RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 5 records.

Status: Verified (3)

RFC 5707, "Media Server Markup Language (MSML)", February 2010

Source of RFC: INDEPENDENT

Errata ID: 3373

Status: Verified
Type: Technical

Reported By: Tamás Györgyey
Date Reported: 2012-10-09
Verifier Name: Nevil Brownlee
Date Verified: 2013-10-31

Section 16.2.2 says:

<xs:attribute name="amt" use="optional">
    <xs:simpleType>
        <xs:restriction base="xs:integer">
            <xs:minInclusive value="-96"/>
            <xs:maxInclusive value="96"/>
        </xs:restriction>
    </xs:simpleType>
</xs:attribute>

It should say:

<xs:attribute name="amt" use="optional">
    <xs:simpleType>
        <xs:union>
            <xs:simpleType>
                <xs:restriction base="xs:integer">
                    <xs:minInclusive value="-96" />
                    <xs:maxInclusive value="96" />
                </xs:restriction>
            </xs:simpleType>
            <xs:simpleType>
                <xs:restriction base="xs:string">
                    <xs:enumeration value="mute" />
                </xs:restriction>
            </xs:simpleType>
        </xs:union>
    </xs:simpleType>
</xs:attribute>

Notes:

Section "8.12.1.1 <gain>" says, for the "amt" attribute of the <gain> element:

"amt: a specific gain to apply specified in dB or the string "mute"
indicating that the stream should be muted. This attribute MUST
NOT be used if "agc" is present."

However, in section "16.2.2. msml-conf-core-datatypes.xsd" the provided schema does not allow the value "mute", only integers. Either the XSD should be corrected as suggested, or the part
'or the string "mute" indicating that the stream should be muted' removed from the description.

Errata ID: 4021

Status: Verified
Type: Technical

Reported By: Wang Lihe
Date Reported: 2014-06-23
Verifier Name: Nevil Brownlee
Date Verified: 2014-07-20

Section 8.3 says:

8.3
      deletewhen: defines whether a media server should automatically
      delete the conference.  Possible values are "nomedia",
      "nocontrol", and "never".  Default is "nomedia".
16.2.2
<xs:attribute name="deletewhen" default="never">
      <xs:simpleType>
       <xs:restriction base="xs:string">
        <xs:enumeration value="nomedia"/>
        <xs:enumeration value="nocontrol"/>
        <xs:enumeration value="never"/>
       </xs:restriction>
      </xs:simpleType>
     </xs:attribute>
10.2.2.1
deletewhen: as defined by <createconference> element in MSML
      Conference Core Package.
16.4.4
<xs:attribute name="deletewhen" use="optional" default="never">
      <xs:simpleType>
       <xs:restriction base="xs:string">
        <xs:enumeration value="nomedia"/>
        <xs:enumeration value="nocontrol"/>
        <xs:enumeration value="never"/>
       </xs:restriction>
      </xs:simpleType>
     </xs:attribute>

Notes:

I don't know which is right, it is "nomedia" from 8.3 and "never" from xsd. One of it should be rewrite. The same thing to the 10.2.2.1 and 16.4.4.

16.2.2 may be missed 'use="optional"'.

---

This RFC's authors confirm that section 8.3 is incorrect; deletewhen's deafult should be 'never'.

As well, "if the 'use=' atribute is not specified in the schema definition for a given attribute, then it defaults to 'optional'".

Errata ID: 4171

Status: Verified
Type: Technical

Reported By: Mistake in Schema
Date Reported: 2014-11-11
Verifier Name: Nevil Brownlee
Date Verified: 2014-12-22

Section 16.3.4 says:

<xs:element name="record" substitutionGroup="primitive">
<xs:complexType>
<xs:complexContent>
<xs:extension base="primitiveType">
<xs:choice minOccurs="0">
<xs:element ref="play" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="tonegen" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="recordexit">
<xs:complexType>
<xs:group ref="sendType"/>
</xs:complexType>
</xs:element>
</xs:choice>

It should say:

<xs:element name="record" substitutionGroup="primitive">
<xs:complexType>
<xs:complexContent>
<xs:extension base="primitiveType">
<xs:choice minOccurs="0">
<xs:element ref="play" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="tonegen" minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
<xs:element name="recordexit">
<xs:complexType>
<xs:group ref="sendType"/>
</xs:complexType>
</xs:element>

Notes:

Example in section 13.3 shows both <play> and <recordexit> within <record>
but the schema doesn't allows this

Sec 13.3 example
<?xml version="1.0" encoding="UTF-8"?>
<msml version="1.1">
<dialogstart target="conn:12345" name="12345">
<record prespeech="3s" postspeech="5s" maxtime="60s" termkey="#"
dest="file://record.wav" format="g729">
<play barge="true">
<audio uri="file://prompt.wav"/>
</play>
<recordexit>
<send target="source" event="done"
namelist="record.len record.end"/>
</recordexit>
</record>
</dialogstart>
</msml>

Status: Reported (2)

RFC 5707, "Media Server Markup Language (MSML)", February 2010

Source of RFC: INDEPENDENT

Errata ID: 4640

Status: Reported
Type: Technical

Reported By: Ignacio Bertacchini
Date Reported: 2016-03-16

Section 16.3.10 says:

<xs:element name="tts" type="smediaType" substitutionGroup="smedia"/>

It should say:

 <xs:element name="tts" substitutionGroup="smedia">
  <xs:complexType mixed="true">
   <xs:complexContent>
    <xs:extension base="smediaType">
     <xs:attribute name="uri" type="xs:string" use="optional"/>
    </xs:extension>
   </xs:complexContent>
  </xs:complexType>
 </xs:element>

Notes:

The tts element as is provided does not accept the uri attribute, nor the text content indicated by the RFC. The corrected validation supports commands like the following:

<?xml version="1.0" encoding="UTF-8"?>
<msml version="1.1">
<dialogstart target="conn:AAI_Unique_ID_1" name="sample" type="application/moml+xml">
<play>
<tts uri="file:///somefile.vxml"/>
<tts uri="file:///someotherfile.vxml" iterate="2" xml:lang="en-us"/>
<tts xml:lang="es-ar">text to be read</tts>
<tts>other text</tts>
</play>
</dialogstart>
</msml>

Errata ID: 4961

Status: Reported
Type: Technical

Reported By: Rajmund Takács
Date Reported: 2017-03-09

Throughout the document, when it says:


Notes:

There are some inconsistencies between the examples and the published XSD.

#1: In all of the examples, <dialogid> is the child of <msml>, but the XSD only accepts it if it's the child of <result>.

For example, this is wrong:
<msml version="1.1">
<result response="200"/>
<dialogid>conn:jd87dfg4h/dialog:12345</dialogid>
</msml>

This would be the correct one, according to the XSD:
<msml version="1.1">
<result response="200">
<dialogid>conn:jd87dfg4h/dialog:12345</dialogid>
</result>
</msml>

#2: The XSD say the <event> tag must have children, but there are examples where it doesn't have. The 'minOccurs' attribute in the regarding <xs:choice> is not explicitly specified in msml-core.xsd, but the default value is '1', so there must be at least one <name> and one <value> element, in sequence.

Ref: https://www.w3schools.com/xml/el_choice.asp

For example, this is invalid:
<event name="msml.dialog.exit" id="conn:jd87dfg4h/dialog:12345" />

#3: This is also related to <event>. In the XSD, there is a regular expression specified for the contents of <value>. This regexp does not accept the colon ':' character, but the examples contain this character.

For example, this is not accepted because of the colon character:
<event name="msml.conf.asn" id="conf:example">
<name>speaker</name>
<value>conn:hd93tg5hdf</value>
</event>

-------------------
msml-core.xsd

<xs:element name="event">
<xs:complexType>
<xs:choice maxOccurs="unbounded">
<xs:sequence>
<xs:element name="name" type="msmlEventNameValue.datatype"/>
<xs:element name="value">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="[a-zA-Z0-9.]+"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:choice>
<xs:attribute name="name" type="msmlEventName.datatype" use="required"/>
<xs:attribute name="id" type="msmlEventSource.datatype" use="required"/>
</xs:complexType>
</xs:element>

Report New Errata



Search RFCs
Advanced Search
×