how-to-brainstorming - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:27:08Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:27, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~how-to brainstorming~~</entry-title>~~		{{DISPLAYTITLE:how-to brainstorming}}

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

Juraj: /* how-to proposal */

2012-05-08T12:31:55Z

how-to proposal

← Older revision		Revision as of 12:31, 8 May 2012
Line 15:		Line 15:

	* '''howto''' - main class		* '''howto''' - main class
	** ~~'''~~problem~~'''~~ - problem which the solution solve.		** problem - problem which the solution solve.
	** ~~'''~~category~~'''~~ - domain or category of problem (IT, horticulture)		** category - domain or category of problem (IT, horticulture)
	** summary		** summary
	** ~~solution - element which content solution~~		** equipment - working tools and working conditions (hammer, brush tool, some kind of IDE...)
	*** tools - 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
	*** 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
	*** duration - time duration, used with microformat hCalendar		** price
	*** ~~'''~~instructions~~'''~~ - steps to solve problem		** instructions - steps to solve problem
	**** hMedia
	**** code
	**** rel-enclosure
	** faq - element for FAQ, which contents questions and answers
	*** question
	*** answer
	** warning		** warning
	** tip		** tip
	** ~~'''~~author~~'''~~ - author of solution (hCard)		** 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 ==		== comments ==

Juraj: /* how-to proposal */

2012-04-16T23:58:09Z

how-to proposal

← Older revision		Revision as of 23:58, 16 April 2012
Line 14:		Line 14:
	possible schema of how-to:		possible schema of how-to:

	* '''~~how-to~~''' - main class		* '''howto''' - main class
	** '''problem''' - problem which the solution solve.		** '''problem''' - problem which the solution solve.
	** '''category''' - domain or category of problem (IT, horticulture)		** '''category''' - domain or category of problem (IT, horticulture)

Juraj: /* how-to proposal */

2012-04-14T21:31:05Z

how-to proposal

← Older revision		Revision as of 21:31, 14 April 2012
Line 17:		Line 17:
	** '''problem''' - problem which the solution solve.		** '''problem''' - problem which the solution solve.
	** '''category''' - domain or category of problem (IT, horticulture)		** '''category''' - domain or category of problem (IT, horticulture)
			** summary
	** solution - element which content solution		** solution - element which content solution
	*** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)		*** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)

Juraj: /* how-to proposal */

2012-04-14T21:27:17Z

how-to proposal

← Older revision		Revision as of 21:27, 14 April 2012
Line 28:		Line 28:
	*** question		*** question
	*** answer		*** answer
			** warning
			** tip
	** '''author''' - author of solution (hCard)		** '''author''' - author of solution (hCard)
	** published - datetime of publishing		** published - datetime of publishing

Juraj at 18:14, 14 April 2012

2012-04-14T18:14:36Z

← Older revision		Revision as of 18:14, 14 April 2012
Line 9:		Line 9:

	== problem statement ==		== 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.		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 ==		== 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:~~		possible schema of how-to:


	== possible schema of how-to ==

	* '''how-to''' - main class		* '''how-to''' - main class

Juraj: /* comments */

2012-04-14T17:36:24Z

comments

← Older revision		Revision as of 17:36, 14 April 2012
Line 38:		Line 38:

	== comments ==		== comments ==

			I think that better property name for working tools and conditions will be '''equipments''' -- [[User:Juraj\|Juraj Sivak]]

	== see also ==		== see also ==

Juraj: /* possible schema of how-to */

2012-04-14T17:32:05Z

possible schema of how-to

← Older revision		Revision as of 17:32, 14 April 2012
Line 36:		Line 36:

	'''Bold''' elements should be required.		'''Bold''' elements should be required.

			== comments ==

	== see also ==		== see also ==

Juraj: /* possible schema of how-to */

2012-04-14T11:13:08Z

possible schema of how-to

← Older revision		Revision as of 11:13, 14 April 2012
Line 20:		Line 20:
	** '''problem''' - problem which the solution solve.		** '''problem''' - problem which the solution solve.
	** '''category''' - domain or category of problem (IT, horticulture)		** '''category''' - domain or category of problem (IT, horticulture)
	** ~~'''~~solution~~'''~~ - element which content solution		** solution - element which content solution
	*** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)		*** tools - 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		*** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct
Line 28:		Line 28:
	**** code		**** code
	**** rel-enclosure		**** rel-enclosure
	*** faq - element for FAQ, which contents questions and answers		** faq - element for FAQ, which contents questions and answers
	*** question		*** question
	*** answer		*** answer

Juraj: /* how-to proposal */

2012-04-14T11:05:03Z

how-to proposal

← Older revision		Revision as of 11:05, 14 April 2012
Line 13:		Line 13:
	== how-to proposal ==		== 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:		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:


			== possible schema of how-to ==

	* '''how-to''' - main class		* '''how-to''' - main class
	** '''problem''' - problem which the solution solve.		** '''problem''' - problem which the solution solve.
	** '''~~domain~~''' - domain of problem (IT, horticulture)		** '''category''' - domain or category of problem (IT, horticulture)
	** '''solution''' - element which content solution		** '''solution''' - element which content solution
	*** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)		*** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)
Line 32:		Line 35:
	** tag - for keywords, rel-tags		** tag - for keywords, rel-tags

	Bold elements should be required.		'''Bold''' elements should be required.

	== see also ==		== see also ==