Web標準化

Web標準化

[1] David Baron's weblog: March 2007 (2007-03-25 14:52:46 +09:00 版) http://dbaron.org/log/2007-03#e20070324b (名無しさん 2007-03-25 05:54:29 +00:00)

[2] David Baron's weblog: March 2007 (2007-03-25 14:52:46 +09:00 版) http://dbaron.org/log/2007-03#e20070324b (名無しさん 2007-03-25 06:14:58 +00:00)

[3] The Norwegians get it! - O'Reilly XML Blog (Rick Jelliffe 著, 2007-05-17 20:37:56 +09:00 版) http://www.oreillynet.com/xml/blog/2007/05/the_norwegians_get_it.html (名無しさん 2007-05-17 11:39:07 +00:00)

[4] Wasting resources - Anne’s Weblog ( 版) http://annevankesteren.nl/2007/05/wasting-resources (名無しさん 2007-05-20 01:43:35 +00:00)

[5] [cs/0105018] HTTP Cookies: Standards, Privacy, and Politics ( 版) http://arxiv.org/abs/cs.SE/0105018

[7] CookieIETF における標準化の歴史と、いかにそれが失敗したかを中の人が振り返った論文です。 議論の長期化によってタイミングを逃したこと、利害関係者を集めることに失敗して誰も興味を持たない標準が生まれたこと、 理想と政治に振り回されて現実とかけ離れた結論が導かれたことなど、 大変興味深いものです。

[6] Re: [http-state] Goals for the UA conformance section (was Re: Updated draft) ( 版) http://www.ietf.org/mail-archive/web/http-state/current/msg00201.html

In general, specs should be specific about what the output should be. We shouldn't leave things undefined or up to the implementation if it affects other implementations (such as servers), because otherwise we will find authors end up relying on the market leader's behaviour.

[8] 細部を未定義のままとしておくことは、実装の自由度が増し、最適化などの余地が生まれることで利用者にとってもメリットが増えると思えます。 しかし実はそれが成り立つのは、その未定義な動作の影響が閉じていて観察できない時に限られます。 たとえ仕様上未定義であっても、ほとんどの人は仕様がどうであるかではなく、主要な実装がどう動いているかに基づき行動します。 結果として、「未定義」は「市場のリーダーに倣え」の意味となり、標準の存在意義を危ぶむこととなるのです。

[9] Re: [http-state] Goals for the UA conformance section (was Re: Updated draft) ( 版) http://www.ietf.org/mail-archive/web/http-state/current/msg00202.html

We're documenting (or should be documenting, IMHO) what all implementations are going to converge on. That means describing what they do when they do the same thing, and considering differences to be bugs for which we are to find solutions that are acceptable to implementors.

[10] IRC logs: freenode / #whatwg / 20090727 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20090727#l-301

[11] (X)HTML5 Tracking ( 版) http://html5.org/tools/web-apps-tracker?from=4027&to=4028

[12] IRC logs: freenode / #whatwg / 20090803 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20090803#l-706

[14:23] <hsivonen> adactio: browser implementation reqs are the most reality-based and the non-machine-detectable conformance reqs are the least reality based parts of the spec

[13] IRC logs: freenode / #whatwg / 20090818 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20090818#l-209

[14] IRC logs: freenode / #whatwg / 20090909 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20090909#l-385

[09:29] <Hixie> tantek: the intent of the person writing teh spec is irrelevant to what the spec means. Only the spec, and what the spec references normatively, are relevant. Unless the spec says that a human can override it, no human can override it.

[15] IRC logs: freenode / #whatwg / 20090910 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20090910#l-243

[16] IRC logs: freenode / #whatwg / 20100721 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20100721#l-584

[17] IRC logs: freenode / #whatwg / 20100727 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20100727#l-1095

[18] IRC logs: freenode / #whatwg / 20101026 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20101026#l-777

[19] IRC logs: freenode / #whatwg / 20101109 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20101109#l-1008

[20] Hixie's Natural Log: Writing specifications: Kinds of statements ( ( 版)) http://ln.hixie.ch/?start=1140242962&count=1

[21] IRC logs: freenode / #whatwg / 20100620 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20100620

[22] How to write a spec - WHATWG Wiki ( ( 版)) http://wiki.whatwg.org/wiki/How_to_write_a_spec

