project-brainstorming: Difference between revisions
m (→Schema) |
|||
| Line 24: | Line 24: | ||
** '''<code>version</code>'''. optional. text. | ** '''<code>version</code>'''. optional. text. | ||
** '''<code>title</code>'''. required. text. the name of the project. | ** '''<code>title</code>'''. required. text. the name of the project. | ||
** '''<code>summary</code>'''. optional. text. one sentence | ** '''<code>summary</code>'''. optional. text. one sentence. | ||
** '''<code>project</code>''' info. required. ('''<code>url</code>''' || '''<code>photo</code>''' ) | ** '''<code>project</code>''' info. required. ('''<code>url</code>''' || '''<code>photo</code>''' ) | ||
** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''. | ** '''<code>author</code>'''. optional. '''[[hcard|hCard]]'''. | ||
Revision as of 21:43, 24 March 2009
projecta
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.
Contributors
- Derek Lewis
See Also
Format
In General
The projecta format is based on a set of fields common to numerous project sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related hCard and hCalendar.
Schema
The projecta schema consists of the following:
- projecta (
projecta)version. optional. text.title. required. text. the name of the project.summary. optional. text. one sentence.projectinfo. required. (url||photo)author. optional. hCard.description. optional. text with optional valid HTML markup.- requirements. optional. text with optional
urlto products or other projects. - steps. optional. text with valid HTML
ol(li) elements. - tags. optional. keywords or phrases, using rel-tag, each with optional rating.
- permalink. optional, using rel-bookmark and rel-self.
Field details
The fields of the projecta schema represent the following:
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".
title:: This required field MUST have at a minimum the name of the project.
summary:: This optional field serves as a one sentence summary of the project.
project info:: This required field MUST have at a minimum the name. However, when using item info subproperties ("url", "photo"), they MUST be nested inside the item element.
author:: The optional field specifies the person who authored the project. If the author is specified, an hCard representing the author MUST be provided.
description:: This optional field contains the full text representing the input of the author. The field MAY include valid HTML markup (e.g. paragraphs). User agents SHOULD preserve any markup.
requirements:: This optional field contains the requirements of the project. The field MAY include links to products or other projects.
tags:: Tags are represented using a list of keywords or phrases (using the rel-tag microformat for each individual keyword or phrase tag) that the author associates with the project.
permalink:: This optional field is a URL for the projecta. In addition to using the <a href> tag for this field, the attribute rel="self bookmark" MUST be used to indicate that the hyperlink is a permalink for the project itself. If the hyperlink already contains a rel attribute, then the values self and bookmark MUST be included among the space-separated set of values in the attribute. Indexers MAY treat the permalink of a project as a unique ID in order to identify and collate the same project from multiple sources (such as indexing a page multiple times). The permalink MAY also be used to indicate or imply the origin of the project. Authors MAY use the classname of "permalink" on the element representing the permalink.
The following field names have been reused from the hCard, hCalendar, and hReview microformats: version, summary, url, photo, description, tags, permalink. In addition, items and authors described by hCards MAY contain any hCard field. The rel value "self" has been reused from the Atom 1.0 specification.
Format Development
Further development is based on your feedback.
Project Type
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).
The former overlaps with hCard / hDOAP; the latter with hRecipe (though hRecipe only suitable for a limited subset). There is very little common ground.
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.
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. -Toby
Suggestion
What do you suggest?
See Also
See projecta for the result and evolution of these thoughts on a microformat.