Microformats Wiki - User contributions [en]

learning-formats

2009-02-02T05:15:21Z

FajRo: minor wikicode fix

= hVocabulary =

== example code ==

this is how iKnow[http://iknow.co.jp] markes up cue-response pairs and the learning content around it

<pre>
<nowiki>
<div class="hVocabulary">

<div class="cue_response">
<div class="cue en" xml:lang="en" lang="en">
<span class="sound">http://media4.cerego.co.jp/contents/core/audio/core2_1_q108.mp3</span>
<span class="text"><a href="http://www.iknow.co.jp/item/37992">record</a></span>
</div>
<div class="response ja" xml:lang="ja" lang="ja">
<span class="text">記録</span>
</div>
</div>

<div id="sample_sentence_0" class="sample_sentence">
<img alt="record" src="http://media2.cerego.co.jp/contents/images/s/3603949.jpg" title="record"/>
<div class="sentence">
<span class="sound" id="37992_sample_sentence_0_sound">http://media4.cerego.co.jp/contents/core/audio/core2_1_s1_108.mp3</span>
<p class="sample en" xml:lang="en" lang="en">I keep <b>records</b> of all the work I have done.</p>
<p class="translation ja" xml:lang="ja" lang="ja">私は自分がした仕事を全て記録している</p>
</div>
</div>
<div id="sample_sentence_1" class="sample_sentence">
<img alt="record" src="http://media2.cerego.co.jp/contents/images/s/3603949.jpg" title="record"/>
<div class="sentence">
<span class="sound" id="37992_sample_sentence_0_sound">http://media4.cerego.co.jp/contents/core/audio/core2_1_s1_108.mp3</span>
<p class="sample en" xml:lang="en" lang="en">The secretary keeps careful <b>records</b>.</p>
<p class="translation ja" xml:lang="ja" lang="ja">その秘書は慎重に記録を取る</p>
</div>
</div>
</div>
</nowiki>
</pre>

= See Also =
* [[learning-brainstorming|brainstorming]]
* [[learning-examples|examples]]
* [[learning-people|people]]
* [[learning-proposal|proposal]]
* [[learning-formats|formats]]
* [[learning-issues|issues]]

wiki-2

2008-11-19T02:33:59Z

FajRo: FamFamFam URL corrected

<entry-title>Microformats.org Wiki 2.0</entry-title>
<p class="entry-summary">Microformats.org has been served by a near-default MediaWiki theme since it first went live in 2005. Over the years the kind of content published on the wiki has been established, and the editing practices of our community better understood. The ‘Wiki 2.0’ project is a medium-sized undertaking to update our wiki software to better suit the communities needs, and take the opportunity to add some visual sparkle too.</p>
__TOC__

==Summary of Changes==

* MediaWiki has been updated from version 1.4 to version 1.13.2.
* The visual styling of the wiki has been upgraded to a completely custom skin, based on Dan Cederholm's original microformats.org design.
* The search feature is now located at the top-right of the page, because having it buried further down was silly.
* The header now links to other vital parts of the microformats site — the blog and the mailing list archives.
* Some new extensions have been added to the MediaWiki install
** HTML phrase elements are now fully supported
** Code syntax highlighting has been added
** Page titles can now be overwritten in mark-up (e.g. ‘hcard’ can become ‘hCard’, or more ambitious transformations)
* ‘Talk’ pages have been <strong>completely</strong> disabled, rather than just ‘hidden’.
* All wiki pages are marked up with [[hAtom]] and [[hCalendar]]
* We will now be using MediaWiki's categories feature to better organize our content.
** Pages placed into the Specifications category gets special ‘spec-like’ styling (see [[hCard]]).
** Pages places into the Draft Specifications category get different special ‘spec-like’ styling (see [[hResume]])
** Pages placed into either specification category will generate links to their respective -issues pages
* TOC — table of contents — is now properly styled in the theme. There is nolonger a need to use inline styles to align the TOC to the right
* There is now styling support for both inline issues tracking and discussions within list nesting. Previously it was hard to identify discussion documentation from proposed content, and hard to follow threads. Mark-up is now supported to style these more apporpriately
* Your username now has a [http://gravatar.com Gravatar] displayed alongside, as in blog comments.
* When editing, the ‘Save’ and ‘Preview’ buttons have been reversed to try and encourage people to preview more before posting

==How to Use Wiki 2.0==

The following tries to explain how best to use the new features in Wiki 2.0.

===Page Titles===

Between version 1.4 and 1.13 MediaWiki fixed a bug whereby headings marked up with HTML elements were excluded from the generated Table of Contents on pages. We have since used <code>H1</code> elements to override the headings of pages whilst not offsetting the TOC numbering into 1.1, 1.2, 1.3, etc. Since that bug is fixed, this hack has been replaced with a more robust mechanism.

<em>Rather than use <code>H1</code> elements to title your pages, instead use the new <code>entry-title</code> element</em>. This is parsed by a MediaWiki extension and overrides the entry title as displayed on the page, whilst excluding it from the TOC. It is so named, because it corresponds to the entry-title element in the underlying hAtom that each entry is now marked up with.

===Writing Specifications===

The new wiki supports special display of specification documents, different from regular pages. The pages are styled more plainly and content spans the full width of the page, akin to documentation from the W3C, WHATWG and other bodies. The sidebar is pushed down into an expanded footer, so all functionality remains.

To enable these views, you must add your page to a particular category.

* Specifications should be added to the ‘Specifications’ category, by including <nowiki>[[Category:Specifications]]</nowiki> at the base of the document.
* Draft Specifications should be added to the ‘Draft Specifications’ category, by including <nowiki>[[Category:Draft Specifications]]</nowiki> at the base of the document. You '''must''' also include the <nowiki>{{DraftSpecification}}</nowiki> template at the head of your document, to provide textual differentiation of the draft.

Please note that issues pages, brainstorming pages, straw-men and anything else not explicitly a Draft Specification or Specification document should not be added to these categories and should continue to be presented as regular wiki pages.

Categories should be declared at the base of articles, please.

===Discussions and Issues===

Within documents discussions are often represented through nested lists. They are hard to follow, and hard to differentiate from the actual content of the document. You can now mark them up and have them presented more appropriately, and hopefully more clearly.

* For <em>discussions</em>: Surround the thread with <code><div class="discussion"></div></code>.
* For raising <em>issues</em>: Surround the thread with <code><div class="discussion issues"></div></code>.

The following are examples to show the rendering:

<div class="discussion">
* I'm not happy with the phrasing of the above. --[[User:BenWard|BenWard]] 09:50, 17 November 2008 (UTC)
** I disagree, I think it's fine! --[[User:BenWard|BenWard]] 09:50, 17 November 2008 (UTC)
</div>

<div class="discussion issues">
* '''New wiki does not support declarative creation of animated GIFs on profile pages'''. This is a big deal for me! --[[User:BenWard|BenWard]] 09:50, 17 November 2008 (UTC)
** No. Just… no! --[[User:BenWard|BenWard]] 09:50, 17 November 2008 (UTC)
</div>

'''Always''' sign your contributions to discussions using the string <nowiki>--~~~~</nowiki> at the end of your text.

===Code Highlighting===

We've installed a [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi Syntax Highlighting extension]. This allows you to have nicer highlighting of many languages used in examples and code snippets on the wiki.

* To use syntax highlighted source blocks, use the new <code><source></code> element. E.g.

<pre><nowiki>
<source lang=html4strict>
<div class="vcard">
<a class="fn org" href="http://microformats.org">Microformats.org</a>
</div>
</source>
</nowiki></pre>

Produces:

<source lang=html4strict>
<div class="vcard">
<a class="fn org" href="http://microformats.org">Microformats.org</a>
</div>
</source>

Note that the language name for HTML is <code>html4strict</code>, not just ‘HTML’. You can find the full list of supported languages on the Syntax Highlighter extension page: http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi#Supported_languages

==Credits==

The Wiki 2.0 project was implemented by [[User:BenWard]]. The visual style is derived from the original microformats.org theme by [http://simplebits.com Dan Cederholm]. The wiki also uses the wonderfully useful [http://famfamfam.com/lab/icons/silk/ Fam Fam Fam Silk icons] by Mark James.

==Issues==

Please report, bugs issues and requests on the [[wiki-2-issues]] page.

[[Category:Microformats.org]]
[[Category:Wiki]]

HReview-feedback

2008-04-03T22:37:30Z

FajRo: spamlinks

#REDIRECT [[hreview-feedback]]

disambiguation

2008-04-03T22:33:47Z

FajRo: spamlinks

#REDIRECT [[microformat]]

User:FajRo

2008-01-10T00:08:51Z

FajRo:

'''Fajro''' means "fire" in [[wikipedia:Esperanto|Esperanto]]

==hCard/vCard ideas==

* Languages Spoken (ISO codes)
* Preferred Contact Languages
* Preferred Method of Contact ( by , Telephone, Cellphone, Fax, Mail, E-mail, IM, SMS, IRC, Twitter, Pibb, Telegraph, Shortwave radio, Smoke signals, Drums, Pigeon post,Tin can telephone, Signal flags, Heliograph, Signal lamp, Telepathy, Singing telegram, in person, etc )

{{cc-public-domain-release}}

User:FajRo

2008-01-09T19:57:22Z

FajRo:

'''Fajro''' means "fire" in [[wikipedia:Esperanto|Esperanto]]

==hCard/vCard ideas==

* Languages Spoken (ISO codes)
* Preferred Contact Languages
* Preferred Method of Contact ( by , Telephone, Cellphone, Fax, Mail, E-mail, IM, SMS, IRC, Twitter, Pibb, Telegraph, Shortwave radio, Smoke signals, Pigeon post, Signal flags, Heliograph, Signal lamp, Telepathy, Singing telegram, In person, etc )

{{cc-public-domain-release}}

User:FajRo

2008-01-09T17:46:00Z

FajRo: /* hCard ideas */

'''Fajro''' means "fire" in [[wikipedia:Esperanto|Esperanto]]

==hCard ideas==

* Languages Spoken (ISO codes)
* Preferred Contact Languages
* Preferred Method of Contact ( by , telephone, mail, e-mail, IM, SMS, etc. )

{{cc-public-domain-release}}

User:FajRo

2008-01-09T17:45:38Z

FajRo: /* hCard ideas */

'''Fajro''' means "fire" in [[wikipedia:Esperanto|Esperanto]]

==hCard ideas==

* Languages Spoken (ISO codes)
* Preferred Contact Languages
* Preferred Method Contact ( by , telephone, mail, e-mail, IM, SMS, etc. )

{{cc-public-domain-release}}

User:FajRo

2008-01-08T22:05:31Z

FajRo: Fajro mikrofomatumas!

'''Fajro''' means "fire" in [[wikipedia:Esperanto|Esperanto]]

==hCard idea==

* Languages
* Preferred Contact Languages

{{cc-public-domain-release}}

how-to-play

2008-01-08T17:55:06Z

FajRo: /* Guidelines */

If this is your first visit, please see the [[introduction]] page.

<h1>How to Play</h1>
{{TOC-right}}

== Guidelines ==
Before contributing please observe these guidelines:

# You have to create an account (see [http://en.wikipedia.org/wiki/Wikipedia:Username Wikipedia Username guidelines]) before editing/creating pages.
# Read about microformats.org [[:Category:public_domain_license|Voluntary Public Domain Declarations]] and please consider adding the [[Template:public-domain-release]] to your User page accordingly to release your contributions to microformats.org into the public domain.
# Try the [http://microformats.org/discuss irc channel (preferable) or mailing lists] first (and read the [[mailing-lists]] page before doing so).
# If you write something opinionated, sign it with your username - you can easily do so with a datetimestamp in MediaWiki with four tildes, e.g.: <nowiki>~~~~</nowiki>.
#*On the few occasions when it is necessary to edit others signed contributions (as opposed to general content), be careful not to change their meaning.
# Please only create pages directly relating to [[POSH]], microformats (and [[picoformats]]) on this wiki. [[data-portability]] in line with microformats [[principles]] is also encouraged. Other pages will likely be deleted.
# Please obey the [[naming-conventions| naming conventions]] for pages.
# Don't use talk pages. See #3.
# Please try to ensure that you produce valid XHTML.
# When you paste code, add some line breaks at a reasonable width.
# Please do not use "?" or other punctuation in the headings - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc.
# Consider using ''lowercase'' words in headings (except for proper nouns), and avoid repeating the page title in headings. This helps with shortening permalinks to sections (thereby increasing fidelity of URL transfer, e.g. across email), and keeping their URLs ''all'' lowercase makes them easier to type.
# Headings may be explicitly marked up with <h1> <h2> tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please <strong style="text-transform:uppercase">do not</strong> change them to "=" or "==" style headings.
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. If you change a heading please leave a <code><nowiki><div id="oldheadingID"></div></nowiki></code> around the new heading with oldHeadingID set to the necessary value to maintain heading permalinks.
# Avoid global editorial wiki changes / edits (e.g. the same or similar edits applied to numerous pages, say, more than a dozen or so pages). If you have an opinion on how to globally improve something stylistically or editorially on the wiki, please add it to your section on the [[to-do]] page, and then perhaps ask the community using the microformats-discuss mailing list what folks think of it. Interpret absence of response(s) as disinterest and thus implicit rejection. Admins may from time to time do global wiki changes to remove spam, repair damage done by other global wiki edits etc.
# Please avoid simple contradictory responses such as "No" to questions and issues. Instead provide at least a short sentence with a reason which provides information beyond what is provided in the question or issue.
# Do not remove "red links", nor create empty / placeholder "..." pages for them just to make them not red. The red links usefully communicate a need or a desire for that page to exist, and the person expressing that desire may not be the same person that is able to take the time, or has the necessary skill/background to draft such a page. The links to pages not yet created often serve as an effective (and easy to execute) "to do" list. Removing those links makes it harder, less convenient to do so. (One exception noted so far: red links to non-existent microformats e.g. "hbib", should be delinked, as it is desirable for it to be harder/less convenient to create new microformats). Finally, as such links do provide information, they are not redundant.
# Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.
# Do not create new "User:" links by hand. User: links should only created as a result of users actually signing their edits with <nowiki>~~~</nowiki> or <nowiki>~~~~</nowiki>. That way each User: page will correspond to an actual login, rather than accidentally linking to a page which doesn't represent a login. If you see a red link which appears like it ''should'' be a User: link, e.g. <nowiki>[[DavidJanes]]</nowiki>, rather than editing the link in place, create a redirect at the destination of the link to the person's User: page.
# Check "what links here" before moving pages, and fix any links to the page you're moving, if appropriate.
# Please use U.S. English ([[en-US]]) spellings of words on English microformats pages. This is by convention, following the [http://www.w3.org/2001/06/manual/#Spelling W3C Manual of Style Spelling Editorial Guideline].
# Use [[rfc-2119#Templates|templates]] for RFC 2119 terms such as {{must}}.
# References to (X)HTML element names should be lowercase and marked up with <nowiki><code>...</code></nowiki>, e.g. the <code>input</code> element. This convention is adopted from the practice used in the [http://www.w3.org/2001/06/manual/ W3C Manual of Style].
# Use <nowiki>example.org</nowiki> for hypothetical URL examples rather than a fake domain name (which may eventually be registered, used for spam etc.). When doing so, be sure to use <code><nowiki></code> tags, e.g.: <code><nowiki><nowiki>http://example.org/</nowiki></nowiki></code> so that the URLs are not auto-hyperlinked by MediaWiki. Where interactions between multiple domains need to be illustrated, you may use <nowiki>example.net or example.com</nowiki> or subdomains of <nowiki>example.org like foo.example.org</nowiki>.
# If you notice that someone is iteratively editing a page (say by watching the IRC channel, or the [[Special:Recentchanges]] page) that you'd like to edit, consider waiting at least 10 minutes after the most recent edit before doing so, as the person iteratively editing the page may have further edits to make, and thus waiting a few minutes would likely save you both time by avoiding potential/likely edit conflicts. Similarly, if you plan to make multiple edits to a page, consider using [[Template:inuse]] by placing '''<nowiki>{{Template:inuse}}</nowiki>''' at the head of the page. Please don't forget to remove it, when you're done!
# Please do not remove apparently broken links (404 etc.). If you cannot fix them, de-link them using <nowiki><nowiki></nowiki> and note (perhaps with a nested list item or parenthetical remark) that the links appear to have stopped working as of a certain date. This way whoever added the links or is responsible for them may discover that they need to fix them, and those researching the links can still look them up in the [http://archive.org/ Internet Archive].

== Accessibility ==
#Use upper case for acronyms like HTML but use <code><nowiki><strong style="text-transform:uppercase"></nowiki></code> to add strength to phrases like "<strong style="text-transform:uppercase">do not</strong>". This improves accessibility <strong>(citation needed)</strong> for text-reading software and other agents <strong>(list and versions of text-reading software & other agents affected needed)</strong>.

== Wiki Cleaning ==
See [[spam-removal]].

If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list rather than doing it yourself.

== Related ==
See [[mediawiki-customization]] for brief notes on how the microformats wiki is different from a "typical" MediaWiki install, in many ways to help with [[how-to-play]] and [[naming-conventions]].