To Do

(Difference between revisions)

Jump to: navigation, search
m (Reverted edits by 766nj57 (Talk) to last version by Tantek)
Line 1: Line 1:
-
HOW THING OUT
+
<entry-title>To Do</entry-title>
-
HOW ANYTHING OUT
+
__TOC__
-
HOW EVERYTHING OUT
+
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]
-
HOW UNIVERSE OUT
+
 
-
HOW MAKE THING OUT
+
== wiki gardening ==
-
HOW MAKE ANYTHING OUT
+
 
-
HOW MAKE EVERYTHING OUT
+
=== trim fixups ===
-
HOW MAKE UNIVERSE OUT
+
Search for all uses of "tr.im" for shortlinks and replace them with "ufs.cc/w/" links that just use the pagename.
-
HOW THING BE OUT
+
 
-
HOW ANYTHING BE OUT
+
* [http://www.google.com/search?q=site%3Amicroformats.org+tr.im Google search for site:microformats.org tr.im]
-
HOW EVERYTHING BE OUT
+
 
-
HOW UNIVERSE BE OUT
+
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.
-
HOW MAKE THING BE OUT
+
 
-
HOW MAKE ANYTHING BE OUT
+
* [[tr.im]]
-
HOW MAKE EVERYTHING BE OUT
+
 
-
HOW MAKE UNIVERSE BE OUT
+
=== simplify pages ===
-
HOW THING OUT
+
Review pages, from the [[Main Page]] on down and:
-
HOW ANYTHING OUT
+
 
-
HOW EVERYTHING OUT
+
* Simplify/minimize the content in the pages with direct writing, assuming an eager(impatient,positive) reader in the primary reading flow.
-
HOW UNIVERSE OUT
+
* 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.
-
HOW MAKE THING OUT
+
 
-
HOW MAKE ANYTHING OUT
+
Examples of simplified pages:
-
HOW MAKE EVERYTHING OUT
+
* [[Main Page]] - simplified quite a bit (2012-04-02), but could probably use additional simplification
-
HOW MAKE UNIVERSE OUT
+
* ...
-
HOW THING BE OUT
+
 
-
HOW ANYTHING BE OUT
+
Pages to simplify:
-
HOW EVERYTHING BE OUT
+
* [[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)
-
HOW UNIVERSE BE OUT
+
* pages listed in [[stable-pages]] (simplifying these first will help with better translations)
-
HOW MAKE THING BE OUT
+
** for specifications, please work with their editor(s) on non-trivial content copy edits.
-
HOW MAKE ANYTHING BE OUT
+
 
-
HOW MAKE EVERYTHING BE OUT
+
== microformats specific ==
-
HOW MAKE UNIVERSE BE OUT
+
 
-
HOW THING OUT
+
Just some nice things, feel free to do any of these.
-
HOW ANYTHING OUT
+
 
-
HOW EVERYTHING OUT
+
=== for all microformats ===
-
HOW UNIVERSE OUT
+
* We have added a new mailing list called microformats-new.  There may be some confusion surrounding this change, so it would be helpful to:
-
HOW MAKE THING OUT
+
** 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.
-
HOW MAKE ANYTHING OUT
+
** Add a faq entry somewhere on why the new list was created.
-
HOW MAKE EVERYTHING OUT
+
** Double check the wiki pages to make sure advice on mailing lists is accurate.
-
HOW MAKE UNIVERSE OUT
+
* quick and easy "how to" pages for each microformat. [[get-started]] is a good overall start.
-
HOW THING BE OUT
+
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
-
HOW ANYTHING BE OUT
+
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
-
HOW EVERYTHING BE OUT
+
* 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.
-
HOW UNIVERSE BE OUT
+
* 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]
-
HOW MAKE THING BE OUT
+
* 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.
-
HOW MAKE ANYTHING BE OUT
+
* 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
-
HOW MAKE EVERYTHING BE OUT
+
 
-
HOW MAKE UNIVERSE BE OUT
+
=== hCard ===
-
HOW THING OUT
+
* microformatted versions of conference pages
-
HOW ANYTHING OUT
+
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
-
HOW EVERYTHING OUT
+
* vcard to hcard converter
-
HOW UNIVERSE OUT
+
** 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 as hCards
-
HOW MAKE THING OUT
+
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
-
HOW MAKE ANYTHING OUT
+
*** For Ruby: http://vpim.rubyforge.org/
-
HOW MAKE EVERYTHING OUT
+
*** For C: http://freshmeat.net/projects/libvc/
-
HOW MAKE UNIVERSE OUT
+
*** For Python: http://www.nongnu.org/python-pdi/
-
HOW THING BE OUT
+
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
-
HOW ANYTHING BE OUT
+
** 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]
-
HOW EVERYTHING BE OUT
+
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
-
HOW UNIVERSE BE OUT
+
* 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])
-
HOW MAKE THING BE OUT
+
* 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
-
HOW MAKE ANYTHING BE OUT
+
** include class="type" without explicit value test cases, based on [[hcard#type_with_unspecified_value|hCard type with unspecified value]].
-
HOW MAKE EVERYTHING BE OUT
+
 
-
HOW MAKE UNIVERSE BE OUT
+
=== hCalendar ===
-
HOW THING OUT
+
==== Add support to open source calendar projects ====
-
HOW ANYTHING OUT
+
These are open source projects that could be potentially enhanced to support hCalendar.
-
HOW EVERYTHING OUT
+
 
-
HOW UNIVERSE OUT
+
* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]
-
HOW MAKE THING OUT
+
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]
-
HOW MAKE ANYTHING OUT
+
* [http://www.vcalendar.org VCalendar]
-
HOW MAKE EVERYTHING OUT
+
* Investigation: [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]
-
HOW MAKE UNIVERSE OUT
+
 
-
HOW THING BE OUT
+
=== hReview ===
-
HOW ANYTHING BE OUT
+
* [[hreview|hReview]] support in Ecto (hey Adriaan!), requested by Andy Smith
-
HOW EVERYTHING BE OUT
+
* an [[hreview|hReview]] validator.
-
HOW UNIVERSE BE OUT
+
* a semantic, clean css star rating picker (e.g. a UI widget to rate from 1-5 stars)
-
HOW MAKE THING BE OUT
+
** both [http://komodomedia.com/blog/index.php/2005/08/24/creating-a-star-rater-using-css/ this] and [http://factorycity.net/demos/drupal/rating/default.html this] have some flaws. Ask [[User:RyanKing|Ryan King]] for an explanation.
-
HOW MAKE ANYTHING BE OUT
+
 
-
HOW MAKE EVERYTHING BE OUT
+
=== hCalendar/hCard/hReview editor ===
-
HOW MAKE UNIVERSE BE OUT
+
* 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).
-
HOW THING OUT
+
 
-
HOW ANYTHING OUT
+
=== hAtom ===
-
HOW EVERYTHING OUT
+
* [[hatom-issues]] needs sections for closed issues, resolved issues, and open issues sorted by year, similar to [[hcard-issues]].
-
HOW UNIVERSE OUT
+
 
-
HOW MAKE THING OUT
+
=== WordPress patches for microformats ===
-
HOW MAKE ANYTHING OUT
+
* submit patches for WordPress code/templates for microformats improvement
-
HOW MAKE EVERYTHING OUT
+
** &lt;address class="vcard"&gt; improvement in post author publication (e.g. home page of http://microformats.org/ )
-
HOW MAKE UNIVERSE OUT
+
* Wordpress plugin for microformats, specifically hReview and hCalendar
-
HOW THING BE OUT
+
** See [http://www.surfarama.com/index.php?p=227 lazyweb request]
-
HOW ANYTHING BE OUT
+
 
-
HOW EVERYTHING BE OUT
+
=== Yahoo Open Source Library Patches ===
-
HOW UNIVERSE BE OUT
+
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.
-
HOW MAKE THING BE OUT
+
 
-
HOW MAKE ANYTHING BE OUT
+
* [http://developer.yahoo.net/yui/ Yahoo! User Interface Library]
-
HOW MAKE EVERYTHING BE OUT
+
* [http://developer.yahoo.net/ypatterns/ Yahoo! Design Patterns Library]
-
HOW MAKE UNIVERSE BE OUT
+
* [http://www.yuiblog.com Yahoo! User Interface Blog]
-
HOW THING OUT
+
 
-
HOW ANYTHING OUT
+
=== Drupal patches for microformats ===
-
HOW EVERYTHING OUT
+
* [http://groups.drupal.org/microformats-in-drupal Microformat Module for Drupal] A group discussing ways to implement microformats in Drupal.  Currently looking to support hAtom, hCard and hCalendar to start with.  Contact digitalspaghetti at gmail dot com if you are interested in contributing to the project.
-
HOW UNIVERSE OUT
+
 
-
HOW MAKE THING OUT
+
=== Adding Microformats to Existing Pages ===
-
HOW MAKE ANYTHING OUT
+
* See [[advocacy#Adding_Microformats_to_Existing_Sites|advocacy: Adding microformats to existing sites]].
-
HOW MAKE EVERYTHING OUT
+
 
-
HOW MAKE UNIVERSE OUT
+
===rel-tagging on Wikipedia===
-
HOW THING BE OUT
+
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)
-
HOW ANYTHING BE OUT
+
 
-
HOW EVERYTHING BE OUT
+
===Glossary===
-
HOW UNIVERSE BE OUT
+
Add to the [[glossary]].
-
HOW MAKE THING BE OUT
+
 
-
HOW MAKE ANYTHING BE OUT
+
===hAtom tutorial===
-
HOW MAKE EVERYTHING BE OUT
+
Finish the [[hatom-tutorial]].
-
HOW MAKE UNIVERSE BE OUT
+
-
HOW THING OUT
+
=== wiki gardening ===
-
HOW ANYTHING OUT
+
* Find [[:Special:Lonelypages|orphaned]] pages, and add links to them.
-
HOW EVERYTHING OUT
+
* Use [[templates]] for boilerplate text and repeated lists of links
-
HOW UNIVERSE OUT
+
* 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.
-
HOW MAKE THING OUT
+
 
-
HOW MAKE ANYTHING OUT
+
====Spelling====
-
HOW MAKE EVERYTHING OUT
+
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).
-
HOW MAKE UNIVERSE OUT
+
 
-
HOW THING BE OUT
+
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.
-
HOW ANYTHING BE OUT
+
 
-
HOW EVERYTHING BE OUT
+
{| border="1"
-
HOW UNIVERSE BE OUT
+
|+
-
HOW MAKE THING BE OUT
+
! [[en-GB]] !! [[en-US]]
-
HOW MAKE ANYTHING BE OUT
+
|-
-
HOW MAKE EVERYTHING BE OUT
+
| [http://microformats.org/wiki/Special:Search?search=behaviour&go=Go behaviour] || behavior
-
HOW MAKE UNIVERSE BE OUT
+
|-
-
HOW THING OUT
+
| [http://microformats.org/wiki/Special:Search?search=behaviours&go=Go behaviours] || behaviors
-
HOW ANYTHING OUT
+
|-
-
HOW EVERYTHING OUT
+
| [http://microformats.org/wiki/Special:Search?search=centre&go=Go centre] || center
-
HOW UNIVERSE OUT
+
|-
-
HOW MAKE THING OUT
+
| [http://microformats.org/wiki/Special:Search?search=colour&go=Go colour] || color
-
HOW MAKE ANYTHING OUT
+
|-
-
HOW MAKE EVERYTHING OUT
+
| [http://microformats.org/wiki/Special:Search?search=colours&go=Go colours] || colors
-
HOW MAKE UNIVERSE OUT
+
|-
-
HOW THING BE OUT
+
| [http://microformats.org/wiki/Special:Search?search=favour&go=Go favour] || favor
-
HOW ANYTHING BE OUT
+
|-
-
HOW EVERYTHING BE OUT
+
| [http://microformats.org/wiki/Special:Search?search=flavour&go=Go flavour] || flavor
-
HOW UNIVERSE BE OUT
+
|-
-
HOW MAKE THING BE OUT
+
| [http://microformats.org/wiki/Special:Search?search=flavours&go=Go flavours] || flavors
-
HOW MAKE ANYTHING BE OUT
+
|-
-
HOW MAKE EVERYTHING BE OUT
+
| [http://microformats.org/wiki/Special:Search?search=flavoured&go=Go flavoured] || flavored
-
HOW MAKE UNIVERSE BE OUT
+
|-
-
HOW THING OUT
+
| [http://microformats.org/wiki/Special:Search?search=minimise&go=Go minimise] || minimize
-
HOW ANYTHING OUT
+
|-
-
HOW EVERYTHING OUT
+
| [http://microformats.org/wiki/Special:Search?search=minimises&go=Go minimises] || minimizes
-
HOW UNIVERSE OUT
+
|-
-
HOW MAKE THING OUT
+
| [http://microformats.org/wiki/Special:Search?search=recognise&go=Go recognise] || recognize
-
HOW MAKE ANYTHING OUT
+
|-
-
HOW MAKE EVERYTHING OUT
+
| [http://microformats.org/wiki/Special:Search?search=recognised&go=Go recognised] || recognized
-
HOW MAKE UNIVERSE OUT
+
|-
-
HOW THING BE OUT
+
|}
-
HOW ANYTHING BE OUT
+
 
-
HOW EVERYTHING BE OUT
+
[http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences More American and British English spelling differences]
-
HOW UNIVERSE BE OUT
+
 
-
HOW MAKE THING BE OUT
+
== Admins ==
-
HOW MAKE ANYTHING BE OUT
+
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>.
-
HOW MAKE EVERYTHING BE OUT
+
 
-
HOW MAKE UNIVERSE BE OUT
+
Admins check this "inbox" periodically and process and move items to [[admin-to-do]].
-
HOW THING OUT
+
 
-
HOW ANYTHING OUT
+
Please check [[admin-to-do]] to see if there is already an ongoing task item relating to your request. Otherwise add the item below.
-
HOW EVERYTHING OUT
+
 
-
HOW UNIVERSE OUT
+
=== Website Improvements ===
-
HOW MAKE THING OUT
+
* ...
-
HOW MAKE ANYTHING OUT
+
 
-
HOW MAKE EVERYTHING OUT
+
=== Wiki improvements ===
-
HOW MAKE UNIVERSE OUT
+
 
-
HOW THING BE OUT
+
* Something broken with the new MediaWiki microformats templates for date modified on delta/version pages? see: https://twitter.com/CogitoStudios/status/32227146466332672
-
HOW ANYTHING BE OUT
+
 
-
HOW EVERYTHING BE OUT
+
* 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>
-
HOW UNIVERSE BE OUT
+
 
-
HOW MAKE THING BE OUT
+
* New link styles for links to mailing list archive
-
HOW MAKE ANYTHING BE OUT
+
** Lacking a more concrete suggestion for how to improve such links, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)
-
HOW MAKE EVERYTHING BE OUT
+
 
-
HOW MAKE UNIVERSE BE OUT
+
* Add proper styling to phrase elements
-
HOW THING OUT
+
** Lacking a more concrete suggestion for how to improve styling of phrase elements, I'm inclined to park this in "won't do". [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)
-
HOW ANYTHING OUT
+
 
-
HOW EVERYTHING OUT
+
* Make email addresses editable [[User:Singpolyma|Singpolyma]] 02:47, 26 July 2009 (UTC)
-
HOW UNIVERSE OUT
+
** How would this work and what's the purpose? [[User:Tantek|Tantek]] 02:39, 10 September 2009 (UTC)
-
HOW MAKE THING OUT
+
 
-
HOW MAKE ANYTHING OUT
+
== Tantek ==
-
HOW MAKE EVERYTHING OUT
+
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].
-
HOW MAKE UNIVERSE OUT
+
 
-
HOW THING BE OUT
+
=== overall priority ordering ===
-
HOW ANYTHING BE OUT
+
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
-
HOW EVERYTHING BE OUT
+
# Help publishers with established microformats: [[hcard|hCard]], [[xfn]], [[rel-tag]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
-
HOW UNIVERSE BE OUT
+
# Help implementers with established microformats
-
HOW MAKE THING BE OUT
+
# Iterate on existing established microformats, resolve issues/feedback etc.
-
HOW MAKE ANYTHING BE OUT
+
# Wiki cleanup/gardening for existing established microformats
-
HOW MAKE EVERYTHING BE OUT
+
# Site usability of microformats.org top-down as an entry point
-
HOW MAKE UNIVERSE BE OUT
+
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments
-
HOW THING OUT
+
# Emerging in-demand microformats: [[hresume|hResume]], [[hlisting|hListing]], [[citation]], [[media-info]] using abovementioned process and principles improvements.
-
HOW ANYTHING OUT
+
# New microformat requests
-
HOW EVERYTHING OUT
+
# Document microformats [[history]].
-
HOW UNIVERSE OUT
+
# Other
-
HOW MAKE THING OUT
+
 
-
HOW MAKE ANYTHING OUT
+
=== protect the community ===
-
HOW MAKE EVERYTHING OUT
+
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
-
HOW MAKE UNIVERSE OUT
+
** add to [[mailing-lists]] and [[how-to-play]] policies/guidelines accordingly.
-
HOW THING BE OUT
+
** redirect and resolve threads accordingly per guidelines
-
HOW ANYTHING BE OUT
+
** privately email violaters kindly asking them to improve their behavior
-
HOW EVERYTHING BE OUT
+
** work with admins on next steps for individuals negatively impacting the community
-
HOW UNIVERSE BE OUT
+
** 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.
-
HOW MAKE THING BE OUT
+
** move exploratory discussions which are failing to follow the process to a separate page from that
-
HOW MAKE ANYTHING BE OUT
+
** repair damage done to the wiki
-
HOW MAKE EVERYTHING BE OUT
+
*** identify damage done to the wiki - often in forms as simple as content changes that hurt usability (and thus accessibility)
-
HOW MAKE UNIVERSE BE OUT
+
*** document additional [[how-to-play]] guidelines to discourage and hopefully reduce such wiki damaging behavior in the future
-
HOW THING OUT
+
*** repair/undo/reorganize page section division that hurt usability (and thus accessibility)
-
HOW ANYTHING OUT
+
**** [[hcalendar-examples-in-wild]]
-
HOW EVERYTHING OUT
+
***** afterwards add some of the excellent conference schedule calendars that [[User:Adactio]] has been creating like:
-
HOW UNIVERSE OUT
+
****** http://adactio.com/extras/schedules/barcampbrighton3/
-
HOW MAKE THING OUT
+
*** repair/undo/reorganize page splitting that hurt usability (and thus accessibility)
-
HOW MAKE ANYTHING OUT
+
**** [[to-do]]
-
HOW MAKE EVERYTHING OUT
+
 
-
HOW MAKE UNIVERSE OUT
+
=== help publishers ===
-
HOW THING BE OUT
+
==== solve problems blocking publishers ====
-
HOW ANYTHING BE OUT
+
* [[value-class-pattern]]
-
HOW EVERYTHING BE OUT
+
** <del>drafted</del>
-
HOW UNIVERSE BE OUT
+
** <del>[[value-class-date-time-tests]] - finish writing date and time tests</del>
-
HOW MAKE THING BE OUT
+
** <del>put out call for review, implementation,</del> and value-title tests
-
HOW MAKE ANYTHING BE OUT
+
 
-
HOW MAKE EVERYTHING BE OUT
+
===== minor update current specifications =====
-
HOW MAKE UNIVERSE BE OUT
+
* draft hCard 1.0.1: [[hcard|hCard spec]] '''next-actions''':
-
HOW THING OUT
+
** <del>resolve remaining [[hcard-issues|hCard issues]]</del>
-
HOW ANYTHING OUT
+
** 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.
-
HOW EVERYTHING OUT
+
** draft [[hcard-1-0-1]] by starting with [[hcard-1-0]] and incorporating [[hcard-brainstorming]] targeted for 1.0.1.
-
HOW UNIVERSE OUT
+
** incorporate [[hcard-feedback]]
-
HOW MAKE THING OUT
+
** continue updating the spec per the inline comment about property references
-
HOW MAKE ANYTHING OUT
+
** 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.
-
HOW MAKE EVERYTHING OUT
+
** iterate [[hcard-parsing]] with [[value-class-pattern]] as a required feature
-
HOW MAKE UNIVERSE OUT
+
** iterate [[hcard-parsing]] with sufficient table element special handling to do people equivalent of [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
-
HOW THING BE OUT
+
** 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.
-
HOW ANYTHING BE OUT
+
** [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve for minor revision, and which later
-
HOW EVERYTHING BE OUT
+
** 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].
-
HOW UNIVERSE BE OUT
+
** Update [[hcard-brainstorming]] on element specific parsing rules
-
HOW MAKE THING BE OUT
+
** Update X2V, hKit, Operator accordingly
-
HOW MAKE ANYTHING BE OUT
+
** Write test cases accordingly
-
HOW MAKE EVERYTHING BE OUT
+
** Update [[hcard-parsing]] accordingly
-
HOW MAKE UNIVERSE BE OUT
+
* draft hCalendar 1.0.1: [[hcalendar|hCalendar spec]] '''next-actions''':
-
HOW THING OUT
+
** <del datetime="2009-10-03">resolve all outstanding [[hcalendar-issues]] into [[hcalendar-issues-resolved]]</del>
-
HOW ANYTHING OUT
+
** 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.
-
HOW EVERYTHING OUT
+
** draft [[hcalendar-1-0-1]] by starting with [[hcalendar-1-0]] and incrementally incorporating [[hcalendar-brainstorming]] targeted for 1.0.1
-
HOW UNIVERSE OUT
+
** incorporate [[hcalendar-feedback]]
-
HOW MAKE THING OUT
+
** 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.
-
HOW MAKE ANYTHING OUT
+
** 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.
-
HOW MAKE EVERYTHING OUT
+
** significantly update and thoroughly specify [[hcalendar-parsing]] with [[value-class-pattern]] as a required feature
-
HOW MAKE UNIVERSE OUT
+
** formally document [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
-
HOW THING BE OUT
+
** 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.
-
HOW ANYTHING BE OUT
+
** [[hcalendar-examples]]
-
HOW EVERYTHING BE OUT
+
*** make sure all hCalendar examples that reference whole days use best international/accessible date format of YYYY-MM-DD
-
HOW UNIVERSE BE OUT
+
*** add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
-
HOW MAKE THING BE OUT
+
** Write [[compound-parsing]] by abstracting commonalities between [[hcard-parsing]] and [[hcalendar-parsing]].
-
HOW MAKE ANYTHING BE OUT
+
* draft hReview 0.4
-
HOW MAKE EVERYTHING BE OUT
+
* resolve hAtom issues
-
HOW MAKE UNIVERSE BE OUT
+
* co-edit hAtom per permission from David Janes
-
HOW THING OUT
+
* draft [[hAtom]] 0.2
-
HOW ANYTHING OUT
+
** Clarify that "published" property values may omit seconds, and that converters to Atom are expected to imply ":00" seconds.
-
HOW EVERYTHING OUT
+
* add sections for comments/opinion from community as well as issues subsection
-
HOW UNIVERSE OUT
+
* solicit feedback
-
HOW MAKE THING OUT
+
* when sufficient consensus and issue resolution achieved, archive previous versions of specs, and update spec pages accordingly.
-
HOW MAKE ANYTHING OUT
+
 
-
HOW MAKE EVERYTHING OUT
+
==== social network portability ====
-
HOW MAKE UNIVERSE OUT
+
Iterate on:
-
HOW THING BE OUT
+
* [[social-network-portability]]
-
HOW ANYTHING BE OUT
+
* [[hcard-supporting-user-profiles]]
-
HOW EVERYTHING BE OUT
+
* [[hcard-xfn-supporting-friends-lists]]
-
HOW UNIVERSE BE OUT
+
 
-
HOW MAKE THING BE OUT
+
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 MAKE ANYTHING BE OUT
+
* how to author/publish hCard user profiles - write this up in [[hcard-authoring]] first (see below) and then use that content.
-
HOW MAKE EVERYTHING BE OUT
+
* how to author/publish hCard+XFN friends lists - write this up in [[hcard-xfn-authoring]] (see below) and then use that content.
-
HOW MAKE UNIVERSE BE OUT
+
* 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 THING OUT
+
* 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)
-
HOW ANYTHING OUT
+
** notes/thoughts on hCard+XFN supporting friends list parsing captured here for now:
-
HOW EVERYTHING OUT
+
*** 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.
-
HOW UNIVERSE OUT
+
**** 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.
-
HOW MAKE THING OUT
+
*** consider parsing within a friends list page, any links that are rel="next" and rel="prev" to iterate over the whole list.
-
HOW MAKE ANYTHING OUT
+
 
-
HOW MAKE EVERYTHING OUT
+
==== foldup cheatsheet ====
-
HOW MAKE UNIVERSE OUT
+
'''next actions''':
-
HOW THING BE OUT
+
* gather feedback on current foldup [[pocket-cheat-sheet|pocket cheatsheet]]
-
HOW ANYTHING BE OUT
+
* document the [[pocket-cheat-sheet-feedback|feedback on the pocket cheatsheet]]
-
HOW EVERYTHING BE OUT
+
* provide printing recommendations for anyone to download and print their own
-
HOW UNIVERSE BE OUT
+
** 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)
-
HOW MAKE THING BE OUT
+
* update cheatsheet to include new [[value-class-pattern]] uses
-
HOW MAKE ANYTHING BE OUT
+
* give feedback to Erin or ask for volunteers to create a new cheatsheet, iterate, print more to have on hand, fold, distribute.
-
HOW MAKE EVERYTHING BE OUT
+
* discuss with [[User:Adactio]] and Hannah how to best create a UK/A4 version of the pocket cheatsheet
-
HOW MAKE UNIVERSE BE OUT
+
** preferably well in advance of dConstruct 2008 so that local cheatsheets can be printed.
-
HOW THING OUT
+
 
-
HOW ANYTHING OUT
+
==== *-authoring microformats wiki pages ====
-
HOW EVERYTHING OUT
+
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
-
HOW UNIVERSE OUT
+
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
-
HOW MAKE THING OUT
+
** instructions for all other hCard properties
-
HOW MAKE ANYTHING OUT
+
** a tutorial on creating an hCard for your site
-
HOW MAKE EVERYTHING OUT
+
*** specific instructions for common blogging platforms
-
HOW MAKE UNIVERSE OUT
+
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
-
HOW THING BE OUT
+
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.
-
HOW ANYTHING BE OUT
+
* [[hcard-xfn-authoring]] - '''next-action''': draft by starting from hCard+XFN instructions in [[hcard-examples]].
-
HOW EVERYTHING BE OUT
+
* [[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.
-
HOW UNIVERSE BE OUT
+
* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].
-
HOW MAKE THING BE OUT
+
* *-authoring for other reasonably well established microformats:
-
HOW MAKE ANYTHING BE OUT
+
** [[xfolk-authoring]], [[hatom-authoring]]
-
HOW MAKE EVERYTHING BE OUT
+
 
-
HOW MAKE UNIVERSE BE OUT
+
==== help with microformat examples in the wild ====
-
HOW THING OUT
+
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:
-
HOW ANYTHING OUT
+
* Flickr.com (3.5m hCards)
-
HOW EVERYTHING OUT
+
* Upcoming.org (100k hCalendar events, 100k hCard venues)
-
HOW UNIVERSE OUT
+
** home page
-
HOW MAKE THING OUT
+
* Eventful.com (100k hCalendar events, 100k hCard venues)
-
HOW MAKE ANYTHING OUT
+
* Yahoo! Tech (300k products with hReviews)
-
HOW MAKE EVERYTHING OUT
+
* JudysBook.com (???k hReviews)
-
HOW MAKE UNIVERSE OUT
+
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.
-
HOW THING BE OUT
+
 
-
HOW ANYTHING BE OUT
+
==== advocacy for obvious sites ====
-
HOW EVERYTHING BE OUT
+
* [[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 ;)
-
HOW UNIVERSE BE OUT
+
** dodgeball.com (hCard + XFN + hAtom for profiles, hCard + hReview for venues)
-
HOW MAKE THING BE OUT
+
** write essay on [[open-data-more-important-than-open-source]] - and a shorthand URL too.
-
HOW MAKE ANYTHING BE OUT
+
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open source.
-
HOW MAKE EVERYTHING BE OUT
+
*** open data &gt; open source
-
HOW MAKE UNIVERSE BE OUT
+
*** "open information" vs "open source"
-
HOW THING OUT
+
*** 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
-
HOW ANYTHING OUT
+
*** if the data is open you can always export it and consume it in any number of open source systems
-
HOW EVERYTHING OUT
+
*** that's why open data is MUCH more important than open source
-
HOW UNIVERSE OUT
+
*** 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.
-
HOW MAKE THING OUT
+
*** if the data was open, anyone could rebuild an accessible version
-
HOW MAKE ANYTHING OUT
+
*** faqs / misconceptions:
-
HOW MAKE EVERYTHING OUT
+
**** eschipul: @tantek - creating microformats is easier. consuming microformats is unfortunately not easier.
-
HOW MAKE UNIVERSE OUT
+
***** 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]].
-
HOW THING BE OUT
+
** write essay on [[open-data-more-important-than-open-apis]] - and a shorthand URL too
-
HOW ANYTHING BE OUT
+
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open APIs.
-
HOW EVERYTHING BE OUT
+
*** 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.
-
HOW UNIVERSE BE OUT
+
 
-
HOW MAKE THING BE OUT
+
=== help implementers ===
-
HOW MAKE ANYTHING BE OUT
+
* wordpress improvements
-
HOW MAKE EVERYTHING BE OUT
+
** WP admin for new profiles
-
HOW MAKE UNIVERSE BE OUT
+
*** should simply read blog URL - '''next-action''': make sure a bug/feature request is filed with wordpress.org
-
HOW THING OUT
+
*** look for hCards and parse them
-
HOW ANYTHING OUT
+
 
-
HOW EVERYTHING OUT
+
* [http://gmpg.org/xfn/creator XFN Creator] localizations
-
HOW UNIVERSE OUT
+
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
-
HOW MAKE THING OUT
+
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
-
HOW MAKE ANYTHING OUT
+
** Add rel="alternate" href="creator-ru" &lt;link&gt;s to the other XFN Creators.
-
HOW MAKE EVERYTHING OUT
+
 
-
HOW MAKE UNIVERSE OUT
+
* Conference Schedule Creator
-
HOW THING BE OUT
+
** '''next-actions''': Review Dmitry Baranovskiy's [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] and give him feedback per how well it:
-
HOW ANYTHING BE OUT
+
*** 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.
-
HOW EVERYTHING BE OUT
+
 
-
HOW UNIVERSE BE OUT
+
=== iterate on current microformats ===
-
HOW MAKE THING BE OUT
+
==== in general ====
-
HOW MAKE ANYTHING BE OUT
+
===== plain language intros =====
-
HOW MAKE EVERYTHING BE OUT
+
For [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xoxo|XOXO]] to start with, write up:
-
HOW MAKE UNIVERSE BE OUT
+
* 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]]
 +
 
 +
=== wiki cleanup ===
 +
==== for all microformat specs ====
 +
'''Next-actions''':
 +
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
 +
** [[hcard|hCard]] -
 +
*** [[hcard-examples-in-the-wild]] group/sort by individuals,  organizations, and hosting sites. Consider moving largest subsection to its own page as well.
 +
** [[rel-tag]]
 +
** [[xoxo]]
 +
 
 +
==== update specification section organization ====
 +
'''Goal''': greater approachability/readability of microformats specs by a broader audience.
 +
 
 +
Reference:
 +
* [[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
 +
#* Must be comprehensive enough to "print and read"
 +
#* Must detail authorship/editorship
 +
#* 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
 +
# Update existing specifications with the new intro/headers structure.
 +
## [[hcard|hCard]]
 +
## [[hcalendar|hCalendar]]
 +
## [[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 ====
 +
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.
 +
 
 +
Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (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: [http://microformats.org/wiki/hcalendar#Implementations 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''':
 +
* [[hcard-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
 +
* [[hreview-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
 +
* [[hatom-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
 +
* [[xfolk-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
 +
 
 +
==== reorg Examples in the Wild sections ====
 +
Work with community to:
 +
* include more *key* details per example, e.g. precise or estimates of counts for services
 +
* collate/sort examples in the wild by
 +
** hosting services - where users/people actively contribute to the growth (e.g. Flickr profile hCards)
 +
** publishing services - where lots of data is published from some datasource/database (e.g. Yahoo! Local)
 +
** companies/groups/organizations member pages (and their own) - pages for a group's site where they list members or employees (e.g. Technorati staff page)
 +
** individiual companies/organizations contact info pages
 +
** individual people's contact info pages
 +
* of course at some point this won't scale, but that will be a very good problem to have, and by then I'm sure we'll have services to point to that provide queries and search results for all this data.
 +
 
 +
=== site usability ===
 +
* 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.
 +
 
 +
=== introduction / community ===
 +
* microformats-discuss *
 +
** introductory email template for 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.
 +
* update and add details/simplifications to [[process]] given the past several months of experience. in particular:
 +
** clarify requirement (MUST rather than SHOULD) of *-examples, *-formats, before any *-brainstorming. 
 +
** Add details of encouragement to experiment with simple semantic class names from *-brainstorming proposals to gain real world experience with real world content.
 +
** note SHOULD prerequisite of use of all relevant microformats on real world web pages, along with documenting such use in respective "Examples in the Wild" sections, before proposing any new microformats.
 +
 
 +
==== posh improvement ====
 +
* Create a page to answer the question "[[how-should-i-markup]]"
 +
* consider creating a process/encouragement for collecting individual [[posh]] practices and examples, like a folksonomy of semantic HTML and semantic class names.
 +
 
 +
==== principles and process ====
 +
Create the following pages and document/fill them with content from other pages, email lists, and [[presentations]].
 +
* [[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
 +
* resolve [[process-issues]]
 +
 
 +
==== 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)
 +
*** add rel="profile" to the [[xmdp-profile]].
 +
** ability/suggestion to reference an XMDP using &lt;a href&gt; in addition to &lt;link&gt;
 +
 
 +
==== community mark ====
 +
* Can we make "microformat" and "microformats" into [http://factoryjoe.com/blog/2006/01/14/the-case-for-community-marks/ Community Marks]?
 +
 
 +
==== document issue resolutions ====
 +
* Prefixing has already been considered and rejected for microformats in general.  Note [[naming-conventions]], limited vocabulary, and exceptions made for [[hatom|hAtom]] and how we went about doing so.
 +
 
 +
=== emerging microformats ===
 +
* [[directions]]
 +
* [[citation]]
 +
* [[hlisting|hListing]]
 +
* [[media-info]]
 +
* [[licensing]]
 +
'''Next-actions''' for each emerging microformat (one at a time)
 +
* review all microformats-email on the new microformat
 +
* determine where new microformats is "stuck" in the process
 +
* brainstorm about how to improve process (or documentation thereof) to get the effort unstuck
 +
* work with community to move the microformat forward through the process, iterating/clarifying the [[process]] as necessary
 +
 
 +
=== new microformat requests ===
 +
* 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
 +
** 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]].
 +
 
 +
=== document microformats history ===
 +
Document microformats [[history]], including:
 +
* dates and origins of microformats, names, terms
 +
* examples and formats for established microformats like [[hcard|hCard]], [[hcalendar|hCalendar]], [[xfn]], [[rel-license]], [[xoxo]]
 +
 
 +
=== other ===
 +
* Add XPath equivalents where appropriate in [[hcard-parsing]]
 +
 
 +
==Ryan==
 +
=== wiki cleanup ===
 +
* <s>possibly move dead proposals off of homepage?</s>
 +
 
 +
=== hCalendar/hCard/hReview creator improvements ===
 +
* get all creators working in IE/Win, IE/Mac, Safari/OSX.3
 +
 
 +
=== other ===
 +
* add an example of how to use DURATION in hcalendar see http://www.policyawareweb.org/2005/ftf2/paw-mtg#item15) -> verify http://svn.lifelint.com/hcalendar_tests/calendar-todo-multiple-attendees-and-alarm.xml
 +
 
 +
=== rel-payment ===
 +
* update rel-payment to reference the IANA registry [http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02055.html]
 +
 
 +
=== 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 ==
 +
 
 +
=== General ===
 +
 
 +
* Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)
 +
* Work on a microformat for play-item (take a look at [[media-info-examples]])
 +
* Work on microformats tutorial for designers
 +
* Add support for OpenID to micformats wiki
 +
* <strike>Add support for [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to the microformats blog</strike>.
 +
* <strike>Read GTD (at least the first two chapters)</strike>.
 +
 
 +
=== Campaigns ===
 +
 
 +
* <strike>Get Blogger to support hAtom and hCard</strike>
 +
* <strike>Get LinkedIn to support hCard, hResume, hCalendar</strike> and XFN
 +
* Get XING to support <strike>hCard</strike>, hCalendar, hResume and XFN
 +
* Get <strike>Digg to support microformats</strike> (still need XFN).
 +
 
 +
=== 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" (see [http://factoryjoe.com/blog/2006/03/20/flocktails-for-flock/  Flocktails])
 +
* Better hCal support -- support many views of same hCal data on one page using XSLT
 +
* We need something that a designer/web programmer can come to and leave w/ 2 examples of each microformat that they can apply right away... a "microformats styleguide for designers", if you will.
 +
* invoicing microformat
 +
* better microformats wiki theme
 +
* 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 ==
 +
[[User:RobertBachmann|Robert Bachmann]]
 +
 
 +
=== XSLTs ===
 +
<ul>
 +
<li><strong>Test scripts</strong>
 +
<ul>
 +
<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>
 +
<li>
 +
Join all hfeed's inside a page (or a fragment thereof) into one feed using [http://greenbytes.de/tech/webdav/rfc4287.html#element.source atom:source] semantics.
 +
</li>
 +
<li>
 +
Extraction of <code>atom:content</code>, <code>atom:summary</code> and <code>atom:title</code>:
 +
* <code>atom:content</code> and <code>atom:summary</code> as HTML
 +
* <code>atom:content</code> and <code>atom:summary</code> as plain-text
 +
* <code>atom:title</code> as XHTML
 +
* <code>atom:title</code> as HTML
 +
</li>
 +
<li>Support for other XSLT engines:
 +
* .Net System.Xml
 +
* 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.
 +
</li>
 +
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
 +
* 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>
 +
** 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>
 +
** Having the possibility of GRDDL-ing hAtom to AtomOWL seems definitly interessting. I realy should implement this some day. - Robert Bachmann
 +
* 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.
 +
*** This could enable some nice JavaScript hacks. I should give hAtom2JSON a try. - Robert Bachmann
 +
</li>
 +
</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)
 +
</li>
 +
</ul>
 +
 
 +
== Brian Suda ==
 +
=== Citation Microformats ===
 +
* Add all my notes to the Wiki
 +
* Start the process of naming the properties using existing names
 +
 
 +
=== 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 ===
 +
* clean-up the MF FAQs
 +
* clean-up FAQs from the major microformats
 +
* pull Questions from the mailing list and document them to the FAQs and example
 +
 
 +
=== Microformats History ===
 +
* get early work from developer.technorati site
 +
** 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 ==
 +
 
 +
=== 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 ====
 +
# Improve understanding of what needs to be done for Wiki
 +
#* IMHO - this should be done here, in [[to-do]] incrementally. -Tantek
 +
# 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
 +
# 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. [http://www.rubyonrails.com/ 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 --[[User:RyanKing|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!
 +
 
 +
== Dan Connolly ==
 +
 
 +
[[User:DanC|DanC]] hopes to sync up on these tasks in [[irc]] roughly
 +
weekly, during Wednesday afternoon (Chicago time) "office hours". See also my [http://esw.w3.org/topic/DanConnolly esw todo list and someday pile].
 +
 
 +
* from SxSW in Austin
 +
** build a combined hcalendar/hcard profile; resolve issues in [[profile-uris]].
 +
*** with XSLT transformation to RDF
 +
** finish [[hcard-tests]]
 +
*** figure out [[include-pattern]] boundaries
 +
 
 +
* Medium term
 +
** sync [[hcalendar-tests]] and [http://www.w3.org/2002/12/cal/ RDF calendar] tests and CALSIFY
 +
*** reconsider RDF calendar naming conventions
 +
** update my CV/resume using [[hResume]] and [[citation-formats]]
 +
*** get an answer from the CALSIFY WG re [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0006.html dtstart and date vs datetime ] 21 Apr 2006
 +
*** refine [[hatom]] so that it's suitable for the workflow around the W3C homepage.
 +
 
 +
* from WWW2006
 +
** follow up on GRDDL as escape valve for microformats proposals, much like CSS was an escape valve for HTML tag proposals.
 +
 
 +
* Someday pile
 +
** set up a timezone registry based on wikipedia and semantic mediawiki. As discussed in [[datetime-design-pattern]], iCalendar's by-value timezone passing is broken. see [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0002.html reconsidering timezones in light of hCalendar and CALSIFY] and [http://dig.csail.mit.edu/breadcrumbs/node/91 Toward Semantic Web data from Wikipedia]
 +
** noodle on a playlist format and some of the media RSS stuff like [[media-info-brainstorming]],  [[media-metadata-examples]] (re playlists: XSPF, SMIL, RDF, and microformats 9 Sep 2005)
 +
** check out that hReview bug stuff...
 +
** noodle on [[meeting-minutes-brainstorming]] and [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the esw wiki].
 +
** noodle on clipboard scenarios, esp how RDFa works in the general case but isn't as author-friendly as domain-specific syntaxes.
 +
 
 +
[[User:DanC|DanC]] 15:39, 31 May 2006 (PDT)
 +
 
 +
== Chris Casciano ==
 +
 
 +
[[User:ChrisCasciano|ChrisCasciano]]
 +
 
 +
* get around to updating [[hatom-issues]] with some multi feed rules/exceptions.
 +
* <del>Update textpattern plugin with simple hreview support and get a new release out</del>
 +
* Redesign placenamehere.com and include hatom
 +
* Follow up with technorati folks on pingerati reviews getting lost (note: this will require publishing more reviews and theen watching them through the update process)
 +
* <del>prototype a NetNewsWire microformat extractor (CSS+AppleScript)</del>
 +
 
 +
== Drew McLellan ==
 +
 
 +
[[User:DrewMcLellan|DrewMcLellan]]
 +
 
 +
* Build an hReview profile for [http://allinthehead.com/hkit/ hKit] and test
 +
* Update the [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver extensions] to mirror recent changes in the online builders
 +
* <del>Publish an hCard to JSON service on [http://tools.microformatic.com/ tools.microformatic.com] using hKit.</del>
 +
* Further develop blog comment form hCard collection ideas.
 +
* Version of hReview creator using hKit to import business details from an hCard
 +
 
 +
== Christophe Ducamp (french localization) ==
 +
 
 +
[[Christophe Ducamp]]
 +
* seed "microformateurs group" and invite them to update http://microformateurs.org
 +
** 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.
 +
** find experts for peer-reviewing
 +
** find french CSS gurus to setup a nice Sandbox-CSS template on Wordpress
 +
* translating the wiki
 +
** translate red links on [[Main_Page-fr]] and synchronize
 +
** find out microformateurs at ease on "the-wiki-way-translation", and ready to help on semi-anonymous-synchro
 +
* community-marketing -> pinko-marketing
 +
** public-relations towards french journalists and complete [[advocacy-fr|advocacy]] (especially [[hcard-advocacy-fr]] towards organizations.
 +
** 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
 +
* 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 ==
 +
 
 +
[[User:Phae|Frances Berriman]]
 +
 
 +
* Clean up this todo list (meta!)
 +
** Move alumni admin tasks out, and into a 'up for grabs' bucket (unless 100% specific to person).
 +
*** Ping anyone with specific tasks / nag
 +
* Proposal for page simplifications - notes, to expand to tasks later:
 +
** Need a way to push active formats (those in the process) to the fore, and push back stagnating items.
 +
** 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) ==
 +
 
 +
[[User:BenWest|bewest]]
 +
* fight spam
 +
* help tend wiki
 +
* documentation of semantic authoring techniques
 +
* researching the social problems relating to authorship and publishing on the web
 +
* development of new microformats in response to failing to meet the needs of the second with the first.
 +
 
 +
=== 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:
 +
* "boil the ocean" A huge task.  "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
 +
* microformats: more than one microformat
 +
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
 +
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
 +
* market: the locus of economic forces
 +
 
 +
: See [[glossary]]. [[User:AndyMabbett|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.
 +
* <strike>Start hatom creator.</strike> http://dichotomize.com/uf/hatom/creator.html
 +
* Code Reuse. These creators are downright handy, and I’ve reimplemented the vcard one on my own site. Instead, let’s make these widgetized. Let’s decide on a more or less canonical html structure and create some javascript that will create the desired microformat. Something as easy to use as new Microformat.hCard($('mycontainer')); would be awesome. Right now, if someone makes an improvement to the hCard creator, the other creators don’t get the benefit. Spec this out!
 +
* About Section. Is there an official creator page? If so, let’s point to that. The about paragraph is getting longer and longer with phrases like “which is based on…” repeated over and over.
 +
* Default all dates to “right now”. Provide an easy to use calendar type widget to change dates.
 +
* hAtom creator: Add multiple. It’d be nice to add an arbitrary number of entries.
 +
* hAtom creator: Optional feed enclosure. Check box to wrap the entry/entries in an hfeed.
 +
* Edit URI: Allow someone to enter a URI and edit whatever microformat is found on the page.
 +
* Optionals. If the format requires, say, a vcard, the creator can defer to an external URI or can trust the user to fill it in later.
 +
* Common stylesheet. I suppose this goes with the reuseable code idea… we have many great coders, we should be reusing eachothers’ work.
 +
* Use Amazon's ECS to pull in information about products when there is an ASIN in the item URI.
 +
 
 +
=== 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:
 +
* What Is This?
 +
* What can I do here?
 +
* Is there a demo?
 +
* Where can I learn more?
 +
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?
 +
* About the Community
 +
** Where to find information.
 +
** Who are the stake holders?
 +
** FAQs
 +
* Web/Architectural Philosophy
 +
** Community Principles
 +
** Why are we doing this?
 +
** XML and Namespaces
 +
** Semantic XHTML
 +
** Common Misconceptions
 +
** Concession and Disposition of Criticism
 +
** FAQs
 +
* Specs
 +
** Examples
 +
** Discussion
 +
** Exploration
 +
** Use Cases
 +
** Implementations
 +
** The spec itself.
 +
 
 +
* Tips and Tricks for Authoring ([[User:BenWest|BenWest]] 15:00, 9 Dec 2006 (PST))
 +
** how to author semantic html
 +
** choosing class names
 +
** using HTML's general extension mechanisms
 +
** advocating use
 +
** collaborating/reusing HTML
 +
** debugging HTML: use pastebin, separate out the relevant bits.
 +
** getting help from the community
 +
** applying Microformats.
 +
 
 +
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:
 +
* Belong to a microformat? (eg hcard-bestof)
 +
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
 +
(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 -- [[User:Cgriego|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:
 +
 
 +
* Microformat
 +
** Specification
 +
** Tutorial
 +
** Examples
 +
** Use cases
 +
** Reference
 +
** Discussion
 +
** Brainstorming (might be combined w/Discussion)
 +
** Implementations
 +
** Related Pages
 +
** Further Reading
 +
** All (Uses Mediawiki's "includes" to create a page including all sub pages; very useful for printing & reading offline)
 +
 
 +
These pages would be located respectively at
 +
 
 +
* http://microformats.org/wiki/hcard/
 +
** http://microformats.org/wiki/hcard/Specification
 +
** http://microformats.org/wiki/hcard/Tutorial
 +
** http://microformats.org/wiki/hcard/Examples
 +
** http://microformats.org/wiki/hcard/Use_cases
 +
** http://microformats.org/wiki/hcard/Reference
 +
** http://microformats.org/wiki/hcard/Discussion
 +
** http://microformats.org/wiki/hcard/Brainstorming
 +
** http://microformats.org/wiki/hcard/Implementations
 +
** http://microformats.org/wiki/hcard/Related_Pages
 +
** http://microformats.org/wiki/hcard/Further_Reading
 +
** http://microformats.org/wiki/hcard/All
 +
 
 +
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 ===
 +
<ul>
 +
<li>Support for other XSLT engines:
 +
* hAtom2Atom written using XSL 2.0
 +
</li>
 +
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
 +
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])
 +
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])
 +
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])
 +
</li>
 +
</ul>
 +
 
 +
=== Microformats Proposals ===
 +
 
 +
* 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.
 +
* 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.
 +
 
 +
== Henri Bergius ==
 +
 
 +
[[User:HenriBergius|Henri Bergius]]
 +
 
 +
* Add hKit support for automatically populating contact details into [http://www.openpsa.org/version2/openpsa/contacts.html OpenPsa Contacts] CRM
 +
* Implement Tail scripts for adding things into Midgard
 +
 
 +
== Justin Thorp ==
 +
* Start researching examples for a To-do microformat
 +
 
 +
== [[User:MarkLentczner|Mark Lentczner]] ==
 +
 
 +
* Get Second Life's event web pages to have proper event microformats data
 +
** Add [[hcard|hCard]] to profile pages
 +
** Add [[hcalendar|hCalendar]] to events listings
 +
* Start pinging pingerati.net/ping/$url when pages are updated
 +
* Collaborate on designing how to integrate microformats, metadata and objects in [http://secondlife.com/ Second Life].
 +
 
 +
== [[User:DerrickPallas|Derrick Pallas]] ==
 +
=== microformat proposal: dependancy ===
 +
* looking for examples of directed graphs on the web
 +
* applications in
 +
** software engineering
 +
*** automatically build library dependency trees
 +
*** distribute security alerts to people that link to your code
 +
** any directed, acyclic graph
 +
*** getting dressed in the morning
 +
*** cooking
 +
* orthogonal to xfn
 +
** people don't have versions
 +
*** libfoo requires libbar-2.0 or later
 +
** people don't have optional relationships
 +
*** ex: at build time, compile in SSL support if present
 +
** people don't have exclusive-or relationships
 +
*** ex: in Gentoo, syslog, syslog-ng, and metalog satisfy virtual/syslog
 +
*** ex: the Ruby library RMagick requires ImageMagick xor GraphicsMagick
 +
 
 +
== [[User:PaulDowney|Paul Downey]] ==
 +
* building a generic Javascript parser
 +
* bundling parser as a [http://tiddlywiki.org TidlyWiki] plugin for hCards
 +
* 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

Revision as of 06:50, 20 August 2013

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

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:

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 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.

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. Help publishers with established microformats: hCard, xfn, rel-tag, hCalendar, hReview, xFolk
  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. Emerging in-demand microformats: hResume, hListing, citation, media-info using abovementioned process and principles improvements.
  9. New microformat requests
  10. Document microformats history.
  11. Other

protect the community

help publishers

solve problems blocking publishers

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

help implementers

iterate on current microformats

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:

wiki cleanup

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

introduction / community

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

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

new microformat requests

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: Wednesday, December 31st, 1969

Views