[uf-discuss] Principles of Microformats?

Mike Schinkel mikeschinkel at gmail.com
Wed Dec 13 16:12:10 PST 2006

I've sat down and tried to define a list of principles regarding
microformats. I wanted to present this list here and get feedback to make
sure that I am not misunderstanding them.
Please comment on them by number so as to make clear any comments.  Thanks
in advance.

1.) Includes visible-only
2.) One flat namespace
3.) No solution for resolving ambiguities
4.) No Microformat registry
5.) No versioning capability
6.) Recognition is exclusive
7.) Requires community process and approval 
8.) Envisions limited scope
9.) Process favors expedience
10.) Specifications allowed to evolved w/o explicit finalization
11.) Considers existing HTML usage 
12.) Centralized control and approval authority
13.) One design discussion mailing list 
14.) No delegation of decision authority
15.) Implementations not part of process
16.) No officially recognized implementations
17.) Inspired by needs of Bloggers and blog-related services
18.) Emphasizes general purpose needs
19.) Focuses on existing content publishing models
20.) Aims to avoid changing publishing behavior
21.) Envisions exposing existing content semantically
22.) Constrained to enhancing known use-cases.

-Mike Schinkel

P.S. I know is a different presentation of principles on the wiki and
elsewhere, but I'm trying to clarify my understanding of the Microformats
vision, principles, and process and as such my use-case needs to understand
them in a list like I have provided above.

More information about the microformats-discuss mailing list