To Do

(Difference between revisions)

Jump to: navigation, search
m (Tantek)
Current revision (00:53, 31 December 2018) (view source)
(Website Improvements: yes we should have HTTPS - moving to admin-to-do)
 
(198 intermediate revisions not shown.)
Line 1: Line 1:
-
<h1>To Do</h1>
+
<entry-title>To Do</entry-title>
-
 
+
__TOC__
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. :) - [http://tantek.com Tantek]
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. :) - [http://tantek.com Tantek]
-
__TOC__
+
== microformats2 updates ==
 +
The following pages need to be updated to for microformats2 (typically code, examples, and any specific format advice)
 +
* [[what-are-microformats]]
 +
* [[introduction]]
 +
* [[get-started]]
 +
* [[faq]]
 +
* [[hcard-authoring]] -> [[h-card-authoring]]
 +
* [[hcard-examples]] -> [[h-card-examples]]
 +
* [[advocacy]]
 +
* ...
 +
 
 +
== wiki gardening ==
 +
 
 +
=== trim fixups ===
 +
Search for all uses of "tr.im" for shortlinks and replace them with "ufs.cc/w/" links that just use the pagename.
 +
 
 +
* [http://www.google.com/search?q=site%3Amicroformats.org+tr.im Google search for site:microformats.org tr.im]
 +
 
 +
In particular, let's document old tr.im links and (unlinked) and where they used to link to so that if someone *searches* for tr.im URLs to figure out what happened to them, there's a chance they'll find the equivalent.
 +
 
 +
* [[tr.im]]
 +
 
 +
=== simplify pages ===
 +
Review pages, from the [[Main Page]] on down and:
 +
 
 +
* Simplify/minimize the content in the pages with direct writing, assuming an eager(impatient,positive) reader in the primary reading flow.
 +
* Move (keep) clarifications/details/documentation for edge case people (i.e. deliberate misinterpreters, sarcastic skeptics, pedants etc.) to details further down in a page (or on subpages) rather than in the primary reading flow.
 +
 
 +
Examples of simplified pages:
 +
* [[Main Page]] - simplified quite a bit (2012-04-02), but could probably use additional simplification
 +
* ...
 +
 
 +
Pages to simplify:
 +
* [[how-to-play]] (should probably be done by an admin, but left here in case someone wants to try drafting a revision on another page and have an admin review it)
 +
* pages listed in [[stable-pages]] (simplifying these first will help with better translations)
 +
** for specifications, please work with their editor(s) on non-trivial content copy edits.
 +
 
 +
=== remove broken URLs ===
 +
 
 +
There's lots of links to sites that are now gone (see [http://indiewebcamp.com/site-deaths site-deaths] on IWC for a full list).
 +
 
 +
It'd be useful if we replaced them where possible with links to archive.org or equivalent.
 +
 
 +
TODO (mark as done when done):
 +
 
 +
* [[Upcoming]]
 +
* code.google.com
 +
 
 +
=== incorporate things expected to break ===
 +
==== shortlink spec ====
 +
The rel=shortlink spec:
 +
* https://code.google.com/p/shortlink/wiki/Specification
 +
is going to die soon as part of Google Code's shutdown.
 +
 
 +
1. We should copy that spec (along with FAQ for the first few valid questions/comments) to [[rel-shortlink]], moving existing contents there to supplementary pages or purely historical record.
 +
 +
2. Get http://purl.org/net/shortlink to redirect to [[rel-shortlink]] instead.
 +
 
 +
 
 +
== more documentation and research ==
 +
=== extract from 1989 timbl proposal ===
 +
* extra all specific problems and use-cases mentioned in http://www.w3.org/History/1989/proposal.html
 +
* write them up as their own wiki pages, one per specific problem/use-case
 +
* see if they're solvable with modern [[microformats2]]
 +
 
-
== Lazyweb ==
+
== microformats specific ==
Just some nice things, feel free to do any of these.
Just some nice things, feel free to do any of these.
=== for all microformats ===
=== for all microformats ===
-
* We have recently added a new mailing list called microformats-new.  There may be some confusion surrounding this change, so it would be helpful to:
+
* quick and easy "how to" pages for each microformat. [[get-started]] is a good overall start.
-
** Draft a message to be added to the confirm message sent when someone subscribes to any list including a welcome message, ground rules, topic for the subscribed list, and the topics for nearby lists.
+
-
** Add a faq entry somewhere on why the new list was created.
+
-
** Double check the wiki pages to make sure advice on mailing lists is accurate.
+
-
* 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.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators.  See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* validators.  See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
-
* Add [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to Microformats Blog.
+
* Submit definitions of "microformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]
-
* Submit definitions of "mcroformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]
+
* it would be nice to replace the -in-the-wild pages with a form that accepted URL entries that would both register the site and look for valid microformatted content and for those pages with problems, would set them aside in a queue to be reviewed by the community. Having such an interface would likely be more efficient for implementors looking to have their work reviewed, and would also add to a ready-database of microformats in the wild -- which would be a great way to feed pingerati.com. [[User:Chris_Messina Chris Messina]] on 2007 Aug 31.
 +
* check with the group and then, assuming this is accepted, remove mention of the profile="" attribute from the wiki, since HTML5 removes the need for profiles to be declared
=== hCard ===
=== hCard ===
Line 31: Line 92:
*** For Python: http://www.nongnu.org/python-pdi/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
 +
** I (Andy Pemberton) started working on this at one point, but haven't touched it in a while: [http://www.andypemberton.com/sandbox/hcardconvert/ vCard-2-hCard]
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])
 +
* more test cases - add to [[hcard-examples]] to begin with, then hopefully create test cases for development to be checked in with mercurial to the repository
 +
** include class="type" without explicit value test cases, based on [[hcard#type_with_unspecified_value|hCard type with unspecified value]].
=== hCalendar ===
=== hCalendar ===
Line 51: Line 115:
=== hCalendar/hCard/hReview editor ===
=== 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).
* 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).
 +
 +
=== hAtom ===
 +
* [[hatom-issues]] needs sections for closed issues, resolved issues, and open issues sorted by year, similar to [[hcard-issues]].
=== WordPress patches for microformats ===
=== WordPress patches for microformats ===
Line 73: Line 140:
===rel-tagging on Wikipedia===
===rel-tagging on Wikipedia===
Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)
Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)
 +
 +
===Glossary===
 +
Add to the [[glossary]].
 +
 +
===hAtom tutorial===
 +
Finish the [[hatom-tutorial]].
 +
 +
=== wiki gardening ===
 +
* Find [[:Special:Lonelypages|orphaned]] pages, and add links to them.
 +
* Use [[templates]] for boilerplate text and repeated lists of links
 +
* Add keywords to the foot of pages (see [[vcard-suggestions]] for examples), so that they can be converted to tags, once this wiki allows the use of "rel" attributes. Keywords can also include synonyms to aid searching.
 +
 +
====Spelling====
 +
Per [[how-to-play]]: for English-language pages only: Find British spellings of common words and replace them with the US spellings per [[en-US]]. Mark such edits as "minor" with the comment: <nowiki>[[en-US]]</nowiki>. Please be careful to use and maintain proper native spelling of proper nouns (see [[how-to-play]] for details).
 +
 +
