W3C入門

目次

• W3Cとは，コンセンサス形成，およびグループ参加者
• W3Cチームについて: 組織図，W3Cディレクター，CEO，およびドメイン・リーダー
• W3Cドメイン
• W3C仕様書(Technical Report)作成手続き，およびW3C特許方針
• 諮問機関: Advisory Board および Technical Architecture Group
• チーム・コンタクトおよび議長の役割

W3Cとは，コンセンサス形成，およびグループ参加者

W3Cとは

• Webの長期的な発展のために必要な，オープンな標準の策定
• 原則: 協力，原則に忠実，協調による発言力増大，ロイヤリティ・フリー，任意による採用
• 共同作業: ホスト，チーム，会員，および一般非会員

W3Cとは

• W3Cプロセスに則って，コンセンサス・ベースで標準化推進
• W3Cプロセスは，公正な標準化，標準化への責任，および標準化の進捗を促進
• W3Cプロセスは，W3Cの議論グループに関する，一般的な方針を定義: 参加方法，問題提起，要求提示，標準策定等
• W3C Advisory Boad (AB) は，W3Cプロセス自体の改善について議論

コンセンサス

「W3Cプロセスにより，各議論グループの議長には，各グループの活動にあたって，グループ内で交わされる適正な意見および反対意見について，その発言者が積極的な参加者であるかどうかによらず，全てきちんと考慮した上で，問題解決にあたることが要求される．」

• コンセンサス: グループ内で本質的な数の参加者が提案を支持しており，かつ，誰も「正式な反対」を唱えていない
• 議長は， 「正式な反対」があった場合，そのことを記録した上で先へ進むことができる．
• 「正式な反対」は，W3Cディレクター (Tim-Berners Lee) に報告され，ディレクターは，グループに対して再考を促すことができる

議論グループへの参加者

• 各議論グループは，以下から構成される:
  1. 会員企業の代表
  2. Invited Experts (招聘専門家)
  3. チームの代表
• 同時に二つの組織を代表することは不可
• Working Group (WG) においては，ロイヤリティ・フリー特許方針への同意が必要

会員企業の代表

• 各会員企業のW3C担当窓口(Advisory Committee representatives; AC Rep.)により参加登録
• 基本的に 各会員企業の被雇用者 (コンサルタント契約等，例外あり)
• W3C利益競合方針 に同意の必要あり
• W3Cディレクターにより，参加が拒否される場合あり
• Working Group (WG) においては，会員企業単位で，ロイヤリティ・フリー特許方針への同意が必要

Invited Experts (招聘専門家)

• 仕様書策定に必要な専門技術に応じて，議長により招聘
• 議長およびチーム・コンタクト(グループ担当チーム・スタッフ)の同意が必要
• 特定の団体を代表することも可能 (例えば，標準化団体同士のリエゾン関係)
• W3C利益相反方針に同意の必要あり
• その他 手続上必要な情報 の提供

チーム・スタッフの代表

• W3C雇用スタッフ，実習生，およびW3Cフェロー(会員企業からの出向)
• W3Cチーム向け利益相反方針に同意

The W3C Team

W3C Team Organization

(Simplified and partial)

W3C Director

• Is the lead technical architect at W3C
• Is responsible for assessing consensus within the community for:
  1. architectural choices
  2. publication of technical reports
  3. creation of new Groups
• Appoints group Chairs
• Resolves appeal of a Working Group decision

W3C CEO

• Leads the W3C organization:
  general sounding board for what's going in the Consortium or for getting feedback on your Group
• Leads Member relations
• Leads liaisons with other organizations, governments, and the public

Note: Ralph Swick, W3C COO, helps in leading the operations of W3C

W3M

• Is composed of the W3C Management
• Approves new Group charters (after AC review) and extensions on behalf of the Director
• Approves Chairs on behalf of the Director
• Prioritize headlight ideas and resources

Domain Leads

• Lead a set of W3C Groups
• Manage team contacts
• Assist the Director, in particular for assessing consensus, appointing group Chairs, or resolving appeal

Team Contacts

• Act, within the Group, as an interface between the Chair, Group Members, other Working Groups, and the W3C Team
• Assist the Chair in his or her role
• Represent the W3C organization and the W3C Director

see also the role of Team Contacts

MarComm Team

Takes care of Marketing and Communications, including:

• Communications with Membership
• Public relations, including social media
• Website design and content
• Marketing programs in support of business development
• Media and analyst relations
• Publications rules

W3C Domains

W3C currently covers a wide range of issues related to the Web.

