Good Practices for Capability URLs
Capability URLs grant access to a resource to anyone who has the URL. There are particular application design patterns for which this is useful as they remove the necessity for users to log in to a site and are easily delegated to others. But their use can open up some security issues. URLs are not generally required to be kept secret, and there are various routes through which capability URLs can
Open Web Platform Weekly Summary - 2013-02-25 - 2013-03-03
Author(s) and publish date By: Karl Dubost Published: 4 March 2013 This is our weekly Openweb Platform Summary from February 25 to March 3, 2013. You can read again the last week blog post. Your comments are helpful. Multi-GET for HTTP2 Phillip Hallam-Baker is wondering if a Multi-GET method would be useful for HTTP2 to access directly a list of contents. The format would be something along MGET <
Streams API (Editor's Draft)
The WHATWG Streams API spec provides an API for representing and handling a stream of data in JavaScript. This W3C spec is intended to extend the WHATWG spec to meet requirements specific to the browser environment. Introduction Web applications should have the ability to acquire, manipulate, and pass data in a wide variety of forms, including as a sequence of data made available over time. The WH
[Editorial Draft] Extending and Versioning Languages: Compatibility Strategies
[Editorial Draft] Extending and Versioning Languages: Compatibility Strategies Draft TAG Finding 17 September 2008This version:http://www.w3.org/2001/tag/doc/versioning-compatibility-strategies-20080917.htmlLatest version:http://www.w3.org/2001/tag/doc/versioning-compatibility-strategiesPrevious versions: Unapproved Editors Drafts: http://www.w3.org/2001/tag/doc/versioning-compatibility-strategies
Plan 2014
Introduction The HTML Working Group has made much progress on HTML5 and related specifications. The HTML Working Group Chairs and the Protocols and Formats WG Chair have been asked by the W3C Team to provide a credible plan to get HTML5 to Recommendation status by 2014. Challenges remain in achieving this goal. We sought to produce a plan that achieves this date and that has minimal risk of delays
2012年8月のW3C: CSS WG F2F開催 | Web標準Blog | ミツエーリンクス
URL
URL W3C Working Group Note 06 December 2016 (Link errors corrected 7 Mar 2017) This version: https://www.w3.org/TR/2016/NOTE-url-1-20161206/ Latest published version: https://www.w3.org/TR/url-1/ Previous version: https://www.w3.org/TR/2014/WD-url-1-20141209/ Latest editor's draft: https://url.spec.whatwg.org/ Editors: Anne van Kesteren, Mozilla Sam Ruby, IBM Repository and Participation: Commit h
Input Method Editor API (W3C Working Draft 17 December 2013)
Input Method Editor API W3C Working Group Note 24 May 2016 This version: http://www.w3.org/TR/2016/NOTE-ime-api-20160524/ Latest published version: http://www.w3.org/TR/ime-api/ Latest editor's draft: http://w3c.github.io/ime-api/ Previous version: http://www.w3.org/TR/2016/NOTE-ime-api-20160515/ Editor: Travis Leithead, Microsoft, travil@microsoft.com Previous Editors: Takayoshi Kochi, Google (th
Document Object Model FAQ
About DOM . DOM Activity statement Technical Reports . Technical Materials Test Suites . FAQ . Mailing List Member-restricted resource: DOM Working Group Document Object Model FAQ October 22, 2003. Subject to change. Maintained by: the W3C DOM WG This document contains the most frequently asked questions about the Document Object Model. It is not intended to replace any specifications or other doc
List of Concerns from Stephen Zilles on 2012-03-07 (www-archive@w3.org from March 2012)
From: Stephen Zilles <szilles@adobe.com> Date: Tue, 6 Mar 2012 16:45:57 -0800 To: "www-archive@w3.org" <www-archive@w3.org> CC: "Stephen N. Zilles" <steve@zilles.org> Message-ID: <CE2F61DA5FA23945A4EA99A212B157954AE1ED0B87@nambx03.corp.adobe.com> Below is the list of Concerns about developing standards within the W3C. An HTML file with the same content is attached to insure the formatting remains.
Encoding Standard
Participate: GitHub whatwg/encoding (new issue, open issues) Chat on Matrix Commits: GitHub whatwg/encoding/commits Snapshot as of this commit @encodings Tests: web-platform-tests encoding/ (ongoing work) Translations (non-normative): 日本語 1. Preface The UTF-8 encoding is the most appropriate encoding for interchange of Unicode, the universal coded character set. Therefore for new protocols and for
CSS 2D Transforms Module Level 3
CSS Transforms Module Level 1 W3C Candidate Recommendation, 14 February 2019 This version: https://www.w3.org/TR/2019/CR-css-transforms-1-20190214/ Latest published version: https://www.w3.org/TR/css-transforms-1/ Editor's Draft: https://drafts.csswg.org/css-transforms/ Previous Versions: https://www.w3.org/TR/2018/WD-css-transforms-1-20181130/ https://www.w3.org/TR/2017/WD-css-transforms-1-201711
Community-Prioritized Web Standards – Brendan Eich
Mozilla is happy to support Facebook in forming a Core Mobile Web Platform W3C Community Group in which to curate prioritized, tiered lists of emerging and de facto standards that browsers should support in order for the Web to compete with native application stacks on mobile devices. The W3C Community Groups do not create normative specifications; their work is informative at most [UPDATED per Ia
fantasai 52: about:csswg
An Inside View of the CSS Working Group at W3C Cette série d’articles est en train d'être traduite en français par Jérémie Patonnier et Frédéric Bourgeon de Mozilla Francophone ! The CSS Working Group is tasked with maintaining the existing CSS standards and creating new ones. There have been many new people joining our group lately, in addition to more non-members interacting with us. Since it us
What jquery and js developers want from web stds. -- 02 Nov 2011
Present Regrets Chair shepazu, yk, pi Scribe darobin pi: we're going to talk about the jQuery Standards Group <npdoty> scribenick: darobin pi: how we're going to help improve specifications ... things that developers want in the platform that we don't see being actively developed ... how to get better involvement from authors yk: I don't like the fact that we use "author", most people are really d
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
CSS WG Blog – Minutes Telecon 2013-10-30
勧告候補になったHTML5.0の仕様についてと、HTML5.1の始まり - HTML5とか勉強会
Evolution/Versions - W3C Wiki
w3c/html
Twitter Open Source on Twitter: "today we are excited to support and join the @w3c, to start we plan on collaborating in the areas of security, mobile and web components"