[23] IRC logs: freenode / #whatwg / 20110504 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20110504#l-110

[24] IRC logs: freenode / #whatwg / 20110720 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20110720#l-279

[25] IRC logs: freenode / #whatwg / 20110720 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20110720#l-279

[26] IRC logs: freenode / #whatwg / 20110727 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20110727#l-197

[27] Aryeh Gregor on being an editor and the W3C process — Anne’s Blog ( ( 版)) http://annevankesteren.nl/2011/07/editor

[28] IRC logs: freenode / #whatwg / 20110729 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20110729

[29] Re: [PageVisibility] Feedback ( (Ian Hickson 著, 版)) http://lists.w3.org/Archives/Public/public-web-perf/2011Jul/0090.html

[30] IRC logs: freenode / #whatwg / 20110805 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20110805

[31] Re: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core] ( (Jonas Sicking 著, 版)) http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0952.html

[32] RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core] ( (Arthur Barstow 著, 版)) http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0789.html

[33] Re: RfC: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core] ( (Ms2ger 著, 版)) http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0790.html

[34] IRC logs: freenode / #whatwg / 20110819 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20110819

[35] How to make a web standards proposal - The Chromium Projects ( ( 版)) http://dev.chromium.org/developers/how-tos/make-a-web-standards-proposal

[36] IRC logs: freenode / #whatwg / 20120213 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20120213#l-1269

[37] IRC logs: freenode / #whatwg / 20120406 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20120406

[38] IRC logs: freenode / #whatwg / 20120420 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20120420

[39] [whatwg] multipart/form-data filename encoding: unicode and special characters ( 版) http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-May/035716.html

[40] IRC logs: freenode / #whatwg / 20120513 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20120513

[41] IRC logs: freenode / #whatwg / 20120514 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20120514

[42] IRC logs: freenode / #whatwg / 20120514 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20120514

[43] IRC logs: freenode / #whatwg / 20120702 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20120702#l-282

[44] IRC logs: freenode / #whatwg / 20120723 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20120723#l-984

[45] [whatwg] New URL Standard ( ( 版)) http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-September/037429.html

[46] IRC logs: freenode / #whatwg / 20121012 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20121012#l-196

[47] Ian Hickson - Google+ - I recently wrote the following in an e-mail, but it seems… ( ( 版)) https://plus.google.com/u/0/107429617152575897589/posts/4MrPNJzE8vV

[48] IRC logs: freenode / #whatwg / 20130225 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20130225#l-1066

[49] Why I don't attend the weekly teleconference (Was: Input on the agenda) (Ian Hickson 著, 版) http://lists.w3.org/Archives/Public/public-html/2009Jun/0616.html

[50] IRC logs: freenode / #whatwg / 20130418 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20130418#l-295

[51] IRC logs: freenode / #whatwg / 20130423 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20130423

[52] Re: Renamed topic: focus and length of HTML5 (Ian Hickson 著, 版) http://lists.w3.org/Archives/Public/public-html/2009Dec/0173.html

[53] Standards/license - MozillaWiki ( ( 版)) https://wiki.mozilla.org/Standards/license

[54] Re: Request to publish HTML+RDFa (draft 3) as FPWD (Jonas Sicking 著, 版) http://lists.w3.org/Archives/Public/public-html/2009Sep/0865.html

[55] IRC logs: freenode / #whatwg / 20100302 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20100302#l-102

[56] Web API Design Cookbook ( ( 版)) http://darobin.github.io/api-design-cookbook/

[57] IRC logs: freenode / #whatwg / 20131105 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20131105

[58] Specs/style - WHATWG Wiki ( ( 版)) http://wiki.whatwg.org/wiki/Specs/style

[59] Specs - WHATWG Wiki ( ( 版)) http://wiki.whatwg.org/wiki/Specs

[60] Specs/advice - WHATWG Wiki ( ( 版)) http://wiki.whatwg.org/wiki/Specs/advice

[61] IRC logs: freenode / #whatwg / 20100222 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20100222#l-893

[62] IRC logs: freenode / #whatwg / 20100618 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20100618#l-453

[63] David Baron's weblog: Hidden complexity in specifications ( 版) http://dbaron.org/log/20100531-specs

