how-to-brainstorming: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(12 intermediate revisions by 2 users not shown)
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:
{{DISPLAYTITLE:how-to brainstorming}}


* '''how-to''' - main class
This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.
** '''problem''' - problem which the solution solve.  
 
** '''domain''' - domain of problem (IT, horticulture)
Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.
** '''solution''' - element which content solution
 
*** difficulty - how difficult is solution for user (technical, equipment, duration, price)
* [[how-to-examples]]
**** technical
* [[how-to-formats]]
**** equipment
 
**** duration
== problem statement ==
**** price
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. Solution to this problem would be how-to microformat.
*** '''instructions''' - steps to solve problem
 
*** inset - insets like images, videos, source codes
== how-to proposal ==
**** hMedia
possible schema of how-to:
**** code
 
**** rel-enclosure
* '''howto''' - main class
** faq - element for FAQ, which contents questions and answers
** problem - problem which the solution solve.  
*** question
** category - domain or category of problem (IT, horticulture)
*** answer
** summary
** '''author''' - author of solution (hCard)
** equipment - working tools and working conditions (hammer, brush tool, some kind of IDE...)
** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct
** duration - time duration, used with microformat hCalendar
** price
** instructions - steps to solve problem
** warning
** tip
** author - author of solution (hCard)
** published - datetime of publishing
** published - datetime of publishing
** tag - for keywords, rel-tags
** tag - for keywords, rel-tags


Bold elements should be required.
== comments ==
 
I think that better property name for working tools and conditions will be '''equipments''' -- [[User:Juraj|Juraj Sivak]]
 
== see also ==
* [[how-to]]
* [[how-to-examples]]
* [[how-to-formats]]

Latest revision as of 16:27, 18 July 2020


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. Solution to this problem would be how-to microformat.

how-to proposal

possible schema of how-to:

  • howto - main class
    • problem - problem which the solution solve.
    • category - domain or category of problem (IT, horticulture)
    • summary
    • equipment - working tools and working conditions (hammer, brush tool, some kind of IDE...)
    • components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct
    • duration - time duration, used with microformat hCalendar
    • price
    • instructions - steps to solve problem
    • warning
    • tip
    • author - author of solution (hCard)
    • published - datetime of publishing
    • tag - for keywords, rel-tags

comments

I think that better property name for working tools and conditions will be equipments -- Juraj Sivak

see also

Retrieved from "http://microformats.org/wiki/index.php?title=how-to-brainstorming&oldid=69877"