Microformats Wiki - User contributions [en]

Main Page

2006-05-08T18:42:35Z

Brush: /* Exploratory discussions */ - added meeting-minutes-brainstorming

__NOTOC__
__NOTOC__
= Microformats Wiki =

'''Please read [[how-to-play]] before making any edits.'''

'''Please read [[process]] before proposing any new microformats.'''

== Introduction ==

What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]], [[presentations]], and [[podcasts]] are also a good place for some background reading as well. Frequently asked questions are answered in the [[faq]]. Want something or want to contribute? Help with things [[to-do]]. Want to learn more in person? Check out microformats [[events]].

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]
* [[rel-home]] {{NewMarker}}

== Design Patterns ==

Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''

* [[abbr-design-pattern]]
* [[class-design-pattern]]
* [[datetime-design-pattern]]
* [[existing-classes|class names defined across all microformats]]
* [[include-pattern]] {{NewMarker}}
* [[rel-design-pattern]]

== Exploratory discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*[[attention]]
*[[blog-description-examples]]
*[[blog-info-examples]]
*[[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]] (yields [[hatom|hAtom]])
*[[book-examples]], [[book-formats]], [[book-brainstorming]]
*[[chat-examples]], [[chat-formats]]
*[[citation|citation microformat overview]], [[citation-examples]], [[citation-formats]], [[citation-brainstorming]]
*[[comment-problem]], [[comment-examples]], (need to extract from [[comments-formats]])
*[[directions-examples]] {{NewMarker}}
*[[directory-inclusion-examples]], [[directory-inclusion-formats]]. (see also [[rel-directory]])
*[[distributed-conversation]], [[distributed-conversation-brainstorming]], [[distributed-conversation-examples]], [[distributed-conversation-formats]]
*[[forms-examples]]
*[[genealogy-formats]]
*[[hash-examples]]
*[[last-modified-examples]], [[last-modified-formats]], [[last-modified-brainstorming]]
*[[hlisting-proposal]], [[hlisting-feedback]] {{NewMarker}}
**[[listing-examples]], [[listing-formats]], [[listing-brainstorming]]
*[[location-formats]]. (see also [[adr]] and [[geo]])
*[[media-info-examples]]
*[[meeting-minutes-examples]], [[meeting-minutes-formats]], [[meeting-minutes-brainstorming]]
*[[mfo-examples]]
*[[music-examples]]
*[[other-formats]]
*[[photo-note-examples]]
*[[recipe-examples]]
*[[requirements-testing]], [[requirements-testing-examples]]
*[[rest-examples]]
*[[resume-brainstorming]], [[resume-formats]]
*[[review-examples]], [[review-formats]] (yielded the [[hreview|hReview]] draft)
*[[search-results-example]]
*[[show-brainstorming]]
*[[showroll-brainstorming]]
*[[table-examples]]
*[[tagspeak-examples]]
*[[transit-table-examples]]
*[[uid]]
*[[widget-examples]], [[widget-brainstorming]]
*[[wiki-formats]]
*[[work-of-art]] {{NewMarker}}
*[[xmdp-brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]] {{NewMarker}}

== Tools & Test Cases & Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[[vcard-implementations]], [[vcard-errata]]
*[[icalendar-implementations]]
*[[faqs-for-rdf]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]] {{NewMarker}}
* [[to-do]]
* [[marked-for-deletion]]

== microformats wiki in other languages ==

You may read and edit microformats articles in <del>many different</del> other languages

=== microformats wiki languages with over 2 articles ===

