project - Revision history

Tantek: Reverted edits by Niuhaibiao (Talk) to last version by Crojecta

2010-01-14T23:08:37Z

Reverted edits by Niuhaibiao (Talk) to last version by Crojecta

← Older revision		Revision as of 23:08, 14 January 2010
Line 167:		Line 167:
	<li>Put seed(s) in container with potting mix.</li>		<li>Put seed(s) in container with potting mix.</li>
	<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li>		<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li>
	<li>Place container under ~~[http://www.skldintl.com solar garden~~ light] source.</li>		<li>Place container under light source.</li>
	</ol>		</ol>
	</div>		</div>

Niuhaibiao: /* duration */

2010-01-14T06:19:34Z

duration

← Older revision		Revision as of 06:19, 14 January 2010
Line 167:		Line 167:
	<li>Put seed(s) in container with potting mix.</li>		<li>Put seed(s) in container with potting mix.</li>
	<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li>		<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li>
	<li>Place container under light source.</li>		<li>Place container under [http://www.skldintl.com solar garden light] source.</li>
	</ol>		</ol>
	</div>		</div>

Crojecta at 06:52, 29 March 2009

2009-03-29T06:52:45Z

← Older revision		Revision as of 06:52, 29 March 2009
Line 10:		Line 10:
	[[User:ZimbaTm\|ZimbaTm]] 08:31, 12 Jan 2008 (PST)		[[User:ZimbaTm\|ZimbaTm]] 08:31, 12 Jan 2008 (PST)

			== Analysis of Examples (Based on 8 examples.)==

			=== Common practical project fields ===
			* fn (100%)
			* summary (100%)
			* author (50%)
			* instructions (100%)
			* requirement (50%)
			* published (50%)
			* duration (25%)
			* tags (25%)

	~~== Analysis of Examples ==~~		=== Common abstract project fields ===
			* fn (100%)
	=== Common project fields ===		* summary (75%)
	* ~~project~~ (~~name/title\|URL~~(s)~~\|image~~)		* author (50%)
	* ~~author~~ (~~name\|email\|URL~~)		* due (50%)
	* ~~summary~~		* goal (25%)
			* duration (25%)

	== existing formats ==		== existing formats ==
Line 166:		Line 177:
	* Lots of discussion I guess, to satisfy different kinds of projects		* Lots of discussion I guess, to satisfy different kinds of projects
	* Semantic approval of experts		* Semantic approval of experts

	~~== Notes ==~~
	Please, keep the format simple. The current brainstorms above don't follow an existing standard (existing standards must first be documented in [[project-formats]] before proceeeding). It is preferable to re-use and develop minimal modules rather than being verbose. Are these bad or good for example: the uuid:.. or scm:// ones ?

	== Related ideas ==		== Related ideas ==
	* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.		* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.

Crojecta: /* real world examples */

2009-03-29T05:41:02Z

real world examples

← Older revision		Revision as of 05:41, 29 March 2009
Line 10:		Line 10:
	[[User:ZimbaTm\|ZimbaTm]] 08:31, 12 Jan 2008 (PST)		[[User:ZimbaTm\|ZimbaTm]] 08:31, 12 Jan 2008 (PST)

	~~== real world examples ==~~

	~~=== Freshmeat.net ===~~
	~~Description of the software project~~
	* http://freshmeat.net

	** full project name (This is the publicly visible project name.)
	** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)
	** full description
	** short description
	** name of author
	** email address
	** branch name
	** branch description
	** license
	** homepage
	** Tar/GZ
	** Tar/BZ2
	** Zip
	** Changelog
	** RPM package
	** Debian package
	** OS X package
	** Bittorrent
	** BSD Ports URL
	** Autopackage URL
	** Jar
	** Purchase
	** CVS tree (cvsweb)
	** Bug tracker
	** Mailing list archive
	** Mirror site
	** Demo site
	** version
	** release focus
	** Dependencies

	~~=== 43things ===~~
	~~How I did a project~~
	* http://43things.com

	** goal title
	** last words (summary)
	** how (instructions)
	** lessons
	** time taken
	** resources

	~~=== Moldova Aid Project ===~~
	~~A humanitarian aid project~~
	* http://www.moldovaaidproject.org.uk/

	** summary
	** achievements

	~~=== CORDIS ===~~
	~~Community Research and Development Information Service~~
	* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]

	** project title
	** Research area
	** Coordinator (author)
	** Project description
	** Project details
	*** Project Acronym
	*** Project Reference
	*** Start Date
	*** Duration
	*** Project Cost
	*** Contract Type
	*** End Date
	*** Project Status
	*** Project Funding
	** Participants

	~~=== The World Bank ===~~
	~~Moldova Community Forestry Project~~
	* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]

	** project title
	** Project ID
	** Project Status
	** Approval Date
	** Closing Date
	** Total Project Cost
	** Region
	** Major Sector (Sector) (%)
	** Old Major Sector
	** Old Sector
	** Environmental Category
	** Bank Team Lead
	** Borrower
	** Implementing Agency
	** Project Goals
	** Available Project Documents
	** Related Country Information

	~~=== Poncho ===~~
	~~How to make a poncho~~
	* http://orangmerajut.blogspot.com/2005/03/poncho_13.html

	** project title
	** summary
	** Material (requirements)
	** Gauge (notes)
	** directions (instructions)

	~~=== RX-8 iPod Install ===~~
	~~How to install an iPod into an RX-8~~
	* http://www.whatsmyip.org/ipodrx8/

	** title
	** author
	** date
	** Car Compatibility List (summary)
	** Basic Idea (instructions)
	** Tools Needed (requirements)
	** notes
	** WARNING

	~~=== How to fix a CD player ===~~
	* http://www.kuro5hin.org/story/2004/3/24/45212/6874

	** title
	** by (author)
	** date and time submitted
	** tags
	** description
	** summary
	** instructions

	== Analysis of Examples ==		== Analysis of Examples ==

