to-do

To Do

This page is for posting microformats related shared to do items. If you want to use this page for your microformats related to-do items, create a section with your name on it. The reason we are keeping these all on the same page is to make it easier to tell when people are working on similar things, and to make it more obvious when people help out with other people's tasks. In theory this probably won't scale, but let's first see how it does in practice. :) - Tantek

Lazyweb

Just some nice things, feel free to do any of these.

for all microformats

• quick and easy "how to" pages for each microformat. use is a good overall start.
• brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
• write up mailing-list questions and answers in the appropriate faq pages.

hReview

• hReview support in Ecto (hey Adriaan!), requested by Andy Smith
• an hReview validator
• a semantic, clean css star rating picker (e.g. a UI widget to rate from 1-5 stars)
  • both this and this have some flaws. Ask Ryan King for an explanation.

hCard

• microformatted versions of conference pages
  • Do a revision of the ETel speaker's page with all the speakers marked up with hCard and links to "Add hCards to Address Book" etc., similar to the Web 2.0 speakers page which Tantek did a revision of last fall.
• vcard to hcard converter
  • would be nice to have a web upload UI that would take one or more vcards from apple's address book and give them back to you hcards
  • RobertBachmann suggests starting points:
    • For Ruby: http://vpim.rubyforge.org/
    • For C: http://freshmeat.net/projects/libvc/
    • For Python: http://www.nongnu.org/python-pdi/
    • For PHP: http://pear.php.net/package/Contact_Vcard_Parse/

hCalendar/hCard/hReview editor