Here is a table of searches for some of the British-English spellings that have crept into English-language microformats wiki pages, along with their respective US-English spellings. If you find other British spellings, please feel free to add them to this table, with their US equivalent.
 +
 +
{| border="1"
 +
|+
 +
! [[en-GB]] !! [[en-US]]
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=behaviour&go=Go behaviour] || behavior
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=behaviours&go=Go behaviours] || behaviors
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=centre&go=Go centre] || center
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=colour&go=Go colour] || color
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=colours&go=Go colours] || colors
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=favour&go=Go favour] || favor
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=flavour&go=Go flavour] || flavor
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=flavours&go=Go flavours] || flavors
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=flavoured&go=Go flavoured] || flavored
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=minimise&go=Go minimise] || minimize
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=minimises&go=Go minimises] || minimizes
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=recognise&go=Go recognise] || recognize
 +
|-
 +
| [http://microformats.org/wiki/Special:Search?search=recognised&go=Go recognised] || recognized
 +
|-
 +
|}
 +
 +
[http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences More American and British English spelling differences]
 +
 +
== Admins ==
 +
This section is for folks to suggest to-do items for [[admins]], in particular, having to do with suggestions for improvements to microformats.org infrastructure such as the wiki. If you do add an item to this list, please sign your username with four tildes: <nowiki>~~~~</nowiki>.
 +
 +
Admins check this "inbox" periodically and process and move items to [[admin-to-do]].
 +
 +
Please check [[admin-to-do]] to see if there is already an ongoing task item relating to your request. Otherwise add the item below.
 +
 +
=== Website Improvements ===
 +
* ...
 +
 +
=== Wiki improvements ===
 +
 +
* Want: Right-to-left (RTL) support in the theme for better translating to RTL languages. Per [https://www.facebook.com/permalink.php?story_fbid=10150109554926465&id=214611 this comment on the microformats page on Facebook 2011-02-13]: <blockquote><cite>Sina Cheraghi</cite> &gt; Microformats <br> "I want to contribute in Microformats wiki by translating it into Persian. But lack of RTL (right-to-left) languages (Persian, Arabic, Hebrew and ...) theme causes some problems for me and other contributors."</blockquote>
 +
 +
* Make email addresses editable [[User:Singpolyma|Singpolyma]] 02:47, 26 July 2009 (UTC)
 +
** How would this work and what's the purpose? [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)
== Tantek ==
== 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,  [http://tantek.com Tantek].
+
I'm keeping microformats related to-do items here both for my own convenience, and for folks looking to help out. - [http://tantek.com Tantek].
=== overall priority ordering ===
=== overall priority ordering ===
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
-
# Help publishers with established microformats: [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
+
# Update [[microformats2-parsing]] with resolved [[microformats2-parsing-issues]]
# Help implementers with established microformats
# Help implementers with established microformats
# Iterate on existing established microformats, resolve issues/feedback etc.
# Iterate on existing established microformats, resolve issues/feedback etc.
Line 85: Line 219:
# Site usability of microformats.org top-down as an entry point
# Site usability of microformats.org top-down as an entry point
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments
-
# Emerging in-demand microformats: [[hresume|hResume]], [[hlisting|hListing]], [[citation]], [[media-info]] using abovementioned process and principles improvements.
+
# Wrap up classic microformats documentation
-
# New microformat requests
+
# Document microformats [[history]].
# Document microformats [[history]].
# Other
# Other
Line 92: Line 225:
=== protect the community ===
=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
-
** add to [[mailing-lists]] policies/guidelines accordingly.
+
** add to [[mailing-lists]] and [[how-to-play]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.
 +
** move exploratory discussions which are failing to follow the process to a separate page from that
 +
** repair damage done to the wiki
 +
*** identify damage done to the wiki - often in forms as simple as content changes that hurt usability (and thus accessibility)
 +
*** document additional [[how-to-play]] guidelines to discourage and hopefully reduce such wiki damaging behavior in the future
 +
*** repair/undo/reorganize page section division that hurt usability (and thus accessibility)
 +
**** [[hcalendar-examples-in-wild]]
 +
***** afterwards add some of the excellent conference schedule calendars that [[User:Adactio]] has been creating like:
 +
****** http://adactio.com/extras/schedules/barcampbrighton3/
 +
*** repair/undo/reorganize page splitting that hurt usability (and thus accessibility)
 +
**** [[to-do]]
-
=== help publishers ===
+
=== update microformats2-parsing with resolved issues ===
-
==== foldup cheatsheet ===
+
Update [[microformats2-parsing]] with resolved [[microformats2-parsing-issues]]
-
'''Next actions''': review all descriptions, property lists, examples in Erin's cheatsheet draft, give feedback back to Erin about her foldup cheatsheet, iterate, print, fold, distribute.
+
-
Help create a printable foldup cheatsheet of multiple microformats (ASAP, perhaps for [[events/2007-04-18-web-2-expo-dinner|Web 2.0 Expo Microformats dinner]]) that:
+
=== help implementers ===
-
* prints onto both sides of a sheet of 8.5x11" paper (size chosen for US distribution, and because it folds nicely into 4ths sliced vertically, then 3rds sliced horizontally into a size approximating a business card, hoping to CC-by the whole thing so that others can do their own variants, perhaps for other paper sizes also)
+
Update all these tasks for [[microformats2]]:
-
* accordion folds first into 1/4 size along 3 vertical creases, then 1/3 size along 2 horizontal creases
+
-
* on each of the 8 vertical stripes (4 one side, 4 the other) of the sheet, info on each of the following microformats (it is assumed that [[hcard|hCard]] documentation will cover [[adr]], and [[geo]] also).
+
-
** people vs. other things
+
-
*** people-centric:
+
-
**** [[xfn|XFN]]
+
-
**** [[hcard|hCard]]([[adr]],[[geo]])
+
-
**** [[hcalendar|hCalendar]]
+
-
**** [[hresume|hResume]] + [[include-pattern]]
+
-
*** content-centric:
+
-
**** [[microformats]] list/overview
+
-
**** other common rels: [[rel-license]] [[rel-enclosure]] [[rel-tag]] [[rel-directory]]
+
-
**** [[hreview|hReview]] + [[xfolk|xFolk]]
+
-
**** [[hatom|hAtom]]
+
-
** original building blocks vs. newer
+
-
*** original:
+
-
**** [[microformats]] list/overview [[rel-license]] [[rel-tag]]
+
-
**** [[xfn|XFN]]
+
-
**** [[hcard|hCard]]([[adr]],[[geo]])
+
-
**** [[hcalendar|hCalendar]]
+
-
*** newer:
+
-
**** [[hreview|hReview]] + [[xfolk|xFolk]]
+
-
**** [[rel-directory]] [[rel-enclosure]]
+
-
**** [[hatom|hAtom]]
+
-
**** [[hresume|hResume]] + [[include-pattern]]
+
-
** other splits of 4 slices vs. 4 slices?
+
-
*** ...
+
-
*** ...
+
-
* each triple accordion fold section for a microformat should contain:
+
-
** property summary with required/optional singular/plural sub-properties (similar to current cheat sheet) + illustrative code sample with common properties
+
-
** list of properties, sub-properties with values and definitions of each
+
-
** URLs to spec, examples, implementations for more info.
+
-
Update: I made a folding cheat sheet to similar specifications.  Not sure if it's 100% correct, it needs to be looked at for needed revisions. [http://erincaton.ca/media/cheatsheetHandout.pdf Cheat sheet PDF.] [[User:ErinCaton|ErinCaton]]
 
-
 
-
Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)
 
-
 
-
==== *-authoring microformats wiki pages ====
 
-
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
 
-
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
 
-
** instructions for all other hCard properties
 
-
** a tutorial on creating an hCard for your site
 
-
*** specific instructions for common blogging platforms
 
-
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
 
-
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.
 
-
 
-
* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.
 
-
 
-
* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].
 
-
 
-
* *-authoring for other reasonably well established microformats:
 
-
** [[xfolk-authoring]], [[hatom-authoring]]
 
-
 
-
==== help with microformat examples in the wild ====
 
-
Using the above updated [[authoring]] pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity [[hcalendar|hCalendar]] and [[hcard|hCard]] etc.  Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. [[flickr]], [[upcoming]], [[eventful]] etc.) Document any exceptions as needed.  In no particular order:
 