* [[Main_Page-fr|Français (French)]]
* [[Main_Page-jp|日本語 (Japanese)]] {{NewMarker}}
* [[Main_Page-sp|Español (Spanish)]] {{NewMarker}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

meeting-minutes-brainstorming

2006-05-08T18:40:35Z

Brush: /* See Also */

= Meeting Minutes Brainstorming =

This is an outline of ideas for how to structure meeting minutes structure, using existing microformats as much as possible.

A schematic outline of thinking for hMinutes:

hMinutes and xoxo root class
* "header" information:
** title
** vCard for organization, location
** date/time
** hParticipants
*** set of vCards
*** roles in this context
* list of topics (can be extensibly classed, also tagged using relTag)
** include title, description, etc.
** include hDecisions in text or as subitems
*** hDecisions also include hParticipants, with roles contextually identifying "proposer", "seconder", "opponent", etc. (locally extensible)
*** hDecisions have their own tags, or inherit topic's tag.
** Action items using vTodo from iCal spec, in text or as subitems.
* include vEvents for next meetings? special class to notate?

== hParticipants ==
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

== hDecision ==
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting? Use the "include" pattern?
* Should have "description" class, if not included tag is used?

== hMinutes ==
Example idea:
<pre><nowiki>
<ul class="xoxo hminutes">
<li class="header">
<ul>
<li>ABC, Inc.
...
</li>
<li class="meeting">
<dl>
<dt>description</dt><dd>Annual Meeting</dd>
<dt>location</dt><dd class="vcard">...</dd>
</dl>
<abbr class="dtstart" title="DT2006...">April 10, 2006; 7pm
<li class="hparticipants">
Participants:
<ul>
<li class="vcard">
John Doe,
Scribe and
Volunteer
...
</li>
<li class="vcard">
Mary Smith,
Facilitator and
Director
</li>
...
</ul>
</li>
</ul>
<li class="agenda">Meeting Summary:
<ol>
<li>
<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag">Our first topic</a>
<dt>
<dl class="description">
Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.





There is also this action item ''do example markup''


</dl>
<dt>
<ul>
<li>
... subpoints ...
</li>
</ul>
</li>
<li>
... next topic ...
</li>
</ol>
</li>
</ul>
</nowiki></pre>

= See Also =
''Link to related pages as they become available''
* [[meeting-minutes-examples]]
* [[meeting-minutes-formats]]
* -proposal
* -microformat

meeting-minutes-brainstorming

2006-05-08T18:37:25Z

Brush: /* hDecision */

= Meeting Minutes Brainstorming =

This is an outline of ideas for how to structure meeting minutes structure, using existing microformats as much as possible.

A schematic outline of thinking for hMinutes:

hMinutes and xoxo root class
* "header" information:
** title
** vCard for organization, location
** date/time
** hParticipants
*** set of vCards
*** roles in this context
* list of topics (can be extensibly classed, also tagged using relTag)
** include title, description, etc.
** include hDecisions in text or as subitems
*** hDecisions also include hParticipants, with roles contextually identifying "proposer", "seconder", "opponent", etc. (locally extensible)
*** hDecisions have their own tags, or inherit topic's tag.
** Action items using vTodo from iCal spec, in text or as subitems.
* include vEvents for next meetings? special class to notate?

== hParticipants ==
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

== hDecision ==
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting? Use the "include" pattern?
* Should have "description" class, if not included tag is used?

== hMinutes ==
Example idea:
<pre><nowiki>
<ul class="xoxo hminutes">
<li class="header">
<ul>
<li>ABC, Inc.
...
</li>
<li class="meeting">
<dl>
<dt>description</dt><dd>Annual Meeting</dd>
<dt>location</dt><dd class="vcard">...</dd>
</dl>
<abbr class="dtstart" title="DT2006...">April 10, 2006; 7pm
<li class="hparticipants">
Participants:
<ul>
<li class="vcard">
John Doe,
Scribe and
Volunteer
...
</li>
<li class="vcard">
Mary Smith,
Facilitator and
Director
</li>
...
</ul>
</li>
</ul>
<li class="agenda">Meeting Summary:
<ol>
<li>
<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag">Our first topic</a>
<dt>
<dl class="description">
Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.





There is also this action item ''do example markup''


</dl>
<dt>
<ul>
<li>
... subpoints ...
</li>
</ul>
</li>
<li>
... next topic ...
</li>
</ol>
</li>
</ul>
</nowiki></pre>

== See Also ==
''Link to related pages as they become available''
* [[meeting-minutes-examples]]
* [[meeting-minutes-formats]]
* -proposal
* -microformat

meeting-minutes-brainstorming

2006-05-08T18:32:23Z

Brush: /* hMinutes */ included full representation of hParticipants

= Meeting Minutes Brainstorming =

This is an outline of ideas for how to structure meeting minutes structure, using existing microformats as much as possible.

A schematic outline of thinking for hMinutes:

hMinutes and xoxo root class
* "header" information:
** title
** vCard for organization, location
** date/time
** hParticipants
*** set of vCards
*** roles in this context
* list of topics (can be extensibly classed, also tagged using relTag)
** include title, description, etc.
** include hDecisions in text or as subitems
*** hDecisions also include hParticipants, with roles contextually identifying "proposer", "seconder", "opponent", etc. (locally extensible)
*** hDecisions have their own tags, or inherit topic's tag.
** Action items using vTodo from iCal spec, in text or as subitems.
* include vEvents for next meetings? special class to notate?

== hParticipants ==
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

== hDecision ==
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting?
* Should it be possible to use [http://microformats.org/wiki/xoxo XOXO] ''inside'' the hDecision to give it structure? Hmmmm. Or should it be forced into multiple decisions?
* Should have "description" class, if not included tag is used?

== hMinutes ==
Example idea:
<pre><nowiki>
<ul class="xoxo hminutes">
<li class="header">
<ul>
<li>ABC, Inc.
...
</li>
<li class="meeting">
<dl>
<dt>description</dt><dd>Annual Meeting</dd>
<dt>location</dt><dd class="vcard">...</dd>
</dl>
<abbr class="dtstart" title="DT2006...">April 10, 2006; 7pm
<li class="hparticipants">
Participants:
<ul>
<li class="vcard">
John Doe,
Scribe and
Volunteer
...
</li>
<li class="vcard">
Mary Smith,
Facilitator and
Director
</li>
...
</ul>
</li>
</ul>
<li class="agenda">Meeting Summary:
<ol>
<li>
<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag">Our first topic</a>
<dt>
<dl class="description">
Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.





There is also this action item ''do example markup''


</dl>
<dt>
<ul>
<li>
... subpoints ...
</li>
</ul>
</li>
<li>
... next topic ...
</li>
</ol>
</li>
</ul>
</nowiki></pre>

== See Also ==
''Link to related pages as they become available''
* [[meeting-minutes-examples]]
* [[meeting-minutes-formats]]
* -proposal
* -microformat

meeting-minutes-brainstorming

2006-05-08T18:19:26Z

Brush: /* See Also */

= Meeting Minutes Brainstorming =

This is an outline of ideas for how to structure meeting minutes structure, using existing microformats as much as possible.

A schematic outline of thinking for hMinutes:

hMinutes and xoxo root class
* "header" information:
** title
** vCard for organization, location
** date/time
** hParticipants
*** set of vCards
*** roles in this context
* list of topics (can be extensibly classed, also tagged using relTag)
** include title, description, etc.
** include hDecisions in text or as subitems
*** hDecisions also include hParticipants, with roles contextually identifying "proposer", "seconder", "opponent", etc. (locally extensible)
*** hDecisions have their own tags, or inherit topic's tag.
** Action items using vTodo from iCal spec, in text or as subitems.
* include vEvents for next meetings? special class to notate?

== hParticipants ==
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

== hDecision ==
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting?
* Should it be possible to use [http://microformats.org/wiki/xoxo XOXO] ''inside'' the hDecision to give it structure? Hmmmm. Or should it be forced into multiple decisions?
* Should have "description" class, if not included tag is used?

== hMinutes ==
Example idea:
<pre><nowiki>
<ul class="xoxo hminutes">
<li class="header">
<ul>
<li>ABC, Inc.
...
</li>
<li class="meeting">
<dl>
<dt>description</dt><dd>Annual Meeting</dd>
<dt>location</dt><dd class="vcard">...</dd>
</dl>
<abbr class="dtstart" title="DT2006...">April 10, 2006; 7pm
<li class="hparticipants">
...
</li>
</ul>
<li class="agenda">
<ol>
<li>
<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag">Our first topic</a>
<dt>
<dl class="description">
Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.





There is also this action item ''do example markup''


</dl>
<dt>
<ul>
<li>
... subpoints ...
</li>
</ul>
</li>
<li>
... next topic ...
</li>
</ol>
</li>
</ul>
</nowiki></pre>

== See Also ==
''Link to related pages as they become available''
* [[meeting-minutes-examples]]
* [[meeting-minutes-formats]]
* -proposal
* -microformat

meeting-minutes-brainstorming

2006-05-08T18:18:35Z

Brush: Add modified brainstorm for format

= Meeting Minutes Brainstorming =

This is an outline of ideas for how to structure meeting minutes structure, using existing microformats as much as possible.

A schematic outline of thinking for hMinutes:

hMinutes and xoxo root class
* "header" information:
** title
** vCard for organization, location
** date/time
** hParticipants
*** set of vCards
*** roles in this context
* list of topics (can be extensibly classed, also tagged using relTag)
** include title, description, etc.
** include hDecisions in text or as subitems
*** hDecisions also include hParticipants, with roles contextually identifying "proposer", "seconder", "opponent", etc. (locally extensible)
*** hDecisions have their own tags, or inherit topic's tag.
** Action items using vTodo from iCal spec, in text or as subitems.
* include vEvents for next meetings? special class to notate?

== hParticipants ==
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

== hDecision ==
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting?
* Should it be possible to use [http://microformats.org/wiki/xoxo XOXO] ''inside'' the hDecision to give it structure? Hmmmm. Or should it be forced into multiple decisions?
* Should have "description" class, if not included tag is used?

== hMinutes ==
Example idea:
<pre><nowiki>
<ul class="xoxo hminutes">
<li class="header">
<ul>
<li>ABC, Inc.
...
</li>
<li class="meeting">
<dl>
<dt>description</dt><dd>Annual Meeting</dd>
<dt>location</dt><dd class="vcard">...</dd>
</dl>
<abbr class="dtstart" title="DT2006...">April 10, 2006; 7pm
<li class="hparticipants">
...
</li>
</ul>
<li class="agenda">
<ol>
<li>
<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag">Our first topic</a>
<dt>
<dl class="description">
Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.





There is also this action item ''do example markup''


</dl>
<dt>
<ul>
<li>
... subpoints ...
</li>
</ul>
</li>
<li>
... next topic ...
</li>
</ol>
</li>
</ul>
</nowiki></pre>

=== See Also ===
''Link to related pages as they become available''
* [[meeting-minutes-brainstorming]]
* [[meeting-minutes-formats]]
* -proposal
* -microformat

meeting-minutes-examples

2006-05-08T17:42:16Z

Brush: /* Proposal */ - move to -brainstorming

= Meeting minutes =
They're typed, they look good, but all the meaning (participants, decisions, action items, etc.) is impossible to glean automatically. Enter hMinutes (or whatever)!

== The Problem ==
''Meeting notes provide a wealth of semantic content, invaluable to organizations. Meeting notes are routinely recorded in intranets, and (with public organizations) on the internet; however, without semantic content it is very difficult to extract the specific information, analyze it, distribute it, or search it effectively. This investigation seeks to document how meeting minutes on the web are structured, towards a lightweight suite of microformats and format extensions for markup.''
== Participants ==
* ''Brush''

== Real-World Examples ==
''These are fairly random, selected for variety of approach. Research is not yet in-depth. Room for more!''

=== [http://www.geneontology.org/minutes/20050408_Pasadena.txt Gene Ontology Consortium] ===
*Abbreviated organization name
*Dates
*Location (locality, region)
*Next meeting date/location (to be confirmed)
*Participants
**Listed by group-affiliation
**Names in comma-delimited parentheses
**Some groups not represented, still listed (like regrets)
*Nested outline of items (XOXO!)
*Major topic -> subsidiary topic
**Includes introduction, by named presenter(s)
**Discussion item list
***Detailed (but flat) following of arguments pro and con
***Identified conclusions (decisions? not formal?)
***Certain items or references id specific people
**Action items
***listed after each topic
***assigned to a person (or to "everyone")
***Also summarized at end of minutes
***Previous action items listed, with status:
****done
****unresolvable
****in progress
****almost done
****other details, etc.
**Brainstorm section
*Next meetings:
**Types
**Dates
**Locations

=== [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] ===
*Organization, committee
*Date
*Time start/end
*Kind of meeting (ie. special meeting, as opposed to regular)
*Present, with roles:
**member/non-member
**President/Secretary
**organizational affiliations
**also plurally generic (ie. "Hospital Managers and citizens from the community, SEIU 1199NW delegation")
*Outline list (flat) of items
**"Call to order"
**"Oath of office" (ie. establishment of new official roles for individuals)
**Approval of previous minutes (special form of decision)
**Reports from managers/committees
**Authorizations for expenditures
**"Other business"
**Public comment
**Adjournment
*Decisions included in text of items
**motion made
**seconded
**approved unanimously
**included appointments to committees (changes in roles?)
*Items include one, sometimes more specifically referenced speakers

=== [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] ===
*Includes relatively unhelpful presentation-oriented table-of-contents link outline markup (more detail?)
*Title
*Date
*Location
*Attendees
**Affiliation
*High-level item
**Includes one-sentence summary
*Second-level item
**Issue
**Discussion
**Conclusion(s)
***Not clear distinction between decisions and action items
***Some action items attached to specific people

=== [http://mail.gnome.org/archives/foundation-list/2004-April/msg00008.html GNOME/Mozilla Meeting] ===
*Title (included two participating organizations)
*Date
*(Email, so "date sent out" included implicitly)
*Attendance
**Organizational affiliation
**minutes
**chair
*Regrets
*Actions (list)
*Discussion (list tree, no titles)
**Specific items inside each discussion item refer to specific person(s)
**Follow pros and cons of arguments

=== [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] ===
*Organization and committee
*form of meeting (ie. teleconference)
*Date
*Time start/end
*Attendance (noted that all were present throughout) with roles:
**member of committee
**member and chair
**non-member, board secretary
**non-member, general counsel
*XOXO-like outline of items
*"Resolved:" decisions for each item.
**vote count (ie. 4-0)
**who proposed
**who seconded
*Also included items deferred to later meetings

== Existing Practices ==
* ''Summary of common patterns discovered'': An informal "80/20" analysis of most commonly used elements:
** 80% used items are mostly extremely common:
*** Title (organization/committee name, sometimes location)
*** Date (time is fairly common as well)
*** Participants (almost always include specific notation of Chair and Secretary, regrets also really common)
*** Point list of topics
**** Often flat, but also often nested
**** Some models (specifically formal meetings) have clear, regular division of kinds of topics (eg. reports from committees, approval of minutes, old business, new business, public comment, etc.)
*** Decisions (usually include description of how vote broke down, movers, seconders, etc.)
*** Action items (who assigned to; sometimes status review, date due, etc.)
*** Next meeting(s) - fairly common
** The 20% portion is primarily specific kinds of topic divisions, specific categories of participants, categories of meetings (special, regular, business, ...), etc. These could be standardized for certain sets of applications without writing into the uformat per se.
* ''Other attempts to solve The Problem'': Does anyone have references to other schemae attempted to address this issue? How about a semantically marked up implementation!?
** All W3C meetings are recorded, as a matter of policy. There are zillions of teleconference and ftf meeting records. See [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the ESW wiki] for notes, patterns, and tools, especially [http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm the scribe.perl tool], Zakim, and RRSAgent. ''-DanC''
** The W3C tools assume the following structure, near as I can tell: (DanC, more advice?) (I've eliminated IRC-specific details)
*** Meeting: ''title''
*** Chair: ''name''
*** Scribe: ''name''
*** Agenda: ''URL of agenda - agendas are automatically formed using various tools, and are essentially a flat list of agenda items''
*** Present: ''comma-delimited list of names''
*** Regrets: ''pre-announced non-attendees''
*** Date: ''yup''
*** Topic: ''next in a flat list of agendums; topic name seems to often be (I think) in a well-formed format for reference to a centrally kept list (RDF or other?)''
*** Action: ''list, of, names'' '''to''' ''description of action'' <nowiki>[STATUS]</nowiki>
**** Status is optional
**** May be DONE, PENDING, DROPPED, with other synonyms
**** Again, this is well-tracked between meetings for the purpose of providing open action item lists
*** Resolved: ''description of decision made''
** The vCard spec includes a [http://www.w3.org/2002/12/cal/rfc2445#sec4.6.2 definition for vTodo]. I'm assuming that iCal-basic and hCalendar don't already include this part of the spec, so it could become the basis to an extension of the hCalendar uformat (or a new hTodo?) that defines action items. (Action item management is a core focus of the W3C technical tools above.) This would be integrated into hMinutes.

== Existing Formats ==

See [[meeting-minutes-formats]] for current standards for publishing meeting-minutes.

'''NOTE: This research should be done ''before'' brainstorming proposals.'''
''Does anyone have ideas? Besides some brainstorming at W3C, haven't found any current standards.''

== Proposal ==

''Moved to [[meeting-minutes-brainstorming]].''

It is probably better to first:
# analyze what are the 80/20 common elements of the examples above. '''Done, at least initially.'''
# complete the research of [[meeting-minutes-formats]]. '''Any other ideas on this?'''
# and then go about proposing a solution for the whole format, rather than parts of it, while attempting to reuse other [[microformats]] as much as possible. [http://tantek.com/ Tantek]

== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

meeting-minutes-formats

2006-05-08T17:38:56Z

Brush: /* Meeting Minutes: Existing Formats */ - See also

=Meeting Minutes: Existing Formats=

''I don't know of any fully described existing schema for meeting minutes; please help with this section!'' - Brush

* W3C has thought a bit about this, but doesn't appear to have completed any implementation
** [http://www.w3.org/2002/11/DAML-IOW#Specific Suggestions for using RDF/OWL] for marking up meeting records.
** What seem to be DanC's [http://www.w3.org/2000/11/mr76/ work on RDF schema for minutes], for use with W3C tools.
** A [http://esw.w3.org/topic/MeetingRecords wiki discussion page about Meeting Records] includes some "noodling" on meeting record ontology, as well as other resources at the end.
** These resources are based on the schema implicit in W3C's agenda, action item, and participation tracking agents, RSSAgent and Zakim, as noted in [[meeting-minutes-examples]].
* W3C's approach is focused on how to create usable data for computer assistance in meeting organization and recording.
** This means that it includes kinds of data that would otherwise be in the "20%" category according to our analysis, such as specific kinds of decision details, agenda preparation, further details on participation, etc. (See [http://esw.w3.org/topic/MeetingRecords wiki discussion page about Meeting Records] again, in particular.)
** Agenda preparation, meeting calling, etc. is more of a focus for W3C; a more comprehensive, extended role for meeting recording. Is this something we want to prepare for?

None of these seem to be a complete schema. What am I missing?

== See Also ==
* [[meeting-minutes-examples]]
* [[meeting-minutes-brainstorming]]

meeting-minutes-formats

2006-05-08T17:35:48Z

Brush: /* Meeting Minutes: Existing Formats */ - add some analysis of W3C's approach

meeting-minutes-examples

2006-05-08T17:28:53Z

Brush: /* Existing Formats */

= Meeting minutes =
They're typed, they look good, but all the meaning (participants, decisions, action items, etc.) is impossible to glean automatically. Enter hMinutes (or whatever)!

== The Problem ==
''Meeting notes provide a wealth of semantic content, invaluable to organizations. Meeting notes are routinely recorded in intranets, and (with public organizations) on the internet; however, without semantic content it is very difficult to extract the specific information, analyze it, distribute it, or search it effectively. This investigation seeks to document how meeting minutes on the web are structured, towards a lightweight suite of microformats and format extensions for markup.''
== Participants ==
* ''Brush''

== Real-World Examples ==
''These are fairly random, selected for variety of approach. Research is not yet in-depth. Room for more!''

=== [http://www.geneontology.org/minutes/20050408_Pasadena.txt Gene Ontology Consortium] ===
*Abbreviated organization name
*Dates
*Location (locality, region)
*Next meeting date/location (to be confirmed)
*Participants
**Listed by group-affiliation
**Names in comma-delimited parentheses
**Some groups not represented, still listed (like regrets)
*Nested outline of items (XOXO!)
*Major topic -> subsidiary topic
**Includes introduction, by named presenter(s)
**Discussion item list
***Detailed (but flat) following of arguments pro and con
***Identified conclusions (decisions? not formal?)
***Certain items or references id specific people
**Action items
***listed after each topic
***assigned to a person (or to "everyone")
***Also summarized at end of minutes
***Previous action items listed, with status:
****done
****unresolvable
****in progress
****almost done
****other details, etc.
**Brainstorm section
*Next meetings:
**Types
**Dates
**Locations

=== [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] ===
*Organization, committee
*Date
*Time start/end
*Kind of meeting (ie. special meeting, as opposed to regular)
*Present, with roles:
**member/non-member
**President/Secretary
**organizational affiliations
**also plurally generic (ie. "Hospital Managers and citizens from the community, SEIU 1199NW delegation")
*Outline list (flat) of items
**"Call to order"
**"Oath of office" (ie. establishment of new official roles for individuals)
**Approval of previous minutes (special form of decision)
**Reports from managers/committees
**Authorizations for expenditures
**"Other business"
**Public comment
**Adjournment
*Decisions included in text of items
**motion made
**seconded
**approved unanimously
**included appointments to committees (changes in roles?)
*Items include one, sometimes more specifically referenced speakers

=== [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] ===
*Includes relatively unhelpful presentation-oriented table-of-contents link outline markup (more detail?)
*Title
*Date
*Location
*Attendees
**Affiliation
*High-level item
**Includes one-sentence summary
*Second-level item
**Issue
**Discussion
**Conclusion(s)
***Not clear distinction between decisions and action items
***Some action items attached to specific people

=== [http://mail.gnome.org/archives/foundation-list/2004-April/msg00008.html GNOME/Mozilla Meeting] ===
*Title (included two participating organizations)
*Date
*(Email, so "date sent out" included implicitly)
*Attendance
**Organizational affiliation
**minutes
**chair
*Regrets
*Actions (list)
*Discussion (list tree, no titles)
**Specific items inside each discussion item refer to specific person(s)
**Follow pros and cons of arguments

=== [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] ===
*Organization and committee
*form of meeting (ie. teleconference)
*Date
*Time start/end
*Attendance (noted that all were present throughout) with roles:
**member of committee
**member and chair
**non-member, board secretary
**non-member, general counsel
*XOXO-like outline of items
*"Resolved:" decisions for each item.
**vote count (ie. 4-0)
**who proposed
**who seconded
*Also included items deferred to later meetings

== Existing Practices ==
* ''Summary of common patterns discovered'': An informal "80/20" analysis of most commonly used elements:
** 80% used items are mostly extremely common:
*** Title (organization/committee name, sometimes location)
*** Date (time is fairly common as well)
*** Participants (almost always include specific notation of Chair and Secretary, regrets also really common)
*** Point list of topics
**** Often flat, but also often nested
**** Some models (specifically formal meetings) have clear, regular division of kinds of topics (eg. reports from committees, approval of minutes, old business, new business, public comment, etc.)
*** Decisions (usually include description of how vote broke down, movers, seconders, etc.)
*** Action items (who assigned to; sometimes status review, date due, etc.)
*** Next meeting(s) - fairly common
** The 20% portion is primarily specific kinds of topic divisions, specific categories of participants, categories of meetings (special, regular, business, ...), etc. These could be standardized for certain sets of applications without writing into the uformat per se.
* ''Other attempts to solve The Problem'': Does anyone have references to other schemae attempted to address this issue? How about a semantically marked up implementation!?
** All W3C meetings are recorded, as a matter of policy. There are zillions of teleconference and ftf meeting records. See [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the ESW wiki] for notes, patterns, and tools, especially [http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm the scribe.perl tool], Zakim, and RRSAgent. ''-DanC''
** The W3C tools assume the following structure, near as I can tell: (DanC, more advice?) (I've eliminated IRC-specific details)
*** Meeting: ''title''
*** Chair: ''name''
*** Scribe: ''name''
*** Agenda: ''URL of agenda - agendas are automatically formed using various tools, and are essentially a flat list of agenda items''
*** Present: ''comma-delimited list of names''
*** Regrets: ''pre-announced non-attendees''
*** Date: ''yup''
*** Topic: ''next in a flat list of agendums; topic name seems to often be (I think) in a well-formed format for reference to a centrally kept list (RDF or other?)''
*** Action: ''list, of, names'' '''to''' ''description of action'' <nowiki>[STATUS]</nowiki>
**** Status is optional
**** May be DONE, PENDING, DROPPED, with other synonyms
**** Again, this is well-tracked between meetings for the purpose of providing open action item lists
*** Resolved: ''description of decision made''
** The vCard spec includes a [http://www.w3.org/2002/12/cal/rfc2445#sec4.6.2 definition for vTodo]. I'm assuming that iCal-basic and hCalendar don't already include this part of the spec, so it could become the basis to an extension of the hCalendar uformat (or a new hTodo?) that defines action items. (Action item management is a core focus of the W3C technical tools above.) This would be integrated into hMinutes.

== Existing Formats ==

See [[meeting-minutes-formats]] for current standards for publishing meeting-minutes.

'''NOTE: This research should be done ''before'' brainstorming proposals.'''
''Does anyone have ideas? Besides some brainstorming at W3C, haven't found any current standards.''

== Proposal ==

''To be moved to [[meeting-minutes-brainstorming]] soon.''

=== hParticipants ===
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

=== hDecision ===
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting?
* Should it be possible to use [http://microformats.org/wiki/xoxo XOXO] ''inside'' the hDecision to give it structure? Hmmmm. Or should it be forced into multiple decisions?
* Should have "description" class, if not included tag is used?

=== hMinutes ===
Example idea:
<pre><nowiki>
<div class="hminutes>

ABC, Inc.
...

<div class="meeting">
Annual Meeting
...
April 10, 2006; 7pm
<div class="hparticipants">
...
</div>
</div>
<ol class="topic xoxo">
<li>
<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag">Our first topic</a>
<dt>
<dl class="description">
Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.





There is also this action item ''do example markup''


</dl>
<dt>
<ul>
<li>
... subpoints ...
</li>
</ul>
</li>
<li>
... next topic ...
</li
</ol>
</div>
</nowiki></pre>

=== See Also ===
''Link to related pages as they become available''
* -brainstorming
* [http://microformats.org/wiki/meeting-minutes-formats meeting-minutes-formats]
* -proposal
* -microformat

It is probably better to first:
# analyze what are the 80/20 common elements of the examples above
# complete the research of [[meeting-minutes-formats]]
# and then go about proposing a solution for the whole format, rather than parts of it, while attempting to reuse other [[microformats]] as much as possible. [http://tantek.com/ Tantek]

''True, but rather than documenting a lot of what is in my head I got a bit hasty. Forgive me, will try to keep better on track.''-Brush

== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

meeting-minutes-examples

2006-05-08T17:25:55Z

Brush: /* Existing Practices */

= Meeting minutes =
They're typed, they look good, but all the meaning (participants, decisions, action items, etc.) is impossible to glean automatically. Enter hMinutes (or whatever)!

== The Problem ==
''Meeting notes provide a wealth of semantic content, invaluable to organizations. Meeting notes are routinely recorded in intranets, and (with public organizations) on the internet; however, without semantic content it is very difficult to extract the specific information, analyze it, distribute it, or search it effectively. This investigation seeks to document how meeting minutes on the web are structured, towards a lightweight suite of microformats and format extensions for markup.''
== Participants ==
* ''Brush''

== Real-World Examples ==
''These are fairly random, selected for variety of approach. Research is not yet in-depth. Room for more!''

=== [http://www.geneontology.org/minutes/20050408_Pasadena.txt Gene Ontology Consortium] ===
*Abbreviated organization name
*Dates
*Location (locality, region)
*Next meeting date/location (to be confirmed)
*Participants
**Listed by group-affiliation
**Names in comma-delimited parentheses
**Some groups not represented, still listed (like regrets)
*Nested outline of items (XOXO!)
*Major topic -> subsidiary topic
**Includes introduction, by named presenter(s)
**Discussion item list
***Detailed (but flat) following of arguments pro and con
***Identified conclusions (decisions? not formal?)
***Certain items or references id specific people
**Action items
***listed after each topic
***assigned to a person (or to "everyone")
***Also summarized at end of minutes
***Previous action items listed, with status:
****done
****unresolvable
****in progress
****almost done
****other details, etc.
**Brainstorm section
*Next meetings:
**Types
**Dates
**Locations

=== [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] ===
*Organization, committee
*Date
*Time start/end
*Kind of meeting (ie. special meeting, as opposed to regular)
*Present, with roles:
**member/non-member
**President/Secretary
**organizational affiliations
**also plurally generic (ie. "Hospital Managers and citizens from the community, SEIU 1199NW delegation")
*Outline list (flat) of items
**"Call to order"
**"Oath of office" (ie. establishment of new official roles for individuals)
**Approval of previous minutes (special form of decision)
**Reports from managers/committees
**Authorizations for expenditures
**"Other business"
**Public comment
**Adjournment
*Decisions included in text of items
**motion made
**seconded
**approved unanimously
**included appointments to committees (changes in roles?)
*Items include one, sometimes more specifically referenced speakers

=== [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] ===
*Includes relatively unhelpful presentation-oriented table-of-contents link outline markup (more detail?)
*Title
*Date
*Location
*Attendees
**Affiliation
*High-level item
**Includes one-sentence summary
*Second-level item
**Issue
**Discussion
**Conclusion(s)
***Not clear distinction between decisions and action items
***Some action items attached to specific people

=== [http://mail.gnome.org/archives/foundation-list/2004-April/msg00008.html GNOME/Mozilla Meeting] ===
*Title (included two participating organizations)
*Date
*(Email, so "date sent out" included implicitly)
*Attendance
**Organizational affiliation
**minutes
**chair
*Regrets
*Actions (list)
*Discussion (list tree, no titles)
**Specific items inside each discussion item refer to specific person(s)
**Follow pros and cons of arguments

=== [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] ===
*Organization and committee
*form of meeting (ie. teleconference)
*Date
*Time start/end
*Attendance (noted that all were present throughout) with roles:
**member of committee
**member and chair
**non-member, board secretary
**non-member, general counsel
*XOXO-like outline of items
*"Resolved:" decisions for each item.
**vote count (ie. 4-0)
**who proposed
**who seconded
*Also included items deferred to later meetings

== Existing Practices ==
* ''Summary of common patterns discovered'': An informal "80/20" analysis of most commonly used elements:
** 80% used items are mostly extremely common:
*** Title (organization/committee name, sometimes location)
*** Date (time is fairly common as well)
*** Participants (almost always include specific notation of Chair and Secretary, regrets also really common)
*** Point list of topics
**** Often flat, but also often nested
**** Some models (specifically formal meetings) have clear, regular division of kinds of topics (eg. reports from committees, approval of minutes, old business, new business, public comment, etc.)
*** Decisions (usually include description of how vote broke down, movers, seconders, etc.)
*** Action items (who assigned to; sometimes status review, date due, etc.)
*** Next meeting(s) - fairly common
** The 20% portion is primarily specific kinds of topic divisions, specific categories of participants, categories of meetings (special, regular, business, ...), etc. These could be standardized for certain sets of applications without writing into the uformat per se.
* ''Other attempts to solve The Problem'': Does anyone have references to other schemae attempted to address this issue? How about a semantically marked up implementation!?
** All W3C meetings are recorded, as a matter of policy. There are zillions of teleconference and ftf meeting records. See [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the ESW wiki] for notes, patterns, and tools, especially [http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm the scribe.perl tool], Zakim, and RRSAgent. ''-DanC''
** The W3C tools assume the following structure, near as I can tell: (DanC, more advice?) (I've eliminated IRC-specific details)
*** Meeting: ''title''
*** Chair: ''name''
*** Scribe: ''name''
*** Agenda: ''URL of agenda - agendas are automatically formed using various tools, and are essentially a flat list of agenda items''
*** Present: ''comma-delimited list of names''
*** Regrets: ''pre-announced non-attendees''
*** Date: ''yup''
*** Topic: ''next in a flat list of agendums; topic name seems to often be (I think) in a well-formed format for reference to a centrally kept list (RDF or other?)''
*** Action: ''list, of, names'' '''to''' ''description of action'' <nowiki>[STATUS]</nowiki>
**** Status is optional
**** May be DONE, PENDING, DROPPED, with other synonyms
**** Again, this is well-tracked between meetings for the purpose of providing open action item lists
*** Resolved: ''description of decision made''
** The vCard spec includes a [http://www.w3.org/2002/12/cal/rfc2445#sec4.6.2 definition for vTodo]. I'm assuming that iCal-basic and hCalendar don't already include this part of the spec, so it could become the basis to an extension of the hCalendar uformat (or a new hTodo?) that defines action items. (Action item management is a core focus of the W3C technical tools above.) This would be integrated into hMinutes.

== Existing Formats ==

See [[meeting-minutes-formats]] for current standards for publishing meeting-minutes.

'''NOTE: This research should be done ''before'' brainstorming proposals.'''

== Proposal ==

''To be moved to [[meeting-minutes-brainstorming]] soon.''

=== hParticipants ===
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

=== hDecision ===
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting?
* Should it be possible to use [http://microformats.org/wiki/xoxo XOXO] ''inside'' the hDecision to give it structure? Hmmmm. Or should it be forced into multiple decisions?
* Should have "description" class, if not included tag is used?

=== hMinutes ===
Example idea:
<pre><nowiki>
<div class="hminutes>

ABC, Inc.
...

<div class="meeting">
Annual Meeting
...
April 10, 2006; 7pm
<div class="hparticipants">
...
</div>
</div>
<ol class="topic xoxo">
<li>
<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag">Our first topic</a>
<dt>
<dl class="description">
Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.





There is also this action item ''do example markup''


</dl>
<dt>
<ul>
<li>
... subpoints ...
</li>
</ul>
</li>
<li>
... next topic ...
</li
</ol>
</div>
</nowiki></pre>

=== See Also ===
''Link to related pages as they become available''
* -brainstorming
* [http://microformats.org/wiki/meeting-minutes-formats meeting-minutes-formats]
* -proposal
* -microformat

It is probably better to first:
# analyze what are the 80/20 common elements of the examples above
# complete the research of [[meeting-minutes-formats]]
# and then go about proposing a solution for the whole format, rather than parts of it, while attempting to reuse other [[microformats]] as much as possible. [http://tantek.com/ Tantek]

''True, but rather than documenting a lot of what is in my head I got a bit hasty. Forgive me, will try to keep better on track.''-Brush

== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

meeting-minutes-examples

2006-05-08T17:20:52Z

Brush: /* Existing Practices */ - Outline common patterns

= Meeting minutes =
They're typed, they look good, but all the meaning (participants, decisions, action items, etc.) is impossible to glean automatically. Enter hMinutes (or whatever)!

== The Problem ==
''Meeting notes provide a wealth of semantic content, invaluable to organizations. Meeting notes are routinely recorded in intranets, and (with public organizations) on the internet; however, without semantic content it is very difficult to extract the specific information, analyze it, distribute it, or search it effectively. This investigation seeks to document how meeting minutes on the web are structured, towards a lightweight suite of microformats and format extensions for markup.''
== Participants ==
* ''Brush''

== Real-World Examples ==
''These are fairly random, selected for variety of approach. Research is not yet in-depth. Room for more!''

=== [http://www.geneontology.org/minutes/20050408_Pasadena.txt Gene Ontology Consortium] ===
*Abbreviated organization name
*Dates
*Location (locality, region)
*Next meeting date/location (to be confirmed)
*Participants
**Listed by group-affiliation
**Names in comma-delimited parentheses
**Some groups not represented, still listed (like regrets)
*Nested outline of items (XOXO!)
*Major topic -> subsidiary topic
**Includes introduction, by named presenter(s)
**Discussion item list
***Detailed (but flat) following of arguments pro and con
***Identified conclusions (decisions? not formal?)
***Certain items or references id specific people
**Action items
***listed after each topic
***assigned to a person (or to "everyone")
***Also summarized at end of minutes
***Previous action items listed, with status:
****done
****unresolvable
****in progress
****almost done
****other details, etc.
**Brainstorm section
*Next meetings:
**Types
**Dates
**Locations

=== [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] ===
*Organization, committee
*Date
*Time start/end
*Kind of meeting (ie. special meeting, as opposed to regular)
*Present, with roles:
**member/non-member
**President/Secretary
**organizational affiliations
**also plurally generic (ie. "Hospital Managers and citizens from the community, SEIU 1199NW delegation")
*Outline list (flat) of items
**"Call to order"
**"Oath of office" (ie. establishment of new official roles for individuals)
**Approval of previous minutes (special form of decision)
**Reports from managers/committees
**Authorizations for expenditures
**"Other business"
**Public comment
**Adjournment
*Decisions included in text of items
**motion made
**seconded
**approved unanimously
**included appointments to committees (changes in roles?)
*Items include one, sometimes more specifically referenced speakers

=== [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] ===
*Includes relatively unhelpful presentation-oriented table-of-contents link outline markup (more detail?)
*Title
*Date
*Location
*Attendees
**Affiliation
*High-level item
**Includes one-sentence summary
*Second-level item
**Issue
**Discussion
**Conclusion(s)
***Not clear distinction between decisions and action items
***Some action items attached to specific people

=== [http://mail.gnome.org/archives/foundation-list/2004-April/msg00008.html GNOME/Mozilla Meeting] ===
*Title (included two participating organizations)
*Date
*(Email, so "date sent out" included implicitly)
*Attendance
**Organizational affiliation
**minutes
**chair
*Regrets
*Actions (list)
*Discussion (list tree, no titles)
**Specific items inside each discussion item refer to specific person(s)
**Follow pros and cons of arguments

=== [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] ===
*Organization and committee
*form of meeting (ie. teleconference)
*Date
*Time start/end
*Attendance (noted that all were present throughout) with roles:
**member of committee
**member and chair
**non-member, board secretary
**non-member, general counsel
*XOXO-like outline of items
*"Resolved:" decisions for each item.
**vote count (ie. 4-0)
**who proposed
**who seconded
*Also included items deferred to later meetings

== Existing Practices ==
* ''Summary of common patterns discovered'': An informal "80/20" analysis of most commonly used elements:
** Title (organization/committee name, sometimes location)
** Date (time is fairly common as well)
** Participants (almost always include specific notation of Chair and Secretary, regrets also really common)
** Point list of topics
*** Often flat, but also often nested
*** Some models (specifically formal meetings) have clear, regular division of kinds of topics (eg. reports from committees, approval of minutes, old business, new business, public comment, etc.)
** Decisions (usually include description of how vote broke down, movers, seconders, etc.)
** Action items (who assigned to; sometimes status review, date due, etc.)
** Next meeting(s) - fairly common
** ''The "20" portion is primarily specific kinds of topic divisions, specific categories of participants, etc. These could be standardized for certain sets of applications without writing into the uformat per se.''
* ''Other attempts to solve The Problem'': Does anyone have references to other schemae attempted to address this issue? How about a semantically marked up implementation!?
** All W3C meetings are recorded, as a matter of policy. There are zillions of teleconference and ftf meeting records. See [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the ESW wiki] for notes, patterns, and tools, especially [http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm the scribe.perl tool], Zakim, and RRSAgent. ''-DanC''
** The W3C tools assume the following structure, near as I can tell: (DanC, more advice?) (I've eliminated IRC-specific details)
*** Meeting: ''title''
*** Chair: ''name''
*** Scribe: ''name''
*** Agenda: ''URL of agenda - agendas are automatically formed using various tools, and are essentially a flat list of agenda items''
*** Present: ''comma-delimited list of names''
*** Regrets: ''pre-announced non-attendees''
*** Date: ''yup''
*** Topic: ''next in a flat list of agendums; topic name seems to often be (I think) in a well-formed format for reference to a centrally kept list (RDF or other?)''
*** Action: ''list, of, names'' '''to''' ''description of action'' <nowiki>[STATUS]</nowiki>
**** Status is optional
**** May be DONE, PENDING, DROPPED, with other synonyms
**** Again, this is well-tracked between meetings for the purpose of providing open action item lists
*** Resolved: ''description of decision made''
** The vCard spec includes a [http://www.w3.org/2002/12/cal/rfc2445#sec4.6.2 definition for vTodo]. I'm assuming that iCal-basic and hCalendar don't already include this part of the spec, so it could become the basis to an extension of the hCalendar uformat (or a new hTodo?) that defines action items. (Action item management is a core focus of the W3C technical tools above.) This would be integrated into hMinutes.

== Existing Formats ==

See [[meeting-minutes-formats]] for current standards for publishing meeting-minutes.

'''NOTE: This research should be done ''before'' brainstorming proposals.'''

== Proposal ==

''To be moved to [[meeting-minutes-brainstorming]] soon.''

=== hParticipants ===
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

=== hDecision ===
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting?
* Should it be possible to use [http://microformats.org/wiki/xoxo XOXO] ''inside'' the hDecision to give it structure? Hmmmm. Or should it be forced into multiple decisions?
* Should have "description" class, if not included tag is used?

=== hMinutes ===
Example idea:
<pre><nowiki>
<div class="hminutes>

ABC, Inc.
...

<div class="meeting">
Annual Meeting
...
April 10, 2006; 7pm
<div class="hparticipants">
...
</div>
</div>
<ol class="topic xoxo">
<li>
<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag">Our first topic</a>
<dt>
<dl class="description">
Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.





There is also this action item ''do example markup''


</dl>
<dt>
<ul>
<li>
... subpoints ...
</li>
</ul>
</li>
<li>
... next topic ...
</li
</ol>
</div>
</nowiki></pre>

=== See Also ===
''Link to related pages as they become available''
* -brainstorming
* [http://microformats.org/wiki/meeting-minutes-formats meeting-minutes-formats]
* -proposal
* -microformat

It is probably better to first:
# analyze what are the 80/20 common elements of the examples above
# complete the research of [[meeting-minutes-formats]]
# and then go about proposing a solution for the whole format, rather than parts of it, while attempting to reuse other [[microformats]] as much as possible. [http://tantek.com/ Tantek]

''True, but rather than documenting a lot of what is in my head I got a bit hasty. Forgive me, will try to keep better on track.''-Brush

== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

Main Page

2006-05-08T02:18:33Z

Brush: /* Exploratory discussions */

__NOTOC__
__NOTOC__
= Microformats Wiki =

'''Please read [[how-to-play]] before making any edits.'''

'''Please read [[process]] before proposing any new microformats.'''

== Introduction ==

What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]], [[presentations]], and [[podcasts]] are also a good place for some background reading as well. Frequently asked questions are answered in the [[faq]]. Want something or want to contribute? Help with things [[to-do]]. Want to learn more in person? Check out microformats [[events]].

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]
* [[rel-home]] {{NewMarker}}

== Design Patterns ==

Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''

* [[abbr-design-pattern]]
* [[class-design-pattern]]
* [[datetime-design-pattern]]
* [[existing-classes|class names defined across all microformats]]
* [[include-pattern]] {{NewMarker}}
* [[rel-design-pattern]]

== Exploratory discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*[[attention]]
*[[blog-description-examples]]
*[[blog-info-examples]]
*[[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]] (yields [[hatom|hAtom]])
*[[book-examples]], [[book-formats]], [[book-brainstorming]]
*[[chat-examples]], [[chat-formats]]
*[[citation|citation microformat overview]], [[citation-examples]], [[citation-formats]], [[citation-brainstorming]]
*[[comment-problem]], [[comment-examples]], (need to extract from [[comments-formats]])
*[[directions-examples]] {{NewMarker}}
*[[directory-inclusion-examples]], [[directory-inclusion-formats]]. (see also [[rel-directory]])
*[[distributed-conversation]], [[distributed-conversation-brainstorming]], [[distributed-conversation-examples]], [[distributed-conversation-formats]]
*[[forms-examples]]
*[[genealogy-formats]]
*[[hash-examples]]
*[[last-modified-examples]], [[last-modified-formats]], [[last-modified-brainstorming]]
*[[hlisting-proposal]], [[hlisting-feedback]] {{NewMarker}}
**[[listing-examples]], [[listing-formats]], [[listing-brainstorming]]
*[[location-formats]]. (see also [[adr]] and [[geo]])
*[[media-info-examples]]
*[[meeting-minutes-examples]], [[meeting-minutes-formats]]
*[[mfo-examples]]
*[[music-examples]]
*[[other-formats]]
*[[photo-note-examples]]
*[[recipe-examples]]
*[[requirements-testing]], [[requirements-testing-examples]]
*[[rest-examples]]
*[[resume-brainstorming]], [[resume-formats]]
*[[review-examples]], [[review-formats]] (yielded the [[hreview|hReview]] draft)
*[[search-results-example]]
*[[show-brainstorming]]
*[[showroll-brainstorming]]
*[[table-examples]]
*[[tagspeak-examples]]
*[[transit-table-examples]]
*[[uid]]
*[[widget-examples]], [[widget-brainstorming]]
*[[wiki-formats]]
*[[work-of-art]] {{NewMarker}}
*[[xmdp-brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]] {{NewMarker}}

== Tools & Test Cases & Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[[vcard-implementations]], [[vcard-errata]]
*[[icalendar-implementations]]
*[[faqs-for-rdf]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]] {{NewMarker}}
* [[to-do]]
* [[marked-for-deletion]]

== microformats wiki in other languages ==

You may read and edit microformats articles in <del>many different</del> other languages

=== microformats wiki languages with over 2 articles ===

* [[Main_Page-fr|Français (French)]]
* [[Main_Page-jp|日本語 (Japanese)]] {{NewMarker}}
* [[Main_Page-sp|Español (Spanish)]] {{NewMarker}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

Main Page

2006-05-08T02:18:11Z

Brush: /* Exploratory discussions */

__NOTOC__
__NOTOC__
= Microformats Wiki =

'''Please read [[how-to-play]] before making any edits.'''

'''Please read [[process]] before proposing any new microformats.'''

== Introduction ==

What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]], [[presentations]], and [[podcasts]] are also a good place for some background reading as well. Frequently asked questions are answered in the [[faq]]. Want something or want to contribute? Help with things [[to-do]]. Want to learn more in person? Check out microformats [[events]].

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]
* [[rel-home]] {{NewMarker}}

== Design Patterns ==

Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''

* [[abbr-design-pattern]]
* [[class-design-pattern]]
* [[datetime-design-pattern]]
* [[existing-classes|class names defined across all microformats]]
* [[include-pattern]] {{NewMarker}}
* [[rel-design-pattern]]

== Exploratory discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*[[attention]]
*[[blog-description-examples]]
*[[blog-info-examples]]
*[[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]] (yields [[hatom|hAtom]])
*[[book-examples]], [[book-formats]], [[book-brainstorming]]
*[[chat-examples]], [[chat-formats]]
*[[citation|citation microformat overview]], [[citation-examples]], [[citation-formats]], [[citation-brainstorming]]
*[[comment-problem]], [[comment-examples]], (need to extract from [[comments-formats]])
*[[directions-examples]] {{NewMarker}}
*[[directory-inclusion-examples]], [[directory-inclusion-formats]]. (see also [[rel-directory]])
*[[distributed-conversation]], [[distributed-conversation-brainstorming]], [[distributed-conversation-examples]], [[distributed-conversation-formats]]
*[[forms-examples]]
*[[genealogy-formats]]
*[[hash-examples]]
*[[last-modified-examples]], [[last-modified-formats]], [[last-modified-brainstorming]]
*[[hlisting-proposal]], [[hlisting-feedback]] {{NewMarker}}
**[[listing-examples]], [[listing-formats]], [[listing-brainstorming]]
*[[location-formats]]. (see also [[adr]] and [[geo]])
*[[media-info-examples]]
*[[meeting-minutes-examples]] [[meeting-minutes-formats]]
*[[mfo-examples]]
*[[music-examples]]
*[[other-formats]]
*[[photo-note-examples]]
*[[recipe-examples]]
*[[requirements-testing]], [[requirements-testing-examples]]
*[[rest-examples]]
*[[resume-brainstorming]], [[resume-formats]]
*[[review-examples]], [[review-formats]] (yielded the [[hreview|hReview]] draft)
*[[search-results-example]]
*[[show-brainstorming]]
*[[showroll-brainstorming]]
*[[table-examples]]
*[[tagspeak-examples]]
*[[transit-table-examples]]
*[[uid]]
*[[widget-examples]], [[widget-brainstorming]]
*[[wiki-formats]]
*[[work-of-art]] {{NewMarker}}
*[[xmdp-brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]] {{NewMarker}}

== Tools & Test Cases & Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[[vcard-implementations]], [[vcard-errata]]
*[[icalendar-implementations]]
*[[faqs-for-rdf]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]] {{NewMarker}}
* [[to-do]]
* [[marked-for-deletion]]

== microformats wiki in other languages ==

You may read and edit microformats articles in <del>many different</del> other languages

=== microformats wiki languages with over 2 articles ===

* [[Main_Page-fr|Français (French)]]
* [[Main_Page-jp|日本語 (Japanese)]] {{NewMarker}}
* [[Main_Page-sp|Español (Spanish)]] {{NewMarker}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

meeting-minutes-examples

2006-05-08T02:17:34Z

Brush: /* See Also */

= Meeting minutes =
They're typed, they look good, but all the meaning (participants, decisions, action items, etc.) is impossible to glean automatically. Enter hMinutes (or whatever)!

== The Problem ==
''Meeting notes provide a wealth of semantic content, invaluable to organizations. Meeting notes are routinely recorded in intranets, and (with public organizations) on the internet; however, without semantic content it is very difficult to extract the specific information, analyze it, distribute it, or search it effectively. This investigation seeks to document how meeting minutes on the web are structured, towards a lightweight suite of microformats and format extensions for markup.''
== Participants ==
* ''Brush''

== Real-World Examples ==
''These are fairly random, selected for variety of approach. Research is not yet in-depth. Room for more!''

=== [http://www.geneontology.org/minutes/20050408_Pasadena.txt Gene Ontology Consortium] ===
*Abbreviated organization name
*Dates
*Location (locality, region)
*Next meeting date/location (to be confirmed)
*Participants
**Listed by group-affiliation
**Names in comma-delimited parentheses
**Some groups not represented, still listed (like regrets)
*Nested outline of items (XOXO!)
*Major topic -> subsidiary topic
**Includes introduction, by named presenter(s)
**Discussion item list
***Detailed (but flat) following of arguments pro and con
***Identified conclusions (decisions? not formal?)
***Certain items or references id specific people
**Action items
***listed after each topic
***assigned to a person (or to "everyone")
***Also summarized at end of minutes
***Previous action items listed, with status:
****done
****unresolvable
****in progress
****almost done
****other details, etc.
**Brainstorm section
*Next meetings:
**Types
**Dates
**Locations

=== [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] ===
*Organization, committee
*Date
*Time start/end
*Kind of meeting (ie. special meeting, as opposed to regular)
*Present, with roles:
**member/non-member
**President/Secretary
**organizational affiliations
**also plurally generic (ie. "Hospital Managers and citizens from the community, SEIU 1199NW delegation")
*Outline list (flat) of items
**"Call to order"
**"Oath of office" (ie. establishment of new official roles for individuals)
**Approval of previous minutes (special form of decision)
**Reports from managers/committees
**Authorizations for expenditures
**"Other business"
**Public comment
**Adjournment
*Decisions included in text of items
**motion made
**seconded
**approved unanimously
**included appointments to committees (changes in roles?)
*Items include one, sometimes more specifically referenced speakers

=== [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] ===
*Includes relatively unhelpful presentation-oriented table-of-contents link outline markup (more detail?)
*Title
*Date
*Location
*Attendees
**Affiliation
*High-level item
**Includes one-sentence summary
*Second-level item
**Issue
**Discussion
**Conclusion(s)
***Not clear distinction between decisions and action items
***Some action items attached to specific people

=== [http://mail.gnome.org/archives/foundation-list/2004-April/msg00008.html GNOME/Mozilla Meeting] ===
*Title (included two participating organizations)
*Date
*(Email, so "date sent out" included implicitly)
*Attendance
**Organizational affiliation
**minutes
**chair
*Regrets
*Actions (list)
*Discussion (list tree, no titles)
**Specific items inside each discussion item refer to specific person(s)
**Follow pros and cons of arguments

=== [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] ===
*Organization and committee
*form of meeting (ie. teleconference)
*Date
*Time start/end
*Attendance (noted that all were present throughout) with roles:
**member of committee
**member and chair
**non-member, board secretary
**non-member, general counsel
*XOXO-like outline of items
*"Resolved:" decisions for each item.
**vote count (ie. 4-0)
**who proposed
**who seconded
*Also included items deferred to later meetings

== Existing Practices ==
* ''Summary of common patterns discovered'': Anyone? Some things are fairly obvious...
* ''Other attempts to solve The Problem'': Does anyone have references to other schemae attempted to address this issue? How about a semantically marked up implementation!?
** All W3C meetings are recorded, as a matter of policy. There are zillions of teleconference and ftf meeting records. See [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the ESW wiki] for notes, patterns, and tools, especially [http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm the scribe.perl tool], Zakim, and RRSAgent. ''-DanC''
** The W3C tools assume the following structure, near as I can tell: (DanC, more advice?) (I've eliminated IRC-specific details)
*** Meeting: ''title''
*** Chair: ''name''
*** Scribe: ''name''
*** Agenda: ''URL of agenda - agendas are automatically formed using various tools, and are essentially a flat list of agenda items''
*** Present: ''comma-delimited list of names''
*** Regrets: ''pre-announced non-attendees''
*** Date: ''yup''
*** Topic: ''next in a flat list of agendums; topic name seems to often be (I think) in a well-formed format for reference to a centrally kept list (RDF or other?)''
*** Action: ''list, of, names'' '''to''' ''description of action'' <nowiki>[STATUS]</nowiki>
**** Status is optional
**** May be DONE, PENDING, DROPPED, with other synonyms
**** Again, this is well-tracked between meetings for the purpose of providing open action item lists
*** Resolved: ''description of decision made''
** The vCard spec includes a [http://www.w3.org/2002/12/cal/rfc2445#sec4.6.2 definition for vTodo]. I'm assuming that iCal-basic and hCalendar don't already include this part of the spec, so it could become the basis to an extension of the hCalendar uformat (or a new hTodo?) that defines action items. (Action item management is a core focus of the W3C technical tools above.) This would be integrated into hMinutes.

== Existing Formats ==

See [[meeting-minutes-formats]] for current standards for publishing meeting-minutes.

'''NOTE: This research should be done ''before'' brainstorming proposals.'''

== Proposal ==

''To be moved to [[meeting-minutes-brainstorming]] soon.''

=== hParticipants ===
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

=== hDecision ===
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting?
* Should it be possible to use [http://microformats.org/wiki/xoxo XOXO] ''inside'' the hDecision to give it structure? Hmmmm. Or should it be forced into multiple decisions?
* Should have "description" class, if not included tag is used?

=== hMinutes ===
Example idea:
<pre><nowiki>
<div class="hminutes>

ABC, Inc.
...

<div class="meeting">
Annual Meeting
...
April 10, 2006; 7pm
<div class="hparticipants">
...
</div>
</div>
<ol class="topic xoxo">
<li>
<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag">Our first topic</a>
<dt>
<dl class="description">
Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.





There is also this action item ''do example markup''


</dl>
<dt>
<ul>
<li>
... subpoints ...
</li>
</ul>
</li>
<li>
... next topic ...
</li
</ol>
</div>
</nowiki></pre>

=== See Also ===
''Link to related pages as they become available''
* -brainstorming
* [http://microformats.org/wiki/meeting-minutes-formats meeting-minutes-formats]
* -proposal
* -microformat

It is probably better to first:
# analyze what are the 80/20 common elements of the examples above
# complete the research of [[meeting-minutes-formats]]
# and then go about proposing a solution for the whole format, rather than parts of it, while attempting to reuse other [[microformats]] as much as possible. [http://tantek.com/ Tantek]

''True, but rather than documenting a lot of what is in my head I got a bit hasty. Forgive me, will try to keep better on track.''-Brush

== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

meeting-minutes-examples

2006-05-08T02:15:33Z

Brush: /* hMinutes */ Include xoxo as structure of topics

= Meeting minutes =
They're typed, they look good, but all the meaning (participants, decisions, action items, etc.) is impossible to glean automatically. Enter hMinutes (or whatever)!

== The Problem ==
''Meeting notes provide a wealth of semantic content, invaluable to organizations. Meeting notes are routinely recorded in intranets, and (with public organizations) on the internet; however, without semantic content it is very difficult to extract the specific information, analyze it, distribute it, or search it effectively. This investigation seeks to document how meeting minutes on the web are structured, towards a lightweight suite of microformats and format extensions for markup.''
== Participants ==
* ''Brush''

== Real-World Examples ==
''These are fairly random, selected for variety of approach. Research is not yet in-depth. Room for more!''

=== [http://www.geneontology.org/minutes/20050408_Pasadena.txt Gene Ontology Consortium] ===
*Abbreviated organization name
*Dates
*Location (locality, region)
*Next meeting date/location (to be confirmed)
*Participants
**Listed by group-affiliation
**Names in comma-delimited parentheses
**Some groups not represented, still listed (like regrets)
*Nested outline of items (XOXO!)
*Major topic -> subsidiary topic
**Includes introduction, by named presenter(s)
**Discussion item list
***Detailed (but flat) following of arguments pro and con
***Identified conclusions (decisions? not formal?)
***Certain items or references id specific people
**Action items
***listed after each topic
***assigned to a person (or to "everyone")
***Also summarized at end of minutes
***Previous action items listed, with status:
****done
****unresolvable
****in progress
****almost done
****other details, etc.
**Brainstorm section
*Next meetings:
**Types
**Dates
**Locations

=== [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] ===
*Organization, committee
*Date
*Time start/end
*Kind of meeting (ie. special meeting, as opposed to regular)
*Present, with roles:
**member/non-member
**President/Secretary
**organizational affiliations
**also plurally generic (ie. "Hospital Managers and citizens from the community, SEIU 1199NW delegation")
*Outline list (flat) of items
**"Call to order"
**"Oath of office" (ie. establishment of new official roles for individuals)
**Approval of previous minutes (special form of decision)
**Reports from managers/committees
**Authorizations for expenditures
**"Other business"
**Public comment
**Adjournment
*Decisions included in text of items
**motion made
**seconded
**approved unanimously
**included appointments to committees (changes in roles?)
*Items include one, sometimes more specifically referenced speakers

=== [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] ===
*Includes relatively unhelpful presentation-oriented table-of-contents link outline markup (more detail?)
*Title
*Date
*Location
*Attendees
**Affiliation
*High-level item
**Includes one-sentence summary
*Second-level item
**Issue
**Discussion
**Conclusion(s)
***Not clear distinction between decisions and action items
***Some action items attached to specific people

=== [http://mail.gnome.org/archives/foundation-list/2004-April/msg00008.html GNOME/Mozilla Meeting] ===
*Title (included two participating organizations)
*Date
*(Email, so "date sent out" included implicitly)
*Attendance
**Organizational affiliation
**minutes
**chair
*Regrets
*Actions (list)
*Discussion (list tree, no titles)
**Specific items inside each discussion item refer to specific person(s)
**Follow pros and cons of arguments

=== [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] ===
*Organization and committee
*form of meeting (ie. teleconference)
*Date
*Time start/end
*Attendance (noted that all were present throughout) with roles:
**member of committee
**member and chair
**non-member, board secretary
**non-member, general counsel
*XOXO-like outline of items
*"Resolved:" decisions for each item.
**vote count (ie. 4-0)
**who proposed
**who seconded
*Also included items deferred to later meetings

== Existing Practices ==
* ''Summary of common patterns discovered'': Anyone? Some things are fairly obvious...
* ''Other attempts to solve The Problem'': Does anyone have references to other schemae attempted to address this issue? How about a semantically marked up implementation!?
** All W3C meetings are recorded, as a matter of policy. There are zillions of teleconference and ftf meeting records. See [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the ESW wiki] for notes, patterns, and tools, especially [http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm the scribe.perl tool], Zakim, and RRSAgent. ''-DanC''
** The W3C tools assume the following structure, near as I can tell: (DanC, more advice?) (I've eliminated IRC-specific details)
*** Meeting: ''title''
*** Chair: ''name''
*** Scribe: ''name''
*** Agenda: ''URL of agenda - agendas are automatically formed using various tools, and are essentially a flat list of agenda items''
*** Present: ''comma-delimited list of names''
*** Regrets: ''pre-announced non-attendees''
*** Date: ''yup''
*** Topic: ''next in a flat list of agendums; topic name seems to often be (I think) in a well-formed format for reference to a centrally kept list (RDF or other?)''
*** Action: ''list, of, names'' '''to''' ''description of action'' <nowiki>[STATUS]</nowiki>
**** Status is optional
**** May be DONE, PENDING, DROPPED, with other synonyms
**** Again, this is well-tracked between meetings for the purpose of providing open action item lists
*** Resolved: ''description of decision made''
** The vCard spec includes a [http://www.w3.org/2002/12/cal/rfc2445#sec4.6.2 definition for vTodo]. I'm assuming that iCal-basic and hCalendar don't already include this part of the spec, so it could become the basis to an extension of the hCalendar uformat (or a new hTodo?) that defines action items. (Action item management is a core focus of the W3C technical tools above.) This would be integrated into hMinutes.

== Existing Formats ==

See [[meeting-minutes-formats]] for current standards for publishing meeting-minutes.

'''NOTE: This research should be done ''before'' brainstorming proposals.'''

== Proposal ==

''To be moved to [[meeting-minutes-brainstorming]] soon.''

=== hParticipants ===
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

=== hDecision ===
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting?
* Should it be possible to use [http://microformats.org/wiki/xoxo XOXO] ''inside'' the hDecision to give it structure? Hmmmm. Or should it be forced into multiple decisions?
* Should have "description" class, if not included tag is used?

=== hMinutes ===
Example idea:
<pre><nowiki>
<div class="hminutes>

ABC, Inc.
...

<div class="meeting">
Annual Meeting
...
April 10, 2006; 7pm
<div class="hparticipants">
...
</div>
</div>
<ol class="topic xoxo">
<li>
<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag">Our first topic</a>
<dt>
<dl class="description">
Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.





There is also this action item ''do example markup''


</dl>
<dt>
<ul>
<li>
... subpoints ...
</li>
</ul>
</li>
<li>
... next topic ...
</li
</ol>
</div>
</nowiki></pre>

=== See Also ===
''Link to related pages as they become available''
* -brainstorming
* -proposal
* -microformat

It is probably better to first:
# analyze what are the 80/20 common elements of the examples above
# complete the research of [[meeting-minutes-formats]]
# and then go about proposing a solution for the whole format, rather than parts of it, while attempting to reuse other [[microformats]] as much as possible. [http://tantek.com/ Tantek]

''True, but rather than documenting a lot of what is in my head I got a bit hasty. Forgive me, will try to keep better on track.''-Brush

== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

meeting-minutes-formats

2006-05-06T21:44:15Z

Brush:

meeting-minutes-examples

2006-05-06T20:21:03Z

Brush: /* See Also */

= Meeting minutes =
They're typed, they look good, but all the meaning (participants, decisions, action items, etc.) is impossible to glean automatically. Enter hMinutes (or whatever)!

== The Problem ==
''Meeting notes provide a wealth of semantic content, invaluable to organizations. Meeting notes are routinely recorded in intranets, and (with public organizations) on the internet; however, without semantic content it is very difficult to extract the specific information, analyze it, distribute it, or search it effectively. This investigation seeks to document how meeting minutes on the web are structured, towards a lightweight suite of microformats and format extensions for markup.''
== Participants ==
* ''Brush''

== Real-World Examples ==
''These are fairly random, selected for variety of approach. Research is not yet in-depth. Room for more!''

=== [http://www.geneontology.org/minutes/20050408_Pasadena.txt Gene Ontology Consortium] ===
*Abbreviated organization name
*Dates
*Location (locality, region)
*Next meeting date/location (to be confirmed)
*Participants
**Listed by group-affiliation
**Names in comma-delimited parentheses
**Some groups not represented, still listed (like regrets)
*Nested outline of items (XOXO!)
*Major topic -> subsidiary topic
**Includes introduction, by named presenter(s)
**Discussion item list
***Detailed (but flat) following of arguments pro and con
***Identified conclusions (decisions? not formal?)
***Certain items or references id specific people
**Action items
***listed after each topic
***assigned to a person (or to "everyone")
***Also summarized at end of minutes
***Previous action items listed, with status:
****done
****unresolvable
****in progress
****almost done
****other details, etc.
**Brainstorm section
*Next meetings:
**Types
**Dates
**Locations

=== [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] ===
*Organization, committee
*Date
*Time start/end
*Kind of meeting (ie. special meeting, as opposed to regular)
*Present, with roles:
**member/non-member
**President/Secretary
**organizational affiliations
**also plurally generic (ie. "Hospital Managers and citizens from the community, SEIU 1199NW delegation")
*Outline list (flat) of items
**"Call to order"
**"Oath of office" (ie. establishment of new official roles for individuals)
**Approval of previous minutes (special form of decision)
**Reports from managers/committees
**Authorizations for expenditures
**"Other business"
**Public comment
**Adjournment
*Decisions included in text of items
**motion made
**seconded
**approved unanimously
**included appointments to committees (changes in roles?)
*Items include one, sometimes more specifically referenced speakers

=== [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] ===
*Includes relatively unhelpful presentation-oriented table-of-contents link outline markup (more detail?)
*Title
*Date
*Location
*Attendees
**Affiliation
*High-level item
**Includes one-sentence summary
*Second-level item
**Issue
**Discussion
**Conclusion(s)
***Not clear distinction between decisions and action items
***Some action items attached to specific people

=== [http://mail.gnome.org/archives/foundation-list/2004-April/msg00008.html GNOME/Mozilla Meeting] ===
*Title (included two participating organizations)
*Date
*(Email, so "date sent out" included implicitly)
*Attendance
**Organizational affiliation
**minutes
**chair
*Regrets
*Actions (list)
*Discussion (list tree, no titles)
**Specific items inside each discussion item refer to specific person(s)
**Follow pros and cons of arguments

=== [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] ===
*Organization and committee
*form of meeting (ie. teleconference)
*Date
*Time start/end
*Attendance (noted that all were present throughout) with roles:
**member of committee
**member and chair
**non-member, board secretary
**non-member, general counsel
*XOXO-like outline of items
*"Resolved:" decisions for each item.
**vote count (ie. 4-0)
**who proposed
**who seconded
*Also included items deferred to later meetings

== Existing Practices ==
* ''Summary of common patterns discovered'': Anyone? Some things are fairly obvious...
* ''Other attempts to solve The Problem'': Does anyone have references to other schemae attempted to address this issue? How about a semantically marked up implementation!?
** All W3C meetings are recorded, as a matter of policy. There are zillions of teleconference and ftf meeting records. See [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the ESW wiki] for notes, patterns, and tools, especially [http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm the scribe.perl tool], Zakim, and RRSAgent. ''-DanC''
** The W3C tools assume the following structure, near as I can tell: (DanC, more advice?) (I've eliminated IRC-specific details)
*** Meeting: ''title''
*** Chair: ''name''
*** Scribe: ''name''
*** Agenda: ''URL of agenda - agendas are automatically formed using various tools, and are essentially a flat list of agenda items''
*** Present: ''comma-delimited list of names''
*** Regrets: ''pre-announced non-attendees''
*** Date: ''yup''
*** Topic: ''next in a flat list of agendums; topic name seems to often be (I think) in a well-formed format for reference to a centrally kept list (RDF or other?)''
*** Action: ''list, of, names'' '''to''' ''description of action'' <nowiki>[STATUS]</nowiki>
**** Status is optional
**** May be DONE, PENDING, DROPPED, with other synonyms
**** Again, this is well-tracked between meetings for the purpose of providing open action item lists
*** Resolved: ''description of decision made''
** The vCard spec includes a [http://www.w3.org/2002/12/cal/rfc2445#sec4.6.2 definition for vTodo]. I'm assuming that iCal-basic and hCalendar don't already include this part of the spec, so it could become the basis to an extension of the hCalendar uformat (or a new hTodo?) that defines action items. (Action item management is a core focus of the W3C technical tools above.) This would be integrated into hMinutes.

== Existing Formats ==

See [[meeting-minutes-formats]] for current standards for publishing meeting-minutes.

'''NOTE: This research should be done ''before'' brainstorming proposals.'''

== Proposal ==

''To be moved to [[meeting-minutes-brainstorming]] soon.''

=== hParticipants ===
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

=== hDecision ===
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting?
* Should it be possible to use [http://microformats.org/wiki/xoxo XOXO] ''inside'' the hDecision to give it structure? Hmmmm. Or should it be forced into multiple decisions?
* Should have "description" class, if not included tag is used?

=== hMinutes ===
Example idea:
<pre><nowiki>
<div class="hminutes>

ABC, Inc.
...

<div class="meeting">
Annual Meeting
...
April 10, 2006; 7pm
<div class="hparticipants">
...
</div>
</div>
<div class="topic">
<a href="http://somethingcool" rel="tag">Our first topic</a>

Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.



There is also this action item ''do example markup''



</div>
<div class="topic">
...
</div>
</div>
</nowiki></pre>

=== See Also ===
''Link to related pages as they become available''
* -brainstorming
* -proposal
* -microformat

It is probably better to first:
# analyze what are the 80/20 common elements of the examples above
# complete the research of [[meeting-minutes-formats]]
# and then go about proposing a solution for the whole format, rather than parts of it, while attempting to reuse other [[microformats]] as much as possible. [http://tantek.com/ Tantek]

''True, but rather than documenting a lot of what is in my head I got a bit hasty. Forgive me, will try to keep better on track.''-Brush

== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

meeting-minutes-examples

2006-05-06T20:17:20Z

Brush: /* Proposal */ -- add example structure

= Meeting minutes =
They're typed, they look good, but all the meaning (participants, decisions, action items, etc.) is impossible to glean automatically. Enter hMinutes (or whatever)!

== The Problem ==
''Meeting notes provide a wealth of semantic content, invaluable to organizations. Meeting notes are routinely recorded in intranets, and (with public organizations) on the internet; however, without semantic content it is very difficult to extract the specific information, analyze it, distribute it, or search it effectively. This investigation seeks to document how meeting minutes on the web are structured, towards a lightweight suite of microformats and format extensions for markup.''
== Participants ==
* ''Brush''

== Real-World Examples ==
''These are fairly random, selected for variety of approach. Research is not yet in-depth. Room for more!''

=== [http://www.geneontology.org/minutes/20050408_Pasadena.txt Gene Ontology Consortium] ===
*Abbreviated organization name
*Dates
*Location (locality, region)
*Next meeting date/location (to be confirmed)
*Participants
**Listed by group-affiliation
**Names in comma-delimited parentheses
**Some groups not represented, still listed (like regrets)
*Nested outline of items (XOXO!)
*Major topic -> subsidiary topic
**Includes introduction, by named presenter(s)
**Discussion item list
***Detailed (but flat) following of arguments pro and con
***Identified conclusions (decisions? not formal?)
***Certain items or references id specific people
**Action items
***listed after each topic
***assigned to a person (or to "everyone")
***Also summarized at end of minutes
***Previous action items listed, with status:
****done
****unresolvable
****in progress
****almost done
****other details, etc.
**Brainstorm section
*Next meetings:
**Types
**Dates
**Locations

=== [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] ===
*Organization, committee
*Date
*Time start/end
*Kind of meeting (ie. special meeting, as opposed to regular)
*Present, with roles:
**member/non-member
**President/Secretary
**organizational affiliations
**also plurally generic (ie. "Hospital Managers and citizens from the community, SEIU 1199NW delegation")
*Outline list (flat) of items
**"Call to order"
**"Oath of office" (ie. establishment of new official roles for individuals)
**Approval of previous minutes (special form of decision)
**Reports from managers/committees
**Authorizations for expenditures
**"Other business"
**Public comment
**Adjournment
*Decisions included in text of items
**motion made
**seconded
**approved unanimously
**included appointments to committees (changes in roles?)
*Items include one, sometimes more specifically referenced speakers

=== [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] ===
*Includes relatively unhelpful presentation-oriented table-of-contents link outline markup (more detail?)
*Title
*Date
*Location
*Attendees
**Affiliation
*High-level item
**Includes one-sentence summary
*Second-level item
**Issue
**Discussion
**Conclusion(s)
***Not clear distinction between decisions and action items
***Some action items attached to specific people

=== [http://mail.gnome.org/archives/foundation-list/2004-April/msg00008.html GNOME/Mozilla Meeting] ===
*Title (included two participating organizations)
*Date
*(Email, so "date sent out" included implicitly)
*Attendance
**Organizational affiliation
**minutes
**chair
*Regrets
*Actions (list)
*Discussion (list tree, no titles)
**Specific items inside each discussion item refer to specific person(s)
**Follow pros and cons of arguments

=== [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] ===
*Organization and committee
*form of meeting (ie. teleconference)
*Date
*Time start/end
*Attendance (noted that all were present throughout) with roles:
**member of committee
**member and chair
**non-member, board secretary
**non-member, general counsel
*XOXO-like outline of items
*"Resolved:" decisions for each item.
**vote count (ie. 4-0)
**who proposed
**who seconded
*Also included items deferred to later meetings

== Existing Practices ==
* ''Summary of common patterns discovered'': Anyone? Some things are fairly obvious...
* ''Other attempts to solve The Problem'': Does anyone have references to other schemae attempted to address this issue? How about a semantically marked up implementation!?
** All W3C meetings are recorded, as a matter of policy. There are zillions of teleconference and ftf meeting records. See [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the ESW wiki] for notes, patterns, and tools, especially [http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm the scribe.perl tool], Zakim, and RRSAgent. ''-DanC''
** The W3C tools assume the following structure, near as I can tell: (DanC, more advice?) (I've eliminated IRC-specific details)
*** Meeting: ''title''
*** Chair: ''name''
*** Scribe: ''name''
*** Agenda: ''URL of agenda - agendas are automatically formed using various tools, and are essentially a flat list of agenda items''
*** Present: ''comma-delimited list of names''
*** Regrets: ''pre-announced non-attendees''
*** Date: ''yup''
*** Topic: ''next in a flat list of agendums; topic name seems to often be (I think) in a well-formed format for reference to a centrally kept list (RDF or other?)''
*** Action: ''list, of, names'' '''to''' ''description of action'' <nowiki>[STATUS]</nowiki>
**** Status is optional
**** May be DONE, PENDING, DROPPED, with other synonyms
**** Again, this is well-tracked between meetings for the purpose of providing open action item lists
*** Resolved: ''description of decision made''
** The vCard spec includes a [http://www.w3.org/2002/12/cal/rfc2445#sec4.6.2 definition for vTodo]. I'm assuming that iCal-basic and hCalendar don't already include this part of the spec, so it could become the basis to an extension of the hCalendar uformat (or a new hTodo?) that defines action items. (Action item management is a core focus of the W3C technical tools above.) This would be integrated into hMinutes.

== Existing Formats ==

See [[meeting-minutes-formats]] for current standards for publishing meeting-minutes.

'''NOTE: This research should be done ''before'' brainstorming proposals.'''

== Proposal ==

''To be moved to [[meeting-minutes-brainstorming]] soon.''

=== hParticipants ===
We need a way to list multiple participants -- both in the meeting overall, and in an action item, and perhaps in a decision. So, here's a way to do that:
<pre><nowiki>

...


John Doe
Scribe
...


Mary Smith
Facilitator
Director

...


</nowiki></pre>
* Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
** Inside "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
** Inside, say, hminutes ''and'' <nowiki></nowiki>, the roles define who has what part to play in the action item.
** Inside hminutes ''and'' <nowiki></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
* Also, note that "title" can be used inside hParticipants to define an enduring organizational capacity, rather than a specific role in the immediate context. Does this make sense?

=== hDecision ===
* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
** If not included, parent topic's tag will be used.
* Use hParticipants to identify who is part of decision.
** Can we create a special "Everyone [else]" "hCard" value to include all participants from parent meeting?
* Should it be possible to use [http://microformats.org/wiki/xoxo XOXO] ''inside'' the hDecision to give it structure? Hmmmm. Or should it be forced into multiple decisions?
* Should have "description" class, if not included tag is used?

=== hMinutes ===
Example idea:
<pre><nowiki>
<div class="hminutes>

ABC, Inc.
...

<div class="meeting">
Annual Meeting
...
April 10, 2006; 7pm
<div class="hparticipants">
...
</div>
</div>
<div class="topic">
<a href="http://somethingcool" rel="tag">Our first topic</a>

Well, we discussed this and that. Then we

decided to make a large temple to Indra.


James Mack
came up with the idea
,
but

Everyone else
agreed.



There is also this action item ''do example markup''



</div>
<div class="topic">
...
</div>
</div>
</nowiki></pre>

=== See Also ===
''Link to related pages as they become available''
* -brainstorming
* -proposal
* -microformat

It is probably better to first:
# analyze what are the 80/20 common elements of the examples above
# complete the research of [[meeting-minutes-formats]]
# and then go about proposing a solution for the whole format, rather than parts of it, while attempting to reuse other [[microformats]] as much as possible. [http://tantek.com/ Tantek]

''True, but I got a bit hasty. Forgive me, will try to keep better on track.''-Brush

== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

meeting-minutes-examples

2006-05-06T19:34:49Z

Brush: /* Proposal */ definition for hparticipants?

meeting-minutes-examples

2006-05-06T19:24:11Z

Brush: /* Proposal */ -- hparticipants brainstorm

meeting-minutes-examples

2006-05-06T18:57:36Z

Brush: /* Existing Practices */

meeting-minutes-examples

2006-05-06T18:56:06Z

Brush: /* Existing Practices */

meeting-minutes-examples

2006-05-06T18:52:45Z

Brush: /* Existing Practices */ -- outline syntax of W3C model

meeting-minutes-examples

2006-05-06T18:31:09Z

Brush: /* Existing Practices */

meeting-minutes-examples

2006-05-06T18:10:22Z

Brush: /* Existing Practices */

meeting-minutes-examples

2006-05-06T18:05:40Z

Brush: /* Existing Practices */ - added vTodo info

meeting-minutes-examples

2006-05-04T01:55:29Z

Brush: /* Real-World Examples */

meeting-minutes-examples

2006-05-04T01:53:12Z

Brush: /* Existing Practices */

meeting-minutes-examples

2006-05-04T01:50:36Z

Brush: /* Real-World Examples -- move around, add summary to PHP mtg */

meeting-minutes-examples

2006-05-04T01:40:53Z

Brush: /* = */

meeting-minutes-examples

2006-05-04T01:40:29Z

Brush: /* [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] */

meeting-minutes-examples

2006-05-04T01:32:08Z

Brush: /* = */

meeting-minutes-examples

2006-05-04T01:31:41Z

Brush: /* Example 4 */

meeting-minutes-examples

2006-05-04T01:00:26Z

Brush: /* [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] */

meeting-minutes-examples

2006-05-04T00:52:32Z

Brush: /* [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] */

meeting-minutes-examples

2006-05-04T00:51:31Z

Brush: /* [http://www.stevenshealthcare.org/board_minutes_12.21.05.php Stevens Hospital Board] */

meeting-minutes-examples

2006-05-04T00:51:07Z

Brush: /* 3rd example */

meeting-minutes-examples

2006-05-04T00:33:40Z

Brush: /* [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committee] */

meeting-minutes-examples

2006-05-04T00:23:47Z

Brush: /* [http://www.icann.org/minutes/minutes-10apr06.htm ICANN Executive Committe] */

meeting-minutes-examples

2006-05-04T00:23:21Z

Brush: /* 2nd example */

meeting-minutes-examples

2006-05-04T00:09:47Z

Brush: /* [http://www.php.net/~derick/meeting-notes.html PHP Developers Meeting] */

meeting-minutes-examples

2006-05-04T00:09:04Z

Brush: /* add first example */

meeting-minutes-examples

2006-05-04T00:01:46Z

Brush: /* Participants */

meeting-minutes-examples

2006-05-03T23:59:29Z

Brush:

Main Page

2006-05-03T23:42:15Z

Brush: /* starting exploration of meeting-minutes uformat */

__NOTOC__
__NOTOC__
= Microformats Wiki =

'''Please read [[how-to-play]] before making any edits.'''

'''Please read [[process]] before proposing any new microformats.'''

== Introduction ==

What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]], [[presentations]], and [[podcasts]] are also a good place for some background reading as well. Frequently asked questions are answered in the [[faq]]. Want something or want to contribute? Help with things [[to-do]]. Want to learn more in person? Check out microformats [[events]].

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]
* [[rel-home]] {{NewMarker}}

== Design Patterns ==

Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''

* [[abbr-design-pattern]]
* [[class-design-pattern]]
* [[datetime-design-pattern]]
* [[existing-classes|class names defined across all microformats]]
* [[include-pattern]] {{NewMarker}}
* [[rel-design-pattern]]

== Exploratory discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*[[attention]]
*[[blog-description-examples]]
*[[blog-info-examples]]
*[[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]] (yields [[hatom|hAtom]])
*[[book-examples]], [[book-formats]], [[book-brainstorming]]
*[[chat-examples]], [[chat-formats]]
*[[citation|citation microformat overview]], [[citation-examples]], [[citation-formats]], [[citation-brainstorming]]
*[[comment-problem]], [[comment-examples]], (need to extract from [[comments-formats]])
*[[directions-examples]] {{NewMarker}}
*[[directory-inclusion-examples]], [[directory-inclusion-formats]]. (see also [[rel-directory]])
*[[distributed-conversation]], [[distributed-conversation-brainstorming]], [[distributed-conversation-examples]], [[distributed-conversation-formats]]
*[[forms-examples]]
*[[genealogy-formats]]
*[[hash-examples]]
*[[last-modified-examples]], [[last-modified-formats]], [[last-modified-brainstorming]]
*[[hlisting-proposal]], [[hlisting-feedback]] {{NewMarker}}
**[[listing-examples]], [[listing-formats]], [[listing-brainstorming]]
*[[location-formats]]. (see also [[adr]] and [[geo]])
*[[media-info-examples]]
*[[meeting-minutes-examples]]
*[[mfo-examples]]
*[[music-examples]]
*[[other-formats]]
*[[photo-note-examples]]
*[[recipe-examples]]
*[[requirements-testing]], [[requirements-testing-examples]]
*[[rest-examples]]
*[[resume-brainstorming]], [[resume-formats]]
*[[review-examples]], [[review-formats]] (yielded the [[hreview|hReview]] draft)
*[[search-results-example]]
*[[show-brainstorming]]
*[[showroll-brainstorming]]
*[[table-examples]]
*[[tagspeak-examples]]
*[[transit-table-examples]]
*[[uid]]
*[[widget-examples]], [[widget-brainstorming]]
*[[wiki-formats]]
*[[work-of-art]] {{NewMarker}}
*[[xmdp-brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]] {{NewMarker}}

== Tools & Test Cases & Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[[vcard-implementations]], [[vcard-errata]]
*[[icalendar-implementations]]
*[[faqs-for-rdf]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]] {{NewMarker}}
* [[to-do]]
* [[marked-for-deletion]]

== microformats wiki in other languages ==

You may read and edit microformats articles in <del>many different</del> other languages

=== microformats wiki languages with over 2 articles ===

* [[Main_Page-fr|Français (French)]]
* [[Main_Page-jp|日本語 (Japanese)]] {{NewMarker}}
* [[Main_Page-sp|Español (Spanish)]] {{NewMarker}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

hcalendar-brainstorming

2006-05-03T09:11:11Z

Brush: /* Examples from RFC 2445 */

<h1> hCalendar Brainstorming </h1>

[[to-do]]: this page could use just a bit more clean-up and reorganization. - Tantek

This page is for trying out and documenting ways of using hCalendar which may involve more details than currently in the specification.

If you have a question, please check the [[hcalendar-faq|hCalendar FAQ]], and ask new questions on the [http://microformats.org/discuss/ mailing lists] first.

__TOC__

== Authors ==

* [http://suda.co.uk/ Brian Suda]
* [http://tantek.com/log/ Tantek Çelik]

== hCalendar authoring best practices ==

=== Tabular event calendars ===

Many calendars are posted in tabular form, where the headings on the columns and rows have property values that apply to the cells which themselves are events. E.g. many conferences have multiple tracks and post names of rooms (LOCATION) as column headers, and time slots (DTSTART, DTEND) as row headers.

Here is a description of how to parse such markup into an iCalendar stream. This has been implemented in X2V and deployed.

'''TO DO: document a "How To" for publishers looking to mark up tabular event listings.'''

To enable mark these up with [[hcalendar|hCalendar]], we must parse additional semantic attributes from HTML4.

When parsing, in addition to the special case rules documented in [[hcard-parsing]]:

* If the element is a table data cell <code><td></code>, then:
*# parse its "headers" attribute as a space separated set of local IDs
*# find the <code><td></code> and <code><th></code> elements referenced by those IDs (call them header cells) and consider them part of the element being parsed as follows:
*## Treat the header cells as children of the element, ordered by the order of ids in its "headers" attribute, immediately following the last child node (text or element) or the element. (The basic idea is that the content from those header cells is used to construct the VEVENT, but secondary to (AFTER) the content in the data cell itself, so that the data cell can customize/override part of the data in the header, e.g. if the header cell included both start time and location, and the event was being held at a different location).
*## Parse the "axis" attribute of a header cell as a comma-separated list of categories. These categories must be used in addition to (and before) any class names on that header cell for determining whether it is a property of the VEVENT.

Real world example in the wild of a tabular event calendar marked up in this fashion: [http://we05.com/program.cfm Web Essentials 05 Session program].

'''Note: We have gained sufficient experience with this that we should formalize this in both [[hcard-parsing]] and [[hcalendar-parsing]] since the table cell headers and axis attributes technique is generic to all class name microformats. The specific use case of how to author a tabular display of events should be documented in [[hcalendar-authoring]]. Tantek'''

=== hCard locations ===

In iCalendar (and thus hCalendar), the LOCATION property is just a text string. In practice however, much event content contains some amount of structure for the location, often a specific venue with name, address etc. Venues are often organizations and are thus conducive to being marked up as [[hcard|hCards]].

Taking the example from the [[hcalendar|hCalendar]] spec:

<pre><nowiki>

<a class="url" href="http://www.web2con.com/">
Web 2.0 Conference:
<abbr class="dtstart" title="2005-10-05">October 5</abbr>-
<abbr class="dtend" title="2005-10-08">7</abbr>,
at the Argent Hotel, San Francisco, CA
</a>

</nowiki></pre>

Clearly the "Argent Hotel" is a venue, and thus could be marked up as an [[hcard|hCard]] itself:

<pre><nowiki>

Argent Hotel,
San Francisco, CA

</nowiki></pre>

Thus in the context of the entire vevent this example would become:

<pre><nowiki>

<a class="url" href="http://www.web2con.com/">
Web 2.0 Conference:
<abbr class="dtstart" title="2005-10-05">October 5</abbr>-
<abbr class="dtend" title="2005-10-08">7</abbr>,
at the 
Argent Hotel,
San Francisco, CA

</a>

</nowiki></pre>

The advantage of marking up the location with explicit [[hcard|hCard]] semantics is that it enables much better identification and pivoting of locations of events.

For a real world example of this in practice see Jeremy Keith's excellent SXSW 2006 event page: http://austin.adactio.com/ where all the events contain locations marked up as hCards with [[geo]] properties as well which then aid in locating the precise locations on a map.

'''Note: We have gained sufficient experience with this that we should formalize this in [[hcalendar-authoring]]. Tantek'''

== iCalendar generation best practices ==

Along with the four base properties, you can define addtional properties through the use of the x-prop property. For best-practices for hCal to iCal transformers, it would be helpful if the transforming application added the following x-* properties:

=== X-FROM-URL ===

* X-FROM-URL. The value of this property would be the URL of the page where the iCal representation was generated.
<pre><nowiki>
X-FROM-URL:http://example.com/page-containing-hCal-encoding.html
</nowiki></pre>

'''Note: We have gained sufficient experience with this that we should formalize this in [[hcalendar-parsing]]. Tantek'''

=== X-WR-CALNAME ===

* X-WR-CALNAME. iCal.app recognizes this property as the "calendar name" for subscribed calendars. Thus transforming applications *should* take the <code><title>...</title></code> from the page being parsed, optionally append " events", and use that value for the X-WR-CALNAME property in the resulting feed. E.g. if the page had <code><title>Example Home Page</title></code> then the .ics output should have as part of the vcalendar object:
<pre><nowiki>
X-WR-CALNAME:Example Home Page
</nowiki></pre>

'''Note: We have gained sufficient experience with this that we should formalize this in [[hcalendar-parsing]]. Tantek'''

== iCalendar examples in hCalendar ==

This is a growing example case written in iCal format and transformed to the corresponding XHTML. These conversions are open to community input. See [[hcalendar-examples]] for current work.

<pre><nowiki>
BEGIN:VEVENT
CATEGORIES:foo,bar
SUMMARY: Short Title
DESCRIPTION: Full Description
DTSTART;VALUE=DATE:20040101
DTEND:20040101T235959Z
RRULE:FREQ=YEARLY;UNTIL=20080102T000000Z
URL;WORK:http://example.com
ATTENDEE;ROLE=CHAIR:MAILTO:JohnDoe@example.com
GEO:37.386013;-122.082932
END:VEVENT
</nowiki></pre>
<pre><nowiki>


Categories:
<ul class="categories">
<li>foo</li>
<li>bar</li>
</ul>
<a href="http://example.com" class="summary">Short Title</a>
description
37.386013 -122.082932



Date: 20040101 - 20040101T235959Z




<a class="attendee chair" href="mailto:JohnDoe@example.com">John Doe</a>


The event will be held yearly until 20080102T000000Z.


</nowiki></pre>

@@-need to look at nested tag examples
<pre><nowiki>
XHTML
Short Title to a longer article

vCal
SUMMARY:Short Title
DESCRIPTION:Short Title to a longer article
</nowiki></pre>

=== Examples from RFC 2445 ===

* These examples are now all available on [[hcalendar-examples]].

With the abbr's title attribute being used rather than the node value, the actual data could vary and still represent the same vcalendar.

<pre><nowiki>
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
BEGIN:VEVENT
DTSTART:19970714T170000Z
DTEND:19970715T035959Z
SUMMARY:Bastille Day Party
END:VEVENT
END:VCALENDAR
</nowiki></pre>

<pre><nowiki>


<abbr class="dtstart" title="19970714T170000Z">July 14th</abbr>
<abbr class="dtend" title="19970715T035959Z"></abbr>
Bastille Day Party


</nowiki></pre>

==== UID handling ====

The UID in iCal is represented in HTML as the id attribute in these examples. Any valid id in HTML is a valid UID in iCal, but not the contrapositive, a valid UID is NOT a valid HTML id. HTML ids can only start with a letter, not a number.

<pre><nowiki>
BEGIN:VEVENT
UID:19970901T130000Z-123401@host.com
DTSTAMP:19970901T1300Z
DTSTART:19970903T163000Z
DTEND:19970903T190000Z
SUMMARY:Annual Employee Review
CLASS:PRIVATE
CATEGORIES:BUSINESS,HUMAN RESOURCES
END:VEVENT
</nowiki></pre>

<pre><nowiki>


<abbr class="dtstamp" title="19970901T1300Z"></abbr>
<abbr class="dtstart" title="19970903T163000Z">September 3rd, 4:30pm</abbr>-
<abbr class="dtend" title="19970903T190000Z">7:00pm</abbr>
Annual Employee Review
private
<ul class="categories">
<li>BUSINESS</li>
<li>HUMAN RESOURCES</li>
</ul>


</nowiki></pre>

<pre><nowiki>
BEGIN:VCALENDAR
BEGIN:VEVENT
UID:19970901T130000Z-123402@host.com
DTSTAMP:19970901T1300Z
DTSTART:19970401T163000Z
DTEND:19970402T010000Z
SUMMARY:Laurel is in sensitivity awareness class.
CLASS:PUBLIC
CATEGORIES:BUSINESS,HUMAN RESOURCES
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR
</nowiki></pre>
<pre><nowiki>


<abbr class="dtstamp" title="19970901T1300Z"></abbr>
<abbr class="dtstart" title="19970401T163000Z">April 1st 4:30pm</abbr>-
<abbr class="dtend" title="19970402T010000Z">1:00am</abbr>
Laurel is in sensitivity awareness class.
PUBLIC
<ul class="categories">
<li>BUSINESS</li>
<li>HUMAN RESOURCES</li>
</ul>
Transparent


</nowiki></pre>

==== RRULE handling ====

The way RRULE is encoded should be discussed.

<pre><nowiki>
BEGIN:VEVENT
UID:19970901T130000Z-123403@host.com
DTSTAMP:19970901T1300Z
DTSTART:19971102
SUMMARY:Our Blissful Anniversary
CLASS:CONFIDENTIAL
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
RRULE:FREQ=YEARLY
END:VEVENT
</nowiki></pre>
<pre><nowiki>


<abbr class="dtstart" title="19970901T1300Z"></abbr>
<abbr class="dtend" title="19971102">November 2nd</abbr>
Our Blissful Anniversary
CONFIDENTIAL
<ul class="categories">
<li>ANNIVERSARY</li>
<li>PERSONAL</li>
<li>SPECIAL OCCASION</li>
</ul>
YEARLY


</nowiki></pre>

== Examples from real world event sites ==

=== W3C Meetings ===

I just got email announcing the dates of another W3C meeting. I don't think it's marked up with hCalendar. I could mark it up myself, like I did for [http://www.w3.org/2005/12/allgroupoverview.html the TP day/week schedule], but it might not stick. Somehow I got [http://www.w3.org/2000/08/w3c-synd/ our syndicated news markup] (precursor to [[hAtom]]) to stick, i.e. to become part of the norm in the W3C comm team. I wonder if I could pull that off for calendars.

My first thought is authoring tools, but I don't think I can wait that long.
Next thought is instant-feedback checking tools...
X2V is really handy, but can't be used for confidential pages (and many/most calendars I use are not public).
So.. how about some in-browser javascript "yes, you got it right!" or "hmm... that looks like a date; is there an event you didn't mark up?" feedback? I think I saw something like that in hCalendar implementations.

[[User:DanC|DanC]] 09:00, 3 Feb 2006 (PST)

=== Laughing Squid ===

Laughing Squid had the following [http://laughingsquid.com/squidlist/calendar/9584/2005/4/7 multiple occurence event example]:

Thu, Apr 7 : Tu/Wed: 12-4pm Th/Fr/Sat 12-7pm Sun 12-6pm

In addition, later on in the description, it says:

April 7-21, 2005

This is actually quite a non-trivial example, because the event lasts for different durations on different days (4 hours, 7 hours, 6 hours).

Because of the differing durations, the specification requires that *each* instance of this recurring event be explicitly specified.

But first we markup the starting date and time explicitly:
<pre>
<abbr class="dtstart" title="20050407T1200-0700">Thu, Apr 7</abbr> :
</pre>
Then we put in the quite lengthy explicit specification of every other time the event occurs, marked up around the human readable description.
<pre>
<abbr class="rdate" title="20050407T1200-0700/PT7H, 20050408T1200-0700/PT7H,
20050409T1200-0700/PT7H, 20050410T1200-0700/PT6H, 20050412T1200-0700/PT4H,
20050413T1200-0700/PT4H, 200504014T1200-0700/PT7H, 20050415T1200-0700/PT7H,
20050416T1200-0700/PT7H, 20050417T1200-0700/PT6H, 20050419T1200-0700/PT4H,
20050420T1200-0700/PT4H, 20050421T1200-0700/PT7H" >
Tu/Wed: 12-4pm Th/Fr/Sat 12-7pm Sun 12-6pm
</abbr>
</pre>

The RDATE "PERIOD" format is fairly straightforward. You simply list *each* occurrence of the event, separated by commas. Each occurrence consists of the ISO8601 datetime of the start of the event, followed by a slash "/", followed by *either* the duration of the event (e.g. 7 hours = PT7H), *or* a complete ISO8601 datetime of the end of the event. I chose to use the duration of the event for this example for reason of brevity.

Note that "value=period:" is unnecessary in the rdate value since the parser can infer "value=period:" from the presence of a "/" in the title attribute value.

With simpler repeating events, or perhaps events which only repeat a day or two, their hCalendar markup may be more illustrative of how to do this in a general way.

== CSS Styles ==

Since the hCal properties are added in as HTML class names, you can style them with CSS class selectors along with other HTML class names. You are free to style these properties in any fashion you want (see specific notes), but here are a few examples that you can use.

=== Preserving White-space ===
If you are encoding data that requires tabs, returns, or other white-space to be perserved you can use the following CSS property to do so in HTML.
<pre><nowiki>

This white-space
will be
preserved

</nowiki></pre>
white-space can take one of three different parameters; normal, pre, and no-wrap.

=== Not recommended ===

The following CSS styling techniques are not recommended:

==== Hiding Data ====
It is possible to encode additional data without it being displayed in the HTML, by using the CSS style property 'display'.
<pre><nowiki>
Hidden Data
</nowiki></pre>
This data will be found by any transforming application and will be properly encoded into an iCal file.

'''You SHOULD NOT do this because it violates the visibility priniciple.'''

== Open Questions ==
=== Undecided Encodings of Certain Property Attributes ===
There are several attributes that still need to be discussed about how to property encode them into HTML.

For example the RSVP and ROLE attrbutes:
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:MAILTO:jsmith@host.com
or
ATTENDEE:CUTYPE=GROUP:MAILTO:john@host.com

Other attributes include:
* Delegate-To
* Delegate-from
* Sent-By
* Member
* Partstat
* CN
* DIR

Then all the enumerated possible values for each of these

=== General Questions ===
Q: Should Transforming applications purely extract the information and ignore validity? or should there be some checking, or should this be left to the importing application? (i.e. DTSTART;VALUE=DATE: This-Is-Not-a-proper-date)

A: The simpler the better. Other than checking for perhaps X(HT)ML validity, it should be a simple translator, because presumably the receiving iCalendar application has to have malformed .ics handling already. Let's avoid duplicating that. -- [http://tantek.com/ Tantek Çelik]

Q: What about multiple of the instances same vCal entity? (two instances of DTSTART) Is this left up to the importing application, or should the XSLT transformation fail?

A: Same as previous. Leave it up to the importing application to interpret it per the iCalendar spec, e.g. what does RFC2445 say about two instances of DTSTART? -- [http://tantek.com/ Tantek Çelik]

From RFC2445:
4.1.2 Multiple Values
Some properties defined in the iCalendar object can have multiple values. The general rule for encoding multi-valued items is to simply create a new content line for each value, including the property name. However, it should be noted that some properties support encoding multiple values in a single property by separating the values with a COMMA character (US-ASCII decimal 44). Individual property definitions should be consulted for determining whether a specific property allows multiple values and in which of these two forms.

Other than that, it does not mention what to do ABOUT invalid data, or which of the multiple entries takes precedence. The only mention of duplicate instances is in the RRULE and EXDATE rules where events exclusions/inclusions overlap. Then duplicate instances are ignore. If it is explicitly written for those items, but NOT for things like DTSTART, then it is difficult to assume duplicate instances are ignored for them as well.

Each of the Components (VEVENT, ...) define which properties can exisit and in what quantity. So multiple DTSTART properties are NOT allowed.
-- [http://suda.co.uk Brian Suda]

Q: Should vCal entitles be represented in XHTML in classes ONLY on block-level element? or should some like VEVENT be block-level and others be of any? does this impact the semantics at all?

A: I don't think the (X)HTML notion of "block-level" should have any bearing whatsoever on vCal entities. You should be able to say or <div class="vevent"> and either should work.

Q: Should the transforming application add any additional information to the iCalendar representation other than what was encoded in the HTML? (i.e. UID, the unique identifier might not be present in the HTML code, but could be generated by the transforming application and added to the iCal file. Should this be allowed? or should the transforming app ONLY be allowed to add X-PROPERTY properties?) IF it was not explicitly encoded in the HTML should it be left out? What about default values?

Q: If we are looking at the most semantic way to encoding iCalendar data in HTML then several other attributes should be considered besides just 'class'. There are two other candidated, ID and REL. The ID tag MUST be unique within the XHTML file (this could be used for the UID property). The REL attribute can ONLY be applied to 'a' and 'link' tags, but might be helpful. Are namespac<ETH>H �n option? xml:lang, xml:base, are there any others that might be more semantically correct to encode this data?

Q: To help distinguish xparam values from other actual CSS styles, should we assume/mandate that all values in a class attribute within an encoded iCal component class attribute (<x class="vevent|vtodo|...">) be considered an xparam?

A: If you are using other CSS styles (e.g. "center", "bluebox", "greenline", etc.) nested within an iCal component, those should be avoided and the styles applied to the list of iCal properties instead/also?

<pre><nowiki>
.center, .vevent { text-align: center; }
</nowiki></pre>

Q: What about cases where the words "yesterday", "last year", or "last week" was used? How should we represent this? Is this overkill or not appropriate for hcard ? - [[User:B.K._DeLong]]

A: I took a stab at "yesterday" and just added a dtstart of the previous day. Not sure how to represent a single year or whole week - [[User:B.K._DeLong]]

<pre><nowiki>
<abbr class="dtstart" title="20050114">Yesterday's</abbr>
</nowiki></pre>

=== Recurring Events ===

Recurring events are tricky. First, there's the question of whether to follow ''For types with multiple components, use nested elements with class names equivalent to the names of the components'' a la
<pre>
<nowiki><div class="rrule">every 1
WEEKLY on TU
until 2004-11-01</div></nowiki>
</pre>
... or ...
<pre>
<nowiki><abbr class="rrule" title="FREQ=WEEKLY;COUNT=17;INTERVAL=2;BYDAY=TH"> every other
Thursday for 34 weeks</abbr></nowiki>
</pre>
... as in [http://microformats.org/discuss/mail/microformats-discuss/2005-August/000516.html Tantek's 1 Aug msg].

[http://www.w3.org/People/Connolly/ DanC] has been experimenting with representing his PDA calendar in hCalendar:

* in [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent], there's dangerSync.py which uses the XMLRPC interface and spits out RDF data. Then asHCal.xsl converts that to hCalendar
* then in [http://www.w3.org/2002/12/cal/ the RDF Calendar workspace], there's [http://www.w3.org/2002/12/cal/glean-hcal.xsl glean-hcal.xsl] that turns hCalendar into RDF Calendar, and finally,
* in [http://www.w3.org/2000/10/swap/ SWAP] there's [http://www.w3.org/2000/10/swap/pim/toIcal.py toIcal.py] that turns RDF Calendar to .ics format.

So I can go from my sidekick to .ics with one Makefile.

[http://dev.w3.org/cvsweb/2001/palmagent/event-test.html events-test.html] is a test file that has all the constructs from my PDA data, in hCalendar. In particular, it uses the nested element representation of recurring events. glean-hcal.xsl would be much less fun to write if it had to parse <nowiki>title="FREQ=WEEKLY;COUNT=17;INTERVAL=2;BYDAY=TH"</nowiki>.

Then there's the question of "every tuesday afternoon at 2pm Chicago time". This isn't expressible using [[datetime-design-pattern]]. There are some good reasons for that, but it leaves a rather large and uncomfortable gap in hCalendar.

=== Encoding Questions ===
The way dates are encoded is not always the most user friendly. If i want to encode january 1st, 2005, that is <code>20050101</code>, which is displayed as 20050101. If we are marking-up comma seperated values, like FN, with each sub-element inside their own tag, then the date should be allowed the same.

(However, FN is in the RFC2426 spec and vCard schema, these individual date terms are not, therefore the reasoning in the last sentence is incorrect. -[http://tantek.com/log/ Tantek])

<pre><nowiki>
20050101
20050101
</nowiki></pre>
With this encoding, then YYYYMMDD schema can be rearranged for different cultures, DD-MM-YYYY for UK, MM-DD-YYYY for US, etc.
<pre><nowiki>
02-01-2005
02-01-2005
01-02-2005
01-02-2005
</nowiki></pre>
Both of the above encodings are equal, the '-' seperator is ignored by the transforming application. -- [http://suda.co.uk Brian Suda]

Agreed that the way dates are encoded is not always the most user friendly, but there is an easier solution to this, once you think of what is actually going on in the difference between ISO8601 dates, and dates the way humans use them. Humans typically use an abbrevation or shorthand for a date, like "tomorrow", or "Tuesday", or "the 4th", or perhaps "July 4th". Thus it makes sense to permit this in hCalendar, using the <code><abbr></code> tag which provides the ability to markup the human-familiar short form of some data or language, while preserving the long form in the 'title' attribute.

E.g. for the above example of a start date of January 1st, 2005, you could use this markup:

<pre><nowiki>
<abbr class="dtstart" title="20050101">January 1st, 2005</abbr>
</nowiki></pre>

Which would display as <code>January 1st, 2005</code> but would provide the respective ISO8601 date in the title attribute. - [http://tantek.com/log Tantek]

== TO DO ==
=== XMDP Profile ===
* hCalendar XMDP profile ([[hcalendar-profile]]) needs to be created.

=== Applications ===
A simple implementation of transforming/extracting vCal data from an XHTML file is available for testing. A bookmarklet is also available. The code will be updated as the spec is finalised.
http://suda.co.uk/projects/X2V/ . You may also use http://feeds.technorati.com/events/ for parsing hCalendar events and returning an iCalendar stream.

=== Parsing ===

Need to write up an [[hcalendar-parsing]] document, similar to [[hcard-parsing]].

== Relationships with other microformats ==

In a [http://www.technologyreview.com/articles/04/10/frauenfelder1004.asp Technology Review interview], TBL said "It would have the relationships between the event and the various people chairing it.".

We should have examples of how hCalendar events can indicate such relationships, both in the format and in the presentation.

E.g.:
* Would it just link to URLs for the various people? (e.g. to their homepages/blogs etc.)
* Would it include hCards for the various people?
* Would it link to hCards for various people?
* Perhaps allow all the above?

== Mime-Type ==

According to RFC2445, the proposed media type value is 'text/calendar'.

A standard vCalendar file has an extension of .vcs and MIME type of text/x-vCalendar. If you use iCalendar, the MIME type is "text/Calendar" and the extension is .ics.

Text/X-vCalendar Content Type

The vCalendar object can also be passed as a non-standard MIME media type. This would be useful in order to clearly identify the vCalendar object in an electronic mail message body part. A non-standard, vCalendar object should be identified as the MIME type/subtype "text/x-vCalendar".

@@ - i have to do some more investigation, but (i think) vCalendar is a subset of iCalendar, so many of the same encodings will work for both, but this document is dealing with iCalendar RFC2445 representation!

== Button ==

We need to come up with a nice <code>[ hCal | friendly ]</code> button to indicate that event info on a page/site is using hCalendar. - [http://tantek.com/log/ Tantek].

Possibilities:
* <code>[ hCal | friendly ]</code>
* <code>[ hCal | aware ]</code>
* <code>[ hCal | inside ]</code>
* <code>[ Valid | hCalendar ]</code> - though that would require writing an hCalendar validator which people could link to.
* <code>[ <icon> | hCalendar ]</code> where <icon> could be some generic calendar looking thing, or it could be a PHP generated image with the actual date in the icon, kind of like how the Apple iCal icon updates in the dock automatically.

And then we have to pick colors and all that stuff - [http://tantek.com/log/ Tantek].

Other ideas:
* <code>[ hCal | enabled ]</code>
* <code>[ hCal | available ]</code> - kind of an off-hand reference to being available for meetings, etc.

- [http://meyerweb.com/ Eric]

== Including More of iCalendar ==

=== Free/Busy information ===

See [http://www.ifreebusy.com/cyclical/blog/ Neil Jensen]'s [http://www.ifreebusy.com/cyclical/blog/calendar/3 analysis of how to represent the iCalendar VFREEBUSY object in hCalendar].

In order to show free/busy information, we could either use the existing vevent class (with empty location, summary, etc. properties) or create a new vfreebusy class. We should create a new vfreebusy class because it is consistent with the XHTML design principles, particularly point #4, "Use class names based on names from the original schema...".

In the iCalendar standard, the vfreebusy calendar component frequently has more than one freebusy property, and also may have a number of other properties such as organizer. For example:

<pre><nowiki>
BEGIN:VFREEBUSY
ORGANIZER:jsmith@host.com
DTSTART:19980313T141711Z
DTEND:19980410T141711Z
FREEBUSY:19980314T233000Z/19980315T003000Z
FREEBUSY:19980316T153000Z/19980316T163000Z
FREEBUSY:19980318T030000Z/19980318T040000Z
URL:http://www.host.com/calendar/busytime/jsmith.ifb
END:VFREEBUSY
</nowiki></pre>

So, our hCalendar representation should include separate elements for the vfreebusy calendar component (defined once) and the freebusy property (possibly defined many times):

<pre><nowiki>


<abbr class="dtstart" title="20050721T1000-0800">
July 21, 2005 - 10:00
</abbr> -
<abbr class="dtend" title="20050721T1100-0800">
11:00
</abbr>
 

<abbr class="dtstart" title="20050722T1000-0800">
July 22, 2005 - 10:00
</abbr> -
<abbr class="dtend" title="20050722T1100-0800">
11:00
</abbr>
 

</nowiki></pre>

According to RFC2445, "When publishing a "VFREEBUSY" calendar component, the property is used to specify the calendar that the published busy time came from." The property type is CAL-ADDRESS, and can include "non-standard, language, common name and directory entry reference" property parameters. CAL-ADDRESS is "...a URI as defined by [RFC 1738] or any other IANA registered form...".

From what I've seen, Microsoft Outlook typically populates this property with the email address of the calendar owner, which initially made me think of using hCard to specify the organizer. However, given that the property refers to the calendar and not necessarily the person who owns or has published it, I think we should use a new organizer element, as shown below:

<pre><nowiki>
BEGIN:VFREEBUSY
ORGANIZER:jsmith@host.com
FREEBUSY:20050314T133000Z/20050314T163000Z
END:VFREEBUSY
</nowiki></pre>

becomes

<pre><nowiki>

organizer: jsmith@host.com

<abbr class="dtstart" title="20050314T133000Z">
March 14, 2005 - 13:30
</abbr> -
<abbr class="dtend" title="20050314T163000Z">
16:30
</abbr>
 

</nowiki></pre>

Hmmm, this looks a little funny when the organizer is so obviously an email address, but at least it is semantically correct. The other problem that I can now see occurring is when the organizer property has parameters, for example (from the iCalendar spec):

<pre><nowiki>
ORGANIZER;CN=JohnSmith;DIR="ldap://host.com:6666/o=3DDC%20Associ
ates,c=3DUS??(cn=3DJohn%20Smith)":MAILTO:jsmith@host1.com
</nowiki></pre>

Perhaps it's best to use the same approach described in "Human vs. ISO8601 dates problem solved"; use the abbr element like so:

<pre><nowiki>


organizer: <abbr class="organizer" title="CN=JohnSmith;DIR=ldap://host.com:6666/o=3DDC%20Associ
ates,c=3DUS??(cn=3DJohn%20Smith):MAILTO:jsmith@host1.com">jsmith@host1.com</abbr>
<abbr class="dtstart" title="20050314T133000Z">
March 14, 2005 - 13:30
</abbr> -
<abbr class="dtend" title="20050314T163000Z">
16:30
</abbr>


</nowiki></pre>

=== To-Do information ===

The [http://www.policyawareweb.org/2005/ftf2/paw-mtg Policy Aware Web (PAW) Project Meeting - 23 Aug 2005] uses class="vtodo" to capture action items. Clearly recording action items from a meeting and publishing them as minutes is a good practical example use of the VTODO object on the web.

What's the scenario for usage though?

What kind of indexer/aggregator application would find these VTODO items and what would it do with them?

Perhaps with some way of figuring out who the to-do item is assigned to ("ATTENDEE"), who assigned it ("DELEGATED-FROM"), and a whitelisting of who, perhaps the "ORGANIZER" property, (and their domains/URLs) that a user would accept assignments from, a user could aggregate to-do items assigned from other folks. Then question remains how to update the status ("STATUS") (RFC 2445 4.8.1.11 Status) on that to-do item when it is (a) completed ("COMPLETED"), (b) abandoned/cut/rejected ("CANCELLED"), (c) some progress is made ("IN-PROCESS") etc. There certainly seems to be sufficient expressiveness in VTODO and its properties to do a decentralized to-do list / task distribution system. Could be very interesting for helping open source projects and other distributed teams do project management using the Web.

== References ==
=== Normative References ===
* [http://www.ietf.org/rfc/rfc2445.txt RFC 2445]
* [http://gmpg.org/xmdp/ XMDP]

=== Informative References ===
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars HTMLForCalendars (FOO camp)] - presented just a few days before this, hopefully these efforts can be combine

* [http://www.imc.org/pdi/ Personal Data Interchange (PDI) at the Internet Mail Consortium]
* [http://tantek.com/log/2004/07.html#d27t1049 Markup language design notes]
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class]
* [http://www.ietf.org/rfc/rfc2446.txt iTIP RFC2446]
* [http://www.ietf.org/rfc/rfc2447.txt iMIP RFC2447]
* [http://www.ietf.org/rfc/rfc3283.txt Guide to Internet Calendaring RFC3283]

== Other Implementations/Ideas ==
* [http://www.nehmer.net/~bergie/openpsa-calendar-horizontal.jpg OpenPSA calendar screenshot]
* [http://www.w3.org/2002/12/cal/ RDF Calendar Workspace] - some older work done with RDF, not really applicable to the simple XHTML case, but perhaps worthy of analysis for when and why they may have diverged from established iCalendar schemas.
* [http://planb.nicecupoftea.org/archives/000072.html 2003 RDF icalendar work, xCal references]

== Blogs About Calendaring ==
* http://staff.washington.edu/oren/weblog2/