1. Open Standards Stories & Practices

    Tantek Çelik, Mozilla Web Standards Lead tantek.com • @t

  2. Open Standards Stories & Practices

    1. CSS 2.1
    2. XFN
    3. microformats
    4. HTML5
    5. W3C Community Groups

  3. 1. CSS 2.1

  4. 1998

  5. CSS 2 Proposed Recommendation

    CSS 2 Proposed Recommendation

  6. joined W3C
    CSS working group

  7. learned to love
    the open web

  8. open free specs
    e.g. IETF & W3C

  9. contrast:
    ISO pay to view

  10. open free test suites
    e.g. W3C

  11. contrast:
    CalConnect pay to test

  12. valid test suites
    e.g. CSS WG

  13. contrast: invalid
    most 2004 W3C tests

  14. open verifiable
    CSS WG test reports

  15. contrast: secret
    CalConnect paid reports

  16. science:
    open reproducibility

  17. 2007

  18. designers frustration:
    CSSWG not open enough

  19. CSSWG opened up

  20. started a blog

  21. public readable wiki

  22. public readable wiki

    public readable CSSWG wiki

  23. closed to open:
    issues tracking

  24. closed to open:
    irc logs

  25. closed to open:
    email list

  26. closed to open:
    editor drafts

  27. meanwhile: CSS 2.1

  28. multiple last calls

  29. 2011

  30. CSS 2.1 Recommendation

    CSS 2.1 Recommendation

  31. took ~9 years

  32. many lessons learned

  33. solid foundation
    for CSS3 modules

  34. key lesson:
    openness evolves

  35. 2. XFN

  36. 2003

  37. SXSW

  38. rel=friend

  39. ultra-minimal

  40. 9 months: research & experimentation

  41. study:
    real web sites

  42. study:
    what do people do?

  43. instead of:
    what might people do

  44. science:
    empirical evidence

  45. XFN 1.0

    XFN 1.0

  46. Creative Commons (CC)
    open license

  47. open source adoption

  48. 2004

  49. XFN added:
    contact, kin, me

  50. XFN 1.1

  51. rel=me

  52. 2012

  53. most supported:
    me, contact

  54. future:
    rel-me + OAuth

  55. key lesson:
    simplify, simplify

  56. 3. microformats

  57. 2004

  58. O'Reilly Emerging Technologies

  59. rel=license
    "microformat"

  60. edited publicly on
    Technorati dev wiki

  61. also open licensed:
    Creative Commons

  62. Foo Camp

  63. HTML for
    people & events

  64. web designer behavior:
    semantic class names

  65. existing vocabularies? vCard & iCalendar

  66. hCard & hCalendar

  67. re-use behavior:
    greater adoption

  68. re-use vocabularies:
    quick interoperability

  69. 2005

  70. no web review formats

  71. research web reviews

  72. 80/20 rule

  73. hReview
    microformat

  74. empirical design:
    quick adoption

  75. 2005-06-20

  76. microformats.org launch!

  77. microformats.org

    microformats.org

  78. microformats process

  79. open IRC & email

  80. public logs & archives

  81. wiki is official
    over email

  82. wiki edits to IRC

  83. 17 translations!

  84. 17 translations!

    17 translations on home page

  85. microformats.org/wiki/Main_Page-ja

    microformats.org wiki Main_Page Japanese

  86. 2007

  87. public domain / CC0

  88. 2009

  89. microformats 2 started

  90. even simpler
    microformats

  91. key lesson:
    open community

  92. 4. HTML5

  93. 2004

  94. W3C Workshop on
    Web Applications

    W3C Workshop on Web Applications

  95. HTML + CSS + DOM vs.
    XHTML2 + XForms + etc.

  96. HTML vs. XML

  97. incremental vs replace

  98. HTML lost: 8-11

  99. HTML lost: 8-11

    HTML lost: 8-11

  100. Great Web Schism

  101. WHATWG launch

  102. WHATWG launch

    WHATWG

  103. Web Applications spec

  104. became HTML5

  105. and split off more specs

  106. core + new APIs

  107. WHATWG uses:
    MIT License

  108. contrast W3C:
    non-forking license

  109. both WHATWG & W3C:
    use-cases, evidence

  110. <time> element

  111. 1 year of evidence
    on WHATWG wiki

  112. Time element on WHATWG wiki

    Time element on WHATWG wiki

  113. debate at W3C
    HTML WG meeting

  114. resolved in WHATWG:
    one week

  115. W3C consensus:
    still working on it

  116. trust editor
    vs. consensus

  117. key lesson:
    finding balance

  118. 5. W3C CGs
    (Community Groups)

  119. 2011

  120. W3C CGs launch

  121. W3C CGs

    W3C CGs

  122. need only 4 people
    to start a CG

  123. new CG license:
    open, permissive

  124. permits CC0 & OWFa
    standard licenses

  125. Mozilla approves:
    CC0 & OWFa for specs

  126. key lesson:
    big can evolve

  127. Conclusion:
    10 best practices

  128. 1. create openly

  129. 2. iterate openly

  130. 3. use an open wiki

  131. 4. discuss openly

  132. 5. open email & IRC

  133. 6. open archives & logs

  134. 7. wiki edits to IRC

  135. 8. open test suites

  136. 9. open test reports

  137. 10. broader community

  138. Thank you.

    Tantek Çelik

    tantek.com • @t