From Microformats Wiki
Jump to navigation Jump to search

Outline for d.Construct 2007 microformats workshop

Here is a rough outline of the structure of the 2007-09-05-dconstruct-microformats-workshop, one of several microformats events

  1. Background
    1. Semantic markup (Tantek)
      1. Web History 1990s
      2. 2000-2001
      3. 2002-2003: Wired News redesign, CSS tipping point, semantic (X)HTML grows
    2. Questions?
  2. POSH
    1. Lesser known markup (Jeremy)
      1. Examples
        1. thead, tbody, summary?
        2. optgroup?
        3. del, ins?
        4. cite attribute?
        5. rel attribute
    2. Questions?
  3. Elemental microformats
    1. rel-license (Tantek)
    2. XFN (Jeremy)
    3. rel-tag (Tantek)
    4. vote-links (Jeremy)
    5. Questions?
  4. Building blocks
    1. The class design pattern (Tantek)
      1. not just for CSS
    2. The abbr design pattern (Jeremy)
      1. datetime
      2. geo
      3. accessibility concerns
    3. Questions?
  5. hCard
    1. background (Tantek)
    2. implementation (Jeremy)
    3. example sites
    4. Questions?
  6. hCalendar
    1. background (Tantek)
    2. implementation (Jeremy)
    3. example sites
    4. Questions?
  7. Exercises
    1. spot the contact and event info
    2. fill in the blanks
    3. Questions?
  8. Compound microformats
    1. hResume (Tantek)
    2. hReview (Jeremy)
    3. hAtom (Tantek)
    4. Questions?
  9. Case study
    1. Yahoo! Europe (Norm!)
    2. Questions?
  10. Philosophy
    1. Scientific method: gather data before forming hypotheses (Tantek)
      1. what information are humans already publishing?
      2. the specific reasons are irrelevant, the 'existence' of the behavior matters
      3. use only information published visibly, it tends to be more accurate than that published invisibly
    2. Progressive problem solving (Jeremy)
      1. solve simple problems before complex problems - simple solutions will often act as building blocks for complex problems, and illuminate how to more easily solve them
      2. solve the most common problems first. by developing ways of sharing the most commonly published/used information types first, more use cases, applications, scenarios will be enabled faster
      3. if only one person seems interested in a problem, it's probably not yet worth the attention of the community
    3. Reusing vocabularies helps communication (Tantek)
      1. reuse rather than reinvent (vocabulary reinvention is a common (e.g. XML) standards mistake = babel)
      2. reuse from existing well implemented interoperable standards
      3. vcard to hcard
      4. icalendar to hcalendar
    4. The Pareto principle (Jeremy)
      1. 80/20
      2. Humans first, machines second
    5. Questions?
  11. Extracting microformats
    1. Operator (Tantek)
    2. Bookmarklet, Bluetooth (Jeremy)
    3. Parsing (Brian)
    4. Questions?
  12. Data Portability
    1. being able to move your data thru time and space
    2. note additional data portability points from Tantek's 2005-09 Web Essentials preso on microformats
    3. most recent high profile example of data portability: social networks
  13. Social Network Portability
    1. problem statement: having to re-enter profile info, re-add friends
    2. solution: your data should be published/shared with microformats
    3. profile info: use hCard
    4. link to your home page: use XFN rel="me" for identity consolidation / URL claiming
    5. friends lists: hCard for names/links to friends + XFN for relationships
    6. view all friends / paginating friends: use XFN rel="me" to consolidate friends lists into profile URL
    7. supported by sites today (show names/logos)
    8. how to support open user profiles with hCard
    9. how to support open friends lists with hCard+XFN
    10. how to import/subscribe to an open user profile (e.g. Satisfaction, hKit)
    11. how to import/subscribe to an open friends list (e.g. Dopplr)
    12. Backnetwork example (Glenn?)
  14. The future
    1. More microformats?
    2. More parsers
      1. Firefox 3
    3. More implementations
      1. Google maps
    4. Questions?
  15. General Q&A - possible Q&A topics:
    1. Why not XML/RDF?
    2. Creating microformats
      1. The process (Tantek)
        1. first make sure your site is POSH
        2. second make sure your site uses existing microformats in known ways
        3. solve a specific problem
        4. try using existing microformats for your new problem
        5. document existing publishing behaviors of your type of information
      2. Proposals (Jeremy)
      3. Community (Tantek)
        1. wiki
        2. IRC
        3. mailing list
      4. Questions?