To Do

(Difference between revisions)

Jump to: navigation, search
(microformats2 updates: need what-are-microformats)
Current revision (20:13, 12 October 2017) (view source)
(Tantek: update with focus on mf2)
 
Line 217: Line 217:
== Tantek ==
== Tantek ==
-
I'm keeping a few microformats related to-do items here both for my own convenience, and for folks looking to help out with small tasks. If so, just create a new section with your name, and and maybe copy the item there, and put your name next to the item in my list.  We'll figure this out as we go along.  Thanks,  [http://tantek.com Tantek].
+
I'm keeping microformats related to-do items here both for my own convenience, and for folks looking to help out. - [http://tantek.com Tantek].
=== overall priority ordering ===
=== overall priority ordering ===
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
-
# Help publishers with established microformats: [[hcard|hCard]], [[xfn]], [[rel-tag]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
+
# Update [[microformats2-parsing]] with resolved [[microformats2-parsing-issues]]
# Help implementers with established microformats
# Help implementers with established microformats
# Iterate on existing established microformats, resolve issues/feedback etc.
# Iterate on existing established microformats, resolve issues/feedback etc.
Line 227: Line 227:
# Site usability of microformats.org top-down as an entry point
# Site usability of microformats.org top-down as an entry point
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments
-
# Emerging in-demand microformats: [[hresume|hResume]], [[hlisting|hListing]], [[citation]], [[media-info]] using abovementioned process and principles improvements.
+
# Wrap up classic microformats documentation
-
# New microformat requests
+
# Document microformats [[history]].
# Document microformats [[history]].
# Other
# Other
Line 250: Line 249:
**** [[to-do]]
**** [[to-do]]
-
=== help publishers ===
+
=== update microformats2-parsing with resolved issues ===
-
==== solve problems blocking publishers ====
+
Update [[microformats2-parsing]] with resolved [[microformats2-parsing-issues]]
-
* [[value-class-pattern]]
+
 
-
** <del>drafted</del>
+
=== help implementers ===
-
** <del>[[value-class-date-time-tests]] - finish writing date and time tests</del>
+
Update all these tasks for [[microformats2]]:
-
** <del>put out call for review, implementation,</del> and value-title tests
+
 
 +
* wordpress improvements
 +
** WP admin for new profiles
 +
*** should simply read blog URL - '''next-action''': make sure a bug/feature request is filed with wordpress.org
 +
*** look for hCards and parse them
 +
 
 +
* [http://gmpg.org/xfn/creator XFN Creator] localizations
 +
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
 +
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
 +
** Add rel="alternate" href="creator-ru" &lt;link&gt;s to the other XFN Creators.
 +
 
 +
* Conference Schedule Creator
 +
** '''next-actions''': Review Dmitry Baranovskiy's [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] and give him feedback per how well it:
 +
*** 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.
 +
 
 +
=== wiki cleanup ===
 +
Update all these tasks for [[microformats2]]:
 +
 
 +
==== 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 ===
 +
Update all these tasks for [[microformats2]]:
 +
 
 +
* 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 ===
 +
Update all these tasks for [[microformats2]]:
 +
 
 +
* 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 ===
 +
Update all these tasks for [[microformats2]]:
 +
 
 +
* [[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 ===
 +
Update all these tasks for [[microformats2]]:
 +
 
 +
* expense reports (really just a list of "expense" items), [http://flickr.com/photos/edyson/56774178/ requested by ED], should look at UBL as a pre-existing format
 +
* 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]].
 +
 
 +
=== wrap up classic microformats documentation ===
 +
* use these tasks to come up with any necessary or useful equivalents for [[microformats2]] specifications and resources.
===== minor update current specifications =====
===== minor update current specifications =====
Line 367: Line 506:
*** 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.
*** publishing/providing open data (e.g. microformats) can be done by any HTML author (yes, you), whereas providing/publishing open APIs requires programming expertise, resouces, and support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.
-
=== help implementers ===
 
-
* wordpress improvements
 
-
** WP admin for new profiles
 
-
*** should simply read blog URL - '''next-action''': make sure a bug/feature request is filed with wordpress.org
 
-
*** look for hCards and parse them
 
-
 
-
* [http://gmpg.org/xfn/creator XFN Creator] localizations
 
-
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
 
-
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
 
-
** Add rel="alternate" href="creator-ru" &lt;link&gt;s to the other XFN Creators.
 
-
 
-
* Conference Schedule Creator
 
-
** '''next-actions''': Review Dmitry Baranovskiy's [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] and give him feedback per how well it:
 
-
*** Makes it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V.  Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.
 
-
 
-
=== iterate on current microformats ===
 
==== in general ====
==== in general ====
===== plain language intros =====
===== plain language intros =====
Line 465: Line 588:
'''Next-actions''':
'''Next-actions''':
* Draft *-parsing for all reasonably well adopted microformats: [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]
* 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 ===

Current revision

Contents

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

microformats2 updates

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

wiki gardening

trim fixups

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

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

simplify pages

Review pages, from the Main Page on down and:

Examples of simplified pages:

Pages to simplify:

remove broken URLs

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

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

TODO (mark as done when done):

incorporate things expected to break

shortlink spec

The rel=shortlink spec:

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

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

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


more documentation and research

extract from 1989 timbl proposal


microformats specific

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

for all microformats

hCard

hCalendar

Add support to open source calendar projects

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

hReview

hCalendar/hCard/hReview editor

hAtom

WordPress patches for microformats

Yahoo Open Source Library Patches

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

Drupal patches for microformats

Adding Microformats to Existing Pages

rel-tagging on Wikipedia

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

Glossary

Add to the glossary.

hAtom tutorial

Finish the hatom-tutorial.

wiki gardening

Spelling

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

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

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

More American and British English spelling differences

Admins

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

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

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

Website Improvements

Wiki improvements

Tantek

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

overall priority ordering

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

protect the community

update microformats2-parsing with resolved issues

Update microformats2-parsing with resolved microformats2-parsing-issues

help implementers

Update all these tasks for microformats2:

wiki cleanup

Update all these tasks for microformats2:

for all microformat specs

Next-actions:

update specification section organization

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

Reference:

Next-actions:

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

reorganizing Implementations sections

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

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

Next-actions:

reorg Examples in the Wild sections

Work with community to:

site usability

Update all these tasks for microformats2:

introduction / community

Update all these tasks for microformats2:

posh improvement

principles and process

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

profiles

community mark

document issue resolutions

emerging microformats

Update all these tasks for microformats2:

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

new microformat requests

Update all these tasks for microformats2:

wrap up classic microformats documentation

minor update current specifications

social network portability

Iterate on:

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

foldup cheatsheet

next actions:

*-authoring microformats wiki pages

help with microformat examples in the wild

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

advocacy for obvious sites

in general

plain language intros

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

In particular for XOXO, Angus McIntyre suggested:

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

exploratory discussions
CSS enhancements for

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

update affiliations
profile URLs

hCard

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

hCalendar

Next-actions:

hReview

Next-actions:

rel-tag

Next-actions:

rel-me

Next-actions:

hAtom

Next-actions:

summary Examples in the Wild page

parsing

Next-actions:

document microformats history

Document microformats history, including:

other

Ryan

wiki cleanup

hCalendar/hCard/hReview creator improvements

other

rel-payment

hcalendar

Dimitri Glazkov

Chris Messina

General

Campaigns

Wishlist

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

Robert Bachmann

Robert Bachmann

XSLTs

Brian Suda

Citation Microformats

X2V

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

WARNINGS and ERROR

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

FAQ

Microformats History

additions to the wiki

Mark Rickerby

Current Tasks

Wishlist

Ernest Prabhakar

Wiki-Thon Proposal

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

Goals

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

Agenda (Wishlist)

In parallel:

Dan Connolly

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

DanC 15:39, 31 May 2006 (PDT)

Chris Casciano

ChrisCasciano

Drew McLellan

DrewMcLellan

Christophe Ducamp (french localization)

Christophe Ducamp

Frances Berriman

Frances Berriman

Ben West (bewest)

bewest

Expore Microformat Deployment Issues

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

Vocabulary

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

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

Creators

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

Information Architecture

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

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

Support Pages

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

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

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

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

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

Mike Schinkel's Comments

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

These pages would be located respectively at

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

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

Matt Dertinger (Thewhoo)

User:Thewhoo

hAtom2Atom

Microformats Proposals

Henri Bergius

Henri Bergius

Justin Thorp

Mark Lentczner

Derrick Pallas

microformat proposal: dependancy

Paul Downey

Rob Manson

Clay Newton

Ben Ward

Recurring

Currently

Next Actions

Ketan Majmudar

Activites

To Do was last modified: Thursday, October 12th, 2017

Views