https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=CrojectaMicroformats Wiki - User contributions [en]2026-05-25T11:51:11ZUser contributionsMediaWiki 1.38.4https://microformats.org/wiki/index.php?title=projecta&diff=38263projecta2009-03-29T07:38:51Z<p>Crojecta: </p>
<hr />
<div>== Format ==<br />
=== In General ===<br />
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]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following elements:<br />
<br />
* '''projecta'''<br />
** '''''fn'''''. required. text. the formatted name of the project. re-used from [[hCard]].<br />
** '''''summary'''''. optional. text. re-used from [[hCalendar]].<br />
** '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]].<br />
** ''published''. optional. re-used from [[hAtom]]. [experimental]<br />
** ''tag''. optional. 1 or more. re-used from [[rel-tag]]. [experimental]<br />
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [experimental]<br />
** ''requirement''. optional. text with optional valid (x)HTML markup.<br />
** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].<br />
** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
==== fn ====<br />
<br />
The title of a single project. The formatted name of what the projecta documents.<br />
<br />
* The element is identified by class name <code>fn</code>.<br />
* A projecta {{must}} include a <code> fn </code>.<br />
* The element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== summary ====<br />
<br />
The summary provides a short introduction to or an accompanying statement about the project.<br />
<br />
* The element is identified by the class name <code>summary</code>.<br />
* A projecta {{may}} include a <code>summary</code>.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==== author ====<br />
<br />
The person who authored the project.<br />
<br />
* The element is identified by class name <code>author</code>.<br />
* A projecta {{may}} include one or more <code>author</code> elements.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== published ====<br />
<br />
The date the project was published.<br />
<br />
* The element is identified by the class name <code>published</code>.<br />
* A projecta {{may}} include a <code>published</code> date.<br />
* The element {{must}} follow the conventions outlined in [[hAtom]].<br />
* The [[datetime-design-pattern]] {{should}} be used to encode the published datetime.<br />
* The element is considered ''experimental'' and may be removed from the final specification.<br />
<br />
==== tag ====<br />
<br />
A keyword indicating a subject or an important aspect of the project like it's main requirement, type of project etc.<br />
<br />
* The element is identified by class name <code>tag</code>.<br />
* A projecta {{may}} include one or more <code>tag</code> elements.<br />
* The element {{must}} follow the conventions outlined in [[rel-tag]].<br />
<br />
==== photo ====<br />
<br />
Accompanying image.<br />
<br />
* The element is identified by the class name <code>photo</code>.<br />
* A projecta {{may}} include one or more photo elements.<br />
* The element {{should}} use an &lt;img&gt; element.<br />
* The element {{may}} use any other element that contains a URL, such as &lt;a&gt; or &lt;object&gt;, but it is not recommended.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== requirement ====<br />
<br />
Describes one or more requirements of the project.<br />
<br />
* The element is identified by the class name <code>requirement</code>.<br />
* A projecta {{must}} include one or more <code>requirement</code>s.<br />
* The field {{may}} include valid HTML markup (e.g. a list of requirements).<br />
<br />
==== instructions ====<br />
<br />
Documents the instructions required to complete the project.<br />
<br />
* The element is identified by the class name <code>instructions</code>.<br />
* A projecta {{may}} include a <code>instructions</code> element. <br />
* The field {{may}} include valid HTML markup e.g. paragraphs or a list of steps.<br />
<br />
==== duration ====<br />
<br />
The time it takes to complete the project described by the projecta. Multiple duration fields can be used to denote time taken per instruction.<br />
* The element is identified by the class name <code>duration</code>.<br />
* A projecta {{may}} include one or more <code>duration</code>s.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
<pre><nowiki><br />
<div class="projecta"><br />
<h3 class="fn">Germinating Seeds</h3><br />
<p class="summary"><br />
How to germinate seeds in potting mix.<br /><br />
</p><br />
<p class="vcard fn">Derek Lewis</p><br />
<p>Published <abbr class="published" title="2009-03-28T09:30-11:00">28. Mar 2009</abbr></p><br />
<img src="/img/seed.png" class="photo" width="100" height="100" alt="Seed"/><br />
<h4>Requirements</h4><br />
<ul class="requirement"><br />
<li>Container(s) (With drain holes)</li><br />
<li>Seed(s)</li><br />
<li>Potting Mix</li><br />
<li>Fresh Water</li><br />
<li>A Light Source</li><br />
</ul><br />
<h4>Instructions</h4><br />
<ol class="instructions"><br />
<li>Loosen and dampen the potting mix.</li><br />
<li>Fill 2/3 of each container(s) with potting mix.</li><br />
<li>Put seed(s) in container with potting mix.</li><br />
<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li><br />
<li>Place container under light source.</li><br />
</ol><br />
</div><br />
</nowiki></pre></div>Crojectahttps://microformats.org/wiki/index.php?title=project&diff=38262project2009-03-29T06:52:45Z<p>Crojecta: </p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
'''View each individual page as the main page omits some content.'''<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
== Analysis of Examples (Based on 8 examples.)==<br />
<br />
=== Common practical project fields ===<br />
* fn (100%)<br />
* summary (100%)<br />
* author (50%)<br />
* instructions (100%)<br />
* requirement (50%)<br />
* published (50%)<br />
* duration (25%)<br />
* tags (25%)<br />
<br />
=== Common abstract project fields ===<br />
* fn (100%)<br />
* summary (75%)<br />
* author (50%)<br />
* due (50%)<br />
* goal (25%)<br />
* duration (25%)<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
== Format ==<br />
=== In General ===<br />
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]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following elements:<br />
<br />
* '''projecta'''<br />
** '''''fn'''''. required. text. the formatted name of the project. re-used from [[hCard]].<br />
** '''''summary'''''. optional. text. re-used from [[hCalendar]].<br />
** '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]].<br />
** ''published''. optional. re-used from [[hAtom]]. [experimental]<br />
** ''tag''. optional. 1 or more. re-used from [[rel-tag]]. [experimental]<br />
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [experimental]<br />
** ''requirement''. optional. text with optional valid (x)HTML markup.<br />
** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].<br />
** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
==== fn ====<br />
<br />
The title of a single project. The formatted name of what the projecta documents.<br />
<br />
* The element is identified by class name <code>fn</code>.<br />
* A projecta {{must}} include a <code> fn </code>.<br />
* The element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== summary ====<br />
<br />
The summary provides a short introduction to or an accompanying statement about the project.<br />
<br />
* The element is identified by the class name <code>summary</code>.<br />
* A projecta {{may}} include a <code>summary</code>.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==== author ====<br />
<br />
The person who authored the project.<br />
<br />
* The element is identified by class name <code>author</code>.<br />
* A projecta {{may}} include one or more <code>author</code> elements.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== published ====<br />
<br />
The date the project was published.<br />
<br />
* The element is identified by the class name <code>published</code>.<br />
* A projecta {{may}} include a <code>published</code> date.<br />
* The element {{must}} follow the conventions outlined in [[hAtom]].<br />
* The [[datetime-design-pattern]] {{should}} be used to encode the published datetime.<br />
* The element is considered ''experimental'' and may be removed from the final specification.<br />
<br />
==== tag ====<br />
<br />
A keyword indicating a subject or an important aspect of the project like it's main requirement, type of project etc.<br />
<br />
* The element is identified by class name <code>tag</code>.<br />
* A projecta {{may}} include one or more <code>tag</code> elements.<br />
* The element {{must}} follow the conventions outlined in [[rel-tag]].<br />
<br />
==== photo ====<br />
<br />
Accompanying image.<br />
<br />
* The element is identified by the class name <code>photo</code>.<br />
* A projecta {{may}} include one or more photo elements.<br />
* The element {{should}} use an &lt;img&gt; element.<br />
* The element {{may}} use any other element that contains a URL, such as &lt;a&gt; or &lt;object&gt;, but it is not recommended.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== requirement ====<br />
<br />
Describes one or more requirements of the project.<br />
<br />
* The element is identified by the class name <code>requirement</code>.<br />
* A projecta {{must}} include one or more <code>requirement</code>s.<br />
* The field {{may}} include valid HTML markup (e.g. a list of requirements).<br />
<br />
==== instructions ====<br />
<br />
Documents the instructions required to complete the project.<br />
<br />
* The element is identified by the class name <code>instructions</code>.<br />
* A projecta {{may}} include a <code>instructions</code> element. <br />
* The field {{may}} include valid HTML markup e.g. paragraphs or a list of steps.<br />
<br />
==== duration ====<br />
<br />
The time it takes to complete the project described by the projecta. Multiple duration fields can be used to denote time taken per instruction.<br />
* The element is identified by the class name <code>duration</code>.<br />
* A projecta {{may}} include one or more <code>duration</code>s.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
<pre><nowiki><br />
<div class="projecta"><br />
<h3 class="fn">Germinating Seeds</h3><br />
<p class="summary"><br />
How to germinate seeds in potting mix.<br /><br />
</p><br />
<p class="vcard fn">Derek Lewis</p><br />
<p>Published <abbr class="published" title="2009-03-28T09:30-11:00">28. Mar 2009</abbr></p><br />
<img src="/img/seed.png" class="photo" width="100" height="100" alt="Seed"/><br />
<h4>Requirements</h4><br />
<ul class="requirement"><br />
<li>Container(s) (With drain holes)</li><br />
<li>Seed(s)</li><br />
<li>Potting Mix</li><br />
<li>Fresh Water</li><br />
<li>A Light Source</li><br />
</ul><br />
<h4>Instructions</h4><br />
<ol class="instructions"><br />
<li>Loosen and dampen the potting mix.</li><br />
<li>Fill 2/3 of each container(s) with potting mix.</li><br />
<li>Put seed(s) in container with potting mix.</li><br />
<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li><br />
<li>Place container under light source.</li><br />
</ol><br />
</div><br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38261project-examples2009-03-29T06:46:51Z<p>Crojecta: </p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
There are two types of projects being documented on the web. Practical (how-you-can-do-it) and Abstract (what-we're-doing).<br />
Fields in [brackets] have already been accommodated for. <br />
<br />
== Practical Projects (how-you-can-do-it) ==<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title [fn]<br />
** last words [summary]<br />
** how [instructions]<br />
** lessons<br />
** time taken [duration]<br />
** resources<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title [fn]<br />
** [summary]<br />
** Material [requirement]<br />
** Gauge<br />
** directions [instructions]<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title [fn]<br />
** [author]<br />
** date [published]<br />
** Car Compatibility List [summary]<br />
** Basic Idea [instructions]<br />
** Tools Needed [requirement]<br />
** notes<br />
** WARNING<br />
<br />
=== How to fix a CD player ===<br />
* http://www.kuro5hin.org/story/2004/3/24/45212/6874<br />
<br />
** title [fn]<br />
** by [author]<br />
** date and time submitted [published]<br />
** [tags]<br />
** description<br />
** [summary]<br />
** [instructions]<br />
<br />
== Abstract Projects (what-we're-doing) ==<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title [fn]<br />
** Research area<br />
** Coordinator [author]<br />
** Project description [summary]<br />
** Project details<br />
*** Project Acronym<br />
*** Project Reference<br />
*** Start Date<br />
*** [duration]<br />
*** Project Cost<br />
*** Contract Type<br />
*** End Date [due]<br />
*** Project Status<br />
*** Project Funding<br />
** Participants <br />
<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.) [fn]<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description <br />
** short description [summary]<br />
** name of author [author]<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage [url]<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** title [fn]<br />
** [summary]<br />
** achievements<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title [fn]<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date [due]<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals [goal]<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
== Analysis of Examples (Based on 8 examples.)==<br />
<br />
=== Common practical project fields ===<br />
* fn (100%)<br />
* summary (100%)<br />
* author (50%)<br />
* instructions (100%)<br />
* requirement (50%)<br />
* published (50%)<br />
* duration (25%)<br />
* tags (25%)<br />
<br />
=== Common abstract project fields ===<br />
* fn (100%)<br />
* summary (75%)<br />
* author (50%)<br />
* due (50%)<br />
* goal (25%)<br />
* duration (25%)<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project&diff=38260project2009-03-29T05:41:02Z<p>Crojecta: /* real world examples */</p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
'''View each individual page as the main page omits some content.'''<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
== Format ==<br />
=== In General ===<br />
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]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following elements:<br />
<br />
* '''projecta'''<br />
** '''''fn'''''. required. text. the formatted name of the project. re-used from [[hCard]].<br />
** '''''summary'''''. optional. text. re-used from [[hCalendar]].<br />
** '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]].<br />
** ''published''. optional. re-used from [[hAtom]]. [experimental]<br />
** ''tag''. optional. 1 or more. re-used from [[rel-tag]]. [experimental]<br />
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [experimental]<br />
** ''requirement''. optional. text with optional valid (x)HTML markup.<br />
** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].<br />
** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
==== fn ====<br />
<br />
The title of a single project. The formatted name of what the projecta documents.<br />
<br />
* The element is identified by class name <code>fn</code>.<br />
* A projecta {{must}} include a <code> fn </code>.<br />
* The element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== summary ====<br />
<br />
The summary provides a short introduction to or an accompanying statement about the project.<br />
<br />
* The element is identified by the class name <code>summary</code>.<br />
* A projecta {{may}} include a <code>summary</code>.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==== author ====<br />
<br />
The person who authored the project.<br />
<br />
* The element is identified by class name <code>author</code>.<br />
* A projecta {{may}} include one or more <code>author</code> elements.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== published ====<br />
<br />
The date the project was published.<br />
<br />
* The element is identified by the class name <code>published</code>.<br />
* A projecta {{may}} include a <code>published</code> date.<br />
* The element {{must}} follow the conventions outlined in [[hAtom]].<br />
* The [[datetime-design-pattern]] {{should}} be used to encode the published datetime.<br />
* The element is considered ''experimental'' and may be removed from the final specification.<br />
<br />
==== tag ====<br />
<br />
A keyword indicating a subject or an important aspect of the project like it's main requirement, type of project etc.<br />
<br />
* The element is identified by class name <code>tag</code>.<br />
* A projecta {{may}} include one or more <code>tag</code> elements.<br />
* The element {{must}} follow the conventions outlined in [[rel-tag]].<br />
<br />
==== photo ====<br />
<br />
Accompanying image.<br />
<br />
* The element is identified by the class name <code>photo</code>.<br />
* A projecta {{may}} include one or more photo elements.<br />
* The element {{should}} use an &lt;img&gt; element.<br />
* The element {{may}} use any other element that contains a URL, such as &lt;a&gt; or &lt;object&gt;, but it is not recommended.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== requirement ====<br />
<br />
Describes one or more requirements of the project.<br />
<br />
* The element is identified by the class name <code>requirement</code>.<br />
* A projecta {{must}} include one or more <code>requirement</code>s.<br />
* The field {{may}} include valid HTML markup (e.g. a list of requirements).<br />
<br />
==== instructions ====<br />
<br />
Documents the instructions required to complete the project.<br />
<br />
* The element is identified by the class name <code>instructions</code>.<br />
* A projecta {{may}} include a <code>instructions</code> element. <br />
* The field {{may}} include valid HTML markup e.g. paragraphs or a list of steps.<br />
<br />
==== duration ====<br />
<br />
The time it takes to complete the project described by the projecta. Multiple duration fields can be used to denote time taken per instruction.<br />
* The element is identified by the class name <code>duration</code>.<br />
* A projecta {{may}} include one or more <code>duration</code>s.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
<pre><nowiki><br />
<div class="projecta"><br />
<h3 class="fn">Germinating Seeds</h3><br />
<p class="summary"><br />
How to germinate seeds in potting mix.<br /><br />
</p><br />
<p class="vcard fn">Derek Lewis</p><br />
<p>Published <abbr class="published" title="2009-03-28T09:30-11:00">28. Mar 2009</abbr></p><br />
<img src="/img/seed.png" class="photo" width="100" height="100" alt="Seed"/><br />
<h4>Requirements</h4><br />
<ul class="requirement"><br />
<li>Container(s) (With drain holes)</li><br />
<li>Seed(s)</li><br />
<li>Potting Mix</li><br />
<li>Fresh Water</li><br />
<li>A Light Source</li><br />
</ul><br />
<h4>Instructions</h4><br />
<ol class="instructions"><br />
<li>Loosen and dampen the potting mix.</li><br />
<li>Fill 2/3 of each container(s) with potting mix.</li><br />
<li>Put seed(s) in container with potting mix.</li><br />
<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li><br />
<li>Place container under light source.</li><br />
</ol><br />
</div><br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Notes ==<br />
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 ?<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38259project-brainstorming2009-03-29T05:37:42Z<p>Crojecta: /* Digestion */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following elements:<br />
<br />
* '''projecta'''<br />
** '''''fn'''''. required. text. the formatted name of the project. re-used from [[hCard]].<br />
** '''''summary'''''. optional. text. re-used from [[hCalendar]].<br />
** '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]].<br />
** ''published''. optional. re-used from [[hAtom]]. [experimental]<br />
** ''tag''. optional. 1 or more. re-used from [[rel-tag]]. [experimental]<br />
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [experimental]<br />
** ''requirement''. optional. text with optional valid (x)HTML markup.<br />
** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].<br />
** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
==== fn ====<br />
<br />
The title of a single project. The formatted name of what the projecta documents.<br />
<br />
* The element is identified by class name <code>fn</code>.<br />
* A projecta {{must}} include a <code> fn </code>.<br />
* The element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== summary ====<br />
<br />
The summary provides a short introduction to or an accompanying statement about the project.<br />
<br />
* The element is identified by the class name <code>summary</code>.<br />
* A projecta {{may}} include a <code>summary</code>.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==== author ====<br />
<br />
The person who authored the project.<br />
<br />
* The element is identified by class name <code>author</code>.<br />
* A projecta {{may}} include one or more <code>author</code> elements.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== published ====<br />
<br />
The date the project was published.<br />
<br />
* The element is identified by the class name <code>published</code>.<br />
* A projecta {{may}} include a <code>published</code> date.<br />
* The element {{must}} follow the conventions outlined in [[hAtom]].<br />
* The [[datetime-design-pattern]] {{should}} be used to encode the published datetime.<br />
* The element is considered ''experimental'' and may be removed from the final specification.<br />
<br />
==== tag ====<br />
<br />
A keyword indicating a subject or an important aspect of the project like it's main requirement, type of project etc.<br />
<br />
* The element is identified by class name <code>tag</code>.<br />
* A projecta {{may}} include one or more <code>tag</code> elements.<br />
* The element {{must}} follow the conventions outlined in [[rel-tag]].<br />
<br />
==== photo ====<br />
<br />
Accompanying image.<br />
<br />
* The element is identified by the class name <code>photo</code>.<br />
* A projecta {{may}} include one or more photo elements.<br />
* The element {{should}} use an &lt;img&gt; element.<br />
* The element {{may}} use any other element that contains a URL, such as &lt;a&gt; or &lt;object&gt;, but it is not recommended.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== requirement ====<br />
<br />
Describes one or more requirements of the project.<br />
<br />
* The element is identified by the class name <code>requirement</code>.<br />
* A projecta {{must}} include one or more <code>requirement</code>s.<br />
* The field {{may}} include valid HTML markup (e.g. a list of requirements).<br />
<br />
==== instructions ====<br />
<br />
Documents the instructions required to complete the project.<br />
<br />
* The element is identified by the class name <code>instructions</code>.<br />
* A projecta {{may}} include a <code>instructions</code> element. <br />
* The field {{may}} include valid HTML markup e.g. paragraphs or a list of steps.<br />
<br />
==== duration ====<br />
<br />
The time it takes to complete the project described by the projecta. Multiple duration fields can be used to denote time taken per instruction.<br />
* The element is identified by the class name <code>duration</code>.<br />
* A projecta {{may}} include one or more <code>duration</code>s.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
<pre><nowiki><br />
<div class="projecta"><br />
<h3 class="fn">Germinating Seeds</h3><br />
<p class="summary"><br />
How to germinate seeds in potting mix.<br /><br />
</p><br />
<p class="vcard fn">Derek Lewis</p><br />
<p>Published <abbr class="published" title="2009-03-28T09:30-11:00">28. Mar 2009</abbr></p><br />
<img src="/img/seed.png" class="photo" width="100" height="100" alt="Seed"/><br />
<h4>Requirements</h4><br />
<ul class="requirement"><br />
<li>Container(s) (With drain holes)</li><br />
<li>Seed(s)</li><br />
<li>Potting Mix</li><br />
<li>Fresh Water</li><br />
<li>A Light Source</li><br />
</ul><br />
<h4>Instructions</h4><br />
<ol class="instructions"><br />
<li>Loosen and dampen the potting mix.</li><br />
<li>Fill 2/3 of each container(s) with potting mix.</li><br />
<li>Put seed(s) in container with potting mix.</li><br />
<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li><br />
<li>Place container under light source.</li><br />
</ol><br />
</div><br />
</nowiki></pre><br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
<br />
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]].<br />
<br />
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]].<br />
<br />
<pre><nowiki><div class="vcard vproject"><br />
<h3 class="fn org">United Nations Giraffism Project</h3><br />
<p class="goal">To cure the people of the world of giraffism,<br />
a terrible disease that gives people long necks,<br />
by <span class="due">2018</span>.</p><br />
<p>Visit our <a href="http://giraffism.example.net/"<br />
class="url">website</a> for more details.</p><br />
</div></nowiki></pre><br />
<br />
====Digestion====<br />
The evolution of hRecipe involves the following:<br />
<br />
Remove "Ingredient"<br /><br />
Remove "Yield"<br /><br />
Remove "Nutrition"<br /><br />
<br />
Add "Requirement"<br />
<br />
As simple as possible.<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=User:Crojecta&diff=38258User:Crojecta2009-03-29T05:24:17Z<p>Crojecta: New page: <entry-title>Derek Lewis (crojecta)</entry-title> == About me == <div class="vcard" id="derek"> <span class="fn">Derek Lewis</span> &lt;<span class="url">http://crojecta.com</span>&gt;,<...</p>
<hr />
<div><entry-title>Derek Lewis (crojecta)</entry-title><br />
<br />
== About me ==<br />
<br />
<div class="vcard" id="derek"><br />
<span class="fn">Derek Lewis</span><br />
&lt;<span class="url">http://crojecta.com</span>&gt;,<br /><br />
<span class="adr"><span class="locality">Miami</span>, <span class="country-name">United States</span>.</span><br />
</div><br />
<br />
== Current Interests ==<br />
<br />
* [[project]] — The Project Microformat</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38257project-brainstorming2009-03-29T04:08:18Z<p>Crojecta: /* Format */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following elements:<br />
<br />
* '''projecta'''<br />
** '''''fn'''''. required. text. the formatted name of the project. re-used from [[hCard]].<br />
** '''''summary'''''. optional. text. re-used from [[hCalendar]].<br />
** '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]].<br />
** ''published''. optional. re-used from [[hAtom]]. [experimental]<br />
** ''tag''. optional. 1 or more. re-used from [[rel-tag]]. [experimental]<br />
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [experimental]<br />
** ''requirement''. optional. text with optional valid (x)HTML markup.<br />
** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].<br />
** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
==== fn ====<br />
<br />
The title of a single project. The formatted name of what the projecta documents.<br />
<br />
* The element is identified by class name <code>fn</code>.<br />
* A projecta {{must}} include a <code> fn </code>.<br />
* The element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== summary ====<br />
<br />
The summary provides a short introduction to or an accompanying statement about the project.<br />
<br />
* The element is identified by the class name <code>summary</code>.<br />
* A projecta {{may}} include a <code>summary</code>.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==== author ====<br />
<br />
The person who authored the project.<br />
<br />
* The element is identified by class name <code>author</code>.<br />
* A projecta {{may}} include one or more <code>author</code> elements.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== published ====<br />
<br />
The date the project was published.<br />
<br />
* The element is identified by the class name <code>published</code>.<br />
* A projecta {{may}} include a <code>published</code> date.<br />
* The element {{must}} follow the conventions outlined in [[hAtom]].<br />
* The [[datetime-design-pattern]] {{should}} be used to encode the published datetime.<br />
* The element is considered ''experimental'' and may be removed from the final specification.<br />
<br />
==== tag ====<br />
<br />
A keyword indicating a subject or an important aspect of the project like it's main requirement, type of project etc.<br />
<br />
* The element is identified by class name <code>tag</code>.<br />
* A projecta {{may}} include one or more <code>tag</code> elements.<br />
* The element {{must}} follow the conventions outlined in [[rel-tag]].<br />
<br />
==== photo ====<br />
<br />
Accompanying image.<br />
<br />
* The element is identified by the class name <code>photo</code>.<br />
* A projecta {{may}} include one or more photo elements.<br />
* The element {{should}} use an &lt;img&gt; element.<br />
* The element {{may}} use any other element that contains a URL, such as &lt;a&gt; or &lt;object&gt;, but it is not recommended.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== requirement ====<br />
<br />
Describes one or more requirements of the project.<br />
<br />
* The element is identified by the class name <code>requirement</code>.<br />
* A projecta {{must}} include one or more <code>requirement</code>s.<br />
* The field {{may}} include valid HTML markup (e.g. a list of requirements).<br />
<br />
==== instructions ====<br />
<br />
Documents the instructions required to complete the project.<br />
<br />
* The element is identified by the class name <code>instructions</code>.<br />
* A projecta {{may}} include a <code>instructions</code> element. <br />
* The field {{may}} include valid HTML markup e.g. paragraphs or a list of steps.<br />
<br />
==== duration ====<br />
<br />
The time it takes to complete the project described by the projecta. Multiple duration fields can be used to denote time taken per instruction.<br />
* The element is identified by the class name <code>duration</code>.<br />
* A projecta {{may}} include one or more <code>duration</code>s.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
<pre><nowiki><br />
<div class="projecta"><br />
<h3 class="fn">Germinating Seeds</h3><br />
<p class="summary"><br />
How to germinate seeds in potting mix.<br /><br />
</p><br />
<p class="vcard fn">Derek Lewis</p><br />
<p>Published <abbr class="published" title="2009-03-28T09:30-11:00">28. Mar 2009</abbr></p><br />
<img src="/img/seed.png" class="photo" width="100" height="100" alt="Seed"/><br />
<h4>Requirements</h4><br />
<ul class="requirement"><br />
<li>Container(s) (With drain holes)</li><br />
<li>Seed(s)</li><br />
<li>Potting Mix</li><br />
<li>Fresh Water</li><br />
<li>A Light Source</li><br />
</ul><br />
<h4>Instructions</h4><br />
<ol class="instructions"><br />
<li>Loosen and dampen the potting mix.</li><br />
<li>Fill 2/3 of each container(s) with potting mix.</li><br />
<li>Put seed(s) in container with potting mix.</li><br />
<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li><br />
<li>Place container under light source.</li><br />
</ol><br />
</div><br />
</nowiki></pre><br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
<br />
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]].<br />
<br />
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]].<br />
<br />
<pre><nowiki><div class="vcard vproject"><br />
<h3 class="fn org">United Nations Giraffism Project</h3><br />
<p class="goal">To cure the people of the world of giraffism,<br />
a terrible disease that gives people long necks,<br />
by <span class="due">2018</span>.</p><br />
<p>Visit our <a href="http://giraffism.example.net/"<br />
class="url">website</a> for more details.</p><br />
</div></nowiki></pre><br />
<br />
====Digestion====<br />
The evolution of hRecipe involves the following:<br />
<br />
Remove "Ingredient"<br /><br />
Remove "Yield"<br /><br />
Remove "Duration"<br /><br />
Remove "Nutrition"<br /><br />
<br />
Add "Requirement"<br />
<br />
As simple as possible.<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project&diff=38256project2009-03-29T04:04:13Z<p>Crojecta: /* In General */</p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
'''View each individual page as the main page omits some content.'''<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
== real world examples ==<br />
<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (summary)<br />
** how (instructions)<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator (author)<br />
** Project description<br />
** Project details<br />
*** Project Acronym<br />
*** Project Reference<br />
*** Start Date<br />
*** Duration<br />
*** Project Cost<br />
*** Contract Type<br />
*** End Date<br />
*** Project Status<br />
*** Project Funding<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (instructions)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (instructions)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
=== How to fix a CD player ===<br />
* http://www.kuro5hin.org/story/2004/3/24/45212/6874<br />
<br />
** title<br />
** by (author)<br />
** date and time submitted<br />
** tags<br />
** description<br />
** summary<br />
** instructions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
== Format ==<br />
=== In General ===<br />
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]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following elements:<br />
<br />
* '''projecta'''<br />
** '''''fn'''''. required. text. the formatted name of the project. re-used from [[hCard]].<br />
** '''''summary'''''. optional. text. re-used from [[hCalendar]].<br />
** '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]].<br />
** ''published''. optional. re-used from [[hAtom]]. [experimental]<br />
** ''tag''. optional. 1 or more. re-used from [[rel-tag]]. [experimental]<br />
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [experimental]<br />
** ''requirement''. optional. text with optional valid (x)HTML markup.<br />
** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].<br />
** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
==== fn ====<br />
<br />
The title of a single project. The formatted name of what the projecta documents.<br />
<br />
* The element is identified by class name <code>fn</code>.<br />
* A projecta {{must}} include a <code> fn </code>.<br />
* The element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== summary ====<br />
<br />
The summary provides a short introduction to or an accompanying statement about the project.<br />
<br />
* The element is identified by the class name <code>summary</code>.<br />
* A projecta {{may}} include a <code>summary</code>.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==== author ====<br />
<br />
The person who authored the project.<br />
<br />
* The element is identified by class name <code>author</code>.<br />
* A projecta {{may}} include one or more <code>author</code> elements.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== published ====<br />
<br />
The date the project was published.<br />
<br />
* The element is identified by the class name <code>published</code>.<br />
* A projecta {{may}} include a <code>published</code> date.<br />
* The element {{must}} follow the conventions outlined in [[hAtom]].<br />
* The [[datetime-design-pattern]] {{should}} be used to encode the published datetime.<br />
* The element is considered ''experimental'' and may be removed from the final specification.<br />
<br />
==== tag ====<br />
<br />
A keyword indicating a subject or an important aspect of the project like it's main requirement, type of project etc.<br />
<br />
* The element is identified by class name <code>tag</code>.<br />
* A projecta {{may}} include one or more <code>tag</code> elements.<br />
* The element {{must}} follow the conventions outlined in [[rel-tag]].<br />
<br />
==== photo ====<br />
<br />
Accompanying image.<br />
<br />
* The element is identified by the class name <code>photo</code>.<br />
* A projecta {{may}} include one or more photo elements.<br />
* The element {{should}} use an &lt;img&gt; element.<br />
* The element {{may}} use any other element that contains a URL, such as &lt;a&gt; or &lt;object&gt;, but it is not recommended.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== requirement ====<br />
<br />
Describes one or more requirements of the project.<br />
<br />
* The element is identified by the class name <code>requirement</code>.<br />
* A projecta {{must}} include one or more <code>requirement</code>s.<br />
* The field {{may}} include valid HTML markup (e.g. a list of requirements).<br />
<br />
==== instructions ====<br />
<br />
Documents the instructions required to complete the project.<br />
<br />
* The element is identified by the class name <code>instructions</code>.<br />
* A projecta {{may}} include a <code>instructions</code> element. <br />
* The field {{may}} include valid HTML markup e.g. paragraphs or a list of steps.<br />
<br />
==== duration ====<br />
<br />
The time it takes to complete the project described by the projecta. Multiple duration fields can be used to denote time taken per instruction.<br />
* The element is identified by the class name <code>duration</code>.<br />
* A projecta {{may}} include one or more <code>duration</code>s.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
<pre><nowiki><br />
<div class="projecta"><br />
<h3 class="fn">Germinating Seeds</h3><br />
<p class="summary"><br />
How to germinate seeds in potting mix.<br /><br />
</p><br />
<p class="vcard fn">Derek Lewis</p><br />
<p>Published <abbr class="published" title="2009-03-28T09:30-11:00">28. Mar 2009</abbr></p><br />
<img src="/img/seed.png" class="photo" width="100" height="100" alt="Seed"/><br />
<h4>Requirements</h4><br />
<ul class="requirement"><br />
<li>Container(s) (With drain holes)</li><br />
<li>Seed(s)</li><br />
<li>Potting Mix</li><br />
<li>Fresh Water</li><br />
<li>A Light Source</li><br />
</ul><br />
<h4>Instructions</h4><br />
<ol class="instructions"><br />
<li>Loosen and dampen the potting mix.</li><br />
<li>Fill 2/3 of each container(s) with potting mix.</li><br />
<li>Put seed(s) in container with potting mix.</li><br />
<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li><br />
<li>Place container under light source.</li><br />
</ol><br />
</div><br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Notes ==<br />
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 ?<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Crojectahttps://microformats.org/wiki/index.php?title=project&diff=38255project2009-03-29T03:50:29Z<p>Crojecta: /* brainstorming */</p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
'''View each individual page as the main page omits some content.'''<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
== real world examples ==<br />
<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (summary)<br />
** how (instructions)<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator (author)<br />
** Project description<br />
** Project details<br />
*** Project Acronym<br />
*** Project Reference<br />
*** Start Date<br />
*** Duration<br />
*** Project Cost<br />
*** Contract Type<br />
*** End Date<br />
*** Project Status<br />
*** Project Funding<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (instructions)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (instructions)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
=== How to fix a CD player ===<br />
* http://www.kuro5hin.org/story/2004/3/24/45212/6874<br />
<br />
** title<br />
** by (author)<br />
** date and time submitted<br />
** tags<br />
** description<br />
** summary<br />
** instructions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
== Format ==<br />
=== In General ===<br />
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]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following elements:<br />
<br />
* '''projecta'''<br />
** '''''fn'''''. required. text. the formatted name of the project. re-used from [[hCard]].<br />
** '''''summary'''''. optional. text. re-used from [[hCalendar]].<br />
** '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]].<br />
** ''published''. optional. re-used from [[hAtom]]. [experimental]<br />
** ''tag''. optional. 1 or more. re-used from [[rel-tag]]. [experimental]<br />
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [experimental]<br />
** ''requirement''. optional. text with optional valid (x)HTML markup.<br />
** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].<br />
** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
==== fn ====<br />
<br />
The title of a single project. The formatted name of what the projecta documents.<br />
<br />
* The element is identified by class name <code>fn</code>.<br />
* A projecta {{must}} include a <code> fn </code>.<br />
* The element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== summary ====<br />
<br />
The summary provides a short introduction to or an accompanying statement about the project.<br />
<br />
* The element is identified by the class name <code>summary</code>.<br />
* A projecta {{may}} include a <code>summary</code>.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==== author ====<br />
<br />
The person who authored the project.<br />
<br />
* The element is identified by class name <code>author</code>.<br />
* A projecta {{may}} include one or more <code>author</code> elements.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== published ====<br />
<br />
The date the project was published.<br />
<br />
* The element is identified by the class name <code>published</code>.<br />
* A projecta {{may}} include a <code>published</code> date.<br />
* The element {{must}} follow the conventions outlined in [[hAtom]].<br />
* The [[datetime-design-pattern]] {{should}} be used to encode the published datetime.<br />
* The element is considered ''experimental'' and may be removed from the final specification.<br />
<br />
==== tag ====<br />
<br />
A keyword indicating a subject or an important aspect of the project like it's main requirement, type of project etc.<br />
<br />
* The element is identified by class name <code>tag</code>.<br />
* A projecta {{may}} include one or more <code>tag</code> elements.<br />
* The element {{must}} follow the conventions outlined in [[rel-tag]].<br />
<br />
==== photo ====<br />
<br />
Accompanying image.<br />
<br />
* The element is identified by the class name <code>photo</code>.<br />
* A projecta {{may}} include one or more photo elements.<br />
* The element {{should}} use an &lt;img&gt; element.<br />
* The element {{may}} use any other element that contains a URL, such as &lt;a&gt; or &lt;object&gt;, but it is not recommended.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== requirement ====<br />
<br />
Describes one or more requirements of the project.<br />
<br />
* The element is identified by the class name <code>requirement</code>.<br />
* A projecta {{must}} include one or more <code>requirement</code>s.<br />
* The field {{may}} include valid HTML markup (e.g. a list of requirements).<br />
<br />
==== instructions ====<br />
<br />
Documents the instructions required to complete the project.<br />
<br />
* The element is identified by the class name <code>instructions</code>.<br />
* A projecta {{may}} include a <code>instructions</code> element. <br />
* The field {{may}} include valid HTML markup e.g. paragraphs or a list of steps.<br />
<br />
==== duration ====<br />
<br />
The time it takes to complete the project described by the projecta. Multiple duration fields can be used to denote time taken per instruction.<br />
* The element is identified by the class name <code>duration</code>.<br />
* A projecta {{may}} include one or more <code>duration</code>s.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
<pre><nowiki><br />
<div class="projecta"><br />
<h3 class="fn">Germinating Seeds</h3><br />
<p class="summary"><br />
How to germinate seeds in potting mix.<br /><br />
</p><br />
<p class="vcard fn">Derek Lewis</p><br />
<p>Published <abbr class="published" title="2009-03-28T09:30-11:00">28. Mar 2009</abbr></p><br />
<img src="/img/seed.png" class="photo" width="100" height="100" alt="Seed"/><br />
<h4>Requirements</h4><br />
<ul class="requirement"><br />
<li>Container(s) (With drain holes)</li><br />
<li>Seed(s)</li><br />
<li>Potting Mix</li><br />
<li>Fresh Water</li><br />
<li>A Light Source</li><br />
</ul><br />
<h4>Instructions</h4><br />
<ol class="instructions"><br />
<li>Loosen and dampen the potting mix.</li><br />
<li>Fill 2/3 of each container(s) with potting mix.</li><br />
<li>Put seed(s) in container with potting mix.</li><br />
<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li><br />
<li>Place container under light source.</li><br />
</ol><br />
</div><br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Notes ==<br />
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 ?<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38254project-brainstorming2009-03-29T03:38:57Z<p>Crojecta: /* Digestion */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following elements:<br />
<br />
* '''projecta'''<br />
** '''''fn'''''. required. text. the formatted name of the project. re-used from [[hCard]].<br />
** '''''summary'''''. optional. text. re-used from [[hCalendar]].<br />
** '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]].<br />
** ''published''. optional. re-used from [[hAtom]]. [experimental]<br />
** ''tag''. optional. 1 or more. re-used from [[rel-tag]]. [experimental]<br />
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [experimental]<br />
** ''requirement''. optional. text with optional valid (x)HTML markup.<br />
** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].<br />
** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].<br />
<br />
<pre><nowiki><br />
<div class="projecta"><br />
<h3 class="fn">Germinating Seeds</h3><br />
<p class="summary"><br />
How to germinate seeds in potting mix.<br /><br />
</p><br />
<p class="vcard fn">Derek Lewis</p><br />
<p>Published <abbr class="published" title="2009-03-28T09:30-11:00">28. Mar 2009</abbr></p><br />
<img src="/img/seed.png" class="photo" width="100" height="100" alt="Seed"/><br />
<h4>Requirements</h4><br />
<ul class="requirement"><br />
<li>Container(s) (With drain holes)</li><br />
<li>Seed(s)</li><br />
<li>Potting Mix</li><br />
<li>Fresh Water</li><br />
<li>A Light Source</li><br />
</ul><br />
<h4>Instructions</h4><br />
<ol class="instructions"><br />
<li>Loosen and dampen the potting mix.</li><br />
<li>Fill 2/3 of each container(s) with potting mix.</li><br />
<li>Put seed(s) in container with potting mix.</li><br />
<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li><br />
<li>Place container under light source.</li><br />
</ol><br />
</div><br />
</nowiki></pre><br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
==== fn ====<br />
<br />
The title of a single project. The formatted name of what the projecta documents.<br />
<br />
* The element is identified by class name <code>fn</code>.<br />
* A projecta {{must}} include a <code> fn </code>.<br />
* The element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== summary ====<br />
<br />
The summary provides a short introduction to or an accompanying statement about the project.<br />
<br />
* The element is identified by the class name <code>summary</code>.<br />
* A projecta {{may}} include a <code>summary</code>.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==== author ====<br />
<br />
The person who authored the project.<br />
<br />
* The element is identified by class name <code>author</code>.<br />
* A projecta {{may}} include one or more <code>author</code> elements.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== published ====<br />
<br />
The date the project was published.<br />
<br />
* The element is identified by the class name <code>published</code>.<br />
* A projecta {{may}} include a <code>published</code> date.<br />
* The element {{must}} follow the conventions outlined in [[hAtom]].<br />
* The [[datetime-design-pattern]] {{should}} be used to encode the published datetime.<br />
* The element is considered ''experimental'' and may be removed from the final specification.<br />
<br />
==== tag ====<br />
<br />
A keyword indicating a subject or an important aspect of the project like it's main requirement, type of project etc.<br />
<br />
* The element is identified by class name <code>tag</code>.<br />
* A projecta {{may}} include one or more <code>tag</code> elements.<br />
* The element {{must}} follow the conventions outlined in [[rel-tag]].<br />
<br />
==== photo ====<br />
<br />
Accompanying image.<br />
<br />
* The element is identified by the class name <code>photo</code>.<br />
* A projecta {{may}} include one or more photo elements.<br />
* The element {{should}} use an &lt;img&gt; element.<br />
* The element {{may}} use any other element that contains a URL, such as &lt;a&gt; or &lt;object&gt;, but it is not recommended.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== requirement ====<br />
<br />
Describes one or more requirements of the project.<br />
<br />
* The element is identified by the class name <code>requirement</code>.<br />
* A projecta {{must}} include one or more <code>requirement</code>s.<br />
* The field {{may}} include valid HTML markup (e.g. a list of requirements).<br />
<br />
==== instructions ====<br />
<br />
Documents the instructions required to complete the project.<br />
<br />
* The element is identified by the class name <code>instructions</code>.<br />
* A projecta {{may}} include a <code>instructions</code> element. <br />
* The field {{may}} include valid HTML markup e.g. paragraphs or a list of steps.<br />
<br />
==== duration ====<br />
<br />
The time it takes to complete the project described by the projecta. Multiple duration fields can be used to denote time taken per instruction.<br />
* The element is identified by the class name <code>duration</code>.<br />
* A projecta {{may}} include one or more <code>duration</code>s.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
<br />
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]].<br />
<br />
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]].<br />
<br />
<pre><nowiki><div class="vcard vproject"><br />
<h3 class="fn org">United Nations Giraffism Project</h3><br />
<p class="goal">To cure the people of the world of giraffism,<br />
a terrible disease that gives people long necks,<br />
by <span class="due">2018</span>.</p><br />
<p>Visit our <a href="http://giraffism.example.net/"<br />
class="url">website</a> for more details.</p><br />
</div></nowiki></pre><br />
<br />
====Digestion====<br />
The evolution of hRecipe involves the following:<br />
<br />
Remove "Ingredient"<br /><br />
Remove "Yield"<br /><br />
Remove "Duration"<br /><br />
Remove "Nutrition"<br /><br />
<br />
Add "Requirement"<br />
<br />
As simple as possible.<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38253project-brainstorming2009-03-29T03:38:06Z<p>Crojecta: /* Format */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following elements:<br />
<br />
* '''projecta'''<br />
** '''''fn'''''. required. text. the formatted name of the project. re-used from [[hCard]].<br />
** '''''summary'''''. optional. text. re-used from [[hCalendar]].<br />
** '''''author'''''. optional. 1 or more. re-used from [[hAtom]] using [[hCard]].<br />
** ''published''. optional. re-used from [[hAtom]]. [experimental]<br />
** ''tag''. optional. 1 or more. re-used from [[rel-tag]]. [experimental]<br />
** ''photo''. optional. 1 or more. using any element containing a URL, such as IMG. re-used from [[hCard]]. [experimental]<br />
** ''requirement''. optional. text with optional valid (x)HTML markup.<br />
** ''instructions''. optional. text with optional valid (x)HTML markup. re-used from [[hRecipe]].<br />
** '''''duration'''''. optional. 1 or more. text (see [[ISO-31-1]] duration brainstorming). re-used from [[hCalendar]].<br />
<br />
<pre><nowiki><br />
<div class="projecta"><br />
<h3 class="fn">Germinating Seeds</h3><br />
<p class="summary"><br />
How to germinate seeds in potting mix.<br /><br />
</p><br />
<p class="vcard fn">Derek Lewis</p><br />
<p>Published <abbr class="published" title="2009-03-28T09:30-11:00">28. Mar 2009</abbr></p><br />
<img src="/img/seed.png" class="photo" width="100" height="100" alt="Seed"/><br />
<h4>Requirements</h4><br />
<ul class="requirement"><br />
<li>Container(s) (With drain holes)</li><br />
<li>Seed(s)</li><br />
<li>Potting Mix</li><br />
<li>Fresh Water</li><br />
<li>A Light Source</li><br />
</ul><br />
<h4>Instructions</h4><br />
<ol class="instructions"><br />
<li>Loosen and dampen the potting mix.</li><br />
<li>Fill 2/3 of each container(s) with potting mix.</li><br />
<li>Put seed(s) in container with potting mix.</li><br />
<li>Sprinkle a few drops of water over of the seed(s). (Remember to repeat this once potting mix becomes dry.)</li><br />
<li>Place container under light source.</li><br />
</ol><br />
</div><br />
</nowiki></pre><br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
==== fn ====<br />
<br />
The title of a single project. The formatted name of what the projecta documents.<br />
<br />
* The element is identified by class name <code>fn</code>.<br />
* A projecta {{must}} include a <code> fn </code>.<br />
* The element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== summary ====<br />
<br />
The summary provides a short introduction to or an accompanying statement about the project.<br />
<br />
* The element is identified by the class name <code>summary</code>.<br />
* A projecta {{may}} include a <code>summary</code>.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==== author ====<br />
<br />
The person who authored the project.<br />
<br />
* The element is identified by class name <code>author</code>.<br />
* A projecta {{may}} include one or more <code>author</code> elements.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== published ====<br />
<br />
The date the project was published.<br />
<br />
* The element is identified by the class name <code>published</code>.<br />
* A projecta {{may}} include a <code>published</code> date.<br />
* The element {{must}} follow the conventions outlined in [[hAtom]].<br />
* The [[datetime-design-pattern]] {{should}} be used to encode the published datetime.<br />
* The element is considered ''experimental'' and may be removed from the final specification.<br />
<br />
==== tag ====<br />
<br />
A keyword indicating a subject or an important aspect of the project like it's main requirement, type of project etc.<br />
<br />
* The element is identified by class name <code>tag</code>.<br />
* A projecta {{may}} include one or more <code>tag</code> elements.<br />
* The element {{must}} follow the conventions outlined in [[rel-tag]].<br />
<br />
==== photo ====<br />
<br />
Accompanying image.<br />
<br />
* The element is identified by the class name <code>photo</code>.<br />
* A projecta {{may}} include one or more photo elements.<br />
* The element {{should}} use an &lt;img&gt; element.<br />
* The element {{may}} use any other element that contains a URL, such as &lt;a&gt; or &lt;object&gt;, but it is not recommended.<br />
* The contents of the element {{must}} follow the conventions outlined in [[hCard]].<br />
<br />
==== requirement ====<br />
<br />
Describes one or more requirements of the project.<br />
<br />
* The element is identified by the class name <code>requirement</code>.<br />
* A projecta {{must}} include one or more <code>requirement</code>s.<br />
* The field {{may}} include valid HTML markup (e.g. a list of requirements).<br />
<br />
==== instructions ====<br />
<br />
Documents the instructions required to complete the project.<br />
<br />
* The element is identified by the class name <code>instructions</code>.<br />
* A projecta {{may}} include a <code>instructions</code> element. <br />
* The field {{may}} include valid HTML markup e.g. paragraphs or a list of steps.<br />
<br />
==== duration ====<br />
<br />
The time it takes to complete the project described by the projecta. Multiple duration fields can be used to denote time taken per instruction.<br />
* The element is identified by the class name <code>duration</code>.<br />
* A projecta {{may}} include one or more <code>duration</code>s.<br />
* The element {{must}} follow the conventions outlined in [[hCalendar]].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
<br />
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]].<br />
<br />
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]].<br />
<br />
<pre><nowiki><div class="vcard vproject"><br />
<h3 class="fn org">United Nations Giraffism Project</h3><br />
<p class="goal">To cure the people of the world of giraffism,<br />
a terrible disease that gives people long necks,<br />
by <span class="due">2018</span>.</p><br />
<p>Visit our <a href="http://giraffism.example.net/"<br />
class="url">website</a> for more details.</p><br />
</div></nowiki></pre><br />
<br />
====Digestion====<br />
Added field named "type" (re-used from [[hreview|hReview]]) with options "abstract" and "practical".<br /><br />
Added field named "goals".<br /><br />
Added field named "instructions" (re-used from [[hrecipe|hRecipe]]).<br /><br />
Added field named "accomplishments".<br /><br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38228project-brainstorming2009-03-25T05:21:14Z<p>Crojecta: /* Field details */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. serves as the title for the project.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as the title for the project.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]] microformats: <code>version, summary, url, photo, description, instructions, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
Toby, what do you suggest?<br />
<br />
====Digestion====<br />
Added field named "type" (re-used from [[hreview|hReview]]) with options "abstract" and "practical".<br /><br />
Added field named "goals".<br /><br />
Added field named "instructions" (re-used from [[hrecipe|hRecipe]]).<br /><br />
Added field named "accomplishments".<br /><br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38227project-brainstorming2009-03-25T05:11:05Z<p>Crojecta: /* Field details */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. serves as the title for the project.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as the title for the project.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]] microformats: <code>version, summary, url, photo, description, instructions, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
Toby, what do you suggest?<br />
<br />
====Digestion====<br />
Added field named "type" (re-used from [[hreview|hReview]]) with options "abstract" and "practical".<br /><br />
Added field named "goals".<br /><br />
Added field named "instructions" (re-used from [[hrecipe|hRecipe]]).<br /><br />
Added field named "accomplishments".<br /><br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project&diff=38226project2009-03-25T05:10:29Z<p>Crojecta: /* brainstorming */</p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
'''View each individual page as the main page omits some content.'''<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
== real world examples ==<br />
<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (summary)<br />
** how (instructions)<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator (author)<br />
** Project description<br />
** Project details<br />
*** Project Acronym<br />
*** Project Reference<br />
*** Start Date<br />
*** Duration<br />
*** Project Cost<br />
*** Contract Type<br />
*** End Date<br />
*** Project Status<br />
*** Project Funding<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (instructions)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (instructions)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
=== How to fix a CD player ===<br />
* http://www.kuro5hin.org/story/2004/3/24/45212/6874<br />
<br />
** title<br />
** by (author)<br />
** date and time submitted<br />
** tags<br />
** description<br />
** summary<br />
** instructions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. serves as the title for the project.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as the title for the project..<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
<br />
=== markup sample ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
<pre><nowiki><br />
<div class="project" id="urn:uuid:233f6e5d-2ad2-4b7e-a3fe-1b90ef2fef57"><br />
<img class="logo" src="..." /><br />
<span class="name">Microformats</span><br />
<span class="desc">An initiative to extract common patterns from POSH</span><br />
<br />
<h1>Some informations</h1><br />
<a href="http://microformats.org/" rel="home">The primary home page of the project.</a><br />
<a href="..." rel="source">Here you can find its source code.</a><br />
<a href="..." rel="release">Get the releases.</a><br />
<-- Every hCard is looked as a participant [including venues? ] --><br />
<br />
<h1>Project's tags</h1><br />
<ul><br />
<li class="tag">open</li><br />
<li class="tag">format</li><br />
<li class="tag">standard</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
=== CSS selection specification ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
A good way to describe the structure, is to look at it trough the view of CSS selectors. Designers sometimes need wrappers, which makes it hard to keep a strict structure. If you used jQuery, you know what I mean.<br />
<br />
<pre><nowiki><br />
.project[@id] : is an UUID (see http://ietf.org/rfc/rfc4122.txt).<br />
A unique identifier for the project.<br />
It is used to resolve name clashes.<br />
.project .name : the content describes the project name.<br />
Should not appear more that one time per project.<br />
.project IMG.logo : the src is a link to the logo.<br />
Can have different sizes with by adding "low | mid | high" classes.<br />
.project A[@rel=home] : a project's home page<br />
.project A[@rel=source] : a link to the project's source.<br />
If it is a scm, it is generally solved by using different uris.<br />
Like git:// or bzr:// or http+git://<br />
.project A[@rel=release] : the linked pages contains file releases.<br />
This page can contain hRelease microformat.<br />
.project A[@rel=...] : many extensions can be imagined, like :<br />
"blog | wiki | parent-project | ..."<br />
.project .tag : the content describes a project tag. You can<br />
have as many as you wish.<br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Notes ==<br />
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 ?<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38225project-brainstorming2009-03-25T05:09:42Z<p>Crojecta: /* Schema */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. serves as the title for the project.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]] microformats: <code>version, summary, url, photo, description, instructions, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
Toby, what do you suggest?<br />
<br />
====Digestion====<br />
Added field named "type" (re-used from [[hreview|hReview]]) with options "abstract" and "practical".<br /><br />
Added field named "goals".<br /><br />
Added field named "instructions" (re-used from [[hrecipe|hRecipe]]).<br /><br />
Added field named "accomplishments".<br /><br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project&diff=38223project2009-03-25T01:15:03Z<p>Crojecta: /* 43things */</p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
'''View each individual page as the main page omits some content.'''<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
== real world examples ==<br />
<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (summary)<br />
** how (instructions)<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator (author)<br />
** Project description<br />
** Project details<br />
*** Project Acronym<br />
*** Project Reference<br />
*** Start Date<br />
*** Duration<br />
*** Project Cost<br />
*** Contract Type<br />
*** End Date<br />
*** Project Status<br />
*** Project Funding<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (instructions)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (instructions)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
=== How to fix a CD player ===<br />
* http://www.kuro5hin.org/story/2004/3/24/45212/6874<br />
<br />
** title<br />
** by (author)<br />
** date and time submitted<br />
** tags<br />
** description<br />
** summary<br />
** instructions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. one sentence.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
<br />
=== markup sample ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
<pre><nowiki><br />
<div class="project" id="urn:uuid:233f6e5d-2ad2-4b7e-a3fe-1b90ef2fef57"><br />
<img class="logo" src="..." /><br />
<span class="name">Microformats</span><br />
<span class="desc">An initiative to extract common patterns from POSH</span><br />
<br />
<h1>Some informations</h1><br />
<a href="http://microformats.org/" rel="home">The primary home page of the project.</a><br />
<a href="..." rel="source">Here you can find its source code.</a><br />
<a href="..." rel="release">Get the releases.</a><br />
<-- Every hCard is looked as a participant [including venues? ] --><br />
<br />
<h1>Project's tags</h1><br />
<ul><br />
<li class="tag">open</li><br />
<li class="tag">format</li><br />
<li class="tag">standard</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
=== CSS selection specification ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
A good way to describe the structure, is to look at it trough the view of CSS selectors. Designers sometimes need wrappers, which makes it hard to keep a strict structure. If you used jQuery, you know what I mean.<br />
<br />
<pre><nowiki><br />
.project[@id] : is an UUID (see http://ietf.org/rfc/rfc4122.txt).<br />
A unique identifier for the project.<br />
It is used to resolve name clashes.<br />
.project .name : the content describes the project name.<br />
Should not appear more that one time per project.<br />
.project IMG.logo : the src is a link to the logo.<br />
Can have different sizes with by adding "low | mid | high" classes.<br />
.project A[@rel=home] : a project's home page<br />
.project A[@rel=source] : a link to the project's source.<br />
If it is a scm, it is generally solved by using different uris.<br />
Like git:// or bzr:// or http+git://<br />
.project A[@rel=release] : the linked pages contains file releases.<br />
This page can contain hRelease microformat.<br />
.project A[@rel=...] : many extensions can be imagined, like :<br />
"blog | wiki | parent-project | ..."<br />
.project .tag : the content describes a project tag. You can<br />
have as many as you wish.<br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Notes ==<br />
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 ?<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38222project-brainstorming2009-03-25T01:12:40Z<p>Crojecta: /* Digestion */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. one sentence.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]] microformats: <code>version, summary, url, photo, description, instructions, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
Toby, what do you suggest?<br />
<br />
====Digestion====<br />
Added field named "type" (re-used from [[hreview|hReview]]) with options "abstract" and "practical".<br /><br />
Added field named "goals".<br /><br />
Added field named "instructions" (re-used from [[hrecipe|hRecipe]]).<br /><br />
Added field named "accomplishments".<br /><br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project&diff=38221project2009-03-25T01:10:50Z<p>Crojecta: /* real world examples */</p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
'''View each individual page as the main page omits some content.'''<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
== real world examples ==<br />
<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (summary)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator (author)<br />
** Project description<br />
** Project details<br />
*** Project Acronym<br />
*** Project Reference<br />
*** Start Date<br />
*** Duration<br />
*** Project Cost<br />
*** Contract Type<br />
*** End Date<br />
*** Project Status<br />
*** Project Funding<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (instructions)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (instructions)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
=== How to fix a CD player ===<br />
* http://www.kuro5hin.org/story/2004/3/24/45212/6874<br />
<br />
** title<br />
** by (author)<br />
** date and time submitted<br />
** tags<br />
** description<br />
** summary<br />
** instructions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. one sentence.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
<br />
=== markup sample ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
<pre><nowiki><br />
<div class="project" id="urn:uuid:233f6e5d-2ad2-4b7e-a3fe-1b90ef2fef57"><br />
<img class="logo" src="..." /><br />
<span class="name">Microformats</span><br />
<span class="desc">An initiative to extract common patterns from POSH</span><br />
<br />
<h1>Some informations</h1><br />
<a href="http://microformats.org/" rel="home">The primary home page of the project.</a><br />
<a href="..." rel="source">Here you can find its source code.</a><br />
<a href="..." rel="release">Get the releases.</a><br />
<-- Every hCard is looked as a participant [including venues? ] --><br />
<br />
<h1>Project's tags</h1><br />
<ul><br />
<li class="tag">open</li><br />
<li class="tag">format</li><br />
<li class="tag">standard</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
=== CSS selection specification ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
A good way to describe the structure, is to look at it trough the view of CSS selectors. Designers sometimes need wrappers, which makes it hard to keep a strict structure. If you used jQuery, you know what I mean.<br />
<br />
<pre><nowiki><br />
.project[@id] : is an UUID (see http://ietf.org/rfc/rfc4122.txt).<br />
A unique identifier for the project.<br />
It is used to resolve name clashes.<br />
.project .name : the content describes the project name.<br />
Should not appear more that one time per project.<br />
.project IMG.logo : the src is a link to the logo.<br />
Can have different sizes with by adding "low | mid | high" classes.<br />
.project A[@rel=home] : a project's home page<br />
.project A[@rel=source] : a link to the project's source.<br />
If it is a scm, it is generally solved by using different uris.<br />
Like git:// or bzr:// or http+git://<br />
.project A[@rel=release] : the linked pages contains file releases.<br />
This page can contain hRelease microformat.<br />
.project A[@rel=...] : many extensions can be imagined, like :<br />
"blog | wiki | parent-project | ..."<br />
.project .tag : the content describes a project tag. You can<br />
have as many as you wish.<br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Notes ==<br />
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 ?<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38220project-examples2009-03-25T00:59:45Z<p>Crojecta: /* Centralized Implementations */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (summary)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator (author)<br />
** Project description<br />
** Project details<br />
*** Project Acronym<br />
*** Project Reference<br />
*** Start Date<br />
*** Duration<br />
*** Project Cost<br />
*** Contract Type<br />
*** End Date<br />
*** Project Status<br />
*** Project Funding<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (instructions)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (instructions)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
=== How to fix a CD player ===<br />
* http://www.kuro5hin.org/story/2004/3/24/45212/6874<br />
<br />
** title<br />
** by (author)<br />
** date and time submitted<br />
** tags<br />
** description<br />
** summary<br />
** instructions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38219project-brainstorming2009-03-25T00:47:41Z<p>Crojecta: /* Digestion */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. one sentence.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]] microformats: <code>version, summary, url, photo, description, instructions, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
Toby, what do you suggest?<br />
<br />
====Digestion====<br />
Added field named "type" (re-used from [[hreview|hReview]]) with options "abstract" and "practical".<br />
<br />
Added field named "goals".<br />
<br />
Added field named "instructions" (re-used from [[hrecipe|hRecipe]].<br />
<br />
Added field named "accomplishments".<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project&diff=38218project2009-03-25T00:46:32Z<p>Crojecta: /* brainstorming */</p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
'''View each individual page as the main page omits some content.'''<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
== real world examples ==<br />
<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things.com ===<br />
* http://43things.com<br />
How I did a project<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. one sentence.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
<br />
=== markup sample ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
<pre><nowiki><br />
<div class="project" id="urn:uuid:233f6e5d-2ad2-4b7e-a3fe-1b90ef2fef57"><br />
<img class="logo" src="..." /><br />
<span class="name">Microformats</span><br />
<span class="desc">An initiative to extract common patterns from POSH</span><br />
<br />
<h1>Some informations</h1><br />
<a href="http://microformats.org/" rel="home">The primary home page of the project.</a><br />
<a href="..." rel="source">Here you can find its source code.</a><br />
<a href="..." rel="release">Get the releases.</a><br />
<-- Every hCard is looked as a participant [including venues? ] --><br />
<br />
<h1>Project's tags</h1><br />
<ul><br />
<li class="tag">open</li><br />
<li class="tag">format</li><br />
<li class="tag">standard</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
=== CSS selection specification ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
A good way to describe the structure, is to look at it trough the view of CSS selectors. Designers sometimes need wrappers, which makes it hard to keep a strict structure. If you used jQuery, you know what I mean.<br />
<br />
<pre><nowiki><br />
.project[@id] : is an UUID (see http://ietf.org/rfc/rfc4122.txt).<br />
A unique identifier for the project.<br />
It is used to resolve name clashes.<br />
.project .name : the content describes the project name.<br />
Should not appear more that one time per project.<br />
.project IMG.logo : the src is a link to the logo.<br />
Can have different sizes with by adding "low | mid | high" classes.<br />
.project A[@rel=home] : a project's home page<br />
.project A[@rel=source] : a link to the project's source.<br />
If it is a scm, it is generally solved by using different uris.<br />
Like git:// or bzr:// or http+git://<br />
.project A[@rel=release] : the linked pages contains file releases.<br />
This page can contain hRelease microformat.<br />
.project A[@rel=...] : many extensions can be imagined, like :<br />
"blog | wiki | parent-project | ..."<br />
.project .tag : the content describes a project tag. You can<br />
have as many as you wish.<br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Notes ==<br />
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 ?<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38217project-examples2009-03-24T23:34:12Z<p>Crojecta: /* RX-8 iPod Install */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (summary)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator (author)<br />
** Project description<br />
** Project details<br />
*** Project Acronym<br />
*** Project Reference<br />
*** Start Date<br />
*** Duration<br />
*** Project Cost<br />
*** Contract Type<br />
*** End Date<br />
*** Project Status<br />
*** Project Funding<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (instructions)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (instructions)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38216project-examples2009-03-24T23:33:48Z<p>Crojecta: /* Poncho */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (summary)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator (author)<br />
** Project description<br />
** Project details<br />
*** Project Acronym<br />
*** Project Reference<br />
*** Start Date<br />
*** Duration<br />
*** Project Cost<br />
*** Contract Type<br />
*** End Date<br />
*** Project Status<br />
*** Project Funding<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (instructions)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=projecta&diff=38215projecta2009-03-24T23:32:27Z<p>Crojecta: </p>
<hr />
<div>=Projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], and [[hreview|hReview]] standards.<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. one sentence.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]] microformats: <code>version, summary, url, photo, description, instructions, 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].</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38214project-brainstorming2009-03-24T23:28:21Z<p>Crojecta: /* Field details */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. one sentence.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]] microformats: <code>version, summary, url, photo, description, instructions, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
Toby, what do you suggest?<br />
<br />
====Digestion====<br />
Added field named "type" (re-used from [[hreview|hReview]]) with options "abstract" and "practical".<br />
Added field named "goals".<br />
Added field named "instructions" (re-used from [[hrecipe|hRecipe]].<br />
Added field named "accomplishments".<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38213project-brainstorming2009-03-24T23:26:54Z<p>Crojecta: /* Format Development */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. one sentence.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''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 "steps" field completed.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]] microformats: <code>version, summary, url, photo, description, instructions, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
Toby, what do you suggest?<br />
<br />
====Digestion====<br />
Added field named "type" (re-used from [[hreview|hReview]]) with options "abstract" and "practical".<br />
Added field named "goals".<br />
Added field named "instructions" (re-used from [[hrecipe|hRecipe]].<br />
Added field named "accomplishments".<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38212project-brainstorming2009-03-24T23:19:02Z<p>Crojecta: /* Format */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''version'''. optional. text.<br />
** '''summary'''. optional. text. one sentence.<br />
** '''type'''. optional. abstract | practical.<br />
** '''project''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''author'''. optional. '''[[hcard|hCard]]'''.<br />
** '''description'''. optional. text with optional valid HTML markup.<br />
** '''goals'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''instructions'''. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** '''accomplishments'''. optional. text with valid HTML '''<code>ul</code>''' ('''<code>li</code>''') elements.<br />
** '''requirements'''. optional. text {{may}} include valid HTML markup e.g. paragraphs or a list. <br />
** '''tags'''. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** '''permalink'''. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''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 "steps" field completed.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''goals''':: This optional field documents the project's goals.<br />
<br />
'''instructions''':: This optional field documents the instructions required to complete the project. Re-used from [[hrecipe|hRecipe]].<br />
<br />
'''accomplishments''':: This optional field documents the project's accomplishments.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], and [[hrecipe|hRecipe]] microformats: <code>version, summary, url, photo, description, instructions, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
What do you suggest?<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38207project-brainstorming2009-03-24T21:43:30Z<p>Crojecta: /* Schema */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]] and [[hcalendar|hCalendar]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''<code>version</code>'''. optional. text.<br />
** '''<code>title</code>'''. required. text. the name of the project.<br />
** '''<code>summary</code>'''. optional. text. one sentence.<br />
** '''<code>project</code>''' info. required. ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''.<br />
** '''<code>description</code>'''. optional. text with optional valid HTML markup.<br />
** requirements. optional. text with optional '''<code>url</code>''' to products or other projects.<br />
** steps. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''title''':: This required field {{must}} have at a minimum the name of the project.<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''project info''':: This required field {{must}} have at a minimum the name. However, when using item info subproperties ("url", "photo"), they {{must}} be nested <em>inside</em> the item element.<br />
<br />
'''author''':: The optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] microformats: <code>version, summary, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
What do you suggest?<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38206project-brainstorming2009-03-24T21:42:54Z<p>Crojecta: /* Projecta */</p>
<hr />
<div>=projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]] and [[hcalendar|hCalendar]].<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* projecta ('''<code>projecta</code>''')<br />
** '''<code>version</code>'''. optional. text.<br />
** '''<code>title</code>'''. required. text. the name of the project.<br />
** '''<code>summary</code>'''. optional. text. one sentence <br />
** '''<code>project</code>''' info. required. ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''.<br />
** '''<code>description</code>'''. optional. text with optional valid HTML markup.<br />
** requirements. optional. text with optional '''<code>url</code>''' to products or other projects.<br />
** steps. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''title''':: This required field {{must}} have at a minimum the name of the project.<br />
<br />
'''summary''':: This optional field serves as a one sentence summary of the project.<br />
<br />
'''project info''':: This required field {{must}} have at a minimum the name. However, when using item info subproperties ("url", "photo"), they {{must}} be nested <em>inside</em> the item element.<br />
<br />
'''author''':: The optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
<br />
'''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.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] microformats: <code>version, summary, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
What do you suggest?<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38201project-brainstorming2009-03-22T05:58:05Z<p>Crojecta: /* Project Type */</p>
<hr />
<div>=Projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], and [[hreview|hReview]] standards.<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* Projecta ('''<code>projecta</code>''')<br />
** '''<code>version</code>'''. optional. text.<br />
** '''<code>summary</code>'''. optional. text.<br />
** '''<code>project</code>''' info. required. ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''.<br />
** '''<code>description</code>'''. optional. text with optional valid HTML markup.<br />
** requirements. optional. text with optional '''<code>url</code>''' to products or other projects.<br />
** steps. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a title for the project itself.<br />
<br />
'''project info''':: This required field {{must}} have at a minimum the name However, when using item info subproperties ("url", "photo"), they {{must}} be nested <em>inside</em> the item element.<br />
<br />
'''author''':: The optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
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.<br />
<br />
'''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.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] microformats: <code>version, summary, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two [types] of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
What do you suggest?<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38182project-examples2009-03-18T05:02:25Z<p>Crojecta: /* CORDIS */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (summary)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator (author)<br />
** Project description<br />
** Project details<br />
*** Project Acronym<br />
*** Project Reference<br />
*** Start Date<br />
*** Duration<br />
*** Project Cost<br />
*** Contract Type<br />
*** End Date<br />
*** Project Status<br />
*** Project Funding<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (steps)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38181project-brainstorming2009-03-18T04:54:49Z<p>Crojecta: /* Format */</p>
<hr />
<div>=Projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], and [[hreview|hReview]] standards.<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* Projecta ('''<code>projecta</code>''')<br />
** '''<code>version</code>'''. optional. text.<br />
** '''<code>summary</code>'''. optional. text.<br />
** '''<code>project</code>''' info. required. ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''.<br />
** '''<code>description</code>'''. optional. text with optional valid HTML markup.<br />
** requirements. optional. text with optional '''<code>url</code>''' to products or other projects.<br />
** steps. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a title for the project itself.<br />
<br />
'''project info''':: This required field {{must}} have at a minimum the name However, when using item info subproperties ("url", "photo"), they {{must}} be nested <em>inside</em> the item element.<br />
<br />
'''author''':: The optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
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.<br />
<br />
'''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.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] microformats: <code>version, summary, 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].<br />
<br />
==Format Development==<br />
Further development is based on your feedback.<br />
<br />
===Project Type===<br />
There are two types of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
====Suggestion====<br />
What do you suggest?<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38180project-examples2009-03-18T04:49:24Z<p>Crojecta: /* 43things */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (summary)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (steps)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38179project-examples2009-03-18T04:44:38Z<p>Crojecta: Undo revision 38178 by Crojecta (Talk)</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (steps)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38178project-examples2009-03-18T04:43:31Z<p>Crojecta: /* CORDIS */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (steps)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38177project-examples2009-03-18T04:42:36Z<p>Crojecta: /* RX-8 iPod Install */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (steps)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** notes<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38176project-examples2009-03-18T04:41:20Z<p>Crojecta: /* Poncho */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material (requirements)<br />
** Gauge (notes)<br />
** directions (steps)<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** Notes (notes)<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38175project-examples2009-03-18T04:40:32Z<p>Crojecta: /* RX-8 iPod Install */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** Notes (notes)<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38174project-examples2009-03-18T04:37:18Z<p>Crojecta: /* RX-8 iPod Install */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** Notes<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38173project-examples2009-03-18T04:33:41Z<p>Crojecta: /* RX-8 iPod Install */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
=== RX-8 iPod Install ===<br />
How to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** Notes (Bullets)<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38172project-examples2009-03-18T04:33:20Z<p>Crojecta: </p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
=== RX-8 iPod Install ===<br />
how to install an iPod into an RX-8<br />
* http://www.whatsmyip.org/ipodrx8/<br />
<br />
** title<br />
** author<br />
** date<br />
** Car Compatibility List (summary)<br />
** Basic Idea (steps)<br />
** Tools Needed (requirements)<br />
** Notes (Bullets)<br />
** WARNING<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=projecta&diff=38171projecta2009-03-18T03:38:19Z<p>Crojecta: /* Field details */</p>
<hr />
<div>=Projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], and [[hreview|hReview]] standards.<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* Projecta ('''<code>projecta</code>''')<br />
** '''<code>version</code>'''. optional. text.<br />
** '''<code>summary</code>'''. optional. text.<br />
** '''<code>project</code>'''. info. required. ('''<code>url</code>''' || '''<code>photo</code>''')<br />
** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''.<br />
** '''<code>description</code>'''. optional. text with optional valid HTML markup.<br />
** requirements. optional. text with optional '''<code>url</code>''' to products or other projects.<br />
** steps. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a title for the project itself.<br />
<br />
'''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.<br />
<br />
'''author''':: This optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
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.<br />
<br />
'''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.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''steps''':: Steps are represented using an ordered list of tasks required to complete the project. Represented as an ordered list with list elements.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
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].</div>Crojectahttps://microformats.org/wiki/index.php?title=projecta&diff=38170projecta2009-03-18T03:36:41Z<p>Crojecta: /* Schema */</p>
<hr />
<div>=Projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], and [[hreview|hReview]] standards.<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* Projecta ('''<code>projecta</code>''')<br />
** '''<code>version</code>'''. optional. text.<br />
** '''<code>summary</code>'''. optional. text.<br />
** '''<code>project</code>'''. info. required. ('''<code>url</code>''' || '''<code>photo</code>''')<br />
** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''.<br />
** '''<code>description</code>'''. optional. text with optional valid HTML markup.<br />
** requirements. optional. text with optional '''<code>url</code>''' to products or other projects.<br />
** steps. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a title for the project itself.<br />
<br />
'''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.<br />
<br />
'''author''':: The optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
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.<br />
<br />
'''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.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''steps''':: Steps are represented using an ordered list of tasks required to complete the project. Represented as an ordered list with list elements.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
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].</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38167project-examples2009-03-18T01:18:52Z<p>Crojecta: /* Project Examples */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project&diff=38143project2009-03-13T10:09:35Z<p>Crojecta: </p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
'''View each individual page as the main page omits some content.'''<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
== real world examples ==<br />
<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things.com ===<br />
* http://43things.com<br />
How I did a project<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* Projecta ('''<code>projecta</code>''')<br />
** '''<code>version</code>'''. optional. text.<br />
** '''<code>summary</code>'''. optional. text.<br />
** '''<code>project</code>''' info. required. ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''.<br />
** '''<code>description</code>'''. optional. text with optional valid HTML markup.<br />
** requirements. optional. text with optional '''<code>url</code>''' to products or other projects.<br />
** steps. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a title for the project itself.<br />
<br />
'''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.<br />
<br />
'''author''':: The optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
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.<br />
<br />
'''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.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''steps''':: Steps are represented using an ordered list of tasks required to complete the project. Represented as an ordered list with list elements.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
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].<br />
<br />
<br />
=== markup sample ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
<pre><nowiki><br />
<div class="project" id="urn:uuid:233f6e5d-2ad2-4b7e-a3fe-1b90ef2fef57"><br />
<img class="logo" src="..." /><br />
<span class="name">Microformats</span><br />
<span class="desc">An initiative to extract common patterns from POSH</span><br />
<br />
<h1>Some informations</h1><br />
<a href="http://microformats.org/" rel="home">The primary home page of the project.</a><br />
<a href="..." rel="source">Here you can find its source code.</a><br />
<a href="..." rel="release">Get the releases.</a><br />
<-- Every hCard is looked as a participant [including venues? ] --><br />
<br />
<h1>Project's tags</h1><br />
<ul><br />
<li class="tag">open</li><br />
<li class="tag">format</li><br />
<li class="tag">standard</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
=== CSS selection specification ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
A good way to describe the structure, is to look at it trough the view of CSS selectors. Designers sometimes need wrappers, which makes it hard to keep a strict structure. If you used jQuery, you know what I mean.<br />
<br />
<pre><nowiki><br />
.project[@id] : is an UUID (see http://ietf.org/rfc/rfc4122.txt).<br />
A unique identifier for the project.<br />
It is used to resolve name clashes.<br />
.project .name : the content describes the project name.<br />
Should not appear more that one time per project.<br />
.project IMG.logo : the src is a link to the logo.<br />
Can have different sizes with by adding "low | mid | high" classes.<br />
.project A[@rel=home] : a project's home page<br />
.project A[@rel=source] : a link to the project's source.<br />
If it is a scm, it is generally solved by using different uris.<br />
Like git:// or bzr:// or http+git://<br />
.project A[@rel=release] : the linked pages contains file releases.<br />
This page can contain hRelease microformat.<br />
.project A[@rel=...] : many extensions can be imagined, like :<br />
"blog | wiki | parent-project | ..."<br />
.project .tag : the content describes a project tag. You can<br />
have as many as you wish.<br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Notes ==<br />
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 ?<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38142project-examples2009-03-13T02:19:54Z<p>Crojecta: /* Project Examples */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com Derek] <br />
<br />
There are two kinds of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself. -[http://tobyinkster.co.uk Toby]<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project&diff=38141project2009-03-13T02:09:26Z<p>Crojecta: /* real world examples */</p>
<hr />
<div><h1>Project</h1><br />
This is a page for tracking the effort to develop a project microformat for authors and publishers to markup public projects like open-source software or other kinds of artistic distributions.<br />
{{TOC-right}}<br />
{{formatset|project}}<br />
<br />
== problem statement ==<br />
=== scenarios ===<br />
One of its primary intent is to allow robots to automatically classify projects in a freshmeat <!-- ? --> manner by browsing the web.<br />
[[User:ZimbaTm|ZimbaTm]] 08:31, 12 Jan 2008 (PST)<br />
<br />
== real world examples ==<br />
<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things.com ===<br />
* http://43things.com<br />
How I did a project<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== existing formats ==<br />
Please document in [[project-formats]].<br />
<br />
* [http://hyperdata.org/xmlns/project/ A vocabulary for describing projects] (primarily goal-oriented)<br />
* [http://usefulinc.com/doap/ DOAP: Description of a Project] (software project specific)<br />
** [http://hyperdata.org/xmlns/hdoap/profile/ hDOAP] - previous [[poshformat|microformat-like]] effort<br />
* [http://en.wikipedia.org/wiki/Program_Evaluation_and_Review_Technique Program Evaluation and Review Technique]<br />
<br />
== Related microformats ==<br />
* [[hCalendar]] for timelines, milestones, and to-do items<br />
* Resources<br />
** [[hCard]] for participating people<br />
** [[product]] for stuff(?)<br />
*** [[rel-payment]]<br />
* [[hReview]] for debriefing<br />
<br />
== brainstorming ==<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* Projecta ('''<code>projecta</code>''')<br />
** '''<code>version</code>'''. optional. text.<br />
** '''<code>summary</code>'''. optional. text.<br />
** '''<code>project</code>''' info. required. ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''.<br />
** '''<code>description</code>'''. optional. text with optional valid HTML markup.<br />
** requirements. optional. text with optional '''<code>url</code>''' to products or other projects.<br />
** steps. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a title for the project itself.<br />
<br />
'''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.<br />
<br />
'''author''':: The optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
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.<br />
<br />
'''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.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''steps''':: Steps are represented using an ordered list of tasks required to complete the project. Represented as an ordered list with list elements.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
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].<br />
<br />
<br />
=== markup sample ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
<pre><nowiki><br />
<div class="project" id="urn:uuid:233f6e5d-2ad2-4b7e-a3fe-1b90ef2fef57"><br />
<img class="logo" src="..." /><br />
<span class="name">Microformats</span><br />
<span class="desc">An initiative to extract common patterns from POSH</span><br />
<br />
<h1>Some informations</h1><br />
<a href="http://microformats.org/" rel="home">The primary home page of the project.</a><br />
<a href="..." rel="source">Here you can find its source code.</a><br />
<a href="..." rel="release">Get the releases.</a><br />
<-- Every hCard is looked as a participant [including venues? ] --><br />
<br />
<h1>Project's tags</h1><br />
<ul><br />
<li class="tag">open</li><br />
<li class="tag">format</li><br />
<li class="tag">standard</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
=== CSS selection specification ===<br />
<strong>Note: this markup sample is not based on any [[project-examples]] implied schema, and therefore is an <em>a priori</em> brainstorm that is not suitable for a microformat.</strong><br />
<br />
A good way to describe the structure, is to look at it trough the view of CSS selectors. Designers sometimes need wrappers, which makes it hard to keep a strict structure. If you used jQuery, you know what I mean.<br />
<br />
<pre><nowiki><br />
.project[@id] : is an UUID (see http://ietf.org/rfc/rfc4122.txt).<br />
A unique identifier for the project.<br />
It is used to resolve name clashes.<br />
.project .name : the content describes the project name.<br />
Should not appear more that one time per project.<br />
.project IMG.logo : the src is a link to the logo.<br />
Can have different sizes with by adding "low | mid | high" classes.<br />
.project A[@rel=home] : a project's home page<br />
.project A[@rel=source] : a link to the project's source.<br />
If it is a scm, it is generally solved by using different uris.<br />
Like git:// or bzr:// or http+git://<br />
.project A[@rel=release] : the linked pages contains file releases.<br />
This page can contain hRelease microformat.<br />
.project A[@rel=...] : many extensions can be imagined, like :<br />
"blog | wiki | parent-project | ..."<br />
.project .tag : the content describes a project tag. You can<br />
have as many as you wish.<br />
</nowiki></pre><br />
<br />
== to-do ==<br />
* [[project-examples]]<br />
* [[project-formats]]<br />
* Lots of discussion I guess, to satisfy different kinds of projects<br />
* Semantic approval of experts<br />
<br />
== Notes ==<br />
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 ?<br />
<br />
== Related ideas ==<br />
* Release: semantic description of a project release. Possible usages : automatic tracking and/or conversion for package managers, automatic platform/mirror selection for download managers.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38140project-examples2009-03-13T02:08:17Z<p>Crojecta: /* Project Examples */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com/ Derek] <br />
<br />
There are two kinds of project page as I see it - the abstract (name of the project, description, goals, who's in charge, related web pages, etc) and the practical (name of the project, step by step how it can be achieved).<br />
<br />
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.<br />
<br />
The World Bank site and CORDIS are examples of the former - what are the goals of the project? who is taking part? who is funding it? how much will it cost? But they don't give you step-by-step instructions for how to carry out the project in your own home in your spare time. And you won't expect them to.<br />
<br />
The knitting site, and recipes are different. The goals are not explicitly stated; no time frame is given (I could knit a poncho tomorrow, or maybe in a few years' time). The focus is on the step by step documentation of how it can be done, so that you can replicate the project yourself.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-examples&diff=38139project-examples2009-03-13T01:52:36Z<p>Crojecta: /* Centralized Implementations */</p>
<hr />
<div>= Project Examples =<br />
<br />
There have been several efforts to define data formats for posting "projects" on the Web.<br />
<br />
This page serves to document the current list of project examples from real world sites for the design of a simple project [[microformat]]. -[http://crojecta.com/ Derek] <br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Examples on the Web ==<br />
<br />
== Centralized Implementations ==<br />
=== Freshmeat.net ===<br />
Description of the software project<br />
* http://freshmeat.net<br />
<br />
** full project name (This is the publicly visible project name.)<br />
** short project name (This will be used to generate a /projects/<shortname>/ URL for your project.)<br />
** full description<br />
** short description<br />
** name of author<br />
** email address<br />
** branch name<br />
** branch description<br />
** license<br />
** homepage<br />
** Tar/GZ<br />
** Tar/BZ2<br />
** Zip<br />
** Changelog<br />
** RPM package<br />
** Debian package<br />
** OS X package<br />
** Bittorrent<br />
** BSD Ports URL<br />
** Autopackage URL<br />
** Jar<br />
** Purchase<br />
** CVS tree (cvsweb)<br />
** Bug tracker<br />
** Mailing list archive<br />
** Mirror site<br />
** Demo site<br />
** version<br />
** release focus<br />
** Dependencies<br />
<br />
=== 43things ===<br />
How I did a project<br />
* http://43things.com<br />
<br />
** goal title<br />
** last words (One sentence summary.)<br />
** how<br />
** lessons<br />
** time taken<br />
** resources<br />
<br />
=== Moldova Aid Project ===<br />
A humanitarian aid project<br />
* http://www.moldovaaidproject.org.uk/<br />
<br />
** summary<br />
** achievements<br />
<br />
=== CORDIS ===<br />
Community Research and Development Information Service<br />
* [http://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&QUERY=011ffa6da836:797a:027547cc&RCN=88231 FP7 Example]<br />
<br />
** project title<br />
** Research area<br />
** Coordinator<br />
** Project description<br />
** Project details<br />
** Participants<br />
<br />
=== The World Bank === <br />
Moldova Community Forestry Project<br />
* [http://web.worldbank.org/external/projects/main?pagePK=64283627&piPK=73230&theSitePK=40941&menuPK=228424&Projectid=P109459 Project Details]<br />
<br />
** project title<br />
** Project ID<br />
** Project Status<br />
** Approval Date<br />
** Closing Date<br />
** Total Project Cost<br />
** Region<br />
** Major Sector (Sector) (%)<br />
** Old Major Sector<br />
** Old Sector<br />
** Environmental Category<br />
** Bank Team Lead<br />
** Borrower<br />
** Implementing Agency<br />
** Project Goals<br />
** Available Project Documents<br />
** Related Country Information<br />
<br />
=== Poncho ===<br />
How to make a poncho<br />
* http://orangmerajut.blogspot.com/2005/03/poncho_13.html<br />
<br />
** project title<br />
** summary<br />
** Material<br />
** Gauge<br />
** directions<br />
<br />
== Analysis of Examples ==<br />
<br />
=== Common project fields ===<br />
* project (name/title|URL(s)|image)<br />
* author (name|email|URL)<br />
* summary<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojectahttps://microformats.org/wiki/index.php?title=project-brainstorming&diff=38138project-brainstorming2009-03-12T10:33:47Z<p>Crojecta: /* Field details */</p>
<hr />
<div>=Projecta=<br />
Even though there are existing project formats, the projecta format {{must}} be developed because there is no established project format and it will enable decentralized development of projects.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Derek Lewis<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
== Format ==<br />
=== In General ===<br />
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]], [[hcalendar|hCalendar]], and [[hreview|hReview]] standards.<br />
<br />
=== Schema ===<br />
The projecta schema consists of the following:<br />
<br />
* Projecta ('''<code>projecta</code>''')<br />
** '''<code>version</code>'''. optional. text.<br />
** '''<code>summary</code>'''. optional. text.<br />
** '''<code>project</code>''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' )<br />
** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''.<br />
** '''<code>description</code>'''. optional. text with optional valid HTML markup.<br />
** requirements. optional. text with optional '''<code>url</code>''' to products or other projects.<br />
** steps. optional. text with valid HTML '''<code>ol</code>''' ('''<code>li</code>''') elements.<br />
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.<br />
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.<br />
<br />
=== Field details ===<br />
The fields of the projecta schema represent the following:<br />
<br />
'''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".<br />
<br />
'''summary''':: This optional field serves as a title for the project itself.<br />
<br />
'''project info''':: This required field {{must}} have at a minimum the name However, when using item info subproperties ("url", "photo"), they {{must}} be nested <em>inside</em> the item element.<br />
<br />
'''author''':: The optional field specifies the person who authored the project. If the author is specified, an hCard representing the author {{must}} be provided.<br />
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.<br />
<br />
'''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.<br />
<br />
'''requirements''':: This optional field contains the requirements of the project. The field {{may}} include links to products or other projects.<br />
<br />
'''steps''':: Steps are represented using an ordered list of tasks required to complete the project. Represented as an ordered list with list elements.<br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
The following field names have been reused from the [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] microformats: <code>version, summary, 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].<br />
<br />
== See Also ==<br />
* [[project]]<br />
* [[project-examples]]<br />
* [[project-brainstorming]]<br />
* [[project-formats]]<br />
<br />
See [[projecta|projecta]] for the result and evolution of these thoughts on a microformat.</div>Crojecta