• Information and Knowledge
• Interaction
• Technology and Society
• Ubiquitous Web
• Web Accessibility Initiative

Information and Knowledge

Information and Knowledge

Structured information publishing and distribution

• LDP: RESTful application integration patterns using read/write Linked Data
• Data on the Web Practices, CSV on the Web
• Digital Publishing: Publishing on the Open Web Platform
• XML: Query, XSLT, maintenance
• Also looking into linked geospatial data, annotation facilities

Interaction

Interaction

Shape the Web's user interface

• Languages and formats: HTML, CSS, SVG, PNG, MathML, WOFF, Web IDL
• APIs: Sockets, Workers, File, Notification, Timing, DOM, Streams, Storage, XHR, Pointer Lock, Web Driver, …
• Internationalization and multilingual: reviews, ITS, Encoding
• Video & Audio: HTML, Web Audio, MIDI, Media Streaming, Encryption, Media Fragments, Annotations, Captioning, media requirements (with WAI PF)
• Graphics: PNG, SVG, HTML/canvas, 2DContext, CSS
• Styling: a lot of CSS, SVG, WOFF
• Network: XHR, Sockets, Streams, Media Source, Timing, Beacon
• Offline: HTML/appcache, Storage, Indexed DB, Manifest, Service Workers, File
• Device: Pointer Events, Pointer Lock, Input Methods, Screen Orientation, Fullscreen, Gamepad, UI Events
• Performance: Timing, Resource Priority, High Resolution Time, Visibility, Error Logging
• Not yet looking at Gaming

Technology and Society

Technology and Society

Intersection of Web technology and public policy

• Privacy: DNT, reviews
• Security: XML, Crypto API, CORS, CSP
• Patent Policy: PSIG
• Also looking into pervasive monitoring, identity, social

Ubiquitous Web

Ubiquitous Web

Web access for anyone, anywhere, anytime, using any device

• Mobile, televisions
• APIs: WebRTC (P2P connections, P2P Data API, P2P DMTF, RTC Statistics), devices
• Devices: Geolocation, NFC, Media Capture and APIs, Ambient Light, Proximity Sensor, Vibration, and permissions
• Video: Media Capture, Media Capture and Streams, Recording
• System Application: Lifecycle, URI, Scheduler, Contacts, Messaging, Telephony
• Network: P2P connections, Raw Sockets
• Voice and speech: VXML, SRGS, SISR, PLS, SSML, CCXML
• Also looking into automotive, Web of things, payments

Web Accessibility Initiative

Web Accessibility Initiative

Make the Web accessible to people with disabilities

• Requirements, reviews and consultations for W3C specifications
• Recommendations, guidelines, techniques, testing materials
• Guidelines: content (WCAG), user agent (UAAG), authoring tools (ATAG)
• WAI ARIA: Accessible Rich Interactive Applications
• Indie UI: input method independence: events, user context
• Techniques and resources to facilitate website evaluation and repair
• Web symposia on accessibility research and development
• Education and outreach
• Standards harmonization

Horizontal reviews

• Accessibility: Protocol and Format Working Group
• Internationalization: Internationalization Working Group
• Privacy: Privacy Interest Group
• Security: (not assigned yet)
• Mobile: (not assigned yet)
• Javascript APIs: public-script-coord@w3.org
• Web Architecture: Technical Architecture Group

Technical Report Development Process and Patent Policy

From an idea to a Web standard

Starting points

Submissions, Headlights, Community Groups, Business Groups and Workshops:

These are ways that we get initial input into areas for W3C Standards work and each has its own attributes

Submissions

• Allows W3C Members to propose technology or other ideas
• Published as a Member submission by W3C
• Should not overlap with the scope of a Working Group

Headlights

Propose a topic and develop a plan to address it

• Annual call for proposals in October (e.g. Headlights 2014) to the W3C Members and W3C Team
• Proposals are public
• W3M prioritization of proposals in January
• Approval of projects in July by W3M

Community Groups

• Designed to promote innovation and to lower barriers to individual participation
• Scope may overlap with Working Groups
• Fast and easy to start, open to everyone
• Several CGs have made contributions to Rec Track work and stay open to keep working on additional issues
• Royalty-free licensing obligations are only for the direct contributions

Business Groups

• W3C umbrella for INDUSTRY conversations for things that MAY have Web Technologies as part of the answer
• Fast and easy to start, some fees involved as more staff committed
• Royalty-free licensing obligations are only for the direct contributions

Workshops

• W3C public event to gather the industry to get as broad a view as possible on a topic
• Results of Workshop can vary depending on nature of conversation, participant awareness of W3C and clarity of requirements

