https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=Juraj 2026-04-07T11:39:26Z User contributions MediaWiki 1.38.4 https://microformats.org/wiki/index.php?title=how-to-examples&diff=46244 2012-05-11T19:20:34Z

<p>Juraj: </p> <hr /> <div>* CodeProject® - Your Development Resource<br /> ** http://www.codeproject.com/<br /> ** article type<br /> ** attachment<br /> ** author<br /> ** category<br /> ** comments<br /> ** date of publication<br /> ** instructions<br /> ** introduction<br /> ** license<br /> ** number of bookmarks<br /> ** number of downloads<br /> ** number of views<br /> ** picture<br /> ** rating<br /> ** title<br /> ** vote<br /> * Stack Overflow<br /> ** http://stackoverflow.com/<br /> ** answer<br /> ** author of answer<br /> ** author of question<br /> ** feedback<br /> ** last update<br /> ** number of answers<br /> ** number of votes<br /> ** number of views<br /> ** question<br /> ** reputation score<br /> ** summary<br /> ** tags<br /> ** title<br /> * About.com: Need. Know. Accomplish.<br /> ** http://www.about.com/<br /> ** author<br /> ** category<br /> ** components<br /> ** instructions<br /> ** instructions - pictures<br /> ** introduction<br /> ** related articles<br /> ** secondary title<br /> ** tags<br /> ** things you'll need<br /> ** title<br /> * wikiHow - The How-to Manual That You Can Edit<br /> ** http://www.wikihow.com/<br /> ** authors<br /> ** category<br /> ** feedback<br /> ** instructions<br /> ** introduction<br /> ** last edited<br /> ** number of views<br /> ** related articles<br /> ** sources and citations<br /> ** tips<br /> ** title<br /> ** warnings<br /> * Wonder How To » How To Videos &amp;amp; How-To Articles<br /> ** http://www.wonderhowto.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** date of last edit<br /> ** date of publications<br /> ** instructions<br /> ** instructions - pictures<br /> ** instructions - video<br /> ** introduction<br /> ** number of views<br /> ** picture<br /> ** related articles<br /> ** related videos<br /> ** tags<br /> ** title<br /> ** video length<br /> * How To Do Things » How To Articles &amp; How To Videos<br /> ** http://www.howtodothings.com/<br /> ** author<br /> ** category<br /> ** caution<br /> ** comments<br /> ** instructions<br /> ** introduction<br /> ** popular searches<br /> ** quick tips<br /> ** related articles<br /> ** required tools<br /> ** summary<br /> ** title<br /> ** useful links<br /> * eHow | How to Videos, Articles &amp; More - Discover the expert in you. | eHow.com<br /> ** http://www.ehow.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** contributor<br /> ** instructions<br /> ** instructions - pictures<br /> ** introduction<br /> ** last updated<br /> ** references<br /> ** related ads<br /> ** related articles<br /> ** related searches<br /> ** resources<br /> ** things you'll need<br /> ** tips &amp; warnings<br /> ** title<br /> ** you may also like<br /> * HowToForge - Linux Howtos and Tutorials<br /> ** http://www.howtoforge.com/<br /> ** author<br /> ** category<br /> ** date &amp; time of publication<br /> ** instructions<br /> ** instructions - pictures<br /> ** introduction<br /> ** license<br /> ** links<br /> ** title<br /> * How-To Geek - Computer Help from yout Griend How-To Geek<br /> ** http://www.howtogeek.com/<br /> ** attachment<br /> ** author<br /> ** comments<br /> ** date of publication<br /> ** instructions<br /> ** instructions - pictures<br /> ** introduction<br /> ** title<br /> * How To - Tips for your phone, tablet, computer, home theater and the Web - CNET<br /> ** http://howto.cnet.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** date &amp; time of publication<br /> ** instructions<br /> ** instructions - pictures<br /> ** instructions - video<br /> ** introduction<br /> ** secondary title<br /> ** summary<br /> ** tags<br /> ** title<br /> * Instructables - Make, How to, and DIY<br /> ** http://www.instructables.com/<br /> ** attachment<br /> ** author<br /> ** comments<br /> ** instructions<br /> ** instructions - pictures<br /> ** introduction<br /> ** picture<br /> ** rating<br /> ** summary<br /> ** tags<br /> ** title<br /> ** you will need<br /> * How to Clean Stuff<br /> ** http://www.howtocleanstuff.net/<br /> ** additional tips and advice<br /> ** category<br /> ** comments<br /> ** instructions<br /> ** introduction<br /> ** picture<br /> ** related posts<br /> ** tags<br /> ** title<br /> ** you will need<br /> * Study skills articles and study tips, improve study habits, teaching tips<br /> ** http://www.how-to-study.com/<br /> ** category<br /> ** instructions<br /> ** introduction<br /> * Home Improvement and Remodeling: This Old House<br /> ** http://www.doityourself.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** instructions<br /> ** introduction<br /> ** picture<br /> ** related how-to's<br /> ** related links<br /> ** related products<br /> ** title<br /> * Repair-Home - Kitchen, Bathroom, Window, HVAC and Other Home Improvements<br /> ** http://www.repair-home.com/<br /> ** category<br /> ** instructions<br /> ** introduction<br /> ** materials<br /> ** title<br /> * HOMETIME<br /> ** http://www.hometime.com/home.html<br /> ** components<br /> ** instructions<br /> ** instructions - pictures<br /> ** instructions - video<br /> ** note<br /> ** pictures<br /> ** title<br /> ** warning<br /> * DIY Network - Home Improvement How-To &amp; Remodeling Projects<br /> ** http://www.diynetwork.com/<br /> ** category<br /> ** comments<br /> ** difficulty<br /> ** duration<br /> ** feedback<br /> ** instructions<br /> ** introduction<br /> ** materials<br /> ** picture<br /> ** price range<br /> ** related articles<br /> ** title<br /> ** tools<br /> * Honestly DIY - Honestly WTF<br /> ** http://honestlywtf.com/diy/<br /> ** author<br /> ** category<br /> ** comments<br /> ** date of posting<br /> ** instructions<br /> ** instructions - pictures<br /> ** introduction<br /> ** picture<br /> ** similar posts<br /> ** tags<br /> ** title<br /> ** you'll need<br /> * 5min - Find the best how to, instructional and DIY videos – Life Videopedia<br /> ** http://www.5min.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** instructions - video<br /> ** rating<br /> ** related videos<br /> ** summary<br /> ** title<br /> ** number of views<br /> * Project Cost - Build a Rail Fence<br /> ** http://www.diyornot.com/<br /> ** category<br /> ** duration<br /> ** feedback<br /> ** instructions<br /> ** instructions - pictures<br /> ** introduction<br /> ** materials required<br /> ** price<br /> ** tip<br /> ** title<br /> ** tools required<br /> * Hack a Day<br /> ** http://hackaday.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** date &amp; time of posted<br /> ** instructions<br /> ** instructions - pictures<br /> ** instructions - video<br /> ** introduction<br /> ** math formulas<br /> ** title</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-examples&diff=46243 2012-05-11T19:04:30Z

<p>Juraj: </p> <hr /> <div>* CodeProject® - Your Development Resource<br /> ** http://www.codeproject.com/<br /> ** article type<br /> ** attachment<br /> ** author<br /> ** category<br /> ** comments<br /> ** date of publication<br /> ** instructions<br /> ** introduction<br /> ** license<br /> ** number of bookmarks<br /> ** number of downloads<br /> ** number pf views<br /> ** picture<br /> ** rating<br /> ** title<br /> ** vote<br /> * Stack Overflow<br /> ** http://stackoverflow.com/<br /> ** answer<br /> ** author of answer<br /> ** author of question<br /> ** feedback<br /> ** last update<br /> ** number of votes<br /> ** number of answers<br /> ** number of views<br /> ** question<br /> ** reputation score<br /> ** summary<br /> ** tags<br /> ** title<br /> * About.com: Need. Know. Accomplish.<br /> ** http://www.about.com/<br /> ** author<br /> ** category<br /> ** components<br /> ** instructions - pictures<br /> ** instructions<br /> ** introduction<br /> ** related articles<br /> ** secondary title<br /> ** tags<br /> ** things you'll need<br /> ** title<br /> * wikiHow - The How-to Manual That You Can Edit<br /> ** http://www.wikihow.com/<br /> ** authors<br /> ** category<br /> ** feedback<br /> ** instructions<br /> ** introduction<br /> ** last edited<br /> ** number of views<br /> ** related articles<br /> ** sources and citations<br /> ** tips<br /> ** title<br /> ** warnings<br /> * Wonder How To » How To Videos &amp;amp; How-To Articles<br /> ** http://www.wonderhowto.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** date of last edit<br /> ** date of publications<br /> ** instructions - pictures<br /> ** instructions - video<br /> ** instructions<br /> ** introduction<br /> ** number of views<br /> ** picture<br /> ** related articles<br /> ** related videos<br /> ** tags<br /> ** title<br /> ** video length<br /> * How To Do Things » How To Articles &amp; How To Videos<br /> ** http://www.howtodothings.com/<br /> ** author<br /> ** category<br /> ** caution<br /> ** comments<br /> ** instructions<br /> ** introduction<br /> ** popular searches<br /> ** quick tips<br /> ** related articles<br /> ** required tools<br /> ** summary<br /> ** title<br /> ** useful links<br /> * eHow | How to Videos, Articles &amp; More - Discover the expert in you. | eHow.com<br /> ** http://www.ehow.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** contributor<br /> ** instructions - pictures<br /> ** instructions<br /> ** introduction<br /> ** last updated<br /> ** references<br /> ** related ads<br /> ** related articles<br /> ** related searches<br /> ** resources<br /> ** things you'll need<br /> ** tips &amp; warnings<br /> ** title<br /> ** you may also like<br /> * HowToForge - Linux Howtos and Tutorials<br /> ** http://www.howtoforge.com/<br /> ** author<br /> ** category<br /> ** date &amp; time of publication<br /> ** instructions - pictures<br /> ** instructions<br /> ** introduction<br /> ** license<br /> ** links<br /> ** title<br /> * How-To Geek - Computer Help from yout Griend How-To Geek<br /> ** http://www.howtogeek.com/<br /> ** attachment<br /> ** author<br /> ** comments<br /> ** date of publication<br /> ** instructions - pictures<br /> ** instructions<br /> ** introduction<br /> ** title<br /> * How To - Tips for your phone, tablet, computer, home theater and the Web - CNET<br /> ** http://howto.cnet.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** date &amp; time of publication<br /> ** instructions - pictures<br /> ** instructions - video<br /> ** instructions<br /> ** introduction<br /> ** secondary title<br /> ** summary<br /> ** tags<br /> ** title<br /> * Instructables - Make, How to, and DIY<br /> ** http://www.instructables.com/<br /> ** attachment<br /> ** author<br /> ** comments<br /> ** instructions<br /> ** instructions - pictures<br /> ** introduction<br /> ** picture<br /> ** rating<br /> ** summary<br /> ** tags<br /> ** title<br /> ** you will need<br /> * How to Clean Stuff<br /> ** http://www.howtocleanstuff.net/<br /> ** additional tips and advice<br /> ** category<br /> ** comments<br /> ** instructions<br /> ** introduction<br /> ** picture<br /> ** related posts<br /> ** tags<br /> ** title<br /> ** you will need<br /> * Study skills articles and study tips, improve study habits, teaching tips<br /> ** http://www.how-to-study.com/<br /> ** category<br /> ** instructions<br /> ** introduction<br /> * Home Improvement and Remodeling: This Old House<br /> ** http://www.doityourself.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** instructions<br /> ** introduction<br /> ** picture<br /> ** related how-to's<br /> ** related links<br /> ** related products<br /> ** title<br /> * Repair-Home - Kitchen, Bathroom, Window, HVAC and Other Home Improvements<br /> ** http://www.repair-home.com/<br /> ** category<br /> ** instructions<br /> ** introduction<br /> ** materials<br /> ** title</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-examples&diff=46242 2012-05-11T18:44:48Z

<p>Juraj: </p> <hr /> <div>* CodeProject® - Your Development Resource<br /> ** http://www.codeproject.com/<br /> ** article type<br /> ** attachment<br /> ** author<br /> ** category<br /> ** comments<br /> ** date of publication<br /> ** instructions<br /> ** introdution<br /> ** license<br /> ** number of bookmarks<br /> ** number of donwloads<br /> ** number pf views<br /> ** picture<br /> ** rating<br /> ** title<br /> ** vote<br /> * Stack Overflow<br /> ** http://stackoverflow.com/<br /> ** answer<br /> ** author of answer<br /> ** author of question<br /> ** feedback<br /> ** last update<br /> ** number of votes<br /> ** number of answers<br /> ** number of views<br /> ** question<br /> ** reputation score<br /> ** summary<br /> ** tags<br /> ** title<br /> * About.com: Need. Know. Accomplish.<br /> ** http://www.about.com/<br /> ** author<br /> ** category<br /> ** components<br /> ** instructions - pictures<br /> ** instructions<br /> ** introdution<br /> ** related articles<br /> ** secondary title<br /> ** tags<br /> ** things you'll need<br /> ** title<br /> * wikiHow - The How-to Manual That You Can Edit<br /> ** http://www.wikihow.com/<br /> ** authors<br /> ** category<br /> ** feedback<br /> ** instructions<br /> ** introduction<br /> ** last edited<br /> ** number of views<br /> ** related articles<br /> ** sources and citations<br /> ** tips<br /> ** title<br /> ** warnings<br /> * Wonder How To » How To Videos &amp;amp; How-To Articles<br /> ** http://www.wonderhowto.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** date of last edit<br /> ** date of publications<br /> ** instructions - pictures<br /> ** instructions - video<br /> ** instructions<br /> ** introdution<br /> ** number of views<br /> ** picture<br /> ** related articles<br /> ** related videos<br /> ** tags<br /> ** title<br /> ** video length<br /> * How To Do Things » How To Articles &amp; How To Videos<br /> ** http://www.howtodothings.com/<br /> ** author<br /> ** category<br /> ** caution<br /> ** comments<br /> ** instructions<br /> ** introdution<br /> ** popular searches<br /> ** quick tips<br /> ** related articles<br /> ** required tools<br /> ** summary<br /> ** title<br /> ** useful links<br /> * eHow | How to Videos, Articles &amp; More - Discover the expert in you. | eHow.com<br /> ** http://www.ehow.com/<br /> ** author<br /> ** category<br /> ** comments<br /> ** contributor<br /> ** instructions - pictures<br /> ** instructions<br /> ** introdution<br /> ** last updated<br /> ** references<br /> ** related ads<br /> ** related articles<br /> ** related searches<br /> ** resources<br /> ** things you'll need<br /> ** tips &amp; warnings<br /> ** title<br /> ** you may also like</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-examples&diff=46241 2012-05-11T18:31:10Z

<p>Juraj: </p> <hr /> <div>* CodeProject® - Your Development Resource<br /> ** http://www.codeproject.com/<br /> ** article type<br /> ** attachment<br /> ** author<br /> ** category<br /> ** comments<br /> ** date of publication<br /> ** instructions<br /> ** introdution<br /> ** license<br /> ** number of bookmarks<br /> ** number of donwloads<br /> ** number pf views<br /> ** picture<br /> ** rating<br /> ** title<br /> ** vote<br /> * Stack Overflow<br /> ** http://stackoverflow.com/<br /> ** answer<br /> ** author of answer<br /> ** author of question<br /> ** feedback<br /> ** last update<br /> ** number of votes<br /> ** number of answers<br /> ** number of views<br /> ** question<br /> ** reputation score<br /> ** summary<br /> ** tags<br /> ** title<br /> * About.com: Need. Know. Accomplish.<br /> ** http://www.about.com/<br /> ** author<br /> ** category<br /> ** components<br /> ** instruction pictures<br /> ** instructions<br /> ** introdution<br /> ** related articles<br /> ** secondary title<br /> ** tags<br /> ** things you'll need<br /> ** title<br /> * wikiHow - The How-to Manual That You Can Edit<br /> ** http://www.wikihow.com/<br /> ** authors<br /> ** category<br /> ** feedback<br /> ** instructions<br /> ** introduction<br /> ** last edited<br /> ** number of views<br /> ** related articles<br /> ** sources and citations<br /> ** tips<br /> ** title<br /> ** warnings<br /> * WonderHowTo<br /> ** http://www.wonderhowto.com/<br /> * HowToDoThings.com<br /> ** http://www.howtodothings.com/<br /> * eHow - Discover the expert in you<br /> ** http://www.ehow.com/</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-formats&diff=46220 2012-05-08T12:33:31Z