-
* Flickr.com (3.5m hCards)
 
-
* Upcoming.org (100k hCalendar events, 100k hCard venues)
 
-
** home page
 
-
* Eventful.com (100k hCalendar events, 100k hCard venues)
 
-
* Yahoo! Tech (300k products with hReviews)
 
-
* JudysBook.com (???k hReviews)
 
-
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.
 
-
 
-
==== advocacy for obvious sites ====
 
-
* [[advocacy]] - add pages/sites that obviously (no pun intended) could use microformats, update them with sample markup, find contacts for those pages to get them updated, and send requests to update their sites with microformats including sample markup. '''next-actions''': markup both twitter.com sample pages and dodgeball.com sample pages, post the changes publicly, and see which one is able to update first ;)
 
-
** dodgeball.com (hCard + XFN + hAtom for profiles, hCard + hReview for venues)
 
-
** write essay on [[open-data-more-important-than-open-source]] - and a shorthand URL too.
 
-
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open source.
 
-
*** open data &gt; open source
 
-
*** "open information" vs "open source"
 
-
*** i.e. please focus first on open data rather than open source, e.g. start with [[hcard|hCards]] for all organizations returned from http://wiserearth.org/organization
 
-
*** if the data is open you can always export it and consume it in any number of open source systems
 
-
*** that's why open data is MUCH more important than open source
 
-
*** adding open data (e.g. microformats) can be done by any HTML author (yes, you), whereas open sourcing requires programming expertise, resouces, support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.
 
-
*** if the data was open, anyone could rebuild an accessible version
 
-
*** faqs / misconceptions:
 
-
**** eschipul: @tantek - creating microformats is easier. consuming microformats is unfortunately not easier.
 
-
***** A: If you think consuming microformats is not easier or hard etc., it may just be that you don't know how to do so easily, don't assume that you are an expert in something that you think is hard.  Rather, if you think something is hard, then assume others may know easier methods, and ''ask''  the community how one can do it more easily.  parsing in particular is something which is becoming easier and easier thanks to open source libraries like [[hkit|hKit]].
 
-
** write essay on [[open-data-more-important-than-open-apis]] - and a shorthand URL too
 
-
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open APIs.
 
-
*** publishing/providing open data (e.g. microformats) can be done by any HTML author (yes, you), whereas providing/publishing open APIs requires programming expertise, resouces, and support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.
 
-
 
-
=== help implementers ===
 
