meeting-minutes-examples - Revision history

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

2006-05-08T17:42:16Z

Proposal: - move to -brainstorming

@@ Line 155: / Line 155: @@
 == Proposal ==
-''To be moved to [[meeting-minutes-brainstorming]] soon.''
+''Moved to [[meeting-minutes-brainstorming]].''
 It is probably better to first:
-# analyze what are the 80/20 common elements of the examples above
+# analyze what are the 80/20 common elements of the examples above. '''Done, at least initially.'''
-# complete the research of [[meeting-minutes-formats]]
+# 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''

Brush: /* Existing Formats */

2006-05-08T17:28:53Z

Existing Formats

← Older revision		Revision as of 17:28, 8 May 2006
Line 151:		Line 151:

	'''NOTE: This research should be done ''before'' brainstorming proposals.'''		'''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 ==		== Proposal ==

Brush: /* Existing Practices */

2006-05-08T17:25:55Z

Existing Practices

← Older revision		Revision as of 17:25, 8 May 2006
Line 117:		Line 117:
	== Existing Practices ==		== Existing Practices ==
	* ''Summary of common patterns discovered'': An informal "80/20" analysis of most commonly used elements:		* ''Summary of common patterns discovered'': An informal "80/20" analysis of most commonly used elements:
	** Title (organization/committee name, sometimes location)		** 80% used items are mostly extremely common:
	** Date (time is fairly common as well)		*** Title (organization/committee name, sometimes location)
	** Participants (almost always include specific notation of Chair and Secretary, regrets also really common)		*** Date (time is fairly common as well)
	** Point list of topics		*** Participants (almost always include specific notation of Chair and Secretary, regrets also really common)
	*** Often flat, but also often nested		*** Point list of topics
	*** 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.)		**** Often flat, but also often nested
	** Decisions (usually include description of how vote broke down, movers, seconders, etc.)		**** 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.)
	** Action items (who assigned to; sometimes status review, date due, etc.)		*** Decisions (usually include description of how vote broke down, movers, seconders, etc.)
	** Next meeting(s) - fairly common		*** Action items (who assigned to; sometimes status review, date due, etc.)
	** ''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.''		*** 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!?		* ''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''		** 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''

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

2006-05-08T17:20:52Z

Existing Practices: - Outline common patterns

← Older revision		Revision as of 17:20, 8 May 2006
Line 116:		Line 116:

	== Existing Practices ==		== Existing Practices ==
	* ''Summary of common patterns discovered'': ~~Anyone?~~ Some ~~things are~~ fairly ~~obvious.~~..		* ''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!?		* ''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''		** 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''

Brush: /* See Also */

2006-05-08T02:17:34Z

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

2006-05-08T02:15:33Z

hMinutes: Include xoxo as structure of topics

← Older revision		Revision as of 02:15, 8 May 2006
Line 195:		Line 195:
	</div>		</div>
	</div>		</div>
	<~~div~~ class="topic">		<ol class="topic xoxo">
	<a href="http://somethingcool" rel="tag"><span class="description">Our first topic</span></a>		<li>
	<~~span~~ class="~~summary~~">		<a href="http://somethingcool/topic/id" title="Would this be different than what is printed?" rel="tag"><span class="description">Our first topic</span></a>
	Well, we discussed this and that. Then we		<dt>
	<span class="hdecision">		<dl class="description">
	<span class="description">decided to make a large temple to Indra.</span>		Well, we discussed this and that. Then we
	<span class="hparticipants">		<span class="hdecision">
	<span class="vcard">		<span class="description">decided to make a large temple to Indra.</span>
	<span class="fn">James Mack</span>		<span class="hparticipants">
	<span class="role" title="mover">came up with the idea</span>		<span class="vcard">
	</span>,		<span class="fn">James Mack</span>
	but		<span class="role" title="mover">came up with the idea</span>
	<span class="vcard">		</span>,
	<span class="fn">Everyone else</span>		but
	<span class="role" title="proponent">agreed</span>.		<span class="vcard">
	</span>		<span class="fn">Everyone else</span>
			<span class="role" title="proponent">agreed</span>.
			</span>
			</span>
			</span>
	<span class="vcalendar">		<span class="vcalendar">
	<span class="vtodo">		<span class="vtodo">
	There is also this action item ''do example markup''		There is also this action item ''do example markup''
	</span>		</span>
	</span>		</span>
	</~~span~~>		</dl>
	<~~/div~~>		<dt>
	~~<div class="~~topic">		<ul>
	...		<li>
	</~~div~~>		... subpoints ...
			</li>
			</ul>
			</li>
			<li>
			... next topic ...
			</li
			</ol>
	</div>		</div>
	</nowiki></pre>		</nowiki></pre>

	=== See Also ===		=== See Also ===
	''Link to related pages as they become available''		''Link to related pages as they become available''

Brush: /* See Also */

2006-05-06T20:21:03Z

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

2006-05-06T20:17:20Z

Proposal: -- add example structure

@@ Line 145: / Line 145: @@
 ''To be moved to [[meeting-minutes-brainstorming]] soon.''
-* 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:
+=== hParticipants ===
 <pre><nowiki>
 <span class="hminutes">
@@ Line 164: / Line 165: @@
 </span>
 </nowiki></pre>
-** Note: ROLE inside an "hparticipants" is strictly limited to the appropriate context.
+* 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 "hminutes" but nothing else, hparticipants' roles define their role for that meeting.
-*** Inside, say, hminutes ''and'' <nowiki><span class="vcalendar"><span class="vtodo"></nowiki>, the roles define who has what part to play in the action item.
+** Inside, say, hminutes ''and'' <nowiki><span class="vcalendar"><span class="vtodo"></nowiki>, the roles define who has what part to play in the action item.
-*** Inside hminutes ''and'' <nowiki><span class="hdecision"><span class="hparticipants"></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer".
+** Inside hminutes ''and'' <nowiki><span class="hdecision"><span class="hparticipants"></nowiki>, the role defines (perhaps) "proponent", or "opponent", or "abstainer" (or "mover", "seconder", "blocker", "standeraside", etc.).
-* ''Link to related pages as they become available''
+* 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?
-** -brainstorming
-** - proposal
+=== hDecision ===
-** -microformat
+* Have an (optional?) topic tag using [http://microformats.org/wiki/reltag reltag].
@@ Line 179: / Line 236: @@
 # 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''

Tantek at 19:53, 6 May 2006

2006-05-06T19:53:46Z

← Older revision		Revision as of 19:53, 6 May 2006
Line 134:		Line 134:
	*** Resolved: ''description of decision made''		*** 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.		** 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 ==		== Proposal ==
	''~~Some ideas, to~~ be moved to -brainstorming soon.''
			''To be moved to [[meeting-minutes-brainstorming]] soon.''

	* 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:		* 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>		<pre><nowiki>
Line 164:		Line 172:
	** - proposal		** - proposal
	** -microformat		** -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]


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

Brush: /* Proposal */ definition for hparticipants?

2006-05-06T19:34:49Z

Proposal: definition for hparticipants?

@@ Line 138: / Line 138: @@
 ''Some ideas, to be moved to -brainstorming soon.''
 * 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:
-** <span class="hparticipants"> <span class="vcard"> ... </span> <span class="vcard"> ... </span> </span>
+<pre><nowiki>
 * ''Link to related pages as they become available''
 ** -brainstorming

← Older revision		Revision as of 02:17, 8 May 2006
Line 238:		Line 238:
	''Link to related pages as they become available''		''Link to related pages as they become available''
	* -brainstorming		* -brainstorming
			* [http://microformats.org/wiki/meeting-minutes-formats meeting-minutes-formats]
	* -proposal		* -proposal
	* -microformat		* -microformat

← Older revision		Revision as of 20:21, 6 May 2006
Line 236:		Line 236:
	# 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]		# 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		''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 ==		== See Also ==
	* ''Other microformats''		* ''Other microformats''
	* ''Normative references for tags used''		* ''Normative references for tags used''