<p>Juraj: </p> <hr /> <div>* The Code Project<br /> ** http://www.codeproject.com/<br /> * stackowerflow<br /> ** http://stackoverflow.com/<br /> * About<br /> ** http://www.about.com/<br /> * wikihow<br /> ** http://www.wikihow.com/<br /> * JavaWorld - Solutions for java developers<br /> ** http://www.javaworld.com/<br /> * HTML.net<br /> ** http://www.html.net/<br /> * WonderHowTo<br /> ** http://www.wonderhowto.com/<br /> * HowToDoThings.com<br /> ** http://www.howtodothings.com/<br /> * eHow - Discover the expert in you<br /> ** http://www.ehow.com/</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=46219 2012-05-08T12:31:55Z

<p>Juraj: /* how-to proposal */</p> <hr /> <div>&lt;entry-title&gt;how-to brainstorming&lt;/entry-title&gt;<br /> <br /> This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.<br /> <br /> Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.<br /> <br /> * [[how-to-examples]]<br /> * [[how-to-formats]]<br /> <br /> == problem statement ==<br /> 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.<br /> <br /> == how-to proposal ==<br /> possible schema of how-to:<br /> <br /> * '''howto''' - main class<br /> ** problem - problem which the solution solve. <br /> ** category - domain or category of problem (IT, horticulture)<br /> ** summary<br /> ** equipment - working tools and working conditions (hammer, brush tool, some kind of IDE...)<br /> ** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct<br /> ** duration - time duration, used with microformat hCalendar<br /> ** price<br /> ** instructions - steps to solve problem<br /> ** warning<br /> ** tip<br /> ** author - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> == comments ==<br /> <br /> I think that better property name for working tools and conditions will be '''equipments''' -- [[User:Juraj|Juraj Sivak]]<br /> <br /> == see also ==<br /> * [[how-to]]<br /> * [[how-to-examples]]<br /> * [[how-to-formats]]</div>

Juraj https://microformats.org/wiki/index.php?title=exploratory-discussions&diff=46071 2012-04-19T12:54:07Z