* wordpress improvements
* wordpress improvements
** WP admin for new profiles
** WP admin for new profiles
*** should simply read blog URL - '''next-action''': make sure a bug/feature request is filed with wordpress.org
*** should simply read blog URL - '''next-action''': make sure a bug/feature request is filed with wordpress.org
-
*** look for hcards and parse them
+
*** look for hCards and parse them
* [http://gmpg.org/xfn/creator XFN Creator] localizations
* [http://gmpg.org/xfn/creator XFN Creator] localizations
Line 200: Line 261:
*** Makes it *trivial* for conference organizers to build/edit/publish an [[hcalendar|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.
*** Makes it *trivial* for conference organizers to build/edit/publish an [[hcalendar|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.
-
=== iterate on current microformats ===
+
=== wiki cleanup ===
-
==== [[hcard|hCard]] ====
+
Update all these tasks for [[microformats2]]:
-
* [[hcard-examples]] '''next-actions''': update with examples described below
+
-
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
+
-
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
+
-
** add example of organization-name and organization-unit usage.
+
-
* [[hcard-issues]] and [[hcard-feedback]].  '''next-actions''': resolve all issues and incorporate all feedback.
+
-
* [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve in April, and which later
+
-
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
+
-
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
+
-
* [[hcard-examples-in-wild]]
+
-
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx
+
-
 
+
-
==== [[hcalendar|hCalendar]] ====
+
-
'''Next-actions''':
+
-
* itemize a list of properties similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list.
+
-
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
+
-
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like
+
-
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
+
-
* need spec details and then [[hcalendar-examples]] of repeating events
+
-
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|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|hCalendar]] normatively depends on [[hcard|hCard]].  Probably makes sense to have a combined profile which hCalendar would use.
+
-
 
+
-
==== [[hreview|hReview]] ====
+
-
'''Next-actions''':
+
-
* 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.
+
-
* Resolve all outstanding [[hreview-issues]] and [[hreview-feedback]] to-do items.
+
-
 
+
-
==== [[rel-tag]] ====
+
-
'''Next-actions''':
+
-
* Write [[rel-tag]] XMDP profile ([[rel-tag-profile]]) and send to [http://dbaron.org/ David Baron].
+
-
* Resolve all outstanding [[rel-tag-issues]] and [[rel-tag-feedback]] to-do items.
+
-
 
+
-
==== summary Examples in the Wild page ====
+
-
* need to create a summary / overall [[examples-in-the-wild]] page
+
-
** parallel the summary/overall [[implementations]] page.
+
-
** use newly reoganized content from the above "reoganizing Examples in the Wild" task
+
-
==== parsing ====
 
-
'''Next-actions''':
 
-
* Draft *-parsing for all reasonably well adopted microformats: [[hcalendar-parsing]], [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]
 
-
 
-
=== wiki cleanup ===
 
==== for all microformat specs ====
==== for all microformat specs ====
'''Next-actions''':
'''Next-actions''':
Line 253: Line 273:
==== update specification section organization ====
==== update specification section organization ====
-
'''Next-action''': work with Ryan, Ernie, Erin, and others who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs for greater approachability/readability by a broader audience, to design an interative update to spec organizations, in particular, the introduction/boilerplate/headers.  See below notes on hResume experiment in progress.
+
'''Goal''': greater approachability/readability of microformats specs by a broader audience.
-
[[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications. [[hreview|hReview]] has some similar improvements, but different. We need to:
+
Reference:
-
# Figure out if the new intro/headers structure in [[hresume|hResume]] and/or [[hreview|hReview]] is an improvement, and if it could be better.  Perhaps figure out the requirements for an intro/header section
+
* [[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications.  
 +
* [[hreview|hReview]] has some similar improvements, but different.
 +
* [[hcard|hCard]] has numerous improvements as well, again different from either hResume or hReview
 +
 
 +
'''Next-actions''':
 +
# contact microformats community members who are content/tutorial authors, and/or have written (or are writing) technical books, and those who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs.
 +
# figure out if the new intro/headers etc. structure/order in [[hcard|hCard]], [[hreview|hReview]], and [[hresume|hResume]]  is an improvement, and if it could be better.  Document reasoning/requirements for intro/header and other sections.
#* Shorter tends to be better
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
#* Must detail copyright/patent statements
 +
# Design an iterative update to spec organization, in particular, the introduction/boilerplate/headers.
# Write up a template - make it self-documenting per the requirements
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
# Update existing specifications with the new intro/headers structure.
Line 266: Line 293:
## [[hcalendar|hCalendar]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]
## [[hreview|hReview]]
 +
# Write up methodology behind the section organization and note editors lessons learned into an [[editors-guide]] page (what other variants were done before, in which specs, and note problems/complaints with other variants).
==== reorganizing Implementations sections ====
==== reorganizing Implementations sections ====
Line 292: Line 320:
=== site usability ===
=== site usability ===
 +
Update all these tasks for [[microformats2]]:
 +
* figure out how to get wordpress to autopost blog posts to the microformats-announce list
* 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
** ideally use the from address of the author of the blog post
Line 297: Line 327:
=== introduction / community ===
=== introduction / community ===
 +
Update all these tasks for [[microformats2]]:
* microformats-discuss *
* microformats-discuss *
Line 317: Line 348:
* [[principles]] - mostly [[microformats#the_microformats_principles|documented in the microformats]] page.
* [[principles]] - mostly [[microformats#the_microformats_principles|documented in the microformats]] page.
* clearer statement of both copyright and patents both in specific specs and in general
* clearer statement of both copyright and patents both in specific specs and in general
 +
* resolve [[process-issues]]
==== profiles ====
==== profiles ====
Line 332: Line 364:
=== emerging microformats ===
=== emerging microformats ===
 +
Update all these tasks for [[microformats2]]:
 +
* [[directions]]
* [[directions]]
* [[citation]]
* [[citation]]
Line 344: Line 378:
=== new microformat requests ===
=== new microformat requests ===
 +
Update all these tasks for [[microformats2]]:
 +
* expense reports (really just a list of "expense" items), [http://flickr.com/photos/edyson/56774178/ requested by ED], should look at UBL as a pre-existing format
* expense reports (really just a list of "expense" items), [http://flickr.com/photos/edyson/56774178/ requested by ED], should look at UBL as a pre-existing format
* photo-notes microformat
* 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
** 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]].
** iterate on [[photo-note-examples]] and start [[photo-note-formats]] and [[photo-note-brainstorming]].
 +
 +
=== wrap up classic microformats documentation ===
 +
* use these tasks to come up with any necessary or useful equivalents for [[microformats2]] specifications and resources.
 +
 +
===== minor update current specifications =====
 +
* draft hCard 1.0.1: [[hcard|hCard spec]] '''next-actions''':
 +
** <del>resolve remaining [[hcard-issues|hCard issues]]</del>
 +
** close remaining [[hcard-issues-resolved|hCard resolved issues]] by writing necessary [[hcard-faq|FAQ]] entries, updating [[hCard]], and adding to [[hcard-brainstorming]] for 1.0.1 and 1.1.
 +
** draft [[hcard-1-0-1]] by starting with [[hcard-1-0]] and incorporating [[hcard-brainstorming]] targeted for 1.0.1.
 +
** incorporate [[hcard-feedback]]
 +
** continue updating the spec per the inline comment about property references
 +
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2426]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
 +
** iterate [[hcard-parsing]] with [[value-class-pattern]] as a required feature
 +
** iterate [[hcard-parsing]] with sufficient table element special handling to do people equivalent of [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
 +
** iterate [[hcard-parsing]] with how to handle new or different [[HTML5]] markup such as the <code>&lt;time&gt;</code> element, including at least one test case with the <code>&lt;time&gt;</code> element.
 +
** [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve for minor revision, and which later
 +
** Update [[semantic-xhtml]] with lists of semantic [http://www.w3.org/TR/html401/index/elements.html elements] and [http://www.w3.org/TR/html401/index/attributes.html attributes].
 +
** Update [[hcard-brainstorming]] on element specific parsing rules
 +
** Update X2V, hKit, Operator accordingly
 +
** Write test cases accordingly
 +
** Update [[hcard-parsing]] accordingly
 +
* draft hCalendar 1.0.1: [[hcalendar|hCalendar spec]] '''next-actions''':
 +
** <del datetime="2009-10-03">resolve all outstanding [[hcalendar-issues]] into [[hcalendar-issues-resolved]]</del>
 +
** close remaining [[hcalendar-issues-resolved|hCalendar resolved issues]] by writing necessary [[hcalendar-faq|FAQ]] entries, updating [[hCalendar]], and adding to [[hcalendar-brainstorming]] for 1.0.1 and 1.1.
 +
** draft [[hcalendar-1-0-1]] by starting with [[hcalendar-1-0]] and incrementally incorporating [[hcalendar-brainstorming]] targeted for 1.0.1
 +
** incorporate [[hcalendar-feedback]]
 +
** itemize a complete property list similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list.  Separate common properties up front.
 +
** add a brief descriptive sentence for each property, similar to what [[hreview|hReview]] has. just enough so that the casual reader can avoid having to reference and read the respective sections in [[RFC2445]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.
 +
** significantly update and thoroughly specify [[hcalendar-parsing]] with [[value-class-pattern]] as a required feature
 +
** formally document [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
 +
** iterate [[hcalendar-parsing]] with how to handle new or different [[HTML5]] markup such as the <code>&lt;time&gt;</code> element, including at least one test case with the <code>&lt;time&gt;</code> element.
 +
** [[hcalendar-examples]]
 +
*** make sure all hCalendar examples that reference whole days use best international/accessible date format of YYYY-MM-DD
 +
*** add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
 +
** Write [[compound-parsing]] by abstracting commonalities between [[hcard-parsing]] and [[hcalendar-parsing]].
 +
* draft hReview 0.4
 +
* resolve hAtom issues
 +
* co-edit hAtom per permission from David Janes
 +
* draft [[hAtom]] 0.2
 +
** Clarify that "published" property values may omit seconds, and that converters to Atom are expected to imply ":00" seconds.
 +
* add sections for comments/opinion from community as well as issues subsection
 +
* solicit feedback
 +
* when sufficient consensus and issue resolution achieved, archive previous versions of specs, and update spec pages accordingly.
 +
 +
==== social network portability ====
 +
Iterate on:
 +
* [[social-network-portability]]
 +
* [[hcard-supporting-user-profiles]]
 +
* [[hcard-xfn-supporting-friends-lists]]
 +
 +
Brainstorm updates to the [[pocket-cheat-sheet]] to better enable [[social-network-portability]], or perhaps design a new '''social network portability pocket cheat sheet''' that specifically documents:
 +
* how to author/publish hCard user profiles - write this up in [[hcard-authoring]] first (see below) and then use that content.
 +
* how to author/publish hCard+XFN friends lists - write this up in [[hcard-xfn-authoring]] (see below) and then use that content.
 +
* how to parse/subscribe to hCard user profiles - write this up by updating: [[hcard-parsing]], and writing [[hcard-supporting-user-profile-parsing]] (collect this into parsing/developers tasks below)
 +
* how to parse/subscribe to hCard+XFN friends lists - write this up by writing: [[xfn-parsing]], [[hcard-xfn-supporting-friends-list-parsing]] (collect these into parsing/developers tasks below)
 +
** notes/thoughts on hCard+XFN supporting friends list parsing captured here for now:
 +
*** do a full rel="me" bidirectional crawling within the domain - some sites' hCard supporting user profiles simply link to their hCard+XFN supporting friends lists with rel="me", and thus you will discover more pages with friends lists.
 +
**** E.g. Flickr's /people/username pages have hCard for the user and link to their /people/username/contacts page with rel="me" (on the "More..." link, though they could also add rel="me" to the number inside "Your contacts (592)"). Need to get them to support hCard+XFN on the contacts themselves.
 +
*** consider parsing within a friends list page, any links that are rel="next" and rel="prev" to iterate over the whole list.
 +
 +
==== foldup cheatsheet ====
 +
'''next actions''':
 +
* gather feedback on current foldup [[pocket-cheat-sheet|pocket cheatsheet]]
 +
* document the [[pocket-cheat-sheet-feedback|feedback on the pocket cheatsheet]]
 +
* provide printing recommendations for anyone to download and print their own
 +
** Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)
 +
* update cheatsheet to include new [[value-class-pattern]] uses
 +
* give feedback to Erin or ask for volunteers to create a new cheatsheet, iterate, print more to have on hand, fold, distribute.
 +
* discuss with [[User:Adactio]] and Hannah how to best create a UK/A4 version of the pocket cheatsheet
 +
** preferably well in advance of dConstruct 2008 so that local cheatsheets can be printed.
 +
 +
==== *-authoring microformats wiki pages ====
 +
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
 +
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
 +
** instructions for all other hCard properties
 +
** a tutorial on creating an hCard for your site
 +
*** specific instructions for common blogging platforms
 +
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
 +
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.
 +
* [[hcard-xfn-authoring]] - '''next-action''': draft by starting from hCard+XFN instructions in [[hcard-examples]].
 +
* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.
 +
* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].
 +
* *-authoring for other reasonably well established microformats:
 +
** [[xfolk-authoring]], [[hatom-authoring]]
 +
 +
==== help with microformat examples in the wild ====
 +
Using the above updated [[authoring]] pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity [[hcalendar|hCalendar]] and [[hcard|hCard]] etc.  Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. [[flickr]], [[upcoming]], [[eventful]] etc.) Document any exceptions as needed.  In no particular order:
 +
* Flickr.com (3.5m hCards)
 +
* Upcoming.org (100k hCalendar events, 100k hCard venues)
 +
** home page
 +
* Eventful.com (100k hCalendar events, 100k hCard venues)
 +
* Yahoo! Tech (300k products with hReviews)
 +
* JudysBook.com (???k hReviews)
 +
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.
 +
 +
==== advocacy for obvious sites ====
 +
* [[advocacy]] - add pages/sites that obviously (no pun intended) could use microformats, update them with sample markup, find contacts for those pages to get them updated, and send requests to update their sites with microformats including sample markup. '''next-actions''': markup both twitter.com sample pages and dodgeball.com sample pages, post the changes publicly, and see which one is able to update first ;)
 +
** dodgeball.com (hCard + XFN + hAtom for profiles, hCard + hReview for venues)
 +
** write essay on [[open-data-more-important-than-open-source]] - and a shorthand URL too.
 +
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open source.
 +
*** open data &gt; open source
 +
*** "open information" vs "open source"
 +
*** i.e. please focus first on open data rather than open source, e.g. start with [[hcard|hCards]] for all organizations returned from http://wiserearth.org/organization
 +
*** if the data is open you can always export it and consume it in any number of open source systems
 +
*** that's why open data is MUCH more important than open source
 +
*** adding open data (e.g. microformats) can be done by any HTML author (yes, you), whereas open sourcing requires programming expertise, resouces, support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.
 +
*** if the data was open, anyone could rebuild an accessible version
 +
*** faqs / misconceptions:
 +
**** eschipul: @tantek - creating microformats is easier. consuming microformats is unfortunately not easier.
 +
***** A: If you think consuming microformats is not easier or hard etc., it may just be that you don't know how to do so easily, don't assume that you are an expert in something that you think is hard.  Rather, if you think something is hard, then assume others may know easier methods, and ''ask''  the community how one can do it more easily.  parsing in particular is something which is becoming easier and easier thanks to open source libraries like [[hkit|hKit]].
 +
** write essay on [[open-data-more-important-than-open-apis]] - and a shorthand URL too
 +
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open APIs.
 +
*** publishing/providing open data (e.g. microformats) can be done by any HTML author (yes, you), whereas providing/publishing open APIs requires programming expertise, resouces, and support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.
 +
 +
==== in general ====
 +
===== plain language intros =====
 +
For [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xoxo|XOXO]] to start with, write up:
 +
* brief plain-language intro at the top (say for example, something that a non-technical person like a member of the general media/press could read and understand), similar to or better than plain language intros on W3C specs.
 +
* followed by links to more plain-language resources, e.g. *-intro pages.
 +
In particular for [[xoxo|XOXO]], Angus McIntyre suggested:
 +
* As well as a syntactic example, examples of use would be useful.
 +
* when I might want to use XOXO.
 +
* Some simple examples right upfront would probably do a lot to help users figure out whether a particular microformat is for them or not.
 +
These suggestions could be incorporated into the other specs as well.
 +
===== exploratory discussions =====
 +
* update [[exploratory-discussions]] with critical microformats as "active"
 +
===== CSS enhancements for =====
 +
Analyze existing microformats for opportunities to enhance CSS and propose to W3C.
 +
* e.g. CSS datetime presentation (need to add links to my earlier work in CSS working group)
 +
* brainstorm additional possibilities for better presentation of content using existing microformats.
 +
===== update affiliations =====
 +
* Start a minimal draft/spec style guide using outline of most readable/accessible spec so far
 +
* Reference http://www.w3.org/2001/06/manual/#Editors for how to manage affiliations
 +
* Update affiliations on [[hcard]], [[hcalendar]], [[hreview]], etc. per http://www.w3.org/2001/06/manual/#Editors
 +
===== profile URLs =====
 +
* write-up and document [[profile-uris|profile URLs]] for all established microformats and perhaps for some drafts as well
 +
 +
==== [[hcard|hCard]] ====
 +
Combined next-actions for iteration on [[hcard|hCard]], and derived/subsetted microformats [[adr]] and [[geo]]
 +
* [[hcard-profile]] '''next-actions''':
 +
** update property definitions with more detail using semantics from [[RFC2426]]
 +
** link from brief sentence descriptions for each property in [[hCard]] to the respective more detailed definition in the [[hcard-profile]].
 +
** link from definitions in the [[hcard-profile]] to the specific sections in the vCard spec
 +
* [[hcard-examples]] '''next-actions''': update with examples described below
 +
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
 +
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
 +
** add example of organization-name and organization-unit usage.
 +
* [[hcard-brainstorming]] '''next-actions''': explore brainstorms proposals for a 1.1 revision, e.g.
 +
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
 +
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
 +
* [[hcard-examples-in-wild]]
 +
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx
 +
 +
* analyze [[hcard-cheatsheet]], [[adr-cheatsheet]], [[geo-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcard-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result.  add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.
 +
 +
==== [[hcalendar|hCalendar]] ====
 +
'''Next-actions''':
 +
* update [[hcalendar-examples]]
 +
** add examples like [[hcard-examples]]
 +
** flesh out and do a once over on markup/presentation of what RFC2445 examples would look like
 +
** update all hcalendar-examples to use value-title from [[value-class-pattern]] where abbr doesn't make sense. e.g.
 +
*** rrule
 +
*** duration
 +
*** ... etc.
 +
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
 +
* need spec details and then [[hcalendar-examples]] of repeating events
 +
* have folks verify [[hcalendar-profile]]. Note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]].  Probably makes sense to have a combined profile which hCalendar would use.
 +
* analyze [[hcalendar-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcalendar-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result.  add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.
 +
 +
==== [[hreview|hReview]] ====
 +
'''Next-actions''':
 +
* reconcile [[hreview-profile|hReview 0.4 XMDP profile]] 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.
 +
* Resolve all outstanding [[hreview-issues]] and [[hreview-feedback]] to-do items.
 +
 +
==== [[rel-tag]] ====
 +
'''Next-actions''':
 +
* send [[rel-tag]] XMDP profile ([[rel-tag-profile]]) to [http://dbaron.org/ David Baron].
 +
* Resolve all outstanding [[rel-tag-issues]] and [[rel-tag-feedback]] to-do items.
 +
 +
==== [[rel-me]] ====
 +
'''Next-actions''':
 +
* move XFN and XMDP FAQs, tutorial, descriptions, spec etc. from gmpg.org to microformats.org
 +
** and put redirects in place, notes about contribution
 +
* update rel-me examples and document with examples the rel-me implict subdir rule
 +
 +
==== [[hatom|hAtom]] ====
 +
'''Next-actions''':
 +
 +
==== summary Examples in the Wild page ====
 +
* need to create a summary / overall [[examples-in-the-wild]] page
 +
** parallel the summary/overall [[implementations]] page.
 +
** use newly reorganized content from the above "reoganizing Examples in the Wild" task
 +
 +
==== parsing ====
 +
'''Next-actions''':
 +
* Draft *-parsing for all reasonably well adopted microformats: [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]
=== document microformats history ===
=== document microformats history ===
Line 359: Line 591:
==Ryan==
==Ryan==
=== wiki cleanup ===
=== wiki cleanup ===
-
* possibly move dead proposals off of homepage?
+
* <s>possibly move dead proposals off of homepage?</s>
=== hCalendar/hCard/hReview creator improvements ===
=== hCalendar/hCard/hReview creator improvements ===
Line 387: Line 619:
* Work on microformats tutorial for designers
* Work on microformats tutorial for designers
* Add support for OpenID to micformats wiki
* Add support for OpenID to micformats wiki
-
* Add support for [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to the microformats blog.
+
* <strike>Add support for [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to the microformats blog</strike>.
-
* Read GTD (at least the first two chapters).
+
* <strike>Read GTD (at least the first two chapters)</strike>.
=== Campaigns ===
=== Campaigns ===
-
* Get Blogger to support hAtom and hCard
+
* <strike>Get Blogger to support hAtom and hCard</strike>
* <strike>Get LinkedIn to support hCard, hResume, hCalendar</strike> and XFN
* <strike>Get LinkedIn to support hCard, hResume, hCalendar</strike> and XFN
* Get XING to support <strike>hCard</strike>, hCalendar, hResume and XFN
* Get XING to support <strike>hCard</strike>, hCalendar, hResume and XFN
-
* Get Digg to support microformats.
+
* Get <strike>Digg to support microformats</strike> (still need XFN).
=== Wishlist ===
=== Wishlist ===
Line 406: Line 638:
* invoicing microformat
* invoicing microformat
* better microformats wiki theme
* better microformats wiki theme
-
* Define flow for OpenID + XFN + hcard
+
* Define flow for OpenID + XFN + hcard (see [http://diso-project.org DiSo Project])
 +
 
 +
Hey Chris.
 +
Congrats on Microsyntax
 +
([http://factoryjoe.com/blog/2009/05/26/stowe-boyd-launches-microsyntax-org/ "Stowe Boyd launches Microsyntax.org"]).
 +
So ... do we need a page on this Microformats wiki describing the connection between microformats and microsyntax?
== Robert Bachmann ==
== Robert Bachmann ==
 +
[[User:RobertBachmann|Robert Bachmann]]
-
=== hAtom2Atom ===
+
=== XSLTs ===
-
 
+
<ul>
-
Some ideas for features which could be implemented :
+
<li><strong>Test scripts</strong>
-
 
+
<ul>
-
(If you are interested in one of this features, add "<i>+1 Your Name</i>")
+
<li>Do some refactoring, split Perl code into smaller modules</li>
-
 
+
<li>Provide test results as HTML pages (similar to http://www.w3.org/2003/08/owl-systems/test-results-out)</li>
 +
<li>Provide some documentation for using the test scripts</li>
 +
</ul>
 +
</li>
 +
<li><strong>hAtom2Atom</strong>
<ul>
<ul>
<li>
<li>
Line 428: Line 670:
</li>
</li>
<li>Support for other XSLT engines:
<li>Support for other XSLT engines:
-
* MSXML
 
* .Net System.Xml
* .Net System.Xml
-
* Sablotron
 
-
* Oracle XSLT
 
-
* XT
 
* hAtom2Atom written using XSL 2.0?
* hAtom2Atom written using XSL 2.0?
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share.  Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share.  Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
Line 439: Line 677:
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
 +
** My opinion at the moment, I neither want to produce nor to consume RSS. Atom is nicer (and should be supported by most good feed readers available today), RSS should fade away. -- Robert Bachmann
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- <i>+1 Matt Dertinger</i>
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- <i>+1 Matt Dertinger</i>
 +
** Having the possibility of GRDDL-ing hAtom to AtomOWL seems definitly interessting. I realy should implement this some day. - Robert Bachmann
* JSON?
* JSON?
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON?  E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON?  E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
 +
*** This could enable some nice JavaScript hacks. I should give hAtom2JSON a try. - Robert Bachmann
</li>
</li>
</ul>
</ul>
([[User:Singpolyma|singpolyma]] 01:02, 9 May 2006 (PDT) -- Not XSLT, but see http://xoxotools.ning.com/hatom2rss.php for hatom to RSS2.0 conversion)
([[User:Singpolyma|singpolyma]] 01:02, 9 May 2006 (PDT) -- Not XSLT, but see http://xoxotools.ning.com/hatom2rss.php for hatom to RSS2.0 conversion)
 +
</li>
 +
</ul>
== Brian Suda ==
== Brian Suda ==
Line 466: Line 709:
* get early work from developer.technorati site
* get early work from developer.technorati site
** issues with MoinMoin full history: http://moinmoin.wikiwikiweb.de/MoinMoinQuestions/UsingTheWiki#head-9d1b1d6beedde40b92cc6c13962b5a6f5b289d10
** issues with MoinMoin full history: http://moinmoin.wikiwikiweb.de/MoinMoinQuestions/UsingTheWiki#head-9d1b1d6beedde40b92cc6c13962b5a6f5b289d10
 +
 +
=== additions to the wiki ===
 +
 +
* better explain why NOT infinitely scaling is a good thing
 +
* better explain why microformats do NOT use namespacing
== Mark Rickerby ==
== Mark Rickerby ==
Line 567: Line 815:
[[Christophe Ducamp]]
[[Christophe Ducamp]]
-
* translate red links on [[Main_Page-fr]]
+
* seed "microformateurs group" and invite them to update http://microformateurs.org
-
* localize a french version of the official website and migrate contents
+
** write a process for newbies in order to make them write [[posh-fr|CHIC]] posts on a public blog-governed-by-wiki ([http://socialsynergyweb.net/cgi-bin/wiki/MicroFormateurs/Blog]) before publication.
-
** ask authorization to the authors
+
** find experts for peer-reviewing
-
** migration could be done on any collaborative CMS
+
** find french CSS gurus to setup a nice Sandbox-CSS template on Wordpress
-
** test a cocomment system (based on local-wiki)
+
* translating the wiki
-
** complete with original links
+
** translate red links on [[Main_Page-fr]] and synchronize
-
* find experts for peer-reviewing
+
** find out microformateurs at ease on "the-wiki-way-translation", and ready to help on semi-anonymous-synchro
-
* update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
+
* community-marketing -> pinko-marketing
-
** create hCard, hCalendar... and all red link pages on french wikipedia
+
** public-relations towards french journalists and complete [[advocacy-fr|advocacy]] (especially [[hcard-advocacy-fr]] towards organizations.
-
* find help and maintain http://www.communitywiki.org/MicroFormats
+
** help to build events, workshops like barcamps and explorcamps
 +
** update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] and subpages via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
 +
** open discussion with french wikipediens about implementing some of the english existing templates
 +
** small gifts: accessories and free gifts ? t-shirts, localized cheat-sheet, id-hcard-openid-providing, etc.
 +
*** create hCard, hCalendar... and all red link pages on french wikipedia
* localize [[species-fr]] and related pages
* localize [[species-fr]] and related pages
-
* clean all dead links pointing to elanceur.org
+
* move all contents remaining on elanceur.org -> microformateurs.org
 +
* wiki and uf:
 +
** write and talk with "aboutus.org" to invite them to make experiences with uf -> talk with Mark Dilley
 +
** maintain/update http://www.communitywiki.org/MicroFormats and talk with LionKimbro
 +
** XWiki : awaiting beta-test of new platform
 +
*** Follow-up LudovicDubost et LaurentLunati
 +
* setup real-life links with european [[governance-fr|governance]] members ;) may be joining dconstruct-microformats-workshop  - find solution (registering fees and travel expenses -> talk with Arnaud Fontaine or search french sponsors)
== Frances Berriman ==
== Frances Berriman ==
Line 584: Line 842:
[[User:Phae|Frances Berriman]]
[[User:Phae|Frances Berriman]]
-
* Work on styles for [[zen-garden]] project.
+
* Clean up this todo list (meta!)
-
* Style HTML cheatsheet to match Brian Suda's PDF.
+
** Move alumni admin tasks out, and into a 'up for grabs' bucket (unless 100% specific to person).
-
* Write simplified help/implementation documents (how tos) for all finalised Microformats.
+
*** Ping anyone with specific tasks / nag
-
* Re-organise general FAQ and simplify
+
* Proposal for page simplifications - notes, to expand to tasks later:
-
** (Feel free to add suggested tasks to my list below:)
+
** Need a way to push active formats (those in the process) to the fore, and push back stagnating items.
-
*** Help converge on organization efforts ~bewest :-)
+
** Process updates to blog?
 +
** Activity overview updates on main site somewhere?
 +
*** Code and Tools page on site: Currently it's mostly only tools.  Need to add a list of actual specifications on the wiki.
 +
** In general: less clutter, more structure, more focus.
== Ben West (bewest) ==
== Ben West (bewest) ==
Line 734: Line 995:
=== Microformats Proposals ===
=== Microformats Proposals ===
-
<ul>
+
 
-
<li>rel="disclaimer":
+
* rel="disclaimer":
-
* Purpose: to create a semantic linkage (relationship) between a foot-note or end-note marker and the actual location of the text that the marker refers to.</li>
+
** Purpose: to create a semantic linkage (relationship) between a foot-note or end-note marker and the actual location of the text that the marker refers to.
-
<li>rel="external":
+
* rel="external":
-
* Purpose: to formalize what is already in existence in the wild. The use of rel="external" to refer to a document that is external or outside of the current domain.</li>
+
** Purpose: to formalize what is already in existence in the wild. The use of rel="external" to refer to a document that is external or outside of the current domain.
-
</ul>
+
== Henri Bergius ==
== Henri Bergius ==
Line 782: Line 1,042:
* bundling parser as a [http://tiddlywiki.org TidlyWiki] plugin for hCards
* bundling parser as a [http://tiddlywiki.org TidlyWiki] plugin for hCards
* documenting how best to microformat TiddlyWiki pages
* documenting how best to microformat TiddlyWiki pages
 +
 +
== [[User:RobManson | Rob Manson]] ==
 +
* chase the admins to get some creation template extensions installed for wiki (see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle)
 +
 +
== [[User:ClayNewton | Clay Newton]] ==
 +
* Work on getting others involved in [[trade-examples]]
 +
** Need examples from major online banking sites
 +
** Need examples from major ecommerce sites
 +
* Continue working on: [[trade-brainstorming]]
 +
 +
== [[User:BenWard | Ben Ward]] ==
 +
 +
=== Recurring ===
 +
 +
* Delete Wiki Spam
 +
 +
=== Currently ===
 +
 +
* Gardening/updating key wiki pages.
 +
** [[how-to-play]]
 +
** XHTML Design Principals
 +
* embed brainstorming
 +
* Considering new welcome banner of µf.org to link to various µf resources, rather than being dominated by the infrequently updated blog.
 +
 +
=== Next Actions ===
 +
 +
* Conclude new hCalendar proposals from Yahoo TV Listings experience
 +
* Resume work on hListing microformat
 +
* Re-org the Microformats.org front-page content
 +
** Work with [[User:Phae]] on refreshing the microformats frontpage content
 +
** Build new events module for the blog using Upcoming.org, rather than hard coded event data (Matt Harris may have done this…)
 +
** Build new wiki edits module for the blog
 +
** Combine ‘list of microformats’ into the intro text? Make intro text more friendly.
 +
* Build a microformats activity stream
 +
** Replace front page blog with activity flow
 +
*** Wiki Edits/New Pages
 +
*** New Mailing List Threads
 +
*** Interesting µf links
 +
*** Blog posts
 +
*** Upcoming events/event reminders
 +
* Improve µf.org/blog OpenID support, find a good workflow for login/comment (current plug-in has an abysmal user experience)
 +
 +
== [[User:Spiritquest|Ketan Majmudar]] ==
 +
=== Activites ===
 +
* Work on developing the [[hlisting-brainstorming|hListing]] proposal
 +
** Provide real world examples and apply this to the proposed specifications
 +
* refine and keep up to date with [[hcard|hCard]] formats as used on existing sites [[http://www.ethical-junction.org| Ethical Junction CIC]]
 +
* Understand / follow and evangalise existing patterns, especially the new [[value-class-pattern]]
 +
* see where I can help the community
 +
* look at using x2v or writing php parser classes for hcard -> vcard
 +
* open source hCard class (php)  used to format db fields

Current revision

Contents

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

microformats2 updates

The following pages need to be updated to for microformats2 (typically code, examples, and any specific format advice)

wiki gardening

trim fixups

Search for all uses of "tr.im" for shortlinks and replace them with "ufs.cc/w/" links that just use the pagename.

In particular, let's document old tr.im links and (unlinked) and where they used to link to so that if someone *searches* for tr.im URLs to figure out what happened to them, there's a chance they'll find the equivalent.

simplify pages

Review pages, from the Main Page on down and:

Examples of simplified pages:

Pages to simplify:

remove broken URLs

There's lots of links to sites that are now gone (see site-deaths on IWC for a full list).

It'd be useful if we replaced them where possible with links to archive.org or equivalent.

TODO (mark as done when done):

incorporate things expected to break

shortlink spec

The rel=shortlink spec:

is going to die soon as part of Google Code's shutdown.

1. We should copy that spec (along with FAQ for the first few valid questions/comments) to rel-shortlink, moving existing contents there to supplementary pages or purely historical record.

2. Get http://purl.org/net/shortlink to redirect to rel-shortlink instead.


more documentation and research

extract from 1989 timbl proposal


microformats specific

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

for all microformats

hCard

hCalendar

Add support to open source calendar projects

These are open source projects that could be potentially enhanced to support hCalendar.

hReview

hCalendar/hCard/hReview editor

hAtom

WordPress patches for microformats

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.

Drupal patches for microformats

Adding Microformats to Existing Pages

rel-tagging on Wikipedia

Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the Wikipedia page on tagging. Andy Mabbett 14:07, 3 Jan 2007 (PST)

Glossary

Add to the glossary.

hAtom tutorial

Finish the hatom-tutorial.

wiki gardening

Spelling

Per how-to-play: for English-language pages only: Find British spellings of common words and replace them with the US spellings per en-US. Mark such edits as "minor" with the comment: [[en-US]]. Please be careful to use and maintain proper native spelling of proper nouns (see how-to-play for details).

Here is a table of searches for some of the British-English spellings that have crept into English-language microformats wiki pages, along with their respective US-English spellings. If you find other British spellings, please feel free to add them to this table, with their US equivalent.

en-GB en-US
behaviour behavior
behaviours behaviors
centre center
colour color
colours colors
favour favor
flavour flavor
flavours flavors
flavoured flavored
minimise minimize
minimises minimizes
recognise recognize
recognised recognized

More American and British English spelling differences

Admins

This section is for folks to suggest to-do items for admins, in particular, having to do with suggestions for improvements to microformats.org infrastructure such as the wiki. If you do add an item to this list, please sign your username with four tildes: ~~~~.

Admins check this "inbox" periodically and process and move items to admin-to-do.

Please check admin-to-do to see if there is already an ongoing task item relating to your request. Otherwise add the item below.

Website Improvements

Wiki improvements

Tantek

I'm keeping microformats related to-do items here both for my own convenience, and for folks looking to help out. - Tantek.

overall priority ordering

  1. Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
  2. Update microformats2-parsing with resolved microformats2-parsing-issues
  3. Help implementers with established microformats
  4. Iterate on existing established microformats, resolve issues/feedback etc.
  5. Wiki cleanup/gardening for existing established microformats
  6. Site usability of microformats.org top-down as an entry point
  7. Community dynamics, process and principles improvements to help guide new microformats developments
  8. Wrap up classic microformats documentation
  9. Document microformats history.
  10. Other

protect the community

update microformats2-parsing with resolved issues

Update microformats2-parsing with resolved microformats2-parsing-issues

help implementers

Update all these tasks for microformats2:

wiki cleanup

Update all these tasks for microformats2:

for all microformat specs

Next-actions:

update specification section organization

Goal: greater approachability/readability of microformats specs by a broader audience.

Reference:

Next-actions:

  1. contact microformats community members who are content/tutorial authors, and/or have written (or are writing) technical books, and those who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs.
  2. figure out if the new intro/headers etc. structure/order in hCard, hReview, and hResume is an improvement, and if it could be better. Document reasoning/requirements for intro/header and other sections.
    • Shorter tends to be better
    • Must be comprehensive enough to "print and read"
    • Must detail authorship/editorship
    • Must detail copyright/patent statements
  3. Design an iterative update to spec organization, in particular, the introduction/boilerplate/headers.
  4. Write up a template - make it self-documenting per the requirements
  5. Update existing specifications with the new intro/headers structure.
    1. hCard
    2. hCalendar
    3. hReview
  6. Write up methodology behind the section organization and note editors lessons learned into an editors-guide page (what other variants were done before, in which specs, and note problems/complaints with other variants).

reorganizing Implementations sections

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.

Next-actions:

reorg Examples in the Wild sections

Work with community to:

site usability

Update all these tasks for microformats2:

introduction / community

Update all these tasks for microformats2:

posh improvement

principles and process

Create the following pages and document/fill them with content from other pages, email lists, and presentations.

profiles

community mark

document issue resolutions

emerging microformats

Update all these tasks for microformats2:

Next-actions for each emerging microformat (one at a time)

new microformat requests

Update all these tasks for microformats2:

wrap up classic microformats documentation

minor update current specifications

social network portability

Iterate on:

Brainstorm updates to the pocket-cheat-sheet to better enable social-network-portability, or perhaps design a new social network portability pocket cheat sheet that specifically documents:

foldup cheatsheet

next actions:

*-authoring microformats wiki pages

help with microformat examples in the wild

Using the above updated authoring pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity hCalendar and hCard etc. Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. flickr, upcoming, eventful etc.) Document any exceptions as needed. In no particular order:

advocacy for obvious sites

in general

plain language intros

For hCard, hCalendar, hReview, XOXO to start with, write up:

In particular for XOXO, Angus McIntyre suggested:

These suggestions could be incorporated into the other specs as well.

exploratory discussions
CSS enhancements for

Analyze existing microformats for opportunities to enhance CSS and propose to W3C.

update affiliations
profile URLs

hCard

Combined next-actions for iteration on hCard, and derived/subsetted microformats adr and geo

hCalendar

Next-actions:

hReview

Next-actions:

rel-tag

Next-actions:

rel-me

Next-actions:

hAtom

Next-actions:

summary Examples in the Wild page

parsing

Next-actions:

document microformats history

Document microformats history, including:

other

Ryan

wiki cleanup

hCalendar/hCard/hReview creator improvements

other

rel-payment

hcalendar

Dimitri Glazkov

Chris Messina

General

Campaigns

Wishlist

Hey Chris. Congrats on Microsyntax ("Stowe Boyd launches Microsyntax.org"). So ... do we need a page on this Microformats wiki describing the connection between microformats and microsyntax?

Robert Bachmann

Robert Bachmann

XSLTs

Brian Suda

Citation Microformats

X2V

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

WARNINGS and ERROR

work on the warnings and error output for the pre-check in X2V

FAQ

Microformats History

additions to the wiki

Mark Rickerby

Current Tasks

Wishlist

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:

Dan Connolly

DanC hopes to sync up on these tasks in irc roughly weekly, during Wednesday afternoon (Chicago time) "office hours". See also my esw todo list and someday pile.

DanC 15:39, 31 May 2006 (PDT)

Chris Casciano

ChrisCasciano

Drew McLellan

DrewMcLellan

Christophe Ducamp (french localization)

Christophe Ducamp

Frances Berriman

Frances Berriman

Ben West (bewest)

bewest

Expore Microformat Deployment Issues

How does who determine the status of work going through some stage of the process? When does a format move from draft to "full spec"? Who decides? What are the qualitative and quantitative features that characterize work in different stages, especially as a spec nears deployment as "full spec". What makes this pronouncement more than a mythical blessing? What quantitative analyses can be provided to validate deployment? Today, we have powerful agents capable of processing huge amounts of information on the web. Should we be using these to measure published marketshare? What role should tools and test suites play in deploying microformats?

Vocabulary

A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is "on the same page," especially since some of the language is highly symbolic. Terms:

See glossary. Andy Mabbett 13:57, 7 Dec 2006 (PST)

Creators

_Concession_: my plans involve reuse of code, which would involve non-compatible changes with the current inline model. This is a nice feature, so maybe I should be branching instead.

Information Architecture

Help Welcomed! Please leave your name Add complaints to wiki-feedback! Helping to make the wiki easier to use. I'd like to see the main page more towards a format like http://simile.mit.edu/solvent/ with the big questions right out front:

I'd like to change the front page to this kind of design.

Support Pages

There are several categories of things in the wiki. Can we enumerate them?

Can others agree and or refine this list? Should I take it to the -discuss list? How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?

The wiki should also capture wisdom that stems from discussions that don't produce microformats. For example, Chris Messina suggests a "Best Of" page suitable for capturing this kind of wisdom. I think we can think of a given microformat as being at a place in a spectrum that ranges from "not yet thought of", to "interesting but needs work," or even "rejected", and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...). If there were such a page would it:

(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)

Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- Cgriego 13:25, 16 Oct 2006 (PDT)

Mike Schinkel's Comments

My suggestion on the list was for us to use a convention that the entry page (i.e. http://microformats.org/wiki/hcard) would be an index into a list of (psuedo) standardized sub pages so that it would be very people to find what is important to them. For example, is a list of potential sub pages:

These pages would be located respectively at

Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.

NOTE: This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat. In this context "microformat" is a more abstract concept and "spec" is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like "spec" are the pages listed on its home page.

Matt Dertinger (Thewhoo)

User:Thewhoo

hAtom2Atom

Microformats Proposals

Henri Bergius

Henri Bergius

Justin Thorp

Mark Lentczner

Derrick Pallas

microformat proposal: dependancy

Paul Downey

Rob Manson

Clay Newton

Ben Ward

Recurring

Currently

Next Actions

Ketan Majmudar

Activites

To Do was last modified: Monday, December 31st, 2018

Views