project-brainstorming - Revision history

Allansideas: /* Suggestion */

2009-07-09T03:51:04Z

Suggestion

← Older revision		Revision as of 03:51, 9 July 2009
Line 154:		Line 154:
	Rather than creating a large format that encompases both here's-how-you-can-do-it-at-home projects and here's-what-we're-doing projects, there is probably more value in creating two small formats, the former as perhaps an evolution of [[hRecipe]] and the latter as perhaps an extension to [[hCard]].		Rather than creating a large format that encompases both here's-how-you-can-do-it-at-home projects and here's-what-we're-doing projects, there is probably more value in creating two small formats, the former as perhaps an evolution of [[hRecipe]] and the latter as perhaps an extension to [[hCard]].

	The hRecipe evolution could be called "hInstructions" - which would semantically separate it from the abstract term. It could, instead of an instructions class have multiple "step" classes each with their own media. It would encompass any description of how to complete a project, including recipes. Perhaps tag could be used to categorize the instruction?		The hRecipe evolution could be called "hInstructions" - which would semantically separate it from the abstract term. It could, instead of an instructions class have multiple "step" classes each with their own media. It would encompass any description of how to complete a project, including recipes. Perhaps tag could be used to categorize the instruction?--[[User:Allansideas\|Allansideas]] 03:51, 9 July 2009 (UTC)

	hCard could be extended, for example, by defining <tt>goal</tt>, <tt>benefactor</tt> (containing an embedded hCard) and <tt>beneficiary</tt> (containing an embedded hCard) classes, and borrowing the <tt>due</tt> class from [[hCalendar]].~~--[[User:Allansideas\|Allansideas]] 03:50, 9 July 2009 (UTC)~~		hCard could be extended, for example, by defining <tt>goal</tt>, <tt>benefactor</tt> (containing an embedded hCard) and <tt>beneficiary</tt> (containing an embedded hCard) classes, and borrowing the <tt>due</tt> class from [[hCalendar]].

	<pre><nowiki><div class="vcard vproject">		<pre><nowiki><div class="vcard vproject">

Allansideas: /* Suggestion */

2009-07-09T03:50:42Z

Suggestion

← Older revision		Revision as of 03:50, 9 July 2009
Line 156:		Line 156:
	The hRecipe evolution could be called "hInstructions" - which would semantically separate it from the abstract term. It could, instead of an instructions class have multiple "step" classes each with their own media. It would encompass any description of how to complete a project, including recipes. Perhaps tag could be used to categorize the instruction?		The hRecipe evolution could be called "hInstructions" - which would semantically separate it from the abstract term. It could, instead of an instructions class have multiple "step" classes each with their own media. It would encompass any description of how to complete a project, including recipes. Perhaps tag could be used to categorize the instruction?

	hCard could be extended, for example, by defining <tt>goal</tt>, <tt>benefactor</tt> (containing an embedded hCard) and <tt>beneficiary</tt> (containing an embedded hCard) classes, and borrowing the <tt>due</tt> class from [[hCalendar]].		hCard could be extended, for example, by defining <tt>goal</tt>, <tt>benefactor</tt> (containing an embedded hCard) and <tt>beneficiary</tt> (containing an embedded hCard) classes, and borrowing the <tt>due</tt> class from [[hCalendar]].--[[User:Allansideas\|Allansideas]] 03:50, 9 July 2009 (UTC)

	<pre><nowiki><div class="vcard vproject">		<pre><nowiki><div class="vcard vproject">

Allansideas: /* Project Type */

2009-07-09T03:50:19Z

Project Type

← Older revision		Revision as of 03:50, 9 July 2009
Line 153:		Line 153:

	Rather than creating a large format that encompases both here's-how-you-can-do-it-at-home projects and here's-what-we're-doing projects, there is probably more value in creating two small formats, the former as perhaps an evolution of [[hRecipe]] and the latter as perhaps an extension to [[hCard]].		Rather than creating a large format that encompases both here's-how-you-can-do-it-at-home projects and here's-what-we're-doing projects, there is probably more value in creating two small formats, the former as perhaps an evolution of [[hRecipe]] and the latter as perhaps an extension to [[hCard]].

			The hRecipe evolution could be called "hInstructions" - which would semantically separate it from the abstract term. It could, instead of an instructions class have multiple "step" classes each with their own media. It would encompass any description of how to complete a project, including recipes. Perhaps tag could be used to categorize the instruction?

	hCard could be extended, for example, by defining <tt>goal</tt>, <tt>benefactor</tt> (containing an embedded hCard) and <tt>beneficiary</tt> (containing an embedded hCard) classes, and borrowing the <tt>due</tt> class from [[hCalendar]].		hCard could be extended, for example, by defining <tt>goal</tt>, <tt>benefactor</tt> (containing an embedded hCard) and <tt>beneficiary</tt> (containing an embedded hCard) classes, and borrowing the <tt>due</tt> class from [[hCalendar]].

Crojecta: /* Digestion */

2009-03-29T05:37:42Z

Digestion

← Older revision		Revision as of 05:37, 29 March 2009
Line 170:		Line 170:
	Remove "Ingredient"<br />		Remove "Ingredient"<br />
	Remove "Yield"<br />		Remove "Yield"<br />
	~~Remove "Duration"<br />~~
	Remove "Nutrition"<br />		Remove "Nutrition"<br />

