Microformats Wiki - User contributions [en]

how-to-play-ja

2010-07-19T19:38:47Z

IwaiMasaharu: sync: english: 2010-07-06T07:55:36

__NOTOC__
初めての方は[[introduction-ja|Microformatsの手引き]]をご覧ください。

Please also review the in-progress [[how-to-play-2]] page and provide feedback on it!

<entry-title>How to Play</entry-title>

== ガイドライン ==
協力する前にこれらのガイドラインを読んでください。また、この内容は遵守してください。

# ページを編集したり作成したりする前にアカウントを作成してください。Please consider using your name, e.g. GivenFamily (FirstLast). [http://en.wikipedia.org/wiki/Wikipedia:Username Wikipedia Username guidelines] もご覧ください。You may use an alias (e.g. [[User:Adactio]], [[User:Phae]]). Please do not use organization names or other proper nouns (e.g. products, technologies).
# microformats.orgの[[:Category:public_domain_license|Public Domain Declarations]]をご覧ください。そして、[[Template:public-domain-release]]を自分のユーザーページに追加して、あなたのmicroformats.orgサイトへの2008年以前の貢献をパブリック・ドメインへ解放することも検討してみてください。
# はじめに[http://microformats.org/discuss IRCチャンネル（こちらがお勧め）か、メーリングリスト]に参加してみてください。(その前には[[mailing-lists]]を読んで下さい)
# もし、論理的な理由を越えて何か意見を書いたならば、あなたのユーザ名も一緒に書いてください。- これはMediaWikiのdatetimestampを使って簡単にできます。4つの半角「~」を以下のように並べます: <nowiki>~~~~</nowiki>
#*On the few occasions when it is necessary to edit others signed contributions (as opposed to general content), take care not to change their meaning.
#*If your logically reasoned statement is part of a discussion which disagrees with a previous comment, you may sign it with your username. However signing such statements is both not required, and may detract from the logically reasoned statement standing on its own (related: [[#avoid-personalizing-proposals|avoid personalizing proposals]]), and thus consider leaving such statements unsigned. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# このWikiには、[[POSH-ja|POSH]]やmicroformats(と[[picoformats]])に直接関係あるページだけを作成してください。[[data-portability]] in line with microformats [[principles]] is also encouraged. 無関係なページは削除されます。
# <span id="naming">ページの[[naming-conventions-ja|命名規則]]に従ってください。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span>
# Wikiのページで会話をしてはいけません。その用途には#3で挙げた[http://microformats.org/discuss mailing lists]を使ってください。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 妥当なXHTMLで記述するようにしてください。
# ソースコードを貼りつける場合、適当な長さで改行を入れてください。
# 見出しに「?」や句読点記号を入れないでください。これは、URLのフラグメント識別子（リンクのターゲットを表す部分）を短くすることにより、可読性を高めたり、コピー＆ペーストなどをしやすくするためです。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# <span id="lowercase-headings">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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]</span>
# 目次に表示させたくない見出しには <h1> タグや <h2> タグなどを使ってもかまいません。こういったタグを見つけても、「=」や「==」などを使ったスタイルの見出しに<strong style="text-transform:uppercase">変更しないでください</strong>。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 見出しのテキストを変更しないようにしてください（大文字と小文字間の変換や、上記のルールに従おうとするための変更も含む）。見出しはパーマリンクとして使われることが多いため、変更によって他で使われているリンク切れなどをひき起こす可能性があります。これらをふまえ、見出しをつける場合は注意して言葉を選んでください。どうしても変更が必要な場合、<code><nowiki><div id="oldheadingID"></div></nowiki></code> というコードで新しい見出しを囲み、"oldHeadingID" の部分を見出しパーマリンクを残すために必要な値にすることで、リンク切れを防ぐことはできます。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# Start headings with a letter (or underscore a letter doesn't work), in order to generate valid ID attributes on heading elements.
# 当Wiki全体に関する変更や編集（例: 10数ページ以上のページに影響する編集など）を行わないでください。もしWiki全体のスタイルや編集のやり方を改善できるような意見があるようでしたら、その内容を[[to-do]]ページの該当セクションに追加した上で、メーリングリストなどを使ってコミュニティの他のメンバーがどう思うか聞いてみましょう。返事がない場合は、あまり興味がない、つまり暗黙的な却下というふうに理解してください。ただしWiki管理人は、スパム削除や他の編集によって壊れた部分の修正などのために、Wiki全体に関わる変更を加えることがあります。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 質問や問題提議に対し、「却下」だけなどの<span id="avoid-simple-contradictions">単純な反対意見で反応するのはやめましょう</span>。かわりに、短くてもいいので、元の質問や意見には含まれていなかった情報を加え、反対の理由を述べてください。Simple contradictions (like just inverting other statements on a page as if such an inversion was an argument), are a waste of time and space and to be avoided.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 赤文字のリンクを削除したり、ダミーコンテンツを置いた空の新規ページを作成しないでください。赤文字のリンクは、新規ページ作成の必要性があるという判断より作成されたものですが、リンク先が編集されていないのは、リンクの作成者が必ずしもそのページの内容に詳しくなかったり、時間がなかったりという理由からです。（ただし、現存しないマイクロフォーマット・タイプのページへのリンクなどは外すべきです）[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# Please do not add MediaWiki Categories. With the [[wiki-2|upgrade to the wiki]] we have begun using a very limited number of categories in order to present specifications and drafts differently than other wiki pages. For now if you think additional Categories would help the community, please make suggestions on the [[category-suggestions]] page. [<abbr title="guideline created due to one or more actions by Toby Inkster">src:TI</abbr>]. 以前は次のようになっていました。『MediaWiki の「カテゴリー」構造を使わないでください。このコミュニティは、MediaWikiの全機能を使わないことにしているからです。（その他の例：「Talk」ページ）』[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 手動で新規 "User:" リンクを作成しないでください。"User:" リンクは、ユーザーが自身の編集に <nowiki>~~~</nowiki> または <nowiki>~~~~</nowiki> の署名を加えたときのみ、自動で作成されるようにしましょう。こうすることで、間違ったログイン名にリンクを作成したりすることなく、各 "User:" ページが実際のログインときちんと対応するようになります。もし、 "User:" リンクにするべき赤文字のリンクを発見した場合（例: <nowiki>[[DavidJanes]]</nowiki>）、リンクを編集するのではなく、実際のユーザーページへのリダイレクトを作成してください。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# もしページを移動させる時は、メニューにある「ここにリンクしている他のページ」を確認し、リンク切れがないよう修正してください。
# Please use U.S. English ([[en-US]]) spellings of common 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].[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]. Exception: Please use and maintain the proper native spellings of proper nouns, e.g. "BT Centre", "Business Design Centre, London, UK", "Centre of Canadian Studies", etc. [<abbr title="guideline created due to numerous edits by Ameer Dawood">src:AD</abbr>([http://microformats.org/wiki/Special:Contributions/AmeerDawood])]
# 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].
# Add whitespace to markup examples for readability. Real world markup examples are often whitespace collapsed, often with all the markup/content on a single line of text. Please add whitespace (e.g. returns between elements, indentation to indicate element depth) to markup examples.
# 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! [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# Please do not remove apparently <span id="brokenlinks">broken links</span> (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]. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# <span id="avoid-personalizing-proposals">Avoid labeling proposals with people's names.</span> Instead please label a proposal using a summary of some (perhaps unique) technical aspect of the proposal. The reasons for this are to avoid overly "personalizing" an idea and having the idea be judged (positively or negatively) by the author associated with it rather than the merits of the idea itself, to avoid having criticisms of the idea even remotely appear as if they are criticisms of the person, and to avoid having a specific person feel like they must defend attacks on an idea as if they were attacks on their person. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# <span id="avoidsplitting">Avoid splitting most pages.</span> Do not split, divide, sub-divide, or otherwise reorganize pages unless you are one of the primary authors of such pages. The reason is that you may not understand what the authors/creators of that page had/have in mind for the organization and growth of the content of the page, and by splitting it or reorganizing it, you might actually cause them <strong>more</strong> work and inconvenience, as well as raising the barrier to editing and/or contributing to the page for new folks as well, thus discouraging community participation. [[Admins]] will likely revert such splits. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>([http://microformats.org/wiki?title=to-do&diff=24428&oldid=24400] [http://microformats.org/wiki?title=to-do&diff=24992&oldid=24707])]
# If you do see a need to split a page which you are not one of the primary authors of, first add notes in the page in-place where you think splits need to occur, and how you think they should occur, before making any split, so that the primary author(s) have a chance to see and follow-up with refinements/changes on how the pages should be split. When deciding how to split pages, consider doing so in ways that both make it easier for new contributors to add information, making it easier for people to iterate, and making it easier for people looking from a real world perspective to find the information. See [[how-to-split-pages]] for more details. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>([http://microformats.org/wiki?title=hcard-examples-in-wild&diff=0&oldid=24726])]
# In general, avoid doing large "clean up" operations on the wiki for the same reasons as avoiding splitting most pages. [[Admins]] will likely revert such large re-organizations of pages and encourage incremental improvements, and suggesting larger improvements to the primary page authors. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]