• onblur in the URL field (e.g. on hCalendar), goes out and tries to retrieve an object of same time (e.g. an hCalendar vevent) from that URL and uses it to autofill the form, same thing if the creator is loaded with that URL prefilled (e.g. due to a ?url=http://example.com/ in the URL that loads the creator).

WordPress patches for microformats

• submit patches for WordPress code/templates for microformats improvement
  • <address class="vcard"> improvement in post author publication (e.g. home page of http://microformats.org/ )
• Wordpress plugin for microformats, specifically hReview and hCalendar
  • See lazyweb request

Yahoo Open Source Library Patches

Several of these could very much be improved with a little microformats markup. Do we just make patches and submit them? Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.

• Yahoo! User Interface Library
• Yahoo! Design Patterns Library
• Yahoo! User Interface Blog

Tantek

I'm keeping a few microformats related to-do items here both for my own convenience, and for folks looking to help out with small tasks. If so, just create a new section with your name, and and maybe copy the item there, and put your name next to the item in my list. We'll figure this out as we go along. Thanks, Tantek.

for all microformat specs

• sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: Authoring, Browsing, Converting, Indexing, Libraries (for developers), and Potential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.

See: hCalendar Implementations for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.

iterate on current microformats

hReview

• Write hReview 0.3 XMDP profile, and reconcile with hcalendar-profile and hcard-profile. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.

hCalendar

• need spec details and then hcalendar-examples of multi-instance hCalendar events
• need spec details and then hcalendar-examples of repeating events
• add explicit explanation and examples for LOCATION hCards and ATTENDEE hCards, perhaps on a separate hcalendar-examples page.
• need to resolve all outstanding hcalendar-issues to-do items.
• create hcalendar-profile and have folks verify it. note that it will likely need reconciliation with the hcard-profile, especially since hCalendar normatively depends on hCard. Probably makes sense to have a combined profile which hCalendar would use.

hCard

• hcard-examples
  • add examples of hCards with work telephone, mailing address etc.
  • add examples of marking up an organization vs. a person, then link to it from hCard spec section on Organization Contact Info.
  • add example of organization-name and organization-unit usage.
• more examples in the wild
  • help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx

introduction / community

• microformats-discuss
  • introductory email sent to new subscribers needs to direct people to process and how-to-play
• Need to add more to the naming-principles, to cover in particular:
  • avoid using the same name to mean two things
  • avoid using two names to mean the same thing
  • seek to keep the microformats vocabulary minimal, memorable, and usable.

profiles

• update XMDP with new required features:
  • ability for one profile to include/import another (rel="import" ?)
  • ability to reference an XMDP via rel="profile" (similar to XHTML2 rel value by same name)
  • ability/suggestion to reference an XMDP using <a href> in addition to <link>

microformat parsing documentation

• Add XPath equivalents where appropriate in hcard-parsing

create microformats wiki pages for

• microformats history
  • introduction of terms (when were microformats terms introduced, by whom, etc.)
  • introduction of specs (when were microformats specifications first introduced)
    • use the history on Technorati's developer wiki for evidence of earliest dates.
    • use the presentations as a source as well.

improve usability and automation on the site

• figure out how to get wordpress to autopost blog posts to the microformats-announce list
  • ideally use the from address of the author of the blog post
  • maybe photomatt knows how to do this.

help with microformat implementations

• hCard creator - add features/fields
  • email
  • aim / instant messaging contact info
• wordpress improvements
  • WP admin for new profiles
    • should simply read blog URL
    • look for hcards and parse them
• XFN Creator localizations
  • Get someone to verify the XFN Creator Russian localization.
  • Add it to the XFN Tools page.
  • Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.
• Conference Schedule Creator
  • We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make it *trivial* for conference organizers to build/edit/publish an hCalendar schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

help with new microformat requests

• expense reports (really just a list of "expense" items), requested by ED, should look at UBL as a pre-existing format
• photo-notes microformat
  • clean up Subethaedit notes from working session with Greg Elin, Ryan King, Kevin Marks, Suw Charman and email to folks and figure out next steps
  • iterate on photo-note-examples and start photo-note-formats and photo-note-brainstorming.

• Can we make "microformat" and "microformats" into Community Marks?

Ryan

hCalendar/hCard/hReview creator improvements

• get all creators working in IE/Win, IE/Mac, Safari/OSX.3

*-authoring microformats wiki pages

• Add some tips to hcard-authoring - a tutorial on creating an hCard for your site, blog (common platforms), etc.
• hcalendar-authoring - a tutorial on how to blog events so your friends can subscribe to them
• hreview-authoring - a tutorial on how to blog reviews so that they'll be aggregated.

other

• add an example of how to use DURATION in hcalendar see http://www.policyawareweb.org/2005/ftf2/paw-mtg#item15)

rel-payment

• update rel-payment to reference the IANA registry [1]

hcalendar

• make sure we explicitly disallow 'vjournal'

Dimitri Glazkov

• Figure out REST/Microformats thing
• Work on result set idea
• Implement h-creators using Web Forms 2.0

Chris Messina

• Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)
• Work on a microformat for play-item

Wishlist

• Microformat for "buyable items" (see listing-examples and related documents)
• Location MF -- right click "map this" (see geo and adr)
• Better hCard support in the browser -- right click "IM this person...", "Add to contacts"
• Better hCal support -- support many views of same hCal data on one page using XSLT

Robert Bachmann

• make hatom2atom.xsl conformant to hatom.

Brian Suda

Citation Microformats

Add all my notes to the Wiki

X2V

Make changes and update site (almost stable) Get ATTENDEE and other strange attributes working

Mark Rickerby

Current Tasks

• Follow up on usability review
  • Edits to homepage feature box text
  • Draft of getting-started page
• Review content for new pages - start-simple, modularity, reuse, humans-first
• xoxo datatype examples
  • test case lists
  • transmitting key/value lists
• practical feedback on hresume

Wishlist

• hmmm

Ernest Prabhakar

Wiki-Thon Proposal

Set aside several hours (probably a Friday night US PST) for focused work on the Wiki, including both physical (e.g., a room in the Bay Area) and virtual (IRC/iChat) participants.

Goals

1. Improve understanding of what needs to be done for Wiki
   • IMHO - this should be done here, in to-do incrementally. -Tantek
2. Tackle larger projects (~1-2 hours) than people usually have time for
   • I'd like to see these projects *documented* first on to-do before we spend 1-2 hours of a bunch of folk's collective time to go through them. -Tantek
3. Motivate community to have fun with otherwise tedious "housecleaning" chores

Agenda (Wishlist)

In parallel:

• Coalesce/prioritize existing To-Do items (above)
• Review/revise desired pathways for:
  • New users learning about microformats
    • e.g., intro, about, explore, tutorials, etc.
    • cf. Rails front page
      • Get Excited (Why, background, motivation)
      • Get Started (What, downloads, getting started)
      • Get Better (How, tutorials, )
      • Get Involved (Who)
  • Microformat lifecycle
    • e.g., research->brainstorm->proposal->spec->maintain
    • see http://theryanking.com/microformats/method.txt --RyanKing 15:35, 22 Feb 2006 (PST)
    • ensure information easy to find, follow, and up-to-date
• Review existing specs for completeness and consistency
• Identify areas of 'bitrot' or 'hole-filling'
• Do it!

New Person 2

etc.