Crojecta: /* In General */

2009-03-29T04:04:13Z

In General

← Older revision		Revision as of 04:04, 29 March 2009
Line 168:		Line 168:
	== Format ==		== Format ==
	=== In General ===		=== 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 ===		=== Schema ===

Crojecta: /* brainstorming */

2009-03-29T03:50:29Z

brainstorming

Show changes

Crojecta: /* brainstorming */

2009-03-25T05:10:29Z

brainstorming

← Older revision		Revision as of 05:10, 25 March 2009
Line 171:		Line 171:
	* projecta ('''<code>projecta</code>''')		* projecta ('''<code>projecta</code>''')
	** '''version'''. optional. text.		** '''version'''. optional. text.
	** '''summary'''. optional. text. ~~one sentence~~.		** '''summary'''. optional. text. serves as the title for the project.
	** '''type'''. optional. abstract \| practical.		** '''type'''. optional. abstract \| practical.
	** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' \|\| '''<code>photo</code>''' )		** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' \|\| '''<code>photo</code>''' )
Line 188:		Line 188:
	'''version''':: This optional field permits projecta publishers to specify a particular version of projecta that their content uses. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.1".		'''version''':: This optional field permits projecta publishers to specify a particular version of projecta that their content uses. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.1".

	'''summary''':: This optional field serves as ~~a one sentence summary of~~ the project.		'''summary''':: This optional field serves as the title for the project..

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

Crojecta: /* 43things */

2009-03-25T01:15:03Z

43things

← Older revision		Revision as of 01:15, 25 March 2009
Line 53:		Line 53:
	** goal title		** goal title
	** last words (summary)		** last words (summary)
	** how		** how (instructions)
	** lessons		** lessons
	** time taken		** time taken

Crojecta: /* real world examples */

2009-03-25T01:10:50Z

real world examples

← Older revision		Revision as of 01:10, 25 March 2009
Line 47:		Line 47:
	** Dependencies		** Dependencies

	=== 43things~~.com~~ ===		=== 43things ===
			How I did a project
	* http://43things.com		* http://43things.com
	~~How I did a project~~

	** goal title		** goal title
	** last words (~~One sentence~~ summary.)		** last words (summary)
	** how		** how
	** lessons		** lessons
Line 71:		Line 71:
	** project title		** project title
	** Research area		** Research area
	** Coordinator		** Coordinator (author)
	** Project description		** Project description
	** Project details		** Project details
			*** Project Acronym
			*** Project Reference
			*** Start Date
			*** Duration
			*** Project Cost
			*** Contract Type
			*** End Date
			*** Project Status
			*** Project Funding
	** Participants		** Participants

Line 104:		Line 113:
	** project title		** project title
	** summary		** summary
	** Material		** Material (requirements)
	** Gauge		** Gauge (notes)
	** directions		** directions (instructions)

			=== RX-8 iPod Install ===
			How to install an iPod into an RX-8
			* http://www.whatsmyip.org/ipodrx8/

			** title
			** author
			** date
			** Car Compatibility List (summary)
			** Basic Idea (instructions)
			** Tools Needed (requirements)
			** notes
			** WARNING

			=== How to fix a CD player ===
			* http://www.kuro5hin.org/story/2004/3/24/45212/6874

			** title
			** by (author)
			** date and time submitted
			** tags
			** description
			** summary
			** instructions

	== Analysis of Examples ==		== Analysis of Examples ==

Crojecta: /* brainstorming */

2009-03-25T00:46:32Z

brainstorming

← Older revision		Revision as of 00:46, 25 March 2009
Line 136:		Line 136:
	The projecta schema consists of the following:		The projecta schema consists of the following:

	* ~~Projecta~~ ('''<code>projecta</code>''')		* projecta ('''<code>projecta</code>''')
	** '''~~<code>~~version~~</code>~~'''. optional. text.		** '''version'''. optional. text.
	** '''~~<code>~~summary~~</code>~~'''. optional. text.		** '''summary'''. optional. text. one sentence.
	** '''<code>~~project~~</code>''' ~~info. required.~~ ('''<code>url</code>''' \|\| '''<code>photo</code>''' )		** '''type'''. optional. abstract \| practical.
	** '''~~<code>~~author~~</code>~~'''. optional. '''[[hcard\|hCard]]'''.		** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' \|\| '''<code>photo</code>''' )
	** '''~~<code>~~description~~</code>~~'''. optional. text with optional valid HTML markup.		** '''author'''. optional. '''[[hcard\|hCard]]'''.
	** ~~requirements~~. optional. text with optional '''<code>~~url~~</code>''' ~~to products or other projects~~.		** '''description'''. optional. text with optional valid HTML markup.
	** ~~steps~~. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.		** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.
	** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.		** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.
	** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.		** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.
			** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list.
			** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.
			** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.

	=== Field details ===		=== Field details ===
Line 152:		Line 155:
	'''version''':: This optional field permits projecta publishers to specify a particular version of projecta that their content uses. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.1".		'''version''':: This optional field permits projecta publishers to specify a particular version of projecta that their content uses. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.1".

	'''summary''':: This optional field serves as a ~~title for~~ the project ~~itself~~.		'''summary''':: This optional field serves as a one sentence summary of the project.

	'''~~project info~~''':: This ~~required~~ field {{~~must~~}} have ~~at a minimum the name However, when using item info subproperties (~~"fn", "~~url~~", "~~photo~~"~~), they~~ {{~~must~~}} ~~be nested <em>inside</em> the item element~~.		'''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.

	'''~~author~~''':: ~~The optional~~ field ~~specifies~~ the ~~person who authored~~ the project~~. If~~ the ~~author is specified~~, ~~an hCard representing the author~~ {{~~must~~}} ~~be provided.~~		'''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.
	~~The projecta format is intended~~ to ~~be used in conjunction with MediaWiki which will require~~ a ~~username to submit a new~~ project. ~~The username will~~ be ~~represented with an hCard~~.

	'''description''':: This optional field contains the full text representing the ~~written opinion~~ of the author. The field {{may}} include valid HTML markup (e.g. paragraphs). User agents {{should}} preserve any markup.		'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.

			'''description''':: This optional field contains the full text representing the input of the author. The field {{may}} include valid HTML markup (e.g. paragraphs). User agents {{should}} preserve any markup.

			'''goals''':: This optional field documents the project's goals.

			'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe\|hRecipe]].

			'''accomplishments''':: This optional field documents the project's accomplishments.

	'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.		'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.

	~~'''steps''':: Steps are represented using an ordered list of tasks required to complete the project. Represented as an ordered list with list elements.~~

	'''tags''':: Tags are represented using a list of keywords or phrases (using the [[rel-tag]] microformat for each individual keyword or phrase tag) that the author associates with the project.		'''tags''':: Tags are represented using a list of keywords or phrases (using the [[rel-tag]] microformat for each individual keyword or phrase tag) that the author associates with the project.

	'''permalink''':: This optional field is a URL for the projecta. In addition to using the <code><a href></code> tag for this field, the attribute <code>rel="self bookmark"</code> {{must}} be used to indicate that the hyperlink is a permalink for the project itself. If the hyperlink already contains a <code>rel</code> attribute, then the values <code>self</code> and <code>bookmark</code> {{must}} be included among the space-separated set of values in the attribute. Indexers {{may}} treat the permalink of a project as a unique ID in order to identify and collate the same project from multiple sources (such as indexing a page multiple times). The permalink {{may}} also be used to indicate or imply the origin of the project. Authors {{may}} use the classname of "permalink" on the element representing the permalink.		'''permalink''':: This optional field is a URL for the projecta. In addition to using the <code><a href></code> tag for this field, the attribute <code>rel="self bookmark"</code> {{must}} be used to indicate that the hyperlink is a permalink for the project itself. If the hyperlink already contains a <code>rel</code> attribute, then the values <code>self</code> and <code>bookmark</code> {{must}} be included among the space-separated set of values in the attribute. Indexers {{may}} treat the permalink of a project as a unique ID in order to identify and collate the same project from multiple sources (such as indexing a page multiple times). The permalink {{may}} also be used to indicate or imply the origin of the project. Authors {{may}} use the classname of "permalink" on the element representing the permalink.

	The following field names have been reused from the [[hcard\|hCard]], [[hcalendar\|hCalendar]], and [[hreview\|hReview]] microformats: <code>version, summary, fn, url, photo, description, tags, permalink</code>. In addition, items and authors described by hCards {{may}} contain any hCard field. The rel value "self" has been reused from the [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0 specification].