RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

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


Errata ID: 4961
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT

Reported By: Rajmund Takács
Date Reported: 2017-03-09
Held for Document Update by: Nevil Brownlee
Date Held: 2017-07-20

Throughout the document, when it says:


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"/>

This would be the correct one, according to the XSD:
<msml version="1.1">
<result response="200">

#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">


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

Report New Errata

Advanced Search