<SMS></SMS>
.nf
-We don't parse this case at the moment.
+We don't parse this case at the moment, but we do recognize it and report
+it as unsupported so that offending documents can be removed. An example
+is provided as test/xml/newsxml-multiple-sms.xml.
.IP \[bu]
\fIOdds_XML.dtd\fR
entirely (although a hack is employed to facilitate parsing). The same
thing goes for the newer <League_Name> element.
+We've also seen XML on the feed where the home/away starter elements
+exist and have ID attributes but no content. For example,
+
+.nf
+<AStarter ID=\(dq0\(dq></AStarter>
+<HStarter ID=\(dq0\(dq></HStarter>
+.fi
+
+We don't handle this at the moment, but since the starter id/name are
+already optional (we just expect them to be present or missing as a
+pair), it wouldn't be too hard to support.
+
.IP \[bu]
\fIweatherxml.dtd\fR
Another problem that comes up occasionally is that the home and away
team elements appear in the reverse order. As in the other case, we
report these as unsupported and then \(dqsucceed\(dq so that the
-offending document can be removed if desired.
+offending document can be removed if desired. An example is provided
+as test/xml/weatherxml-backwards-teams.xml.
.SH DEPLOYMENT
.P