how-to-brainstorming: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
(add header with process reference, prerequisites, see also)
Line 1: Line 1:
Every day we are looking for some kind of manual to solve our problems. If we can not effectively use Web search engine, it is quite time consuming task. After reviewing the web microformats.org, I decided to propose microformat for publishing troubleshooting. I called my microformat "how-to" and its schema is as follows:
<entry-title>how-to brainstorming</entry-title>
 
This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.
 
Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.
 
* [[how-to-examples]]
* [[how-to-formats]]
 
== problem statement ==
Every day we are looking for some kind of manual to solve our problems. If we can not effectively use Web search engine, it is quite time consuming task.  
 
== how-to proposal ==
After reviewing the web microformats.org, I decided to propose microformat for publishing troubleshooting. I called my microformat "how-to" and its schema is as follows:


* '''how-to''' - main class
* '''how-to''' - main class
Line 23: Line 36:


Bold elements should be required. [[User:Juraj|Juraj Sivak]]
Bold elements should be required. [[User:Juraj|Juraj Sivak]]
== see also ==
* [[how-to]]
* [[how-to-examples]]
* [[how-to-formats]]

Revision as of 15:47, 30 March 2012

<entry-title>how-to brainstorming</entry-title>

This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.

Per the microformats process, the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.

problem statement

Every day we are looking for some kind of manual to solve our problems. If we can not effectively use Web search engine, it is quite time consuming task.

how-to proposal

After reviewing the web microformats.org, I decided to propose microformat for publishing troubleshooting. I called my microformat "how-to" and its schema is as follows:

  • how-to - main class
    • problem - problem which the solution solve.
    • domain - domain of problem (IT, horticulture)
    • solution - element which content solution
      • difficulty - how difficult is solution for user (technical, equipment, duration, price)
        • technical
        • equipment
        • duration
        • price
      • instructions - steps to solve problem
      • inset - insets like images, videos, source codes
        • hMedia
        • code
        • rel-enclosure
    • faq - element for FAQ, which contents questions and answers
      • question
      • answer
    • author - author of solution (hCard)
    • published - datetime of publishing
    • tag - for keywords, rel-tags

Bold elements should be required. Juraj Sivak

see also