Software Projects Description Re: [uf-discuss] Potential Microformats

Tantek Ç elik tantek at cs.stanford.edu
Thu Oct 5 10:27:50 PDT 2006



On 10/5/06 9:18 AM, "Danny Ayers" <danny.ayers at gmail.com> wrote:

> I could have sworn I mailed this or the dev list about hDOAP [1] , but
> I can't find anything substantial in the archives, probably forgot the
> cc...anyhow basically it's a way of describing software projects in
> HTML, based on DOAP [2] which could potentially become a microformat
> (according to microformats.org conventions).

<snip>

> I didn't follow microformats.org process, though I do believe some of
> the key prerequisites have been fulfilled.

This is the key.  Just taking an existing format and translating them to
class names is not enough - as the folks working on citations will tell you.

> I believe what's lacking from a process point of view is mainly a few
> cycles through this list ;-)

What is lacking is following the process step by step:

 http://microformats.org/wiki/process

starting with a *-examples page, then a *-formats page (which should list
DOAP of course), and *then* a *-brainstorming page.


The reasons for this are very much inline with what Karl said:

On 10/5/06 6:51 AM, "Karl Dubost" <karl at w3.org> wrote:

> I'm not sure I will bother ask each time. But let's try.
> 
> * Use Case Scenarios?

E.g. *-examples


> * Benefits for the End Users?

I.e. what is the real world problem we are trying to solve?


> Wrong answers:
>  - more semantic pages
>  - to help the Web site manager with its data

Thanks Karl,

Tantek



More information about the microformats-discuss mailing list