== 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 for people using text-reading software and other assistive technologies ([http://www.kent.gov.uk/NR/rdonlyres/489181F9-B134-455E-98A3-EE75722400E2/11935/technicalguidance0708.pdf] PDF) <strong>(list and versions of text-reading software & other agents affected needed)</strong>.
#Do not use styles or write in ways which contravene [http://www.w3.org/TR/WCAG10/full-checklist.html Web Content Accessibility Guidelines 1.0]. For example, do not rely on color alone to convey information; mark up lists and list items properly.

== Wiki Cleaning ==

「[[spam-removal|スパムの削除]]」をご覧ください。

Wiki上で大掛かりな削除作業が必要と思われる状況を発見した場合、あなた自身で作業するよりもIRCチャンネルまたは microformats-discuss メーリングリストから管理者にご連絡ください。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]

== Related ==
* [[mediawiki-customization|MediaWiki のカスタム化]]」- このマイクロフォーマットWikiと典型的な MediaWiki の違いについての簡単な説明があります。主に、[[how-to-play-ja|how-to-play]] および [[naming-conventions-ja|命名規則]]を使いやすくするためにカスタム化を加えています。
* [[wiki2]]
* [[wiki-better-than-email]]
* [[how-to-play-2]]

html5-ja

2009-12-01T04:48:50Z

IwaiMasaharu: /* article element */ 翻訳

<h1>Microformats in HTML 5</h1>

''This page is to document '''future''' use of microformats in [http://www.w3.org/html/wg/html5 HTML 5]. None of the items documented are supported now, and may change upon proper development within the microformats community, or changes in the HTML 5 specification. This page is to track HTML5 enabled enhancements to microformats, and issues that HTML5 raises. It may be used to track issues which we need to push back into the HTML 5 development process.''

If there are things that Microformats would like to mark up that aren't handled by HTML5 explicitly, please let the WHATWG know, so we can improve HTML5. This is how <code>time</code> came to be, for instance.

==New features in HTML5==

=== time element ===
'''<code>time</code> element for representing date times'''. In HTML5, the machine form of datetimes can be represented natively. It should be possible to replace the date-time design pattern with native HTML.
* <code>time</code> takes an optional <code>pubdate</code> attribute, to indicate the publication date of an <code>article</code>. Synonymous with [[hAtom]] <code>published</code>, may imply [[hAtom]] <code>updated</code>, may imply [[hReview]] <code>dtreviewed</code>, may imply [[hListing]] <code>dtlisted</code>

=== article要素 ===
'''<code>article</code>'''要素は、ページ内にあるコンテンツの、主要な、独立した部分です。[[hAtom]]の<code>hentry</code>と概ね同じものです。明示的な<code>hfeed</code>ブロック内の<code>hentry</code>のように解釈されるのでしょうか?

=== microdata ===
'''[[microdata]]'''. HTML5 provides a set of attributes and associated DOM APIs for extracting data from web pages.
* <code>itemprop</code> attribute is a more specific version of <code>class</code>, for field names
* <del><code>subject</code> attribute allows semantically linking within the page. Conceptually similar to the [[include-pattern]].</del>
* <code><itemref refid="x" /></code> allows semantically linking within the page. Conceptually similar to the [[include-pattern]].
* <code>content</code> attribute on the <code>meta</code> element can be used to invisibly include data. Conceptually similar to the [[value-class-pattern]].
* <code>itemscope</code> attribute identifies blocks to be marked as structure data. Conceptually similar to the [[mfo]] brainstorming?
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)

==== microdata vocabularies ====
* [http://dev.w3.org/html5/mdvcard/ microdata vCard] - use [[hCard]] instead, taking into account the [[hcard-faq|hCard FAQ]] and [[hcard-issues-resolved|resolved]]+[[hcard-issues-closed|closed issues]]. hCard 1.0.1 (under development) is incorporating these errata. Avoid the "microdata vCard" vocabulary as it is an out-of-date fork/snapshot of hCard.
* [http://dev.w3.org/html5/mdvevent/ microdata vEvent] - use [[hCalendar]] instead, taking into account the [[hcalendar-faq|hCalendar FAQ]] and [[hcalendar-issues-resolved|resolved]]+[[hcalendar-issues-closed|closed issues]]. hCalendar 1.0.1 is incorporating these errata. Avoid the "microdata vEvent" vocabulary, as it is an out-of-date fork/snapshot of hCalendar's vevent root class name and applicable properties.
* [http://dev.w3.org/html5/mdwork/ microdata Licensing Works] - see also [[licensing-brainstorming]]

=== data attributes ===
'''<code>data-</code> naming convention for tag attributes'''. the draft specification states that any attribute that starts with "data-" will be treated as a storage area for private data.
* Note that the data-* stuff is explicitly <em>not</em> for microformats. Those attributes are defined in such a way that browsers will never do anything special with them, ever. They are intended for script authors to have a space in which they can play without ever clashing with anything the browser does. There may be some cases of private [[poshformats]] that are never intended for interchange that may be used in data-* attributes.

== Current microformat compatibility ==
There seems to be no issue with current implementation of the following microformats in HTML 5:
* [[hcard]]
* [[xfn]]

== Requests ==
* "how to use with HTML5" sections that include (a) microformats examples that use [[HTML5]], and (b) microformats parsing details that specify what to do (if anything special is required) with HTML5 elements (e.g. how to parse the <code>time</code> element for dates and times for microformats). See (and add to if necessary) :
** [[hcard-brainstorming#how_to_use_with_HTML5|hCard brainstorming - how to use with HTML5]]
** [[hcalendar-brainstorming#how_to_use_with_HTML5|hCalendar brainstorming - how to use with HTML5]] e.g. hCalendar with the <code>time</code> element
** [[citation-brainstorming#how_to_use_with_HTML5|citation brainstorming - how to use with HTML5]]
** if nothing special is required for HTML5, then after performing the analysis, that should be noted as well, for the purpose of clarity.

==Issues==
<div class='discussion issues'>
* '''The <code>rev</code> attribute has been removed'''. In HTML5, <code>rel</code> and <code>rev</code> are no-longer paired, and the <code>rel</code> attribute nolonger describes the direction of a relationship. Microformats which use <code>rev</code> will need to use <code>rel</code> instead.
** Or something like data-rev="vote-for"
*** As above, <code>data-</code> attributes are for application-context functionality, ''not'' shared vocabularies. Further, the HTML5 specification makes <code>rel</code> the correct attribute to use, regardless of direction, through the changed specification. --[[User:BenWard|BenWard]] 17:53, 12 May 2009 (UTC)
* '''The <code>profile</code> attribute has been removed'''. In HTML, the <code>profile</code> attribute from the <code>head</code> has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in <code>link</code> elements instead, or even as a custom HTTP header. See [[grddl]] and [[profile-uris]]
** See [[rel-profile]] which is the replacement for the profile attribute. [[User:Tantek|Tantek]] 23:24, 5 November 2009 (UTC)
* '''Microdata <code>itemprop</code> duplicates <code>class</code> data'''. the new attribute itemprop is designed to hold some meaningful data about an element, but class already exists to hold this data. Unsure of reasons why itemprop required?
** This is because microdata is designed to be generically parsable, even when the parser does not understand the vocabulary. As such, property names have to be on an explicit attribute, not shared with other, non-data classnames. --[[User:BenWard|BenWard]] 21:12, 4 September 2009 (UTC)
</div>

== see also ==
* [[HTML3]]

html5-ja

2009-12-01T04:41:05Z

IwaiMasaharu: english: 2009-11-05T23:30:00

<h1>Microformats in HTML 5</h1>

''This page is to document '''future''' use of microformats in [http://www.w3.org/html/wg/html5 HTML 5]. None of the items documented are supported now, and may change upon proper development within the microformats community, or changes in the HTML 5 specification. This page is to track HTML5 enabled enhancements to microformats, and issues that HTML5 raises. It may be used to track issues which we need to push back into the HTML 5 development process.''

If there are things that Microformats would like to mark up that aren't handled by HTML5 explicitly, please let the WHATWG know, so we can improve HTML5. This is how <code>time</code> came to be, for instance.

==New features in HTML5==

=== time element ===
'''<code>time</code> element for representing date times'''. In HTML5, the machine form of datetimes can be represented natively. It should be possible to replace the date-time design pattern with native HTML.
* <code>time</code> takes an optional <code>pubdate</code> attribute, to indicate the publication date of an <code>article</code>. Synonymous with [[hAtom]] <code>published</code>, may imply [[hAtom]] <code>updated</code>, may imply [[hReview]] <code>dtreviewed</code>, may imply [[hListing]] <code>dtlisted</code>

=== article element ===
'''<code>article</code>''' element for major, independent compositions of content within a page. Perhaps synonymous with [[hAtom]] <code>hentry</code>. Could be parsed as <code>hentry</code> within explicit <code>hfeed</code> blocks?

=== microdata ===
'''[[microdata]]'''. HTML5 provides a set of attributes and associated DOM APIs for extracting data from web pages.
* <code>itemprop</code> attribute is a more specific version of <code>class</code>, for field names
* <del><code>subject</code> attribute allows semantically linking within the page. Conceptually similar to the [[include-pattern]].</del>
* <code><itemref refid="x" /></code> allows semantically linking within the page. Conceptually similar to the [[include-pattern]].
* <code>content</code> attribute on the <code>meta</code> element can be used to invisibly include data. Conceptually similar to the [[value-class-pattern]].
* <code>itemscope</code> attribute identifies blocks to be marked as structure data. Conceptually similar to the [[mfo]] brainstorming?
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)

==== microdata vocabularies ====
* [http://dev.w3.org/html5/mdvcard/ microdata vCard] - use [[hCard]] instead, taking into account the [[hcard-faq|hCard FAQ]] and [[hcard-issues-resolved|resolved]]+[[hcard-issues-closed|closed issues]]. hCard 1.0.1 (under development) is incorporating these errata. Avoid the "microdata vCard" vocabulary as it is an out-of-date fork/snapshot of hCard.
* [http://dev.w3.org/html5/mdvevent/ microdata vEvent] - use [[hCalendar]] instead, taking into account the [[hcalendar-faq|hCalendar FAQ]] and [[hcalendar-issues-resolved|resolved]]+[[hcalendar-issues-closed|closed issues]]. hCalendar 1.0.1 is incorporating these errata. Avoid the "microdata vEvent" vocabulary, as it is an out-of-date fork/snapshot of hCalendar's vevent root class name and applicable properties.
* [http://dev.w3.org/html5/mdwork/ microdata Licensing Works] - see also [[licensing-brainstorming]]

=== data attributes ===
'''<code>data-</code> naming convention for tag attributes'''. the draft specification states that any attribute that starts with "data-" will be treated as a storage area for private data.
* Note that the data-* stuff is explicitly <em>not</em> for microformats. Those attributes are defined in such a way that browsers will never do anything special with them, ever. They are intended for script authors to have a space in which they can play without ever clashing with anything the browser does. There may be some cases of private [[poshformats]] that are never intended for interchange that may be used in data-* attributes.

== Current microformat compatibility ==
There seems to be no issue with current implementation of the following microformats in HTML 5:
* [[hcard]]
* [[xfn]]

== Requests ==
* "how to use with HTML5" sections that include (a) microformats examples that use [[HTML5]], and (b) microformats parsing details that specify what to do (if anything special is required) with HTML5 elements (e.g. how to parse the <code>time</code> element for dates and times for microformats). See (and add to if necessary) :
** [[hcard-brainstorming#how_to_use_with_HTML5|hCard brainstorming - how to use with HTML5]]
** [[hcalendar-brainstorming#how_to_use_with_HTML5|hCalendar brainstorming - how to use with HTML5]] e.g. hCalendar with the <code>time</code> element
** [[citation-brainstorming#how_to_use_with_HTML5|citation brainstorming - how to use with HTML5]]
** if nothing special is required for HTML5, then after performing the analysis, that should be noted as well, for the purpose of clarity.

==Issues==
<div class='discussion issues'>
* '''The <code>rev</code> attribute has been removed'''. In HTML5, <code>rel</code> and <code>rev</code> are no-longer paired, and the <code>rel</code> attribute nolonger describes the direction of a relationship. Microformats which use <code>rev</code> will need to use <code>rel</code> instead.
** Or something like data-rev="vote-for"
*** As above, <code>data-</code> attributes are for application-context functionality, ''not'' shared vocabularies. Further, the HTML5 specification makes <code>rel</code> the correct attribute to use, regardless of direction, through the changed specification. --[[User:BenWard|BenWard]] 17:53, 12 May 2009 (UTC)
* '''The <code>profile</code> attribute has been removed'''. In HTML, the <code>profile</code> attribute from the <code>head</code> has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in <code>link</code> elements instead, or even as a custom HTTP header. See [[grddl]] and [[profile-uris]]
** See [[rel-profile]] which is the replacement for the profile attribute. [[User:Tantek|Tantek]] 23:24, 5 November 2009 (UTC)
* '''Microdata <code>itemprop</code> duplicates <code>class</code> data'''. the new attribute itemprop is designed to hold some meaningful data about an element, but class already exists to hold this data. Unsure of reasons why itemprop required?
** This is because microdata is designed to be generically parsable, even when the parser does not understand the vocabulary. As such, property names have to be on an explicit attribute, not shared with other, non-data classnames. --[[User:BenWard|BenWard]] 21:12, 4 September 2009 (UTC)
</div>

== see also ==
* [[HTML3]]

rel-tag-ja

2009-03-20T12:31:53Z

IwaiMasaharu: sync: English: 2009-03-18T18:08:00

<entry-title>rel="tag"</entry-title>

__TOC__

== 仕様ドラフト 2005-01-10 ==
; 編者/作者
:[http://tantek.com/ Tantek Çelik]
:[http://epeus.blogspot.com/ Kevin Marks]

; 原案
:[http://powazek.com/ Derek Powazek]

=== 著作権 ===
{{MicroFormatCopyrightStatement2004-ja}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.

=== 特許 ===
{{MicroFormatPatentStatement-ja}}

== 概要 ==
[[rel-tag-ja|rel-tag]]は[[microformats-ja|microformats]]のひとつです。ハイパーリンクに<code>rel="tag"</code>を書き加える事により、リンク元のページに対しページ作者が定義した「タグ（キーワードやテーマ）」を関連づけることができます。
タグはblogの記事内容すべてに関係する言葉とは限りません。たとえば次のようなリンクでタグを関連づけるとします。

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">tech</a></nowiki></pre>

これは作者がこのWebページ（または内容の一部）に「tech」というタグをつけていることを意味します。

リンク先のページはWeb上に存在するべき（SHOULD）であり、またタグの意味はリンクテキストの内容よりも、リンク先のページが持つ情報が優先されます。たとえば次のようなマークアップでページに対しタグ付けを行ったとします。

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">fish</a></nowiki></pre>

URLの最後にある単語がタグの意味として扱われるので、この場合ページのタグは「fish」ではなく「tech」となります。

== rel-tagの意図、範囲 ==
rel-tagはWebページ（又はその一部）に「タグ付け」をする目的で作られました。このため、任意のURLやページ外部のコンテンツに対し、rel-tagによりタグ付けを行える様にはできていません。現在のページから外部のURLへのタグ付けの一般的な構文についての要望はありますが、rel-tagにおいてその議論はなされるべきでないと考えています。[[xfolk|xFolk]]や[[hreview|hReview]]にてURLのタグ付けについて考えられているので、そちらを参照してください。

タグを用いるシステムにおいては、タグの表現に特化したrel-tagは優れたフォーマットと言えるでしょう。

== XMDPプロファイル ==
http://microformats.org/wiki/rel-tag-profile

== タグスペースとタグの扱い ==
タグはURIの中に分かりやすい形で埋め込まれています、そのためURIからタグを機械的に抽出することが比較的容易です。具体的に説明すると、タグはURIパスの最後にある単語（一番後ろの"/"より後の文字列）となります。たとえば<pre><nowiki>http://www.example.com/tags/foo</nowiki></pre>というURIが示すタグは「foo」となります。

このため、ある二つのURIをタグとみなし比較する場合は、まず始めにタグをパスの最後から抽出することが推奨（SHOULD）されます。

''タグの抽出・比較についてはもう少し標準的な仕組みが必要だと考えています。''

rel="tag"を埋め込んだハイパーリンクが示す先はタグスペース（同じタグの付いた文書の一覧またはタグの定義）であるよう求められています。たとえば、リンク先の文書が次のURLで表されるとします。

<pre><nowiki>http://technorati.com/tag/tech </nowiki></pre>

この場合、この文書は「tech」というタグに関するタグスペースであるとみなされます。

タグとなる文字列はURLパスの最後にのみ記すことを許されています。これはクエリパラメータやフラグメント識別子がタグとして認識されないことを意味します。さて、次のURLはどう扱われるでしょうか。

<pre><nowiki>http://technorati.com/tag/tech?tag=fish#emu </nowiki></pre>

この場合も先述のとおり「tech」というタグに関するもので、「fish」や「emu」についてのものではないことに注意してください。

タグスペースに関する決まり事は「タグとなる文字列がURLパスの最後にあること」のみです。このためタグスペースはどのドメインにおいても提供可能となっています。ページ作者はいくつかのタグスペースを選びリンクすることで、特定の意味をタグに持たせることが可能です。たとえばWikipediaのページをタグスペースに用いる事ができます。

<pre><nowiki> http://en.wikipedia.org/wiki/Technology </nowiki></pre>

この場合、タグは「Technology」を指します。

URLの末にあるスラッシュは無視されます。つまり次のURL

<pre><nowiki> http://technorati.com/tag/Technology/ </nowiki></pre>
これをrel-tagに用いる場合、最後のスラッシュは取り除かれ、
<pre><nowiki> http://technorati.com/tag/Technology </nowiki></pre>
と同じ扱いを受けることになります。

== タグのエンコード ==
タグにおけるスペースは「<code>+</code>」又は「<code>%20</code>」へとエンコードして含めることが可能です。Unicode文字は[http://www.ietf.org/rfc/rfc3986.txt <nowiki>RFC 3986</nowiki>]で述べられている様にエンコードされます。たとえば次のようになります。

<pre><nowiki><a href="http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre" rel="tag">Santé et bien-être</a> </nowiki></pre>

Wikipediaをタグスペースとして利用する場合には「<code>%20</code>」を利用すべきです。Wikipediaは「+」を「<code>%2B</code>」へと置換してしまうため、通常ページのタイトルに存在しない「+」を表示させてしまうからです。

== 目にみえるメタデータとしてのタグ ==
<code>rel="tag"</code>を含んだハイパーリンクは、Webページ上に現れるよう期待されています。これはページ上に現れず、閲覧者の目に届く事がほとんどないmetaキーワードとrel-tagの大きな違いです。タグがWebページに表示されるため、metaキーワードよりも弾力的にキーワードspamなどの問題に対処することができると考えています。

タグのリンクが目に見えることにより、ページ閲覧者はそのリンクが悪用されたものかを簡単に知ることができます。このためリンクを用いた不正行為をある程度抑止できると考えています。どんな目に見えないメタデータが生成されているのかを知らないページ作成者にも効果的でしょう。

このため、<code><link rel="tag" href="..." /></code> のような目に見えないタグリンクの表現は実装されるべきではありません（SHOULD NOT）。

== rel-tagの利用例 ==
このセクションは'''参考情報'''です。

以下はrel-tagを実装したWebサイトのリストです。rel-tagをパースしている、又はタグのインデックスを作っていたり、タグの整理が行われているWebサイトの例をお探しなら、きっとこのリストが役立つでしょう。もしあなたがrel-tagを利用していたら、気軽に'''このリストの上'''に追加してください。リストが大きくなったら、別のページにて紹介する予定です。

* [http://huffduffer.com/ Huffduffer] uses rel-tag on every page, pointing to its own tag space e.g. http://huffduffer.com/tags/microformats
* [http://www.pantrymothtrap.com/ Pantry Moth Traps] implements the rel-tag in articles where an authoritative source is known. (for example in the article [http://www.pantrymothtrap.com/MothTrapsPick.html Moth Trap Picks] the tag [http://www.cleanertoday.com/tag/moth%20trap Moth Trap])
* [http://www.hightechcville.com/ HighTechCville] uses rel-tag on all the pages listing tagged content for [http://www.hightechcville.com/people people], [http://www.hightechcville.com/organizations organizations] and [http://www.hightechcville.com/events events] related to high tech in Charlottesville, VA.
* [http://skateboardspot.info skateboardspot.info] uses rel-tag in spotguide entries which are added to the site and categorized by the users (for example: [http://skateboardspot.info/cat/spotguide/action/view/id/1 “El Toro High School” spotguide entry]).
* [http://www.idoneos.com Idoneos.com] uses rel-tag for conceptual links to its own tag space, a collection of 'concepts' (mostly spanish).
* [http://www.professionalontheweb.com Professional On The Web] uses rel-tag for user entered tags which categorize web professionals and freelancers.
* [https://www.coderesort.com/p/epicode/wiki/CloudCuckoo CloudCuckoo] (secure site but open to all) an [http://www.episerver.com EPiServer] module distributed free by [http://www.interakting.co.uk Interakting], generates tag clouds with rel-tag links.
* [http://www.lifetime.com Lifetime.com] uses rel- and rev-tags in all content pages.
* [http://www.my-warehouse.de the my-Warehouse shopsystem] implements rel-tags in box headings and categories links.
* Joseph Bergantine uses tags to categorize [http://bergantinedesign.us/wallpaper/ wallpapers] and [http://bergantinedesign.us/blog/my-name-is-rachel-corrie blog posts]
* [http://www.codesignville.com Codesignville] uses rel-tag to indicate content categories.
* [http://www.bossalive.com BossaLive] uses rel-tag for tagging music. Publishes rel-tags for album, artist and genre.
** Also uses [[hcard|hCard]] on user profile pages.
* [http://www.qmpeople.com/ qmpeople] Uses rel-tag for translated tags into english, french and italian to meet new friends in different countries.
* [http://www.keevu.com Keevu.com] uses rel-tag to indicate content categories on most pages, like [http://www.keevu.com/venues venues]
* [http://www.amazingincredible.com Amazing Incredible] uses rel-tag on content pages
* [http://www.auctionlink.com.au AuctionLink]では[http://www.auctionlink.com.au/TagList/Auctioneers/ Auction Sales Listings]のタグにrel-tagを用いています。
** Could also use [[hcard|hCard]], e.g. on [http://www.auctionlink.com.au/Auctioneers/Auctioneer/Bonhams_Goodman_1/] [[User:AndyMabbett|Andy Mabbett]]
* Christian Hessは[http://www.hess-cr.com blog]と他のページでrel-tagを用いています。
* [http://spacedust.atspace.com/ Spacedust]はギャラリーページのマークアップにrel-tagを利用しています。
* [http://my.opera.com/dstorey/blog/ My Opera]では、全てのユーザのblogエントリがrel-tagを利用しています。
* [http://dev.opera.com/articles/view/making-wii-friendly-pages/ Dev Opera]では、記事のタグにrel-tagが使われています。
* [http://www.international.unt.edu UNT International]はほとんどのページにおいて、カテゴリをrel-tagで表現しています。
* [http://yedda.com Yedda] - Yeddaは利用者が自分につけたタグ、そしてYeddaにて質問された事柄につけられたタグにrel-tagを利用しています。
* [http://www.lingr.com Lingr]はユーザが入力したすべてのタグを表示しています。
* [http://odeo.com ODEO]では[http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html rel-tagを利用しています]。
* [http://eventful.com Eventful]ではユーザがつけたタグの表現に、rel-tagが使われています。
* [http://spinn3r.com Spinn3r] implements rel-tag as well as RSS and Atom subject and categories.
* [http://www.weboffate.com Web of Fate] publishes rel-tags for future predictions.

== 実装 ==
このセクションは'''参考情報'''です。

次に紹介されているリストは、rel-tagを実装しているアプリケーションのものです。もしあなたがrel-tagを利用したサービスやソフトウェアを開発していたら、気軽に'''このリストの上'''に追加してください。リストが大きくなったら、別のページにて紹介する予定です。

* [http://www.textcube.org Textcube.org] makes a blogging tool, Textcube which generates rel-tag for tags on blog posts.
* [http://hashtags.org/ HashTags] tags Twitter posts, converting "#example" into a tag of "example"
* [http://ikiwiki.info ikiwiki] generates rel-tag for all tagged pages (as of version 2.6)
* [http://www.hubtag.com HubTag] helps users find a unique tag across the web for their event - eg. JohnAndBettysWeddingWimbledonMarch07
* [http://www.necctar.com Necctar] is a search engine exclusively based on tag microformat parsing and processing. Necctar uses tags entered by bloggers to index the world wide web
* Nutchは[[rel-tag]]のパーサを[http://www.mail-archive.com/nutch-commits@lucene.apache.org/msg01014.html svnレポジトリにコミットしました]。
* [http://webstandards.org/ Web Standards Project]が提供している[http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver拡張スイート]を導入することにより、Dreamweaver 8でrel-tagを用いたタギングができます。
* スライドショー作成サービス[http://scooch.gr0w.com/ Scooch]では、作成者がスライドショーに埋め込んだタグのタグクラウドを見ることができます。
* Weblogシステム[http://www.s9y.org Serendipity]のFreetagプラグインは、エントリのタグ付けを可能とします。（FreetagプラグインはSPARTACUSのなかにあります。）
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf]は[http://textpattern.com/ Textpattern]でrel-tagや他のmicroformatsをテンプレートやエントリで利用可能とするプラグインです。[http://placenamehere.com/ Chris Casciano]により制作されました。
* [http://www.truist.com/blog/493/trutags-a-tagging-plugin-for-textpattern tru_tags]は[http://textpattern.com/ Textpattern]で、キーワード欄からエントリのタグ付けを可能とするプラグインです。
* [http://news.livejournal.com/86492.html?thread=24881884 LiveJournal]には[http://www.livejournal.com/support/faq.bml?cat=tags タグに関するサポートページ]が用意されています。
* [http://trac.labnotes.org/cgi-bin/trac.cgi/wiki/TagsLinks TagsLinks]を用いて、ページに埋め込まれたタグと、他のサービスが用意したタグスペースをつなげることができます。
* [http://dev.wp-plugins.org/wiki/BunnysTechnoratiTags WordPress用のタグ付けプラグイン]です。
** Note that some sites using WordPress (http://microformatique.com/ for instance) are getting incorrect tags. The tag is ?cat=12 instead of the actual tag value.
* [http://noone.org/blog/tags/Tagging Blosxom用のタグ付けプラグイン]です。
* Technoratiはrel-tagを実装した最初のサービスです。[http://technorati.com/tag/ Technorati Tags]から、Technoratiがインデックスしているタグを見ることが出来ます。
* [http://consumingexperience.blogspot.com/2005/12/updated-multiple-word-technorati-tag.html Bloggerでタグを利用するためのGreasemonkeyスクリプト]です。
* [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint]は[[User:DrewMcLellan|Drew McLellan]]による、rel-tagを検証するツールです。

== 参照 ==
=== 標準仕様 ===
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML 1]
* [http://gmpg.org/xmdp/ XMDP]
* RFC 3986ではURIの構文を規定しています。Section 3.3にURLパスとパスセグメントに関する記述があります。

=== 参考 ===
* [[hreview|hReview]]ではrel-tagを一般的なタグ、またレート付けに用いています。
* [[xfolk|xFolk]]はrel-tagを用いて、タグ付けされたリソースの分散型処理を可能としています。
* [http://developers.technorati.com/wiki/attentionxml Attention.XML]はrel-tagを用い、読者がページやweblogの投稿、又はフィードへのタグ付けを行えるようにしています。
* [[hcard|hCard]]では、rel-tagを用いたカテゴリの作成が可能です。
* [[hcalendar|hCalendar]]でも、rel-tagを用いたカテゴリの作成が可能です。
* [http://technorati.com/help/tags.html Using Technorati Tags]で、Technoratiにおけるタグの扱いを知ることが出来ます。
* rel-tagは http://developers.technorati.com/wiki/RelTag からの寄稿により作成されました。
* microformatique.comの[http://microformatique.com/?p=61 Know your rel-tag]に、rel-tagについての説明があります。

== ディスカッション ==
* フィードバックは[[rel-tag-feedback]]にてお願いします。
* [http://www.technorati.com/cosmos/referer.html rel-tagについて言及しているページ]も参照してください。
* これまでの経緯については[http://www.powazek.com/ Derek Powazek]による[http://www.powazek.com/2005/07/000532.html How Tags Happened at Technorati]をお読み下さい。

=== Q&A ===
* rel-tagに関して分からないことがありますか？それがrel属性に関する疑問ならば[[rel-faq|rel FAQ]]を、rel-tagに関する疑問であれば[[rel-tag-faq|rel-tag FAQ]]をお読み下さい。これらのページを読んでも疑問が解消されない場合は、[http://microformats.org/discuss microformats-discuss]にメールを投稿するとよいでしょう。

==Related pages==
{{rel-tag-related-pages}}

[[Category:Specifications]]
[[Category:rel-tag]]

POSH-ja

2009-02-26T16:43:26Z

IwaiMasaharu: create redirect

#REDIRECT [[posh-ja]]

how-to-play-ja

2009-02-26T16:32:07Z

IwaiMasaharu: sync: english: 2009-01-15T22:26:15

__NOTOC__
初めての方は[[introduction-ja|Microformatsの手引き]]をご覧ください。

<entry-title>How to Play</entry-title>

== ガイドライン ==
協力する前にこれらのガイドラインを読んでください。また、この内容は遵守してください。

# ページを編集したり作成したりする前にアカウントを作成してください。Please consider using your name, e.g. GivenFamily (FirstLast). [http://en.wikipedia.org/wiki/Wikipedia:Username Wikipedia Username guidelines] もご覧ください。You may use an alias (e.g. [[User:Adactio]], [[User:Phae]]). Please do not use organization names or other proper nouns (e.g. products, technologies).
# microformats.orgの[[:Category:public_domain_license|Public Domain Declarations]]をご覧ください。そして、[[Template:public-domain-release]]を自分のユーザーページに追加して、あなたのmicroformats.orgサイトへの2008年以前の貢献をパブリック・ドメインへ解放することも検討してみてください。
# はじめに[http://microformats.org/discuss IRCチャンネル（こちらがお勧め）か、メーリングリスト]に参加してみてください。(その前には[[mailing-lists]]を読んで下さい)
# もし、論理的な理由を越えて何か意見を書いたならば、あなたのユーザ名も一緒に書いてください。- これはMediaWikiのdatetimestampを使って簡単にできます。4つの半角「~」を以下のように並べます: <nowiki>~~~~</nowiki>
#*On the few occasions when it is necessary to edit others signed contributions (as opposed to general content), take care not to change their meaning.
#*If your logically reasoned statement is part of a discussion which disagrees with a previous comment, you may sign it with your username. However signing such statements is both not required, and may detract from the logically reasoned statement standing on its own (related: [[#avoid-personalizing-proposals|avoid personalizing proposals]]), and thus consider leaving such statements unsigned. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# このWikiには、[[POSH-ja|POSH]]やmicroformats(と[[picoformats]])に直接関係あるページだけを作成してください。[[data-portability]] in line with microformats [[principles]] is also encouraged. 無関係なページは削除されます。
# <span id="naming">ページの[[naming-conventions-ja|命名規則]]に従ってください。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span>
# Wikiのページで会話をしてはいけません。その用途には#3で挙げた[http://microformats.org/discuss mailing lists]を使ってください。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 妥当なXHTMLで記述するようにしてください。
# ソースコードを貼りつける場合、適当な長さで改行を入れてください。
# 見出しに「?」や句読点記号を入れないでください。これは、URLのフラグメント識別子（リンクのターゲットを表す部分）を短くすることにより、可読性を高めたり、コピー＆ペーストなどをしやすくするためです。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# <span id="lowercase-headings">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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]</span>
# 目次に表示させたくない見出しには <h1> タグや <h2> タグなどを使ってもかまいません。こういったタグを見つけても、「=」や「==」などを使ったスタイルの見出しに<strong style="text-transform:uppercase">変更しないでください</strong>。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 見出しのテキストを変更しないようにしてください（大文字と小文字間の変換や、上記のルールに従おうとするための変更も含む）。見出しはパーマリンクとして使われることが多いため、変更によって他で使われているリンク切れなどをひき起こす可能性があります。これらをふまえ、見出しをつける場合は注意して言葉を選んでください。どうしても変更が必要な場合、<code><nowiki><div id="oldheadingID"></div></nowiki></code> というコードで新しい見出しを囲み、"oldHeadingID" の部分を見出しパーマリンクを残すために必要な値にすることで、リンク切れを防ぐことはできます。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 当Wiki全体に関する変更や編集（例: 10数ページ以上のページに影響する編集など）を行わないでください。もしWiki全体のスタイルや編集のやり方を改善できるような意見があるようでしたら、その内容を[[to-do]]ページの該当セクションに追加した上で、メーリングリストなどを使ってコミュニティの他のメンバーがどう思うか聞いてみましょう。返事がない場合は、あまり興味がない、つまり暗黙的な却下というふうに理解してください。ただしWiki管理人は、スパム削除や他の編集によって壊れた部分の修正などのために、Wiki全体に関わる変更を加えることがあります。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 質問や問題提議に対し、「却下」だけなどの<span id="avoid-simple-contradictions">単純な反対意見で反応するのはやめましょう</span>。かわりに、短くてもいいので、元の質問や意見には含まれていなかった情報を加え、反対の理由を述べてください。Simple contradictions (like just inverting other statements on a page as if such an inversion was an argument), are a waste of time and space and to be avoided.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 赤文字のリンクを削除したり、ダミーコンテンツを置いた空の新規ページを作成しないでください。赤文字のリンクは、新規ページ作成の必要性があるという判断より作成されたものですが、リンク先が編集されていないのは、リンクの作成者が必ずしもそのページの内容に詳しくなかったり、時間がなかったりという理由からです。（ただし、現存しないマイクロフォーマット・タイプのページへのリンクなどは外すべきです）[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# Please do not add MediaWiki Categories. With the [[wiki-2|upgrade to the wiki]] we have begun using a very limited number of categories in order to present specifications and drafts differently than other wiki pages. For now if you think additional Categories would help the community, please make suggestions on the [[category-suggestions]] page. [<abbr title="guideline created due to one or more actions by Toby Inkster">src:TI</abbr>]. 以前は次のようになっていました。『MediaWiki の「カテゴリー」構造を使わないでください。このコミュニティは、MediaWikiの全機能を使わないことにしているからです。（その他の例：「Talk」ページ）』[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 手動で新規 "User:" リンクを作成しないでください。"User:" リンクは、ユーザーが自身の編集に <nowiki>~~~</nowiki> または <nowiki>~~~~</nowiki> の署名を加えたときのみ、自動で作成されるようにしましょう。こうすることで、間違ったログイン名にリンクを作成したりすることなく、各 "User:" ページが実際のログインときちんと対応するようになります。もし、 "User:" リンクにするべき赤文字のリンクを発見した場合（例: <nowiki>[[DavidJanes]]</nowiki>）、リンクを編集するのではなく、実際のユーザーページへのリダイレクトを作成してください。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# もしページを移動させる時は、メニューにある「ここにリンクしている他のページ」を確認し、リンク切れがないよう修正してください。
# Please use U.S. English ([[en-US]]) spellings of common 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].[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]. Exception: Please use and maintain the proper native spellings of proper nouns, e.g. "BT Centre", "Business Design Centre, London, UK", "Centre of Canadian Studies", etc. [<abbr title="guideline created due to numerous edits by Ameer Dawood">src:AD</abbr>([http://microformats.org/wiki/Special:Contributions/AmeerDawood])]
# 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].
# Add whitespace to markup examples for readability. Real world markup examples are often whitespace collapsed, often with all the markup/content on a single line of text. Please add whitespace (e.g. returns between elements, indentation to indicate element depth) to markup examples.
# 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! [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# 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]. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# <span id="avoid-personalizing-proposals">Avoid labeling proposals with people's names.</span> Instead please label a proposal using a summary of some (perhaps unique) technical aspect of the proposal. The reasons for this are to avoid overly "personalizing" an idea and having the idea be judged (positively or negatively) by the author associated with it rather than the merits of the idea itself, to avoid having criticisms of the idea even remotely appear as if they are criticisms of the person, and to avoid having a specific person feel like they must defend attacks on an idea as if they were attacks on their person. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]
# <span id="avoidsplitting">Avoid splitting most pages.</span> Do not split, divide, sub-divide, or otherwise reorganize pages unless you are one of the primary authors of such pages. The reason is that you may not understand what the authors/creators of that page had/have in mind for the organization and growth of the content of the page, and by splitting it or reorganizing it, you might actually cause them <strong>more</strong> work and inconvenience, as well as raising the barrier to editing and/or contributing to the page for new folks as well, thus discouraging community participation. [[Admins]] will likely revert such splits. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>([http://microformats.org/wiki?title=to-do&diff=24428&oldid=24400] [http://microformats.org/wiki?title=to-do&diff=24992&oldid=24707])]
# If you do see a need to split a page which you are not one of the primary authors of, first add notes in the page in-place where you think splits need to occur, and how you think they should occur, before making any split, so that the primary author(s) have a chance to see and follow-up with refinements/changes on how the pages should be split. When deciding how to split pages, consider doing so in ways that both make it easier for new contributors to add information, making it easier for people to iterate, and making it easier for people looking from a real world perspective to find the information. See [[how-to-split-pages]] for more details. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>([http://microformats.org/wiki?title=hcard-examples-in-wild&diff=0&oldid=24726])]
# In general, avoid doing large "clean up" operations on the wiki for the same reasons as avoiding splitting most pages. [[Admins]] will likely revert such large re-organizations of pages and encourage incremental improvements, and suggesting larger improvements to the primary page authors. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]

== 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 for people using text-reading software and other assistive technologies ([http://www.kent.gov.uk/NR/rdonlyres/489181F9-B134-455E-98A3-EE75722400E2/11935/technicalguidance0708.pdf] PDF) <strong>(list and versions of text-reading software & other agents affected needed)</strong>.
#Do not use styles or write in ways which contravene [http://www.w3.org/TR/WCAG10/full-checklist.html Web Content Accessibility Guidelines 1.0]. For example, do not rely on color alone to convey information; mark up lists and list items properly.

== Wiki Cleaning ==

「[[spam-removal|スパムの削除]]」をご覧ください。

Wiki上で大掛かりな削除作業が必要と思われる状況を発見した場合、あなた自身で作業するよりもIRCチャンネルまたは microformats-discuss メーリングリストから管理者にご連絡ください。[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]

== Related ==
「[[mediawiki-customization|MediaWiki のカスタム化]]」ページに、このマイクロフォーマットWikiと典型的な MediaWiki の違いについての簡単な説明があります。主に、[[how-to-play-ja|how-to-play]] および [[naming-conventions-ja|命名規則]]を使いやすくするためにカスタム化を加えています。

faq-ja

2007-10-27T22:05:49Z

IwaiMasaharu: sync: english: 10:56, 14 Oct 2007

<h1> Microformats FAQ </h1>

microfotmatsについてよく聞かれる質問とその答えのページです。 For frequently asked questions from the [[press]], see [[press-faq]].

If you're looking for a microformat for marking up FAQs, see [[question-answer]].

__TOC__

== Wiki特有の質問 ==
===Q: ''ユーザー名はどうやって作りますか? どのようなユーザー名が望ましいですか?''===

A: まずは、 http://en.wikipedia.org/wiki/Wikipedia:Username を読んでください。また、ユーザー名としては、ペンネームやハンドルなどよりも本名の方が好まれます。本名を用いると、より高い透明性や責任を伴うと考えられるからです。さらに、ユーザー名の最初の文字は大文字である必要があります。これは登録の際に最も問題になることの一つです。ユーザー名としては、例えば「RyanKing」のようにあなたの氏名のWikiCaseバージョンはどうでしょうか?

== Email list ==
===Q: ''I've joined the discussion mailing list but am not seeing my replies anywhere. Why?''===

A: There is no moderation on microformats-discuss, but it only accepts posts from subscribers. You MUST post to microformats-discuss using the email address you used to subscribe.

===Q: ''What does "The message's content type was not explicitly allowed" mean?'' ===

A: Please go read [http://microformats.org/mailinglists-policies/ mailinglists-policies]. In particular note:
<blockquote>
'''No HTML or RTF e-mail''' period, end of story, full stop. Your mail client should let you configure it so you can send plain text messages. Make use of this ability or else there are no guarantees that anyone will be able to read your email.
</blockquote>
The mailing lists are set up to automatically reject email that is sent as text/html. Thus please configure your email client to send plain text (text/plain) email.

== microformatについての基本的な質問 ==
===Q: ''What does ''xxx'' mean?''===

A: See our [[glossary]].

===Q: ''Who uses microformats?'' ===

A: See a list of [[notable-users|some notable users]]; [[examples-in-wild|other microformat users]] and [[implementations|tools using microformats]].

===Q: ''When should I use a microformat? What are they for?"===

A: You are writing some HTML that contains useful human-readable information (such as a piece of contact information). You say to yourself: I would like to mark this up with some classes now for styling. You look up the relevant microformat, and you
pull in the standard names. You don't have to make your own up, and now your page is machine-readable too. Bonus!

Microformats are designed to make the data you already publish for humans available to machines. It allows applications as simple as cut-and-paste or as complex as a search engine to use your data effectively.

===Q: ''microformatsは(X)HTMLに依存していますか?''===

A: Microformatsは埋め込んで使うものです。(X)HTMLやRSS、Atomなどに埋め込むことができます。

===Q: ''microformatsは素晴らしいと思います。私にも何か協力できることがありますか?''===


A: Take a look at [[get-started]] for how to implement microformats yourself, and the [[to-do]] list for things to help out with. See http://microformats.org/discuss to see some ways to join the conversations about microformats.

===Q: ''I'd like to make a donation to the microformat cause. How can I do this?''===

A: Thank you for your willingness to support microformats. We've only recently started this site and have decided that while we are figuring out exactly how to accept donations, we will be passing along donations to other good causes. Please consider donating to another cause like Red Cross, perhaps directed to help victims of recent natural disasters.

===Q: ''microformatsにはどのような実装がありますか?'' ===

A: [[implementations-ja|実装]]ページを見てください。

===Q: ''Which microformats should I implement?''===

A: Chances are you that your website already has data very similar to several microformats. For example, you probably have people and/or their contact information somewhere. That information could be marked up with [[hcard|hCard]], see the [[hcard-authoring|hCard authoring]] page for step by step instructions. If you are publishing press releases, try using [[hatom|hAtom]].

===Q: ''Do you have any link badges I can add to my website/blog?''===

A: There are some [[buttons]] but we can certainly use more! Please contribute what you come up with!

===Q. ''Are there any tools that support microformats?''===

A. Yes...tons... [[implementations]].

===Q. ''Is there a way to indicate that a given web page contains markup that conforms to one or more microformats?'' ===

A. The HTML HEAD element's '<code>profile</code>' attribute alerts applications to the potential presence of microformats. The [http://www.w3.org/TR/1999/REC-html401-19991224/struct/global.html#h-7.4.4.3 W3C HTML Specification] describes more about the profile attribute, and the [http://gmpg.org/xmdp/description XMDP description] documents how it is used.

===Q. ''What about using new URI schemes instead of class names, e.g. for geo information?''===

A. In general, it is more work, and less content-publisher friendly, to ask publishers to use URI schemes instead of class names.

Authors aren't publishing links to geo information.

They're publishing *visible text* of [[geo]] information.

So the easiest thing to do, for the author, is to leave it as visible text.

Thus, it makes the most sense to do the simple thing of just wrapping that
visible text with a little bit of markup, rather than asking the author to
move (or copy) it into an attribute, which may or may not require a
reformatting of the data as well.

It would make sense from a usability persepective to hyperlink geo information to a maps page or something, so that clicking it actually does something. If you forced them to use a hypothetical "geo:" protocol instead, then that would interfere, since you can only hyperlink something to one destination.

===Q: ''Who controls microformats?''===

A: An open community. Microformats are open standards licensed under Creative Commons Attribution. Much of the work here was begun on [http://developers.technorati.com/wiki Technorati's Developer Wiki], but Technorati has since divested control of these microformat standards to the open community here. The microformats.org domain is registered to Rohit Khare(see [http://whois.uberdose.com/microformats.org Whois microformats.org]), CommerceNet is graciously hosting the servers, but claims no control over microformat standards. Anyone may follow the established [[process]] and contribute towards the development of microformat standards.
Any required [[governance]] of the microformats IRC channel, wiki, and mailing lists (and very little ''has been'' required) is discussed by a group of volunteer administrators, who are listed on that page.

===Q: ''Who is the registrar for microformats?''===

A: There is no central registry. Microformats are registered in a distributed manner using profiles. For more information on profiles see http://microformats.org/wiki/profile-uris and http://gmpg.org/xmdp/

Conflicts and interoperability are managed through social processes rather than a formal registry. Current microformat profiles can be found at http://gmpg.org, http://w3.org, and http://microformats.org.

===Q: ''So multiple microformats with the same name can be valid?''===

A: Yes. The community at microformats.org can hopefully play a role in determining which is preferred by bringing interested folks together in one place and helping them resolve that question. As long as each microformat maintains a valid profile, each can be used effectively.

===Q: ''How do I validate my microformated content?''===

A: Currently there is no automatic general-purpose validator for microformats (See [[to-do#for_all_microformats|To Do - for all microformats]]). There are however some microformat-specific tools listed on the [[implementations]] page which can help with validation. [https://addons.mozilla.org/firefox/4106/ Operator] does a good job of compliant parsing for microformats in general. For [[hcard|hCard]], try the [http://feeds.technorati.com/contacts/ Technorati Contacts Feed service]. For [[hcalendar|hCalendar]], try the [http://feeds.technorati.com/events/ Technorati Events Feed service]. Also, posting your examples to the [http://microformats.org/discuss microformats-discuss mailing list], and adding them to the respective examples/implementations sections/pages will very often get folks from the community to review and validate them for you.

===Q: ''How do microformats breach language barriers?''===
'''Would we have to "force" non-English speaking web page developers to use something like class="name" (as opposed to "namen" or "nom") for their productions to be properly indexed by agents?'''

A: Yes, but that's no different to using English words like "class", "span" or "head". This was briefly discussed on the microformats-discuss list most recently as "Language Maps" but has been raised before that. Some folks have raised the issue that microformats use English names for properties, and they would like alternate (non-English) names in other (natural) languages, and perhaps try to establish a mapping between them. As microformats property names are based on existing standards (see [[process]], and [[naming-principles]]), this is another problem that is far outside the scope of microformats. As Ryan King put it, this is a pre-existing (unsolved) "problem" with English-based HTML, the English-based CSS, the English-based HTTP and so on. Note that this is NOT about the internationalization of the content and data itself - which is of course an excellent goal, advocated and promoted by microformats and the standards they are based on (e.g. W3C, IETF). This is purely about the names of the properties (and enumerated values) in the formats. See also [[internationalization]].

===Q: ''How come microformats sometimes to linger as Drafts even though they seem usable?'' ===

A: [http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F Tantek] went over this at the recent [http://2007.sxsw.com/interactive/programming/panels/?action=show&id=IAP060234 The Growth and Evolution of Microformats] panel at [http://en.wikipedia.org/wiki/South_by_Southwest SXSW]. He conveyed that it was important to have a basic software implementation -- even an experimental one -- before moving a format from Draft to Specification. It can sometimes be hard to recognize subtle inconsistencies within a format by eye; however, in the process of implementing a format-reader in code, inconsistencies (if any) can become much more noticeable (due to [[dry | DRY / Don't Repeat Yourself]], among other programming best practices). Then, once such a tool has been created (in effect, confirming the programmability of the format), it can be transitioned to a Specification (so as to encourage other machine-based implementations).

== 新しいmicroformatsの作成や提案について ==

===Q. ''I would like to author a new microformats open standards specification for my site/business. How do I get started?''===

A. The first thing to do before attempting a new microformat open standard is to make as much use of [[POSH]] and existing [[microformats]] open standards as possible in whatever site you are looking to mark up with your new microformat, as a way of learning what is left to be done. That is, at a minimum first:
* Mark up all people and organizations as [[hcard|hCards]].
* Mark up all events and time based things as [[hcalendar|hCalendar]] events.
* Mark up all reviews as [[hreview|hReviews]].
* etc.
Then join the microformats [http://microformats.org/discuss discuss list], and ask folks what they think of your use of the microformats and if it can be improved.

From that experience you will then be able to figure out what is left to be specified. Otherwise it is too hard to approach the "whole problem".

Once you have completed that, take a look at the microformats [[process]] for how to walk through the steps of creating a new microformat, and note the specific problem you are trying to solve to the microformats-discuss list. This will help you find more people to help you solve the problems you are trying to solve.

===''Q 過去に提案されたmicroformatsのアイデアにを知りたいのですが、どうすればいいですか?''===

A. 提案されて却下されたmicroformatsのリストがありますので、それをチェックしてください。
* [[rejected-formats]]

===Q. ''What if I can't find real-world examples of a standard I'd like to propose?''===

A. If we can't find real-world examples of the '''types of data''' a proposal would address, it's probably not suitable for a microformat. If we only can't find real-world examples of the '''specific markup''' a proposal would use for that data, however, that's not really a problem. It's actually the lack of such standard markup in real-world publishing around a specific problem that suggests the need for increased consensus.

== それぞれのmicroformasに関する質問 ==
個別のmicroformatsに関する質問については、それぞれのFAQを見てください。
* [[hatom-faq]]
* [[hcalendar-faq]]
* [[hcard-faq]]
* [[hreview-faq]]
* [[rel-faq]]
* [[rel-tag-faq]]
* [http://gmpg.org/xfn/faq xfn-faq]
* [[xfolk-faq]]
* [[xmdp-faq]]
* [[xoxo-faq]]

== Class interactions ==

===Q. ''ページスタイリング上の問題が発生するようなclass名はありますか?''===

A. あるかも知れません。ただ、仮に問題が発生したとしても、文脈セレクタを用いることで容易に回避できるでしょう。

===Q. ''How does the use of class values for semantics interact with the use of class values for attaching CSS styles?''===

A. The class attribute takes a space separated set of class names [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 HTML4 reference]. Thus both author and microformat defined class names may be used in the same class attribute. In addition, microformat class names provide the author with a consistent set of class names to use for styling. If the author is already using using specific class names, they can continue to do so, and include microformat class names. If the author is already using a class name that happens to also be a microformat class name, then the author may want to consider using contextual CSS class selectors to make sure that avoid any unintentional styling effects.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://tantek.com/log/2004/07.html#classmeaningnotshow Class For Meaning Not For Show]
* [http://www.meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competant Classing], by Eric Meyer for discussion of choosing class names in (X)HTML
* [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling] - Ryan King dispells common misconceptions about the ''HTML'' class attribute.

== <code><div></code>と<code><span></code>のセマンティクス ==

===Q. ''Is it semantically meaningless to use divs?'' ===

A. Yes, both <code><div></code> and <code><span></code> have nearly no semantics. <code><div></code> can be used to represent a "division" of the page content. Similarly <code><span></code> can be used to reperesent that that "span" of text has some meaning, but the specifics of what that meaning is undefined by the <code><span></code>.

===Q. ''Does the use of <code><div></code> and <code><span></code> elements add any semantics to web pages?''===

A. According to the [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.4 HTML 4 spec], <code><div></code> and <code><span></code> "offer a generic mechanism for adding structure to documents." Their only meaning is in dividing documents into sections, and as such, their presence implies that the content within has a specific, but undefined by the element markup, semantic. Thus they are nearly semantic-free.

===Q. ''Why do the examples on the wiki use <code class="element"><span></code> and <code class="element"><div></code> for nearly everything?''===

A. <code class="element"><span></code> and <code class="element"><div></code> are generic elements in HTML. When you use microformats, you should pick the most specific semantic element available for the semantics you are trying to express. You might, for example, apply <code>class="vevent"</code> to a <code><nowiki><tr></nowiki></code>, or <code>class="vcard"</code> to a <code><nowiki><p></nowiki></code>.

== classのセマンティクス ==

===Q. ''How will microformat class names impact page size?''===

A. You probably won't notice any impact on page size when authoring with microformats. Our experience is that people use comparably sized class names, and [[semantic-class-names|semantic class names]] are now considered an industry best practice. Some sites are successfully publishing millions of microformats, and we haven't heard any complaints yet. You are more likely to gain space savings by more fully adopting [[microformats#the_microformats_principles|the principles of microformats]], and eliminating tables for layout.
<span class="todo">''TODO: Consider creating a new section for web authoring tips? Or at least linking to another site that advocates good authorship.''</span>

===Q. ''1つの要素に複数のclass名を付けることはできますか?''===

A. できます。class属性の値は、空白区切りを入れることで複数のclass名を書くことができます。例えば次のようになります。
<p class="todo idea">Write high quality and simple mark-up.</p>

W3C HTML 4.01 Specificationのclass属性についての記述も見てください: [http://www.w3.org/TR/html401/struct/global.html#adef-class 7.5.2 Element identifiers: the id and class attributes]

===Q. ''Do (X)HTML class names have semantics?''===

A. The HTML4 specification does not define any particular class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], nor does it define any particular semantic for class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], except that they "may be used for general user agent processing" [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF]. However, the [http://www.w3.org/TR/WD-htmllink-970328#profile" draft of "Hypertext Links in HTML"], allows for a "profile" to define meanings for those classes. [http://gmpg.org/xmdp/ XMDP] is a format for defining meta data profiles for (X)HTML, and thus an XMDP profile can be used to define the meanings of class names.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://www.w3.org/TR/WD-htmllink-970328 Hypertext Links in HTML]

===Q. ''I thought one of the main goals of CSS was to separate data from presentation. Isn’t this sneaking presentation back into data?''===

A. This is a quite commonly expressed objection to the way microformats uses class, but it's based on a misunderstanding of the way the class attribute in HTML was designed. Yes, class is very commonly,and appropriately used by web designers in conjunction with CSS to style pages, and in truth, it is often overused for that, but despite this, class, according to the HTML specification "has several roles in HTML", including [http://www.w3.org/TR/html4/struct/global.html#h-7.5.2 "for general purpose processing by user agents"].

Microformats utilize this second aspect of the class (and id) attribute, and do so legitimately. It is not an abuse of the class or id attribute to use it to add semantic context to a document. Nor is the use of class in and of itself presentational - in fact, it is an important mechanism for separating presentation from structured content.

For some more on using class semantically, here are some articles

* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer]
* [http://www.w3.org/QA/Tips/goodclassnames Use class with semantics in mind, W3C]
* [http://tantek.com/log/2004/07.html#d20t2359 More about the class attribute, Tantek Çelik]

== microformatsとspam ==
===Q. ''Given that Google now looks at hidden content as potential spam, will invisible microformats be considered spam?''===

A. It is advisable not to hide information in your site, regardless of whether it is microformatted or not. Microformats provide a mechanism for marking up ''visible'' content. Any mechanism for embedding ''invisible'' or hidden content risks being considered spam due to the fact that invisible (meta)data inevitably ends up being abused. Avoid invisible (meta)data. Publish visible data.

== abbrとtitleに関するデザインパターン ==
===Q. ''Why is ABBR being used when the title attribute is available on all HTML elements?''===

In the datetime design pattern the title attribute is used for the value of the property and the node value is used as the display value. <abbr title="value-here">Display-Here</abbr>.

A. The short answer is that <abbr> has the correct semantics.

The longer answer is that the value is often an abbreviated version of the formal value. Of course, if you don't want to use an <abbr>, you can use another element like this:

<abbr title="2006-12-31T12:59:59Z" class="dtstamp">New Year</abbr>

<span class="dtstamp">2006-12-31T12:59:59Z</span>

In addition, microformats encourage the content to be visible and thus prefer the text of an element rather than using the 'title' attribute or any other less visible alternative. The exception is made for datetimes and abbr due to the fact that microformats are for humans first, machines second. Thus the content of the abbr element is used to provide human visible content and the machine equivalent is placed in the less visible (but still easily verifiable) 'title' attribute.

== 要素の入れ子 ==
===Q. ''<code><span class="vcard fn org" id="club">...</span></code>としたいのですが、良いのでしょうか?''===

A. ダメです。[[hcard-faq#nesting-properties]]を見てください。

== See Also ==
* [[misconceptions]]

how-to-play-ja

2007-10-27T21:39:13Z

IwaiMasaharu: sync: english: 07:22, 19 Oct 2007

初めての方は[[introduction-ja|Microformatsの手引き]]をご覧ください。

<h1>How to Play</h1>
{{TOC-right}}
== ガイドライン ==
協力する前にこれらのガイドラインを読んでください。また、この内容は遵守してください。

# ページを編集したり作成したりする前にアカウントを作成してください。( [http://en.wikipedia.org/wiki/Wikipedia:Username Wikipedia Username guidelines] もご覧ください)
# microformats.orgの[http://microformats.org/wiki/Category:public_domain_license Voluntary Public Domain Declarations]をご覧ください。そして、[[Template:public-domain-release]]を自分のユーザーページに追加して、あなたのmicroformats.orgサイトへの貢献をパブリック・ドメインへ解放することも検討してみてください。
# はじめに[http://microformats.org/discuss IRCチャンネル（こちらがお勧め）か、メーリングリスト]に参加してみてください。(その前には[[mailing-lists]]を読んで下さい)
# もし、何か意見を書いたならば、あなたのユーザ名も一緒に書いてください。- これはMediaWikiのdatetimestampを使って簡単にできます。4つの半角「~」を以下のように並べます: <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.
# このWikiには、microformats(と[[picoformats]])に直接関係あるページだけを作成してください。無関係なページは削除されます。
# ページの[[naming-conventions-ja|命名規則]]に従ってください。
# Wikiのページで会話をしてはいけません。その用途には#3で挙げた[http://microformats.org/discuss mailing lists]を使ってください。
# 妥当なXHTMLで記述するようにしてください。
# ソースコードを貼りつける場合、適当な長さで改行を入れてください。
# 見出しに「?」などの句読点記号を入れないでください。これは、URLのフラグメント識別子（リンクのターゲットを表す部分）を短くすることにより、可読性を高めたり、コピー＆ペーストなどをしやすくするためです。
# 目次に表示させたくない見出しには <h1> タグや <h2> タグなどを使ってもかまいません。こういったタグを見つけても、「=」や「==」などを使ったスタイルの見出しに<strong style="text-transform:uppercase">変更しないでください</strong>。
# 見出しのテキストを変更しないようにしてください（大文字と小文字間の変換や、上記のルールに従おうとするための変更も含む）。見出しはパーマリンクとして使われることが多いため、変更によって他で使われているリンク切れなどをひき起こす可能性があります。これらをふまえ、見出しをつける場合は注意して言葉を選んでください。どうしても変更が必要な場合、<code><nowiki><div id="oldheadingID"></div></nowiki></code> というコードで新しい見出しを囲み、"oldHeadingID" の部分を見出しパーマリンクを残すために必要な値にすることで、リンク切れを防ぐことはできます。
# 当Wiki全体に関する変更や編集（例: 10数ページ以上のページに影響する編集など）を行わないでください。もしWiki全体のスタイルや編集のやり方を改善できるような意見があるようでしたら、その内容を[[to-do]]ページの該当セクションに追加した上で、メーリングリストなどを使ってコミュニティの他のメンバーがどう思うか聞いてみましょう。返事がない場合は、あまり興味がない、つまり暗黙的な却下というふうに理解してください。ただしWiki管理人は、スパム削除や他の編集によって壊れた部分の修正などのために、Wiki全体に関わる変更を加えることがあります。
# 質問や問題提議に対し、単純な反対意見（「却下」だけ、など）で反応するのはやめましょう。かわりに、短くてもいいので、元の質問や意見には含まれていなかった情報を加え、反対の理由を述べてください。
# 赤文字のリンクを削除したり、ダミーコンテンツを置いた空の新規ページを作成しないでください。赤文字のリンクは、新規ページ作成の必要性があるという判断より作成されたものですが、リンク先が編集されていないのは、リンクの作成者が必ずしもそのページの内容に詳しくなかったり、時間がなかったりという理由からです。（ただし、現存しないマイクロフォーマット・タイプのページへのリンクなどは外すべきです）
# MediaWiki の「カテゴリー」構造を使わないでください。このコミュニティは、MediaWikiの全機能を使わないことにしているからです。（その他の例：「Talk」ページ）
# 手動で新規 "User:" リンクを作成しないでください。"User:" リンクは、ユーザーが自身の編集に <nowiki>~~~</nowiki> または <nowiki>~~~~</nowiki> の署名を加えたときのみ、自動で作成されるようにしましょう。こうすることで、間違ったログイン名にリンクを作成したりすることなく、各 "User:" ページが実際のログインときちんと対応するようになります。もし、 "User:" リンクにするべき赤文字のリンクを発見した場合（例: <nowiki>[[DavidJanes]]</nowiki>）、リンクを編集するのではなく、実際のユーザーページへのリダイレクトを作成してください。
# もしページを移動させる時は、メニューにある「ここにリンクしている他のページ」を確認し、リンク切れがないよう修正してください。
# 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 ==

「[[spam-removal|スパムの削除]]」をご覧ください。

Wiki上で大掛かりな削除作業が必要と思われる状況を発見した場合、あなた自身で作業するよりもIRCチャンネルまたは microformats-discuss メーリングリストから管理者にご連絡ください。

== Related ==
「[[mediawiki-customization|MediaWiki のカスタム化]]」ページに、このマイクロフォーマットWikiと典型的な MediaWiki の違いについての簡単な説明があります。主に、[[how-to-play-ja|how-to-play]] および [[naming-conventions-ja|命名規則]]を使いやすくするためにカスタム化を加えています。

Main Page-ja

2007-09-27T07:25:59Z

IwaiMasaharu: /* ツール、テストケース、リサーチ */ 表現の変更

Microformats Wikiにようこそ！

初めての方は、[[introduction-ja|microformatsの手引き]]からどうぞ。編集を始める前に、[[how-to-play-ja]]を読んでください。

__TOC__

== はじめに ==

* まず、[[posh-ja|<abbr title="Plain Old Semantic HTML">POSH</abbr>]] とは何なのかを理解しましょう。
* 「[http://microformats.org/about/ microformatsについて]」のページ、[http://microformats.org/ 最新ニュース]、[[press|メディア紹介例]]や [[presentations-ja|プレゼンテーション]]、microformatsに関する[[books|書籍]]、[[podcasts|ポッドキャスト]]、[[screencasts|スクリーンキャスト]]などについて読んでみてください。
* 質問がある場合は、[[faq|よく聞かれる質問]]や[[glossary|用語集]]をご覧ください。
* 誰かから直接話を聞きたければ、[[events|microformatsのイベント]]に参加してみてください。

== 定義 ==

[http://microformats.org/discuss/ メーリングリスト]([[mailing-lists]])での一般的な定義は、「分散的開発を実現するために用いられる、セマンティクスをHTMLに埋め込む為のシンプルな仕様」です。もう少し細かく説明すると、microformatsは下記のように定義できます。
:分散的開発を実現するために用いられる
::Webにあるリソースそのものや、それを利用するツールやサービスを分散的に処理できるようにします。
:セマンティクスをHTMLに埋め込むための
::それぞれの分野に特化することで、各仕様が小さいものとなります。
:シンプルな仕様
:人間が解読できる(X)HTML/XMLドキュメントやAtom/RSSフィード、そしてプレーンなXMLでの提供
::現存するコンテンツの利用パターンを標準化することからはじめています。
::概略的で説明的なclass名を使い、ソースをみてもわかりやすくなっています。
::現存の相互運用できる規格に基づくことにより、汎用性が高まります。

「ブラウザーでWeb巡回しかしないんだ。それはまた20世紀的だね。」 -- [http://diveintomark.org Mark Pilgrim]

[[what-are-microformats|マイクロフォーマットとは何か]]について、[[what-can-you-do-with-microformats|マイクロフォーマットを使うと何ができるか]]についてさらに詳しい説明を読んでみてください。

== 協力の方法 ==

マイクロフォーマットをさらに発展させるために、こんなことができます。

* マイクロフォーマットをもっと使ってもらえるよう、[[advocacy|周りに伝えていく]]。
* [[testimonial|推薦文]]を書く。
* [[to-do|TO DOリスト]]にあるタスクを引き受ける。
*[http://microformats.org/discuss mailing lists] や [[irc-ja|IRCチャンネル]] に参加して、マイクロフォーマットに関する知識を深めたり、質問に答えたりする（投稿の前に、[[mailing-lists#General_guidelines|一般ガイドライン]]をお読みください）。
*世界中の人が利用しやすくなるよう、microformats wikiの翻訳を手伝う（[[Main_Page-ja#.E4.BB.96.E8.A8.80.E8.AA.9E.E3.81.A7.E3.81.AEmicroformats_wiki|他言語でのmicroformats wiki]]）。
* Wiki内の[[orphans|孤立したページ]]を見つけ、正しくリンクを貼る。
* 新しいマイクロフォーマットを提案する前に、あなたのサイトが[[POSH]]（セマンティックHTML）で書かれており、[[get-started|現存するマイクロフォーマットをすでに利用していること]]を確認する。その後、[[process|新規提案のプロセス]]についてよく読む。

== 仕様 ==

以下はオープンスタンダードとなった[[microformats-ja|microformats]]の仕様です。([[implementations|実装]]や[[examples-in-the-wild-ja|実際の使用例]]もご覧ください)

* [[hcalendar-ja|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator](翻訳中！)
* [[hcard-ja|hCard]] - [http://microformats.org/code/hcard/creator hcard creator](翻訳中！)
* [[rel-license-ja|rel-license]](翻訳完了)
* [[rel-nofollow-ja|rel-nofollow]](翻訳完了)
* [[rel-tag-ja|rel-tag]](翻訳完了)
* [[vote-links-ja|Vote Links]](翻訳完了)
* [http://gmpg.org/xfn/ XFN] ([[xfn-implementations|XFNの実装]]もご覧下さい)
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo-ja|XOXO]](翻訳中！)

== ドラフト ==

* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]]
* [[hresume-ja|hResume]](翻訳中！)
* [[hreview-ja|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== デザインパターン ==

{{design_patterns-ja}} 

== Exploratory Discussions ==
Per the microformats [[process]]:
実世界での[[examples|例]]の調査や分析、既に存在するフォーマット、またmicroformatsにできそうなもののブレインストーミングをまとめています。もし何かページを追加した場合、まず[[rejected-formats]]を見てから行ってください。
* alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]
*[[attention]]
* audio-info ([[audio-info-examples|examples]], [[audio-info-formats|formats]], [[audio-info-brainstorming|brainstorming]], [[audio-info-proposal|proposal]]) - Marking up information and metadata related to audio (speech, music, and sound in general). {{NewMarker}}
* blog description [[blog-description-examples|blog description examples]]
* blog info [[blog-info-examples|blog info examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]
* code [[code-examples| code examples]], [[code-brainstorming|code brainstorming]] {{NewMarker}}
* comment [[comment-problem-ja|コメントに関する問題]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[collection-description|collection description]] - for describing collections in libraries {{NewMarker}}
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]
* [[depend-examples]]: examples of dependency graphs, especially as they relate to software {{NewMarker}}
* [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) {{NewMarker}}
* directions [[directions-examples|directions examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]
* error messages [[error-message-examples|error message examples]], [[error-message-brainstorming|error message brainstorming]]
* forms [[forms-examples|forms examples]]
* file-format ([[file-format-examples|examples]], formats, brainstorming) - for the mark-up of file format information (size, type, codecs, bitrate, etc.) {{NewMarker}}
* genealogy [[genealogy-formats|genealogy exploration]]
* geo extensions
** [[geo-extension-strawman]] - extend geo for moons, other planets, etc.
** [[geo-elevation-examples]] - extend geo for representing altitude {{NewMarker}}
** [[geo-waypoint-examples]] - extend geo for representing routes and boundaries, using waypoints {{NewMarker}}
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]
* hash [[hash-examples|hash examples]]
* grouping ([[grouping-examples|examples]], [[grouping-formats|formats]], [[grouping-brainstorming|brainstorming]], [[grouping-proposal|proposal]]) - Metadata markup of items that should be grouped together. {{NewMarker}}
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]]
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]]
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]
* [[htodo|hToDo]]
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) {{UpdateMarker}}
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]
* [[mfo-examples|MFO examples]]
* music [[music-examples|music examples]] {{UpdateMarker}}
* news [[news-examples|news examples]] {{NewMarker}}
* photo note [[photo-note-examples|photo note examples]]
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}
* receipt ([[receipt-examples|examples]], [[receipt-formats|formats]], [[receipt-brainstorming|brainstorming]], [[receipt-proposal|proposal]]) - Marking up information and metadata related to purchase receipts. {{NewMarker}}
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|search results example]]
* show [[show-brainstorming|show brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|tagspeak examples]]
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].
* transit table [[transit-table-examples|transit table examples]]
* [[uid]]
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]
* [[wiki-formats|wiki formats]]
* 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]]
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])
*[[realestate-propertydetail|realestate-propertydetail brainstorming]]

== 例 ==
* [[examples-in-the-wild-ja|実際の使用例]]
* [[implementations|ツールの実装]]
* [[zen-garden|マイクロフォーマット Zen Garden]]

== ツール、テストケース、リサーチ ==

事例、コード、テストケースを知るには、マイクロフォーマットを使った各ページをご覧ください。複数のマイクロフォーマットを使っているツールやサービスは少ししかありません。このセクションは複数のマイクロフォーマットに関連するエディター、パーサー、妥当性検証ソフト、テストケースなどの情報をご紹介しています。

*[[accessibility|アクセシビリティ]]
*[[faqs-for-rdf|RDFに対してよく聞かれる質問]]
*[[icalendar-implementations|iCalendarの実装]]
*[[internationalization|国際化]]
*[[parsing-microformats|マイクロフォーマットのパース方法]]
*[[selected-test-cases-from-the-web|Web上の厳選テストケース]]
*[http://hg.microformats.org/ ソースコード・レポジトリ] -- [[mercurial-quick-start|ハウツー：レポジトリからコードをダウンロードするには]]
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]
*[[why-are-content-standards-hard|コンテンツの標準化が難しい理由]]
*[[profile-examples-in-wild|Profile フォーマット実際の使用例]]

== リソース ==

* [[events|イベント]]
* [[cheatsheets|カンニングペーパー]]は、マイクロフォーマットの仕様をど忘れしてしまったときなどに便利です。
* [[spread-microformats|マイクロフォーマット普及キャンペーン]]
* [[buttons|ブログ＆サイト用ボタン]]
* [[icons-ja|デスクトップアイコン]]
* [[demo|デモ]] - microformatを試すデモへのリンク集
* [[semacode|Semacode]]
* [[jobs|求人情報]]
* [[user-interface|ユーザーインターフェース]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[microformats-issues|複数のマイクロフォーマットに関する問題点]]
* [[spellcheck|スペルチェックディレクトリ]]

== 共用ワークスペース ==
* [[to-do|TO DO リスト]]
* [[microformats-issues|複数のマイクロフォーマットに関する問題点]]
* [[external-issues|外的問題]]

== 他言語でのmicroformats wiki ==

microformatsの記事を色々な言語で読んだり編集したりできます。

* 100以上の記事のある言語
** [[Main_Page|<span lang="en">English</span> (本家の英語)]]
** [[Main_Page-fr|<span lang="fr">Francais</span> (フランス語)]] <span lang="fr">{{UpdateMarker-fr}}</span>
* 10以上の記事のある言語
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (ブラジル系ポルトガル語)]]
** [[Main_Page-ja|日本語]]
* 2以上の記事のある言語
** [[Main_Page-es|<span lang="es">Espanol</span> (スペイン語)]]
** [[Main_Page-de|<span lang="de">Deutsch</span> (ドイツ語)]]
** [[Main_Page-ro|Romanian]]
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.
See also [[other-languages]], and [[how-to-start-new-translation-ja|how-to-start-a-new-translation]].

how-to-play-ja

2007-09-27T07:22:21Z

IwaiMasaharu: /* Related */ 日本語ページへのリンクに変更

初めての方は[[introduction-ja|Microformatsの手引き]]をご覧ください。

= How to Play =

協力する前にこれらのガイドラインを読んでください。また、この内容は遵守してください。

# ページを編集したり作成したりする前にアカウントを作成してください。( [http://en.wikipedia.org/wiki/Wikipedia:Username Wikipedia Username guidelines] も見てください)
# Read about microformats.org [http://microformats.org/wiki/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.
# はじめに[http://microformats.org/discuss IRCチャンネル(こちらがお勧め)かメーリングリスト]に参加してみてください。(その前には[[mailing-lists]]を読んで下さい)
# もし、何か意見を書いたならば、あなたのユーザ名も一緒に書いてください。- you can easily do so with a datetimestamp in MediaWiki with four ~s, e.g.: <nowiki>~~~~</nowiki>.
# このWikiには、microformatsに直接関係あるページだけを作成してください。無関係なページは削除されます。
# ページの[[naming-conventions-ja|命名規則]]に従ってください。
# Wikiのページで会話をしてはいけません。その用途には#3で挙げた[http://microformats.org/discuss mailing lists]を使ってください。
# 妥当なXHTMLで記述するようにしてください。
# ソースコードを貼りつける場合、適当な長さで改行を入れてください。
# 見出しに「?」などの句読点記号を入れないでください。これは、URLのフラグメント識別子（リンクのターゲットを表す部分）を短くすることにより、可読性を高めたり、コピー＆ペーストなどをしやすくするためです。
# 目次に表示させたくない見出しには <h1> タグや <h2> タグなどを使ってもかまいません。こういったタグを見つけても、「=」や「==」などを使ったスタイルの見出しに変更しないでください。
# 見出しのテキストを変更しないようにしてください（大文字と小文字間の変換や、上記のルールに従おうとするための変更も含む。）。見出しはパーマリンクとして使われることが多いため、変更によって他で使われているリンク切れなどをひき起こす可能性があります。これらをふまえ、見出しをつける場合は注意して言葉を選んでください。どうしても変更が必要な場合、空の <code><nowiki><span id="oldheadingID"></span></nowiki></code> というコードを見出しの前に書き、"oldHeadingID" の部分を見出しパーマリンクを残すために必要な値にすることで、リンク切れを防ぐことはできます。
# 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.
# 赤文字のリンクを削除したり、ダミーコンテンツを置いた空の新規ページを作成しないでください。赤文字のリンクは、新規ページ作成の必要性があるという判断より作成されたものですが、リンク先が編集されていないのは、リンクの作成者が必ずしもそのページの内容に詳しくなかったり、時間がなかったりという理由からです。（ただし、現存しないマイクロフォーマット・タイプのページへのリンクなどは外すべきです）
# MediaWiki の「カテゴリー」構造を使わないでください。このコミュニティは、MediaWikiの全機能を使わないことにしているからです。（その他の例：「Talk」ページ）
# 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.
# もしページを移動させる時は、メニューにある「ここにリンクしている他のページ」を確認し、リンク切れがないよう修正してください。

== Wiki Cleaning ==

「[[spam-removal|スパムの削除]]」をご覧ください。

Wiki上で大掛かりな削除作業が必要と思われる状況を発見した場合、IRCチャンネルまたは microformats-discuss メーリングリストから管理者にご連絡ください。

== Related ==

「[[mediawiki-customization|MediaWiki のカスタム化]]」ページに、このマイクロフォーマットWikiと典型的な MediaWiki の違いについての簡単な説明があります。主に、[[how-to-play-ja|how-to-play]] および [[naming-conventions-ja|命名規則]]を使いやすくするためにカスタム化を加えています。

User:IwaiMasaharu

2007-08-17T06:07:54Z

IwaiMasaharu: revert spam

== profile ==

My name is IWAI, Masaharu a.k.a. iwaim. I'm one of the Japanese Wiki translators/localizers.

* http://iwaim.beering.be/
* http://d.hatena.ne.jp/iwaim/
* [[User:IwaiMasaharu/greasemonkey-user-scripts|greasemonkey user scripts for Microformats Wiki]]

== ライセンス ==
{{public-domain-release}}

== ドキュメント ==

*[[User:IwaiMasaharu/guidance-of-translation-ja|翻訳の手引き(私家版)]]

== 日本語版ローカルルール(私家版)==

*日本語の言語コードは「ja」なので、翻訳時にはページの末尾に「-ja」を付けましょう。
*冒頭に「<nowiki></nowiki>」という感じでベースとなった英語版を指定しましょう。
*句読点は"、"と"。"を使いましょう。

== ツール ==

=== 対訳表 ===

*[[User:IwaiMasaharu/english-to-japanese-map|英日対訳表]]
*[[User:IwaiMasaharu/english-to-japanese-map-for-wiki-notation|Wiki記法の英日対応表]]

=== 閲覧補助 ===

*[[User:IwaiMasaharu/greasemonkey-user-scripts|Greasemonkey ユーザスクリプト集]]

User:IwaiMasaharu

2007-07-25T10:14:56Z

IwaiMasaharu: public-domain-releaseテンプレートを追加

presentational-html-ja

2007-07-25T09:51:45Z

IwaiMasaharu: /* See also */ リンク先を日本語ページに。

<h1> 表現的な(X)HTML </h1>

Presentational (X)HTML refers to:
# (X)HTMLの表現的な要素と属性（[[semantic-html-ja|意味的なHTML]]とは対照的なもの）
# 表現的な(X)HTMLを使ってかかれた(X)HTML文書
# 表現的な(X)HTMLを使って書く習慣

__TOC__

== Contributors ==
* [http://tantek.com/ Tantek]

== 表現的な要素 ==

Presentational elements sensu lato can be divided into two groups. "Pure" presentational elements (b, i, small, …) have no semantic meaning. "Abused" presentational elements (table, blockquote, …) have a semantic meaning, but are abused because of their default appearance in browsers (the blockquote element could be used for indenting text, for example).

（このリストは未完成です。[[presentational-html|英語版]]に追加してください！）

Pure:

* b
* basefont
* big
* br（スペースを空けるために使われたり、意味的にはdiv要素やp要素の方が適切である場所に使われたりする場合）
* center
* font
* hr
* i
* s
* small
* strike
* tt
* u
* ...

Abused:

* （テキストのインデントのために使われる）blockquote
* （レイアウトのために使われる）table
* ...

== 表現的な属性 ==

（このリストは未完成です。[[presentational-html|英語版]]に追加してください！）

* align
* alink
* bgcolor
* color
* face
* height
* （body要素の）link
* （font要素の）size
* valign
* vlink
* width

== See also ==
* [[posh-ja|POSH]]
* [[semantic-html-ja|semantic-html]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

presentational-html-ja

2007-07-25T09:51:03Z

IwaiMasaharu: /* Presentational Attributes */ 翻訳

<h1> 表現的な(X)HTML </h1>

Presentational (X)HTML refers to:
# (X)HTMLの表現的な要素と属性（[[semantic-html-ja|意味的なHTML]]とは対照的なもの）
# 表現的な(X)HTMLを使ってかかれた(X)HTML文書
# 表現的な(X)HTMLを使って書く習慣

__TOC__

== Contributors ==
* [http://tantek.com/ Tantek]

== 表現的な要素 ==

Presentational elements sensu lato can be divided into two groups. "Pure" presentational elements (b, i, small, …) have no semantic meaning. "Abused" presentational elements (table, blockquote, …) have a semantic meaning, but are abused because of their default appearance in browsers (the blockquote element could be used for indenting text, for example).

（このリストは未完成です。[[presentational-html|英語版]]に追加してください！）

Pure:

* b
* basefont
* big
* br（スペースを空けるために使われたり、意味的にはdiv要素やp要素の方が適切である場所に使われたりする場合）
* center
* font
* hr
* i
* s
* small
* strike
* tt
* u
* ...

Abused:

* （テキストのインデントのために使われる）blockquote
* （レイアウトのために使われる）table
* ...

== 表現的な属性 ==

（このリストは未完成です。[[presentational-html|英語版]]に追加してください！）

* align
* alink
* bgcolor
* color
* face
* height
* （body要素の）link
* （font要素の）size
* valign
* vlink
* width

== See also ==
* [[POSH]]
* [[semantic-html]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

presentational-html-ja

2007-07-25T09:50:07Z

IwaiMasaharu: /* Presentational Elements */ 冒頭の文以外を翻訳

<h1> 表現的な(X)HTML </h1>

Presentational (X)HTML refers to:
# (X)HTMLの表現的な要素と属性（[[semantic-html-ja|意味的なHTML]]とは対照的なもの）
# 表現的な(X)HTMLを使ってかかれた(X)HTML文書
# 表現的な(X)HTMLを使って書く習慣

__TOC__

== Contributors ==
* [http://tantek.com/ Tantek]

== 表現的な要素 ==

Presentational elements sensu lato can be divided into two groups. "Pure" presentational elements (b, i, small, …) have no semantic meaning. "Abused" presentational elements (table, blockquote, …) have a semantic meaning, but are abused because of their default appearance in browsers (the blockquote element could be used for indenting text, for example).

（このリストは未完成です。[[presentational-html|英語版]]に追加してください！）

Pure:

* b
* basefont
* big
* br（スペースを空けるために使われたり、意味的にはdiv要素やp要素の方が適切である場所に使われたりする場合）
* center
* font
* hr
* i
* s
* small
* strike
* tt
* u
* ...

Abused:

* （テキストのインデントのために使われる）blockquote
* （レイアウトのために使われる）table
* ...

== Presentational Attributes ==

(This list is incomplete, please add!)

* align
* alink
* bgcolor
* color
* face
* height
* link (on body)
* size (on font element)
* valign
* vlink
* width

== See also ==
* [[POSH]]
* [[semantic-html]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

presentational-html-ja

2007-07-25T09:31:14Z

IwaiMasaharu: 冒頭を翻訳

<h1> 表現的な(X)HTML </h1>

Presentational (X)HTML refers to:
# (X)HTMLの表現的な要素と属性（[[semantic-html-ja|意味的なHTML]]とは対照的なもの）
# 表現的な(X)HTMLを使ってかかれた(X)HTML文書
# 表現的な(X)HTMLを使って書く習慣

__TOC__

== Contributors ==
* [http://tantek.com/ Tantek]

== Presentational Elements ==

Presentational elements sensu lato can be divided into two groups. "Pure" presentational elements (b, i, small, …) have no semantic meaning. "Abused" presentational elements (table, blockquote, …) have a semantic meaning, but are abused because of their default appearance in browsers (the blockquote element could be used for indenting text, for example).

(This list is incomplete, please add!)

Pure:

* b
* basefont
* big
* br (when used for spacing, or when used inappropriately where a div or p would have been semantically correct)
* center
* font
* hr
* i
* s
* small
* strike
* tt
* u
* ...

Abused:

* blockquote (when used for indenting text)
* table (when used for layout)
* ...

== Presentational Attributes ==

(This list is incomplete, please add!)

* align
* alink
* bgcolor
* color
* face
* height
* link (on body)
* size (on font element)
* valign
* vlink
* width

== See also ==
* [[POSH]]
* [[semantic-html]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

presentational-html-ja

2007-07-25T09:24:51Z

IwaiMasaharu: english: 19:54, 14 May 2007

<h1> Presentational (X)HTML </h1>

Presentational (X)HTML refers to:
# The presentational elements and attributes of (X)HTML (as opposed to the [[semantic-html|semantic HTML]] elements and attributes)
# (X)HTML documents that are written using presentational (X)HTML.
# The practice of writing presentational (X)HTML

__TOC__

== Contributors ==
* [http://tantek.com/ Tantek]

== Presentational Elements ==

Presentational elements sensu lato can be divided into two groups. "Pure" presentational elements (b, i, small, …) have no semantic meaning. "Abused" presentational elements (table, blockquote, …) have a semantic meaning, but are abused because of their default appearance in browsers (the blockquote element could be used for indenting text, for example).

(This list is incomplete, please add!)

Pure:

* b
* basefont
* big
* br (when used for spacing, or when used inappropriately where a div or p would have been semantically correct)
* center
* font
* hr
* i
* s
* small
* strike
* tt
* u
* ...

Abused:

* blockquote (when used for indenting text)
* table (when used for layout)
* ...

== Presentational Attributes ==

(This list is incomplete, please add!)

* align
* alink
* bgcolor
* color
* face
* height
* link (on body)
* size (on font element)
* valign
* vlink
* width

== See also ==
* [[POSH]]
* [[semantic-html]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

presentational-ja

2007-07-25T09:19:13Z

IwaiMasaharu: リダイレクトページの作成

#REDIRECT:[[presentational-html-ja]]

semantic-ja

2007-07-25T09:18:00Z

IwaiMasaharu: リダイレクトの作成

#REDIRECT:[[semantic-xhtml-ja]]

posh-ja

2007-07-25T09:17:21Z

IwaiMasaharu: /* POSHとは？ */ リンク先を日本語ページに。

<h1>Plain Old Semantic HTML (POSH)</h1>

<abbr title="Plain Old Semantic HTML">POSH</abbr>のホームページ（日本語版）へようこそ。（[[posh|英語版]]）

__TOC__

== 起源 ==
'''POSH'''という用語は、[http://rbach.priv.at/Microformats-IRC/2007-04-06#T091456 2007年4月6日にmicroformatsのIRCチャネルにおいて]、<kwijibo>によって考案されました。POSHとは、[[plain-old-semantic-html-ja|plain-old-semantic-html]]の頭文字を取った略語です。John Allsopp、Tantek Çelik、Jeremy Keith、Chris Messinaらが[[events/2007-04-18-web-2-expo-dinner|2007年4月18日のWeb 2.0 Expo後に行われたMicroformats Dinner]]で交わした議論を通して、microformatsのよりどころでありそれが正しいサブセットともなっているPOSHの発想と、そのより幅広い目標を広めることの重要性があらためて注目されました。詳しくは[[posh#History|POSHの歴史]]を参照してください。

== 理由 ==
[[semantic-html-ja|意味的（セマンティック）なHTML]]という用語はやや仰々しいため、それがどれほどシンプルなものであり昨今のウェブデザイナーたちの間でいかに確固たる支持を受けているかということも、意味的なマークアップを用いてウェブを真っ当に作ることだけにとどまらない大きなメリットをもたらすということも、うまく伝えられていません。私たちは、そのコンセプトの本質を的確に表現でき、簡単に動詞にも応用できるような（たとえば「to posh」「poshify」「poshed up」などという使い方ができるような）、覚えやすい用語を必要としていたのです。

== POSHとは？ ==
POSHとは、Webページを作成する際に[[semantic-html-ja|意味的なHTML]]を用いることのベストプラクティスを簡潔にあらわしたものです。意味的なHTMLとは、HTML 4.01（またはXHTML 1.0）にある要素と属性のなかで、''[[presentational-ja|表現的]]''ではなく''[[semantic-ja|意味的]]''なものから成るサブセットのこと。POSHを習い理解する最も良い方法は、実践することです。あなたのWebサイトからいちページを選び、[[posh-ja#POSH.E3.83.81.E3.82.A7.E3.83.83.E3.82.AF.E3.83.AA.E3.82.B9.E3.83.88|POSHチェックリスト]]を適用してください。[[posh-ja#POSH.E3.83.97.E3.83.AD.E3.82.BB.E3.82.B9|POSHプロセス]]に則り、そのまま続けてください。POSHについてより詳しく学ぶには、[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]をお読みください。

== POSHプロセス ==
あなたがPOSHであるために、そしてあなたのウェブサイトをPOSHなものにするためには、何ができるでしょうか？

# POSHなコンテンツを公開する。[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]に目を通し、あなたのウェブサイトでvalidな[[semantic-html-ja|意味的な(X)HTML]]を公開し、それに伴って[[semantic-class-names]]を使用するように心がけましょう。
# POSHを広める。このページへのリンクを貼って、他の人たちもPOSHになるように、そしてウェブサイトをPOSH対応させる（POSHify）ように勧めてみましょう。
# POSHを改善する。より多くの人が手軽にウェブサイトをPOSH対応させられるように、POSHリソースの収集をお手伝いください。

== POSHチェックリスト ==
* POSHの最初のルールとして、まずあなたのPOSHを必ず[http://validator.w3.org 検証]しましょう。
* 次に、単なる表現上の目的で使われているTABLEや、スペーサーGIF画像、いわゆる[[presentational-html|表現的なHTML]]を取り除きましょう。
* さらに、（BタグやBRタグの濫用を典型とする）[http://tantek.com/log/2002/10.html#L20021022t1432 その場しのぎ（'''B'''ed and '''BR'''eakfast）]のマークアップを修正しましょう。
* [http://tantek.com/log/2002/11.html#L20021128t1352 空っぽアンカー（Anorexic Anchors）]を取り除きましょう。
* よい[[semantic-class-names|意味的なクラス名]]を使いましょう。
* ...

== POSHリソース ==
=== POSHチュートリアル ===
Step by step tutorials to create POSH content or upgrade existing content to POSH.

* [http://westciv.com/style_master/house/tutorials/quick/validation/index.html Validating your css and html] A simple step by step guide to how and why you should validate your markup
* ...

=== POSH関連ブックマーク ===
* Ma.gnoliaの[http://ma.gnolia.com/groups/posh POSHグループ]をチェックしてみてください。
* See pages tagged both [http://del.icio.us/tag/posh+microformats POSH and microformats] on del.icio.us.

=== POSH関連プレゼンテーション ===
Presentations which explain and advocate concepts and techniques for utilizing semantic HTML. If/when this section gets too big, we can move it to [[posh-presentations]].
* [http://tantek.com/presentations/2003SXSW/stylesheets.html CSS: Between the Style Sheets by Tantek Çelik (2003-03)], specifically, see slides 3-4,6 starting with "Leaving the [http://tantek.com/log/2002/10.html#L20021022t1432 <B>ed & <BR>eakfast]", and slide 9 "CSS & the Semantic Spectrum" which provides an overview of the semantic spectrum of (X)HTML tags.
* [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics] (2004-02-11)
* [http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean] (2004-09-28)
* [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (2005-09-29, first version: [http://tantek.com/presentations/2005/03/elementsofxhtml/ 2005-03-13 at SXSW Interactive]).
* ...
* See also more microformats [[presentations]] in general.

=== POSH関連書籍 ===
Modern web design books which document good semantic HTML practices.
* <cite>[http://www.oreilly.com/catalog/wdnut3/ http://www.oreilly.com/catalog/covers/0596009879_thumb.gif] [http://www.oreilly.com/catalog/wdnut3/ Web Design in a Nutshell, <strong>Third Edition</strong>]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Jennifer</span> <span class="additional-name">Niederst</span> <span class="family-name">Robbins</span></span> See [http://jenville.com/ Jenville].</span>
* <cite>[http://microformatique.com/book/ Microformats empowering your markup for Web 2.0]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">John</span> <span class="family-name">Allsopp</span>.</span></span> Chapter 3 is a detailed and practical overview of the appropriate use of structural, valid and semantic HTML.
* <cite>[http://htmlmastery.com/ http://htmlmastery.com/images/hm-cover-sm.gif][http://htmlmastery.com/ Semantics, Standards and Styling]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Paul</span> <span class="family-name">Haine</span>.</span></span>

=== POSH関連雑誌 ===
Online (and off) magazines which frequently publish articles about semantic HTML. If/when this section gets too big, we can move it to [[posh-magazines]].

* [http://alistapart.com/ A List Apart: For People Making Websites] (see in particular [http://www.alistapart.com/topics/code/htmlxhtml/ HTML and XHTML Articles])
* [http://www.digital-web.com/ Digital Web Magazine]

=== POSH関連ブログ ===
Blogs that with some regularity post high quality discussions, insights, and in general have advanced the state of the art of POSH. If/when this section gets too big, we can move it to [[posh-blogs]].

* [http://dbaron.org/log/current David Baron's weblog]
* [http://zeldman.com/ Jeffrey Zeldman Presents]
* [http://meyerweb.com/ meyerweb.com - Eric Meyer]
* [http://microformatique.com/ Microformatique - John Allsopp]
* [http://simplebits.com/ SimpleBits - Dan Cederholm] (see in particular [http://simplebits.com/bits/simplequiz/ SimpleQuiz])
* [http://tantek.com/ Tantek Çelik]
* ...

=== POSH関連ブログ記事 ===
Blog posts that provide specific, modern, guidance, techniques and tips for using more and better semantic HTML. This list is ''incomplete''. We know there are lots more blog posts out there that fit the aforementioned description - please add them! If/when this section gets too big, we can move it to [[posh-blog-posts]].

* [http://www.plaintxt.org/wp-content/uploads/sandbox-v09_readme.html The Sandbox theme for WordPress readme.html] discusses what POSH is and how the theme helps users use it.
* [http://tantek.com/log/2002/10.html#L20021022t1432 Bed and BReakfast markup (B&BR)] (2002-10-22) - avoiding nonsemantic uses of <nowiki><b>old and <br>eak</nowiki> tags and using <nowiki><h3>adings and <p>aragraphs</nowiki> instead.
* [http://tantek.com/log/2002/11.html#L20021128t1352 <nowiki><A>norexic </A>nchors</nowiki>] (2002-11-28) - use the "id" attribute on existing elements instead of adding empty <code><nowiki><a name="foo"></a></nowiki></code> elements. Use [[rel-bookmark]] for post permalinks within the document.
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class] (2002-12-16) - introduction to proper use of the HTML 'class' attribute.
* [http://tantek.com/log/2002/12.html#L20021231t1850 Dive into Semantic MARKup] (2002-12-31)
* [http://tantek.com/log/2003/01.html#L20030104t1249 Comment markup, presentation and plumbing] (2003-01-04) - how to markup a list of comments, including example use of the rare "hreflang" attribute.
* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer] (2004-07-18)
* [http://tantek.com/log/2004/07.html#d20t2359 More about the 'class' attribute] (2004-07-20)
* [http://www.uie.com/articles/holzschlag_interview/ Web Standards in the Real World: An Interview with Molly Holzschlag] (2005-06-01)
* [http://westciv.typepad.com/dog_or_higher/2005/11/webpatterns_and.html Webpatterns and websemantics] (2005-11-18)
* [http://www.thefutureoftheweb.com/blog/2006/2/writing-semantic-html Writing Semantic HTML by Jesse Skinner] (2006-02-22)
* [http://www.thefutureoftheweb.com/blog/2007/1/who-will-read-your-semantic-html Who will read your Semantic HTML?] by Jesse Skinner (2007-01-04)
* [http://microformatique.com/?page_id=109 Semantics in HTML] by John Allsopp (2007-01-08 - 2007-03-12)
** [http://microformatique.com/?p=83 Part I - Traditional HTML Semantics] (2007-01-08)
** [http://microformatique.com/?p=97 Part II - standardizing vocabularies] (2007-02-20)
** [http://microformatique.com/?p=108 Part III - Towards a semantic web] (2007-03-12)
* [http://microformatique.com/?p=82 Built in HTML semantics] A list of the semantic elements and attributes of HTML by John Allsopp (2007-01-08)
* [http://tantek.com/log/2007/04.html#d20t0823 The Importance of Being POSH] by Tantek Çelik (2007-04-20)
* [http://factoryjoe.com/blog/2007/04/21/getting-back-to-posh-plain-ol-semantic-html/ Getting back to POSH (Plain ol’ Semantic HTML)] by Chris Messina (2007-04-21)
* [http://friedcellcollective.net/outbreak/2007/04/22/im-posh-are-you/ I’m POSH - are you?] (2007-04-23)
* [http://www.unintentionallyblank.co.uk/2007/04/24/plain-old-semantic-html/ The Internet’s Upper Class Or Why Your Site Should Be POSH] (2007-04-24)
* [http://nate.koechley.com/blog/2006/12/15/divitis_and_correct_div_usage/ On Appropriate Use of DIVs, or When Divitis Doesn’t Apply] by Nate Koechley, 2006-12-15
* [http://nate.koechley.com/blog/2006/12/22/note_on_structural_and_semantic_meaning/ Quick Comment: Choose Class/ID Names Based on Semantic and/or Structural Meaning] by Nate Koechley, 2006-12-22
* [http://leland.nu/think/2006/07/31/seeing-is-believing/ SEEing is believing] - using standards and efficient design, coding, maintenance, and marketing to produce a search-engine-efficient site by Richard Leland (2006-07-31)
* ...

See [http://technorati.com/search/%22semantic%20HTML%22 more blogs talking about "semantic HTML"] and [http://technorati.com/search/posh+semantic+HTML POSH].

===POSH関連ポッドキャスト===
* [http://www.netmag.co.uk/podcasts/07-05-03-net.mp3 A talk about POSH] in the .Net magazine podcast episode 8 (56 minutes; 26 Mb. Relevant section 30:10-42:40)

=== POSHにまつわる隠れた情報源 ===
The following sites have POSH related articles, tutorials etc. on them, but you have to dig for them from the home page. Help find the hidden POSH treasures in these sites and add ''direct'' links to POSH related articles, tutorials etc. to the specific sections above. You can leave the top level site links here until/unless you have dug thru the entire site and found all the treasures.
* [http://www.w3schools.com/ W3Schools Online Web Tutorials]
* [http://dev.opera.com/ Dev.Opera]

=== POSH Bling for your Blog ===
If you want to improve your existing blog, there are some pretty simple things you can do:

==== WordPress ====
* Use the [http://www.plaintxt.org/themes/sandbox/ Sandbox] or [http://getk2.com K2] themes that already support hAtom and hCard
* Add the [http://redmonk.net/archives/2007/04/18/wordpress-widget-hcard-about-box/ hCard About Widget] to your site

== POSHを広める ==
Now that you've poshified your website(s), what next? Well, help spread POSH to other websites!

* Promote POSH. Make a POSH button (perhaps using semantic HTML and CSS ;) linking to this page and put it on your site, in your blogroll, in your footer, etc. Maybe even come up with a nice POSH button graphic and share it with the microformats community with a liberal license (public domain, CC-by-3.0, MIT, etc.) Like these:
** [http://redmonk.net/archives/2007/04/25/the-new-question/ http://redmonk.net/wp-content/uploads/2007/04/are_you_posh.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
** [http://redmonk.net/archives/2007/04/26/chic/ http://redmonk.net/wp-content/uploads/2007/04/chic_fancy.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
* Tell a friend. Talk to web design friends about POSH and convince and help them to poshify both their personal websites, and the websites they build for others. Blog about your experience with poshification and what steps you went through to poshify your websites. Write a [[posh-testimonial]]!
* Come up with more ideas to help spread POSH. Here are a few.
** Hold a PoshPit - a one or half day marathon session mixing semantic HTML experts with folks who maintain/run web sites in general and see how many websites you can collectively upgrade to POSH during the course of the day.
** ...

== POSHを改善する ==
As you read the [[posh#Resources|POSH resources]] documented here, what other POSH resources did you find? Add them to this page.

With your experience with both poshifying your sites and helping others do so, what have you learned? What kind of [[posh-issues|issues]] did you run into? What questions were commonly asked? What do you feel like you need to more easily and quickly help more people poshify their content?

== 歴史 ==
A brief history of references to "POSH" in this context and "plain old semantic HTML".

=== plain old semantic HTML ===
The earliest references to <strong>"plain old semantic HTML"</strong> that have been found so far are:
* [http://groups.google.com/group/comp.infosystems.www.authoring.site-design/msg/2373e9043c08cba4 1998-05-01: Kirrily 'Skud' Robert on comp.infosystems.www.authoring.site-design] - "The site is implemented in HTML 4.0 Transitional with style sheets; this means that anyone with an older browser won't get presentational markup, just <strong>plain old semantic HTML</strong>. "
* [http://www.highrankings.com/advisor/tables-seo/ 2006-09-21 Drew's comment by on "Tables and SEO"]: "I’d say it’s well worth it for a variety of reasons to only use tables when you’re presenting tabular data, and use <strong>plain old semantic HTML</strong> to mark up your content in all other cases." (retrieved by [[User:Tantek|Tantek]] 08:20, 20 Apr 2007 (PDT))
If you can find earlier references, please ''add'' them and include a brief quotation of the context of the reference to "plain old semantic HTML".

posh-ja

2007-07-25T09:15:17Z

IwaiMasaharu: /* 理由 */ 日本語表現の更新

<h1>Plain Old Semantic HTML (POSH)</h1>

<abbr title="Plain Old Semantic HTML">POSH</abbr>のホームページ（日本語版）へようこそ。（[[posh|英語版]]）

__TOC__

== 起源 ==
'''POSH'''という用語は、[http://rbach.priv.at/Microformats-IRC/2007-04-06#T091456 2007年4月6日にmicroformatsのIRCチャネルにおいて]、<kwijibo>によって考案されました。POSHとは、[[plain-old-semantic-html-ja|plain-old-semantic-html]]の頭文字を取った略語です。John Allsopp、Tantek Çelik、Jeremy Keith、Chris Messinaらが[[events/2007-04-18-web-2-expo-dinner|2007年4月18日のWeb 2.0 Expo後に行われたMicroformats Dinner]]で交わした議論を通して、microformatsのよりどころでありそれが正しいサブセットともなっているPOSHの発想と、そのより幅広い目標を広めることの重要性があらためて注目されました。詳しくは[[posh#History|POSHの歴史]]を参照してください。

== 理由 ==
[[semantic-html-ja|意味的（セマンティック）なHTML]]という用語はやや仰々しいため、それがどれほどシンプルなものであり昨今のウェブデザイナーたちの間でいかに確固たる支持を受けているかということも、意味的なマークアップを用いてウェブを真っ当に作ることだけにとどまらない大きなメリットをもたらすということも、うまく伝えられていません。私たちは、そのコンセプトの本質を的確に表現でき、簡単に動詞にも応用できるような（たとえば「to posh」「poshify」「poshed up」などという使い方ができるような）、覚えやすい用語を必要としていたのです。

== POSHとは？ ==
POSHとは、Webページを作成する際に[[semantic-html-ja|意味的なHTML]]を用いることのベストプラクティスを簡潔にあらわしたものです。意味的なHTMLとは、HTML 4.01（またはXHTML 1.0）にある要素と属性のなかで、''[[presentational|表現的]]''ではなく''[[semantic|意味的]]''なものから成るサブセットのこと。POSHを習い理解する最も良い方法は、実践することです。あなたのWebサイトからいちページを選び、[[posh-ja#POSH.E3.83.81.E3.82.A7.E3.83.83.E3.82.AF.E3.83.AA.E3.82.B9.E3.83.88|POSHチェックリスト]]を適用してください。[[posh-ja#POSH.E3.83.97.E3.83.AD.E3.82.BB.E3.82.B9|POSHプロセス]]に則り、そのまま続けてください。POSHについてより詳しく学ぶには、[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]をお読みください。

== POSHプロセス ==
あなたがPOSHであるために、そしてあなたのウェブサイトをPOSHなものにするためには、何ができるでしょうか？

# POSHなコンテンツを公開する。[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]に目を通し、あなたのウェブサイトでvalidな[[semantic-html-ja|意味的な(X)HTML]]を公開し、それに伴って[[semantic-class-names]]を使用するように心がけましょう。
# POSHを広める。このページへのリンクを貼って、他の人たちもPOSHになるように、そしてウェブサイトをPOSH対応させる（POSHify）ように勧めてみましょう。
# POSHを改善する。より多くの人が手軽にウェブサイトをPOSH対応させられるように、POSHリソースの収集をお手伝いください。

== POSHチェックリスト ==
* POSHの最初のルールとして、まずあなたのPOSHを必ず[http://validator.w3.org 検証]しましょう。
* 次に、単なる表現上の目的で使われているTABLEや、スペーサーGIF画像、いわゆる[[presentational-html|表現的なHTML]]を取り除きましょう。
* さらに、（BタグやBRタグの濫用を典型とする）[http://tantek.com/log/2002/10.html#L20021022t1432 その場しのぎ（'''B'''ed and '''BR'''eakfast）]のマークアップを修正しましょう。
* [http://tantek.com/log/2002/11.html#L20021128t1352 空っぽアンカー（Anorexic Anchors）]を取り除きましょう。
* よい[[semantic-class-names|意味的なクラス名]]を使いましょう。
* ...

== POSHリソース ==
=== POSHチュートリアル ===
Step by step tutorials to create POSH content or upgrade existing content to POSH.

* [http://westciv.com/style_master/house/tutorials/quick/validation/index.html Validating your css and html] A simple step by step guide to how and why you should validate your markup
* ...

=== POSH関連ブックマーク ===
* Ma.gnoliaの[http://ma.gnolia.com/groups/posh POSHグループ]をチェックしてみてください。
* See pages tagged both [http://del.icio.us/tag/posh+microformats POSH and microformats] on del.icio.us.

=== POSH関連プレゼンテーション ===
Presentations which explain and advocate concepts and techniques for utilizing semantic HTML. If/when this section gets too big, we can move it to [[posh-presentations]].
* [http://tantek.com/presentations/2003SXSW/stylesheets.html CSS: Between the Style Sheets by Tantek Çelik (2003-03)], specifically, see slides 3-4,6 starting with "Leaving the [http://tantek.com/log/2002/10.html#L20021022t1432 <B>ed & <BR>eakfast]", and slide 9 "CSS & the Semantic Spectrum" which provides an overview of the semantic spectrum of (X)HTML tags.
* [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics] (2004-02-11)
* [http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean] (2004-09-28)
* [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (2005-09-29, first version: [http://tantek.com/presentations/2005/03/elementsofxhtml/ 2005-03-13 at SXSW Interactive]).
* ...
* See also more microformats [[presentations]] in general.

=== POSH関連書籍 ===
Modern web design books which document good semantic HTML practices.
* <cite>[http://www.oreilly.com/catalog/wdnut3/ http://www.oreilly.com/catalog/covers/0596009879_thumb.gif] [http://www.oreilly.com/catalog/wdnut3/ Web Design in a Nutshell, <strong>Third Edition</strong>]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Jennifer</span> <span class="additional-name">Niederst</span> <span class="family-name">Robbins</span></span> See [http://jenville.com/ Jenville].</span>
* <cite>[http://microformatique.com/book/ Microformats empowering your markup for Web 2.0]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">John</span> <span class="family-name">Allsopp</span>.</span></span> Chapter 3 is a detailed and practical overview of the appropriate use of structural, valid and semantic HTML.
* <cite>[http://htmlmastery.com/ http://htmlmastery.com/images/hm-cover-sm.gif][http://htmlmastery.com/ Semantics, Standards and Styling]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Paul</span> <span class="family-name">Haine</span>.</span></span>

=== POSH関連雑誌 ===
Online (and off) magazines which frequently publish articles about semantic HTML. If/when this section gets too big, we can move it to [[posh-magazines]].

* [http://alistapart.com/ A List Apart: For People Making Websites] (see in particular [http://www.alistapart.com/topics/code/htmlxhtml/ HTML and XHTML Articles])
* [http://www.digital-web.com/ Digital Web Magazine]

=== POSH関連ブログ ===
Blogs that with some regularity post high quality discussions, insights, and in general have advanced the state of the art of POSH. If/when this section gets too big, we can move it to [[posh-blogs]].

* [http://dbaron.org/log/current David Baron's weblog]
* [http://zeldman.com/ Jeffrey Zeldman Presents]
* [http://meyerweb.com/ meyerweb.com - Eric Meyer]
* [http://microformatique.com/ Microformatique - John Allsopp]
* [http://simplebits.com/ SimpleBits - Dan Cederholm] (see in particular [http://simplebits.com/bits/simplequiz/ SimpleQuiz])
* [http://tantek.com/ Tantek Çelik]
* ...

=== POSH関連ブログ記事 ===
Blog posts that provide specific, modern, guidance, techniques and tips for using more and better semantic HTML. This list is ''incomplete''. We know there are lots more blog posts out there that fit the aforementioned description - please add them! If/when this section gets too big, we can move it to [[posh-blog-posts]].

* [http://www.plaintxt.org/wp-content/uploads/sandbox-v09_readme.html The Sandbox theme for WordPress readme.html] discusses what POSH is and how the theme helps users use it.
* [http://tantek.com/log/2002/10.html#L20021022t1432 Bed and BReakfast markup (B&BR)] (2002-10-22) - avoiding nonsemantic uses of <nowiki><b>old and <br>eak</nowiki> tags and using <nowiki><h3>adings and <p>aragraphs</nowiki> instead.
* [http://tantek.com/log/2002/11.html#L20021128t1352 <nowiki><A>norexic </A>nchors</nowiki>] (2002-11-28) - use the "id" attribute on existing elements instead of adding empty <code><nowiki><a name="foo"></a></nowiki></code> elements. Use [[rel-bookmark]] for post permalinks within the document.
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class] (2002-12-16) - introduction to proper use of the HTML 'class' attribute.
* [http://tantek.com/log/2002/12.html#L20021231t1850 Dive into Semantic MARKup] (2002-12-31)
* [http://tantek.com/log/2003/01.html#L20030104t1249 Comment markup, presentation and plumbing] (2003-01-04) - how to markup a list of comments, including example use of the rare "hreflang" attribute.
* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer] (2004-07-18)
* [http://tantek.com/log/2004/07.html#d20t2359 More about the 'class' attribute] (2004-07-20)
* [http://www.uie.com/articles/holzschlag_interview/ Web Standards in the Real World: An Interview with Molly Holzschlag] (2005-06-01)
* [http://westciv.typepad.com/dog_or_higher/2005/11/webpatterns_and.html Webpatterns and websemantics] (2005-11-18)
* [http://www.thefutureoftheweb.com/blog/2006/2/writing-semantic-html Writing Semantic HTML by Jesse Skinner] (2006-02-22)
* [http://www.thefutureoftheweb.com/blog/2007/1/who-will-read-your-semantic-html Who will read your Semantic HTML?] by Jesse Skinner (2007-01-04)
* [http://microformatique.com/?page_id=109 Semantics in HTML] by John Allsopp (2007-01-08 - 2007-03-12)
** [http://microformatique.com/?p=83 Part I - Traditional HTML Semantics] (2007-01-08)
** [http://microformatique.com/?p=97 Part II - standardizing vocabularies] (2007-02-20)
** [http://microformatique.com/?p=108 Part III - Towards a semantic web] (2007-03-12)
* [http://microformatique.com/?p=82 Built in HTML semantics] A list of the semantic elements and attributes of HTML by John Allsopp (2007-01-08)
* [http://tantek.com/log/2007/04.html#d20t0823 The Importance of Being POSH] by Tantek Çelik (2007-04-20)
* [http://factoryjoe.com/blog/2007/04/21/getting-back-to-posh-plain-ol-semantic-html/ Getting back to POSH (Plain ol’ Semantic HTML)] by Chris Messina (2007-04-21)
* [http://friedcellcollective.net/outbreak/2007/04/22/im-posh-are-you/ I’m POSH - are you?] (2007-04-23)
* [http://www.unintentionallyblank.co.uk/2007/04/24/plain-old-semantic-html/ The Internet’s Upper Class Or Why Your Site Should Be POSH] (2007-04-24)
* [http://nate.koechley.com/blog/2006/12/15/divitis_and_correct_div_usage/ On Appropriate Use of DIVs, or When Divitis Doesn’t Apply] by Nate Koechley, 2006-12-15
* [http://nate.koechley.com/blog/2006/12/22/note_on_structural_and_semantic_meaning/ Quick Comment: Choose Class/ID Names Based on Semantic and/or Structural Meaning] by Nate Koechley, 2006-12-22
* [http://leland.nu/think/2006/07/31/seeing-is-believing/ SEEing is believing] - using standards and efficient design, coding, maintenance, and marketing to produce a search-engine-efficient site by Richard Leland (2006-07-31)
* ...

See [http://technorati.com/search/%22semantic%20HTML%22 more blogs talking about "semantic HTML"] and [http://technorati.com/search/posh+semantic+HTML POSH].

===POSH関連ポッドキャスト===
* [http://www.netmag.co.uk/podcasts/07-05-03-net.mp3 A talk about POSH] in the .Net magazine podcast episode 8 (56 minutes; 26 Mb. Relevant section 30:10-42:40)

=== POSHにまつわる隠れた情報源 ===
The following sites have POSH related articles, tutorials etc. on them, but you have to dig for them from the home page. Help find the hidden POSH treasures in these sites and add ''direct'' links to POSH related articles, tutorials etc. to the specific sections above. You can leave the top level site links here until/unless you have dug thru the entire site and found all the treasures.
* [http://www.w3schools.com/ W3Schools Online Web Tutorials]
* [http://dev.opera.com/ Dev.Opera]

=== POSH Bling for your Blog ===
If you want to improve your existing blog, there are some pretty simple things you can do:

==== WordPress ====
* Use the [http://www.plaintxt.org/themes/sandbox/ Sandbox] or [http://getk2.com K2] themes that already support hAtom and hCard
* Add the [http://redmonk.net/archives/2007/04/18/wordpress-widget-hcard-about-box/ hCard About Widget] to your site

== POSHを広める ==
Now that you've poshified your website(s), what next? Well, help spread POSH to other websites!

* Promote POSH. Make a POSH button (perhaps using semantic HTML and CSS ;) linking to this page and put it on your site, in your blogroll, in your footer, etc. Maybe even come up with a nice POSH button graphic and share it with the microformats community with a liberal license (public domain, CC-by-3.0, MIT, etc.) Like these:
** [http://redmonk.net/archives/2007/04/25/the-new-question/ http://redmonk.net/wp-content/uploads/2007/04/are_you_posh.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
** [http://redmonk.net/archives/2007/04/26/chic/ http://redmonk.net/wp-content/uploads/2007/04/chic_fancy.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
* Tell a friend. Talk to web design friends about POSH and convince and help them to poshify both their personal websites, and the websites they build for others. Blog about your experience with poshification and what steps you went through to poshify your websites. Write a [[posh-testimonial]]!
* Come up with more ideas to help spread POSH. Here are a few.
** Hold a PoshPit - a one or half day marathon session mixing semantic HTML experts with folks who maintain/run web sites in general and see how many websites you can collectively upgrade to POSH during the course of the day.
** ...

== POSHを改善する ==
As you read the [[posh#Resources|POSH resources]] documented here, what other POSH resources did you find? Add them to this page.

With your experience with both poshifying your sites and helping others do so, what have you learned? What kind of [[posh-issues|issues]] did you run into? What questions were commonly asked? What do you feel like you need to more easily and quickly help more people poshify their content?

== 歴史 ==
A brief history of references to "POSH" in this context and "plain old semantic HTML".

=== plain old semantic HTML ===
The earliest references to <strong>"plain old semantic HTML"</strong> that have been found so far are:
* [http://groups.google.com/group/comp.infosystems.www.authoring.site-design/msg/2373e9043c08cba4 1998-05-01: Kirrily 'Skud' Robert on comp.infosystems.www.authoring.site-design] - "The site is implemented in HTML 4.0 Transitional with style sheets; this means that anyone with an older browser won't get presentational markup, just <strong>plain old semantic HTML</strong>. "
* [http://www.highrankings.com/advisor/tables-seo/ 2006-09-21 Drew's comment by on "Tables and SEO"]: "I’d say it’s well worth it for a variety of reasons to only use tables when you’re presenting tabular data, and use <strong>plain old semantic HTML</strong> to mark up your content in all other cases." (retrieved by [[User:Tantek|Tantek]] 08:20, 20 Apr 2007 (PDT))
If you can find earlier references, please ''add'' them and include a brief quotation of the context of the reference to "plain old semantic HTML".

plain-old-semantic-html-ja

2007-07-25T08:36:28Z

IwaiMasaharu: リダイレクトページ作成

#REDIRECT:[[posh-ja]]

posh-ja

2007-07-25T08:35:02Z

IwaiMasaharu: /* 起源 */ plain-old-semantic-htmlのリンク先を日本語ページに。

<h1>Plain Old Semantic HTML (POSH)</h1>

<abbr title="Plain Old Semantic HTML">POSH</abbr>のホームページ（日本語版）へようこそ。（[[posh|英語版]]）

__TOC__

== 起源 ==
'''POSH'''という用語は、[http://rbach.priv.at/Microformats-IRC/2007-04-06#T091456 2007年4月6日にmicroformatsのIRCチャネルにおいて]、<kwijibo>によって考案されました。POSHとは、[[plain-old-semantic-html-ja|plain-old-semantic-html]]の頭文字を取った略語です。John Allsopp、Tantek Çelik、Jeremy Keith、Chris Messinaらが[[events/2007-04-18-web-2-expo-dinner|2007年4月18日のWeb 2.0 Expo後に行われたMicroformats Dinner]]で交わした議論を通して、microformatsのよりどころでありそれが正しいサブセットともなっているPOSHの発想と、そのより幅広い目標を広めることの重要性があらためて注目されました。詳しくは[[posh#History|POSHの歴史]]を参照してください。

== 理由 ==
[[semantic-html-ja|意味的（セマンティック）なHTML]]という用語はやや仰々しく、それがどれほどシンプルなものであり昨今のウェブデザイナーたちの間でいかに確固たる支持を受けているかということも、意味的なマークアップを用いてウェブを真っ当に作ることだけにとどまらない大きなメリットをもたらすということも、いずれもうまく伝えられていません。私たちは、そのコンセプトの本質をうまく表現でき、簡単に動詞にも応用できるような（たとえば「to posh」「poshify」「poshed up」などという使い方ができるような）、覚えやすい用語を必要としていたのです。

== POSHとは？ ==
POSHとは、Webページを作成する際に[[semantic-html-ja|意味的なHTML]]を用いることのベストプラクティスを簡潔にあらわしたものです。意味的なHTMLとは、HTML 4.01（またはXHTML 1.0）にある要素と属性のなかで、''[[presentational|表現的]]''ではなく''[[semantic|意味的]]''なものから成るサブセットのこと。POSHを習い理解する最も良い方法は、実践することです。あなたのWebサイトからいちページを選び、[[posh-ja#POSH.E3.83.81.E3.82.A7.E3.83.83.E3.82.AF.E3.83.AA.E3.82.B9.E3.83.88|POSHチェックリスト]]を適用してください。[[posh-ja#POSH.E3.83.97.E3.83.AD.E3.82.BB.E3.82.B9|POSHプロセス]]に則り、そのまま続けてください。POSHについてより詳しく学ぶには、[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]をお読みください。

== POSHプロセス ==
あなたがPOSHであるために、そしてあなたのウェブサイトをPOSHなものにするためには、何ができるでしょうか？

# POSHなコンテンツを公開する。[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]に目を通し、あなたのウェブサイトでvalidな[[semantic-html-ja|意味的な(X)HTML]]を公開し、それに伴って[[semantic-class-names]]を使用するように心がけましょう。
# POSHを広める。このページへのリンクを貼って、他の人たちもPOSHになるように、そしてウェブサイトをPOSH対応させる（POSHify）ように勧めてみましょう。
# POSHを改善する。より多くの人が手軽にウェブサイトをPOSH対応させられるように、POSHリソースの収集をお手伝いください。

== POSHチェックリスト ==
* POSHの最初のルールとして、まずあなたのPOSHを必ず[http://validator.w3.org 検証]しましょう。
* 次に、単なる表現上の目的で使われているTABLEや、スペーサーGIF画像、いわゆる[[presentational-html|表現的なHTML]]を取り除きましょう。
* さらに、（BタグやBRタグの濫用を典型とする）[http://tantek.com/log/2002/10.html#L20021022t1432 その場しのぎ（'''B'''ed and '''BR'''eakfast）]のマークアップを修正しましょう。
* [http://tantek.com/log/2002/11.html#L20021128t1352 空っぽアンカー（Anorexic Anchors）]を取り除きましょう。
* よい[[semantic-class-names|意味的なクラス名]]を使いましょう。
* ...

== POSHリソース ==
=== POSHチュートリアル ===
Step by step tutorials to create POSH content or upgrade existing content to POSH.

* [http://westciv.com/style_master/house/tutorials/quick/validation/index.html Validating your css and html] A simple step by step guide to how and why you should validate your markup
* ...

=== POSH関連ブックマーク ===
* Ma.gnoliaの[http://ma.gnolia.com/groups/posh POSHグループ]をチェックしてみてください。
* See pages tagged both [http://del.icio.us/tag/posh+microformats POSH and microformats] on del.icio.us.

=== POSH関連プレゼンテーション ===
Presentations which explain and advocate concepts and techniques for utilizing semantic HTML. If/when this section gets too big, we can move it to [[posh-presentations]].
* [http://tantek.com/presentations/2003SXSW/stylesheets.html CSS: Between the Style Sheets by Tantek Çelik (2003-03)], specifically, see slides 3-4,6 starting with "Leaving the [http://tantek.com/log/2002/10.html#L20021022t1432 <B>ed & <BR>eakfast]", and slide 9 "CSS & the Semantic Spectrum" which provides an overview of the semantic spectrum of (X)HTML tags.
* [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics] (2004-02-11)
* [http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean] (2004-09-28)
* [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (2005-09-29, first version: [http://tantek.com/presentations/2005/03/elementsofxhtml/ 2005-03-13 at SXSW Interactive]).
* ...
* See also more microformats [[presentations]] in general.

=== POSH関連書籍 ===
Modern web design books which document good semantic HTML practices.
* <cite>[http://www.oreilly.com/catalog/wdnut3/ http://www.oreilly.com/catalog/covers/0596009879_thumb.gif] [http://www.oreilly.com/catalog/wdnut3/ Web Design in a Nutshell, <strong>Third Edition</strong>]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Jennifer</span> <span class="additional-name">Niederst</span> <span class="family-name">Robbins</span></span> See [http://jenville.com/ Jenville].</span>
* <cite>[http://microformatique.com/book/ Microformats empowering your markup for Web 2.0]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">John</span> <span class="family-name">Allsopp</span>.</span></span> Chapter 3 is a detailed and practical overview of the appropriate use of structural, valid and semantic HTML.
* <cite>[http://htmlmastery.com/ http://htmlmastery.com/images/hm-cover-sm.gif][http://htmlmastery.com/ Semantics, Standards and Styling]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Paul</span> <span class="family-name">Haine</span>.</span></span>

=== POSH関連雑誌 ===
Online (and off) magazines which frequently publish articles about semantic HTML. If/when this section gets too big, we can move it to [[posh-magazines]].

* [http://alistapart.com/ A List Apart: For People Making Websites] (see in particular [http://www.alistapart.com/topics/code/htmlxhtml/ HTML and XHTML Articles])
* [http://www.digital-web.com/ Digital Web Magazine]

=== POSH関連ブログ ===
Blogs that with some regularity post high quality discussions, insights, and in general have advanced the state of the art of POSH. If/when this section gets too big, we can move it to [[posh-blogs]].

* [http://dbaron.org/log/current David Baron's weblog]
* [http://zeldman.com/ Jeffrey Zeldman Presents]
* [http://meyerweb.com/ meyerweb.com - Eric Meyer]
* [http://microformatique.com/ Microformatique - John Allsopp]
* [http://simplebits.com/ SimpleBits - Dan Cederholm] (see in particular [http://simplebits.com/bits/simplequiz/ SimpleQuiz])
* [http://tantek.com/ Tantek Çelik]
* ...

=== POSH関連ブログ記事 ===
Blog posts that provide specific, modern, guidance, techniques and tips for using more and better semantic HTML. This list is ''incomplete''. We know there are lots more blog posts out there that fit the aforementioned description - please add them! If/when this section gets too big, we can move it to [[posh-blog-posts]].

* [http://www.plaintxt.org/wp-content/uploads/sandbox-v09_readme.html The Sandbox theme for WordPress readme.html] discusses what POSH is and how the theme helps users use it.
* [http://tantek.com/log/2002/10.html#L20021022t1432 Bed and BReakfast markup (B&BR)] (2002-10-22) - avoiding nonsemantic uses of <nowiki><b>old and <br>eak</nowiki> tags and using <nowiki><h3>adings and <p>aragraphs</nowiki> instead.
* [http://tantek.com/log/2002/11.html#L20021128t1352 <nowiki><A>norexic </A>nchors</nowiki>] (2002-11-28) - use the "id" attribute on existing elements instead of adding empty <code><nowiki><a name="foo"></a></nowiki></code> elements. Use [[rel-bookmark]] for post permalinks within the document.
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class] (2002-12-16) - introduction to proper use of the HTML 'class' attribute.
* [http://tantek.com/log/2002/12.html#L20021231t1850 Dive into Semantic MARKup] (2002-12-31)
* [http://tantek.com/log/2003/01.html#L20030104t1249 Comment markup, presentation and plumbing] (2003-01-04) - how to markup a list of comments, including example use of the rare "hreflang" attribute.
* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer] (2004-07-18)
* [http://tantek.com/log/2004/07.html#d20t2359 More about the 'class' attribute] (2004-07-20)
* [http://www.uie.com/articles/holzschlag_interview/ Web Standards in the Real World: An Interview with Molly Holzschlag] (2005-06-01)
* [http://westciv.typepad.com/dog_or_higher/2005/11/webpatterns_and.html Webpatterns and websemantics] (2005-11-18)
* [http://www.thefutureoftheweb.com/blog/2006/2/writing-semantic-html Writing Semantic HTML by Jesse Skinner] (2006-02-22)
* [http://www.thefutureoftheweb.com/blog/2007/1/who-will-read-your-semantic-html Who will read your Semantic HTML?] by Jesse Skinner (2007-01-04)
* [http://microformatique.com/?page_id=109 Semantics in HTML] by John Allsopp (2007-01-08 - 2007-03-12)
** [http://microformatique.com/?p=83 Part I - Traditional HTML Semantics] (2007-01-08)
** [http://microformatique.com/?p=97 Part II - standardizing vocabularies] (2007-02-20)
** [http://microformatique.com/?p=108 Part III - Towards a semantic web] (2007-03-12)
* [http://microformatique.com/?p=82 Built in HTML semantics] A list of the semantic elements and attributes of HTML by John Allsopp (2007-01-08)
* [http://tantek.com/log/2007/04.html#d20t0823 The Importance of Being POSH] by Tantek Çelik (2007-04-20)
* [http://factoryjoe.com/blog/2007/04/21/getting-back-to-posh-plain-ol-semantic-html/ Getting back to POSH (Plain ol’ Semantic HTML)] by Chris Messina (2007-04-21)
* [http://friedcellcollective.net/outbreak/2007/04/22/im-posh-are-you/ I’m POSH - are you?] (2007-04-23)
* [http://www.unintentionallyblank.co.uk/2007/04/24/plain-old-semantic-html/ The Internet’s Upper Class Or Why Your Site Should Be POSH] (2007-04-24)
* [http://nate.koechley.com/blog/2006/12/15/divitis_and_correct_div_usage/ On Appropriate Use of DIVs, or When Divitis Doesn’t Apply] by Nate Koechley, 2006-12-15
* [http://nate.koechley.com/blog/2006/12/22/note_on_structural_and_semantic_meaning/ Quick Comment: Choose Class/ID Names Based on Semantic and/or Structural Meaning] by Nate Koechley, 2006-12-22
* [http://leland.nu/think/2006/07/31/seeing-is-believing/ SEEing is believing] - using standards and efficient design, coding, maintenance, and marketing to produce a search-engine-efficient site by Richard Leland (2006-07-31)
* ...

See [http://technorati.com/search/%22semantic%20HTML%22 more blogs talking about "semantic HTML"] and [http://technorati.com/search/posh+semantic+HTML POSH].

===POSH関連ポッドキャスト===
* [http://www.netmag.co.uk/podcasts/07-05-03-net.mp3 A talk about POSH] in the .Net magazine podcast episode 8 (56 minutes; 26 Mb. Relevant section 30:10-42:40)

=== POSHにまつわる隠れた情報源 ===
The following sites have POSH related articles, tutorials etc. on them, but you have to dig for them from the home page. Help find the hidden POSH treasures in these sites and add ''direct'' links to POSH related articles, tutorials etc. to the specific sections above. You can leave the top level site links here until/unless you have dug thru the entire site and found all the treasures.
* [http://www.w3schools.com/ W3Schools Online Web Tutorials]
* [http://dev.opera.com/ Dev.Opera]

=== POSH Bling for your Blog ===
If you want to improve your existing blog, there are some pretty simple things you can do:

==== WordPress ====
* Use the [http://www.plaintxt.org/themes/sandbox/ Sandbox] or [http://getk2.com K2] themes that already support hAtom and hCard
* Add the [http://redmonk.net/archives/2007/04/18/wordpress-widget-hcard-about-box/ hCard About Widget] to your site

== POSHを広める ==
Now that you've poshified your website(s), what next? Well, help spread POSH to other websites!

* Promote POSH. Make a POSH button (perhaps using semantic HTML and CSS ;) linking to this page and put it on your site, in your blogroll, in your footer, etc. Maybe even come up with a nice POSH button graphic and share it with the microformats community with a liberal license (public domain, CC-by-3.0, MIT, etc.) Like these:
** [http://redmonk.net/archives/2007/04/25/the-new-question/ http://redmonk.net/wp-content/uploads/2007/04/are_you_posh.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
** [http://redmonk.net/archives/2007/04/26/chic/ http://redmonk.net/wp-content/uploads/2007/04/chic_fancy.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
* Tell a friend. Talk to web design friends about POSH and convince and help them to poshify both their personal websites, and the websites they build for others. Blog about your experience with poshification and what steps you went through to poshify your websites. Write a [[posh-testimonial]]!
* Come up with more ideas to help spread POSH. Here are a few.
** Hold a PoshPit - a one or half day marathon session mixing semantic HTML experts with folks who maintain/run web sites in general and see how many websites you can collectively upgrade to POSH during the course of the day.
** ...

== POSHを改善する ==
As you read the [[posh#Resources|POSH resources]] documented here, what other POSH resources did you find? Add them to this page.

With your experience with both poshifying your sites and helping others do so, what have you learned? What kind of [[posh-issues|issues]] did you run into? What questions were commonly asked? What do you feel like you need to more easily and quickly help more people poshify their content?

== 歴史 ==
A brief history of references to "POSH" in this context and "plain old semantic HTML".

=== plain old semantic HTML ===
The earliest references to <strong>"plain old semantic HTML"</strong> that have been found so far are:
* [http://groups.google.com/group/comp.infosystems.www.authoring.site-design/msg/2373e9043c08cba4 1998-05-01: Kirrily 'Skud' Robert on comp.infosystems.www.authoring.site-design] - "The site is implemented in HTML 4.0 Transitional with style sheets; this means that anyone with an older browser won't get presentational markup, just <strong>plain old semantic HTML</strong>. "
* [http://www.highrankings.com/advisor/tables-seo/ 2006-09-21 Drew's comment by on "Tables and SEO"]: "I’d say it’s well worth it for a variety of reasons to only use tables when you’re presenting tabular data, and use <strong>plain old semantic HTML</strong> to mark up your content in all other cases." (retrieved by [[User:Tantek|Tantek]] 08:20, 20 Apr 2007 (PDT))
If you can find earlier references, please ''add'' them and include a brief quotation of the context of the reference to "plain old semantic HTML".

Main Page-ja

2007-07-25T07:18:37Z

IwaiMasaharu: /* はじめに */ POSHのリンク先を日本語ページに。

Microformats Wikiにようこそ！

[[introduction-ja|microformatsの手引き]]からどうぞ。編集を始めるまえには[[how-to-play-ja]]を読んでください。

__TOC__

== はじめに ==

* First, read up on what it means to be [http://microformats.org/wiki/posh-ja <abbr title="Plain Old Semantic HTML">POSH</abbr>] {{NewMarker}}.
* See the [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations-ja|プレゼンテーション]], [[books]], [[podcasts|ポッドキャスト]], and [[screencasts|スクリーンキャスト]].
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary|用語集]] for new terms.
* 識者からもっと教わりたいことがあれば、[[events|microformatsのイベント]]をどうぞ。

== 定義 ==

[http://microformats.org/discuss/ メーリングリスト]([[mailing-lists]])での一般的な定義は、「分散的開発を実現するために用いられる、セマンティクスをHTMLに埋め込む為のシンプルな仕様」です。もう少し細かく説明すると、microformatsは下記のように定義できます。
:分散的開発を実現するために用いられる
::Webにあるリソースそのものや、それを利用するツールやサービスを分散的に処理できるようにします。
:セマンティクスをHTMLに埋め込むための
::それぞれの分野に特化することで、各仕様が小さいものとなります。
:シンプルな仕様
:人間が解読できる(X)HTML/XMLドキュメントやAtom/RSSフィード、そしてプレーンなXMLでの提供
::現存するコンテンツの利用パターンを標準化することからはじめています。
::概略的で説明的なclass名を使い、ソースをみてもわかりやすくなっています。
::現存の相互運用できる規格に基づくことにより、汎用性が高まります。

「ブラウザーでWeb巡回しかしないんだ。それはまた20世紀的だね。」 -- [http://diveintomark.org Mark Pilgrim]

See more explanations of [[what-are-microformats|what are microformats]], and [[what-can-you-do-with-microformats|what you can do with them]].

== 協力の方法 ==

microformatsをより発展させるためには次のことができます。

* [[advocacy|Advocate]] the use of microformats.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
*[http://microformats.org/discuss mailing lists] と [[irc|IRC Channel]] に参加しマイクロフォーマットに関して質問したり学んだりすることができます。
*[[Main_Page-ja#.E4.BB.96.E8.A8.80.E8.AA.9E.E3.81.A7.E3.81.AEmicroformats_wiki|他言語でのmicroformats wiki]]を見てください。そして、世界中の人が利用しやすくするためにmicroformats wikiの翻訳を手伝ってください。
* Find [[orphans|orphaned]] pages, and add links to them.
* Before proposing any new microformats, make sure your website is [[POSH]] and uses existing microformats, and then read the [[process]].

== 仕様 ==

以下はオープンスタンダードとなった[[microformats-ja|microformats]]の仕様です。([[implementations|実装]]や[[examples-in-the-wild|実世界での例]]もご覧ください)

* [[hcalendar-ja|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator](翻訳中！)
* [[hcard-ja|hCard]] - [http://microformats.org/code/hcard/creator hcard creator](翻訳中！)
* [[rel-license-ja|rel-license]](翻訳完了)
* [[rel-nofollow-ja|rel-nofollow]](翻訳完了)
* [[rel-tag-ja|rel-tag]](翻訳完了)
* [[vote-links-ja|Vote Links]](翻訳完了)
* [http://gmpg.org/xfn/ XFN] ([[xfn-implementations|XFNの実装]]もご覧下さい)
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo-ja|XOXO]](翻訳中！)

== ドラフト ==

* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]]
* [[hresume|hResume]]
* [[hreview-ja|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== デザインパターン ==

{{design_patterns-ja}} 

== Exploratory Discussions ==
Per the microformats [[process]]:
実世界での[[examples|例]]の調査や分析、既に存在するフォーマット、またmicroformatsにできそうなもののブレインストーミングをまとめています。もし何かページを追加した場合、まず[[rejected-formats]]を見てから行ってください。
* alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]
*[[attention]]
* audio-info ([[audio-info-examples|examples]], [[audio-info-formats|formats]], [[audio-info-brainstorming|brainstorming]], [[audio-info-proposal|proposal]]) - Marking up information and metadata related to audio (speech, music, and sound in general). {{NewMarker}}
* blog description [[blog-description-examples|blog description examples]]
* blog info [[blog-info-examples|blog info examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]
* code [[code-examples| code examples]], [[code-brainstorming|code brainstorming]] {{NewMarker}}
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[collection-description|collection description]] - for describing collections in libraries {{NewMarker}}
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]
* [[depend-examples]]: examples of dependency graphs, especially as they relate to software {{NewMarker}}
* [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) {{NewMarker}}
* directions [[directions-examples|directions examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]
* error messages [[error-message-examples|error message examples]], [[error-message-brainstorming|error message brainstorming]]
* forms [[forms-examples|forms examples]]
* file-format ([[file-format-examples|examples]], formats, brainstorming) - for the mark-up of file format information (size, type, codecs, bitrate, etc.) {{NewMarker}}
* genealogy [[genealogy-formats|genealogy exploration]]
* geo extensions
** [[geo-extension-strawman]] - extend geo for moons, other planets, etc.
** [[geo-elevation-examples]] - extend geo for representing altitude {{NewMarker}}
** [[geo-waypoint-examples]] - extend geo for representing routes and boundaries, using waypoints {{NewMarker}}
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]
* hash [[hash-examples|hash examples]]
* grouping ([[grouping-examples|examples]], [[grouping-formats|formats]], [[grouping-brainstorming|brainstorming]], [[grouping-proposal|proposal]]) - Metadata markup of items that should be grouped together. {{NewMarker}}
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]]
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]]
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]
* [[htodo|hToDo]]
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) {{UpdateMarker}}
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]
* [[mfo-examples|MFO examples]]
* music [[music-examples|music examples]] {{UpdateMarker}}
* news [[news-examples|news examples]] {{NewMarker}}
* photo note [[photo-note-examples|photo note examples]]
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}
* receipt ([[receipt-examples|examples]], [[receipt-formats|formats]], [[receipt-brainstorming|brainstorming]], [[receipt-proposal|proposal]]) - Marking up information and metadata related to purchase receipts. {{NewMarker}}
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|search results example]]
* show [[show-brainstorming|show brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|tagspeak examples]]
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].
* transit table [[transit-table-examples|transit table examples]]
* [[uid]]
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]
* [[wiki-formats|wiki formats]]
* 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]]
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])
*[[realestate-propertydetail|realestate-propertydetail brainstorming]]

== 例 ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== ツール、テストケース、リサーチ ==

事例やコードやテストケースを見るために最初に見るべき場所はmicroformatを使ったそれぞれのページです. 二つ以上のmicroformatを使うツールやサービスは少ししかありません. このセクションは複数のmicroformatに関連するエディター、パーサー、妥当性検証ソフト、テストケース、その他情報等のためのものです。

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[internationalization]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]
*[[why-are-content-standards-hard]]
*[[profile-examples-in-wild|Profile examples, in the wild]]

== リソース ==

* [[events]]
* [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.
* [[spread-microformats]]
* [[buttons]]
* [[icons-ja]]
* [[demo|デモ]] - microformatを試すデモへのリンク集
* [[semacode|Semacode]]
* [[jobs]]
* [[user-interface]]
* [[marked-for-deletion]]
* [[microformats-issues]] {{NewMarker}} - 一つ以上のmicroformatに関するissue
* [[spellcheck|spell-check dictionary]]

== 共用ワークスペース ==
* [[to-do]]
* [[microformats-issues]] - issues related to more than one microformat.
* [[external-issues]]

== 他言語でのmicroformats wiki ==

microformatsの記事を色々な言語で読んだり編集したりできます。

* 100以上の記事のある言語
** [[Main_Page|English (本家の英語)]]
** [[Main_Page-fr|Francais (フランス語)]] {{UpdateMarker-fr}}
* 10以上の記事のある言語
** [[Main_Page-pt-br| Português (ブラジル系ポルトガル語)]]
** [[Main_Page-ja|日本語]]
* 2以上の記事のある言語
** [[Main_Page-es|Espanol (スペイン語)]]
** [[Main_Page-de|Deutsch (ドイツ語)]]
** [[Main_Page-ro|Romanian]]
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.
See also [[other-languages]], and [[how-to-start-new-translation-ja|how-to-start-a-new-translation]].

vote-links-ja

2007-07-21T20:07:57Z

IwaiMasaharu: Reverted edit of SajY01, changed back to last version by Tantek

= Vote Links =
__TOC__
== Specification 2005 ==
=== 編者 ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.] (formerly of [http://microsoft.com/ Microsoft Corporation])

=== 着想 ===
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati,Inc.]

=== 作者 ===
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati, Inc]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]

=== 著作権 ===
{{MicroFormatCopyrightStatement2004-ja}}

=== Patents ===
{{MicroFormatPatentStatement-ja}}

=== 謝辞 ===
Vote Linksに対しフィードバックをくれたみなさんに感謝します。特にEtanWexler、彼はVote Linksの文書に置いて初めて、Vote Linksはrel属性ではなくrev属性を使うべきだと指摘しました（[[vote-links-faq]]）。また同じくrel属性について考え、relやrev、linktypesの利用法を[[rel-faq ]]としてまとめたJohn Allsoppにも謝辞を述べたいと思います。

== 概要 ==
トラッキングやインデックス作成を行うアプリケーションが、リンク先の文書に対するページ作者のスタンスを理解していないというのは問題です。賛成や支持だけではなく、リンクしたリソースの内容に反論したい、又はもっと議論を重ねたい場合があるはずですから。

== 仕様 ==
Vote Linksは[[elemental-microformat-ja|単純microformat]]と呼ばれる、[[microformats]]オープンスタンダードのひとつです。
私たちはHTMLにてハイパーリンクを張るa要素、そのrev属性に対し、3つの新しい値を提案します。

"vote-for"、"vote-abstain"、そして"vote-against"がVote Linksで用いられる属性値です。これら3つの値は互いに相容れないものであり、それぞれ順に賛成、中立又は棄権、そして反対を表します。

アプリケーションの解釈にも寄りますが、rev属性のないVote Linkは"vote-for"又は"vote-abstain"として扱われることがあります。

リンクには人が分かり易いよう、補助的なコメントをtitle属性を用いて与えることが可能です。一般のブラウザであれば、コメントはリンクのロールオーバー時に現れるでしょう。

では、Vote Linksの例です。
<pre><nowiki>
<a rev="vote-for" href="http://ragingcow.blogspot.com"
title="neat spoof">Raging Cow</a>
<a rev="vote-against" href="http://ragingcow.com"
title="nasty corn syrup drink">Raging Cow</a>
</nowiki></pre>

=== 廃止された案: rel属性を用いたVote Links ===
前ドラフトではrev属性の代わりにrel属性を用いてリンクを張っていました。これに対しいくつかのフィードバックや分析が寄せられた結果、rel属性を使うのは適切ではなく、rev属性の方が意味をより正確に伝えられると判断されました。詳しくは[[rel-faq]]をご覧ください。

Vote Linksを解釈する実装系に関しては、後方互換性の為、rel属性を用いたリンクを解釈してもよい（MAY）となっています。

しかしWebページ作者はrel属性をVote Linksで使ってはいけません（MUST NOT）。

== XMDPプロファイル ==
<pre><nowiki>
<dl class="profile">
<dt id="rev">rev</dt>
<dd><p><a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rev">
HTML4 definition of the 'rev' attribute.</a>
Here are some additional values.</p>
<dl>
<dt id="vote-for">vote-for</dt>
<dd>Indicates agreement with or recommendation for the referred resource.</dd>
<dt id="vote-abstain">vote-abstain</dt>
<dd>Indicates abstention or indifference for the referred resource.</dd>
<dt id="vote-against">vote-against</dt>
<dd>Indicates disagreement with or recommendation against the referred resource.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== 実装 ==
このセクションは'''参考情報'''です。

* [http://jyte.com/cl/jyte-should-integrate-microformats-votelinks vote-links claim]によると、[http://jyte.com/profile/brianellin.com Brian Ellin]はVote Linksを[http://jyte.com Jyte]上に、わずか30分で実装したとのことです。

* [http://moloko.itc.it/paoloblog/ Paolo Massa]は[http://moloko.itc.it/paoloblog/semantic_links/ SemanticLinks]というFirefoxの拡張を開発しています。これはvote-for又はvote-againstが付いたリンクを表示する、というものです。(なお、現在は作者の手によりSemanticLinksのダウンロード先が消されています)

== 標準仕様 ==
* [http://gmpg.org/xmdp/ XMDP]

== 関連仕様 ==
* [[xoxo]]
* [http://gmpg.org/xfn/ XFN]
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]
* [[rel-license]]
* [[rel-tag]]
* [[rel-nofollow]]

== FAQ ==
* Vote LinkのFAQは[[vote-links-faq]]に、rel属性に関するものは[[rel-faq]]をご覧ください。
* [[vote-links-issues]]には、このVote Links [[microformat]]に関して、いくつかの提案があります。

User:IwaiMasaharu

2007-07-21T19:30:07Z

IwaiMasaharu: /* profile */

== profile ==

My name is IWAI, Masaharu a.k.a. iwaim. I'm one of the Japanese Wiki translators/localizers.

* http://iwaim.beering.be/
* http://d.hatena.ne.jp/iwaim/
* [[User:IwaiMasaharu/greasemonkey-user-scripts|greasemonkey user scripts for Microformats Wiki]]

== ドキュメント ==

*[[User:IwaiMasaharu/guidance-of-translation-ja|翻訳の手引き(私家版)]]

== 日本語版ローカルルール(私家版)==

*日本語の言語コードは「ja」なので、翻訳時にはページの末尾に「-ja」を付けましょう。
*冒頭に「<nowiki></nowiki>」という感じでベースとなった英語版を指定しましょう。
*句読点は"、"と"。"を使いましょう。

== ツール ==

=== 対訳表 ===

*[[User:IwaiMasaharu/english-to-japanese-map|英日対訳表]]
*[[User:IwaiMasaharu/english-to-japanese-map-for-wiki-notation|Wiki記法の英日対応表]]

=== 閲覧補助 ===

*[[User:IwaiMasaharu/greasemonkey-user-scripts|Greasemonkey ユーザスクリプト集]]

semantic-html-ja

2007-07-21T19:23:44Z

IwaiMasaharu: リダイレクトの作成

#REDIRECT:[[semantic-xhtml-ja]]

posh-ja

2007-07-21T19:21:33Z

IwaiMasaharu: semantic-htmlのリンク先を日本語訳へ

<h1>Plain Old Semantic HTML (POSH)</h1>

<abbr title="Plain Old Semantic HTML">POSH</abbr>のホームページ（日本語版）へようこそ。（[[posh|英語版]]）

__TOC__

== 起源 ==
'''POSH'''という用語は、[http://rbach.priv.at/Microformats-IRC/2007-04-06#T091456 2007年4月6日にmicroformatsのIRCチャネルにおいて]、<kwijibo>によって考案されました。POSHとは、[[plain-old-semantic-html]]の頭文字を取った略語です。John Allsopp、Tantek Çelik、Jeremy Keith、Chris Messinaらが[[events/2007-04-18-web-2-expo-dinner|2007年4月18日のWeb 2.0 Expo後に行われたMicroformats Dinner]]で交わした議論を通して、microformatsのよりどころでありそれが正しいサブセットともなっているPOSHの発想と、そのより幅広い目標を広めることの重要性があらためて注目されました。詳しくは[[posh#History|POSHの歴史]]を参照してください。

== 理由 ==
[[semantic-html-ja|意味的（セマンティック）なHTML]]という用語はやや仰々しく、それがどれほどシンプルなものであり昨今のウェブデザイナーたちの間でいかに確固たる支持を受けているかということも、意味的なマークアップを用いてウェブを真っ当に作ることだけにとどまらない大きなメリットをもたらすということも、いずれもうまく伝えられていません。私たちは、そのコンセプトの本質をうまく表現でき、簡単に動詞にも応用できるような（たとえば「to posh」「poshify」「poshed up」などという使い方ができるような）、覚えやすい用語を必要としていたのです。

== POSHとは？ ==
POSHとは、Webページを作成する際に[[semantic-html-ja|意味的なHTML]]を用いることのベストプラクティスを簡潔にあらわしたものです。意味的なHTMLとは、HTML 4.01（またはXHTML 1.0）にある要素と属性のなかで、''[[presentational|表現的]]''ではなく''[[semantic|意味的]]''なものから成るサブセットのこと。POSHを習い理解する最も良い方法は、実践することです。あなたのWebサイトからいちページを選び、[[posh-ja#POSH.E3.83.81.E3.82.A7.E3.83.83.E3.82.AF.E3.83.AA.E3.82.B9.E3.83.88|POSHチェックリスト]]を適用してください。[[posh-ja#POSH.E3.83.97.E3.83.AD.E3.82.BB.E3.82.B9|POSHプロセス]]に則り、そのまま続けてください。POSHについてより詳しく学ぶには、[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]をお読みください。

== POSHプロセス ==
あなたがPOSHであるために、そしてあなたのウェブサイトをPOSHなものにするためには、何ができるでしょうか？

# POSHなコンテンツを公開する。[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]に目を通し、あなたのウェブサイトでvalidな[[semantic-html-ja|意味的な(X)HTML]]を公開し、それに伴って[[semantic-class-names]]を使用するように心がけましょう。
# POSHを広める。このページへのリンクを貼って、他の人たちもPOSHになるように、そしてウェブサイトをPOSH対応させる（POSHify）ように勧めてみましょう。
# POSHを改善する。より多くの人が手軽にウェブサイトをPOSH対応させられるように、POSHリソースの収集をお手伝いください。

== POSHチェックリスト ==
* POSHの最初のルールとして、まずあなたのPOSHを必ず[http://validator.w3.org 検証]しましょう。
* 次に、単なる表現上の目的で使われているTABLEや、スペーサーGIF画像、いわゆる[[presentational-html|表現的なHTML]]を取り除きましょう。
* さらに、（BタグやBRタグの濫用を典型とする）[http://tantek.com/log/2002/10.html#L20021022t1432 その場しのぎ（'''B'''ed and '''BR'''eakfast）]のマークアップを修正しましょう。
* [http://tantek.com/log/2002/11.html#L20021128t1352 空っぽアンカー（Anorexic Anchors）]を取り除きましょう。
* よい[[semantic-class-names|意味的なクラス名]]を使いましょう。
* ...

== POSHリソース ==
=== POSHチュートリアル ===
Step by step tutorials to create POSH content or upgrade existing content to POSH.

* [http://westciv.com/style_master/house/tutorials/quick/validation/index.html Validating your css and html] A simple step by step guide to how and why you should validate your markup
* ...

=== POSH関連ブックマーク ===
* Ma.gnoliaの[http://ma.gnolia.com/groups/posh POSHグループ]をチェックしてみてください。
* See pages tagged both [http://del.icio.us/tag/posh+microformats POSH and microformats] on del.icio.us.

=== POSH関連プレゼンテーション ===
Presentations which explain and advocate concepts and techniques for utilizing semantic HTML. If/when this section gets too big, we can move it to [[posh-presentations]].
* [http://tantek.com/presentations/2003SXSW/stylesheets.html CSS: Between the Style Sheets by Tantek Çelik (2003-03)], specifically, see slides 3-4,6 starting with "Leaving the [http://tantek.com/log/2002/10.html#L20021022t1432 <B>ed & <BR>eakfast]", and slide 9 "CSS & the Semantic Spectrum" which provides an overview of the semantic spectrum of (X)HTML tags.
* [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics] (2004-02-11)
* [http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean] (2004-09-28)
* [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (2005-09-29, first version: [http://tantek.com/presentations/2005/03/elementsofxhtml/ 2005-03-13 at SXSW Interactive]).
* ...
* See also more microformats [[presentations]] in general.

=== POSH関連書籍 ===
Modern web design books which document good semantic HTML practices.
* <cite>[http://www.oreilly.com/catalog/wdnut3/ http://www.oreilly.com/catalog/covers/0596009879_thumb.gif] [http://www.oreilly.com/catalog/wdnut3/ Web Design in a Nutshell, <strong>Third Edition</strong>]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Jennifer</span> <span class="additional-name">Niederst</span> <span class="family-name">Robbins</span></span> See [http://jenville.com/ Jenville].</span>
* <cite>[http://microformatique.com/book/ Microformats empowering your markup for Web 2.0]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">John</span> <span class="family-name">Allsopp</span>.</span></span> Chapter 3 is a detailed and practical overview of the appropriate use of structural, valid and semantic HTML.
* <cite>[http://htmlmastery.com/ http://htmlmastery.com/images/hm-cover-sm.gif][http://htmlmastery.com/ Semantics, Standards and Styling]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Paul</span> <span class="family-name">Haine</span>.</span></span>

=== POSH関連雑誌 ===
Online (and off) magazines which frequently publish articles about semantic HTML. If/when this section gets too big, we can move it to [[posh-magazines]].

* [http://alistapart.com/ A List Apart: For People Making Websites] (see in particular [http://www.alistapart.com/topics/code/htmlxhtml/ HTML and XHTML Articles])
* [http://www.digital-web.com/ Digital Web Magazine]

=== POSH関連ブログ ===
Blogs that with some regularity post high quality discussions, insights, and in general have advanced the state of the art of POSH. If/when this section gets too big, we can move it to [[posh-blogs]].

* [http://dbaron.org/log/current David Baron's weblog]
* [http://zeldman.com/ Jeffrey Zeldman Presents]
* [http://meyerweb.com/ meyerweb.com - Eric Meyer]
* [http://microformatique.com/ Microformatique - John Allsopp]
* [http://simplebits.com/ SimpleBits - Dan Cederholm] (see in particular [http://simplebits.com/bits/simplequiz/ SimpleQuiz])
* [http://tantek.com/ Tantek Çelik]
* ...

=== POSH関連ブログ記事 ===
Blog posts that provide specific, modern, guidance, techniques and tips for using more and better semantic HTML. This list is ''incomplete''. We know there are lots more blog posts out there that fit the aforementioned description - please add them! If/when this section gets too big, we can move it to [[posh-blog-posts]].

* [http://www.plaintxt.org/wp-content/uploads/sandbox-v09_readme.html The Sandbox theme for WordPress readme.html] discusses what POSH is and how the theme helps users use it.
* [http://tantek.com/log/2002/10.html#L20021022t1432 Bed and BReakfast markup (B&BR)] (2002-10-22) - avoiding nonsemantic uses of <nowiki><b>old and <br>eak</nowiki> tags and using <nowiki><h3>adings and <p>aragraphs</nowiki> instead.
* [http://tantek.com/log/2002/11.html#L20021128t1352 <nowiki><A>norexic </A>nchors</nowiki>] (2002-11-28) - use the "id" attribute on existing elements instead of adding empty <code><nowiki><a name="foo"></a></nowiki></code> elements. Use [[rel-bookmark]] for post permalinks within the document.
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class] (2002-12-16) - introduction to proper use of the HTML 'class' attribute.
* [http://tantek.com/log/2002/12.html#L20021231t1850 Dive into Semantic MARKup] (2002-12-31)
* [http://tantek.com/log/2003/01.html#L20030104t1249 Comment markup, presentation and plumbing] (2003-01-04) - how to markup a list of comments, including example use of the rare "hreflang" attribute.
* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer] (2004-07-18)
* [http://tantek.com/log/2004/07.html#d20t2359 More about the 'class' attribute] (2004-07-20)
* [http://www.uie.com/articles/holzschlag_interview/ Web Standards in the Real World: An Interview with Molly Holzschlag] (2005-06-01)
* [http://westciv.typepad.com/dog_or_higher/2005/11/webpatterns_and.html Webpatterns and websemantics] (2005-11-18)
* [http://www.thefutureoftheweb.com/blog/2006/2/writing-semantic-html Writing Semantic HTML by Jesse Skinner] (2006-02-22)
* [http://www.thefutureoftheweb.com/blog/2007/1/who-will-read-your-semantic-html Who will read your Semantic HTML?] by Jesse Skinner (2007-01-04)
* [http://microformatique.com/?page_id=109 Semantics in HTML] by John Allsopp (2007-01-08 - 2007-03-12)
** [http://microformatique.com/?p=83 Part I - Traditional HTML Semantics] (2007-01-08)
** [http://microformatique.com/?p=97 Part II - standardizing vocabularies] (2007-02-20)
** [http://microformatique.com/?p=108 Part III - Towards a semantic web] (2007-03-12)
* [http://microformatique.com/?p=82 Built in HTML semantics] A list of the semantic elements and attributes of HTML by John Allsopp (2007-01-08)
* [http://tantek.com/log/2007/04.html#d20t0823 The Importance of Being POSH] by Tantek Çelik (2007-04-20)
* [http://factoryjoe.com/blog/2007/04/21/getting-back-to-posh-plain-ol-semantic-html/ Getting back to POSH (Plain ol’ Semantic HTML)] by Chris Messina (2007-04-21)
* [http://friedcellcollective.net/outbreak/2007/04/22/im-posh-are-you/ I’m POSH - are you?] (2007-04-23)
* [http://www.unintentionallyblank.co.uk/2007/04/24/plain-old-semantic-html/ The Internet’s Upper Class Or Why Your Site Should Be POSH] (2007-04-24)
* [http://nate.koechley.com/blog/2006/12/15/divitis_and_correct_div_usage/ On Appropriate Use of DIVs, or When Divitis Doesn’t Apply] by Nate Koechley, 2006-12-15
* [http://nate.koechley.com/blog/2006/12/22/note_on_structural_and_semantic_meaning/ Quick Comment: Choose Class/ID Names Based on Semantic and/or Structural Meaning] by Nate Koechley, 2006-12-22
* [http://leland.nu/think/2006/07/31/seeing-is-believing/ SEEing is believing] - using standards and efficient design, coding, maintenance, and marketing to produce a search-engine-efficient site by Richard Leland (2006-07-31)
* ...

See [http://technorati.com/search/%22semantic%20HTML%22 more blogs talking about "semantic HTML"] and [http://technorati.com/search/posh+semantic+HTML POSH].

===POSH関連ポッドキャスト===
* [http://www.netmag.co.uk/podcasts/07-05-03-net.mp3 A talk about POSH] in the .Net magazine podcast episode 8 (56 minutes; 26 Mb. Relevant section 30:10-42:40)

=== POSHにまつわる隠れた情報源 ===
The following sites have POSH related articles, tutorials etc. on them, but you have to dig for them from the home page. Help find the hidden POSH treasures in these sites and add ''direct'' links to POSH related articles, tutorials etc. to the specific sections above. You can leave the top level site links here until/unless you have dug thru the entire site and found all the treasures.
* [http://www.w3schools.com/ W3Schools Online Web Tutorials]
* [http://dev.opera.com/ Dev.Opera]

=== POSH Bling for your Blog ===
If you want to improve your existing blog, there are some pretty simple things you can do:

==== WordPress ====
* Use the [http://www.plaintxt.org/themes/sandbox/ Sandbox] or [http://getk2.com K2] themes that already support hAtom and hCard
* Add the [http://redmonk.net/archives/2007/04/18/wordpress-widget-hcard-about-box/ hCard About Widget] to your site

== POSHを広める ==
Now that you've poshified your website(s), what next? Well, help spread POSH to other websites!

* Promote POSH. Make a POSH button (perhaps using semantic HTML and CSS ;) linking to this page and put it on your site, in your blogroll, in your footer, etc. Maybe even come up with a nice POSH button graphic and share it with the microformats community with a liberal license (public domain, CC-by-3.0, MIT, etc.) Like these:
** [http://redmonk.net/archives/2007/04/25/the-new-question/ http://redmonk.net/wp-content/uploads/2007/04/are_you_posh.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
** [http://redmonk.net/archives/2007/04/26/chic/ http://redmonk.net/wp-content/uploads/2007/04/chic_fancy.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
* Tell a friend. Talk to web design friends about POSH and convince and help them to poshify both their personal websites, and the websites they build for others. Blog about your experience with poshification and what steps you went through to poshify your websites. Write a [[posh-testimonial]]!
* Come up with more ideas to help spread POSH. Here are a few.
** Hold a PoshPit - a one or half day marathon session mixing semantic HTML experts with folks who maintain/run web sites in general and see how many websites you can collectively upgrade to POSH during the course of the day.
** ...

== POSHを改善する ==
As you read the [[posh#Resources|POSH resources]] documented here, what other POSH resources did you find? Add them to this page.

With your experience with both poshifying your sites and helping others do so, what have you learned? What kind of [[posh-issues|issues]] did you run into? What questions were commonly asked? What do you feel like you need to more easily and quickly help more people poshify their content?

== 歴史 ==
A brief history of references to "POSH" in this context and "plain old semantic HTML".

=== plain old semantic HTML ===
The earliest references to <strong>"plain old semantic HTML"</strong> that have been found so far are:
* [http://groups.google.com/group/comp.infosystems.www.authoring.site-design/msg/2373e9043c08cba4 1998-05-01: Kirrily 'Skud' Robert on comp.infosystems.www.authoring.site-design] - "The site is implemented in HTML 4.0 Transitional with style sheets; this means that anyone with an older browser won't get presentational markup, just <strong>plain old semantic HTML</strong>. "
* [http://www.highrankings.com/advisor/tables-seo/ 2006-09-21 Drew's comment by on "Tables and SEO"]: "I’d say it’s well worth it for a variety of reasons to only use tables when you’re presenting tabular data, and use <strong>plain old semantic HTML</strong> to mark up your content in all other cases." (retrieved by [[User:Tantek|Tantek]] 08:20, 20 Apr 2007 (PDT))
If you can find earlier references, please ''add'' them and include a brief quotation of the context of the reference to "plain old semantic HTML".

posh-ja

2007-07-21T19:15:31Z

IwaiMasaharu: sync: english: 05:14, 29 Jun 2007

<h1>Plain Old Semantic HTML (POSH)</h1>

<abbr title="Plain Old Semantic HTML">POSH</abbr>のホームページ（日本語版）へようこそ。（[[posh|英語版]]）

__TOC__

== 起源 ==
'''POSH'''という用語は、[http://rbach.priv.at/Microformats-IRC/2007-04-06#T091456 2007年4月6日にmicroformatsのIRCチャネルにおいて]、<kwijibo>によって考案されました。POSHとは、[[plain-old-semantic-html]]の頭文字を取った略語です。John Allsopp、Tantek Çelik、Jeremy Keith、Chris Messinaらが[[events/2007-04-18-web-2-expo-dinner|2007年4月18日のWeb 2.0 Expo後に行われたMicroformats Dinner]]で交わした議論を通して、microformatsのよりどころでありそれが正しいサブセットともなっているPOSHの発想と、そのより幅広い目標を広めることの重要性があらためて注目されました。詳しくは[[posh#History|POSHの歴史]]を参照してください。

== 理由 ==
[[semantic-html|意味的（セマンティック）なHTML]]という用語はやや仰々しく、それがどれほどシンプルなものであり昨今のウェブデザイナーたちの間でいかに確固たる支持を受けているかということも、意味的なマークアップを用いてウェブを真っ当に作ることだけにとどまらない大きなメリットをもたらすということも、いずれもうまく伝えられていません。私たちは、そのコンセプトの本質をうまく表現でき、簡単に動詞にも応用できるような（たとえば「to posh」「poshify」「poshed up」などという使い方ができるような）、覚えやすい用語を必要としていたのです。

== POSHとは？ ==
POSHとは、Webページを作成する際に[[semantic-html|意味的なHTML]]を用いることのベストプラクティスを簡潔にあらわしたものです。意味的なHTMLとは、HTML 4.01（またはXHTML 1.0）にある要素と属性のなかで、''[[presentational|表現的]]''ではなく''[[semantic|意味的]]''なものから成るサブセットのこと。POSHを習い理解する最も良い方法は、実践することです。あなたのWebサイトからいちページを選び、[[posh-ja#POSH.E3.83.81.E3.82.A7.E3.83.83.E3.82.AF.E3.83.AA.E3.82.B9.E3.83.88|POSHチェックリスト]]を適用してください。[[posh-ja#POSH.E3.83.97.E3.83.AD.E3.82.BB.E3.82.B9|POSHプロセス]]に則り、そのまま続けてください。POSHについてより詳しく学ぶには、[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]をお読みください。

== POSHプロセス ==
あなたがPOSHであるために、そしてあなたのウェブサイトをPOSHなものにするためには、何ができるでしょうか？

# POSHなコンテンツを公開する。[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]に目を通し、あなたのウェブサイトでvalidな[[semantic-html|semantic (X)HTML]]を公開し、それに伴って[[semantic-class-names]]を使用するように心がけましょう。
# POSHを広める。このページへのリンクを貼って、他の人たちもPOSHになるように、そしてウェブサイトをPOSH対応させる（POSHify）ように勧めてみましょう。
# POSHを改善する。より多くの人が手軽にウェブサイトをPOSH対応させられるように、POSHリソースの収集をお手伝いください。

== POSHチェックリスト ==
* POSHの最初のルールとして、まずあなたのPOSHを必ず[http://validator.w3.org 検証]しましょう。
* 次に、単なる表現上の目的で使われているTABLEや、スペーサーGIF画像、いわゆる[[presentational-html|表現的なHTML]]を取り除きましょう。
* さらに、（BタグやBRタグの濫用を典型とする）[http://tantek.com/log/2002/10.html#L20021022t1432 その場しのぎ（'''B'''ed and '''BR'''eakfast）]のマークアップを修正しましょう。
* [http://tantek.com/log/2002/11.html#L20021128t1352 空っぽアンカー（Anorexic Anchors）]を取り除きましょう。
* よい[[semantic-class-names|意味的なクラス名]]を使いましょう。
* ...

== POSHリソース ==
=== POSHチュートリアル ===
Step by step tutorials to create POSH content or upgrade existing content to POSH.

* [http://westciv.com/style_master/house/tutorials/quick/validation/index.html Validating your css and html] A simple step by step guide to how and why you should validate your markup
* ...

=== POSH関連ブックマーク ===
* Ma.gnoliaの[http://ma.gnolia.com/groups/posh POSHグループ]をチェックしてみてください。
* See pages tagged both [http://del.icio.us/tag/posh+microformats POSH and microformats] on del.icio.us.

=== POSH関連プレゼンテーション ===
Presentations which explain and advocate concepts and techniques for utilizing semantic HTML. If/when this section gets too big, we can move it to [[posh-presentations]].
* [http://tantek.com/presentations/2003SXSW/stylesheets.html CSS: Between the Style Sheets by Tantek Çelik (2003-03)], specifically, see slides 3-4,6 starting with "Leaving the [http://tantek.com/log/2002/10.html#L20021022t1432 <B>ed & <BR>eakfast]", and slide 9 "CSS & the Semantic Spectrum" which provides an overview of the semantic spectrum of (X)HTML tags.
* [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics] (2004-02-11)
* [http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean] (2004-09-28)
* [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (2005-09-29, first version: [http://tantek.com/presentations/2005/03/elementsofxhtml/ 2005-03-13 at SXSW Interactive]).
* ...
* See also more microformats [[presentations]] in general.

=== POSH関連書籍 ===
Modern web design books which document good semantic HTML practices.
* <cite>[http://www.oreilly.com/catalog/wdnut3/ http://www.oreilly.com/catalog/covers/0596009879_thumb.gif] [http://www.oreilly.com/catalog/wdnut3/ Web Design in a Nutshell, <strong>Third Edition</strong>]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Jennifer</span> <span class="additional-name">Niederst</span> <span class="family-name">Robbins</span></span> See [http://jenville.com/ Jenville].</span>
* <cite>[http://microformatique.com/book/ Microformats empowering your markup for Web 2.0]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">John</span> <span class="family-name">Allsopp</span>.</span></span> Chapter 3 is a detailed and practical overview of the appropriate use of structural, valid and semantic HTML.
* <cite>[http://htmlmastery.com/ http://htmlmastery.com/images/hm-cover-sm.gif][http://htmlmastery.com/ Semantics, Standards and Styling]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Paul</span> <span class="family-name">Haine</span>.</span></span>

=== POSH関連雑誌 ===
Online (and off) magazines which frequently publish articles about semantic HTML. If/when this section gets too big, we can move it to [[posh-magazines]].

* [http://alistapart.com/ A List Apart: For People Making Websites] (see in particular [http://www.alistapart.com/topics/code/htmlxhtml/ HTML and XHTML Articles])
* [http://www.digital-web.com/ Digital Web Magazine]

=== POSH関連ブログ ===
Blogs that with some regularity post high quality discussions, insights, and in general have advanced the state of the art of POSH. If/when this section gets too big, we can move it to [[posh-blogs]].

* [http://dbaron.org/log/current David Baron's weblog]
* [http://zeldman.com/ Jeffrey Zeldman Presents]
* [http://meyerweb.com/ meyerweb.com - Eric Meyer]
* [http://microformatique.com/ Microformatique - John Allsopp]
* [http://simplebits.com/ SimpleBits - Dan Cederholm] (see in particular [http://simplebits.com/bits/simplequiz/ SimpleQuiz])
* [http://tantek.com/ Tantek Çelik]
* ...

=== POSH関連ブログ記事 ===
Blog posts that provide specific, modern, guidance, techniques and tips for using more and better semantic HTML. This list is ''incomplete''. We know there are lots more blog posts out there that fit the aforementioned description - please add them! If/when this section gets too big, we can move it to [[posh-blog-posts]].

* [http://www.plaintxt.org/wp-content/uploads/sandbox-v09_readme.html The Sandbox theme for WordPress readme.html] discusses what POSH is and how the theme helps users use it.
* [http://tantek.com/log/2002/10.html#L20021022t1432 Bed and BReakfast markup (B&BR)] (2002-10-22) - avoiding nonsemantic uses of <nowiki><b>old and <br>eak</nowiki> tags and using <nowiki><h3>adings and <p>aragraphs</nowiki> instead.
* [http://tantek.com/log/2002/11.html#L20021128t1352 <nowiki><A>norexic </A>nchors</nowiki>] (2002-11-28) - use the "id" attribute on existing elements instead of adding empty <code><nowiki><a name="foo"></a></nowiki></code> elements. Use [[rel-bookmark]] for post permalinks within the document.
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class] (2002-12-16) - introduction to proper use of the HTML 'class' attribute.
* [http://tantek.com/log/2002/12.html#L20021231t1850 Dive into Semantic MARKup] (2002-12-31)
* [http://tantek.com/log/2003/01.html#L20030104t1249 Comment markup, presentation and plumbing] (2003-01-04) - how to markup a list of comments, including example use of the rare "hreflang" attribute.
* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer] (2004-07-18)
* [http://tantek.com/log/2004/07.html#d20t2359 More about the 'class' attribute] (2004-07-20)
* [http://www.uie.com/articles/holzschlag_interview/ Web Standards in the Real World: An Interview with Molly Holzschlag] (2005-06-01)
* [http://westciv.typepad.com/dog_or_higher/2005/11/webpatterns_and.html Webpatterns and websemantics] (2005-11-18)
* [http://www.thefutureoftheweb.com/blog/2006/2/writing-semantic-html Writing Semantic HTML by Jesse Skinner] (2006-02-22)
* [http://www.thefutureoftheweb.com/blog/2007/1/who-will-read-your-semantic-html Who will read your Semantic HTML?] by Jesse Skinner (2007-01-04)
* [http://microformatique.com/?page_id=109 Semantics in HTML] by John Allsopp (2007-01-08 - 2007-03-12)
** [http://microformatique.com/?p=83 Part I - Traditional HTML Semantics] (2007-01-08)
** [http://microformatique.com/?p=97 Part II - standardizing vocabularies] (2007-02-20)
** [http://microformatique.com/?p=108 Part III - Towards a semantic web] (2007-03-12)
* [http://microformatique.com/?p=82 Built in HTML semantics] A list of the semantic elements and attributes of HTML by John Allsopp (2007-01-08)
* [http://tantek.com/log/2007/04.html#d20t0823 The Importance of Being POSH] by Tantek Çelik (2007-04-20)
* [http://factoryjoe.com/blog/2007/04/21/getting-back-to-posh-plain-ol-semantic-html/ Getting back to POSH (Plain ol’ Semantic HTML)] by Chris Messina (2007-04-21)
* [http://friedcellcollective.net/outbreak/2007/04/22/im-posh-are-you/ I’m POSH - are you?] (2007-04-23)
* [http://www.unintentionallyblank.co.uk/2007/04/24/plain-old-semantic-html/ The Internet’s Upper Class Or Why Your Site Should Be POSH] (2007-04-24)
* [http://nate.koechley.com/blog/2006/12/15/divitis_and_correct_div_usage/ On Appropriate Use of DIVs, or When Divitis Doesn’t Apply] by Nate Koechley, 2006-12-15
* [http://nate.koechley.com/blog/2006/12/22/note_on_structural_and_semantic_meaning/ Quick Comment: Choose Class/ID Names Based on Semantic and/or Structural Meaning] by Nate Koechley, 2006-12-22
* [http://leland.nu/think/2006/07/31/seeing-is-believing/ SEEing is believing] - using standards and efficient design, coding, maintenance, and marketing to produce a search-engine-efficient site by Richard Leland (2006-07-31)
* ...

See [http://technorati.com/search/%22semantic%20HTML%22 more blogs talking about "semantic HTML"] and [http://technorati.com/search/posh+semantic+HTML POSH].

===POSH関連ポッドキャスト===
* [http://www.netmag.co.uk/podcasts/07-05-03-net.mp3 A talk about POSH] in the .Net magazine podcast episode 8 (56 minutes; 26 Mb. Relevant section 30:10-42:40)

=== POSHにまつわる隠れた情報源 ===
The following sites have POSH related articles, tutorials etc. on them, but you have to dig for them from the home page. Help find the hidden POSH treasures in these sites and add ''direct'' links to POSH related articles, tutorials etc. to the specific sections above. You can leave the top level site links here until/unless you have dug thru the entire site and found all the treasures.
* [http://www.w3schools.com/ W3Schools Online Web Tutorials]
* [http://dev.opera.com/ Dev.Opera]

=== POSH Bling for your Blog ===
If you want to improve your existing blog, there are some pretty simple things you can do:

==== WordPress ====
* Use the [http://www.plaintxt.org/themes/sandbox/ Sandbox] or [http://getk2.com K2] themes that already support hAtom and hCard
* Add the [http://redmonk.net/archives/2007/04/18/wordpress-widget-hcard-about-box/ hCard About Widget] to your site

== POSHを広める ==
Now that you've poshified your website(s), what next? Well, help spread POSH to other websites!

* Promote POSH. Make a POSH button (perhaps using semantic HTML and CSS ;) linking to this page and put it on your site, in your blogroll, in your footer, etc. Maybe even come up with a nice POSH button graphic and share it with the microformats community with a liberal license (public domain, CC-by-3.0, MIT, etc.) Like these:
** [http://redmonk.net/archives/2007/04/25/the-new-question/ http://redmonk.net/wp-content/uploads/2007/04/are_you_posh.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
** [http://redmonk.net/archives/2007/04/26/chic/ http://redmonk.net/wp-content/uploads/2007/04/chic_fancy.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
* Tell a friend. Talk to web design friends about POSH and convince and help them to poshify both their personal websites, and the websites they build for others. Blog about your experience with poshification and what steps you went through to poshify your websites. Write a [[posh-testimonial]]!
* Come up with more ideas to help spread POSH. Here are a few.
** Hold a PoshPit - a one or half day marathon session mixing semantic HTML experts with folks who maintain/run web sites in general and see how many websites you can collectively upgrade to POSH during the course of the day.
** ...

== POSHを改善する ==
As you read the [[posh#Resources|POSH resources]] documented here, what other POSH resources did you find? Add them to this page.

With your experience with both poshifying your sites and helping others do so, what have you learned? What kind of [[posh-issues|issues]] did you run into? What questions were commonly asked? What do you feel like you need to more easily and quickly help more people poshify their content?

== 歴史 ==
A brief history of references to "POSH" in this context and "plain old semantic HTML".

=== plain old semantic HTML ===
The earliest references to <strong>"plain old semantic HTML"</strong> that have been found so far are:
* [http://groups.google.com/group/comp.infosystems.www.authoring.site-design/msg/2373e9043c08cba4 1998-05-01: Kirrily 'Skud' Robert on comp.infosystems.www.authoring.site-design] - "The site is implemented in HTML 4.0 Transitional with style sheets; this means that anyone with an older browser won't get presentational markup, just <strong>plain old semantic HTML</strong>. "
* [http://www.highrankings.com/advisor/tables-seo/ 2006-09-21 Drew's comment by on "Tables and SEO"]: "I’d say it’s well worth it for a variety of reasons to only use tables when you’re presenting tabular data, and use <strong>plain old semantic HTML</strong> to mark up your content in all other cases." (retrieved by [[User:Tantek|Tantek]] 08:20, 20 Apr 2007 (PDT))
If you can find earlier references, please ''add'' them and include a brief quotation of the context of the reference to "plain old semantic HTML".

how-to-play-ja

2007-07-21T19:06:27Z

IwaiMasaharu: sync: english: 07:05, 19 Jul 2007

初めての方は[[introduction-ja|Microformatsの手引き]]をご覧ください。

= How to Play =

協力する前にこれらのガイドラインを読んでください。また、この内容は遵守してください。

# ページを編集したり作成したりする前にアカウントを作成してください。( [http://en.wikipedia.org/wiki/Wikipedia:Username Wikipedia Username guidelines] も見てください)
# Read about microformats.org [http://microformats.org/wiki/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.
# はじめに[http://microformats.org/discuss IRCチャンネル(こちらがお勧め)かメーリングリスト]に参加してみてください。(その前には[[mailing-lists]]を読んで下さい)
# もし、何か意見を書いたならば、あなたのユーザ名も一緒に書いてください。- you can easily do so with a datetimestamp in MediaWiki with four ~s, e.g.: <nowiki>~~~~</nowiki>.
# このWikiには、microformatsに直接関係あるページだけを作成してください。無関係なページは削除されます。
# ページの[[naming-conventions-ja|命名規則]]に従ってください。
# Wikiのページで会話をしてはいけません。その用途には#3で挙げた[http://microformats.org/discuss mailing lists]を使ってください。
# 妥当なXHTMLで記述するようにしてください。
# ソースコードを貼りつける場合、適当な長さで改行を入れてください。
# 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.
# 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 DO NOT 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. You may change a heading if you are careful to leave an empty <code><nowiki><span id="oldheadingID"></span></nowiki></code> in front of the 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.

== 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.

== 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]].

posh-ja

2007-07-21T18:44:18Z

IwaiMasaharu: /* POSHとは？ */ リンク先の間違いを修正

<h1>Plain Old Semantic HTML (POSH)</h1>

<abbr title="Plain Old Semantic HTML">POSH</abbr>のホームページ（日本語版）へようこそ。（[[posh|英語版]]）

__TOC__

== 起源 ==
'''POSH'''という用語は、[http://rbach.priv.at/Microformats-IRC/2007-04-06#T091456 2007年4月6日にmicroformatsのIRCチャネルにおいて]、<kwijibo>によって考案されました。POSHとは、[[plain-old-semantic-html]]の頭文字を取った略語です。John Allsopp、Tantek Çelik、Jeremy Keith、Chris Messinaらが[[events/2007-04-18-web-2-expo-dinner|2007年4月18日のWeb 2.0 Expo後に行われたMicroformats Dinner]]で交わした議論を通して、microformatsのよりどころでありそれが正しいサブセットともなっているPOSHの発想と、そのより幅広い目標を広めることの重要性があらためて注目されました。詳しくは[[posh#History|POSHの歴史]]を参照してください。

== 理由 ==
[[semantic-html|意味的（セマンティック）なHTML]]という用語はやや仰々しく、それがどれほどシンプルなものであり昨今のウェブデザイナーたちの間でいかに確固たる支持を受けているかということも、意味的なマークアップを用いてウェブを真っ当に作ることだけにとどまらない大きなメリットをもたらすということも、いずれもうまく伝えられていません。私たちは、そのコンセプトの本質をうまく表現でき、簡単に動詞にも応用できるような（たとえば「to posh」「poshify」「poshed up」などという使い方ができるような）、覚えやすい用語を必要としていたのです。

== POSHとは？ ==
POSHとは、Webページを作成する際に[[semantic-html|意味的なHTML]]を用いることのベストプラクティスを簡潔にあらわしたものです。意味的なHTMLとは、HTML 4.01（またはXHTML 1.0）にある要素と属性のなかで、''[[presentational|表現的]]''ではなく''[[semantic|意味的]]''なものから成るサブセットのこと。POSHを習い理解する最も良い方法は、実践することです。あなたのWebサイトからいちページを選び、[[posh-ja#POSH.E3.83.81.E3.82.A7.E3.83.83.E3.82.AF.E3.83.AA.E3.82.B9.E3.83.88|POSHチェックリスト]]を適用してください。[[posh-ja#POSH.E3.83.97.E3.83.AD.E3.82.BB.E3.82.B9|POSHプロセス]]に則り、そのまま続けてください。POSHについてより詳しく学ぶには、[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]をお読みください。

== POSHプロセス ==
あなたがPOSHであるために、そしてあなたのウェブサイトをPOSHなものにするためには、何ができるでしょうか？

# POSHなコンテンツを公開する。[[posh-ja#POSH.E3.83.AA.E3.82.BD.E3.83.BC.E3.82.B9|POSHリソース]]に目を通し、あなたのウェブサイトでvalidな[[semantic-html|semantic (X)HTML]]を公開し、それに伴って[[semantic-class-names]]を使用するように心がけましょう。
# POSHを広める。このページへのリンクを貼って、他の人たちもPOSHになるように、そしてウェブサイトをPOSH対応させる（POSHify）ように勧めてみましょう。
# POSHを改善する。より多くの人が手軽にウェブサイトをPOSH対応させられるように、POSHリソースの収集をお手伝いください。

== POSHチェックリスト ==
* POSHの最初のルールとして、まずあなたのPOSHを必ず[http://validator.w3.org 検証]しましょう。
* 次に、単なる表現上の目的で使われているTABLEや、スペーサーGIF画像、いわゆる[[presentational-html|表現的なHTML]]を取り除きましょう。
* さらに、（BタグやBRタグの濫用を典型とする）[http://tantek.com/log/2002/10.html#L20021022t1432 その場しのぎ（Bed and BReakfast）]のマークアップを修正しましょう。
* [http://tantek.com/log/2002/11.html#L20021128t1352 空っぽアンカー（Anorexic Anchors）]を取り除きましょう。
* よい[[semantic-class-names|意味的なクラス名]]を使いましょう。
* ...

== POSHリソース ==
=== POSHチュートリアル ===
Step by step tutorials to create POSH content or upgrade existing content to POSH.

* [http://westciv.com/style_master/house/tutorials/quick/validation/index.html Validating your css and html] A simple step by step guide to how and why you should validate your markup
* ...

=== POSH関連ブックマーク ===
* Ma.gnoliaの[http://ma.gnolia.com/groups/posh POSHグループ]をチェックしてみてください。

=== POSH関連プレゼンテーション ===
Presentations which explain and advocate concepts and techniques for utilizing semantic HTML. If/when this section gets too big, we can move it to [[posh-presentations]].
* [http://tantek.com/presentations/2003SXSW/stylesheets.html CSS: Between the Style Sheets by Tantek Çelik (2003-03)], specifically, see slides 3-4,6 starting with "Leaving the [http://tantek.com/log/2002/10.html#L20021022t1432 <B>ed & <BR>eakfast]", and slide 9 "CSS & the Semantic Spectrum" which provides an overview of the semantic spectrum of (X)HTML tags.
* [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics] (2004-02-11)
* [http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean] (2004-09-28)
* [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (2005-09-29, first version: [http://tantek.com/presentations/2005/03/elementsofxhtml/ 2005-03-13 at SXSW Interactive]).
* ...
* See also more microformats [[presentations]] in general.

=== POSH関連書籍 ===
Modern web design books which document good semantic HTML practices.
* <cite>[http://www.oreilly.com/catalog/wdnut3/ http://www.oreilly.com/catalog/covers/0596009879_thumb.gif] [http://www.oreilly.com/catalog/wdnut3/ Web Design in a Nutshell, <strong>Third Edition</strong>]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Jennifer</span> <span class="additional-name">Niederst</span> <span class="family-name">Robbins</span></span> See [http://jenville.com/ Jenville].</span>
* <cite>[http://microformatique.com/book/ Microformats empowering your markup for Web 2.0]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">John</span> <span class="family-name">Allsopp</span>.</span></span> Chapter 3 is a detailed and practical overview of the appropriate use of structural, valid and semantic HTML.
* <cite>[http://htmlmastery.com/ http://htmlmastery.com/images/hm-cover-sm.gif][http://htmlmastery.com/ Semantics, Standards and Styling]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Paul</span> <span class="family-name">Haine</span>.</span></span>

=== POSH関連雑誌 ===
Online (and off) magazines which frequently publish articles about semantic HTML. If/when this section gets too big, we can move it to [[posh-magazines]].

* [http://alistapart.com/ A List Apart: For People Making Websites] (see in particular [http://www.alistapart.com/topics/code/htmlxhtml/ HTML and XHTML Articles])
* [http://www.digital-web.com/ Digital Web Magazine]

=== POSH関連ブログ ===
Blogs that with some regularity post high quality discussions, insights, and in general have advanced the state of the art of POSH. If/when this section gets too big, we can move it to [[posh-blogs]].

* [http://dbaron.org/log/current David Baron's weblog]
* [http://zeldman.com/ Jeffrey Zeldman Presents]
* [http://meyerweb.com/ meyerweb.com - Eric Meyer]
* [http://microformatique.com/ Microformatique - John Allsopp]
* [http://simplebits.com/ SimpleBits - Dan Cederholm] (see in particular [http://simplebits.com/bits/simplequiz/ SimpleQuiz])
* [http://tantek.com/ Tantek Çelik]
* ...

=== POSH関連ブログ記事 ===
Blog posts that provide specific, modern, guidance, techniques and tips for using more and better semantic HTML. This list is ''incomplete''. We know there are lots more blog posts out there that fit the aforementioned description - please add them! If/when this section gets too big, we can move it to [[posh-blog-posts]].

* [http://tantek.com/log/2002/10.html#L20021022t1432 Bed and BReakfast markup (B&BR)] (2002-10-22) - avoiding nonsemantic uses of <nowiki><b>old and <br>eak</nowiki> tags and using <nowiki><h3>adings and <p>aragraphs</nowiki> instead.
* [http://tantek.com/log/2002/11.html#L20021128t1352 <nowiki><A>norexic </A>nchors</nowiki>] (2002-11-28) - use the "id" attribute on existing elements instead of adding empty <code><nowiki><a name="foo"></a></nowiki></code> elements. Use [[rel-bookmark]] for post permalinks within the document.
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class] (2002-12-16) - introduction to proper use of the HTML 'class' attribute.
* [http://tantek.com/log/2002/12.html#L20021231t1850 Dive into Semantic MARKup] (2002-12-31)
* [http://tantek.com/log/2003/01.html#L20030104t1249 Comment markup, presentation and plumbing] (2003-01-04) - how to markup a list of comments, including example use of the rare "hreflang" attribute.
* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer] (2004-07-18)
* [http://tantek.com/log/2004/07.html#d20t2359 More about the 'class' attribute] (2004-07-20)
* [http://www.uie.com/articles/holzschlag_interview/ Web Standards in the Real World: An Interview with Molly Holzschlag] (2005-06-01)
* [http://westciv.typepad.com/dog_or_higher/2005/11/webpatterns_and.html Webpatterns and websemantics] (2005-11-18)
* [http://www.thefutureoftheweb.com/blog/2006/2/writing-semantic-html Writing Semantic HTML by Jesse Skinner] (2006-02-22)
* [http://www.thefutureoftheweb.com/blog/2007/1/who-will-read-your-semantic-html Who will read your Semantic HTML?] by Jesse Skinner (2007-01-04)
* [http://microformatique.com/?page_id=109 Semantics in HTML] by John Allsopp (2007-01-08 - 2007-03-12)
** [http://microformatique.com/?p=83 Part I - Traditional HTML Semantics] (2007-01-08)
** [http://microformatique.com/?p=97 Part II - standardizing vocabularies] (2007-02-20)
** [http://microformatique.com/?p=108 Part III - Towards a semantic web] (2007-03-12)
* [http://microformatique.com/?p=82 Built in HTML semantics] A list of the semantic elements and attributes of HTML by John Allsopp (2007-01-08)
* [http://tantek.com/log/2007/04.html#d20t0823 The Importance of Being POSH] by Tantek Çelik (2007-04-20)
* [http://factoryjoe.com/blog/2007/04/21/getting-back-to-posh-plain-ol-semantic-html/ Getting back to POSH (Plain ol’ Semantic HTML)] by Chris Messina (2007-04-21)
* [http://friedcellcollective.net/outbreak/2007/04/22/im-posh-are-you/ I’m POSH - are you?] (2007-04-23)
* [http://www.unintentionallyblank.co.uk/2007/04/24/plain-old-semantic-html/ The Internet’s Upper Class Or Why Your Site Should Be POSH] (2007-04-24)
* [http://nate.koechley.com/blog/2006/12/15/divitis_and_correct_div_usage/ On Appropriate Use of DIVs, or When Divitis Doesn’t Apply] by Nate Koechley, 2006-12-15
* [http://nate.koechley.com/blog/2006/12/22/note_on_structural_and_semantic_meaning/ Quick Comment: Choose Class/ID Names Based on Semantic and/or Structural Meaning] by Nate Koechley, 2006-12-22
* ...

See [http://technorati.com/search/%22semantic%20HTML%22 more blogs talking about "semantic HTML"] and [http://technorati.com/search/posh+semantic+HTML POSH].

===POSH関連ポッドキャスト===
* [http://www.netmag.co.uk/podcasts/07-05-03-net.mp3 A talk about POSH] in the .Net magazine podcast episode 8 (56 minutes; 26 Mb. Relevant section 30:10-42:40)

=== POSHにまつわる隠れた情報源 ===
The following sites have POSH related articles, tutorials etc. on them, but you have to dig for them from the home page. Help find the hidden POSH treasures in these sites and add ''direct'' links to POSH related articles, tutorials etc. to the specific sections above. You can leave the top level site links here until/unless you have dug thru the entire site and found all the treasures.
* [http://www.w3schools.com/ W3Schools Online Web Tutorials]
* [http://dev.opera.com/ Dev.Opera]

=== POSH Bling for your Blog ===
If you want to improve your existing blog, there are some pretty simple things you can do:

==== WordPress ====
* Use the [http://www.plaintxt.org/themes/sandbox/ Sandbox] or [http://getk2.com K2] themes that already support hAtom and hCard
* Add the [http://redmonk.net/archives/2007/04/18/wordpress-widget-hcard-about-box/ hCard About Widget] to your site

== POSHを広める ==
Now that you've poshified your website(s), what next? Well, help spread POSH to other websites!

* Promote POSH. Make a POSH button (perhaps using semantic HTML and CSS ;) linking to this page and put it on your site, in your blogroll, in your footer, etc. Maybe even come up with a nice POSH button graphic and share it with the microformats community with a liberal license (public domain, CC-by-3.0, MIT, etc.) Like these:
** [http://redmonk.net/archives/2007/04/25/the-new-question/ http://redmonk.net/wp-content/uploads/2007/04/are_you_posh.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
** [http://redmonk.net/archives/2007/04/26/chic/ http://redmonk.net/wp-content/uploads/2007/04/chic_fancy.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
* Tell a friend. Talk to web design friends about POSH and convince and help them to poshify both their personal websites, and the websites they build for others. Blog about your experience with poshification and what steps you went through to poshify your websites. Write a [[posh-testimonial]]!
* Come up with more ideas to help spread POSH. Here are a few.
** Hold a PoshPit - a one or half day marathon session mixing semantic HTML experts with folks who maintain/run web sites in general and see how many websites you can collectively upgrade to POSH during the course of the day.
** ...

== POSHを改善する ==
As you read the [[posh#Resources|POSH resources]] documented here, what other POSH resources did you find? Add them to this page.

With your experience with both poshifying your sites and helping others do so, what have you learned? What kind of [[posh-issues|issues]] did you run into? What questions were commonly asked? What do you feel like you need to more easily and quickly help more people poshify their content?

== 歴史 ==
A brief history of references to "POSH" in this context and "plain old semantic HTML".

=== plain old semantic HTML ===
The earliest references to <strong>"plain old semantic HTML"</strong> that have been found so far are:
* [http://groups.google.com/group/comp.infosystems.www.authoring.site-design/msg/2373e9043c08cba4 1998-05-01: Kirrily 'Skud' Robert on comp.infosystems.www.authoring.site-design] - "The site is implemented in HTML 4.0 Transitional with style sheets; this means that anyone with an older browser won't get presentational markup, just <strong>plain old semantic HTML</strong>. "
* [http://www.highrankings.com/advisor/tables-seo/ 2006-09-21 Drew's comment by on "Tables and SEO"]: "I’d say it’s well worth it for a variety of reasons to only use tables when you’re presenting tabular data, and use <strong>plain old semantic HTML</strong> to mark up your content in all other cases." (retrieved by [[User:Tantek|Tantek]] 08:20, 20 Apr 2007 (PDT))
If you can find earlier references, please ''add'' them and include a brief quotation of the context of the reference to "plain old semantic HTML".

Main Page-ja

2007-07-21T00:53:28Z

IwaiMasaharu: /* 他言語でのmicroformats wiki */ リンク先変更

Microformats Wikiにようこそ！

[[introduction-ja|microformatsの手引き]]からどうぞ。編集を始めるまえには[[how-to-play-ja]]を読んでください。

__TOC__

== はじめに ==

* First, read up on what it means to be [http://microformats.org/wiki/posh <abbr title="Plain Old Semantic HTML">POSH</abbr>] {{NewMarker}}.
* See the [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations-ja|プレゼンテーション]], [[books]], [[podcasts|ポッドキャスト]], and [[screencasts|スクリーンキャスト]].
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary|用語集]] for new terms.
* 識者からもっと教わりたいことがあれば、[[events|microformatsのイベント]]をどうぞ。

== 定義 ==

[http://microformats.org/discuss/ メーリングリスト]([[mailing-lists]])での一般的な定義は、「分散的開発を実現するために用いられる、セマンティクスをHTMLに埋め込む為のシンプルな仕様」です。もう少し細かく説明すると、microformatsは下記のように定義できます。
:分散的開発を実現するために用いられる
::Webにあるリソースそのものや、それを利用するツールやサービスを分散的に処理できるようにします。
:セマンティクスをHTMLに埋め込むための
::それぞれの分野に特化することで、各仕様が小さいものとなります。
:シンプルな仕様
:人間が解読できる(X)HTML/XMLドキュメントやAtom/RSSフィード、そしてプレーンなXMLでの提供
::現存するコンテンツの利用パターンを標準化することからはじめています。
::概略的で説明的なclass名を使い、ソースをみてもわかりやすくなっています。
::現存の相互運用できる規格に基づくことにより、汎用性が高まります。

「ブラウザーでWeb巡回しかしないんだ。それはまた20世紀的だね。」 -- [http://diveintomark.org Mark Pilgrim]

See more explanations of [[what-are-microformats|what are microformats]], and [[what-can-you-do-with-microformats|what you can do with them]].

== 協力の方法 ==

microformatsをより発展させるためには次のことができます。

* [[advocacy|Advocate]] the use of microformats.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
*[http://microformats.org/discuss mailing lists] と [[irc|IRC Channel]] に参加しマイクロフォーマットに関して質問したり学んだりすることができます。
*[[Main_Page-ja#.E4.BB.96.E8.A8.80.E8.AA.9E.E3.81.A7.E3.81.AEmicroformats_wiki|他言語でのmicroformats wiki]]を見てください。そして、世界中の人が利用しやすくするためにmicroformats wikiの翻訳を手伝ってください。
* Find [[orphans|orphaned]] pages, and add links to them.
* Before proposing any new microformats, make sure your website is [[POSH]] and uses existing microformats, and then read the [[process]].

== 仕様 ==

以下はオープンスタンダードとなった[[microformats-ja|microformats]]の仕様です。([[implementations|実装]]や[[examples-in-the-wild|実世界での例]]もご覧ください)

* [[hcalendar-ja|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator](翻訳中！)
* [[hcard-ja|hCard]] - [http://microformats.org/code/hcard/creator hcard creator](翻訳中！)
* [[rel-license-ja|rel-license]](翻訳完了)
* [[rel-nofollow-ja|rel-nofollow]](翻訳完了)
* [[rel-tag-ja|rel-tag]](翻訳完了)
* [[vote-links-ja|Vote Links]](翻訳完了)
* [http://gmpg.org/xfn/ XFN] ([[xfn-implementations|XFNの実装]]もご覧下さい)
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo-ja|XOXO]](翻訳中！)

== ドラフト ==

* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]]
* [[hresume|hResume]]
* [[hreview-ja|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== デザインパターン ==

{{design_patterns-ja}} 

== Exploratory Discussions ==
Per the microformats [[process]]:
実世界での[[examples|例]]の調査や分析、既に存在するフォーマット、またmicroformatsにできそうなもののブレインストーミングをまとめています。もし何かページを追加した場合、まず[[rejected-formats]]を見てから行ってください。
* alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]
*[[attention]]
* audio-info ([[audio-info-examples|examples]], [[audio-info-formats|formats]], [[audio-info-brainstorming|brainstorming]], [[audio-info-proposal|proposal]]) - Marking up information and metadata related to audio (speech, music, and sound in general). {{NewMarker}}
* blog description [[blog-description-examples|blog description examples]]
* blog info [[blog-info-examples|blog info examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]
* code [[code-examples| code examples]], [[code-brainstorming|code brainstorming]] {{NewMarker}}
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[collection-description|collection description]] - for describing collections in libraries {{NewMarker}}
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]
* [[depend-examples]]: examples of dependency graphs, especially as they relate to software {{NewMarker}}
* [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) {{NewMarker}}
* directions [[directions-examples|directions examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]
* error messages [[error-message-examples|error message examples]], [[error-message-brainstorming|error message brainstorming]]
* forms [[forms-examples|forms examples]]
* file-format ([[file-format-examples|examples]], formats, brainstorming) - for the mark-up of file format information (size, type, codecs, bitrate, etc.) {{NewMarker}}
* genealogy [[genealogy-formats|genealogy exploration]]
* geo extensions
** [[geo-extension-strawman]] - extend geo for moons, other planets, etc.
** [[geo-elevation-examples]] - extend geo for representing altitude {{NewMarker}}
** [[geo-waypoint-examples]] - extend geo for representing routes and boundaries, using waypoints {{NewMarker}}
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]
* hash [[hash-examples|hash examples]]
* grouping ([[grouping-examples|examples]], [[grouping-formats|formats]], [[grouping-brainstorming|brainstorming]], [[grouping-proposal|proposal]]) - Metadata markup of items that should be grouped together. {{NewMarker}}
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]]
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]]
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]
* [[htodo|hToDo]]
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) {{UpdateMarker}}
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]
* [[mfo-examples|MFO examples]]
* music [[music-examples|music examples]] {{UpdateMarker}}
* news [[news-examples|news examples]] {{NewMarker}}
* photo note [[photo-note-examples|photo note examples]]
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}
* receipt ([[receipt-examples|examples]], [[receipt-formats|formats]], [[receipt-brainstorming|brainstorming]], [[receipt-proposal|proposal]]) - Marking up information and metadata related to purchase receipts. {{NewMarker}}
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|search results example]]
* show [[show-brainstorming|show brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|tagspeak examples]]
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].
* transit table [[transit-table-examples|transit table examples]]
* [[uid]]
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]
* [[wiki-formats|wiki formats]]
* 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]]
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])
*[[realestate-propertydetail|realestate-propertydetail brainstorming]]

== 例 ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== ツール、テストケース、リサーチ ==

事例やコードやテストケースを見るために最初に見るべき場所はmicroformatを使ったそれぞれのページです. 二つ以上のmicroformatを使うツールやサービスは少ししかありません. このセクションは複数のmicroformatに関連するエディター、パーサー、妥当性検証ソフト、テストケース、その他情報等のためのものです。

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[internationalization]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]
*[[why-are-content-standards-hard]]
*[[profile-examples-in-wild|Profile examples, in the wild]]

== リソース ==

* [[events]]
* [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.
* [[spread-microformats]]
* [[buttons]]
* [[icons-ja]]
* [[demo|デモ]] - microformatを試すデモへのリンク集
* [[semacode|Semacode]]
* [[jobs]]
* [[user-interface]]
* [[marked-for-deletion]]
* [[microformats-issues]] {{NewMarker}} - 一つ以上のmicroformatに関するissue
* [[spellcheck|spell-check dictionary]]

== 共用ワークスペース ==
* [[to-do]]
* [[microformats-issues]] - issues related to more than one microformat.
* [[external-issues]]

== 他言語でのmicroformats wiki ==

microformatsの記事を色々な言語で読んだり編集したりできます。

* 100以上の記事のある言語
** [[Main_Page|English (本家の英語)]]
** [[Main_Page-fr|Francais (フランス語)]] {{UpdateMarker-fr}}
* 10以上の記事のある言語
** [[Main_Page-pt-br| Português (ブラジル系ポルトガル語)]]
** [[Main_Page-ja|日本語]]
* 2以上の記事のある言語
** [[Main_Page-es|Espanol (スペイン語)]]
** [[Main_Page-de|Deutsch (ドイツ語)]]
** [[Main_Page-ro|Romanian]]
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.
See also [[other-languages]], and [[how-to-start-new-translation-ja|how-to-start-a-new-translation]].

how-to-start-new-translation-ja

2007-07-21T00:50:51Z

IwaiMasaharu: /* Read Wikipedia Tips */ Main_Page-jaからの転記

<h1>How to start a microformats wiki in another language</h1>

== Intro ==
Start a microformats wiki in another language.

Don't see the language you want among [[other-languages]]? Help translate this microformats wiki into another language!

We're still figuring this out.

== Wikipedia Tipsを読みましょう ==
翻訳に際し、まずは[http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipediaにおける多言語版の位置づけ]、そして[http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia 新しいWikipediaを始めるには] をご覧下さい。
一般的なTIPSやアドバイス、このコミュニティの慣習が書いてあります。

== Pages To Start With ==
実際に翻訳を始めるときは、まず、比較的静的であまり変化がないものを集めた[[stable-pages-ja|静的ページ]]に挙がっているものを少しずつ翻訳していくことから始めましょう。そして、(ページの変更を監視できる)[[Special:Watchlist|ウォッチリスト]]機能を使って英語版と歩調を合わせるとよいでしょう。

== ページ名の規約 ==
翻訳したページの名前: 翻訳したページのページ名は、英語版のページ名の末尾にハイフンに続いてRFC 3066の言語コード付けてください。例えば日本語版では、[[Main_Page]]は[[Main_Page-ja]]に、そして [[how-to-play]]は[[how-to-play-ja]]になります。

== more languages folks want to see ==

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])
* Does somebody want to see a Dutch translation???

==See also==
*[[internationalization]]

Back to the [[Main_Page|main page]].

how-to-start-new-translation-ja

2007-07-21T00:47:37Z

IwaiMasaharu: /* Pages To Start With */ Main_Page-jaからの転記

<h1>How to start a microformats wiki in another language</h1>

== Intro ==
Start a microformats wiki in another language.

Don't see the language you want among [[other-languages]]? Help translate this microformats wiki into another language!

We're still figuring this out.

== Read Wikipedia Tips ==
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

== Pages To Start With ==
実際に翻訳を始めるときは、まず、比較的静的であまり変化がないものを集めた[[stable-pages-ja|静的ページ]]に挙がっているものを少しずつ翻訳していくことから始めましょう。そして、(ページの変更を監視できる)[[Special:Watchlist|ウォッチリスト]]機能を使って英語版と歩調を合わせるとよいでしょう。

== ページ名の規約 ==
翻訳したページの名前: 翻訳したページのページ名は、英語版のページ名の末尾にハイフンに続いてRFC 3066の言語コード付けてください。例えば日本語版では、[[Main_Page]]は[[Main_Page-ja]]に、そして [[how-to-play]]は[[how-to-play-ja]]になります。

== more languages folks want to see ==

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])
* Does somebody want to see a Dutch translation???

==See also==
*[[internationalization]]

Back to the [[Main_Page|main page]].

how-to-start-new-translation-ja

2007-07-21T00:46:00Z

IwaiMasaharu: /* Page naming convention */ Main_Page-jaからの転記

<h1>How to start a microformats wiki in another language</h1>

== Intro ==
Start a microformats wiki in another language.

Don't see the language you want among [[other-languages]]? Help translate this microformats wiki into another language!

We're still figuring this out.

== Read Wikipedia Tips ==
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

== Pages To Start With ==
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

== ページ名の規約 ==
翻訳したページの名前: 翻訳したページのページ名は、英語版のページ名の末尾にハイフンに続いてRFC 3066の言語コード付けてください。例えば日本語版では、[[Main_Page]]は[[Main_Page-ja]]に、そして [[how-to-play]]は[[how-to-play-ja]]になります。

== more languages folks want to see ==

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])
* Does somebody want to see a Dutch translation???

==See also==
*[[internationalization]]

Back to the [[Main_Page|main page]].

how-to-start-new-translation-ja

2007-07-21T00:43:14Z

IwaiMasaharu: english: 09:18, 27 Mar 2007

<h1>How to start a microformats wiki in another language</h1>

== Intro ==
Start a microformats wiki in another language.

Don't see the language you want among [[other-languages]]? Help translate this microformats wiki into another language!

We're still figuring this out.

== Read Wikipedia Tips ==
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

== Pages To Start With ==
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

== Page naming convention ==
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

== more languages folks want to see ==

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])
* Does somebody want to see a Dutch translation???

==See also==
*[[internationalization]]

Back to the [[Main_Page|main page]].

Main Page-ja

2007-07-21T00:40:05Z

IwaiMasaharu: sync: english: 16:37, 18 Jul 2007

Microformats Wikiにようこそ！

[[introduction-ja|microformatsの手引き]]からどうぞ。編集を始めるまえには[[how-to-play-ja]]を読んでください。

__TOC__

== はじめに ==

* First, read up on what it means to be [http://microformats.org/wiki/posh <abbr title="Plain Old Semantic HTML">POSH</abbr>] {{NewMarker}}.
* See the [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations-ja|プレゼンテーション]], [[books]], [[podcasts|ポッドキャスト]], and [[screencasts|スクリーンキャスト]].
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary|用語集]] for new terms.
* 識者からもっと教わりたいことがあれば、[[events|microformatsのイベント]]をどうぞ。

== 定義 ==

[http://microformats.org/discuss/ メーリングリスト]([[mailing-lists]])での一般的な定義は、「分散的開発を実現するために用いられる、セマンティクスをHTMLに埋め込む為のシンプルな仕様」です。もう少し細かく説明すると、microformatsは下記のように定義できます。
:分散的開発を実現するために用いられる
::Webにあるリソースそのものや、それを利用するツールやサービスを分散的に処理できるようにします。
:セマンティクスをHTMLに埋め込むための
::それぞれの分野に特化することで、各仕様が小さいものとなります。
:シンプルな仕様
:人間が解読できる(X)HTML/XMLドキュメントやAtom/RSSフィード、そしてプレーンなXMLでの提供
::現存するコンテンツの利用パターンを標準化することからはじめています。
::概略的で説明的なclass名を使い、ソースをみてもわかりやすくなっています。
::現存の相互運用できる規格に基づくことにより、汎用性が高まります。

「ブラウザーでWeb巡回しかしないんだ。それはまた20世紀的だね。」 -- [http://diveintomark.org Mark Pilgrim]

See more explanations of [[what-are-microformats|what are microformats]], and [[what-can-you-do-with-microformats|what you can do with them]].

== 協力の方法 ==

microformatsをより発展させるためには次のことができます。

* [[advocacy|Advocate]] the use of microformats.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
*[http://microformats.org/discuss mailing lists] と [[irc|IRC Channel]] に参加しマイクロフォーマットに関して質問したり学んだりすることができます。
*[[Main_Page-ja#.E4.BB.96.E8.A8.80.E8.AA.9E.E3.81.A7.E3.81.AEmicroformats_wiki|他言語でのmicroformats wiki]]を見てください。そして、世界中の人が利用しやすくするためにmicroformats wikiの翻訳を手伝ってください。
* Find [[orphans|orphaned]] pages, and add links to them.
* Before proposing any new microformats, make sure your website is [[POSH]] and uses existing microformats, and then read the [[process]].

== 仕様 ==

以下はオープンスタンダードとなった[[microformats-ja|microformats]]の仕様です。([[implementations|実装]]や[[examples-in-the-wild|実世界での例]]もご覧ください)

* [[hcalendar-ja|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator](翻訳中！)
* [[hcard-ja|hCard]] - [http://microformats.org/code/hcard/creator hcard creator](翻訳中！)
* [[rel-license-ja|rel-license]](翻訳完了)
* [[rel-nofollow-ja|rel-nofollow]](翻訳完了)
* [[rel-tag-ja|rel-tag]](翻訳完了)
* [[vote-links-ja|Vote Links]](翻訳完了)
* [http://gmpg.org/xfn/ XFN] ([[xfn-implementations|XFNの実装]]もご覧下さい)
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo-ja|XOXO]](翻訳中！)

== ドラフト ==

* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]]
* [[hresume|hResume]]
* [[hreview-ja|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== デザインパターン ==

{{design_patterns-ja}} 

== Exploratory Discussions ==
Per the microformats [[process]]:
実世界での[[examples|例]]の調査や分析、既に存在するフォーマット、またmicroformatsにできそうなもののブレインストーミングをまとめています。もし何かページを追加した場合、まず[[rejected-formats]]を見てから行ってください。
* alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]
*[[attention]]
* audio-info ([[audio-info-examples|examples]], [[audio-info-formats|formats]], [[audio-info-brainstorming|brainstorming]], [[audio-info-proposal|proposal]]) - Marking up information and metadata related to audio (speech, music, and sound in general). {{NewMarker}}
* blog description [[blog-description-examples|blog description examples]]
* blog info [[blog-info-examples|blog info examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]
* code [[code-examples| code examples]], [[code-brainstorming|code brainstorming]] {{NewMarker}}
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[collection-description|collection description]] - for describing collections in libraries {{NewMarker}}
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]
* [[depend-examples]]: examples of dependency graphs, especially as they relate to software {{NewMarker}}
* [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) {{NewMarker}}
* directions [[directions-examples|directions examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]
* error messages [[error-message-examples|error message examples]], [[error-message-brainstorming|error message brainstorming]]
* forms [[forms-examples|forms examples]]
* file-format ([[file-format-examples|examples]], formats, brainstorming) - for the mark-up of file format information (size, type, codecs, bitrate, etc.) {{NewMarker}}
* genealogy [[genealogy-formats|genealogy exploration]]
* geo extensions
** [[geo-extension-strawman]] - extend geo for moons, other planets, etc.
** [[geo-elevation-examples]] - extend geo for representing altitude {{NewMarker}}
** [[geo-waypoint-examples]] - extend geo for representing routes and boundaries, using waypoints {{NewMarker}}
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]
* hash [[hash-examples|hash examples]]
* grouping ([[grouping-examples|examples]], [[grouping-formats|formats]], [[grouping-brainstorming|brainstorming]], [[grouping-proposal|proposal]]) - Metadata markup of items that should be grouped together. {{NewMarker}}
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]]
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]]
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]
* [[htodo|hToDo]]
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) {{UpdateMarker}}
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]
* [[mfo-examples|MFO examples]]
* music [[music-examples|music examples]] {{UpdateMarker}}
* news [[news-examples|news examples]] {{NewMarker}}
* photo note [[photo-note-examples|photo note examples]]
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}
* receipt ([[receipt-examples|examples]], [[receipt-formats|formats]], [[receipt-brainstorming|brainstorming]], [[receipt-proposal|proposal]]) - Marking up information and metadata related to purchase receipts. {{NewMarker}}
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|search results example]]
* show [[show-brainstorming|show brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|tagspeak examples]]
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].
* transit table [[transit-table-examples|transit table examples]]
* [[uid]]
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]
* [[wiki-formats|wiki formats]]
* 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]]
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])
*[[realestate-propertydetail|realestate-propertydetail brainstorming]]

== 例 ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== ツール、テストケース、リサーチ ==

事例やコードやテストケースを見るために最初に見るべき場所はmicroformatを使ったそれぞれのページです. 二つ以上のmicroformatを使うツールやサービスは少ししかありません. このセクションは複数のmicroformatに関連するエディター、パーサー、妥当性検証ソフト、テストケース、その他情報等のためのものです。

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[internationalization]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]
*[[why-are-content-standards-hard]]
*[[profile-examples-in-wild|Profile examples, in the wild]]

== リソース ==

* [[events]]
* [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.
* [[spread-microformats]]
* [[buttons]]
* [[icons-ja]]
* [[demo|デモ]] - microformatを試すデモへのリンク集
* [[semacode|Semacode]]
* [[jobs]]
* [[user-interface]]
* [[marked-for-deletion]]
* [[microformats-issues]] {{NewMarker}} - 一つ以上のmicroformatに関するissue
* [[spellcheck|spell-check dictionary]]

== 共用ワークスペース ==
* [[to-do]]
* [[microformats-issues]] - issues related to more than one microformat.
* [[external-issues]]

== 他言語でのmicroformats wiki ==

microformatsの記事を色々な言語で読んだり編集したりできます。

* 100以上の記事のある言語
** [[Main_Page|English (本家の英語)]]
** [[Main_Page-fr|Francais (フランス語)]] {{UpdateMarker-fr}}
* 10以上の記事のある言語
** [[Main_Page-pt-br| Português (ブラジル系ポルトガル語)]]
** [[Main_Page-ja|日本語]]
* 2以上の記事のある言語
** [[Main_Page-es|Espanol (スペイン語)]]
** [[Main_Page-de|Deutsch (ドイツ語)]]
** [[Main_Page-ro|Romanian]]
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.
See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

semantic-xhtml-ja

2007-07-21T00:02:39Z

IwaiMasaharu: /* Semantic Attributes */ 翻訳

<h1> 意味的な(X)HTML </h1>

Semantic (X)HTML refers to:
# (X)HTMLの意味的な要素と属性（[[presentational-html|表現的なHTML]]とは対照的なもの）
# 意味的な(X)HTMLを使って書かれた(X)HTML文書
# 意味的な(X)HTMLを使って書く習慣
# [[posh-ja|plain old semantic HTML]]

__TOC__

== Contributors ==
* [http://tantek.com/ Tantek]
* [[User:AndyMabbett|Andy Mabbett]]

== 意味的な要素 ==

（このリストは未完成です。[[semantic-xhtml|英語版]]に追加してください！）

* a
* abbr
* acronym
* address
* blockquote
* caption
* cite
* code
* dl
** dt
** dd
* dfn
* em
* ...
* h1,h2,h3,h4,h5,h6
* kbd
* li
* ...
* label
* legend
* ...
* ol
* p
* q
* ...
* samp
* strong
* sub
* sup
* table (when used for tabular data, not layout)
** tbody
** td
** tfoot
** th
** thead
** tr
* ul
* var

== 意味的な属性 ==

（このリストは未完成です。[[semantic-xhtml|英語版]]に追加してください！）

* caption
* class
* data
* href
* hreflang
* id
* lang
* rel
* rev
* scope
* summary
* type

== Presentations ==
See [[posh#POSH_Presentations|POSH Presentations]].

== See also ==
* [[semantic-xhtml-design-principles]]
* [[semantic-class-names]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

semantic-xhtml-ja

2007-07-21T00:02:10Z

IwaiMasaharu: /* Semantic Elements */ 翻訳

<h1> 意味的な(X)HTML </h1>

Semantic (X)HTML refers to:
# (X)HTMLの意味的な要素と属性（[[presentational-html|表現的なHTML]]とは対照的なもの）
# 意味的な(X)HTMLを使って書かれた(X)HTML文書
# 意味的な(X)HTMLを使って書く習慣
# [[posh-ja|plain old semantic HTML]]

__TOC__

== Contributors ==
* [http://tantek.com/ Tantek]
* [[User:AndyMabbett|Andy Mabbett]]

== 意味的な要素 ==

（このリストは未完成です。[[semantic-xhtml|英語版]]に追加してください！）

* a
* abbr
* acronym
* address
* blockquote
* caption
* cite
* code
* dl
** dt
** dd
* dfn
* em
* ...
* h1,h2,h3,h4,h5,h6
* kbd
* li
* ...
* label
* legend
* ...
* ol
* p
* q
* ...
* samp
* strong
* sub
* sup
* table (when used for tabular data, not layout)
** tbody
** td
** tfoot
** th
** thead
** tr
* ul
* var

== Semantic Attributes ==

(This list is incomplete, please add!)

* caption
* class
* data
* href
* hreflang
* id
* lang
* rel
* rev
* scope
* summary
* type

== Presentations ==
See [[posh#POSH_Presentations|POSH Presentations]].

== See also ==
* [[semantic-xhtml-design-principles]]
* [[semantic-class-names]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

semantic-xhtml-ja

2007-07-20T23:58:46Z

IwaiMasaharu: 冒頭を翻訳

<h1> 意味的な(X)HTML </h1>

Semantic (X)HTML refers to:
# (X)HTMLの意味的な要素と属性（[[presentational-html|表現的なHTML]]とは対照的なもの）
# 意味的な(X)HTMLを使って書かれた(X)HTML文書
# 意味的な(X)HTMLを使って書く習慣
# [[posh-ja|plain old semantic HTML]]

__TOC__

== Contributors ==
* [http://tantek.com/ Tantek]
* [[User:AndyMabbett|Andy Mabbett]]

== Semantic Elements ==

(This list is incomplete, please add!)

* a
* abbr
* acronym
* address
* blockquote
* caption
* cite
* code
* dl
** dt
** dd
* dfn
* em
* ...
* h1,h2,h3,h4,h5,h6
* kbd
* li
* ...
* label
* legend
* ...
* ol
* p
* q
* ...
* samp
* strong
* sub
* sup
* table (when used for tabular data, not layout)
** tbody
** td
** tfoot
** th
** thead
** tr
* ul
* var

== Semantic Attributes ==

(This list is incomplete, please add!)

* caption
* class
* data
* href
* hreflang
* id
* lang
* rel
* rev
* scope
* summary
* type

== Presentations ==
See [[posh#POSH_Presentations|POSH Presentations]].

== See also ==
* [[semantic-xhtml-design-principles]]
* [[semantic-class-names]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

semantic-xhtml-ja

2007-07-20T23:50:28Z

IwaiMasaharu: english: 19:37, 14 May 2007

<h1> Semantic (X)HTML </h1>

Semantic (X)HTML refers to:
# The semantic elements and attributes of (X)HTML (as opposed to the [[presentational-html|presentational HTML]] elements and attributes)
# (X)HTML documents that are written using semantic (X)HTML.
# The practice of writing semantic (X)HTML
# [[posh|plain old semantic HTML]]

__TOC__

== Contributors ==
* [http://tantek.com/ Tantek]
* [[User:AndyMabbett|Andy Mabbett]]

== Semantic Elements ==

(This list is incomplete, please add!)

* a
* abbr
* acronym
* address
* blockquote
* caption
* cite
* code
* dl
** dt
** dd
* dfn
* em
* ...
* h1,h2,h3,h4,h5,h6
* kbd
* li
* ...
* label
* legend
* ...
* ol
* p
* q
* ...
* samp
* strong
* sub
* sup
* table (when used for tabular data, not layout)
** tbody
** td
** tfoot
** th
** thead
** tr
* ul
* var

== Semantic Attributes ==

(This list is incomplete, please add!)

* caption
* class
* data
* href
* hreflang
* id
* lang
* rel
* rev
* scope
* summary
* type

== Presentations ==
See [[posh#POSH_Presentations|POSH Presentations]].

== See also ==
* [[semantic-xhtml-design-principles]]
* [[semantic-class-names]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

vote-links-ja

2007-03-16T20:25:37Z

IwaiMasaharu: /* 廃止された案: rel属性を用いたVote Links */ 日本語表現を更新

vote-links-ja

2007-03-16T20:24:11Z

IwaiMasaharu: /* 廃止された案: rel属性を用いたVote Links */ fix typo

= Vote Links =
__TOC__
== Specification 2005 ==
=== 編者 ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.] (formerly of [http://microsoft.com/ Microsoft Corporation])

=== 着想 ===
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati,Inc.]

=== 作者 ===
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati, Inc]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]

=== 著作権 ===
{{MicroFormatCopyrightStatement2004-ja}}

=== Patents ===
{{MicroFormatPatentStatement-ja}}

=== 謝辞 ===
Vote Linksに対しフィードバックをくれたみなさんに感謝します。特にEtanWexler、彼はVote Linksの文書に置いて初めて、Vote Linksはrel属性ではなくrev属性を使うべきだと指摘しました（[[vote-links-faq]]）。また同じくrel属性について考え、relやrev、linktypesの利用法を[[rel-faq ]]としてまとめたJohn Allsoppにも謝辞を述べたいと思います。

== 概要 ==
トラッキングやインデックス作成を行うアプリケーションが、リンク先の文書に対するページ作者のスタンスを理解していないというのは問題です。賛成や支持だけではなく、リンクしたリソースの内容に反論したい、又はもっと議論を重ねたい場合があるはずですから。

== 仕様 ==
Vote Linksは[[elemental-microformat-ja|単純microformat]]と呼ばれる、[[microformats]]オープンスタンダードのひとつです。
私たちはHTMLにてハイパーリンクを張るa要素、そのrev属性に対し、3つの新しい値を提案します。

"vote-for"、"vote-abstain"、そして"vote-against"がVote Linksで用いられる属性値です。これら3つの値は互いに相容れないものであり、それぞれ順に賛成、中立又は棄権、そして反対を表します。

アプリケーションの解釈にも寄りますが、rev属性のないVote Linkは"vote-for"又は"vote-abstain"として扱われることがあります。

リンクには人が分かり易いよう、補助的なコメントをtitle属性を用いて与えることが可能です。一般のブラウザであれば、コメントはリンクのロールオーバー時に現れるでしょう。

では、Vote Linksの例です。
<pre><nowiki>
<a rev="vote-for" href="http://ragingcow.blogspot.com"
title="neat spoof">Raging Cow</a>
<a rev="vote-against" href="http://ragingcow.com"
title="nasty corn syrup drink">Raging Cow</a>
</nowiki></pre>

=== 廃止された案: rel属性を用いたVote Links ===
前ドラフトではrev属性の代わりにrel属性を用いてリンクを張っていました。これに対しいくつかのフィードバックや分析が寄せられ、rel属性を使うのは適切ではなく、rev属性の方が意味をより正確に伝えられると判断されました。詳しくは[[rel-faq]]をご覧ください。

Vote Linksの実装に関しては、後方互換性の為、rel属性を用いたリンクを解釈してもよい（MAY）となっています。

しかしWebページ作者はrel属性をVote Linksで使ってはいけません（MUST NOT）。

== XMDPプロファイル ==
<pre><nowiki>
<dl class="profile">
<dt id="rev">rev</dt>
<dd><p><a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rev">
HTML4 definition of the 'rev' attribute.</a>
Here are some additional values.</p>
<dl>
<dt id="vote-for">vote-for</dt>
<dd>Indicates agreement with or recommendation for the referred resource.</dd>
<dt id="vote-abstain">vote-abstain</dt>
<dd>Indicates abstention or indifference for the referred resource.</dd>
<dt id="vote-against">vote-against</dt>
<dd>Indicates disagreement with or recommendation against the referred resource.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== 実装 ==
このセクションは'''参考情報'''です。

* [http://jyte.com/cl/jyte-should-integrate-microformats-votelinks vote-links claim]によると、[http://jyte.com/profile/brianellin.com Brian Ellin]はVote Linksを[http://jyte.com Jyte]上に、わずか30分で実装したとのことです。

* [http://moloko.itc.it/paoloblog/ Paolo Massa]は[http://moloko.itc.it/paoloblog/semantic_links/ SemanticLinks]というFirefoxの拡張を開発しています。これはvote-for又はvote-againstが付いたリンクを表示する、というものです。(なお、現在は作者の手によりSemanticLinksのダウンロード先が消されています)

== 標準仕様 ==
* [http://gmpg.org/xmdp/ XMDP]

== 関連仕様 ==
* [[xoxo]]
* [http://gmpg.org/xfn/ XFN]
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]
* [[rel-license]]
* [[rel-tag]]
* [[rel-nofollow]]

== FAQ ==
* Vote LinkのFAQは[[vote-links-faq]]に、rel属性に関するものは[[rel-faq]]をご覧ください。
* [[vote-links-issues]]には、このVote Links [[microformat]]に関して、いくつかの提案があります。

User:IwaiMasaharu

2007-03-16T19:31:33Z

IwaiMasaharu: /* profile */

== profile ==

I'm one of the Japanese Wiki translators/localizers.

* http://iwaim.beering.be/
* http://d.hatena.ne.jp/iwaim/
* [[User:IwaiMasaharu/greasemonkey-user-scripts|greasemonkey user scripts for Microformats Wiki]]

== ドキュメント ==

*[[User:IwaiMasaharu/guidance-of-translation-ja|翻訳の手引き(私家版)]]

== 日本語版ローカルルール(私家版)==

*日本語の言語コードは「ja」なので、翻訳時にはページの末尾に「-ja」を付けましょう。
*冒頭に「<nowiki></nowiki>」という感じでベースとなった英語版を指定しましょう。
*句読点は"、"と"。"を使いましょう。

== ツール ==

=== 対訳表 ===

*[[User:IwaiMasaharu/english-to-japanese-map|英日対訳表]]
*[[User:IwaiMasaharu/english-to-japanese-map-for-wiki-notation|Wiki記法の英日対応表]]

=== 閲覧補助 ===

*[[User:IwaiMasaharu/greasemonkey-user-scripts|Greasemonkey ユーザスクリプト集]]

icons-ja

2007-03-06T07:23:03Z

IwaiMasaharu: sync: english: 00:19, 23 Jan 2007

<h1> アイコン </h1>
これらのアイコンは、ウェブページやデスクトップ上で様々なmicroformatsを表現するために使うことができます。

== 作者 ==
* [http://factoryjoe.com/blog Chris Messina]
* [http://dmitry.baranovskiy.com Dmitry Baranovskiy]
* [http://bartleme.at Wolfgang Bartelme]

==Accessibility==
Publishers are advised to ensure that these icons are used in an accessible fashion, by including suitable "alt" attributes.

Icon designers are reminded that inability to distinguish between red and green is the commonest form of colour-blindness .

=== 著作権 ===
特に断りのない限り、これらのアイコンのライセンスは、[http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons 帰属 - 同一条件許諾 2.5]です。

== アイコン ==

=== Web ===

A [http://factorycity.net/projects/microformats-icons/ first effort] has been completed by Wolfgang Bartelme and Chris Messina to create a series of web-friendly icons and buttons for microformats.

==== General ====

* http://factorycity.net/projects/microformats%2Dicons/images/icon-hatom.png hAtom
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hcalendar.png hCalendar
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hcard-add.png hCard Add
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hcard-download.png hCard Download
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hresume.png hResume (button)
* http://factorycity.net/projects/microformats%2Dicons/images/icon-rel-tag.png rel-tag (button)
* http://factorycity.net/projects/microformats%2Dicons/images/icon-xfn.png XFN (button)

'''Comments:'''

* Hober pointed out that bright green seems to be a common color for [eventful.com/images/skin/ical.gif ical chicklets]
* Tantek wonders if the rel-tag button is useful
* ChrisMessina suggest a need for a small 10x10 tag icon
* Tantek wonders whether we need an hCard Download icon -- since it focuses too much on the "pipes"
* Ron thinks it's ok to use icons, cause it's a nice way of promoting the "Microformat idea". Maybe it's a good idea to use a downward aimed arrow to indicate the possibility to "download" something (like an hCard or hResume).

==== XFN ====

* http://factorycity.net/projects/microformats%2Dicons/images/xfn-me.png rel-me
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-friend.png rel-friend
** http://factorycity.net/projects/microformats%2Dicons/images/xfn-friend-met.png met
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-sweetheart.png rel-sweetheart
** http://factorycity.net/projects/microformats%2Dicons/images/xfn-sweetheart-met.png met
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-colleague.png rel-colleague
** http://factorycity.net/projects/microformats%2Dicons/images/xfn-colleague-met.png met

'''Comments:'''

* Tantek: wonders if a rel-me icon is necessary or appropriate; perhaps something indicating "facets"?
* ChrisMesssina: rel-me is useful in blog posts where you link to other posts that you've written
* [[User:WizardIsHungry|Jon Williams]] 13:40, 5 Jan 2007 (PST): I thought "Flickr buddy" when I first saw these due to the color. Also the pink/blue may annoy people with some gender issues. Maybe we should use green for the sweetheart?

==== VoteLinks ====
[http://microformats.org/wiki/vote-links VoteLinks]

* http://deliciouslymeta.com/projects/vote-links/vote-for.gif vote-for
* http://deliciouslymeta.com/projects/vote-links/vote-against.gif vote-against

'''Comments:'''
* [[User:SteveIvy|Steve Ivy]]: I don't have a good icon for vote-abstain. Recommendations welcome. These are also a tad large to site next to links, perhaps?
** [[User:AndyMabbett|Andy Mabbett]]: Is +1/-1 a common way of representing voting? Would ticks and crosses be better, or thumbs up/ down (or horizontal for abstain)?
*** [[User:SteveIvy|Steve Ivy]]: I rather like the icons used by [http://digg.com digg] for voting on comments, but cannot use them for obvious reasons. I'm no iconographer to be honest, but if someone were to create thumbs-up/thumbs-down icons I'd use them instead of these.

==== Geo ====

Can be used in the ''background-image'' CSS property, next to a geo microformat. It could also indicate that a map opens in a new window:

* http://microformats.telemetry.gr/openmap.gif

----

=== Mac ===
[http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons.zip http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons-preview.png]

これらの[http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons.zip アイコン]は、Macのフォルダーやファイルのアイコンとして使うことができます。それらを管理、適用するために[http://iconfactory.com/software/pixadex Pixadex]のようなツールを使うことができます。

[http://factoryjoe.com/blog Chris Messina]によって作られました。
----

=== PDF & SVG ===
[http://dmitry.baranovskiy.com/res/mf-logo.pdf http://dmitry.baranovskiy.com/i/pdffile.png] [http://dmitry.baranovskiy.com/res/mf-logo.svg http://dmitry.baranovskiy.com/i/svgfile.png]

このロゴはChrisのセットの最初のアイコンとほとんど同じような見ためです。Adobe PhotoshopやAdobe Illustratorのような編集ツールでビットマップやベクターデータに変換できます。

[http://dmitry.baranovskiy.com Dmitry Baranovskiy]によって作られました。

== Examples in the Wild ==

* [http://zeroseis.com.br ZeroSeis] uses hCard download icon.
* [http://www.nextbbs.com nextBBS] uses vote-links icons.
* [http://www.revolucao.etc.br Revolução Etc] uses hCard download icon and tag icon.

Main Page

2007-03-06T07:04:16Z

IwaiMasaharu: /* Start a microformats wiki in another language */ drop garbage

__NOTOC__
<h1>Microformats Wiki</h1>

'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.

Please read [[how-to-play]] before making any edits.

Please read [[process]] before proposing any new microformats.

__TOC__

==Getting Started==

[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]?

The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.

Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]].

Want to learn more in person? Check out [[events|microformats events]].

==Definition==

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== How to contribute ==

Do you want to help take microformats to the next level? You can:

*Check out our open [[to-do|to do list]] for things to help get done.
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.
*[[advocacy|Advocate]] the use of microformats.
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]], [[examples-in-the-wild]])
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]]
* [[hresume|hResume]]
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==

{{design_patterns}} 

== Exploratory Discussions ==
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.

* alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]
*[[attention]]
* blog description [[blog-description-examples|blog description examples]]
* blog info [[blog-info-examples|blog info examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]
* code [[code-examples| code examples]], [[code-brainstorming|code brainstorming]]{{NewMarker}}
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[collection-description|collection description]] {{NewMarker}}
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]
* [[depend-examples]]: examples of dependency graphs, especially as they relate to software {{NewMarker}}
* [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) {{NewMarker}}
* directions [[directions-examples|directions examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]
* forms [[forms-examples|forms examples]]
* genealogy [[genealogy-formats|genealogy examples]]
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]]
* hash [[hash-examples|hash examples]]
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]]
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]])
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]
* [[mfo-examples|MFO examples]]
* music [[music-examples|music examples]]
* [[operating-hours]]: [[operating-hours-examples]] ..of stores, restaurants, etc. {{UpdateMarker}}
* [[payment]]
* photo note [[photo-note-examples|photo note examples]]
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|search results example]]
* show [[show-brainstorming|show brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|tagspeak examples]]
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].
* [[thoughts-on-extending-the-geo-microformat|thoughts on extending the geo microformat]], [http://microformats.telemetry.gr examples] {{NewMarker}}
* transit table [[transit-table-examples|transit table examples]]
* [[uid]]
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]
* [[wiki-formats|wiki formats]]
* 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]]
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Tools, Test Cases and Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]
*[[why-are-content-standards-hard]]
* [[profile-examples-in-wild|Profile examples, in the wild]]

== shared work areas ==
* [[buttons]]
* [[icons]] {{NewMarker}}
* [[spread-microformats]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]]
* [[to-do]]
* [[user-interface]]
* [[marked-for-deletion]]
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.

== microformats wiki in other languages ==

You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}
** [[Main_Page-ja|日本語 (Japanese)]]
* languages with over 2 articles
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-de|Deutsch (German)]]

==== microformats translations elsewhere ====
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])
* Does somebody want to see a Dutch translation???

Main Page

2007-03-06T06:58:13Z

IwaiMasaharu: /* Exploratory Discussions */ fix syntax error

__NOTOC__
<h1>Microformats Wiki</h1>

'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.

Please read [[how-to-play]] before making any edits.

Please read [[process]] before proposing any new microformats.

__TOC__

==Getting Started==

[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]?

The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.

Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]].

Want to learn more in person? Check out [[events|microformats events]].

==Definition==

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== How to contribute ==

Do you want to help take microformats to the next level? You can:

*Check out our open [[to-do|to do list]] for things to help get done.
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.
*[[advocacy|Advocate]] the use of microformats.
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]], [[examples-in-the-wild]])
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]]
* [[hresume|hResume]]
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==

{{design_patterns}} 

== Exploratory Discussions ==
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.

* alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]
*[[attention]]
* blog description [[blog-description-examples|blog description examples]]
* blog info [[blog-info-examples|blog info examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]
* code [[code-examples| code examples]], [[code-brainstorming|code brainstorming]]{{NewMarker}}
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[collection-description|collection description]] {{NewMarker}}
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]
* [[depend-examples]]: examples of dependency graphs, especially as they relate to software {{NewMarker}}
* [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) {{NewMarker}}
* directions [[directions-examples|directions examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]
* forms [[forms-examples|forms examples]]
* genealogy [[genealogy-formats|genealogy examples]]
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]]
* hash [[hash-examples|hash examples]]
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]]
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]])
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]
* [[mfo-examples|MFO examples]]
* music [[music-examples|music examples]]
* [[operating-hours]]: [[operating-hours-examples]] ..of stores, restaurants, etc. {{UpdateMarker}}
* [[payment]]
* photo note [[photo-note-examples|photo note examples]]
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|search results example]]
* show [[show-brainstorming|show brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|tagspeak examples]]
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].
* [[thoughts-on-extending-the-geo-microformat|thoughts on extending the geo microformat]], [http://microformats.telemetry.gr examples] {{NewMarker}}
* transit table [[transit-table-examples|transit table examples]]
* [[uid]]
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]
* [[wiki-formats|wiki formats]]
* 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]]
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Tools, Test Cases and Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]
*[[why-are-content-standards-hard]]
* [[profile-examples-in-wild|Profile examples, in the wild]]

== shared work areas ==
* [[buttons]]
* [[icons]] {{NewMarker}}
* [[spread-microformats]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]]
* [[to-do]]
* [[user-interface]]
* [[marked-for-deletion]]
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.

== microformats wiki in other languages ==

You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}
** [[Main_Page-ja|日本語 (Japanese)]]
* languages with over 2 articles
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-de|Deutsch (German)]]

==== microformats translations elsewhere ====
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. [http://google.con google] E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])
* Does somebody want to see a Dutch translation???

Main Page-ja

2007-03-06T06:56:18Z

IwaiMasaharu: sync: english: 21:55, 1 Mar 2007

__NOTOC__
<h1>Microformats Wiki</h1>

'''こんにちは！''' microformats wikiにようこそ。もしこのページを見るのが初めてでしたら、[[introduction-ja|microformatsの手引き]]をご覧ください。

何か編集する前には必ず[[how-to-play-ja]]を読んでください。

新しいmicroformatsを提案する際は、必ず[[process]]を読んでからにしてください。

__TOC__

== はじめに ==

[[what-are-microformats|microformatsとは何でしょう]]？また[[what-can-you-do-with-microformats|microformatsで何ができますか]]？

まずは[http://microformats.org/about/ about page]、そして[http://microformats.org/ latest news]をご覧ください。また最新の[[press-ja|プレス]]や[[presentations-ja|プレゼンテーション]]、さらには[[podcasts|ポッドキャスト]]や[[screencasts|スクリーンキャスト]]もmicroformatsの基礎を理解する手助けになると思います。Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.
よくある質問とその答えは[[faq|FAQ]]で、また[[glossary|用語集]]もあります。

識者からもっと教わりたいことがあれば、[[events|microformatsのイベント]]もありますよ。

== 定義 ==

[http://microformats.org/discuss/ メーリングリスト]([[mailing-lists]])での一般的な定義は、「分散的開発を実現するために用いられる、セマンティクスをHTMLに埋め込む為のシンプルな仕様」です。もう少し細かく説明すると、microformatsは下記のように定義できます。
:分散的開発を実現するために用いられる
::Webにあるリソースそのものや、それを利用するツールやサービスを分散的に処理できるようにします。
:セマンティクスをHTMLに埋め込むための
::それぞれの分野に特化することで、各仕様が小さいものとなります。
:シンプルな仕様
:人間が解読できる(X)HTML/XMLドキュメントやAtom/RSSフィード、そしてプレーンなXMLでの提供
::現存するコンテンツの利用パターンを標準化することからはじめています。
::概略的で説明的なclass名を使い、ソースをみてもわかりやすくなっています。
::現存の相互運用できる規格に基づくことにより、汎用性が高まります。

シンプルに言うと、「microformatsは成文化したコンベンションのことです。」 -- [http://easy-reader.net Aaron Gustafson]

「ブラウザーでWeb巡回しかしないんだ。それはまた20世紀的だね。」 -- [http://diveintomark.org Mark Pilgrim]

== 協力の方法 ==

microformatsをより発展させるためには次のことができます。

*Check out our open [[to-do|to do list]] for things to help get done.
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.
*[[advocacy|Advocate]] the use of microformats.
*[[Main_Page-ja#.E4.BB.96.E8.A8.80.E8.AA.9E.E3.81.A7.E3.81.AEmicroformats_wiki|他言語でのmicroformats wiki]]を見てください。そして、世界中の人が利用しやすくするためにmicroformats wikiの翻訳を手伝ってください。

== 仕様 ==

[[microformats-ja|microformats]] オープンスタンダードの仕様 ([[implementations|実装]]や[[examples-in-the-wild]]もご覧ください)

* [[hcalendar-ja|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]
* [[hcard-ja|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]
* [[rel-license-ja|rel-license]](翻訳完了)
* [[rel-nofollow-ja|rel-nofollow]](翻訳完了)
* [[rel-tag-ja|rel-tag]](翻訳完了)
* [[vote-links-ja|VoteLinks]](翻訳中！)
* [http://gmpg.org/xfn/ XFN] ([[xfn-implementations|XFNの実装]]もご覧下さい)
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo-ja|XOXO]](翻訳中！)

== ドラフト ==

* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]]
* [[hresume|hResume]]
* [[hreview-ja|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== デザインパターン ==

{{design_patterns-ja}} 

== Exploratory Discussions ==
Per the microformats [[process]]:
実世界での[[examples|例]]の調査や分析、既に存在するフォーマット、またmicroformatsにできそうなもののブレインストーミングをまとめています。もし何かページを追加した場合、まず[[rejected-formats]]を見てから行ってください。
* alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]
*[[attention]]
* blog description [[blog-description-examples|blog description examples]]
* blog info [[blog-info-examples|blog info examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]
* code [[code-examples| code examples]], [[code-brainstorming|code brainstorming]]{{NewMarker}}
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[collection-description|collection description]] {{NewMarker}}
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]
* [[depend-examples]]: examples of dependency graphs, especially as they relate to software {{NewMarker}}
* [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) {{NewMarker}}
* directions [[directions-examples|directions examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]
* forms [[forms-examples|forms examples]]
* genealogy [[genealogy-formats|genealogy examples]]
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]
* hash [[hash-examples|hash examples]]
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]]
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]]
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars)- see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]])
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]
* [[mfo-examples|MFO examples]]
* music [[music-examples|music examples]]
* photo note [[photo-note-examples|photo note examples]]
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|search results example]]
* show [[show-brainstorming|show brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|tagspeak examples]]
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].
* [[thoughts-on-extending-the-geo-microformat|thoughts on extending the geo microformat]], [http://microformats.telemetry.gr examples] {{NewMarker}}
* transit table [[transit-table-examples|transit table examples]]
* [[uid]]
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]
* [[wiki-formats|wiki formats]]
* 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]]
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])

== 例 ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== ツール、テストケース、リサーチ ==

事例やコードやテストケースを見るために最初に見るべき場所はmicroformatを使ったそれぞれのページです. 二つ以上のmicroformatを使うツールやサービスは少ししかありません. このセクションは複数のmicroformatに関連するエディター、パーサー、妥当性検証ソフト、テストケース、その他情報等のためのものです。

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]
*[[why-are-content-standards-hard]]
*[[profile-examples-in-wild|Profile examples, in the wild]]

== 共有ワークスペース ==

* [[buttons]]
* [[icons-ja]] {{NewMarker}}
* [[spread-microformats]] {{NewMarker}}
* [[demo|デモ]] - microformatを試すデモへのリンク集
* [[events]]
* [[to-do]]
* [[user-interface]]
* [[marked-for-deletion]]
* [[microformats-issues]] {{NewMarker}} - 一つ以上のmicroformatに関するissue

== 他言語でのmicroformats wiki ==

microformatsの記事を色々な言語で読んだり編集したりできます。

* 100以上の記事のある言語
** [[Main_Page|English (本家の英語)]]
** [[Main_Page-fr|Francais (フランス語)]] {{UpdateMarker-fr}}
* 10以上の記事のある言語
** [[Main_Page-pt-br| Português (ブラジル系ポルトガル語)]] {{NewMarker-pt-br}}
** [[Main_Page-ja|日本語]]
* 2以上の記事のある言語
** [[Main_Page-es|Espanol (スペイン語)]]
** [[Main_Page-de|Deutsch (ドイツ語)]]

==== 他の場所にあるmicroformatsの翻訳版 ====

いくつかのmicroformatsは、このWiki以外の場所にて翻訳が行われています。もしあなたがその翻訳に関わっていたら、ぜひこのmicroformats wikiで作業しないか考えて頂けると幸いです。
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}

=== 他の言語に翻訳するのをお手伝いください！ ===

読みたい記事があなたの読みたい言葉で存在していませんか？それならば是非microformats wikiを翻訳するのにご協力ください！microformats wikiの多言語化については現在も取り組んでいます。

翻訳に際し、まずは[http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipediaにおける多言語版の位置づけ]、そして[http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia 新しいWikipediaを始めるには] をご覧下さい。
一般的なTIPSやアドバイス、このコミュニティの慣習が書いてあります。

実際に翻訳を始めるときは、まず、比較的静的であまり変化がないものを集めた[[stable-pages-ja|静的ページ]]に挙がっているものを少しずつ翻訳していくことから始めましょう。そして、(ページの変更を監視できる)[[Special:Watchlist|ウォッチリスト]]機能を使って英語版と歩調を合わせるとよいでしょう。

翻訳したページの名前: 翻訳したページのページ名は、英語版のページ名の末尾にハイフンに続いてRFC 3066の言語コード付けてください。例えば日本語版では、[[Main_Page]]は[[Main_Page-ja]]に、そして [[how-to-play]]は[[how-to-play-ja]]になります。

=== 要望のある言語はこちら ===

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])
* Does somebody want to see a Dutch translation???

hreview-ja

2007-01-28T22:34:30Z

IwaiMasaharu: /* Schema */

<h1> hReview 0.3 </h1>

[[hreview|hReview]] is a simple, open, distributed format, suitable for embedding reviews (of products, services, businesses, events, etc.) in (X)HTML, Atom, RSS, and arbitrary XML. hReview is one of several [[microformats]] open standards.

Want to get started with writing an [[hreview|hReview]]? Use the [http://microformats.org/code/hreview/creator hReview creator] to write a review and publish it.

== Microformats Draft Specification 2006-02-22 ==

; Editor: [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]
; Authors: [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]
: [http://360.yahoo.com/alidiabali Ali Diab],[http://yahoo.com Yahoo! Inc.]
: [http://spaces.msn.com/members/ianmcallister/ Ian McAllister], [http://microsoft.com/ Microsoft Corporation]
: [http://journals.aol.com/panzerjohn/abstractioneer John Panzer], [http://www.aol.com America Online, Inc.]
: [http://ifindkarma.com/blog Adam Rifkin], [http://labs.commerce.net/ CommerceNet Labs]
: [http://sippey.typepad.com/ Michael Sippey], [http://sixapart.com Six Apart, Ltd.]

Microformats [http://microformats.org/wiki/hreview#Copyright copyright] and [http://microformats.org/wiki/hreview#Patents patents] statements apply.

__TOC__

== Introduction ==
Numerous web sites publish reviews using a broad variety of schema for all sorts of things from products (movies, music, books), to businesses (restaurants, hotels, stores), to events (concerts, theatre), to people (artists, leaders, celebrities), to places (landmarks, parks), to online resources (web pages, files), to reviews of reviews themselves.

In order to enable and encourage the sharing, distribution, syndication, and aggregation, of reviews, the authors propose the hReview microformat, an open standard for distributed reviews. The authors have researched both numerous [[review-examples]] in the wild and earlier attempts at [[review-formats]], and have designed hReview around a simple minimal schema for reviews. Feedback is encouraged on the [[hreview-feedback|hReview feedback]] page.

=== Inspiration and Acknowledgments ===
Thanks to everyone who responded to the open call for implementor participation for hReview. The authors in particular wish to thank the following individuals for their constructive input and feedback: [http://www.richardault.com/ Richard Ault], [http://dannyayers.com Danny Ayers], [http://www.vertexdev.com/~jeff/ Jeffrey Barr],[http://adriancuthbert.blogspot.com/ Adrian Cuthbert],[http://jason.defillippo.com/ Jason DeFillippo], [http://www.hybernaut.com/bdv Brian Del Vecchio], Scott Derringer, [http://budgibson.com/home/ Bud Gibson], [http://joi.ito.com/ Joi Ito], [http://www.kanai.net/weblog/ Gen Kanai],[http://niallkennedy.com/ Niall Kennedy], [http://labs.commerce.net/wiki/index.php/Rohit_Khare Rohit Khare], [http://theryanking.com/ Ryan King], [http://www.jluster.org/ Jonas Luster], [http://epeus.blogspot.com/ Kevin Marks], Mark Nottingham, [http://www.powazek.com/ Derek Powazek], [http://www.judysbook.com/ Jeff Rodenburg], [http://sifry.com/alerts/ David Sifry], [http://jystewart.net/ James Stewart], [http://kung-foo.tv/ Adriaan Tijsseling], [http://www.flashenabled.com/ Phillip Torrone], Thai Tran, [http://w6daily.winn.com/ Phillip Winn], [http://yohei-y.blogspot.com YAMAMOTO Yohei].

=== Scope ===
Reviews consistently share several common fields. Where possible hReview has been based on this minimal common subset.

==== Out of scope ====
Fields that are type-specific have been omitted from hReview. It is important that hReview be kept simple and minimal from the start. Additional features can be added as deemed necessary by practical implementation experience.

The concept of a "universal object identifier", that is, how to identify the same object/item/product across different shopping sites, though something very useful to have, is outside the scope of this format.

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The hReview format is based on a set of fields common to numerous review sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related [[hcard|hCard]] and [[hcalendar|hCalendar]] standards.

=== Schema ===
hReviewのスキーマは以下の通りです:

* hReview ('''<code>hreview</code>''')
** '''<code>version</code>'''. 任意。テキスト。
** '''<code>summary</code>'''. 任意。テキスト
** item '''<code>type</code>'''. 任意。 product | business | event | person | place | website | url.
** '''<code>item</code>''' info. 必須。'''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' ) | '''[[hcard|hCard]]''' (for person or business) | '''[[hcalendar|hCalendar]]''' (for event)
** '''<code>reviewer</code>'''. 任意。'''[[hcard|hCard]]'''.
** '''<code>dtreviewed</code>'''. 任意。 ISO8601 absolute date time.
** '''<code>rating</code>'''. 任意。 fixed point integer [1.0-5.0], with optional alternate '''<code>worst</code>''' (default:1.0) and/or '''<code>best</code>''' (default:5.0), also fixed point integers, and explicit '''<code>value</code>'''.
** '''<code>description</code>'''. 任意。text with optional valid XHTML markup.
** tags. 任意。keywords or phrases, using '''[[rel-tag]]''', each with optional rating.
** permalink. 任意。'''[[rel-bookmark]]'''と'''[[rel-self]]'''を使う。
** license. 任意。'''[[rel-license]]'''を使う。

=== Field details ===
The fields of the hReview schema represent the following:

'''version''':: This optional field permits hReview publishers to specify a particular version of hReview that their content uses. By omitting this field, the publisher is stating that implementations may interpret the hReviews according to any version of the hReview specification v0.2 or later. In practice the authors of this specification are comitted to maintaining backward compatibility with content produced using earlier versions of the specification. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.3".

'''summary''':: This optional field serves as a title for the review itself.

'''item type''':: This optional field "type" provides the type of the item being reviewed, one of the following: product, business, event, person, place, website, url. If omitted, then in some cases the item type may be inferred. If the item is also an [[hcard|hCard]], then the item type is a "business" or a "person" based upon which of those the hCard represents. If the item is also an [[hcalendar|hCalendar]] event, then the item type is an "event".

'''item info''':: This required field MUST have at a minimum the name ("fn" - the formatted text corresponding to the name) of ''the'' item (an hReview describes only one item), SHOULD provide at least one URI ("url") for the item, and MAY provide at least one URL to a photo or depiction ("photo") of the item. For items of type person or business, the item info (fn, url, photo) MUST be encapsulated in an [[hcard|hCard]]. For items of type event, the item info SHOULD be encapsulated in an [[hcalendar|hCalendar]] "vevent". Unique item IDs (e.g. ISBNs, UPCs) MAY be represented as a URN ("url") for the item. Encapsulated microformats (e.g. [[hcard|hCard]] and [[hcalendar|hCalendar]] events for now) may be set on the item itself (e.g. class="item vcard"). However, when using item info subproperties ("fn", "url", "photo"), they MUST be nested <em>inside</em> the item element.

'''reviewer''':: The optional field specifies the person who authored the review. If the reviewer is specified, an hCard representing the reviewer MUST be provided. For anonymous reviews, use "anonymous" (without quotes) for the full name of the reviewer. If no "reviewer" is found inside the hReview, parsers should look outside the hReview, in the context of the page, for the "reviewer". If there is no "reviewer" outside either, then parsers should use the author defined by the containing document language, e.g. for (X)HTML documents, the <code><nowiki><address></nowiki></code> contact info for the page (which is ideally marked up as an [[hcard|hCard]] as well), for Atom 1.0 the <code><nowiki><entry></nowiki></code> <code><nowiki><author></nowiki></code> if present and if not the <code><nowiki><feed></nowiki></code> <code><nowiki><author></nowiki></code>, for RSS the <code><nowiki><author></nowiki></code> inside the containing <code><nowiki><item></nowiki></code> element.

'''dtreviewed''':: This optional field when present MUST provide an ISO8601 absolute date time of when the review was written or otherwise authored. This field SHOULD use UTC, but MAY use the time zone offset syntax. If dtreviewed is absent from the hReview, then look outside the hReview, in the surrounding context. If the context is an [[hatom|hAtom]] entry, use its "published" (or "updated" if that is missing) datetime as the dtreviewed, if not present on the entry, use the "published" (or "updated" if that is missing) of the feed. Otherwise use the creation date (or modified date if that is missing) information according to the containing document language (e.g. "published"/"updated" similarly for Atom feeds), then protocol (e.g. HTTP Last-Modified, or file system last modified datetime) as the dtreviewed.

'''rating''':: The rating is a fixed point integer (one decimal point of precision) from 1.0 to 5.0 inclusive indicating a rating for the item, higher indicating a better rating by default. Optionally a different integral "worst" value and/or "best" value MAY be specified to indicate a different range (e.g. 6 from 0-10). The "best" value may be numerically smaller than the "worst" value.

'''description''':: This optional field contains the full text representing the written opinion of the reviewer. The field MAY include valid XHTML markup (e.g. paragraphs). User agents SHOULD preserve any markup. Multiple descriptions or section descriptions (e.g. pros and cons, plusses and minusses) SHOULD be included in the description field.

'''tags''':: Tags are represented using a list of keywords or phrases (using the [[rel-tag]] microformat for each individual keyword or phrase tag) that the reviewer associates with the item. The reviewer MAY optionally provide a tag-specific rating inside each [[rel-tag]], e.g. ambience:5. Tag-specific ratings by default use the same range as an overall rating for the item if present, and MAY also have a custom worst...best range specified. Authors MAY also invert this structure for the same semantic if it is more convenient for their markup, that is, place the [[rel-tag]] inside a rating to indicate a rated tag. Note: rated tags should ideally use a tag space that explains what the ratings for that tag mean. E.g. Food:18/30 should link to a tags space for Food that explains what an 18 out of 30 means for the Food tag.

'''permalink''':: This optional field is a URL for the hReview. In addition to using the <code><a href></code> tag for this field, the attribute <code>rel="self bookmark"</code> MUST be used to indicate that the hyperlink is a permalink for the review itself. If the hyperlink already contains a <code>rel</code> attribute, then the values <code>self</code> and <code>bookmark</code> MUST be included among the space-separated set of values in the attribute. Indexers MAY treat the permalink of a review as a unique ID in order to identify and collate the same review from multiple sources (such as indexing a page multiple times). The permalink MAY also be used to indicate or imply the origin of the review. Authors MAY use the classname of "permalink" on the element representing the permalink, but are not required to do so.

'''license''':: This optional field links to the license under which the contents of the hReview itself is licensed, using the '''[[rel-license]]''' microformat.

The following field names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: <code>version, summary, fn, url, photo, description</code>. In addition, items and reviewers described by hCards MAY contain any hCard field. The rel value "self" has been reused from the [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0 specification].

=== More Semantic Equivalents ===

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For any "url", use <code><a class="url" href="...">...</a></code> inside the element with the class name 'hreview' in hReview.
* And for "photo", use <code><img class="photo" src="..." alt="Photo of ..." /></code>

* Ratings are often presented either as a set of images or characters, e.g. "***". For these, the <code><abbr></code> element is particularly useful, as such characters are an abbreviation for the precise rating, e.g. <code><abbr class="rating" title="3.0">***</abbr></code>. This is further explored in the next section.

==== Language ====
* To explicitly convey the natural language that an hReview is written in, use the standard (X)HTML 'lang' attribute on the element with class="hreview", e.g. <code><div class="hreview" lang="en"> ... </div></code> If portions of an hReview (e.g. the item name) are in a different language, use the 'lang' attribute on those portions.
* hReview processors which need to handle the language of reviews MUST process the standard (X)HTML 'lang' attribute as specified.

=== Human vs. Machine Readable ===
If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

Similarly, if an <code><img /></code> element is used for one or more properties, it MUST be treated as follows:

# For the "photo" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img /></code> element's '<code>alt</code>' attribute is the value of the property.

=== Object Includes ===

hReview 0.3 includes support for the object [[include-pattern]].

Often a single page lists an item, and then several reviews for that item. In order to avoid having to repeat the item info for each review of the item, the first review should be marked up as an hReview, with a unique "id" attribute on the item info, and then following reviews should use the object [[include-pattern]] to include the item info from the first review.

=== Notes ===
This section is informative.

* By marking up a review with the hReview microformat, the expectation is communicated that the review MAY be indexed. This has no impact on the copyright of the review itself which the publisher may explicitly specify using [[rel-license]] as specified above.
* The enumerated list of item types is under development and may be extended.
* Each type may have custom hReview fields that follow the common set.
* Additional details about a particular item should be specified with the rest of the item's info at the URL provided for the item.
* Most rating systems use the range 1.0 to 5.0, and most of those represent the rating as a number (and possibly half) of stars. Sites may use whatever graphic they wish to represent the rating.

== Examples ==
Here are a few examples of reviews from current web sites, and how they could be easily enhanced to support the hReview structured review microformat.

Want to get started with writing an [[hreview|hReview]]? Use the [http://microformats.org/code/hreview/creator hReview creator] to write a review and publish it on your blog.

=== Restaurant reviews ===

Here is an example of a simple online restaurant review:

<pre><nowiki>
<div>
<span>5 stars out of 5 stars</span>
<h4>Crepes on Cole is awesome</h4>
<span>Reviewer: <span>Tantek</span> - April 18, 2005</span>
<blockquote><p>
Crepes on Cole is one of the best little creperies in San Francisco.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</p></blockquote>
<p>Visit date: <span>April 2005</span></p>
<p>Food eaten: <span>Florentine crepe</span></p>
</div>
</nowiki></pre>

Adding hReview to this review is quite simple:

<pre><nowiki>
<div class="hreview">
<span><span class="rating">5</span> out of 5 stars</span>
<h4 class="summary">Crepes on Cole is awesome</h4>
<span class="reviewer vcard">Reviewer: <span class="fn">Tantek</span> -
<abbr class="dtreviewed" title="20050418T2300-0700">April 18, 2005</abbr></span>
<div class="description item vcard"><p>
<span class="fn org">Crepes on Cole</span> is one of the best little
creperies in <span class="adr"><span class="locality">San Francisco</span></span>.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</p></div>
<p>Visit date: <span>April 2005</span></p>
<p>Food eaten: <span>Florentine crepe</span></p>
</div>
</nowiki></pre>

Note that some of the properties of this sample review are not captured by hReview (visit date, food eaten). This is deliberate per the scope of keeping hReview minimal and simple.

This sample hReview could be rendered like this:

5 stars out of 5 stars<br />
'''Crepes on Cole is awesome'''<br />
Reviewer: Tantek - April 18, 2005<br />

Crepes on Cole is one of the best little creperies in San Francisco. Excellent food and service. Plenty of tables in a variety of sizes for parties large and small. Window seating makes for excellent people watching to/from the N-Judah which stops right outside. I've had many fun social gatherings here, as well as gotten plenty of work done thanks to neighborhood wifi.

Visit date: April 2005<br />
Food eaten: Florentine crepe<br />

==== Multidimensional Restaurant Review ====
Some restaurant reviews indicate ratings for different aspects of the restaurant. Such details are represented in hReview using tagged ratings. In addition, note the inline tags inside the description of this review.

Here is one such review in text format:

Cafe Borrone

1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;
cafeborrone.com

Food: 18/30; Ambience: 19/30; Service: 15/30; Price: $$...

This cafe is a welcoming oasis on the Peninsula. It even has a fountain
outside which cloaks the nearby sounds of El Camino traffic. Next door to a
superb indy bookstore, Cafe Borrone is an ideal spot to grab a coffee or a
snack to accompany a newly purchased book or imported periodical. Soups and
sandwich specials rotate daily. The corn chowder with croutons and big
chunks of cheese goes especially well with a freshly toasted mini-baguette.
Evenings are often crowded and may require sharing a table with a perfect
stranger. Espresso afficionados will appreciate the Illy coffee. Noise
levels can vary from peaceful in the late mornings to nearly overwhelming on
jazz band nights.

As an hReview:

<pre><nowiki>
<div class="hreview">
<div class="item vcard">
<div class="fn org summary">Cafe Borrone</div>
<span class="adr">
<span class="street-address">1010 El Camino Real</span>,
<span class="locality">Menlo Park</span>,
<span class="region">CA</span>
<span class="postal-code">94025</span>,
</span>
<span class="tel">+1-650-327-0830</span>;
<a class="url" href="http://cafeborrone.com">cafeborrone.com</a>
</div>
<ul>
<li class="rating"><a href="http://en.wikipedia.org/wiki/Food" rel="tag">
Food: <span class="value">18</span>/<span class="best">30</span></a>;</li>
<li class="rating"><a href="http://flickr.com/photos/tags/Ambience" rel="tag">
Ambience: <span class="value">19</span>/<span class="best">30</span></a>;</li>
<li class="rating"><a href="http://en.wikipedia.org/wiki/Service" rel="tag">
Service: <span class="value">15</span>/<span class="best">30</span></a>;</li>
<li class="rating"><a href="http://en.wikipedia.org/wiki/Price" rel="tag">
Price: <abbr class="value" title="2">$$</abbr>...</a></li>
</ul>
<div class="description"><p>
This <abbr class="type" title="business">
<a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a></abbr>
is a welcoming oasis on the Peninsula.
It even has a fountain outside which nearly eliminates
the sounds of El Camino traffic. Next door to a superb indy bookstore,
Cafe Borrone is an ideal spot to grab a
<a href="http://en.wikipedia.org/wiki/coffee" rel="tag">coffee</a>
or a meal to accompany a newly purchased book or imported periodical.
<a href="http://technorati.com/tag/soup" rel="tag">Soups</a> and
<a href="http://technorati.com/tag/sandwich" rel="tag">sandwich</a>
specials rotate daily. The corn chowder with croutons and big chunks of cheese
goes especially well with a freshly toasted mini-baguette. Evenings are
often crowded and may require sharing a table with a perfect stranger.
<a href="http://flickr.com/photos/tags/espresso" rel="tag">Espresso</a>
afficionados will appreciate the
<a href="http://en.wikipedia.org/wiki/Illy" rel="tag">Illy</a> coffee.
Noise levels can vary from peaceful in the late mornings to nearly overwhelming on
<a href="http://en.wikipedia.org/wiki/jazz" rel="tag">jazz</a> band nights.
</p></div>
Review (<a href="http://microformats.org/wiki/hreview">
hReview v<span class="version">0.3</span></a>)
by <span class="reviewer vcard"><span class="fn">anonymous</span></span>,
<abbr class="dtreviewed" title="20050428T2130-0700">April 28th, 2005</abbr>.
</div>
</nowiki></pre>

With an accompanying CSS style sheet like:

<pre><nowiki>
a.url { display:block }
ul { margin:1em 0; padding:0 }
ul li { display:inline }
</nowiki></pre>

This hReview could be presented similar to the original text:

Cafe Borrone<br />
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;<br />
[http://cafeborrone.com/ cafeborrone.com]<br />
<br />
[http://en.wikipedia.org/wiki/Food Food: 18/30];
[http://flickr.com/photos/tags/Ambience Ambience: 19/30];
[http://en.wikipedia.org/wiki/Service Service: 15/30];
[http://en.wikipedia.org/wiki/Price Price: $$...]<br />

This [http://en.wikipedia.org/wiki/cafe cafe] is a welcoming oasis on the Peninsula. It even has a fountain outside which cloaks the nearby sounds of El Camino traffic. Next door to a superb indy bookstore, Cafe Borrone is an ideal spot to grab a [http://en.wikipedia.org/wiki/coffee coffee] or a snack to accompany a newly purchased book or imported periodical. [http://technorati.com/tag/soup Soups] and [http://technorati.com/tag/sandwich sandwich] specials rotate daily. The corn chowder with croutons and big chunks of cheese goes especially well with a freshly toasted mini-baguette. Evenings are often crowded and may require sharing a table with a perfect stranger. [http://flickr.com/photos/tags/espresso Espresso] afficionados will appreciate the [http://en.wikipedia.org/wiki/Illy Illy] coffee. Noise levels can vary from peaceful in the late mornings to nearly overwhelming on [http://en.wikipedia.org/wiki/jazz jazz] band nights.

Review ([http://microformats.org/wiki/hreview hReview v0.3]) by anonymous, April 28th, 2005.

=== Product review ===
Here is an example of a product review:

<pre><nowiki>
<div>
<a href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up." />
The Postal Service: Give Up</a>
<blockquote><p>
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."
</p><p>
"Nothing Better" is a great track on this album, too...
</p></blockquote>
(*****)
</div>
</nowiki></pre>

Adding hReview to this review is also quite simple, but in this case requires a few more elements for the rating and reviewer which are required by hReview:

<pre><nowiki>
<div class="hreview"><span class="item">
<a class="url fn" href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up. "
class="photo" />
The Postal Service: Give Up</a></span>
<div class="description"><p>
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."
</p><p>
"Nothing Better" is a great track on this album, too...
</p></div>
(<abbr class="rating" title="5">*****</abbr>)
<p class="reviewer vcard">Review by
<a class="url fn" href="http://ifindkarma.com/blog/">Adam Rifkin</a>,
<abbr class="dtreviewed" title="200502">February 2005</abbr>
</p>
</div>
</nowiki></pre>

And this hReview might be presented like this:

[Album cover photo: ]
[The Postal Service:]
[ Give Up ]

The Postal Service: Give Up

"The people thought they were just being rewarded for treating others as they like to be treated, for obeying stop signs and curing diseases, for mailing letters with the address of the sender... Don't wake me, I plan on sleeping in..."

"Nothing Better" is a great track on this album, too...

(*****)

Review by Adam Rifkin, February 2005.

=== Movie Review ===
Finally, here is an example of a movie review.

<pre><nowiki>
<div>
<span>anonymous, April 18th, 2005</span>
<div>
<a lang="zh" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (<span lang="en">HERO</span>)
</a>
</div>
<div>Rating: 4 out of 5</div>
<blockquote><p>
This movie has great visuals and music.
</p></blockquote>
</div>
</nowiki></pre>

With hReview:

<pre><nowiki>
<div class="hreview">
<span class="reviewer vcard">
<span class="fn">anonymous</span>,
<abbr class="dtreviewed" title="20050418">April 18th, 2005</abbr>
</span>
<div class="item">
<a lang="zh" class="url fn" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (<span lang="en">HERO</span>)
</a>
</div>
<div>Rating: <span class="rating">4</span> out of 5</div>
<div class="description"><p>
This movie has great music and visuals.
</p></div>
</div>
</nowiki></pre>

Which could be presented like this:

anonymous, April 18th, 2005<br />
Ying Xiong (HERO)<br />
Rating: 4 out of 5<br />

This movie has great music and visuals.

== Examples in the wild ==
This section is '''informative'''. The number of hReview examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hreview-examples-in-wild|separate page]].

See [[hreview-examples-in-wild|hReview Examples in the wild]].

== Implementations ==
This section is '''informative'''. The number of hReview implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hreview-implementations|separate page]].

See [[hreview-implementations|hReview Implementations]].

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[rel-tag]]
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]
* [http://www.ietf.org/rfc/rfc3986.txt RFC3986]
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.ietf.org/rfc/rfc3667.txt RFC3667]
* [http://www.ietf.org/rfc/rfc3668.txt RFC3668]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* [http://local.yahoo.com/details?id=21359628 Crepes on Cole reviews on Yahoo! Local]
* Other reviews efforts. See [[reviews-formats]].
* Contributed from http://developers.technorati.com/wiki/hReview.

==== Similar Work ====
* [[hlisting-proposal|hListing]]
* [[xoxo|XOXO]]

=== Copyright ===
{{MicroformatCopyrightStatement2005}}

=== Patents ===
{{MicroFormatPatentStatement}}

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

=== Changes from v0.2 ===
The following changes have been made in hReview v0.3 over [[hreview-v0.2|hReview v0.2]]:

Normative changes:
# MUST (instead of SHOULD) use [[hcard|hCard]] for the item description of a business or person
# "reviewer" changes
## Made reviewer *optional* per feedback from Ryan King and Mark Nottingham
## If reviewer is absent from the hReview, then look outside the hReview, in the context of the page, for the reviewer. If there is no "reviewer" outside either, then use the author information according to the containing document language (e.g. <code><nowiki><address></nowiki></code> for (X)HTML pages) as the reviewer.
## MUST (instead of SHOULD) use [[hcard|hCard]] to represent reviewer information
# "dtreviewed" changes
## Made dtreviewed *optional* per feedback from Ryan King and Mark Nottingham
## If dtreviewed is absent from the hReview, then look outside the hReview, in the surrounding context. If the context is an [[hatom|hAtom]] entry, use its "published" (or "updated" if that is missing) datetime as the dtreviewed, if not present on the entry, use the "published" (or "updated" if that is missing) of the feed. Otherwise use the information according to the containing document language (e.g. "published"/"updated" similarly for Atom feeds), then protocol (e.g. HTTP Last-Modified, or file system last modified datetime).
# SHOULD use [[hcalendar|hCalendar]] to represent an item of 'type' 'event'
# Added one decimal digit of precision to ratings' numerical values based on publisher experience.
# Use [http://microformats.org/wiki/hcard#Value_excerpting the "value" construct from hCard] (as it is used in "tel" properties for example) to more explicitly markup the rating value when also providing (marking up) the best/worst of a rating.
# Added [[rel-license]] to indicate the license of the hReview as a whole.
# Permit tags inside ratings to denote rated tags, the same as ratings inside tags per suggestion from Eran Globen.
# Add [[include-pattern]] support to allow multiple reviews for the same item to not repeat the item info.

Informative changes (several, but in particular):
# Note that scalar/rated tags would ideally use a tag space that explain the ratings for that tag. E.g. to explain what Food:18/30 means.
# Updated examples accordingly.

== Further Reading ==
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

== Related Pages ==
{{hreview-related-pages}}

User:IwaiMasaharu/english-to-japanese-map

2007-01-28T22:29:29Z

IwaiMasaharu: /* 英日対訳表 O-Z */

英語と日本語の対訳表です。更新してくださってかまわないです。

__TOC__

== 英日対訳表 A-G ==

{| border="1" cellpadding="10"
|+英日対訳表 A-G
|-align=center
!bgcolor=#cccccc|英語
!bgcolor=#cccccc|日本語
|-
|Author(s)
|作者
|-
|Community
|コミュニティ
|-
|[[compound-microformat|compound microformat]]
|複合microformat
|-
|Concept
|原案
|-
|Copyright
|著作権
|-
|Creators
|作者
|-
|Draft Specification
|仕様ドラフト
|-
|Editor(s)
|編者、編集者
|-
|[[elemental-microformat|elemental microformat]]
|単純microformat
|}

== 英日対訳表 H-N ==

{| border="1" cellpadding="10"
|+英日対訳表 H-N
|-align=center
!bgcolor=#cccccc|英語
!bgcolor=#cccccc|日本語
|-
|Implementations
|実装
|-
|informative references
|
|-
|Inspiration and Acknowledgments
|謝辞
|-
|normative References
|
|-
|Name
|名称
|}

== 英日対訳表 O-Z ==

{| border="1" cellpadding="10"
|+英日対訳表 O-Z
|-align=center
!bgcolor=#cccccc|英語
!bgcolor=#cccccc|日本語
|-
|open issue(s)
|未解決の問題
|-
|optional.
|任意。
|-
|podcast(s)
|ポッドキャスト
|-
|Preamble
|あらすじ
|-
|References
|参照、関連
|-
|required.
|必須。
|-
|screencast(s)
|スクリーンキャスト
|-
|Specification(s)
|仕様、仕様書
|-
|XMDP profile
|XMDPプロファイル
|}