Currently upcoming Workshops

• Strengthening the Internet Against Pervasive Monitoring (STRINT)
• Linking Geospatial Data
• Web and TV Convergence
• Web Payments: How do you want to pay?
• New Horizons for the Multilingual Web

See also Workshops

52 Working Groups

Each has:

• One or more Chairs
• One or more Team Contacts
• A Charter developed with the W3C Members
• Tools:
  Mailing list(s), teleconference(s), wiki(s), Version Control System(s), etc.

A Working Group MUST follow the W3C Process.

Group charter

• Proposed to the Advisory Committee and approved by the W3C Director
• Contains the scope, nature of the deliverables, dependencies, communication mechanisms, additional decision procedures, etc.
• Is also a tool for driving the Group, so make it useful and use it well

Groups can proposed to add new deliverables at any time

W3C Recommendation Track

W3C Patent Policy

• facilitate the development of W3C Recommendations by W3C Working Groups;
• address issues related to patents that arise during and after the development of a Recommendation.

W3C Patent Policy

W3C Patent Policy for Chairs

• Patent Policy Management with IPP (eg CSS)
• Exclusion periods are at First Public (150 days) and Last Call (60 days)
• Managing contributions from non-participants: Chair should ask the Contributor to disclose any essential claims and their associated terms
• Exceptions are handled by Patent Advisory Groups (PAG)

Advisory Board and Technical Architecture Group

W3C Advisory Board

• Provides ongoing guidance to the Team on issues of strategy, management, legal matters, process, and conflict resolution
• Manages the evolution of the Process Document, acting as the sponsoring Working Group
• Currently revising the Recommendation Track Process (comments sent to public-w3process@w3.org)

*PROPOSED* Rec Track

W3C Technical Architecture Group

• Scope is limited to technical issues about Web architecture
• Documents and builds consensus around principles of Web architecture
• Resolves issues involving general Web architecture
• Helps coordinate cross-technology architecture developments

Contact the TAG Chairs if you're interested in TAG feedback (Daniel Appelquist, Peter Linss).

Role of Team Contacts and Chairs

Team Contacts (1)

• Is a Participant and Contributor in the Working Group
• ensure coordination and communication; act as an interface between the Chair, Group Members, other Working Groups, and the W3C Team
• are aware of the technical requirements and issues in the Group
• represent the W3C organization and the W3C Director within the Group, i.e. represent the views of the W3C Team even if the Team does not have a single position (note that the Team Contact may raise Formal Objections as well on behalf ot the Director)

Team Contacts (2)

• Drive and help Group organizers in creating charter and convening Group
• monitor group participation and operations: participation, records, publications
• serve as Contact with W3C Team: webmaster, MarComm team, Domain Lead, CEO, Director, etc.
• assist the Chair in completing his or her role, including coordination or moderating disputes

See also Role of the Team Contact

Chairs

• Provides Leadership in the Working Group
• Ensures the Group in making progress and maintaining timelines
• Develop Group charter with the Team Contact and proposes it to the Director
• Coordinate with W3C Team and other W3C Working Groups as needed
• Maintain Group Process & Organization, including maintaining a positive work environment

See also Role of the Group Chair

W3C Director

• Proposes Charters to the Advisory Committee (delegated to W3M)
• Approves Charters and their extensions (delegated to W3M)
• Approves Group closures (delegated to W3M)
• Appoints or reappoints Chairs (delegated to W3M)
• Submit W3C Recommendations to other standards bodies (delegated to W3M)
• Approves First Public Wording Draft publication (delegated to Domain Leaders)
• Approves Candidate Recommendation transitions and beyond (delegated to Ralph Swick and Philippe Le Hegaret)
• Evaluates formal objections (delegated to Ralph Swick and Philippe Le Hegaret)
• Confirms or denies Group decision in case of appeal
• May decline Group participation to an individual

Have an issue?

1. Get feedback from your team contact
2. If this is not enough, contact the associated Domain Lead
3. If this is not enough, contact the CEO and/or the Director

References

• W3C Process Document
• W3C Patent Policy
• Overview and Summary of W3C Patent Policy
• The Art of Consensus: Guidebook for the W3C Group Chairs
• Organize a Technical Report Transition
• Working Groups and Activities
• W3C Group Status and Participation

Feedback wanted

Help us make Chairs training relevant to you!

• Was this introduction useful?
• What's missing?
• Which part did you learn the most from?

Next sessions

2. Tools
   Ralph Swick
3. The Human Dimension
   Charles McCathie Nevile
4. Focusing the Working Group
   Arnaud Le Hors