Your SlideShare is downloading. ×
Standardization in W3C
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Standardization in W3C

917

Published on

Introduction of standardization methods in W3C. 오늘 TTA에서 진행된 국제표준전문가 교육과정에서 W3C에서의 표준화 활동 및 기고서 제출 방법 들에 대한 발표 자료입니다. W3C 표준화 활동에 관심있으신 분들은 참고하시길 바랍니다.

Introduction of standardization methods in W3C. 오늘 TTA에서 진행된 국제표준전문가 교육과정에서 W3C에서의 표준화 활동 및 기고서 제출 방법 들에 대한 발표 자료입니다. W3C 표준화 활동에 관심있으신 분들은 참고하시길 바랍니다.

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
917
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
11
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Standardization in W3C Jonghong Jeon ETRI, PEC Email: hollobit@etri.re.kr Blog: http://mobile2.tistory.com http://twitter.com/hollobit http://www.etri.re.kr
  • 2. 5 Agenda 1. Overview of Web Technology 2. Introduction to W3C 3. Standardization Process 4. Structure 5. Tools 6. Group Participation 7. Contribution 8. Conclusion
  • 3. 1. Overview of Web Technology
  • 4. 7 In The Beginning .....  World Wide Web (Tim Berners-Lee, 1989)  universe of network-accessible information  anyone, anywhere, anytime  Client to server interactions
  • 5. 8 Evolution of World Wide Web
  • 6. 9 Web Page vs. Web Application  Web Page(Site)  HTML로 표현된 웹 문서(또는 페이지들을 제공)  Web Application  특정한 기능을 수행하도록 설계된 프로그램
  • 7. 10 Evolution of World Wide Web  1단계 (1989~1999) : 웹사이트의 시대, HTML과 WAP  HTML, URL, HTTP 라는 세 가지 기술에 기초한 웹 기술이 제안되고, 보다 나은 인간 중심의 정보처리 및 지식공유 등을 목표로 하는 단계  2단계 (2000~2004) : XML과 웹서비스, 시맨틱 웹  XML(eXtensible Markup Language)에 기반하며 인간 중심의 정보 처리뿐 아 니라 다양한 디바이스와 서비스, 멀티미디어를 연결하는 것을 목표로 하는 단계  3단계 (2005~2009) : 웹 2.0, 웹 플랫폼 시대의 성장  구글, 아마존, 위키피디아 등의 성공과 함께 웹 산업을 제2의 전성기로 이 끌며 다양한 신규 서비스가 등장할 수 있는 기반을 마련  4단계 (2010~현재) : 웹 앱의 시대, 모바일과 N-Screen 시대  스마트 폰 및 태블릿 등 다양한 모바일 기기들을 대상으로 HTML5와 Web API를 통해 한 단계 진화된 웹 응용 환경을 제공하며, 위치정보 및 소셜 정 보 등을 결합하는 통합 응용 플랫폼으로서 웹이 자리잡아 가는 단계
  • 8. 11 Evolution of World Wide Web
  • 9. 12 Evolution of World Wide Web
  • 10. 2. Introduction to W3C
  • 11. 14 Welcome to W3C!  FPWD  First Public Working Draft  WD  Working Draft  LC  Last Call Working Draft  CR  Candidate Recommendation  PR  Proposed Recommendation  PER  Proposed Edited Recommendation  REC  Recommendation  AC  Advisory Committee  AB  Advisory Board  CFP  Call for Participation  WG  Working Group  CG  Community or Coordination Group  IG  Interest Group  PAG  Patent Advisory Group
  • 12. 15 Organizational Structure  Host  MIT , ERCIM , Keio University, and Beihang University  Offices  Australia Benelux/Bénélux Brasil Deutschland und Österreich España France India/भारत Italia Magyarország Sénégal Southern Africa Suomi Sverige United Kingdom and Ireland Ελλάδα Россия ‫ישראל‬ ‫المغرب‬ 中国 한국  ome key components of the organization are:  the Advisory Committee, composed of one representative from each W3C Member. The Advisory Committee has a number of review roles in the W3C Process, and they elect the Advisory Board and TAG.  the Advisory Board, an advisory body elected by the Advisory Committee  the Technical Architecture Group (TAG), which primarily seeks to document Web Architecture principles  the W3C Director and CEO, who assess consensus for W3C-wide decisions  the chartered groups, populated by Member representatives and invited experts, and which produce most of W3C's deliverables according to the steps of the W3C Process.
  • 13. 16 W3C Membership
  • 14. 17 People of W3C http://www.w3.org/People/
  • 15. 18 W3C Organization
  • 16. 19 How do W3C make Web Standards?  We get ideas through submissions, workshops, business groups, and community groups  Only W3C Working Groups are producing W3C Recommendations  Standard track: W3C Recommendation Track …as defined by the W3C Process.
  • 17. 20 From an idea to a Web standard
  • 18. 21 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
  • 19. 22 Group Types  http://www.w3.org/community/about/agreements/compare/
  • 20. 23 Community Groups  Started in 2011 to provide W3C umbrella for TECHNICAL conversations for things that MAY be submitted to Rec Track  Fast and easy to start, no fees involved, no Staff commitment, W3C Membership not required  To date there are 123 Community Groups  Several CGs have made contributions to Rec Track work and stay open to keep wokring on additional issues
  • 21. 24 CG Participation History  A history of Community and Business Groups participation:
  • 22. 25 CG Achievements  Did we help W3C create high quality, relevant standards?  16 Groups with reports  18 Final  25 Draft  3 CG Reports taken up by Working Groups:  JSON for Linking Data CG → RDF WG: JSON-LD Syntax 1.0, JSON-LD API 1.0  Responsive Images CG → HTML WG: the picture element  2 CGs proposed transition as new WG:  Core Mobile CG → Web and Mobile IG (under AC review)  Speech API CG → Web Speech WG (under AC review)
  • 23. 26 Business Groups  Started in 2011 to provide W3C umbrella for INDUSTRY conversations for things that MAY have Web Technologies as part of the answer  Fast and easy to start, Fees involved as more staff committed, no membership required  Currently there are 3 very active Business GroupsWeb Based Signage (44)  Web and Broadcasters (51)  Automotive and Web Platform (85)  Web Based Signage has made contributions to WGs  Web and Broadcasters interacts with Web & TV IG  Automotive and Web Platform is just getting started
  • 24. 27 Workshops  Long standing tool used by W3C to gather the industry to get as broad a view as possible on a topic  By invitation participation based on submission of a relative position paper  Some topics (Web & TV, Digital Publishing) require multiple Workshops in different regions to gather all requirements  Results of Workshop can vary depending on nature of conversation, participant awareness of W3C and clarity of requirements
  • 25. 28 Recent Workshops  W3C Workshop on Web Performance  Shift into High Gear on the Web: W3C Workshop on Web and Automotive  Do Not Track and Beyond  eBooks: Great Expectations for Web StandardsMaking the Multilingual Web Work  Open Data on the Web (23-24 April 2013)  Referencing and Applying WCAG 2.0 in Different Contexts (23 May 2013)  eBooks and i18n: Richer Internationalization for eBooks (4 June 2013)
  • 26. 29 Workshops  Workshop on Social Standards: The Future of Business (7-8 August 2013, San Francisco, USA)  RDF Validation Workshop - Practical Assurances for Quality RDF Data (10-11 September 2013, Cambridge, USA)  Publishing and the Open Web Platform (16-17 September 2013, Paris, France)  Get Smart: Smart Homes, Cars, Devices and the Web; W3C Workshop on Rich Multimodal Application Development (22-23 July 2013, New York Metropolitan Area, USA)
  • 27. 30 52 Working Groups  Each has:  One or more Chairs  One or more Team Contacts  A Charter developed with the W3C Members: scope, one or more deliverables, liaisons  Tools: Mailing list(s), teleconference(s), wiki(s), Version Control System(s), etc.  A Working Group MUST follow the W3C Process.
  • 28. 31 Advisory Groups  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)  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). Source: http://www.w3.org/2014/Talks/chairs-part4/
  • 29. 32 Role of Team Contacts and Chairs  Team Contacts  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)  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 Source: http://www.w3.org/2014/Talks/chairs-part4/
  • 30. 33 Role of Team Contacts and Chairs  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 Source: http://www.w3.org/2014/Talks/chairs-part4/
  • 31. 34 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 Source: http://www.w3.org/2014/Talks/chairs-part4/
  • 32. 3. Standardization Process
  • 33. 36 W3C standards == Recommendation
  • 34. 37 Document status
  • 35. 38 How to Read W3C Specs  Realize that W3C specifications are written for implementers, not end users.  Many specifications contain a section that tells how they are organized and how you should read them.  Know the vocabulary that specifications use.  Remember that you don’t have to read every word. Skim for the parts that make sense.  Avoid discussions of namespaces.  Learn to read BNF — it’s used in lots of places.  Learn to read a DTD for answers to syntax questions.  If a technology is scriptable, the information is in the bindings. Source: http://codedefect.com/ttwf-sz-belem/#/
  • 36. 39 W3C’s standard development  Initiation  Communication with External group  W3C Member submission  Formation  W3C Workshop  Group creation  Development  Document Drafting  Recommendation Track
  • 37. 40 W3C Recommendation Track http://www.w3.org/2005/10/Process-20051014/tr.html#rec-advance
  • 38. 41 W3C Recommendation Track
  • 39. 42 Change of W3C Recommendation Track
  • 40. 43 *PROPOSED* Rec Track
  • 41. 44 Example: HTML5 (aka "Plan 2014“)  Working Draft  22 January 2008  Last Call  3 August 2011  Candidate Recommendation  17 December 2012  Proposed Recommendation  2014 Q4  Recommendation  2014 Q4
  • 42. 45 W3C Patent Policy
  • 43. 46 [FYI] Why RF IPR – from IBM  RAND vs RF  1995-2003 – RAND!  2003- present – RF!  IBM leads the world in patents  Hard to change internal culture  SW & HW have diff cultures w.r.t. IPR  For SW…the key to shifting from RAND  RF  RF Standards  Bigger Markets  More $$  It’s a business decision! • If standard activity is strategic, default = RF  Glad to answer questions talk details later  https://www.w3.org/2005/Talks/IBM-W3C-PP.pdf Source: IBM
  • 44. 4. Structure
  • 45. 48 Interaction Domain  We shape the Web's user interface by enhancing the first- generation Web language, HTML, while developing second- generation Web languages: CSS, MathML, SVG, etc.  We integrate all those components together into the Rich Web Clients of tomorrow.
  • 46. 49 Interaction Domain  17 Working Groups, 6 Interest Groups, 1 Coordination Group
  • 47. 50 CSS WG  40 documents  Done: Colors, Selectors, Namespaces, Media Queries  High Priority: transitions, transforms, background/borders, animations  Joint work with SVG: transitions, transforms, animations, filter effects, compositing, masking/clipping  New: fullscreen, line grid, device adaptation, object model, regions, positioned layout, UI, selectors 4, masking/clipping  23 organizations (69 representatives), 4 invited experts  Bugs  Bugs: 29 transitions, 11 transforms, 45 animations  Tests: always need more of them…
  • 48. 51 WEB APPLICATIONS WG  33 documents  New: DOM Parsing and Serialization, File API: Directories, File API: Writer, Fullscreen, IM, Pointer Lock, Gamepad, Screen Lock, URL, Web Intents, Packaging.  Done: Widgets*  Stopped: Programmable HTTP Caching and Serving, Uniform Messaging Policy, Web SQL Database, XMLHttpRequest Level 1, XBL2  15 organizations (85 representatives), 1 invited expert  Bugs  Bugs: 3 CORS, 6 IndexedDB, 5 Sockets, 2 Storage, 2 Workers  Tests (Messaging, File API), test facilitators, test approval  See more on the dashboard
  • 49. 52 HTML WG  10 documents  HTML5  HTML+RDFa  HTML Microdata  HTML Canvas 2D Context  HTML: The Markup Language  HTML/XHTML Compatibility Authoring Guidelines  HTML5: Techniques for providing useful text alternatives  HTML5 diffs from HTML4  HTML to Platform Accessibility APIs Implementation Guide  HTML5: Edition for Web Authors
  • 50. 53 HTML WG  80 organizations (234 representatives), 259 invited experts  Bugs and Issues  Bugs: 177 HTML5, 5 Canvas, 4 HTML/RDFa, 7 Microdata, 16 Diffs, 4 Markup  21 issues before moving to LC#2 (3 on editors, 9 Chairs, 9 Group)  Next  Media source, media content protection  Canvas: integration of 2D Context and SVG  Web Intent, Web Component  Tests: parser and 2D Context  More during the HTML Update…
  • 51. 54 TESTING  Test Suites:  HTML5 tests  CSS tests  WebApps tests  http://w3c-test.org/  Test framework  Test authoring  More during testing session tomorrow…
  • 52. 55 Technology and Society Domain  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
  • 53. 56 Ubiquitous Web Domain  http://www.w3.org/UbiWeb/  Activities  Mobile Web Initiative Activity  Multimodal Interaction Activity  Ubiquitous Web Applications Activity  Voice Browser Activity  Web and TV Activity
  • 54. 57 Ubiquitous Web Domain  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
  • 55. 58 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
  • 56. 5. Tools
  • 57. 60 W3C Tools  Homepage  Public page, Member Page  Wiki  Mailing List  Tele-conference  IRC  Zakim  RRSagent, Trackbot  F2F Meeting  Bugzilla  Tracker  Other tools  Github
  • 58. 61 W3C Homepage  http://www.w3.org
  • 59. 62 IRC for Minutes and Chatter  Internet Relay Chat  To connect:  Get an IRC client or use irc.w3.org  Choose a nickname  Choose a channel name (and, if required, password).
  • 60. 63 IRC for Minutes and Chatter  http://www.w3.org/wiki/IRC
  • 61. 64 IRC for Minutes and Chatter  A scribe taking minutes  Can be helpful for people whose first language is not English.  People "lining up" to ask questions with q+  Other people making comments  By default, what you type becomes part of the meeting record  Unless you start with /me  IRC "bots" doing useful things (saving minutes to Web page, connecting to telephone bridge, managing speaker queue)
  • 62. 65 IRC - Zakim  http://www.w3.org/2001/12/zakim-irc-bot.html#agenda  The Zakim IRC "bot" is a Semantic Web agent ("swagent") that helps facilitate meetings using IRC in conjunction with the W3C's Zakim audio teleconference bridge.  Commands  /invite Zakim <channel>  Zakim,
  • 63. 66 IRC- rrsagent  http://www.w3.org/2002/03/RRSAgent  RRSAgent is a helpful bot for recording an IRC session. All text sent to the channel by any user is logged except '/me' text and text send with logging explicitly turned off.  Command  /invite RRSAgent <channel>  rrsagent, [please] excuse us  rrsagent, bye  rrsagent, [please] part  rrsagent, [please] leave  [rrsagent,] ACTION: <text>
  • 64. 67 IRC – trackbot  http://www.w3.org/2005/06/tracker/irc  Tracker also comes with trackbot, an IRC bot to Assist with creating actions during meetings (or other times). Over time, I expect trackbot will evolve to learn other things, but for now it's as simple as possible.  Command  /invite trackbot #channelname  trackbot, start meeting  trackbot, end meeting  issue-50  trackbot, ACTION-81?  resolution-12  ISSUE: Regular expression support needs a test suite  action eileen: Propose new language for pragma handling
  • 65. 68 Teleconference cheat sheet  Zakim is the teleconference bridge. The IRC bot helps with participant, agenda, and queue management,  RRSAgent records IRC discussion for later generation into minutes. It can trigger Scribe to generate minutes, and also does action tracking, though this has been superseded by Tracker.  Scribe generates formatted minutes from the raw log recorded by RRSAgent. It accepts many commands inline in the log. An online interface is available to generate minutes after the fact.  Tracker tracks issues and action items. Source: http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
  • 66. 69 Teleconference cheat sheet - Before  Step 1: Invite trackbot, Zakim and RRSAgent  trackbot, start telcon  Normally the above is all that is needed to get the teleconference going. The trackbot sets up the other bots with standard meeting information. if the above command doesn't work, it is necessary to set up the bots manually.  /invite Zakim #pf  /invite rrsagent #pf  Step 2: Set Meeting Info  rrsagent, set logs world-visible (for groups with open proceedings)  rrsagent, set logs member-visible (for member- confidential minutes)  scribe: ZakimName  ScribeNick: IRC_screen-name  meeting: @@@ Weekly Teleconference  chair: Real_Name  agenda: URI  Previous: URI (provides pointer to last minutes)  present: (names separated by commas)  regrets: (names separated by commas)  rrsagent, pointer? (gives location of IRC log)  zakim, Wrong_Name is Correct_Name  2.1 Manually Entering An Agenda  agenda: this  agenda+ First Agenda Item  agenda+ Second Agenda Item  agenda+ Third Agenda Item  repeat as necessary, then:  agenda+ be done  zakim, save agenda (after agenda entered) Source: http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
  • 67. 70 Teleconference cheat sheet – During  trackbot, status? (shows the users trackbot knows about; use this to find the TrackbotName for an individual on the call)  ACTION: TrackbotName to ActionText - DueDate  RESOLVED: (resolution text)  RESOLUTION: (resolution text)  zakim, Gregory_Rosmiata is Gregory_Rosmaita  zakim, mute me  zakim, unmute me  correction syntax: s/rosmiata/rosmaita/  note: correction syntax for the IRC tracker is a sub-set of sed  q+ (puts you in the speaker queue)  q- (remove yourself from the speaker queue)  q+ to ask ...  q+ to say ...  present+ Real_Name (to add late arrivals)  present- PhoneCode (to remove coded IDs)  regrets+ Real_Name for last minute regrets  rrsagent, pointer? (gives location of IRC log)  zakim, choose a victim (randomly assigns a task to a participant)  Switching Scribes:  ScribeNick+ IRC_nick  after-the- fact: i/Text_Where_Scribe_Changed/ScribeNick: IRC_name  rrsagent, drop action # (to drop a malformed action)  close ISSUE-# (how to close an issue from IRC)  close ACTION-# (how to close an action item from IRC)  trackbot, status? (shows the users trackbot knows about) Source: http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
  • 68. 71 Teleconference cheat sheet - After  Turn RRSAgent Logging Off  use the following command to turn RRSAgent's logging function off, so that any bot instructions or side chatter that follows the meeting's adjournment are not included in the meeting's log: • rrsagent, stop log  Creating Minutes:  rrsagent, create minutes  note: the following 5 commands are synonyms: • rrsagent, draft minutes • rrsagent, format minutes • rrsagent, generate minutes • rrsagent, make minutes • rrsagent, publish minutes Source: http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
  • 69. 72 DISMISSING ZAKIM AND RRSAGENT  1) zakim, please part (this will result in the output of attendees)  NOTE: non-staff members who are acting as scribe MUST effect any changes or corrections BEFORE dismissing RRSAgent; staff can edit slash manipulate minutes by appending a comma and the word tools to the URI for the minutes - for example:  http://www.w3.org/YYYY/MM/DD-IRC_Channel-minutes.html,tools  NOTE: the naming syntax for the automatically generated documents is:  http://www.w3.org/YYYY/MM/DD-IRC_Channel-minutes.html http://www.w3.org/YYYY/MM/DD-IRC_Channel-irc  2) after dismissing zakim, issue an "RRSAgent, draft minutes" command to ensure that the attendees list is correctly populated -- use the plus (+) and minus (-) syntax to add or delete attendees, regrets, etc. -- remember that you MUST issue an "RRSAgent, draft minutes" command in order for the bot to execute your instructions -- every time you do so, be sure to REFRESH the document in the browser instance in which you are reviewing the draft minutes  3) VERY LAST STEP: rrsagent, please part (logs actions and resolutions)  4) email HTML and IRC log pointers to w3c-wai-pf@w3.org. Including a text dump of the minutes is optional, although appreciated by many, and also needed for tracker to link issues referenced in the minutes. Source: http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
  • 70. 73 Mail & Mailing list  http://www.w3.org/Mail/  W3C hosts hundreds of mailing lists and archives, many of them public, for the benefit of the Web community at large. By providing this service, we hope to foster a highly responsive and interactive community for creating new ideas and advancing web technologies and culture.  Public Mail Archives  http://lists.w3.org/Archives/Public/  Member-restricted Mail Archives  https://lists.w3.org/Archives/Member/  Team-restricted
  • 71. 74 Event calendar  Public Event Calendar - http://www.w3.org/participate/eventscal.html  talks •  workshops •  group meetings •  membership meetings (AC, TPAC) •  regional events •  conferences endorsed by W3C  Member Event Calendar - https://www.w3.org/Member/Eventscal  group meetings •  advisory committee meetings •  technical plenary week (TPAC) •  conference discounts for members
  • 72. 75 F2F(Face to Face) meeting  http://www.w3.org/participate/meetings.html  Group Meeting  TPAC ("Technical Plenary / Advisory Committee")  During that week, a number of W3C Working, Interest, and Coordination Groups gather, network, and try to resolve challenging technical or social issues. This well-attended and popular week of meetings is an important means for W3C to coordinate solutions to technical issues that cross group borders. A "plenary session" with panels and other presentations brings all participants together; plenary meeting records are public. See past TPAC meetings.  Advisory Committee Meetings  AC meeting are Members-only meetings that focus on strategic issues facing the Consortium and future directions envisioned by the Membership and Staff. See past AC meetings (Member-only)
  • 73. 76 Attend meeting  WG Teleconference  WG F2F meeting  http://www.w3.org/Guide/hosting.htm  Preparing • Date / Location / Venue selection (who is host) • Facility check – network, projector, room, staffs … • Venue / Transportation guideline • Sponsored meals / dinner • Wiki set-up • Questionnaires (Attendee check)  Attend • Set up phone-bridge & zakim • Set up IRC channel
  • 74. 77 Wiki  http://www.w3.org/wiki/Main_Page
  • 75. 6. Group Participation
  • 76. 79 Group participants  Groups are composed of:  Member Representatives  Invited Experts  Team representatives  Must represent at most one organization  Are subject to W3C royalty-free licensing requirements
  • 77. 80 Group participants  Member representatives  Designated by Advisory Committee representatives  Are in general employed by the Member organization  Are under the Conflict of Interest Policy  May be declined participation by the W3C Director  Are subject to the royalty-free licensing requirements of their Member organization  Invited Experts  Invited by the Chair, due to particular expertise  Need agreement from the Chair and the Team Contact  May represent an organization (e.g. acting as a liaison)  Are subject to the Conflict of Interest Policy  Are required to provide a set of information  Team representatives  Composed of W3C paid staff, interns, and W3C Fellows  Are subject to the W3C Team Conflict of Interest Policy
  • 78. 81 WG Participation (Join/Disclose/Exclude)  http://www.w3.org/2004/01/pp-impl/  Live Statistics on W3C groups  Total unique number of participants: 1831  Total unique number of participants in good standing: 1805  Total number of Members with 1 or more individuals in good standing in a group: 254
  • 79. 82 WG Participation  List of Patent Disclosures and Exclusions Known to IPP  http://www.w3.org/2004/01/pp-impl/showPatents.php  Working Groups and Activities  https://www.w3.org/Member/Mail/  Information and Knowledge · Interaction · Technology & Society · Ubiquitous Web · Web Accessibility Initiative · TAG, AB · Member Communications  Working Group Tools Status Report  https://www.w3.org/2003/04/wg-report/  WBS: Web-Based Straw-poll and balloting system  https://www.w3.org/2002/09/wbs/showwb  DB-backed groups list (org)  https://www.w3.org/2000/09/dbwg/orgs
  • 80. 83 Social Coding  깃허브(GitHub, /'ɡɪtˌhʌb/[1])는 깃을 사용하는 프로젝트를 지원하는 웹 기반의 호스팅 서비스이다. 루비 온 레일스로 작성되었다. GitHub는 영리적인 서비스 와 오픈소스를 위한 무상 서비스를 모두 제공한다. 2009년의 Git 사용자 조사 에 따르면 GitHub는 가장 인기있는 Git 호스팅 사이트이다.[2]또한 2011년의 조 사에서는 가장 인기있는 오픈 소스 코드 저장소로 꼽혔다.[3]  https://github.com/w3c  https://github.com/sysapps  Features  Web Hosting  Project management  Social Coding  Issue Tracking
  • 81. 84 Github procedure
  • 82. 85 HTML5 process (with github)
  • 83. 86 W3C Bugzilla  https://www.w3.org/Bugs/Public/
  • 84. 87 Testing  Test The Web Forward  http://testthewebforward.org/  https://github.com/w3c/web-platform-tests  https://github.com/w3c/testtwf-website  Community-Driven & Industry-Supported  Open-Source & Standards-Based  Lean & Data-Driven  Centralized & Discoverable W3C's one stop shop for Open Web Platform testing.
  • 85. 7. Contribution
  • 86. 89 How can I make good contributions ?  History Taking  Spec version  Issues  Key player & company  Key staff (W3C team member)  WG’s culture  Collaboration  Contribution  Relationship  Chairs, editors, communities
  • 87. 90 W3C Contributions  Paper  Workshop Position paper  Group Proposal  Initial Draft Document  Contributions  Input Contribution  Change Request  Issue Raising  Issue resolving proposal  Bug report  Testing  Others  Wiki contribution
  • 88. 91 Case Study  Responsive Images  Community Group (2012.02) • http://www.w3.org/community/respimg/  Public Mailing list (2012.02) • http://lists.w3.org/Archives/Public/public-respimg/  Github (2012.10) • https://github.com/ResponsiveImagesCG/  Use Case (2012.10) • http://usecases.responsiveimages.org/  Specifications (2013.02) • Picture Element - http://picture.responsiveimages.org/ • Srcset attribute - http://www.w3.org/html/wg/drafts/srcset/w3c-srcset/  Implementation (2013.08) • WebKit Has Implemented srcset
  • 89. 8. Conclusion
  • 90. 93 The Art of Consensus (1/3)  This Guidebook is the collected wisdom of the W3C Group Chairs and other collaborators.  http://www.w3.org/Guide/  Starting a Group  Create a Charter (generator, horizontal review);  Join a group (see also Invited Expert Policy)  Edit w3.org using edit.w3.org, WebDAV, or (for experts) CVS  If you need a blog, wiki, mercurial repository, or mailing list, ask your staff contact.  ...more advice on roles in a group Source: http://www.w3.org/Guide/
  • 91. 94 The Art of Consensus (2/3)  Running a Group  Running a Meeting (especially a teleconference) on IRC (Web client): • Quick start guide for setting up tools for managing an agenda, generating minutes, and updating issues lists • Scheduling teleconferences • Scribe 101: Taking meeting minutes using W3C IRC tools • Individual IRC tools ("bots"): – Zakim for bridge management – RRSAgent for minutes management – Trackbot for issue management (using Tracker) during an IRC-based meeting  Predicting milestones  Face-to-face meetings • Send face-to-face meeting information to calreq@w3.org; that information appears on the events calendar • Host a face-to-face meeting • Policy Regarding Non-Disclosure Agreements and W3C Meetings  Issue tracking: • Tracker to track issues and action items through mail, IRC and the Web • Last Call comments tracker to track public comments on specifications and build a disposition of comments • DisCo, for creating a disposition of comments from tracker data. • Bugzilla for issues and bugs2html for disposition of comments via Bugzilla  WBS for questionnaires  Positive Work Environment [Draft] Code of Ethics and Professional Conduct (Member-only in draft form)  ...more advice on meetings, decisions, issue tracking Source: http://www.w3.org/Guide/
  • 92. 95 The Art of Consensus (3/3)  Specification Development  W3C Editors home page and specifically the Style for Group-internal Drafts  Transition requirements (for First Public Draft, Last Call, CR, PR, REC, etc.)  Pubrules (publication requirements) and links to related policies (e.g., namespaces, MIME type registration, and version management, in-place modifications)  See also Pubrules issue management / tracker  Normative References; what the Director looks at  Publications happen on Tuesdays and Thursdays (Member-only archive of announcement)  How to license definitions and bindings  Discussion about specifications on spec-prod@w3.org  ...more advice on specification development Source: http://www.w3.org/Guide/
  • 93. 96 Collected Wisdom, Advice  Roles  Chair's role; On Chairing a group (Member-only)  Editor's role (Member-only though could be made public)  Editor, Author, Contributor Policies  Staff Contact's role  Liaison's role. Note: Per section 10 of the Process Document, liaisons MUST be coordinated by the Team due to requirements for public communication; patent, copyright, and other IPR policies; confidentiality agreements; and mutual membership agreements.  Advice on Meetings, Decisions, Issue Tracking  "tracker" (an issue tracking tool)  ESW Wiki patterns: MidwestWeeklyAgenda, MeetingRecords, TrackingIssues  The Seven Sins of Deadly Meetings  Advice on Specification Development  W3C Manual of Style  W3C XML Specification DTD (XMLspec), by Norman Walsh.  ReSpec, by Robin Berjon.  Anolis, by GSnedders.  CSS postprocessor, by Bert Bos.  QA resources: Specification Guidelines, Handbook for QA in groups, and QA Framework primer  Tips for getting to Recommendation faster  Getting reviews • Contact the WAI PF Group for accessibility review • Contact the Web Security IG for security review • Contact the TAG for Web Architecture review • Tips on securing document reviews (Member-only)  Advice on Speaking, Promoting Your Work  HTML Slidy for slide presentations  How to Make Presentations Accessible to All Source: http://www.w3.org/Guide/
  • 94. 97 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
  • 95. 98 Open Web and Web Things
  • 96. 99 JongHong Jeon (hollobit@etri.re.kr) +82-42-860-5333 http://mobile2.tistory.com/m http://twitter.com/hollobit

×