<p>Juraj: /* education related */</p> <hr /> <div>&lt;entry-title&gt;Exploratory Discussions&lt;/entry-title&gt;<br /> <br /> Per the microformats [[process]]: research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br /> <br /> Sort each section alphabetically. Group similar efforts.<br /> <br /> ==active==<br /> '''New: [[microformats 2]]''' has sufficiently stabilized to start using on public web pages and developing parsers and applications. Current exploratory microformats should switch to the microformats-2 syntax for further development.<br /> <br /> The following exploratory discussions are being actively pursued, generally, edited in the last month, and/or being utilized/experimented with by multiple sites in the wild.<br /> <br /> * [[activity-streams]]<br /> * [[citation]]: [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], [[citation-strawman-01|h3988 proposal]] and [[citation-faq|citation FAQ]]<br /> * [[comment]] ([[comment-problem|comment problem]], [[comment-examples|comment examples]], [[comments-formats|comment formats]], and [[comment-brainstorming|comment brainstorming]]{{NewMarker}} (Some stuff needs to be extracted from [[comments-formats]], [[hcomment]] and [[mfcomment]]))<br /> * figures [[figure]], [[figure-examples|figure examples]], [[figure-formats]], [[figure-brainstorming|figure brainstorming]]<br /> * [[group]]: [[group-examples|group examples]], [[group-formats]], [[group-brainstorming|group brainstorming]] <br /> * listing / hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br /> ** based on listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br /> * measures and measurement units [[measure]], [[measure-examples]], [[measure-formats]]<br /> * [[mfo]]: [[mfo-examples]]<br /> * [[page]] - what does a page represent?<br /> * [[product]] - [[product-examples]], [[product-formats]], [[product-brainstorming]].<br /> * [[project|project]]{{NewMarker}}, [[project-examples|project examples]]{{NewMarker}}, [[project-formats|project formats]]{{NewMarker}}, [[project-brainstorming|project brainstorming]]{{NewMarker}}<br /> * [[recipe]] [[recipe-examples|recipe examples]], [[recipe-formats]], [[recipe-brainstorming]]<br /> * [[rel-shortlink]] {{NewMarker}}<br /> * [[representative-hcard]] - see also [[uid]]<br /> <br /> === media related ===<br /> Media related efforts are very active in the microformats community and thus have been grouped here for convenience<br /> * [[xrate]] {{NewMarker}} - marking explicit content<br /> * [[audio-info]] ([[audio-info-examples|examples]], [[audio-info-formats|formats]], [[audio-info-brainstorming|brainstorming]], [[audio-info-proposal|proposal]], [[audio-info-issues|issues]], [[haudio|specification]]{{NewMarker}}) - Marking up information and metadata related to audio (speech, music, and sound in general).<br /> ** music [[music-examples|music examples]]<br /> * audio-album (see [[audio-info]] pages for examples, formats, brainstorming. [[audio-album-proposal]], [[audio-album-issues]]) - Marking up information and metadata related to audio albums/collections.<br /> * broadcast: Internet Radio &amp; TV: [[broadcast-examples]], [[broadcast-brainstorming]]<br /> * [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]], [[media-info-proposal| media-info Proposal]])<br /> * photo note [[photo-note-examples|photo note examples]]<br /> * video-info ([[video-info-examples|examples]], [[video-info-formats|formats]], [[video-info-brainstorming|brainstorming]], [[video-info-proposal|proposal]], [[video-info-issues|issues]]) - Marking up information and metadata related to video (video clips, movies, television, and video multimedia presentation in general).<br /> <br /> == other ==<br /> The following explorations are fairly inactive, though they may just be waiting for folks with sufficient interest and use cases to help further their development. Some of them could probably be consolidated, or even rejected with suggestions of re-using existing microformats.<br /> <br /> * [[alternates]] ([[alternates-examples|alternates examples]], [[alternates-formats]], [[alternates-brainstorming|alternates brainstorming]])<br /> *[[attention]]<br /> * book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br /> * chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br /> * code [[code-examples|code examples]], [[code-formats]], [[code-brainstorming|code brainstorming]]<br /> * [[collection-description|collection description]] - for describing collections in libraries <br /> * [[definition-examples]]<br /> * [[depend-examples]]: examples of dependency graphs, especially as they relate to software <br /> * [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-formats]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) <br /> * directions [[directions-examples|directions examples]] <br /> * [[downloads]] [[downloads-examples|downloads examples]], [[downloads-formats|downloads formats]], [[downloads-brainstorming|downloads brainstorming]] <br /> * [[error-message]] [[error-message-examples|error message examples]], [[error-message-formats]], [[error-message-brainstorming|error message brainstorming]]<br /> * file-format ([[file-format-examples|examples]], formats, brainstorming) - for the mark-up of file format information (size, type, codecs, bitrate, etc.) - should this be merged with [[downloads]] ?<br /> * forms [[forms-examples|forms examples]]<br /> * genealogy [[genealogy-examples]], [[genealogy-formats|genealogy formats]]<br /> * grouping ([[grouping-examples|examples]], [[grouping-formats|formats]], [[grouping-brainstorming|brainstorming]], [[grouping-proposal|proposal]]) - Metadata markup of items that should be grouped together. <br /> * hash [[hash-examples|hash examples]] (see also [[downloads]])<br /> * items [[items-examples|items examples]], [[items-formats]], [[items-brainstorming|items brainstorming]]<br /> * [[journal-brainstorming]]<br /> * last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br /> * metalink [[metalink-examples|metalink examples]] <br /> * [[operating-hours]]: [[operating-hours-examples]] ..of stores, restaurants, etc.<br /> * [[page-summary]] [[page-summary-examples]], [[page-summary-formats]]<br /> * [[payment]]<br /> * [[question-answer]], [[question-answer-examples]], [[question-answer-formats]], [[question-answer-brainstorming]] <br /> * requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br /> * [[rest-examples|REST examples]] (see also [[rest]])<br /> * search results [[search-results-example|search results example]]<br /> * [[species]] - for the marking up of the scientific names of living things: [[species-examples]], [[species-formats]], [[species-brainstorming]]<br /> * table [[table-examples|examples]]<br /> * transit table [[transit-table-examples|transit table examples]]<br /> * [[widget]], [[widget-examples|widget examples]], [[widget-formats]], [[widget-brainstorming|widget brainstorming]]<br /> * [[wiki-formats|wiki formats]]<br /> * work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]]<br /> * [[xpn-examples]] - proposal to extend (or replicate) XFN for business (or professional - hence X'''P'''N) relationships <br /> * [[wa-page-view-examples]] - proposal for declaring web analytics page view variables in HTML<br /> <br /> === blogging related ===<br /> * blog description [[blog-description-examples|blog description examples]]<br /> * blog info [[blog-info-examples|blog info examples]]<br /> * distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-examples|distributed conversation examples]], [[distributed-conversation-formats|distributed conversation formats]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]]<br /> * tagspeak [[tagspeak-examples|tagspeak examples]]<br /> * tagcloud [[tagcloud-examples|tagcloud examples]], [[tagcloud-formats]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br /> <br /> === education related ===<br /> * higher education academic information<br /> ** [[hied-course-examples]], [[hied-course-formats]], [[hied-course-brainstorming]] - an academic course activity<br /> ** [[course-catalog]]; [[course-catalog-examples]] <br /> * learning ([[learning-examples|examples]], [[learning-formats|formats]], [[learning-brainstorming|brainstorming]], [[learning-people|people]], [[learning-proposal|proposal]], [[learning-issues|issues]]) - a microformat for microlearning<br /> * howto {{NewMarker}} [[how-to-examples]], [[how-to-formats]], [[how-to-brainstorming]] - microformat for authors and publishers to markup solutions to common problems<br /> <br /> === productivity related ===<br /> * [[task]] effort, [[task-examples|task examples]], [[task-formats|task formats]], [[task-brainstorming|task brainstorming]], and [[task-faq|task FAQ]]<br /> * [[to-do-examples]]<br /> * meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br /> ** meetings usually aren't very productive, yet, hopefully if meeting minutes are captured, meetings aren't a complete waste of time.<br /> <br /> === commerce products listings related ===<br /> * bank account [[bankaccount-brainstorming]], [[bankaccount-examples]]<br /> * [[currency]]; [[currency-examples]]; [[currency-formats]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]<br /> * job listing [[job-listing-examples|job listing examples]], [[job-listing-formats]], [[job-listing-brainstorming|job listing brainstorming]]<br /> * receipt ([[receipt-examples|examples]], [[receipt-formats|formats]], [[receipt-brainstorming|brainstorming]], [[receipt-proposal|proposal]]) - Marking up information and metadata related to purchase receipts.<br /> * [[wishlist]], [[wishlist-examples]]<br /> * [[hService_Proposal|proposal for selling commercial services]]<br /> <br /> == completed ==<br /> The following exploratory discussions resulted in a microformat.<br /> <br /> * blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br /> * directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (yielded the [[rel-directory]] microformat)<br /> * location [[location-examples]], [[location-formats|location formats]]. (see also [[adr]], [[geo]], [[hcard|hCard]])<br /> * resume [[resume-examples]], [[resume-formats|resume formats]], [[resume-brainstorming|resume brainstorming]] yielded the [[hresume|hResume]] draft.<br /> * review [[review-examples|review examples]], and [[review-formats|review formats]] yielded the [[hreview|hReview]] draft<br /> <br /> <br /> == solo pursuits ==<br /> The following are primarily pursued by a single individual and thus have not generated widespread interest in the community yet. In general, solo pursuits are discouraged. <br /> <br /> The goal of a format is to help human communication, the exchange of information between two people. Thus if only one community member is really interested in pursuing it (enough to work on it in the community), it's not important as a format. While a list of contributors or supporters helps demonstrate some broader interest, it is still insufficient if a format is only really being worked on in the community by a single individual.<br /> <br /> * geo extensions ([[User:AndyMabbett|Andy Mabbett]])<br /> ** [[geo-elevation-examples]], [[geo-elevation-formats]] - extend geo for representing altitude <br /> ** [[geo-waypoint-examples]], [[geo-waypoint-formats]] - extend geo for representing routes and boundaries, using waypoints <br /> ** [[geo-extension-examples]], [[geo-extension-formats]], [[geo-extension-brainstorming]], [[geo-extension-strawman]] - extend geo for moons, other planets, etc.<br /> * [[off|OFF]]<br /> * [[hJoke]] a microformat used to delineate jokes/humor<br /> * [[itinerary]] ([[User:Lfbn|Luís Nóbrega]]), [[itinerary-examples]].<br /> <br /> == failed to follow process ==<br /> All too often it seems people propose a new microformat without following the [[process]] (most often not even reading apparently), nor creating the proper research pages first (and doing the research), nor sometimes even reading the [[introduction]] and [[how-to-play]] pages. Such proposals are relegated to this section to make it clear that they are worse than mere solo pursuits, they are (most of the time) solo pursuits by people who haven't even read the [[process]] page!<br /> <br /> In short, if you, the proposer, don't even bother to spend the time reading and attempting to use existing microformats (as the [[Main_Page]], [[introduction]], AND [[process]] page ask you to do so), how can you expect anyone else to bother to read and consider your proposal?<br /> <br /> * [[directory-proposal]]<br /> * [[realestate-propertydetail]], [[realestate-propertydetail-examples]], [[realestate-propertydetail-formats]], [[realestate-propertydetail brainstorming]]<br /> * show [[show-examples]], [[show-formats]], [[show-brainstorming|show brainstorming]]<br /> * showroll [[showroll-examples]], [[showroll-formats]], [[showroll-brainstorming]]<br /> * syllabus [[syllabus-examples]], [[syllabus-formats]], [[syllabus-brainstorming]]<br /> * [[web-page]]<br /> <br /> === did not read main page ===<br /> Even worse, proposals by people who apparently didn't even bother to read the rest of the [[Main_Page]]!<br /> These are proposals that failed to follow the process and were added by the author to the [[Main_Page]] where it explicitly says to follow the process (often right next to where they added the link to their brainstorm proposal).<br /> <br /> * [[hwiki|hWiki]]<br /> * [[rel-ecolabel]]</div>

Juraj https://microformats.org/wiki/index.php?title=exploratory-discussions&diff=46028 2012-04-17T02:00:15Z

<p>Juraj: /* education related */</p> <hr /> <div>&lt;entry-title&gt;Exploratory Discussions&lt;/entry-title&gt;<br /> <br /> Per the microformats [[process]]: research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br /> <br /> Sort each section alphabetically. Group similar efforts.<br /> <br /> ==active==<br /> '''New: [[microformats 2]]''' has sufficiently stabilized to start using on public web pages and developing parsers and applications. Current exploratory microformats should switch to the microformats-2 syntax for further development.<br /> <br /> The following exploratory discussions are being actively pursued, generally, edited in the last month, and/or being utilized/experimented with by multiple sites in the wild.<br /> <br /> * [[activity-streams]]<br /> * [[citation]]: [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], [[citation-strawman-01|h3988 proposal]] and [[citation-faq|citation FAQ]]<br /> * [[comment]] ([[comment-problem|comment problem]], [[comment-examples|comment examples]], [[comments-formats|comment formats]], and [[comment-brainstorming|comment brainstorming]]{{NewMarker}} (Some stuff needs to be extracted from [[comments-formats]], [[hcomment]] and [[mfcomment]]))<br /> * figures [[figure]], [[figure-examples|figure examples]], [[figure-formats]], [[figure-brainstorming|figure brainstorming]]<br /> * [[group]]: [[group-examples|group examples]], [[group-formats]], [[group-brainstorming|group brainstorming]] <br /> * listing / hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br /> ** based on listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br /> * measures and measurement units [[measure]], [[measure-examples]], [[measure-formats]]<br /> * [[mfo]]: [[mfo-examples]]<br /> * [[page]] - what does a page represent?<br /> * [[product]] - [[product-examples]], [[product-formats]], [[product-brainstorming]].<br /> * [[project|project]]{{NewMarker}}, [[project-examples|project examples]]{{NewMarker}}, [[project-formats|project formats]]{{NewMarker}}, [[project-brainstorming|project brainstorming]]{{NewMarker}}<br /> * [[recipe]] [[recipe-examples|recipe examples]], [[recipe-formats]], [[recipe-brainstorming]]<br /> * [[rel-shortlink]] {{NewMarker}}<br /> * [[representative-hcard]] - see also [[uid]]<br /> <br /> === media related ===<br /> Media related efforts are very active in the microformats community and thus have been grouped here for convenience<br /> * [[audio-info]] ([[audio-info-examples|examples]], [[audio-info-formats|formats]], [[audio-info-brainstorming|brainstorming]], [[audio-info-proposal|proposal]], [[audio-info-issues|issues]], [[haudio|specification]]{{NewMarker}}) - Marking up information and metadata related to audio (speech, music, and sound in general).<br /> ** music [[music-examples|music examples]]<br /> * audio-album (see [[audio-info]] pages for examples, formats, brainstorming. [[audio-album-proposal]], [[audio-album-issues]]) - Marking up information and metadata related to audio albums/collections.<br /> * broadcast: Internet Radio &amp; TV: [[broadcast-examples]], [[broadcast-brainstorming]]<br /> * [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]], [[media-info-proposal| media-info Proposal]])<br /> * photo note [[photo-note-examples|photo note examples]]<br /> * video-info ([[video-info-examples|examples]], [[video-info-formats|formats]], [[video-info-brainstorming|brainstorming]], [[video-info-proposal|proposal]], [[video-info-issues|issues]]) - Marking up information and metadata related to video (video clips, movies, television, and video multimedia presentation in general).<br /> <br /> == other ==<br /> The following explorations are fairly inactive, though they may just be waiting for folks with sufficient interest and use cases to help further their development. Some of them could probably be consolidated, or even rejected with suggestions of re-using existing microformats.<br /> <br /> * [[alternates]] ([[alternates-examples|alternates examples]], [[alternates-formats]], [[alternates-brainstorming|alternates brainstorming]])<br /> *[[attention]]<br /> * book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br /> * chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br /> * code [[code-examples|code examples]], [[code-formats]], [[code-brainstorming|code brainstorming]]<br /> * [[collection-description|collection description]] - for describing collections in libraries <br /> * [[definition-examples]]<br /> * [[depend-examples]]: examples of dependency graphs, especially as they relate to software <br /> * [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-formats]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) <br /> * directions [[directions-examples|directions examples]] <br /> * [[downloads]] [[downloads-examples|downloads examples]], [[downloads-formats|downloads formats]], [[downloads-brainstorming|downloads brainstorming]] <br /> * [[error-message]] [[error-message-examples|error message examples]], [[error-message-formats]], [[error-message-brainstorming|error message brainstorming]]<br /> * file-format ([[file-format-examples|examples]], formats, brainstorming) - for the mark-up of file format information (size, type, codecs, bitrate, etc.) - should this be merged with [[downloads]] ?<br /> * forms [[forms-examples|forms examples]]<br /> * genealogy [[genealogy-examples]], [[genealogy-formats|genealogy formats]]<br /> * grouping ([[grouping-examples|examples]], [[grouping-formats|formats]], [[grouping-brainstorming|brainstorming]], [[grouping-proposal|proposal]]) - Metadata markup of items that should be grouped together. <br /> * hash [[hash-examples|hash examples]] (see also [[downloads]])<br /> * items [[items-examples|items examples]], [[items-formats]], [[items-brainstorming|items brainstorming]]<br /> * [[journal-brainstorming]]<br /> * last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br /> * metalink [[metalink-examples|metalink examples]] <br /> * [[operating-hours]]: [[operating-hours-examples]] ..of stores, restaurants, etc.<br /> * [[page-summary]] [[page-summary-examples]], [[page-summary-formats]]<br /> * [[payment]]<br /> * [[question-answer]], [[question-answer-examples]], [[question-answer-formats]], [[question-answer-brainstorming]] <br /> * requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br /> * [[rest-examples|REST examples]] (see also [[rest]])<br /> * search results [[search-results-example|search results example]]<br /> * [[species]] - for the marking up of the scientific names of living things: [[species-examples]], [[species-formats]], [[species-brainstorming]]<br /> * table [[table-examples|examples]]<br /> * transit table [[transit-table-examples|transit table examples]]<br /> * [[widget]], [[widget-examples|widget examples]], [[widget-formats]], [[widget-brainstorming|widget brainstorming]]<br /> * [[wiki-formats|wiki formats]]<br /> * work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]]<br /> * [[xpn-examples]] - proposal to extend (or replicate) XFN for business (or professional - hence X'''P'''N) relationships <br /> * [[wa-page-view-examples]] - proposal for declaring web analytics page view variables in HTML<br /> <br /> === blogging related ===<br /> * blog description [[blog-description-examples|blog description examples]]<br /> * blog info [[blog-info-examples|blog info examples]]<br /> * distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-examples|distributed conversation examples]], [[distributed-conversation-formats|distributed conversation formats]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]]<br /> * tagspeak [[tagspeak-examples|tagspeak examples]]<br /> * tagcloud [[tagcloud-examples|tagcloud examples]], [[tagcloud-formats]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br /> <br /> === education related ===<br /> * higher education academic information<br /> ** [[hied-course-examples]], [[hied-course-formats]], [[hied-course-brainstorming]] - an academic course activity<br /> ** [[course-catalog]]; [[course-catalog-examples]] <br /> * learning ([[learning-examples|examples]], [[learning-formats|formats]], [[learning-brainstorming|brainstorming]], [[learning-people|people]], [[learning-proposal|proposal]], [[learning-issues|issues]]) - a microformat for microlearning<br /> * howto [[how-to-examples]], [[how-to-formats]], [[how-to-brainstorming]] - microformat for authors and publishers to markup solutions to common problems<br /> <br /> === productivity related ===<br /> * [[task]] effort, [[task-examples|task examples]], [[task-formats|task formats]], [[task-brainstorming|task brainstorming]], and [[task-faq|task FAQ]]<br /> * [[to-do-examples]]<br /> * meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br /> ** meetings usually aren't very productive, yet, hopefully if meeting minutes are captured, meetings aren't a complete waste of time.<br /> <br /> === commerce products listings related ===<br /> * bank account [[bankaccount-brainstorming]], [[bankaccount-examples]]<br /> * [[currency]]; [[currency-examples]]; [[currency-formats]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]<br /> * job listing [[job-listing-examples|job listing examples]], [[job-listing-formats]], [[job-listing-brainstorming|job listing brainstorming]]<br /> * receipt ([[receipt-examples|examples]], [[receipt-formats|formats]], [[receipt-brainstorming|brainstorming]], [[receipt-proposal|proposal]]) - Marking up information and metadata related to purchase receipts.<br /> * [[wishlist]], [[wishlist-examples]]<br /> * [[hService_Proposal|proposal for selling commercial services]]<br /> <br /> == completed ==<br /> The following exploratory discussions resulted in a microformat.<br /> <br /> * blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br /> * directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (yielded the [[rel-directory]] microformat)<br /> * location [[location-examples]], [[location-formats|location formats]]. (see also [[adr]], [[geo]], [[hcard|hCard]])<br /> * resume [[resume-examples]], [[resume-formats|resume formats]], [[resume-brainstorming|resume brainstorming]] yielded the [[hresume|hResume]] draft.<br /> * review [[review-examples|review examples]], and [[review-formats|review formats]] yielded the [[hreview|hReview]] draft<br /> <br /> <br /> == solo pursuits ==<br /> The following are primarily pursued by a single individual and thus have not generated widespread interest in the community yet. In general, solo pursuits are discouraged. <br /> <br /> The goal of a format is to help human communication, the exchange of information between two people. Thus if only one community member is really interested in pursuing it (enough to work on it in the community), it's not important as a format. While a list of contributors or supporters helps demonstrate some broader interest, it is still insufficient if a format is only really being worked on in the community by a single individual.<br /> <br /> * geo extensions ([[User:AndyMabbett|Andy Mabbett]])<br /> ** [[geo-elevation-examples]], [[geo-elevation-formats]] - extend geo for representing altitude <br /> ** [[geo-waypoint-examples]], [[geo-waypoint-formats]] - extend geo for representing routes and boundaries, using waypoints <br /> ** [[geo-extension-examples]], [[geo-extension-formats]], [[geo-extension-brainstorming]], [[geo-extension-strawman]] - extend geo for moons, other planets, etc.<br /> * [[off|OFF]]<br /> * [[hJoke]] a microformat used to delineate jokes/humor<br /> * [[itinerary]] ([[User:Lfbn|Luís Nóbrega]]), [[itinerary-examples]].<br /> <br /> == failed to follow process ==<br /> All too often it seems people propose a new microformat without following the [[process]] (most often not even reading apparently), nor creating the proper research pages first (and doing the research), nor sometimes even reading the [[introduction]] and [[how-to-play]] pages. Such proposals are relegated to this section to make it clear that they are worse than mere solo pursuits, they are (most of the time) solo pursuits by people who haven't even read the [[process]] page!<br /> <br /> In short, if you, the proposer, don't even bother to spend the time reading and attempting to use existing microformats (as the [[Main_Page]], [[introduction]], AND [[process]] page ask you to do so), how can you expect anyone else to bother to read and consider your proposal?<br /> <br /> * [[directory-proposal]]<br /> * [[realestate-propertydetail]], [[realestate-propertydetail-examples]], [[realestate-propertydetail-formats]], [[realestate-propertydetail brainstorming]]<br /> * show [[show-examples]], [[show-formats]], [[show-brainstorming|show brainstorming]]<br /> * showroll [[showroll-examples]], [[showroll-formats]], [[showroll-brainstorming]]<br /> * syllabus [[syllabus-examples]], [[syllabus-formats]], [[syllabus-brainstorming]]<br /> * [[web-page]]<br /> <br /> === did not read main page ===<br /> Even worse, proposals by people who apparently didn't even bother to read the rest of the [[Main_Page]]!<br /> These are proposals that failed to follow the process and were added by the author to the [[Main_Page]] where it explicitly says to follow the process (often right next to where they added the link to their brainstorm proposal).<br /> <br /> * [[hwiki|hWiki]]<br /> * [[rel-ecolabel]]</div>

Juraj https://microformats.org/wiki/index.php?title=exploratory-discussions&diff=46026 2012-04-17T01:48:37Z

<p>Juraj: /* education related */</p> <hr /> <div>&lt;entry-title&gt;Exploratory Discussions&lt;/entry-title&gt;<br /> <br /> Per the microformats [[process]]: research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br /> <br /> Sort each section alphabetically. Group similar efforts.<br /> <br /> ==active==<br /> '''New: [[microformats 2]]''' has sufficiently stabilized to start using on public web pages and developing parsers and applications. Current exploratory microformats should switch to the microformats-2 syntax for further development.<br /> <br /> The following exploratory discussions are being actively pursued, generally, edited in the last month, and/or being utilized/experimented with by multiple sites in the wild.<br /> <br /> * [[activity-streams]]<br /> * [[citation]]: [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], [[citation-strawman-01|h3988 proposal]] and [[citation-faq|citation FAQ]]<br /> * [[comment]] ([[comment-problem|comment problem]], [[comment-examples|comment examples]], [[comments-formats|comment formats]], and [[comment-brainstorming|comment brainstorming]]{{NewMarker}} (Some stuff needs to be extracted from [[comments-formats]], [[hcomment]] and [[mfcomment]]))<br /> * figures [[figure]], [[figure-examples|figure examples]], [[figure-formats]], [[figure-brainstorming|figure brainstorming]]<br /> * [[group]]: [[group-examples|group examples]], [[group-formats]], [[group-brainstorming|group brainstorming]] <br /> * listing / hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br /> ** based on listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br /> * measures and measurement units [[measure]], [[measure-examples]], [[measure-formats]]<br /> * [[mfo]]: [[mfo-examples]]<br /> * [[page]] - what does a page represent?<br /> * [[product]] - [[product-examples]], [[product-formats]], [[product-brainstorming]].<br /> * [[project|project]]{{NewMarker}}, [[project-examples|project examples]]{{NewMarker}}, [[project-formats|project formats]]{{NewMarker}}, [[project-brainstorming|project brainstorming]]{{NewMarker}}<br /> * [[recipe]] [[recipe-examples|recipe examples]], [[recipe-formats]], [[recipe-brainstorming]]<br /> * [[rel-shortlink]] {{NewMarker}}<br /> * [[representative-hcard]] - see also [[uid]]<br /> <br /> === media related ===<br /> Media related efforts are very active in the microformats community and thus have been grouped here for convenience<br /> * [[audio-info]] ([[audio-info-examples|examples]], [[audio-info-formats|formats]], [[audio-info-brainstorming|brainstorming]], [[audio-info-proposal|proposal]], [[audio-info-issues|issues]], [[haudio|specification]]{{NewMarker}}) - Marking up information and metadata related to audio (speech, music, and sound in general).<br /> ** music [[music-examples|music examples]]<br /> * audio-album (see [[audio-info]] pages for examples, formats, brainstorming. [[audio-album-proposal]], [[audio-album-issues]]) - Marking up information and metadata related to audio albums/collections.<br /> * broadcast: Internet Radio &amp; TV: [[broadcast-examples]], [[broadcast-brainstorming]]<br /> * [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]], [[media-info-proposal| media-info Proposal]])<br /> * photo note [[photo-note-examples|photo note examples]]<br /> * video-info ([[video-info-examples|examples]], [[video-info-formats|formats]], [[video-info-brainstorming|brainstorming]], [[video-info-proposal|proposal]], [[video-info-issues|issues]]) - Marking up information and metadata related to video (video clips, movies, television, and video multimedia presentation in general).<br /> <br /> == other ==<br /> The following explorations are fairly inactive, though they may just be waiting for folks with sufficient interest and use cases to help further their development. Some of them could probably be consolidated, or even rejected with suggestions of re-using existing microformats.<br /> <br /> * [[alternates]] ([[alternates-examples|alternates examples]], [[alternates-formats]], [[alternates-brainstorming|alternates brainstorming]])<br /> *[[attention]]<br /> * book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br /> * chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br /> * code [[code-examples|code examples]], [[code-formats]], [[code-brainstorming|code brainstorming]]<br /> * [[collection-description|collection description]] - for describing collections in libraries <br /> * [[definition-examples]]<br /> * [[depend-examples]]: examples of dependency graphs, especially as they relate to software <br /> * [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-formats]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) <br /> * directions [[directions-examples|directions examples]] <br /> * [[downloads]] [[downloads-examples|downloads examples]], [[downloads-formats|downloads formats]], [[downloads-brainstorming|downloads brainstorming]] <br /> * [[error-message]] [[error-message-examples|error message examples]], [[error-message-formats]], [[error-message-brainstorming|error message brainstorming]]<br /> * file-format ([[file-format-examples|examples]], formats, brainstorming) - for the mark-up of file format information (size, type, codecs, bitrate, etc.) - should this be merged with [[downloads]] ?<br /> * forms [[forms-examples|forms examples]]<br /> * genealogy [[genealogy-examples]], [[genealogy-formats|genealogy formats]]<br /> * grouping ([[grouping-examples|examples]], [[grouping-formats|formats]], [[grouping-brainstorming|brainstorming]], [[grouping-proposal|proposal]]) - Metadata markup of items that should be grouped together. <br /> * hash [[hash-examples|hash examples]] (see also [[downloads]])<br /> * items [[items-examples|items examples]], [[items-formats]], [[items-brainstorming|items brainstorming]]<br /> * [[journal-brainstorming]]<br /> * last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br /> * metalink [[metalink-examples|metalink examples]] <br /> * [[operating-hours]]: [[operating-hours-examples]] ..of stores, restaurants, etc.<br /> * [[page-summary]] [[page-summary-examples]], [[page-summary-formats]]<br /> * [[payment]]<br /> * [[question-answer]], [[question-answer-examples]], [[question-answer-formats]], [[question-answer-brainstorming]] <br /> * requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br /> * [[rest-examples|REST examples]] (see also [[rest]])<br /> * search results [[search-results-example|search results example]]<br /> * [[species]] - for the marking up of the scientific names of living things: [[species-examples]], [[species-formats]], [[species-brainstorming]]<br /> * table [[table-examples|examples]]<br /> * transit table [[transit-table-examples|transit table examples]]<br /> * [[widget]], [[widget-examples|widget examples]], [[widget-formats]], [[widget-brainstorming|widget brainstorming]]<br /> * [[wiki-formats|wiki formats]]<br /> * work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]]<br /> * [[xpn-examples]] - proposal to extend (or replicate) XFN for business (or professional - hence X'''P'''N) relationships <br /> * [[wa-page-view-examples]] - proposal for declaring web analytics page view variables in HTML<br /> <br /> === blogging related ===<br /> * blog description [[blog-description-examples|blog description examples]]<br /> * blog info [[blog-info-examples|blog info examples]]<br /> * distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-examples|distributed conversation examples]], [[distributed-conversation-formats|distributed conversation formats]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]]<br /> * tagspeak [[tagspeak-examples|tagspeak examples]]<br /> * tagcloud [[tagcloud-examples|tagcloud examples]], [[tagcloud-formats]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br /> <br /> === education related ===<br /> * higher education academic information<br /> ** [[hied-course-examples]], [[hied-course-formats]], [[hied-course-brainstorming]] - an academic course activity<br /> ** [[course-catalog]]; [[course-catalog-examples]] <br /> * learning ([[learning-examples|examples]], [[learning-formats|formats]], [[learning-brainstorming|brainstorming]], [[learning-people|people]], [[learning-proposal|proposal]], [[learning-issues|issues]]) - a microformat for microlearning<br /> * howto [[how-to-examples]], [[how-to-formats]], [[how-to-brainstorming]]<br /> <br /> === productivity related ===<br /> * [[task]] effort, [[task-examples|task examples]], [[task-formats|task formats]], [[task-brainstorming|task brainstorming]], and [[task-faq|task FAQ]]<br /> * [[to-do-examples]]<br /> * meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br /> ** meetings usually aren't very productive, yet, hopefully if meeting minutes are captured, meetings aren't a complete waste of time.<br /> <br /> === commerce products listings related ===<br /> * bank account [[bankaccount-brainstorming]], [[bankaccount-examples]]<br /> * [[currency]]; [[currency-examples]]; [[currency-formats]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]<br /> * job listing [[job-listing-examples|job listing examples]], [[job-listing-formats]], [[job-listing-brainstorming|job listing brainstorming]]<br /> * receipt ([[receipt-examples|examples]], [[receipt-formats|formats]], [[receipt-brainstorming|brainstorming]], [[receipt-proposal|proposal]]) - Marking up information and metadata related to purchase receipts.<br /> * [[wishlist]], [[wishlist-examples]]<br /> * [[hService_Proposal|proposal for selling commercial services]]<br /> <br /> == completed ==<br /> The following exploratory discussions resulted in a microformat.<br /> <br /> * blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br /> * directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (yielded the [[rel-directory]] microformat)<br /> * location [[location-examples]], [[location-formats|location formats]]. (see also [[adr]], [[geo]], [[hcard|hCard]])<br /> * resume [[resume-examples]], [[resume-formats|resume formats]], [[resume-brainstorming|resume brainstorming]] yielded the [[hresume|hResume]] draft.<br /> * review [[review-examples|review examples]], and [[review-formats|review formats]] yielded the [[hreview|hReview]] draft<br /> <br /> <br /> == solo pursuits ==<br /> The following are primarily pursued by a single individual and thus have not generated widespread interest in the community yet. In general, solo pursuits are discouraged. <br /> <br /> The goal of a format is to help human communication, the exchange of information between two people. Thus if only one community member is really interested in pursuing it (enough to work on it in the community), it's not important as a format. While a list of contributors or supporters helps demonstrate some broader interest, it is still insufficient if a format is only really being worked on in the community by a single individual.<br /> <br /> * geo extensions ([[User:AndyMabbett|Andy Mabbett]])<br /> ** [[geo-elevation-examples]], [[geo-elevation-formats]] - extend geo for representing altitude <br /> ** [[geo-waypoint-examples]], [[geo-waypoint-formats]] - extend geo for representing routes and boundaries, using waypoints <br /> ** [[geo-extension-examples]], [[geo-extension-formats]], [[geo-extension-brainstorming]], [[geo-extension-strawman]] - extend geo for moons, other planets, etc.<br /> * [[off|OFF]]<br /> * [[hJoke]] a microformat used to delineate jokes/humor<br /> * [[itinerary]] ([[User:Lfbn|Luís Nóbrega]]), [[itinerary-examples]].<br /> <br /> == failed to follow process ==<br /> All too often it seems people propose a new microformat without following the [[process]] (most often not even reading apparently), nor creating the proper research pages first (and doing the research), nor sometimes even reading the [[introduction]] and [[how-to-play]] pages. Such proposals are relegated to this section to make it clear that they are worse than mere solo pursuits, they are (most of the time) solo pursuits by people who haven't even read the [[process]] page!<br /> <br /> In short, if you, the proposer, don't even bother to spend the time reading and attempting to use existing microformats (as the [[Main_Page]], [[introduction]], AND [[process]] page ask you to do so), how can you expect anyone else to bother to read and consider your proposal?<br /> <br /> * [[directory-proposal]]<br /> * [[realestate-propertydetail]], [[realestate-propertydetail-examples]], [[realestate-propertydetail-formats]], [[realestate-propertydetail brainstorming]]<br /> * show [[show-examples]], [[show-formats]], [[show-brainstorming|show brainstorming]]<br /> * showroll [[showroll-examples]], [[showroll-formats]], [[showroll-brainstorming]]<br /> * syllabus [[syllabus-examples]], [[syllabus-formats]], [[syllabus-brainstorming]]<br /> * [[web-page]]<br /> <br /> === did not read main page ===<br /> Even worse, proposals by people who apparently didn't even bother to read the rest of the [[Main_Page]]!<br /> These are proposals that failed to follow the process and were added by the author to the [[Main_Page]] where it explicitly says to follow the process (often right next to where they added the link to their brainstorm proposal).<br /> <br /> * [[hwiki|hWiki]]<br /> * [[rel-ecolabel]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=46020 2012-04-16T23:58:09Z

<p>Juraj: /* how-to proposal */</p> <hr /> <div>&lt;entry-title&gt;how-to brainstorming&lt;/entry-title&gt;<br /> <br /> This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.<br /> <br /> Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.<br /> <br /> * [[how-to-examples]]<br /> * [[how-to-formats]]<br /> <br /> == problem statement ==<br /> 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.<br /> <br /> == how-to proposal ==<br /> possible schema of how-to:<br /> <br /> * '''howto''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''category''' - domain or category of problem (IT, horticulture)<br /> ** summary<br /> ** solution - element which content solution<br /> *** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)<br /> *** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct<br /> *** duration - time duration, used with microformat hCalendar<br /> *** '''instructions''' - steps to solve problem<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** warning<br /> ** tip<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> '''Bold''' elements should be required.<br /> <br /> == comments ==<br /> <br /> I think that better property name for working tools and conditions will be '''equipments''' -- [[User:Juraj|Juraj Sivak]]<br /> <br /> == see also ==<br /> * [[how-to]]<br /> * [[how-to-examples]]<br /> * [[how-to-formats]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-examples&diff=46007 2012-04-15T19:50:03Z

<p>Juraj: </p> <hr /> <div>* The Code Project<br /> ** http://www.codeproject.com/<br /> * stackowerflow<br /> ** http://stackoverflow.com/<br /> * About<br /> ** http://www.about.com/<br /> * wikihow<br /> ** http://www.wikihow.com/<br /> * JavaWorld - Solutions for java developers<br /> ** http://www.javaworld.com/<br /> * HTML.net<br /> ** http://www.html.net/<br /> * WonderHowTo<br /> ** http://www.wonderhowto.com/<br /> * HowToDoThings.com<br /> ** http://www.howtodothings.com/<br /> * eHow - Discover the expert in you<br /> ** http://www.ehow.com/</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-examples&diff=46006 2012-04-15T19:44:06Z

<p>Juraj: </p> <hr /> <div>* The Code Project<br /> ** http://www.codeproject.com/<br /> * stackowerflow<br /> ** http://stackoverflow.com/<br /> * About<br /> ** http://www.about.com/<br /> * wikihow<br /> ** http://www.wikihow.com/<br /> * JavaWorld - Solutions for java developers<br /> ** http://www.javaworld.com/<br /> * HTML.net<br /> ** http://www.html.net/<br /> * WonderHowTo<br /> ** http://www.wonderhowto.com/<br /> * HowToDoThings.com<br /> ** http://www.howtodothings.com/<br /> * eHow - Discover theexpert in you<br /> ** http://www.ehow.com/</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=46003 2012-04-14T21:31:05Z

<p>Juraj: /* how-to proposal */</p> <hr /> <div>&lt;entry-title&gt;how-to brainstorming&lt;/entry-title&gt;<br /> <br /> This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.<br /> <br /> Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.<br /> <br /> * [[how-to-examples]]<br /> * [[how-to-formats]]<br /> <br /> == problem statement ==<br /> 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.<br /> <br /> == how-to proposal ==<br /> possible schema of how-to:<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''category''' - domain or category of problem (IT, horticulture)<br /> ** summary<br /> ** solution - element which content solution<br /> *** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)<br /> *** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct<br /> *** duration - time duration, used with microformat hCalendar<br /> *** '''instructions''' - steps to solve problem<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** warning<br /> ** tip<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> '''Bold''' elements should be required.<br /> <br /> == comments ==<br /> <br /> I think that better property name for working tools and conditions will be '''equipments''' -- [[User:Juraj|Juraj Sivak]]<br /> <br /> == see also ==<br /> * [[how-to]]<br /> * [[how-to-examples]]<br /> * [[how-to-formats]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=46002 2012-04-14T21:27:17Z

<p>Juraj: /* how-to proposal */</p> <hr /> <div>&lt;entry-title&gt;how-to brainstorming&lt;/entry-title&gt;<br /> <br /> This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.<br /> <br /> Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.<br /> <br /> * [[how-to-examples]]<br /> * [[how-to-formats]]<br /> <br /> == problem statement ==<br /> 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.<br /> <br /> == how-to proposal ==<br /> possible schema of how-to:<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''category''' - domain or category of problem (IT, horticulture)<br /> ** solution - element which content solution<br /> *** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)<br /> *** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct<br /> *** duration - time duration, used with microformat hCalendar<br /> *** '''instructions''' - steps to solve problem<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** warning<br /> ** tip<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> '''Bold''' elements should be required.<br /> <br /> == comments ==<br /> <br /> I think that better property name for working tools and conditions will be '''equipments''' -- [[User:Juraj|Juraj Sivak]]<br /> <br /> == see also ==<br /> * [[how-to]]<br /> * [[how-to-examples]]<br /> * [[how-to-formats]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-examples&diff=46001 2012-04-14T21:09:13Z

<p>Juraj: </p> <hr /> <div>* The Code Project<br /> ** http://www.codeproject.com/<br /> * stackowerflow<br /> ** http://stackoverflow.com/<br /> * About<br /> ** http://www.about.com/<br /> * wikihow<br /> ** http://www.wikihow.com/<br /> * JavaWorld - Solutions for java developers<br /> ** http://www.javaworld.com/<br /> * HTML.net<br /> ** http://www.html.net/</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-formats&diff=46000 2012-04-14T20:46:19Z

<p>Juraj: New page: * The Code Project ** http://www.codeproject.com/ ** problem ** category ** solution *** tools *** instructions ** author ** published * stackowerflow ** http://stackoverflow.com/ ** faq *...</p> <hr /> <div>* The Code Project<br /> ** http://www.codeproject.com/<br /> ** problem<br /> ** category<br /> ** solution<br /> *** tools<br /> *** instructions<br /> ** author<br /> ** published<br /> * stackowerflow<br /> ** http://stackoverflow.com/<br /> ** faq<br /> * About<br /> ** http://www.about.com/<br /> ** problem<br /> ** solution<br /> ** author<br /> ** published<br /> * wikihow<br /> ** http://www.wikihow.com/<br /> ** problem<br /> ** category<br /> ** solution<br /> *** tools<br /> *** instructions<br /> ** author<br /> ** published</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-examples&diff=45999 2012-04-14T20:38:28Z

<p>Juraj: </p> <hr /> <div>* The Code Project<br /> ** http://www.codeproject.com/<br /> * stackowerflow<br /> ** http://stackoverflow.com/<br /> * About<br /> ** http://www.about.com/<br /> * wikihow<br /> ** http://www.wikihow.com/</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=45998 2012-04-14T18:14:36Z

<p>Juraj: </p> <hr /> <div>&lt;entry-title&gt;how-to brainstorming&lt;/entry-title&gt;<br /> <br /> This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.<br /> <br /> Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.<br /> <br /> * [[how-to-examples]]<br /> * [[how-to-formats]]<br /> <br /> == problem statement ==<br /> 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.<br /> <br /> == how-to proposal ==<br /> possible schema of how-to:<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''category''' - domain or category of problem (IT, horticulture)<br /> ** solution - element which content solution<br /> *** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)<br /> *** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct<br /> *** duration - time duration, used with microformat hCalendar<br /> *** '''instructions''' - steps to solve problem<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> '''Bold''' elements should be required.<br /> <br /> == comments ==<br /> <br /> I think that better property name for working tools and conditions will be '''equipments''' -- [[User:Juraj|Juraj Sivak]]<br /> <br /> == see also ==<br /> * [[how-to]]<br /> * [[how-to-examples]]<br /> * [[how-to-formats]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=45995 2012-04-14T17:36:24Z

<p>Juraj: /* comments */</p> <hr /> <div>&lt;entry-title&gt;how-to brainstorming&lt;/entry-title&gt;<br /> <br /> This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.<br /> <br /> Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.<br /> <br /> * [[how-to-examples]]<br /> * [[how-to-formats]]<br /> <br /> == problem statement ==<br /> 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. <br /> <br /> == how-to proposal ==<br /> After reviewing the web microformats.org, I decided to propose microformat for publishing troubleshooting. I called my microformat &quot;how-to&quot; and its schema is as follows:<br /> <br /> <br /> == possible schema of how-to ==<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''category''' - domain or category of problem (IT, horticulture)<br /> ** solution - element which content solution<br /> *** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)<br /> *** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct<br /> *** duration - time duration, used with microformat hCalendar<br /> *** '''instructions''' - steps to solve problem<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> '''Bold''' elements should be required.<br /> <br /> == comments ==<br /> <br /> I think that better property name for working tools and conditions will be '''equipments''' -- [[User:Juraj|Juraj Sivak]]<br /> <br /> == see also ==<br /> * [[how-to]]<br /> * [[how-to-examples]]<br /> * [[how-to-formats]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=45994 2012-04-14T17:32:05Z

<p>Juraj: /* possible schema of how-to */</p> <hr /> <div>&lt;entry-title&gt;how-to brainstorming&lt;/entry-title&gt;<br /> <br /> This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.<br /> <br /> Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.<br /> <br /> * [[how-to-examples]]<br /> * [[how-to-formats]]<br /> <br /> == problem statement ==<br /> 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. <br /> <br /> == how-to proposal ==<br /> After reviewing the web microformats.org, I decided to propose microformat for publishing troubleshooting. I called my microformat &quot;how-to&quot; and its schema is as follows:<br /> <br /> <br /> == possible schema of how-to ==<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''category''' - domain or category of problem (IT, horticulture)<br /> ** solution - element which content solution<br /> *** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)<br /> *** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct<br /> *** duration - time duration, used with microformat hCalendar<br /> *** '''instructions''' - steps to solve problem<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> '''Bold''' elements should be required.<br /> <br /> == comments ==<br /> <br /> == see also ==<br /> * [[how-to]]<br /> * [[how-to-examples]]<br /> * [[how-to-formats]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=45992 2012-04-14T11:13:08Z

<p>Juraj: /* possible schema of how-to */</p> <hr /> <div>&lt;entry-title&gt;how-to brainstorming&lt;/entry-title&gt;<br /> <br /> This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.<br /> <br /> Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.<br /> <br /> * [[how-to-examples]]<br /> * [[how-to-formats]]<br /> <br /> == problem statement ==<br /> 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. <br /> <br /> == how-to proposal ==<br /> After reviewing the web microformats.org, I decided to propose microformat for publishing troubleshooting. I called my microformat &quot;how-to&quot; and its schema is as follows:<br /> <br /> <br /> == possible schema of how-to ==<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''category''' - domain or category of problem (IT, horticulture)<br /> ** solution - element which content solution<br /> *** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)<br /> *** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct<br /> *** duration - time duration, used with microformat hCalendar<br /> *** '''instructions''' - steps to solve problem<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> '''Bold''' elements should be required.<br /> <br /> == see also ==<br /> * [[how-to]]<br /> * [[how-to-examples]]<br /> * [[how-to-formats]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=45991 2012-04-14T11:05:03Z

<p>Juraj: /* how-to proposal */</p> <hr /> <div>&lt;entry-title&gt;how-to brainstorming&lt;/entry-title&gt;<br /> <br /> This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.<br /> <br /> Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.<br /> <br /> * [[how-to-examples]]<br /> * [[how-to-formats]]<br /> <br /> == problem statement ==<br /> 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. <br /> <br /> == how-to proposal ==<br /> After reviewing the web microformats.org, I decided to propose microformat for publishing troubleshooting. I called my microformat &quot;how-to&quot; and its schema is as follows:<br /> <br /> <br /> == possible schema of how-to ==<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''category''' - domain or category of problem (IT, horticulture)<br /> ** '''solution''' - element which content solution<br /> *** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)<br /> *** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct<br /> *** duration - time duration, used with microformat hCalendar<br /> *** '''instructions''' - steps to solve problem<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> *** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> '''Bold''' elements should be required.<br /> <br /> == see also ==<br /> * [[how-to]]<br /> * [[how-to-examples]]<br /> * [[how-to-formats]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=45990 2012-04-14T10:49:52Z

<p>Juraj: /* how-to proposal */</p> <hr /> <div>&lt;entry-title&gt;how-to brainstorming&lt;/entry-title&gt;<br /> <br /> This is a page for brainstorming proposals for a how-to microformat for authors and publishers to markup solutions to common problems.<br /> <br /> Per the microformats [[process]], the following pages need to be first created and documented, and then brainstorming should be based upon the research therein.<br /> <br /> * [[how-to-examples]]<br /> * [[how-to-formats]]<br /> <br /> == problem statement ==<br /> 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. <br /> <br /> == how-to proposal ==<br /> After reviewing the web microformats.org, I decided to propose microformat for publishing troubleshooting. I called my microformat &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''domain''' - domain of problem (IT, horticulture)<br /> ** '''solution''' - element which content solution<br /> *** tools - working tools and working conditions (hammer, brush tool, some kind of IDE...)<br /> *** components - parts needed for repair, modification or creation of something that is the subject of the problem, can be used with microformat hProduct<br /> *** duration - time duration, used with microformat hCalendar<br /> *** '''instructions''' - steps to solve problem<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> *** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> Bold elements should be required.<br /> <br /> == see also ==<br /> * [[how-to]]<br /> * [[how-to-examples]]<br /> * [[how-to-formats]]</div>

Juraj https://microformats.org/wiki/index.php?title=User:Juraj&diff=45941 2012-04-08T23:23:44Z

<p>Juraj: </p> <hr /> <div>Hi, my name is Juraj Sivak and I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. It should be my own idea. <br /> <br /> ----<br /> <br /> &lt;span class=&quot;hresume&quot;&gt;<br /> &lt;div class=&quot;vcard&quot;&gt;<br /> '''''Curriculum vitae'''''<br /> <br /> * '''Name:''' &lt;span class=&quot;fn n&quot;&gt;&lt;span class=&quot;given-name&quot;&gt;Juraj&lt;/span&gt; &lt;span class=&quot;family-name&quot;&gt;Sivák&lt;/span&gt;&lt;/span&gt;<br /> * '''Date of birth:''' &lt;span class=&quot;bday&quot; title=&quot;1986-09-13&quot;&gt;13th September 1986&lt;/span&gt;<br /> <br /> * '''Address:'''&lt;span class=&quot;adr&quot;&gt;<br /> ** &lt;span class=&quot;locality&quot;&gt;Kosice&lt;/span&gt;<br /> ** &lt;span class=&quot;country-name&quot;&gt;Slovakia&lt;/span&gt;&lt;/span&gt;<br /> * '''E-mail:''' &lt;span class=&quot;email&quot;&gt;juraj.sivak@student.tuke.sk&lt;/span&gt;<br /> * '''Web:''' &lt;span class=&quot;url&quot;&gt;[http://mikroformaty.wz.sk Sémantický web - Mikroformáty]&lt;/span&gt;<br /> &lt;/div&gt;<br /> <br /> * '''Education:'''&lt;span class=&quot;vcalendar&quot;&gt;<br /> ** &lt;span class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2006&quot;&gt;2006&lt;/span&gt;-&lt;span class=&quot;dtend&quot;title=&quot;2010&quot;&gt;2010&lt;/span&gt; &lt;span class=&quot;summary vcard&quot;&gt;&lt;span class=&quot;fn n org&quot;&gt;[http://www.fei.tuke.sk Technical University of Kosice, Faculty of Electrical Engineering and Computer Science, Department of Computer Science]&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> ** &lt;span class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2002&quot;&gt;2002&lt;/span&gt;-&lt;span class=&quot;dtend&quot; title=&quot;2006&quot;&gt;2006&lt;/span&gt; &lt;span class=&quot;summary vcard&quot;&gt;&lt;span class=&quot;fn n org&quot;&gt;[http://www.souhag.edu.sk Vocational School metallurgical Kosice-Saca, department of computer networking engineer]&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> <br /> * '''Additional training and study courses:'''<br /> ** &lt;span class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2011-07&quot;&gt;july 2011&lt;/span&gt; &lt;span class=&quot;summary vcard&quot;&gt;&lt;span class=&quot;fn n org&quot;&gt;[http://www.rweit-slovakia.com/web/cms/sk/594716/rwe-it-slovakia/kariera/summer-school RWE IT Summer School]&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> <br /> <br /> ----<br /> <br /> <br /> == how-to microformat ==<br /> <br /> 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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to'''<br /> ** '''problem'''<br /> ** '''domain'''<br /> ** '''solution'''<br /> *** difficulty<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions'''<br /> *** inset<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq<br /> *** question<br /> *** answer<br /> ** '''author'''<br /> ** published<br /> ** tag</div>

Juraj https://microformats.org/wiki/index.php?title=User:Juraj&diff=45940 2012-04-08T23:14:22Z

<p>Juraj: </p> <hr /> <div>Hi, my name is Juraj Sivak and I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. It should be my own idea. <br /> <br /> ----<br /> <br /> &lt;div class=&quot;hresume&quot;&gt;<br /> &lt;div class=&quot;vcard&quot;&gt;<br /> '''''Curriculum vitae'''''<br /> <br /> * '''Name:''' &lt;div class=&quot;fn n&quot;&gt;&lt;span class=&quot;given-name&quot;&gt;Juraj&lt;/span&gt; &lt;span class=&quot;family-name&quot;&gt;Sivák&lt;/span&gt;&lt;/div&gt;<br /> * '''Date of birth:''' &lt;span class=&quot;bday&quot; title=&quot;1986-09-13&quot;&gt;13th September 1986&lt;/span&gt;<br /> <br /> * '''Address:'''&lt;div class=&quot;adr&quot;&gt;<br /> ** &lt;span class=&quot;locality&quot;&gt;Košice&lt;/span&gt;<br /> ** &lt;span class=&quot;country-name&quot;&gt;Slovakia&lt;/span&gt;&lt;/span&gt;<br /> * '''E-mail:''' &lt;span class=&quot;email&quot;&gt;juraj.sivak@student.tuke.sk&lt;/span&gt;<br /> * '''Web:''' &lt;span class=&quot;url&quot;&gt;[http://mikroformaty.wz.sk Sémantický web - Mikroformáty]&lt;/span&gt;<br /> &lt;/div&gt;&lt;/div&gt;<br /> <br /> * '''Education:'''&lt;span div=&quot;vcalendar&quot;&gt;<br /> ** &lt;div class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2006&quot;&gt;2006&lt;/span&gt;-&lt;span class=&quot;dtend&quot;title=&quot;2010&quot;&gt;2010&lt;/span&gt; &lt;div class=&quot;summary vcard&quot;&gt;&lt;span class=&quot;fn n org&quot;&gt;[http://www.fei.tuke.sk Technical University of Kosice, Faculty of Electrical Engineering and Computer Science, Department of Computer Science]&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;<br /> ** &lt;div class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2002&quot;&gt;2002&lt;/span&gt;-&lt;span class=&quot;dtend&quot; title=&quot;2006&quot;&gt;2006&lt;/span&gt; &lt;div class=&quot;summary vcard&quot;&gt;&lt;span class=&quot;fn n org&quot;&gt;[http://www.souhag.edu.sk Vocational School metallurgical Kosice-Saca, department of computer networking engineer]&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;<br /> <br /> * '''Additional training and study courses:'''<br /> ** &lt;div class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2011-07&quot;&gt;july 2011&lt;/span&gt; &lt;div class=&quot;summary vcard&quot;&gt;&lt;span class=&quot;fn n org&quot;&gt;[http://www.rweit-slovakia.com/web/cms/sk/594716/rwe-it-slovakia/kariera/summer-school RWE IT Summer School]&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> <br /> ----<br /> <br /> <br /> == how-to microformat ==<br /> <br /> 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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to'''<br /> ** '''problem'''<br /> ** '''domain'''<br /> ** '''solution'''<br /> *** difficulty<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions'''<br /> *** inset<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq<br /> *** question<br /> *** answer<br /> ** '''author'''<br /> ** published<br /> ** tag</div>

Juraj https://microformats.org/wiki/index.php?title=User:Juraj&diff=45939 2012-04-08T14:40:40Z

<p>Juraj: </p> <hr /> <div>Hi, my name is Juraj Sivak and I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. It should be my own idea. <br /> <br /> ----<br /> <br /> &lt;span class=&quot;hresume&quot;&gt;<br /> &lt;span class=&quot;vcard&quot;&gt;<br /> '''''Curriculum vitae'''''<br /> <br /> * '''Name:''' &lt;span class=&quot;fn n&quot;&gt;&lt;span class=&quot;given-name&quot;&gt;Juraj&lt;/span&gt; &lt;span class=&quot;family-name&quot;&gt;Sivák&lt;/span&gt;&lt;/span&gt;<br /> * '''Date of birth:''' &lt;span class=&quot;bday&quot; title=&quot;1986-09-13&quot;&gt;13th September 1986&lt;/span&gt;<br /> <br /> * '''Address:'''&lt;span class=&quot;adr&quot;&gt;<br /> ** &lt;span class=&quot;locality&quot;&gt;Košice&lt;/span&gt;<br /> ** &lt;span class=&quot;country-name&quot;&gt;Slovakia&lt;/span&gt;&lt;/span&gt;<br /> * '''E-mail:''' &lt;span class=&quot;email&quot;&gt;juraj.sivak@student.tuke.sk&lt;/span&gt;<br /> * '''Web:''' &lt;span class=&quot;url&quot;&gt;[http://mikroformaty.wz.sk Sémantický web - Mikroformáty]&lt;/span&gt;<br /> &lt;/span&gt;<br /> <br /> * '''Education:'''&lt;span class=&quot;vcalendar&quot;&gt;<br /> ** &lt;span class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2006&quot;&gt;2006&lt;/span&gt;-&lt;span class=&quot;dtend&quot;title=&quot;2010&quot;&gt;2010&lt;/span&gt; &lt;span class=&quot;fn n org&quot;&gt;[http://www.fei.tuke.sk Technical University of Kosice, Faculty of Electrical Engineering and Computer Science, Department of Computer Science]&lt;/span&gt;&lt;/span&gt;<br /> ** &lt;span class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2002&quot;&gt;2002&lt;/span&gt;-&lt;span class=&quot;dtend&quot; title=&quot;2006&quot;&gt;2006&lt;/span&gt; &lt;span class=&quot;fn n org&quot;&gt;[http://www.souhag.edu.sk Vocational School metallurgical Kosice-Saca, department of computer networking engineer]&lt;/span&gt;&lt;/span&gt;<br /> <br /> * '''Additional training and study courses:'''<br /> ** &lt;span class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2011-07&quot;&gt;july 2011&lt;/span&gt; &lt;span class=&quot;summary vcard&quot;&gt;&lt;span class=&quot;fn n org&quot;&gt;[http://www.rweit-slovakia.com/web/cms/sk/594716/rwe-it-slovakia/kariera/summer-school RWE IT Summer School]&lt;/span&gt;&lt;/span&gt;<br /> &lt;/span&gt;<br /> &lt;/span&gt;<br /> <br /> <br /> ----<br /> <br /> <br /> == how-to microformat ==<br /> <br /> 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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to'''<br /> ** '''problem'''<br /> ** '''domain'''<br /> ** '''solution'''<br /> *** difficulty<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions'''<br /> *** inset<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq<br /> *** question<br /> *** answer<br /> ** '''author'''<br /> ** published<br /> ** tag</div>

Juraj https://microformats.org/wiki/index.php?title=User:Juraj&diff=45938 2012-04-08T14:39:35Z

<p>Juraj: </p> <hr /> <div>Hi, my name is Juraj Sivak and I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. It should be my own idea. <br /> <br /> ----<br /> <br /> &lt;span class=&quot;hresume&quot;&gt;<br /> &lt;span class=&quot;vcard&quot;&gt;<br /> '''''Curriculum vitae'''''<br /> <br /> * '''Name:''' &lt;span class=&quot;fn n&quot;&gt;&lt;span class=&quot;given-name&quot;&gt;Juraj&lt;/span&gt; &lt;span class=&quot;family-name&quot;&gt;Sivák&lt;/span&gt;&lt;/span&gt;<br /> * '''Date of birth:''' &lt;span class=&quot;bday&quot; title=&quot;1986-09-13&quot;&gt;13th September 1986&lt;/span&gt;<br /> <br /> * '''Address:'''&lt;span class=&quot;adr&quot;&gt;<br /> ** &lt;span class=&quot;locality&quot;&gt;Košice&lt;/span&gt;<br /> ** &lt;span class=&quot;country-name&quot;&gt;Slovakia&lt;/span&gt;&lt;/span&gt;<br /> * '''E-mail:''' &lt;span class=&quot;email&quot;&gt;juraj.sivak@student.tuke.sk&lt;/span&gt;<br /> * '''Web:''' &lt;span class=&quot;url&quot;&gt;[http://mikroformaty.wz.sk Sémantický web - Mikroformáty]&lt;/span&gt;<br /> &lt;/span&gt;<br /> <br /> * '''Education:'''&lt;span class=&quot;vcalendar&quot;&gt;<br /> ** &lt;span class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2006&quot;&gt;2006&lt;/span&gt;-&lt;span class=&quot;dtend&quot;title=&quot;2010&quot;&gt;2010&lt;/span&gt; &lt;span class=&quot;fn n org&quot;&gt;[http://www.fei.tuke.sk Technical University of Kosice, Faculty of Electrical Engineering and Computer Science, Department of Computer Science]&lt;/span&gt;&lt;/span&gt;<br /> ** &lt;span class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2002&quot;&gt;2002&lt;/span&gt;-&lt;span class=&quot;dtend&quot; title=&quot;2006&quot;&gt;2006&lt;/span&gt; &lt;span class=&quot;fn n org&quot;&gt;[http://www.souhag.edu.sk Vocational School metallurgical Kosice-Saca, department of computer networking engineer]&lt;/span&gt;&lt;/span&gt;<br /> <br /> * '''Additional training and study courses:'''<br /> ** &lt;span class=&quot;education vevent&quot;&gt;&lt;span class=&quot;dtstart&quot; title=&quot;2011-07&quot;&gt;july 2011&lt;/span&gt; &lt;span class=&quot;summary vcard&quot;&gt;&lt;span class=&quot;fn n org&quot;&gt;[http://www.rweit-slovakia.com/web/cms/sk/594716/rwe-it-slovakia/kariera/summer-school RWE IT Summer School]&lt;/span&gt;&lt;/span&gt;<br /> &lt;/span&gt;<br /> &lt;/span&gt;<br /> <br /> <br /> ----<br /> <br /> <br /> 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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to'''<br /> ** '''problem'''<br /> ** '''domain'''<br /> ** '''solution'''<br /> *** difficulty<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions'''<br /> *** inset<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq<br /> *** question<br /> *** answer<br /> ** '''author'''<br /> ** published<br /> ** tag</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-examples&diff=45901 2012-04-03T02:21:51Z

<p>Juraj: New page: * The Code Project ** http://stackoverflow.com/ * stackowerflow ** http://www.codeproject.com/ * About ** http://www.about.com/ * wikihow ** http://www.wikihow.com/</p> <hr /> <div>* The Code Project<br /> ** http://stackoverflow.com/<br /> * stackowerflow<br /> ** http://www.codeproject.com/<br /> * About<br /> ** http://www.about.com/<br /> * wikihow<br /> ** http://www.wikihow.com/</div>

Juraj https://microformats.org/wiki/index.php?title=irc-people&diff=45879 2012-03-30T22:40:45Z

<p>Juraj: </p> <hr /> <div>A list of [[irc|IRC]] regulars, sorted by nick, and their normal timezones (winter/summer).<br /> <br /> * {{irc user|Amodal1| amodal1|-0500/-0600}}<br /> * {{irc user|Adam Ballai|AdamBallai|-700/-700}}<br /> * {{irc user|Adam Craven|AdamCraven|+0000}}<br /> * {{irc user|Alenonimo|Alenonimo|-0300}}<br /> * {{irc user|Alexander Graf|AlexanderGraf|+0100}}<br /> * {{irc user|Axelator|ax|-0700}}<br /> * {{irc user|Tomasino|aloneone|-0500}}<br /> * {{irc user|AmanuelTewolde|Amanuel|-0500/-0400}}<br /> * {{irc user|Amette|amette|+1000}}<br /> * {{irc user|Amir Guindehi|AmirGuindehi|+1000}}<br /> * {{irc user|Andr3|andr3|+0000}}<br /> * {{irc user|Ajaswa|Andrew Jaswa|-0500}}<br /> * {{irc user|AndrewDisley|AndrewDisley|+0000}}<br /> * {{irc user|Andrii Ponomarov|Andrii|+0300}}<br /> * {{irc user|AngeloGladding|angelogladding|-0800/-0700}}<br /> * {{irc user|AnselHalliburton|anselxyz|-0800/-0700}}<br /> * {{irc user|Ashe Dryden|Ashe|-600}}<br /> * {{irc user|Atamido|Atamido|-0600/-0500}}<br /> * {{irc user|Barce|Barce|-0800/-0700}}<br /> * {{irc user|Azathoth|Florian Beer|+1000}}<br /> * {{irc user|Tyler Roehmholdt|Baristo|-0800/-0700}}<br /> * {{irc user|BarnabyWalters|barnabywalters|+0000}}<br /> * {{irc user|Belling|Belling|-0800/-0700}}<br /> * {{irc user|BenjaminCarlyle|BenjaminCarlyle|+1000}}<br /> * {{irc user|HenriBergius|bergie|+0200/+0300}}<br /> * {{irc user|Ben Ward|BenWard|-0800/-0700}}<br /> * {{irc user|BenWest|bewest|-0800/-0700}}<br /> * {{irc user|B.K._DeLong|bkdelong|-0500/-0400}}<br /> * {{irc user|Robert|blueace|+0100}}<br /> * {{irc user|Robert|blueace|+0100}}<br /> * {{irc user|BluesMoon|bluesmoon|+0530}}<br /> * {{irc user|BobChao|BobChao|+0800}}<br /> * {{irc user|Bob Jonkman|BobJonkman|-0500/-0400}}<br /> * {{irc user|Oli|boblet|+0900}}<br /> * {{irc user|Boneill|boneill|+0000}}<br /> * {{irc user|Brian|briansuda|+0000}}<br /> * {{irc user|TimT|bringo|-0800/-0700}}<br /> * {{irc user|Briski|Briski|+0000}}<br /> * {{irc user|BryanL|BryanL|-0500/-0400}}<br /> * {{irc user|BryanRieger|Bryan Rieger|+0000}}<br /> * {{irc user|Bug-E|Bug-E|+0200}}<br /> * {{irc user|CarlaHufstedler|carlamagpie|-0500/-0400}}<br /> * {{irc user|Colin_Barrett|cbarrett|-1000}}<br /> * {{irc user|Cognizance|Cognizance|-0800/-0700}}<br /> * {{irc user|ColinDDevroe|cdevroe|-0500/-0600}}<br /> * {{irc user|CoryGwin|corygwin|-0500/-0600}}<br /> * {{irc user|Cgriego|cgriego|-0600/-0500}}<br /> * {{irc user|Charlvn|Charl|+0200/+0200}}<br /> * {{irc user|CharlesRoper|charles_r|0000/+0100}}<br /> * {{irc user|ChiefRA|ChiefRA|+0200}}<br /> * {{irc user|Chris_Cressman|Chris Cressman|-0500/-0400}}<br /> * {{irc user|ChristopherStJohn|cks|-0600/-0500}}<br /> * {{irc user|JeremyBoggs|clioweb|-5000/-4000}}<br /> * {{irc user|Cloud|Cloud|+0000}}<br /> * {{irc user|Cruster|cruster|+0200}}<br /> * {{irc user|Csarven|csarven|-0500/-0400}}<br /> * {{irc user|ChrisBrentano|ctb|-0800/-0700}}<br /> * {{irc user|DanC|DanC|-0600/-0500}}<br /> * {{irc user|DanielBurka|DanielBurka|-0400}}<br /> * {{irc user|DanielJohnLewis|danieljohnlewis|0000}}<br /> * {{irc user|DannyAyers|danja|+0100/+0200}}<br /> * {{irc user|Dave Cardwell|davecardwell|+0000}}<br /> * {{irc user|DavidMead|DavidMead|-0400}}<br /> * {{irc user|DavidRussell|davidrussell|-0600/-0500}}<br /> * {{irc user|DBounds|Darren Bounds|-0500}}<br /> * {{irc user|Ddonat|David Gratton|-0800/-700}}<br /> * {{irc user|DenisDefreyne|ddfreyne|+0100/+0200}}<br /> * {{irc user|DeanEro|deanero|-0800/-0700}}<br /> * {{irc user|DeepText|Deep Text|-0800/-0700}}<br /> * {{irc user|DerrickPallas|DerrickPallas|-0800/-0700}}<br /> * {{irc user|DimitriGlazkov|dglazkov|-0600/-0500}}<br /> * {{irc user|DiegoBudny|DiegoBudny|&lt;small&gt;-unspecified-&lt;/small&gt;}}<br /> * {{irc user|DKerzman|DKerzman|-0600}}<br /> * {{irc user|Dan Kubb|dkubb|-0800/-0700}}<br /> * {{irc user|Dreamisle|dreamisle|-0500}}<br /> * {{irc user|DrErnie|DrErnie|-0800/-0700}}<br /> * {{irc user|DrewMcLellan|drewinthehead|+0000/+0100}}<br /> * {{irc user|DrewBell|droob|-0600/-0500}}<br /> * {{irc user|DimitriosZachariadis|dzach|+0200/+0300}}<br /> * {{irc user|Ed Summers|edsu|-0500/-0400}}<br /> * {{irc user|Enric|Enric|-0800/-0700}} (alt sp &quot;enric&quot;)<br /> * {{irc user|Evan|evanpro|-0500}}<br /> * {{irc user|Evan|e_s_p|-0500}}<br /> * {{irc user|Ket Majmudar|ethicaljunction|+0100}}<br /> * {{irc user|EdwardWelker|ewelker|-0500}}<br /> * {{irc user|ChrisMessina|factoryjoe|-0800/-0700}}<br /> * {{irc user|Fil|Fil|+0200}}<br /> * {{irc user|CFinke|Finke|-0700/-0600}}<br /> * {{irc user|MarkoMrdjenovic|friedcell|+0100/+0200}}<br /> * {{irc user|GarethR|garethr|+0000/+0100}}<br /> * {{irc user|GeorgeBrock|georgebrock|+0000/+0100}}<br /> * {{irc user|Grantbow|Grantbow|-0800/-0700}}<br /> * {{irc user|Griffin|Griffin|-0600/-0500}}<br /> * {{irc user|Guillaume Lebleu|glebleu|-0800}}<br /> * {{irc user|Aubergine10|Guy Fraser|+0100/+0000}}<br /> * {{irc user|HenrichPoehls|HenrichP|+0100}}<br /> * {{irc user|IanHickson|Hixie|-0800/-0700}}<br /> * {{irc user|Hlb|hlb|+0800-0700}}<br /> * {{irc user|EdwardOConnor|hober|-0800/-0700}}<br /> * {{irc user|Ichigo|ichigo|+1000}}<br /> * {{irc user|Alper|illustir|+0100}}<br /> * {{irc user|Inkbase|inkbase|-0800/-0700}}<br /> * {{irc user|IwaiMasaharu|iwaim|+0900}}<br /> * {{irc user|Izo|IZO|&lt;small&gt;-unspecified-&lt;/small&gt;}}<br /> * {{irc user|Jabz|Jabz|+0000}}<br /> * {{irc user|JamieKnight|JamieKnight|+1000/0000}}<br /> * {{irc user|JayMyers|jaymyers|-0600/-0500}}<br /> * {{irc user|JoeGregorio|jcgregorio|&lt;small&gt;-unspecified-&lt;/small&gt;}}<br /> * {{irc user|WizardIsHungry|jcw9|-0500/-0400}}<br /> * {{irc user|Adactio|Jeremy Keith|+0000}}<br /> * {{irc user|jrodgers|JesseRodgers|-0500}}<br /> * {{irc user|JasonK|jkridner|-0600/-0500}}<br /> * {{irc user|JeffMcNeill|jeffmcneill|-1000}}<br /> * {{irc user|jesudasjj|jesudas nadar|+0530}}<br /> * {{irc user|JimboJW|jimbojw|-0600/-0500}}<br /> * {{irc user|Jonathan_Arkell|jonnay|-0700/0600}}<br /> * {{irc user|JonathanMalek|JonathanMalek|-0800/-0700}}<br /> * {{irc user|JosephHolsten|josephholsten|-0600/-0500}}<br /> * {{irc user|JulianStahnke|julianstahnke|+0000}}<br /> * {{irc user|Juraj|jurajsivak|+0100}}<br /> * {{irc user|Kapowaz|kapowaz|+0000/+0100}}<br /> * {{irc user|Keri Henare|kerihenare|+1200}}<br /> * {{irc user|KevBurnsJr|kevburnsjr|-0800}}<br /> * [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)<br /> * {{irc user|RyanKing|kingryan|-0800/-0700}}<br /> ** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC<br /> * {{irc user|Lachlan Hunt|Lachy|+1000/+1100}}<br /> * {{irc user|Levitation|levitation[A]|+0200/+0300}}<br /> * {{irc user|Linmic|linmic|+0800-0700}}<br /> * {{irc user|Loiseau2nuit|Loiseau2nuit|+0100}} (Fr.)<br /> * {{irc user|MarkNg|madness|+0000/+0100}}<br /> * {{irc user|Mark Mansour|Mark Mansour|+1100}}<br /> * {{irc user|MarkNormanFrancis|Mark Norman Francis|+0000/+0100}}<br /> * {{irc user|Maddiin|Martin Czura|+0100}}<br /> * {{irc user|MattBowen|Matt Bowen|-0500/-0400}}<br /> * {{irc user|Groningen|Matthias Kluth|+0100}}<br /> * {{irc user|MattisManzel|Mattis Manzel|+0100/+0200}}<br /> * {{irc user|CiaranMc|McNulty|+0000/+0100}}<br /> * {{irc user|MicroAngelo|MicroAngelo|+0000/+0100}}<br /> * {{irc user|Mike|Michael McCracken(mmc)|-0800/-0700}}<br /> * {{irc user|MikeKaply|mkaply|-0600/-0500}}<br /> * {{irc user|SteveIvy|monkinetic/redmonk|-0700}}<br /> * {{irc user|MWTE|mwte|+0000/+0100}}<br /> * {{irc user|RobManson|nambor|+1000}}<br /> * {{irc user|Naterkane|Nater Kane|-0500}}<br /> * {{irc user|Nelix|nelix|+1000}}<br /> * {{irc user|Neuro|neuro|+0000/+0100}}<br /> * {{irc user|Niekie|niekie|+0100/+0200}}<br /> * {{irc user|NTollervey|ntoll|+0000/+0100}}<br /> * {{irc user|Pawlik|pawlik|+0100/+0200}}<br /> * {{irc user|Andy Pemberton|pembertona|-0500/-0400}}<br /> * {{irc user|Phae|Phae|+0000/+0100}}<br /> * {{irc user|pius|Pius Uzamere|+0500}}<br /> * {{irc user|PriitLaes|plaes|+0200/+0300}}<br /> * {{irc user|ChrisCasciano|pnhChris|-0500/-0400}}<br /> * {{irc user|Hugopeixoto|Politoed|+0000/+0100}}<br /> * {{irc user|PetarPopov|popov|-0800/-0700}}<br /> * {{irc user|Pfefferle|pfefferle|+0100/+0200}}<br /> * {{irc user|Lauren Scime|pseudowish|-0800/-700}}<br /> * {{irc user|DavidOsolkowski|qid|-0500}}<br /> * {{irc user|RCanine|RCanine|-0500/-0400}}<br /> * {{irc user|Remi|Remi|-0500/-0400}}<br /> * {{irc user|ZachCarter|riah|-0500/-0400}}<br /> * {{irc user|RobertBachmann|RobertBachmann|+0100/+0200}}<br /> ** Office hours: &lt;s&gt;Wednesday, 18:00-20:00 UTC&lt;/s&gt; (Currently no office hours}}<br /> * {{irc user|RobLinton|RobLinton|-0800/-0700}}<br /> * {{irc user|Ronnos|Ron Kok|+0000}}<br /> * {{irc user|SamJohnston|samj|+0100/+0200}}<br /> * {{irc user|SarahWorsham|sazbean|-0500/-0400}}<br /> * {{irc user|sebheath|sebheath|-0500/-0400}}<br /> * {{irc user|ScottNelle|snelle|-0500/-0400}}<br /> * {{irc user|ScottRozic|gravitas|-0500/+0100}}<br /> * {{irc user|Dana Benson|Snowden|-0800/-0700}}<br /> * {{irc user|SinDoc|SinDoc|+0100/+0200}}<br /> * {{irc user|Savell Martin|Savell|+0000/+0000}}<br /> * {{irc user|Smackman|Steve Farrell|-0800/-0700}}<br /> * {{irc user|SpikeUK|SpikeUK|+0000/+0100}}<br /> * {{irc user|Steve Ganz|SteveGanz|-0800/-0700}}<br /> * {{irc user|Stii|Stii|+0200 GMT}}<br /> * {{irc user|ReinierZ|surial|+0100 GMT}}<br /> * {{irc user|SuperPhly|SuperPhly|-600/-500}}<br /> * {{irc user|SyedSRahman|syedsrahman|+0530}}<br /> * &lt;span class=&quot;vcard&quot;&gt;&lt;span class=&quot;fn&quot;&gt;sym[[User:LynX|lynX]]&lt;/span&gt;&lt;/span&gt; or (better) [[User:LynX|lynX]] on [http://about.psyc.eu PSYC] (+0100}}<br /> * {{irc user|DavidLehn|taaz|-0500/-0400}}<br /> * {{irc user|Tantek|Tantek|-0800/-0700}}<br /> * {{irc user|tbmartin|tbmartin|-0800/-0700}}<br /> * {{irc user|themattharris|themattharris|-0800/-0700}}<br /> * {{irc user|Wojciech|theanxy|+0100/+0200}}<br /> * {{irc user|TheJbf|thejbf|+0100/+0200}}<br /> * {{irc user|Thomasknoll|thomasknoll|-0800}}<br /> * {{irc user|thuddwhirr|thuddwhirr|-0800/-0700}}<br /> * {{irc user|TobyInk|tobyink|+0000/+0100}}<br /> * {{irc user|Trovster|trovster|-0800/-0700}}<br /> * {{irc user|Vadania|vadania|-0600/-0700}}<br /> * {{irc user|Vant|vant|+0900}}<br /> * {{irc user|venkateswaran|vensilver|+5.30 GMT}}<br /> * {{irc user|Victor|victor|+0100/+0200}}<br /> * {{irc user|V-I-P|V-I-P|+0100/+0200}}<br /> * {{irc user|KrissWatt|VoodooChild|+0000/+0100}}<br /> * {{irc user|WebOrganics|weborganics|+0100}}<br /> * {{irc user|JacksonWilkinson|whafro|-0500/-0400}}<br /> * {{irc user|Richard Conyard|WhiskeyM|+0000}}<br /> * {{irc user|Veeliam|William Lawrence|-0800/-0700}}<br /> * {{irc user|StevenWoods|woodss|+0000 GMT}}<br /> * {{irc user|Ianloic|yakk|-0800/-0700}}<br /> <br /> <br /> Needs alpha sorting into the above list (please help!)<br /> * {{irc user|LarsStrojny|mastaYoda|+0100}}<br /> * {{irc user|Bui Thanh Hai|haibtdt}}<br /> * {{irc user|ZimbaTm|zimbatm|+0100}}<br /> * {{irc user|FoundAtion|Foundation|-0800}}<br /> * {{irc user|PJKix|pjkix|-0800/-700}}<br /> * {{irc user| ChrisBroadfoot|broady|+1000}}<br /> * {{irc user|Natalie Downe|NatBat|+0000}}<br /> * {{irc user|Dotjay|dotjay|+0000}}<br /> * {{irc user|PeterHellberg|zil|+0100}}<br /> * {{irc user|Kiryl Zhybul|zkv|+0400}}<br /> * {{irc user|ScottThorpe|Salve|-0800/-0700}}<br /> * {{irc user|Dane|imdane|-0600/-0500}}<br /> * {{irc user|ThomasLoertsch|tl|+0100/+0200}}<br /> * {{irc user|Francisco Bernardo|frantic0|+0100/+0200}}<br /> * {{irc user|Steven Osborn|steve918|-0700/-0800}}<br /> * {{irc user|Trodrigues|trodrigues|+0000}}<br /> * {{irc user|Epicurious|epicurious|+0000/+0100}}<br /> * {{irc user|GermanMartinez|German|-0500}}<br /> <br /> Inactive:<br /> * [[mfbot]] - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.</div>

Juraj https://microformats.org/wiki/index.php?title=User:Juraj&diff=45878 2012-03-30T22:40:34Z

<p>Juraj: </p> <hr /> <div>Hi, my name is Juraj Sivak and I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. It should be my own idea. <br /> <br /> 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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to'''<br /> ** '''problem'''<br /> ** '''domain'''<br /> ** '''solution'''<br /> *** difficulty<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions'''<br /> *** inset<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq<br /> *** question<br /> *** answer<br /> ** '''author'''<br /> ** published<br /> ** tag<br /> <br /> <br /> If you want to contact me, my e-mail is: juraj.sivak@student.tuke.sk</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=45825 2012-03-29T21:52:09Z

<p>Juraj: </p> <hr /> <div>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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''domain''' - domain of problem (IT, horticulture)<br /> ** '''solution''' - element which content solution<br /> *** difficulty - how difficult is solution for user (technical, equipment, duration, price)<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions''' - steps to solve problem<br /> *** inset - insets like images, videos, source codes<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> Bold elements should be required. [[User:Juraj|Juraj Sivak]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=45824 2012-03-29T21:49:29Z

<p>Juraj: </p> <hr /> <div>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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''domain''' - domain of problem (IT, horticulture)<br /> ** '''solution''' - element which content solution<br /> *** difficulty - how difficult is solution for user (technical, equipment, duration, price)<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions''' - steps to solve problem<br /> *** inset - insets like images, videos, source codes<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags<br /> <br /> Bold elements should be required.</div>

Juraj https://microformats.org/wiki/index.php?title=how_to&diff=45823 2012-03-29T21:47:25Z

<p>Juraj: how to moved to how-to-brainstorming</p> <hr /> <div>#REDIRECT [[how-to-brainstorming]]</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=45822 2012-03-29T21:47:25Z

<p>Juraj: how to moved to how-to-brainstorming</p> <hr /> <div>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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''domain''' - domain of problem (IT, horticulture)<br /> ** '''solution''' - element which content solution<br /> *** difficulty - how difficult is solution for user (technical, equipment, duration, price)<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions''' - steps to solve problem<br /> *** inset - insets like images, videos, source codes<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags</div>

Juraj https://microformats.org/wiki/index.php?title=how-to-brainstorming&diff=45821 2012-03-29T21:45:24Z

<p>Juraj: New page: 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 microforma...</p> <hr /> <div>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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to''' - main class<br /> ** '''problem''' - problem which the solution solve. <br /> ** '''domain''' - domain of problem (IT, horticulture)<br /> ** '''solution''' - element which content solution<br /> *** difficulty - how difficult is solution for user (technical, equipment, duration, price)<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions''' - steps to solve problem<br /> *** inset - insets like images, videos, source codes<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq - element for FAQ, which contents questions and answers<br /> *** question<br /> *** answer<br /> ** '''author''' - author of solution (hCard)<br /> ** published - datetime of publishing<br /> ** tag - for keywords, rel-tags</div>

Juraj https://microformats.org/wiki/index.php?title=User:Juraj&diff=45820 2012-03-29T21:43:06Z

<p>Juraj: </p> <hr /> <div>Hi, I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. It should be my own idea. <br /> <br /> 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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to'''<br /> ** '''problem'''<br /> ** '''domain'''<br /> ** '''solution'''<br /> *** difficulty<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions'''<br /> *** inset<br /> **** hMedia<br /> **** code<br /> **** rel-enclosure<br /> ** faq<br /> *** question<br /> *** answer<br /> ** '''author'''<br /> ** published<br /> ** tag<br /> <br /> <br /> If you want to contact me, my e-mail is: juraj.sivak@student.tuke.sk</div>

Juraj https://microformats.org/wiki/index.php?title=brainstroming-how-to&diff=45819 2012-03-29T21:17:09Z

<p>Juraj: brainstroming-how-to moved to User:Juraj over redirect</p> <hr /> <div>#REDIRECT [[User:Juraj]]</div>

Juraj https://microformats.org/wiki/index.php?title=User:Juraj&diff=45818 2012-03-29T21:17:09Z

<p>Juraj: brainstroming-how-to moved to User:Juraj over redirect</p> <hr /> <div>Hi, I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. It should be my own idea. <br /> <br /> 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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to'''<br /> ** '''problem'''<br /> ** '''domain'''<br /> ** '''solution'''<br /> *** difficulty<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions'''<br /> *** inset<br /> **** hMedia<br /> **** code<br /> *** rel-enclosure<br /> ** faq<br /> *** question<br /> *** answer<br /> ** '''author'''<br /> ** published<br /> ** tag<br /> ** summary<br /> ** see-also<br /> <br /> If you want to contact me, my e-mail is: juraj.sivak@student.tuke.sk</div>

Juraj https://microformats.org/wiki/index.php?title=User:Juraj&diff=45816 2012-03-29T21:15:22Z

<p>Juraj: User:Juraj moved to brainstroming-how-to</p> <hr /> <div>Hi, I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. It should be my own idea. <br /> <br /> 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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to'''<br /> ** '''problem'''<br /> ** '''domain'''<br /> ** '''solution'''<br /> *** difficulty<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions'''<br /> *** inset<br /> **** hMedia<br /> **** code<br /> *** rel-enclosure<br /> ** faq<br /> *** question<br /> *** answer<br /> ** '''author'''<br /> ** published<br /> ** tag<br /> ** summary<br /> ** see-also<br /> <br /> If you want to contact me, my e-mail is: juraj.sivak@student.tuke.sk</div>

Juraj https://microformats.org/wiki/index.php?title=User:Juraj&diff=45815 2012-03-29T19:49:41Z

<p>Juraj: </p> <hr /> <div>Hi, I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. It should be my own idea. <br /> <br /> 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 &quot;how-to&quot; and its schema is as follows:<br /> <br /> * '''how-to'''<br /> ** '''problem'''<br /> ** '''domain'''<br /> ** '''solution'''<br /> *** difficulty<br /> **** technical<br /> **** equipment<br /> **** duration<br /> **** price<br /> *** '''instructions'''<br /> *** inset<br /> **** hMedia<br /> **** code<br /> *** rel-enclosure<br /> ** faq<br /> *** question<br /> *** answer<br /> ** '''author'''<br /> ** published<br /> ** tag<br /> ** summary<br /> ** see-also<br /> <br /> If you want to contact me, my e-mail is: juraj.sivak@student.tuke.sk</div>

Juraj https://microformats.org/wiki/index.php?title=User:Juraj&diff=45800 2012-03-28T18:29:49Z

<p>Juraj: New page: Hi, I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. If you want to contact...</p> <hr /> <div>Hi, I am student of Technical University of Kosice. My theme of final paper is: Semantic web - Microformats. Part of my task is to design some kind of microformat. <br /> <br /> If you want to contact me, my e-mail is: juraj.sivak@student.tuke.sk</div>

Juraj https://microformats.org/wiki/index.php?title=job-listing-brainstorming&diff=45777 2012-03-26T13:08:03Z

<p>Juraj: /* Juraj Sivak */</p> <hr /> <div>= Job Listing Brainstorming =<br /> <br /> Ideas for a possible [[job-listing]] microformat.<br /> <br /> == Fields from examples ==<br /> <br /> (see the [[job-listing-examples]])<br /> <br /> {| class=&quot;sortable&quot;<br /> ! property || xhtml-element || description || major/minor (+/-) priority<br /> |-<br /> | title || h# || title of the job, e.g. 'Project-Manager for Customer-Service-Project' || +<br /> |-<br /> | description || class || job-description || +<br /> |-<br /> | company || [[hcard]] || || +<br /> |-<br /> | company size || class || || +<br /> |-<br /> | company logo || class || || -<br /> |-<br /> | multimedia || class || || -<br /> |-<br /> | location || [[adr]] || || +<br /> |-<br /> | start &amp; end date || dtstart &amp; dtend || :or should we use dstart for the date the ad is posted,&lt;br /&gt; and dtend for the closing date for aplications? || +<br /> |-<br /> | type (employee|contract) || class || || +<br /> |-<br /> | classification (full time|part time|temporary|&lt;br /&gt;temp to hire|seasonal|internship) || class || || +<br /> |-<br /> | hours/week || class || || +<br /> |-<br /> | salary base || class (see [[currency]]) || || +<br /> |-<br /> | salary max || class (see [[currency]]) || || +<br /> |-<br /> | wage/hour || class (see [[currency]]) || || +<br /> |-<br /> | education || class || ||<br /> |-<br /> | certification || class || ||<br /> |-<br /> | years || class || ||<br /> |-<br /> | skill || class || management can fall under skill ||<br /> |-<br /> | years || class || ||<br /> |-<br /> | required || class || ||<br /> |-<br /> | benefit || class || ||<br /> |-<br /> | holiday allowance || || expressed in days or weeks? ||<br /> |-<br /> | contact || [[hcard]]<br /> |-<br /> | time posted || date-time || (is this dtstart? See above) ||<br /> |-<br /> | relocation covered || class || ||<br /> |-<br /> | job function || class || (if absent, fall back to title?) ||<br /> |-<br /> | travel required || class || || <br /> |-<br /> | industry || || tag on company?<br /> |-<br /> | language of job-listing || &lt;s&gt;class&lt;/s&gt; @lang on containing element (or use page's language) || ||<br /> |-<br /> | job-language || class || mainlanguage spoken with colleagues ||<br /> |-<br /> | applicationmaterial || class || e.g. cv, worksamples, licenses, greencard || <br /> |-<br /> | organisationalid || class || number or phrase - large enterprises have an unique id for a specific job offer || <br /> |-<br /> | applicationurl || class || Some companies require applicants to fill out application forms online || <br /> |-<br /> |}<br /> <br /> <br /> ==Filip Chereches-Tosa==<br /> * Maybe there's no need to have a dedicated microformat for jobs and we could somehow extend [http://microformats.org/wiki/hlisting-proposal the hListing proposal], by adding the following optional fields under '''description''':<br /> ** salary<br /> ** education<br /> ** skills<br /> ** type<br /> <br /> [[User:FilipCte|Filip C.T.E.]]<br /> <br /> ==Bruce Stockwell==<br /> I concur with [[User:FilipCte|Filip C.T.E.]]. A vacant or new position at a company can be represented in its basic form by [http://microformats.org/wiki/hlisting-proposal the hListing proposal]. [http://microformats.org/wiki/measure hMeasure] and [http://microformats.org/wiki/currency-proposal hCurrency] could handle the salary as it would the monetary value of any basic listing. Describing optional and required skill set items needs more discussion.<br /> <br /> [[User:BruceStockwell|Bruce Stockwell]]<br /> <br /> ==Andy Mabbett==<br /> &quot;job-listing&quot; is clunky, would &quot;vacancy&quot; be a better name?<br /> *I second the change of name to &quot;Vacancy&quot;. - [[User: NTollervey|ntoll]]<br /> **I disagree, &quot;vacancy&quot; has no context. It could refer to anything - eg &quot;hotel vacancy&quot;. - Quint<br /> ***In which case, &quot;job-vacancy&quot; or just &quot;job&quot;? [[User:AndyMabbett|Andy Mabbett]]<br /> **** A job is a offering to the market for someone to fill so using the 3 attributes from the hlisting spec Listing Type=&quot;Offer&quot;, Listing Action = &quot;Announce&quot; and Item Type =&quot;Opening&quot; describe a job opening. [[User:Mspecht|Michael Specht]]<br /> <br /> ==Christian Pfetzing==<br /> <br /> What about &quot;job-offer&quot;? Reason: People with low english-skills often know &quot;offer&quot; but not &quot;vacancy&quot;.<br /> On the other hand:<br /> Why not easily &quot;job&quot;?<br /> With an attribute you can specify if it is a &quot;job-offer&quot; or a &quot;job-application&quot;. So human beeings/job-platforms can easily compare &quot;offers&quot; and &quot;applications&quot;. Manually (humans) or automatic (machines) -- [[User:Christian|Christian]] 05:48, 28 Apr 2007 (PDT)<br /> <br /> ==Darren Bounds==<br /> <br /> Keep in mind the internationally recognized term in the ATS industry is &quot;requisition&quot;. This is also defined in the [http://www.hr-xml.org HRXML specification]. <br /> <br /> While I believe other non-standard options should be considered, it does not appear as though the hResume specification gave any consideration to HRXML, which does have a large adoption for backend transations regarding HR data (including resumes and requisitions).<br /> <br /> * While this makes perfect sense from a specialist's back-end view, I'm not sure that I would ever look for a requisition (actually positive that I wouldn't) [[User:Amodal1| Robert Cooksey]]<br /> <br /> <br /> ==See also==<br /> *[http://www.twict.gov.uk/jobs.asp Joined Up Jobs] (job syndication initiative in UK local government)<br /> *[[currency]] - proposed microformat for marking-up amounts of money (for salary, wage, payment, earnings)<br /> <br /> ==Robert Cooksey==<br /> (hello everyone, my first post, I'll get to creating my user page[[User: Amodal1 | Robert Cooksey]] )<br /> * The idea of extending the hListing proposal sounds like a good one. <br /> ** This simplifies the models to more generic containers with detail coming from attribute values<br /> ** It also utilizes the time tested models of information organization on sites such as craigslist and paper models such as classifieds while adding the semantic specificity that allows the data to be utilized by systems in widely divergent varieties by agents--human and digital<br /> * Questions concerning this:<br /> ** Is there another word than job or requisition that captures all of each and is used in common parlance?<br /> ** Would &quot;offer&quot; be the best action for this? Maybe &quot;opportunity&quot; or something of which I'm not thinking?<br /> *** A general enough heading for this action in hListing would allow for a breakdown in terms of type of different forms<br /> *** The suggestion of type could accept values such as:<br /> **** contract, submission (for calls for conferences, publications, etc.), full-time, part-time, etc.<br /> **** This would allow for an opportunity (job/employment, call for papers, etc.) that could be differentiated by attributes of type and availability status (open, closed, conditional, etc.)<br /> ** Also, the word &quot;available&quot; seems more flexible should one want to allow for just an expression that expresses openness without too much specificity, but the expiration date might catch-that. What if open-until-filled?<br /> * One last suggestion is to add &quot;experience&quot; to the list Filip posted above<br /> ** While many job listers search for skills and education level, number of years experience are also used at least as often<br /> <br /> ==Michael Specht==<br /> Agree the hlisting format looks like it could easily be extended to meet the initial needs of a job posting, assuming we look at a job posting as a classified ad not from the view point of a recruiter. One of the issues that limited the take up of HRXML in the early days was it's complexity, experienced gained here in Australia trying to get vendors to support the format. The list of elements above seems to describe a job from an HR/recruitment point of view not a classifieds point of view.<br /> <br /> I see the biggest issue with the hlisting format being how to handle: salary, skills, type, industry and application process.<br /> <br /> == Jeff Donner ==<br /> For tech jobs at least, it'd be nice to have /graded/ requirements for skills, whether measured in years experience, general goodness, or how important to the position (1-5 say; 5 absolutely required, 1 lightly used, only nice-to-have). Also, Visa requirements (H1B, citizen, green card ...), security clearance, whether remote work is ok. And actually, all of these are applicable to general jobs as well. -- [[User:JeffDonner|Jeff Donner]]<br /> <br /> == Juraj Sivak ==<br /> Hi, I am student of Technical University of Kosice, and my theme of final paper is Semantic web - Microformats. Part of my task is to design some kind of microformat. I began to evolve microformat for job offer, regardless of this brainstorming. My proposed scheme of this microformat is as follows:<br /> * job-offer<br /> ** employer - name of employer (hCard) <br /> ** position - Type of job vacancy (ISCO)<br /> ** description - scope of employment<br /> ** salary/wage - sallary or wage<br /> *** currency <br /> ** adr - locality of job <br /> ** employment - type of employment <br /> ** dtstart - start-date of employment <br /> ** dtend - end-date of employment <br /> ** duration - duration of employment <br /> ** last-modified - last update <br /> ** requirements<br /> *** education-level - education level <br /> **** scope - scope of education<br /> *** experience - experiences like PC experience, practice, driving license...<br /> **** duration/level - duration or level of experience<br /> *** skill<br /> **** assumption - assumption like flexibility, communicativeness...<br /> **** language - language skill <br /> ***** level - level of language skill<br /> <br /> I am sorry for my english. I am just pre-intermediate.<br /> [[User:Juraj|Juraj Sivak]]</div>

Juraj https://microformats.org/wiki/index.php?title=job-listing-brainstorming&diff=45776 2012-03-26T12:59:14Z

<p>Juraj: /* Juraj Sivak */</p> <hr /> <div>= Job Listing Brainstorming =<br /> <br /> Ideas for a possible [[job-listing]] microformat.<br /> <br /> == Fields from examples ==<br /> <br /> (see the [[job-listing-examples]])<br /> <br /> {| class=&quot;sortable&quot;<br /> ! property || xhtml-element || description || major/minor (+/-) priority<br /> |-<br /> | title || h# || title of the job, e.g. 'Project-Manager for Customer-Service-Project' || +<br /> |-<br /> | description || class || job-description || +<br /> |-<br /> | company || [[hcard]] || || +<br /> |-<br /> | company size || class || || +<br /> |-<br /> | company logo || class || || -<br /> |-<br /> | multimedia || class || || -<br /> |-<br /> | location || [[adr]] || || +<br /> |-<br /> | start &amp; end date || dtstart &amp; dtend || :or should we use dstart for the date the ad is posted,&lt;br /&gt; and dtend for the closing date for aplications? || +<br /> |-<br /> | type (employee|contract) || class || || +<br /> |-<br /> | classification (full time|part time|temporary|&lt;br /&gt;temp to hire|seasonal|internship) || class || || +<br /> |-<br /> | hours/week || class || || +<br /> |-<br /> | salary base || class (see [[currency]]) || || +<br /> |-<br /> | salary max || class (see [[currency]]) || || +<br /> |-<br /> | wage/hour || class (see [[currency]]) || || +<br /> |-<br /> | education || class || ||<br /> |-<br /> | certification || class || ||<br /> |-<br /> | years || class || ||<br /> |-<br /> | skill || class || management can fall under skill ||<br /> |-<br /> | years || class || ||<br /> |-<br /> | required || class || ||<br /> |-<br /> | benefit || class || ||<br /> |-<br /> | holiday allowance || || expressed in days or weeks? ||<br /> |-<br /> | contact || [[hcard]]<br /> |-<br /> | time posted || date-time || (is this dtstart? See above) ||<br /> |-<br /> | relocation covered || class || ||<br /> |-<br /> | job function || class || (if absent, fall back to title?) ||<br /> |-<br /> | travel required || class || || <br /> |-<br /> | industry || || tag on company?<br /> |-<br /> | language of job-listing || &lt;s&gt;class&lt;/s&gt; @lang on containing element (or use page's language) || ||<br /> |-<br /> | job-language || class || mainlanguage spoken with colleagues ||<br /> |-<br /> | applicationmaterial || class || e.g. cv, worksamples, licenses, greencard || <br /> |-<br /> | organisationalid || class || number or phrase - large enterprises have an unique id for a specific job offer || <br /> |-<br /> | applicationurl || class || Some companies require applicants to fill out application forms online || <br /> |-<br /> |}<br /> <br /> <br /> ==Filip Chereches-Tosa==<br /> * Maybe there's no need to have a dedicated microformat for jobs and we could somehow extend [http://microformats.org/wiki/hlisting-proposal the hListing proposal], by adding the following optional fields under '''description''':<br /> ** salary<br /> ** education<br /> ** skills<br /> ** type<br /> <br /> [[User:FilipCte|Filip C.T.E.]]<br /> <br /> ==Bruce Stockwell==<br /> I concur with [[User:FilipCte|Filip C.T.E.]]. A vacant or new position at a company can be represented in its basic form by [http://microformats.org/wiki/hlisting-proposal the hListing proposal]. [http://microformats.org/wiki/measure hMeasure] and [http://microformats.org/wiki/currency-proposal hCurrency] could handle the salary as it would the monetary value of any basic listing. Describing optional and required skill set items needs more discussion.<br /> <br /> [[User:BruceStockwell|Bruce Stockwell]]<br /> <br /> ==Andy Mabbett==<br /> &quot;job-listing&quot; is clunky, would &quot;vacancy&quot; be a better name?<br /> *I second the change of name to &quot;Vacancy&quot;. - [[User: NTollervey|ntoll]]<br /> **I disagree, &quot;vacancy&quot; has no context. It could refer to anything - eg &quot;hotel vacancy&quot;. - Quint<br /> ***In which case, &quot;job-vacancy&quot; or just &quot;job&quot;? [[User:AndyMabbett|Andy Mabbett]]<br /> **** A job is a offering to the market for someone to fill so using the 3 attributes from the hlisting spec Listing Type=&quot;Offer&quot;, Listing Action = &quot;Announce&quot; and Item Type =&quot;Opening&quot; describe a job opening. [[User:Mspecht|Michael Specht]]<br /> <br /> ==Christian Pfetzing==<br /> <br /> What about &quot;job-offer&quot;? Reason: People with low english-skills often know &quot;offer&quot; but not &quot;vacancy&quot;.<br /> On the other hand:<br /> Why not easily &quot;job&quot;?<br /> With an attribute you can specify if it is a &quot;job-offer&quot; or a &quot;job-application&quot;. So human beeings/job-platforms can easily compare &quot;offers&quot; and &quot;applications&quot;. Manually (humans) or automatic (machines) -- [[User:Christian|Christian]] 05:48, 28 Apr 2007 (PDT)<br /> <br /> ==Darren Bounds==<br /> <br /> Keep in mind the internationally recognized term in the ATS industry is &quot;requisition&quot;. This is also defined in the [http://www.hr-xml.org HRXML specification]. <br /> <br /> While I believe other non-standard options should be considered, it does not appear as though the hResume specification gave any consideration to HRXML, which does have a large adoption for backend transations regarding HR data (including resumes and requisitions).<br /> <br /> * While this makes perfect sense from a specialist's back-end view, I'm not sure that I would ever look for a requisition (actually positive that I wouldn't) [[User:Amodal1| Robert Cooksey]]<br /> <br /> <br /> ==See also==<br /> *[http://www.twict.gov.uk/jobs.asp Joined Up Jobs] (job syndication initiative in UK local government)<br /> *[[currency]] - proposed microformat for marking-up amounts of money (for salary, wage, payment, earnings)<br /> <br /> ==Robert Cooksey==<br /> (hello everyone, my first post, I'll get to creating my user page[[User: Amodal1 | Robert Cooksey]] )<br /> * The idea of extending the hListing proposal sounds like a good one. <br /> ** This simplifies the models to more generic containers with detail coming from attribute values<br /> ** It also utilizes the time tested models of information organization on sites such as craigslist and paper models such as classifieds while adding the semantic specificity that allows the data to be utilized by systems in widely divergent varieties by agents--human and digital<br /> * Questions concerning this:<br /> ** Is there another word than job or requisition that captures all of each and is used in common parlance?<br /> ** Would &quot;offer&quot; be the best action for this? Maybe &quot;opportunity&quot; or something of which I'm not thinking?<br /> *** A general enough heading for this action in hListing would allow for a breakdown in terms of type of different forms<br /> *** The suggestion of type could accept values such as:<br /> **** contract, submission (for calls for conferences, publications, etc.), full-time, part-time, etc.<br /> **** This would allow for an opportunity (job/employment, call for papers, etc.) that could be differentiated by attributes of type and availability status (open, closed, conditional, etc.)<br /> ** Also, the word &quot;available&quot; seems more flexible should one want to allow for just an expression that expresses openness without too much specificity, but the expiration date might catch-that. What if open-until-filled?<br /> * One last suggestion is to add &quot;experience&quot; to the list Filip posted above<br /> ** While many job listers search for skills and education level, number of years experience are also used at least as often<br /> <br /> ==Michael Specht==<br /> Agree the hlisting format looks like it could easily be extended to meet the initial needs of a job posting, assuming we look at a job posting as a classified ad not from the view point of a recruiter. One of the issues that limited the take up of HRXML in the early days was it's complexity, experienced gained here in Australia trying to get vendors to support the format. The list of elements above seems to describe a job from an HR/recruitment point of view not a classifieds point of view.<br /> <br /> I see the biggest issue with the hlisting format being how to handle: salary, skills, type, industry and application process.<br /> <br /> == Jeff Donner ==<br /> For tech jobs at least, it'd be nice to have /graded/ requirements for skills, whether measured in years experience, general goodness, or how important to the position (1-5 say; 5 absolutely required, 1 lightly used, only nice-to-have). Also, Visa requirements (H1B, citizen, green card ...), security clearance, whether remote work is ok. And actually, all of these are applicable to general jobs as well. -- [[User:JeffDonner|Jeff Donner]]<br /> <br /> == Juraj Sivak ==<br /> Hi, I am student of Technical University of Kosice, and my theme of final paper is Semantic web - Microformats. Part of my task is to design some kind of microformat. I began to evolve microformat for job offer, regardless of this brainstorming. My proposed scheme of this microformat is as follows:<br /> * job-offer<br /> ** employer - name of employer (hCard) <br /> ** position - Type of job vacancy (ISCO)<br /> ** description - scope of employment<br /> ** salary/wage - sallary or wage<br /> *** currency <br /> ** adr - locality of job <br /> ** employment - type of employment <br /> ** dtstart - start-date of employment <br /> ** dtend - end-date of employment <br /> ** duration - duration of employment <br /> ** last-modified - last update <br /> <br /> ** requirements - this atribute is used only for clearer structure<br /> *** education-level - education level <br /> **** scope - scope of education<br /> *** experience - experiences like PC experience, practice, driving license...<br /> **** duration/level - duration or level of experience<br /> *** skill<br /> **** assumption - assumption like flexibility, communicativeness...<br /> **** language - language skill <br /> ***** level - level of language skill<br /> <br /> I am sorry for my english. I am just pre-intermediate.<br /> [[User:Juraj|Juraj Sivak]]</div>

Juraj https://microformats.org/wiki/index.php?title=job-listing-brainstorming&diff=45775 2012-03-26T12:58:23Z

<p>Juraj: </p> <hr /> <div>= Job Listing Brainstorming =<br /> <br /> Ideas for a possible [[job-listing]] microformat.<br /> <br /> == Fields from examples ==<br /> <br /> (see the [[job-listing-examples]])<br /> <br /> {| class=&quot;sortable&quot;<br /> ! property || xhtml-element || description || major/minor (+/-) priority<br /> |-<br /> | title || h# || title of the job, e.g. 'Project-Manager for Customer-Service-Project' || +<br /> |-<br /> | description || class || job-description || +<br /> |-<br /> | company || [[hcard]] || || +<br /> |-<br /> | company size || class || || +<br /> |-<br /> | company logo || class || || -<br /> |-<br /> | multimedia || class || || -<br /> |-<br /> | location || [[adr]] || || +<br /> |-<br /> | start &amp; end date || dtstart &amp; dtend || :or should we use dstart for the date the ad is posted,&lt;br /&gt; and dtend for the closing date for aplications? || +<br /> |-<br /> | type (employee|contract) || class || || +<br /> |-<br /> | classification (full time|part time|temporary|&lt;br /&gt;temp to hire|seasonal|internship) || class || || +<br /> |-<br /> | hours/week || class || || +<br /> |-<br /> | salary base || class (see [[currency]]) || || +<br /> |-<br /> | salary max || class (see [[currency]]) || || +<br /> |-<br /> | wage/hour || class (see [[currency]]) || || +<br /> |-<br /> | education || class || ||<br /> |-<br /> | certification || class || ||<br /> |-<br /> | years || class || ||<br /> |-<br /> | skill || class || management can fall under skill ||<br /> |-<br /> | years || class || ||<br /> |-<br /> | required || class || ||<br /> |-<br /> | benefit || class || ||<br /> |-<br /> | holiday allowance || || expressed in days or weeks? ||<br /> |-<br /> | contact || [[hcard]]<br /> |-<br /> | time posted || date-time || (is this dtstart? See above) ||<br /> |-<br /> | relocation covered || class || ||<br /> |-<br /> | job function || class || (if absent, fall back to title?) ||<br /> |-<br /> | travel required || class || || <br /> |-<br /> | industry || || tag on company?<br /> |-<br /> | language of job-listing || &lt;s&gt;class&lt;/s&gt; @lang on containing element (or use page's language) || ||<br /> |-<br /> | job-language || class || mainlanguage spoken with colleagues ||<br /> |-<br /> | applicationmaterial || class || e.g. cv, worksamples, licenses, greencard || <br /> |-<br /> | organisationalid || class || number or phrase - large enterprises have an unique id for a specific job offer || <br /> |-<br /> | applicationurl || class || Some companies require applicants to fill out application forms online || <br /> |-<br /> |}<br /> <br /> <br /> ==Filip Chereches-Tosa==<br /> * Maybe there's no need to have a dedicated microformat for jobs and we could somehow extend [http://microformats.org/wiki/hlisting-proposal the hListing proposal], by adding the following optional fields under '''description''':<br /> ** salary<br /> ** education<br /> ** skills<br /> ** type<br /> <br /> [[User:FilipCte|Filip C.T.E.]]<br /> <br /> ==Bruce Stockwell==<br /> I concur with [[User:FilipCte|Filip C.T.E.]]. A vacant or new position at a company can be represented in its basic form by [http://microformats.org/wiki/hlisting-proposal the hListing proposal]. [http://microformats.org/wiki/measure hMeasure] and [http://microformats.org/wiki/currency-proposal hCurrency] could handle the salary as it would the monetary value of any basic listing. Describing optional and required skill set items needs more discussion.<br /> <br /> [[User:BruceStockwell|Bruce Stockwell]]<br /> <br /> ==Andy Mabbett==<br /> &quot;job-listing&quot; is clunky, would &quot;vacancy&quot; be a better name?<br /> *I second the change of name to &quot;Vacancy&quot;. - [[User: NTollervey|ntoll]]<br /> **I disagree, &quot;vacancy&quot; has no context. It could refer to anything - eg &quot;hotel vacancy&quot;. - Quint<br /> ***In which case, &quot;job-vacancy&quot; or just &quot;job&quot;? [[User:AndyMabbett|Andy Mabbett]]<br /> **** A job is a offering to the market for someone to fill so using the 3 attributes from the hlisting spec Listing Type=&quot;Offer&quot;, Listing Action = &quot;Announce&quot; and Item Type =&quot;Opening&quot; describe a job opening. [[User:Mspecht|Michael Specht]]<br /> <br /> ==Christian Pfetzing==<br /> <br /> What about &quot;job-offer&quot;? Reason: People with low english-skills often know &quot;offer&quot; but not &quot;vacancy&quot;.<br /> On the other hand:<br /> Why not easily &quot;job&quot;?<br /> With an attribute you can specify if it is a &quot;job-offer&quot; or a &quot;job-application&quot;. So human beeings/job-platforms can easily compare &quot;offers&quot; and &quot;applications&quot;. Manually (humans) or automatic (machines) -- [[User:Christian|Christian]] 05:48, 28 Apr 2007 (PDT)<br /> <br /> ==Darren Bounds==<br /> <br /> Keep in mind the internationally recognized term in the ATS industry is &quot;requisition&quot;. This is also defined in the [http://www.hr-xml.org HRXML specification]. <br /> <br /> While I believe other non-standard options should be considered, it does not appear as though the hResume specification gave any consideration to HRXML, which does have a large adoption for backend transations regarding HR data (including resumes and requisitions).<br /> <br /> * While this makes perfect sense from a specialist's back-end view, I'm not sure that I would ever look for a requisition (actually positive that I wouldn't) [[User:Amodal1| Robert Cooksey]]<br /> <br /> <br /> ==See also==<br /> *[http://www.twict.gov.uk/jobs.asp Joined Up Jobs] (job syndication initiative in UK local government)<br /> *[[currency]] - proposed microformat for marking-up amounts of money (for salary, wage, payment, earnings)<br /> <br /> ==Robert Cooksey==<br /> (hello everyone, my first post, I'll get to creating my user page[[User: Amodal1 | Robert Cooksey]] )<br /> * The idea of extending the hListing proposal sounds like a good one. <br /> ** This simplifies the models to more generic containers with detail coming from attribute values<br /> ** It also utilizes the time tested models of information organization on sites such as craigslist and paper models such as classifieds while adding the semantic specificity that allows the data to be utilized by systems in widely divergent varieties by agents--human and digital<br /> * Questions concerning this:<br /> ** Is there another word than job or requisition that captures all of each and is used in common parlance?<br /> ** Would &quot;offer&quot; be the best action for this? Maybe &quot;opportunity&quot; or something of which I'm not thinking?<br /> *** A general enough heading for this action in hListing would allow for a breakdown in terms of type of different forms<br /> *** The suggestion of type could accept values such as:<br /> **** contract, submission (for calls for conferences, publications, etc.), full-time, part-time, etc.<br /> **** This would allow for an opportunity (job/employment, call for papers, etc.) that could be differentiated by attributes of type and availability status (open, closed, conditional, etc.)<br /> ** Also, the word &quot;available&quot; seems more flexible should one want to allow for just an expression that expresses openness without too much specificity, but the expiration date might catch-that. What if open-until-filled?<br /> * One last suggestion is to add &quot;experience&quot; to the list Filip posted above<br /> ** While many job listers search for skills and education level, number of years experience are also used at least as often<br /> <br /> ==Michael Specht==<br /> Agree the hlisting format looks like it could easily be extended to meet the initial needs of a job posting, assuming we look at a job posting as a classified ad not from the view point of a recruiter. One of the issues that limited the take up of HRXML in the early days was it's complexity, experienced gained here in Australia trying to get vendors to support the format. The list of elements above seems to describe a job from an HR/recruitment point of view not a classifieds point of view.<br /> <br /> I see the biggest issue with the hlisting format being how to handle: salary, skills, type, industry and application process.<br /> <br /> == Jeff Donner ==<br /> For tech jobs at least, it'd be nice to have /graded/ requirements for skills, whether measured in years experience, general goodness, or how important to the position (1-5 say; 5 absolutely required, 1 lightly used, only nice-to-have). Also, Visa requirements (H1B, citizen, green card ...), security clearance, whether remote work is ok. And actually, all of these are applicable to general jobs as well. -- [[User:JeffDonner|Jeff Donner]]<br /> <br /> == Juraj Sivak ==<br /> Hi, I am student of Technical University of Kosice, and my theme of final paper is Semantic web - Microformats. Part of my task is to design some kind of microformat. I began to evolve microformat for job offer, regardless of this brainstorming. My proposed scheme of this microformats is as follows:<br /> * job-offer<br /> ** employer - name of employer (hCard) <br /> ** position - Type of job vacancy (ISCO)<br /> ** description - scope of employment<br /> ** salary/wage - sallary or wage<br /> *** currency <br /> ** adr - locality of job <br /> ** employment - type of employment <br /> ** dtstart - start-date of employment <br /> ** dtend - end-date of employment <br /> ** duration - duration of employment <br /> ** last-modified - last update <br /> <br /> ** requirements - this atribute is used only for clearer structure<br /> *** education-level - education level <br /> **** scope - scope of education<br /> *** experience - experiences like PC experience, practice, driving license...<br /> **** duration/level - duration or level of experience<br /> *** skill<br /> **** assumption - assumption like flexibility, communicativeness...<br /> **** language - language skill <br /> ***** level - level of language skill<br /> <br /> I am sorry for my english. I am just pre-intermediate.<br /> [[User:Juraj|Juraj Sivak]]</div>

Juraj