[1]
[CITE[xml5 - Google Code]] ([CODE[2007-06-03 00:01:34 +09:00]] 版)
([[名無しさん]] [WEAK[2007-06-02 15:02:34 +00:00]])
[2]
[CITE[ECS - Moving from Well-Formed XML to Amply-Tagged XML - O'Reilly XML Blog]] ([[Rick Jelliffe]] 著, [CODE[2007-09-07 22:31:18 +09:00]] 版)
([[名無しさん]])
[3]
[CITE[XML5 - Anne’s Weblog]] ([CODE[2007-10-28 13:25:53 +09:00]] 版)
([[名無しさん]])
[4]
[CITE[IRC logs: freenode / #whatwg / 20081014]] ([TIME[2008-10-15 16:26:09 +09:00]] 版)
>
- [10:39] annevk3: How many entities do you intend to define in XML5?
- [10:40] I was planning on having the exact same list as HTML5 (though always require a semicolon)
[5] [CITE@en[Re: Comments on HTML WG face to face meetings in France Oct 08]] ([[Håkon Wium Lie]] 著, [TIME[2008-11-17 17:40:16 +09:00]] 版)
>The first test of this that I experienced was with WML. WML is
expressed in XML and UAs must therefore follow the draconian rules of
XML. All UAs were starting from scratch and they were expected to
follow the rules. WML was going to be much cleaner than HTML! Opera
certainly followed the rules, and we still do. However, one major
handset maker quickly changed its parser to be more lenient, along the
lines of HTML. I can't really blame them. Noone has ever thanked Opera
for sticking to the rules; rather, we've heard much grief from users
and customers. Fortunately, WML didn't succeed.