Crojecta: /* Format */

2009-03-29T04:08:18Z

Format

@@ Line 16: / Line 16: @@
 == Format ==
 === In General ===
-The projecta format is based on a set of fields common to numerous project sites and formats in use today on the web.  Where possible field names have been chosen based on those defined by the related [[hcard|hCard]], [[hatom|hAtom]], [[hcalendar|hCalendar]], and [[hrecipe|hRecipe]].
+The projecta format documents practical (how-you-can-do) projects.  Where possible field names have been chosen based on those defined by the related [[hcard|hCard]], [[hatom|hAtom]], [[hcalendar|hCalendar]], and [[hrecipe|hRecipe]].
 === Schema ===
@@ Line 31: / Line 31: @@
 ** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].
 ** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].
 === Field details ===
@@ Line 137: / Line 109: @@
 * A projecta {{may}} include one or more <code>duration</code>s.
 * The element {{must}} follow the conventions outlined in [[hCalendar]].
 ==Format Development==

Crojecta: /* Digestion */

2009-03-29T03:38:57Z

Digestion

← Older revision		Revision as of 03:38, 29 March 2009
Line 166:		Line 166:

	====Digestion====		====Digestion====
	~~Added field named "type" (re-used from [[hreview\|hReview]]) with options "abstract~~" ~~and~~ "~~practical".~~<br />		The evolution of hRecipe involves the following:
	~~Added field named~~ "~~goals~~".<br />
	~~Added field named~~ "~~instructions~~" ~~(re-used from [[hrecipe\|hRecipe]]).~~<br />		Remove "Ingredient"<br />
	~~Added field named~~ "~~accomplishments~~".<br />		Remove "Yield"<br />
			Remove "Duration"<br />
			Remove "Nutrition"<br />

			Add "Requirement"

			As simple as possible.

	== See Also ==		== See Also ==

Crojecta: /* Format */

2009-03-29T03:38:06Z

Format

Show changes

TobyInk: /* Suggestion */ I did actually preview it before, but somehow didn't spot the b0rken links

2009-03-26T10:21:09Z

Suggestion: I did actually preview it before, but somehow didn't spot the b0rken links

← Older revision		Revision as of 10:21, 26 March 2009
Line 78:		Line 78:
	====Suggestion====		====Suggestion====

	Rather than creating a large format that encompases both here's-how-you-can-do-it-at-home projects and here's-what-we're-doing projects, there is probably more value in creating two small formats, the former as perhaps an evolution of [hRecipe] and the latter as perhaps an extension to [hCard].		Rather than creating a large format that encompases both here's-how-you-can-do-it-at-home projects and here's-what-we're-doing projects, there is probably more value in creating two small formats, the former as perhaps an evolution of [[hRecipe]] and the latter as perhaps an extension to [[hCard]].

	hCard could be extended, for example, by defining <tt>goal</tt>, <tt>benefactor</tt> (containing an embedded hCard) and <tt>beneficiary</tt> (containing an embedded hCard) classes, and borrowing the <tt>due</tt> class from [hCalendar]		hCard could be extended, for example, by defining <tt>goal</tt>, <tt>benefactor</tt> (containing an embedded hCard) and <tt>beneficiary</tt> (containing an embedded hCard) classes, and borrowing the <tt>due</tt> class from [[hCalendar]].

	<pre><nowiki><div class="vcard vproject">		<pre><nowiki><div class="vcard vproject">

TobyInk: /* Suggestion */ split the format in two

2009-03-26T10:20:10Z

Suggestion: split the format in two

@@ Line 77: / Line 77: @@
 ====Suggestion====
-Toby, what do you suggest?
 ====Digestion====

Crojecta: /* Field details */

2009-03-25T05:21:14Z

Field details

← Older revision		Revision as of 05:21, 25 March 2009
Line 44:		Line 44:
	'''type''':: This optional field "type" provides the type of project, one of the following: abstract, practical. If omitted, then in some cases the project type may be inferred. For projects of type "abstract" {{should}} have "goals" and/or "accomplishments" fields completed. For projects of type "practical" {{should}} have "instructions" field completed.		'''type''':: This optional field "type" provides the type of project, one of the following: abstract, practical. If omitted, then in some cases the project type may be inferred. For projects of type "abstract" {{should}} have "goals" and/or "accomplishments" fields completed. For projects of type "practical" {{should}} have "instructions" field completed.

	'''project''':: This required field {{must}} have at a minimum the name ("fn" - the formatted text corresponding to the name) of ''the'' project (a projecta describes only one project), {{may}} provide at least one URI ("url") for the project, and {{may}} provide at least one URL to a photo or depiction ("photo") of the project. However, when using item info subproperties ("fn", "url", "photo"), they {{must}} be nested <em>inside</em> the project element.		'''project''':: This required field {{must}} have at a minimum the name ("fn" - the [http://grammartips.homestead.com/caps.html formatted text] corresponding to the name) of ''the'' project (a projecta describes only one project), {{may}} provide at least one URI ("url") for the project, and {{may}} provide at least one URL to a photo or depiction ("photo") of the project. However, when using item info subproperties ("fn", "url", "photo"), they {{must}} be nested <em>inside</em> the project element.

	'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.		'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.