[64] IRC logs: freenode / #whatwg / 20140409 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20140409

[65] IRC logs: freenode / #whatwg / 20140626 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20140626#l-721

[66] IRC logs: freenode / #whatwg / 20090920 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20090920#l-213

[67] Standards - MozillaWiki ( ( 版)) https://wiki.mozilla.org/Standards

[68] IRC logs: freenode / #whatwg / 20140906 ( ( 版)) http://krijnhoetmer.nl/irc-logs/whatwg/20140906

[69] Web Applications 1.0 r8772 XML MIME types: Apparently this 'stable' reference became stale instead of stable, and now needs updating. ( ( 版)) https://html5.org/r/8772

[70] xkcd: Standards ( ( 版)) http://xkcd.com/927/

[71] Re: Bringing APIs for experimental hardware/software to the Web ( (Robert O'Callahan 著, 版)) http://lists.w3.org/Archives/Public/public-webapps/2014OctDec/0396.html

[72] WebAPI/DesignGuidelines - MozillaWiki ( ( 版)) https://wiki.mozilla.org/WebAPI/DesignGuidelines

[73] IRC logs: freenode / #whatwg / 20150301 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20150301#l-331

# [21:12] <Hixie> i agree that in theory it sounds like you'd get better results long term if you provided general solutions to hypothetical general problem spaces instead of generalised solutions to targetted problems

# [21:12] <Hixie> but in practice it never works

# [21:12] <Hixie> the specific has a way to focus the solution to one that actually works

# [21:12] <Hixie> whereas general solutions tend to become quagmired in theoretical problems

[74] IRC logs: freenode / #whatwg / 20150302 ( 版) http://krijnhoetmer.nl/irc-logs/whatwg/20150302

# [02:30] <tantek> TabAtkins: just the last time someone tried to do "server can expose an HTTP endpoint and respond to certain standardized discovery protocols", we ended up with WS-Deathstar

# [02:31] <tantek> or perhaps that was the *first time*

# [02:31] <tantek> "Web Intents" may have been the latest version of that kind of discovery abstraction disaster.

# [02:31] <tantek> I wish you better luck.

# [02:31] <TabAtkins> I mean, you can layer whatever you want on top of it; you've just got an open communications channel.

# [02:31] <tantek> exactly what they both said

# [02:31] <tantek> classic architecture astronomy

[75] Re: new meta tags to protect code visibility or immuatbility (Brad Hill 著, 版) https://lists.w3.org/Archives/Public/public-webappsec/2016Feb/0072.html

[76] The Web Browser API Incubation Anti-Pattern | The Beautiful, Tormented Machine ( 版) http://manu.sporny.org/2016/browser-api-incubation-antipattern/#comment-29249

[78] WHATWG は「Please leave your sense of logic at the door, thanks!」 を標語としています。

[77] annevk は、 「the more you learn the less you know」が Webプラットフォームのテーマだと言っています。

[79] [e] (0) More information on the reasons for authoring conformance cri… ( (Hixie著, )) https://github.com/whatwg/html/commit/0ab4246caf8b113e44602b713c37de87f8e84241

[80] Users, clients, and servers — Anne’s Blog () https://annevankesteren.nl/2016/05/client-server

[81] Revive createObjectURL? · Issue #404 · w3c/mediacapture-main () https://github.com/w3c/mediacapture-main/issues/404#issuecomment-255324610

[82] Why specs matter () http://www.diveintomark.link/2004/why-specs-matter

[83] Feedback on the proposal to change U+FFFD generation when decoding ill-formed UTF-8 () http://unicode.org/pipermail/unicode/2017-May/005453.html

[84] [selectors-4] Note that adherence to grammar is insufficient for vali… (fantasai著, ) https://github.com/w3c/csswg-drafts/commit/e60e220b27a10ef17e2a5dd9016448be559fae54

[85] Normative: Use array indices instead of integer indices in OrdinaryOwnPropertyKeys by mathiasbynens · Pull Request #1242 · tc39/ecma262 () https://github.com/tc39/ecma262/pull/1242

[86] Standards should be standards regardless of vendor client adoption · Issue #89 · whatwg/sg () https://github.com/whatwg/sg/issues/89