[2]
ECS - Moving from Well-Formed XML to Amply-Tagged XML - O'Reilly XML Blog (Rick Jelliffe 著, 2007-09-07 22:31:18 +09:00 版) http://www.oreillynet.com/xml/blog/2007/02/ecs_moving_from_wellformed_xml.html
(名無しさん)
[10:39] <gsnedders> annevk3: How many entities do you intend to define in XML5?
[10:40] <annevk3> I was planning on having the exact same list as HTML5 (though always require a semicolon)
[5] Re: Comments on HTML WG face to face meetings in France Oct 08 (Håkon Wium Lie 著, 版) http://lists.w3.org/Archives/Public/public-html/2008Nov/0181.html
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.
[14:59] <annevk> XML5 is pretty much done, but there's no buy-in
[15:00] <annevk> just a lot of buzz
[15:00] <rubys> done? as in an implementation that works?
[15:00] <annevk> there's a Python implementation
[15:01] <annevk> from which some sort of spec has been generated as well
[15:01] <rubys> that's not just a prototype, but something that you consider as something that might be useful?
[15:01] <annevk> missing details are attribute value normalization, character encoding sniffing, and >5 predefined entities iirc
[15:01] <Philip`> Has it been advertised at all, or mentioned anywhere other than a few posts on your blog?
[15:02] <annevk> rubys, if someone packages it it's pretty much like html5lib with a few missing bits
[15:02] <rubys> python would make entities easy (it has a builtin function for this), and chardet could address sniffing
[15:03] <annevk> I mostly meant <?xml ... ?>
[15:03] <rubys> attribute value normalization, xml style, sucks
[15:03] <annevk> apparently infinite whitespace is allowed...
[15:03] <annevk> agreed
[15:03] <Philip`> annevk: You should sneakily add the XML5 code into html5lib, so it can gain widespread deployment before anyone even knows they should care about it
[15:03] <annevk> it would sort of break the design principles if that was changed
[15:03] <rubys> i'll put it on my list of things to look at, which unfortunately is also too long
[15:04] <rubys> Philip`: +1
[15:04] <rubys> I put a "liberal xml parser" in there, but would love to see it replaced with xml5.
[15:05] * jgraham is more than happy with anything that replaces the lxp and is maintained
[57] Charter - XML Error Recovery Community Group
( ( 版))
http://www.w3.org/community/xml-er/wiki/Charter
[60] XML Error Recovery Community Group
( (Jeni Tennison 著, 版))
http://lists.w3.org/Archives/Public/www-tag/2012Feb/0045.html
[61] XML Error Recovery Community Group
( ( 版))
http://www.w3.org/community/xml-er/
[62] XML Prague 2012: The web would be so cool without the web developers | Eric van der Vlist
( ( 版))
http://eric.van-der-vlist.com/blog/2012/02/15/xml-prague-2012-the-web-would-be-so-cool-without-the-web-developers/
[58] Another approach
( (James Clark 著, 版))
http://lists.w3.org/Archives/Public/public-xml-er/2012Nov/0000.html
[43] Intent to Deprecate and Remove: XSLT - Google Groups
( ( 版))
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/zIg2KC7PyH0
[44] 501837 – Liberalize XML Names to reflect latest XML 1.0 edition (5th)
( ( 版))
https://bugzilla.mozilla.org/show_bug.cgi?id=501837#c3
[45] 233154 – Add support for XML 1.1
( ( 版))
https://bugzilla.mozilla.org/show_bug.cgi?id=233154#c30
[46] Intent to Deprecate and Remove: XSLT - Google グループ
( ( 版))
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/zIg2KC7PyH0/Ym28fD2ZIAsJ
[47] Re: Ending DTD proliferation at the W3C
( (Henri Sivonen 著, 版))
http://lists.w3.org/Archives/Public/www-tag/2014Jan/0041.html
[48] Google Project Hosting
( 版)
https://code.google.com/hosting/moved?project=xml5
[18:22] <TabAtkins> annevk: Opinion - if SVG explicitly embraces a looser format for standalone, should we just use HTML (special-case when the first tag is <svg> to make it an SVG document rather than HTML) or use your XML5 or something similar?
[65] 1180625 – Implement an XML5 parser.
( 版)
https://bugzilla.mozilla.org/show_bug.cgi?id=1180625
xml5ever is an XML parser that works on a modified specification of XML called XML5, which drops certain properties of XML like well-formedness for better compatibility with HTML and better error recovery.
[71] Characterizing ill-formed XML on the web
( 版)
https://www.w3.org/2012/Talks/08-quin-xml-web-corpus/
[72]>>71 おかしな XML は HTML と Atom と RSS ばかりじゃないか、
と言ってるけどおかしくない XML もそれ (と XML Sitemap くらい)
しかないんですよね、そこに示されてるデータだと。。。
[73] Make UAs support named character references in all XML docs by sideshowbarker · Pull Request #2056 · whatwg/html
()
https://github.com/whatwg/html/pull/2056
[74] HTML parser: align custom elements with the template element · Issue #630 · w3c/webcomponents
()
https://github.com/w3c/webcomponents/issues/630
[76] HTML parser: align custom elements with the template element · Issue #630 · w3c/webcomponents
()
https://github.com/w3c/webcomponents/issues/630
[77] HTML module should require a new top level element · Issue #752 · w3c/webcomponents
()
https://github.com/w3c/webcomponents/issues/752#issuecomment-459368703
[78] Create an XML5 standard · Issue #4436 · whatwg/html
()
https://github.com/whatwg/html/issues/4436
[79] The case for XML5 — Anne’s Blog
()
https://annevankesteren.nl/2019/10/case-for-xml5
[81] Consider more name validation loosening · Issue #1373 · whatwg/dom, https://github.com/whatwg/dom/issues/1373#issuecomment-2896873457