Microformats Wiki - User contributions [en]

hatom

2008-12-20T09:49:47Z

Hr.takahashi: Undo revision 35783 by AlcnaOlova (Talk)

<entry-title>hAtom 0.1</entry-title>
{{Template:DraftSpecification}}

hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is based on a subset of the [http://www.atomenabled.org/ Atom] syndication format. hAtom will be one of several [[microformats]] open standards.
__TOC__
== Draft Specification ==

;Editor/Author
:[http://blogmatrix.blogmatrix.com/ David Janes] ([http://www.blogmatrix.com BlogMatrix, Inc.])

;Contributors
:[http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]
:[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}
* [[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.

=== Patents ===
{{MicroFormatPatentStatement}}

== Introduction ==

hAtom is a [[microformat]] for identifying semantic information in weblog posts and practically any other place [http://www.atomenabled.org/ Atom] may be used, such as news articles. hAtom content is easily added to most blogs by simple modifications to the blog's template definitions.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The [http://atomenabled.org/developers/syndication/#person Atom Syndication Format] provides the conceptual basis for this microformat, with the following caveats:

* Atom provides a lot more functionality than we need for a "blog post" microformat, so we've taken the minimal number of elements needed.
* the "logical" model of hAtom is that of Atom. If there is a conflict, Atom should be taken as correct.
* the "physical" model of hAtom -- the actual writing of elements -- is a lot more varied than Atom provides for, due to the variety of ways weblogs are actually produced in the wild. The hAtom microformat provides a number of rules for "bridging the gap"

=== Schema ===
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, '<code>h</code>') on the outermost container elements -- the Feed or Entry. The parts of this microformat are based on analysis of many weblog, bulletin board and media posts and can be read [[blog-post-brainstorming#Discovered_Elements]].

The hAtom schema consists of the following:

* hfeed ('''<code>hfeed</code>'''). optional.
** '''<code>feed category</code>'''. optional. keywords or phrases, using '''[[rel-tag]]'''.
** hentry ('''<code>hentry</code>''').
*** '''<code>entry-title</code>'''. required. text.
*** '''<code>entry-content</code>'''. optional (see field description). text. [*]
*** '''<code>entry-summary</code>'''. optional. text.
*** '''<code>updated</code>'''. required using [[datetime-design-pattern]]. [*]
*** '''<code>published</code>'''. optional using [[datetime-design-pattern]].
*** '''<code>author</code>'''. required using '''[[hcard|hCard]]'''. [*]
*** '''<code>bookmark</code>''' (permalink). optional, using '''[[rel-bookmark]]'''.
*** tags. optional. keywords or phrases, using '''[[rel-tag]]'''.

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Feed =====
* a Feed element is identified by the class name <code>hfeed</code>
* a Feed element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1 Atom feed]
* the Feed element is optional and, if missing, is assumed to be the page
* hAtom documents {{may}} have multiple Feed elements

===== Feed Category =====
* a Feed Category element is identified by [[rel-tag]]
* a Feed {{may}} have a Feed Category
* a Feed Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside a [http://www.atomenabled.org/developers/syndication/#optionalFeedElements feed]
* Feed Category elements {{must}} appear inside a Feed element but not inside an Entry element
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry =====
* an Entry element is identified by class name <code>hentry</code>
* an Entry element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2 Atom entry]
* any microformat content inside a <code><blockquote></code> or <code><q></code> element within the Entry should not be considered part of the Entry.
: ''This allows quoting other microformated data without worry of corrupting the model''

===== Entry Category =====
* an Entry Category element is identified by [[rel-tag]]
* an Entry {{may}} have an Entry Category
* an Entry Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside an [http://www.atomenabled.org/developers/syndication/#optionalEntryElements entry]
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry Title =====
* an Entry Title element is identified by the class name <code>entry-title</code>
* an Entry {{should}} have an Entry Title
* an Entry Title element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14 Atom entry title]
* if the Entry Title is missing, use
** the first <code><h#></code> element in the Entry, or
** the <code><title></code> of the page, if there is no enclosing Feed element, or
** assume it is the empty string

===== Entry Content =====
* an Entry Content element is identified by class name <code>entry-content</code>
* an Entry {{should}} have Entry Content
* an Entry Content element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent Atom content]
* an Entry {{may}} have 0 or more Entry Content elements. The "logical Entry Content" of an Entry is the concatenation, in order of appearance, of all the Entry Contents within the Entry
: ''Many web logs split content into multiple sections with a "Read More" link and JavaScript tricks. This is also needed in cases where Entry Titles are coded in-line and are considered part of the content.''
* if the Entry Content is missing, assume it is the empty string

===== Entry Summary =====
* an Entry Summary element is identified by class name <code>entry-summary</code>
* an Entry Summary element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13 Atom summary]
* an Entry {{may}} have 0 or more Entry Summary elements. The "logical Entry Summary" of an Entry is the concatenation, in order of appearance, of all the Entry Summarys within the Entry

===== Entry Permalink =====
* an Entry Permalink element is identified by [[rel-bookmark]]
* an Entry {{should}} have an Entry Permalink
* an Entry Permalink element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7 Atom link in an entry]
* if the Entry Permalink is missing, use the URI of the page; if the Entry has an "id" attribute, add that as a fragment to the page URI to distinguish individual entries

===== Entry Updated =====
* an Entry Updated element is identified by class name <code>updated</code>
* an Entry Updated element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15 Atom updated]
* an Entry {{should}} have an Entry Updated element
* use the [[datetime-design-pattern]] to encode the updated datetime
* if there is no Entry Updated element,
** use the Entry Published element, if present
** otherwise the page is invalid hAtom

===== Entry Published =====
* an Entry Published element is identified by the class name <code>published</code>
* an Entry Published element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 Atom published]
* use the [[datetime-design-pattern]] to encode the published datetime

===== Entry Author =====
* an Entry Author element is represented by class name <code>author</code>
* an Entry Author element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1 Atom author]
* an Entry Author element {{must}} be encoded in an [[hcard|hCard]]
* an Entry Author element {{should}} be encoded in an <code><address></code> element
* an Entry {{should}} have at least one Entry Author element
* an Entry {{may}} have more than one Entry Author elements
* if the Entry Author is missing
** find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
** otherwise the entry is invalid hAtom

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hfeed</dt>
<dd>
The concept of atom:feed from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>hentry</dt>
<dd>
The concept of atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-title</dt>
<dd>
The concept of atom:title inside of an atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-content</dt>
<dd>
The concept of atom:content from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-summary</dt>
<dd>
The concept of atom:summary from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>bookmark</dt>
<dd>
The concept of atom:link (without any "rel") with an atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>published</dt>
<dd>
The concept of atom:published from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>updated</dt>
<dd>
The concept of atom:updated from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>author</dt>
<dd>
The concept of atom:author from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
</dl>
</dd>
</dl>
</pre>

== Examples ==

See [[hatom-examples]].

=== Examples in the wild ===

See [[hatom-examples-in-wild]].

== Implementations ==

This section is '''informative'''.

The following implementations have been developed which either generate or parse hAtom links. If you have an hAtom implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://spinn3r.com/opensource.php Spinn3r Open Source] - implemented in [http://spinn3r.com Spinn3r] and part of [http://code.tailrank.com/feedparser FeedParser] and our announcement of [http://blog.spinn3r.com/2008/01/announcing-spin.html hAtom in Spinn3r 2.1]
* the [http://tools.blogmatrix.com/extract/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://tools.blogmatrix.com/extract/?uri=http%3A%2F%2Fblog.davidjanes.com&microformat=hatom&submit=Submit example])
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - has GPL'ed PHP code for reading hAtom
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supports subscribing to hAtom as a feed format
* There is a [http://code.google.com/p/transformr/downloads/list hAtom toolkit] that extracts hAtom, there is also a [http://transformr.co.uk/ demo here]


== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc4287 RFC4287: The Atom Syndication Format]
* [[hcard-parsing]]
* [[rfc-2119|RFC 2119]]
* [[iso-8601|ISO8601]]

=== Informative References ===
* [http://www.atomenabled.org/ atomenabled.org]

== Further Reading ==
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/ Getting Semantic With Microformats, Part 5: hAtom] by [http://www.ablognotlimited.com/ Emily Lewis]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hAtom:

* [[blog-post-brainstorming|blog-post Brainstorming]]

=== Version 0.1 ===

Version 0.1 was released 28 February 2006.

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hAtom, check the [[hatom-faq|hAtom FAQ]], and if you don't find answers, add your questions!

=== Issues ===
* Please add any issues with the specification to the separate [[hatom-issues|hAtom issues]] document.

==See Also==
{{hatom-related-pages}}
* [[rel-enclosure]] - how to semantically reference enclosures (e.g. podcasts) in hAtom
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-post-feed-equivalence]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[xhtml-syndication]]

[[Category:Draft Specifications]]
[[Category:hAtom]]

press-ja

2008-12-20T09:46:08Z

Hr.takahashi: Undo revision 35729 by MonouRodro (Talk)

__NOTOC__

<h1> Press </h1>

このページでは、[[microformats-ja|microformats]]が取り上げられたオンライン上の記事を紹介しています。他に[[screencasts]]、[[presentations-ja|プレゼンテーション]]、[[podcasts|ポッドキャスト]]、[[books-ja|書籍]]などのメディアでもmicroformatsが取り上げられています。

== 2006 ==

=== 8月 ===

* [http://digital-web.com/articles/the_big_picture_on_microformats/ The Big Picture on microformats] - who's doing what with microformats right now - by John Allsopp - Published August 28th, 2006.
* [http://www.thinkvitamin.com/features/design/how-to-use-microformats Add microformats magic to your site] by John Allsopp - Published August 25th, 2006.

=== 7月 ===
* [http://knowledge.wharton.upenn.edu/article.cfm?articleid=1526 Knowledge at Wharton: Tantek Çelik and Rohit Khare: The Progress and the Promise of Microformats] - 2006年7月20日に公開。

=== 6月 ===
* [http://devzone.zend.com/node/view/id/584 Microformats, PHP and hKit] PHP開発者の為の情報サイトdevzone.zend.comより。6月28日。
* [http://www.mercurytide.com/knowledge/white-papers/microformats Building a more semantic web with microformats] Mercurytideより。6月20日。

=== 5月 ===
* [http://www.devsource.com/article2/0,1895,1961106,00.asp DevSource: An Developer's Introduction to Microformats by Phil Haack, May 11.]
** 記事の著者Phil Haackによる[http://haacked.com/archive/2006/05/11/IntroductionToMicroformatsArticle.aspx 記事に関するblogポスト]も参照されたい。

=== 4月 ===
=== 3月 ===
* (need to backfill these - there were a bunch and I think we simply forgot to add them in)

=== 2月 ===
* [http://book.mycom.co.jp/wd/ Web Designing] [http://book.mycom.co.jp/wd/bn/200603.html 2006年3月号]にmicroformatsの紹介記事が載っています。
* [http://www.release1-0.com/freshproduce/newideas_socialtime.cfm Release 1.0 / Ideas / New Ideas that Matter: Time as a social object], February 16. Video interviews composite, including a bit on microformats.
* [http://2006.sxsw.com/interactive/web_awards/finalists/ SXSW 2006 Web Awards Finalists], February 3rd. [http://microformats.org microformats.org] is a finalist in the "Technical Achievement" category for "the sites that are re-inventing and re-defining the technical parameters of our online experience".

=== 1月 ===
* [http://code.google.com/webstats/index.html Google Web Authoring Statistics, January 20]
*# The home page of the study "[http://code.google.com/webstats/index.html Web Authoring Statistics]" itself both mentions “microformats.org” and links to http://microformats.org .
*# The "[http://code.google.com/webstats/2005-12/pageheaders.html Page Headers]” page notes that the [http://gmpg.org/xfn/ XFN] microformat is the most popular HTML metadata profile: “…people do use the profile attribute, though. The three most-often used values are http://gmpg.org/xfn/1, http://dublincore.org/documents/dcq-html/, and http://gmpg.org/xfn/11. This makes XFN the most popular HTML metadata profile!”
*# The “[http://code.google.com/webstats/2005-12/element-a.html a element]” page found that three of the most popular ‘rel’ attribute values were microformats: #1 [[rel-nofollow-ja|rel-nofollow]], #2 [[rel-license]], #5 [[rel-tag-ja|rel-tag]].
* [http://www.philoneist.com/50226711/interview_with_technorati_marketing_director_derek_gordon.php Philoneist: Interview With Technorati Marketing Director Derek Gordon by Jonathan G. Cohen, January 11]
* [http://www.kbcafe.com/iBLOGthere4iM/?guid=20060101232742 #2 on the list of Best Web 2.0 Blogs, January 2]

== 2005 ==

=== 12月 ===
* [http://www.publish.com/article2/0,1759,1904359,00.asp Publish: Year in Review: CSS, Standards, Microformats and Flash, By Stephen Bryant, December 21]
* [http://www.primezone.com/newsroom/news.html?d=91118 Newswire: Structured Blogging to support microformats, December 13th]
* [http://www.linuxjournal.com/article/8731 Linux Journal: Syndication and the Live Web Economy, By Doc Searls, December 9]

=== 11月 ===
* [http://acmqueue.com/modules.php?name=Content&pa=showpage&pid=349&page=4 ACM Queue: A Conversation with Ray Ozzie, ACM Queue vol. 3, no. 9 - November 2005]
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer by Garrett Dimon, November 14, 2005]

=== 10月 ===
* [http://www.xml.com/pub/a/2005/10/19/microformats-and-web-2.0.html XML.com: Microformats and Web 2.0 by Micah Dubinko, October 19, 2005]

=== 9月 ===
* [http://channel9.msdn.com/Showpost.aspx?postid=118325 Channel 9: Interview at PDC] - Robert Scoble interviews Tantek Çelik briefly on web standards, IE, and microformats.

=== 7月 ===
* [http://www.acm.org/technews/articles/2005-7/0722f.html#item12 ACM News Service - Volume 7, Issue 819: Friday, July 22, 2005]
* [http://lists.ssc.com/pipermail/suitwatch/2005-July/000090.html Linux Journal: SuitWatch -- July 21 -- by Doc Searls, Senior Editor of Linux Journal: Making More Sense of the Web]
* [http://knowledge.wharton.upenn.edu/index.cfm?fa=viewArticle&id=1247&specialId=38 Knowledge at Wharton: Supernova 2005: It's a Whole New, Connected World: What's the Next Big Thing on the Web? It May Be a Small, Simple Thing -- Microformats]
** Simplified Chinese: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&languageid=4>
** Traditional Chinese: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&l=4&languageid=5>
** Original english version: <http://knowledge2.wharton.com.cn//index.cfm?fa=article&articleid=1203&specialid=58&languageid=1>

=== 6月 ===
* [http://news.com.com/2030-12-5745034.html#microformats CNET News.com: Supernova 2005 blogcast] - David Weinberger interviews Tantek Çelik and Rohit Khare about microformats and [http://microformats.org/ microformats.org].
** [http://blog.blogcast2005.silkclips.com/clipView?http://silkblogs.com/FindResource/EC139870-22E5-F208-70FA-BC437BD64420/celik-khave-full.mov Watch the full interview with Rohit Khare & Tantek Çelik (22:21 minutes)]
* Golem: [http://www.golem.de/0506/38831.html microformats.org - Formate für Menschen und Maschinen] (German: microformats.org - Formats for humans and machines)

=== 3月 ===
* [http://www.xml.com/pub/a/2005/03/23/deviant.html XML.com: What Are Microformats?]

User:IwaiMasaharu/english-to-japanese-map

2008-12-20T09:45:30Z

Hr.takahashi: Undo revision 35848 by ElpasCnaze (Talk)

英語と日本語の対訳表です。更新してくださってかまわないです。

__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プロファイル
|}

presentation-jp

2008-12-20T09:44:56Z

Hr.takahashi: Undo revision 35977 by SitlaTatrd (Talk)

#REDIRECT [[presentation-ja]]

Main Page-jp

2008-12-20T09:44:38Z

Hr.takahashi: Undo revision 35836 by RelroLchic (Talk)

#REDIRECT [[Main Page-ja]]

User:IwaiMasaharu/greasemonkey-user-scripts

2008-12-20T09:40:26Z

Hr.takahashi: Undo revision 35550 by BogetEltde (Talk)

__TOC__

=== add Link to Main_Page-ja for Microformats Wiki ===

*http://gmscripts.sourceforge.jp/files/microformats/org/wiki/addLinkToJapaneseMainPageforMicroformatsWiki.user.js

This script add the link to Main_Page-ja in navigation list.

User:IwaiMasaharu

2008-12-20T09:38:57Z

Hr.takahashi: Undo revision 36082 by CdomcOroll (Talk)

== 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 ユーザスクリプト集]]

elemental-microformat-ja

2008-12-20T09:32:43Z

Hr.takahashi: 存在しない日本語翻訳記事へのリンクを修正

単純[[microformats-ja|microformat]]は、標準化されたXHTML要素の中に埋め込んで一つの問題解決する小さな解決法です。ウェブページに組み込むためのものであり、大きな[[compound-microformat-ja|複合microformats]]のためのブロックとして機能するように設計されています。

今存在する実例は次のものです。
* [[rel-enclosure|rel-enclosure]]
* [[rel-license-ja|rel-license]]
* [[rel-nofollow-ja|rel-nofollow]]
* [[rel-tag-ja|rel-tag]]
* [[vote-links-ja|VoteLinks]]
* [http://gmpg.org/xfn/ XFN]
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo-ja|XOXO]]

http://www.microformats.org/img/micro-diagram.gif

hresume-ja

2008-12-20T09:28:01Z

Hr.takahashi: Undo revision 35547 by PasboAcelv (Talk)

<h1> hResume </h1>

hResumeは、経歴(resume)や履歴書(CV)を公開するためのmicroformatです。hResume is one of several open microformat standards suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML.

Want to get started with writing an hResume? Use the [http://hresume.weblogswork.com/hresumecreator/ hResume Creator] to create your hResume and publish it, or follow the hResume authoring tips to add hResume markup to your web page or blog.

<h2> Microformats Draft Specification </h2>

; Editor/Author: [http://theryanking.com Ryan King]
; Acknowledgments: See [http://microformats.org/wiki/hresume#Acknowledgements acknowledgments].

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

__TOC__

== Status ==
Draft, version 0.1.

== Introduction ==
=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

== Format ==
=== In General ===
The hResume format is based on a set of fields common to numerous resumes published today on the web. Where possible field names have been chosen and reused from preexisting microformats.

=== Schema ===
The hResume schema consists of the following:

* hResume
** summary. optional. text.
** contact info. required. '''Must''' use [[hcard|hCard]]. '''Should''' use <code class="element"><address></code> + [[hcard|hCard]].
** experience. optional. One or more [[hcalendar]] events with the class name '<code class="class-name">experience</code>', with an embedded [[hcard|hCard]] indicating the job title, name of company, address of company etc.
** education. optional One or more [[hcalendar]] events with the class name '<code class="class-name">education</code>', with an embedded [[hcard|hCard]] indicating the name of school, address of school etc.
** skills. optional. phrases or keywords using the [[rel-tag]] microformat with the class name '<code class="class-name">skill</code>'.
** affiliations. optional. the class name <code class="class-name">affiliation</code> along with an [[hcard]] of the organization
** publications. optional. One or more citations. Use cite tag.

=== Field details ===
The fields of the hResume schema represent the following:

* '''<code class="class-name">hresume</code>''':: root class name
* '''<code class="class-name">summary</code>''':: The class name <code class="class-name">summary</code> is used to mark up an overview of qualifications and objectives.
* '''contact''':: Current contact info in an [[hCard]]. '''Should''' use <code class="element"><address></code> with [[hCard]] when possible.
* '''<code class="class-name">education</code>''':: the class name '<code class="class-name">education</code>' is applied to an [[hcalendar]] event.
* '''<code class="class-name">experience</code>''':: the class name '<code class="class-name">experience</code>' is applied to an [[hcalendar]] event. Job titles/positions should use an [[hCard]].
* '''<code class="class-name">skill</code>''':: An hResume may be tagged using the [[rel-tag]] microformat and the '<code class="class-name">skill</code>' class name.
* '''<code class="class-name">affiliation</code>''':: The class name <code="class-name">affiliation</code> is used along with an [[hcard]] of the organization
* '''<code class="class-name">publications</code>''':: just use <code class="element"><cite></code>. When there is a [[citation]] microformat, then that can be used in combination with the cite element to further markup the components of the citation.

=== XMDP Profile ===
* [[hresume-profile]] (@TODO)

=== Notes ===
This section is informative.

*...

== Examples ==
=== Summary ===
An example summary:

<pre><nowiki>

I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996,
designing with pastels while others will still using tiled background images and frames...

</nowiki></pre>

=== Contact ===
<pre><nowiki>
<address class="vcard">
Pedro Sanchez

123 Fake St.
Preston, Idaho 83263

Email: <a class="email" href="mailto:joe@example.com">pedro@vote-for-pedro.com</a>
Homepage: <a class="url" href="http://vote-for-pedro.com/">vote-for-pedro.com</a>
Phone: +01.208.555.4567
</address>
</nowiki></pre>

=== Education ===
<pre><nowiki>
<ol class="vcalendar">
<li class="education vevent">
<a class="url summary" href="http://example.edu/">Preston High School</a>
(<abbr class="dtstart" title="2001-01-24">2001</abbr> - <abbr class="dtend" title="2005-05-25">2005</abbr>)
</li>
...
</nowiki></pre>

=== Experience ===
==== Basic ====
A basic experience event:

<pre><nowiki>
<ol class="vcalendar">
<li class="experience vevent">
President,
Preston High School,
<abbr class="dtstart" title="2004-09-01">May 2004</abbr> - <abbr title="2005-05-25">present</abbr>
</li>
...
</nowiki></pre>

==== Job Titles ====
To express one or more job titles/positions in the same experience event you should use [[hCard]]s. [[hcard]] requires the <code class="class-name">fn</code> ("formatted name") field, but it isn't reasonable to repeat your name for every job title you mark up in [[hResume|hresume]]. So, you may use an <code class="element"><object></code> and the class name '<code class="class-name">include</code>' with a reference to the <code class="class-name">fn</code> somewhere else on the page.

For example, this [[hCard]] refers to another [[hCard]]

<pre>

<object data="#j" class="include"></object>
Preston High School
Class President

</pre>

Where "<code class="attr-value">j</code>" is the id attribute value of the "<code class="mf-prop">fn n</code>" element of the contact [[hCard]] at the top of the page, e.g. (shown here as a verbose [[hCard]] for purposes of illustration that the reference may be to a subtree, not just a text node):

<pre><nowiki>
<address class="vcard">

Pedro
Sanchez

</address>
</nowiki></pre>

This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.
Note: the object data attribute MUST be a local ID reference. External references (which would require a consuming application to load an external resource) are currently not supported by this method.

=== Skills ===
Some sample skills tags:
<pre><nowiki>
I have skills in <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Bow_%28weapon%29">bow hunting</a>
and <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Nunchucks">nunchucks</a>.
</nowiki></pre>

=== Affiliations ===
<pre><nowiki>
National Honor Society
</nowiki></pre>

=== Publications ===
<pre><nowiki>
<cite>Breeding Ligers for Fun and Magic</cite>, Idaho Press, 2004.
</nowiki></pre>

== Examples in the wild ==
This section is '''informative'''.

The following sites have published hResumes, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hResume on your own page, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://steinhardt.nyu.edu/ NYU Steinhardt] has [http://steinhardt.nyu.edu/faculty_bios/list/Faculty 240+ faculty bios marked up], e.g. [http://steinhardt.nyu.edu/faculty_bios/view/Susan_Murray]. ([[User:WizardIsHungry|Jon Williams]])
* [[User:ClintAndrewHall|Clint Hall]] has marked up his [http://www.clintandrewhall.com/resume.html resume] as an hResume.
* [[User:Csarven|Sarven Capadisli]] has marked up his [http://www.csarven.ca/cv Curriculum Vitae] as an hResume.
* [[User:Jax|Xavier Roy]] has marked his [http://xavierroy.com/resume/ resume] with hResume
* [[User:SanchTheFat|Robert O'Rourke]] has marked up his [http://robert.o-rourke.org/ CV] with hResume.
* [[User:Keri Henare|Keri Henare]] has marked up [http://www.kerihenare.com/cv/ his Curriculum Vitae] using hResume.
* [[User:Kwilson|Kenn Wilson]] has marked up [http://www.3color.org/~kwilson/resume/kenneth-wilson.html his resume] using hResume, following [[User:Ralph Brandi|Ralph Brandi]]'s method of using object.include.
* [[User:Ralph Brandi|Ralph Brandi]] has [http://www.brandi.org/ralph/resume/ marked up his resume] with hResume, additionally using the object.include method to associate one description with three hCalendar experiences.
* [[User:Pat Ramsey|Pat Ramsey]] has his [http://www.southwestern.edu/~ramseyp/ramsey_resume2006.html resume] marked up as an hResume.
* [[User:Wim Le Page|Wim Le Page]] has also marked up [http://adrem.ua.ac.be/~wlepage/curriculum-vitae/ his curriculum vitae] as an hResume.
* [[user:Jonathan Arkell|Jonathan Arkell]] has posted an [http://portfolio.jonnay.net/cv/ hResume] on his portfolio website.
* [http://steve.ganz.name/hresume/ Steve Ganz - hResume 0.1]
* [[User:Dave Cardwell|Dave Cardwell]] has marked up [http://davecardwell.co.uk/cv/ his curriculum vitae] as an hResume.
* [[User:EdwardOConnor|Edward O'Connor]]'s [http://edward.oconnor.cx/resume/ resume] is in hResume, and has some experimental JavaScript in it to extract a skill summary from the resume.
* [[User:Lindsey Simon|Lindsey Simon]] has his [http://www.commoner.com/~lsimon/lindsey_simon_resume.html resume] marked up as an hResume - with lots of thanks to Pat Ramsey.
* [[User:Ben Ward|Ben Ward]] has published [http://ben-ward.co.uk/cv his CV] with hResume.
* [http://www.kelleychambers.com Kelley Chambers] has published her [http://www.kelleychambers.com/resume resume] via [http://www.ssdesigninteractive.com/ssdesign/?p=96 Sajid Saiyed's Microformat hResume Plugin for Wordpress].
* [[User:Fishy5|Brennan Falkner]] used hResume to markup his [http://my.usf.edu/bbcswebdav/users/bfalker/resume.html resume].
* [http://www.zachary.com/creemer/resume.html David Creemer's resume] uses hResume, with thanks to Pat Ramsey for the CSS.

=== Examples with problems ===
* [[user:Izo|Mathieu Drouet]] has posted an [http://izo.aucuneid.com/hresume.html hResume].
** ''Incorrect root class name hResume? -- [[DavidJanes]]''

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse hResumes. If you have an hResume implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* The [http://spurinc.com Spur] team has created an hResume WordPress plugin located at [http://hresume.weblogswork.com/?page_id=3 hResume Plugin]. See an example of the hResume markup [http://hresume.weblogswork.com/?page_id=6 here]. Neat feature of the hResume plugin is that it automatically creates a new page for the resume - no cutting and pasting...

* The [http://www.ssdesigninteractive.com/ssdesign Sajid Saiyed] has created an hResume WordPress plugin located at [http://www.ssdesigninteractive.com/ssdesign/?p=96 Microformat Resume Plugin]. See an example of the hResume markup [http://www.ssdesigninteractive.com/ssdesign/?page_id=95 here].

* Spur also created a standalone hResume Creator located at [http://hresume.weblogswork.com/hresumecreator/ hResume Creator]. The creator will generate hResume markup ready to cut and paste into your webpage.

== Copyright ==
{{MicroFormatCopyrightStatement2006}}

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[include-pattern|include pattern]]
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML]
* [http://gmpg.org/xmdp/ XMDP]
* [[rel-tag| Rel-Tag]]
* @TODO

=== Informative References ===
@TODO

== Acknowledgements ==
=== Concept ===
* [http://theryanking.com/ Ryan King], [http://technorati.com Technorati]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati]
* James Levine [http://simplyhired.com Simply Hired]
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati]

== Related Pages ==
* [[resume-examples]]
* [[resume-formats]]
* [[resume-brainstorming]]
* Feedback is encouraged on the [[hresume-feedback]] page.
* If you have any questions about hResume, check the [[hresume-faq|hResume FAQ]], and if you don't find answers, add your questions to the end!
* Please add any issues with the specification to the separate [[hresume-issues|hResume issues]] document.

== Further Reading ==
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

Main Page-ja

2008-12-20T09:27:31Z

Hr.takahashi: /* 仕様 */ XMDPの日本語翻訳記事が存在しないので、リンク先を修正。

<entry-title>Microformats Wikiにようこそ！</entry-title>

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

== はじめに ==
* [[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のイベント]]に参加してみてください。
* microformats wiki は、microformats の開発と貢献を支援するため、素晴らしい強化を行いました。この wiki を使いこなして発表するための概要は [[wiki-2-ja|wiki-2]] 紹介ページをご覧ください。

== 定義 ==
Microformatsとは、Webサイトで人やイベント、タグを記述する際に用いるマークアップ方法です。

Microformatsは、あなたのWebサイトからフィードやAPIを早く簡単に提供するための手段です。また、Microformatsによって、さらに詳しい情報をWebで発信することができるようになります。[[what-are-microformats-ja|マイクロフォーマットとは何か]]、また[[what-can-you-do-with-microformats|マイクロフォーマットを使うと何ができるか]]にある、より詳しい説明もご覧ください。

== 協力するには ==
Microformatsをさらに高めるためには、みなさんの協力が必要です。

* あなたのWebサイトやサービス、製品で[[get-started|microformatsを利用]]する。
* マイクロフォーマットをもっと使ってもらえるよう、[[advocacy|周りにすすめる]]。
* [[testimonial|Microformatsをおすすめするエントリ]]を書く。
* [[to-do|TO DOリスト]]にあるタスクをこなす。
* [[irc-ja|IRCチャンネル]]や[[mail|メーリングリスト]]で学んだり、質問に答える (メールを送る前に、[[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]])。
* 新しいmicroformatsを提案する前に、あなたのWebサイトが[[POSH]]であり、[[get-started|すでにあるmicroformatsを利用]]している事を確認する。そのあと、[[process|新しいフォーマットを提案する際のプロセス]]について良く読む。

== 仕様 ==
以下はオープンスタンダードとなった[[microformats-ja|microformats]]の仕様です。

* [[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]]
* [[XFN-ja|XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP|XMDP]]
* [[xoxo-ja|XOXO]] (翻訳中!)

== ドラフト ==
* [[adr|adr]] - 住所のマークアップ
* [[geo|geo]] - [http://en.wikipedia.org/wiki/WGS84 世界測地系]による、緯度と経度のマークアップ
* [[hatom|hAtom]] - 更新情報を配信する (例: Weblogのエントリ)
* [[hresume-ja|hResume]] (翻訳中!) - 履歴書の公開
* [[hreview-ja|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]]- to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[relpayment-research|rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]
* [[xfolk-ja|xFolk]]
* [[haudio|hAudio]]
* [[recipe|hRecipe]]

== デザインパターン ==
{{design_patterns-ja}} 
* [[elemental-microformat-ja|単純microformats]]
* [[compound-microformat-ja|複合microformats]]

== 予備的な論議 ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== 例 ==
* [[examples-in-the-wild-ja|実際の利用例]]
* [[implementations|ツールの実装]]
* [[zen-garden|Zen Garden]]

== リソース ==
See [[resources]].

== ユーザ中心開発 ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== 共有作業領域 ==
* [[to-do|TODOリスト]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|特別ページ]]
* [[year-in-review]]

== ツール、テストケース、リサーチ ==
例やコード、テストケースなどはそれぞれ個々のmicroformatのページに記載しています。
ただほんの少しだけ、複数のmicroformatの処理を必要とする分野横断的な[[tools|ツールとサービス]]があります。
[[tools|ツールとサービス]]は、複数のmicroformat全体に関連した編集者、パーサ、バリデータ、テストケース、およびその他の情報を対象としたページです。

== 他言語でのmicroformats wiki ==
microformatsの記事を、さまざまな言語で読んだり、編集したりできます。

* 100以上の記事のある言語
** [[Main_Page|English (本家の英語)]]
** [[Main_Page-fr|Français (フランス語)]] {{UpdateMarker-fr}}
* 10以上の記事のある言語
** [[Main_Page-pt-br|Português (ブラジル系ポルトガル語)]]
** [[Main_Page-ja|日本語]]
** [[Main_Page-ru|Русский (ロシア語)]]
* 2以上の記事のある言語
** [[Main_Page-cs|Česky (チェコ語)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (ドイツ語)]]
** [[Main_Page-es|Español (スペイン語)]]
** [[Main_Page-gl|Galego (ガリーシア語)]] {{NewMarker}}
** [[Main_Page-pl|Polski (ポーランド語)]]
** [[Main_Page-ro|Română (ルーマニア語)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (中国語)]]
* 翻訳が始まったばかりの言語
** [[Main_Page-ar|العربية (アラビア語)]]
** [[Main_Page-th|ภาษาไทย (タイ語)]]
** [[Main_Page-it|Italiano (イタリア語)]] {{NewMarker}}
** [[Main_Page-kr|대한민국 (韓国語)]] {{NewMarker}}
* その他
**[http://ja.wikipedia.org/wiki/Microformat Wikipediaのmicroformatsページ]は、多くの言語版ができています。

[[other-languages]]や[[how-to-start-new-translation|how-to-start-a-new-translation]]もご覧ください。

presentations-ja

2008-12-20T09:21:20Z

Hr.takahashi: Undo revision 35727 by RactaPasba (Talk)

<h1> microformats のプレゼンテーション資料</h1>

このページは、[[microformats]]という概念や特定のmicroformatsについての解説やディスカッションで使われた様々なプレゼンテーションやセッションの資料、論文、ポスターのリストです。これから行われるプレゼンテーションについてはmicroformats関連の[[events|イベント]]をチェックしてください。他にも音声やビデオによるプレゼンテーションやディスカッションを記録したmicroformatsの[[podcasts|ポッドキャスト]]や[[screencasts|スクリーンキャスト]]があります。

最近行われたプレゼンテーションやセッションから順に並べています。

== 2006 ==
* August 26th, Tantek Çelik led the [http://barcamp.org/BarCampStanfordMicroformats BarCampStanfordMicroformats] discussion at room 426, Margaret Jacks Hall, Stanford, CA 94305. There is an [http://barcamp.org/f/MF-barcamp_08_26_2006.ogg Ogg recording of the session].
* July 11th, [http://tantek.com/presentations/2006/07/what-are-microformats/ What are microformats?] at [[events/2006-07-11-an-event-apart-microformats|An Event Apart in New York City]]
* July 6th, [http://yatil.de/webmontag/ka0706/ Mikroformate Erweiterte Semantik von HTML-Dokumenten] (Präsentation von Eric Eggert) Web mondays presentation in german - translation is available here
* June 15th, Phil Wilson presented to the [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ Institutional Web Management Workshop]
* June 8, Pete Prodoehl presented [http://rasterweb.net/raster/presentations/microformats-20060608/ Microformats] to the Milwaukee Web Design Meetup Group
* May 30, [http://netsquared.org NetSquared] [http://netsquared.org/conference/ Conference], 4:15pm-5:10pm: : [http://netsquared.org/conference/conference-sessions/Mashups A web more woven - the alchemy and practicalities of Mashups]. Tantek Çelik, Taylor McKnight and Chris Messina will discuss the core utility of microformats to publish and share data for/with mashups and other applications. Location: Jordan room, Cisco Systems' Vineyard Conference Center, 260 E. Tasman Drive, San Jose, CA.
* May 25, Brian Suda and Ryan King presented [http://theryanking.com/presentations/2006/www/ Practical Microformats] at WWW 2006 ([http://www.molly.com Molly Holzschlag] was orginally scheduled to give this talk, we filled in at the last minute with our slides from XTech)
* May 24, Kevin Lawver presented [http://presentations.lawver.net/standards/a_microformat_and_proposal_for/ A Microformat and Proposal For Interoperable Widgets]
* May 18, [http://xtech06.usefulinc.com/schedule/paper/148 The Intelligent Design of Microformats] by Ryan King at XTech 2006. ([http://theryanking.com/presentations/2006/xtech/talk/ slides]).
* May 16, [http://thebigjc.org/articles/2006/05/16/is-web-2-0-changing-the-software-industry Is Web 2.0 Changing the Software Industry?] by Chris Messina at [http://meshconference.com Mesh Conference]
* May 16, [http://theryanking.com/presentations/2006/xtech/tutorial/ Microformats from the Ground Up] by Brian Suda and Ryan King @ XTech 2006
* April 25, At [http://barcamp.org/TorCampDemoCamp5 DemoCamp #5 in Toronto], [http://blog.davidjanes.com David Janes] demonstrated [http://www.blogmatrix.com/ BlogMatrix] his platform for publish which supports microformats. (see [http://accordionguy.blogware.com/blog/_archives/2006/4/26/1913279.html Accordionguy blogpost]).
* April 23, [http://jazkarta.com/presentations/microformats.pdf/view Microformats and the Future of Syndication] by Nate Aune, AdaptiveWave (CM Pros Summit, San Francisco, CA)
* April 22, Intro to Microformats, [http://barcamp.pbwiki.com/BarCampBangalore Barcamp Bangalore], Bangalore, India, (photos [http://flickr.com/photos/abgpt/133393564/ 1], [http://flickr.com/photos/abgpt/133393545/ 2], [http://flickr.com/photos/abgpt/133393626/ 3])
* March 16, [http://ono.cdlib.org/archives/shimenawa/000219.html Reading 2.0] (see [http://radar.oreilly.com/archives/2006/03/link_list_reading_20_1.html Tim O'Reilly's notes]), San Francisco, CA
** Building with MicroFormats, [http://www.chaddickerson.com/blog/2006/03/17/reading-20-and-microformats/ Chad Dickerson], Yahoo
* March 13, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX
** [[events/2006-03-13-sxsw-microformats|Microformats: Evolving the Web]], 11:30am-12:30pm
* March 11, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX
** [http://tantek.com/presentations/2006/03/building-blocks Creating Building Blocks For Independents], 5pm-6pm
** [http://flickr.com/photos/tags/microformatssxsw photos]
* March 7, O'Reilly Emerging Technologies (ETech) Conference, Manchester Grand Hyatt, Ballroom, San Diego, CA
** [[events/2006-03-07-etech-microformats|Microformats intro and lightning demos at O'Reilly ETech conf.]], 5:30pm-6:15pm
** [http://flickr.com/photos/tags/microformatsetech photos]
* March 1, W3C Technical Plenary Day, Hotel Sofitel Cannes Mandelieu Royal Casino, main auditorium, 605 avenuedu Général de Gaulle, BP 49, MANDELIEU LA NAPOULE CEDEX, 06212 MANDELIEU LA NAPOULE, FRANCE
** [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Technical Plenary Day]], 10:30am-11:30am
*** Ian Hickson (Google) - "A billion documents and no semantics anywhere" (NEED LINK TO SLIDES OR STUDY)
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2006/03/what-are-microformats/ What are microformats?]"
*** Håkon Wium Lie (Opera) - "Cascading Markup Languages — boom!" (NEED LINK TO SLIDES)
*** Rohit Khare (CommerceNet) - "[http://labs.commerce.net/~rohit/Angstro-W3C-TP/ Where Angle Brackets Fear to Tread]"
*** Dan Connolly (W3C) - "[http://www.w3.org/2003/g/talk62/slides Microformats for practical Semantic Web deployment]"
*** Q&A
**** "I'm very excited about '''microformats'''. What I really want is to get all the data out of databases and expressed as part of the Semantic Web." - Tim Berners-Lee. ('''emphasis''' added)
** "Services and the Web" by Mark Nottingham (Yahoo), 12:05pm-12:10pm.
*** Request to W3T/W3M: Go After The "Real" Web: Apache, PHP, Mozilla, Intermediaries and Caches, '''Microformats''', JSON... ('''emphasis''' added)
** Attendees voted the "Microformats" session the best session of the Plenary Day. 6:17pm.
* February 24, Yahoo Speakers Series, Yahoo Mission College Campus, 2nd floor conference room, 2821 Mission College Blvd., Santa Clara, CA 95054
** [http://tantek.com/presentations/2006/02/microformats-evolution/ Microformats: Evolving the Web]
* January 18, Apple Web Publishers internal meeting, Apple Computer, Star Trek conference room, 1 Infinite Loop, Cupertino, CA 95014, 12-1:40pm
** [http://tantek.com/presentations/2006/01/microformats-evolution/ Microformats: Evolving the Web]
* January 10, SD Forum Emerging Technologies SIG, Room H1, Cubberley Community Center, Palo Alto, CA, 7-9pm
** Ryan King's presentation, Ernie Prabhakar's presentation, Rohit Khare's presentation
** Microformats panel: Ryan King, Ernie Prabhakar, Rohit Khare, Tantek Çelik, Kevin Marks

== 2005 ==
* December 15, Syndicate Conference, San Francisco, CA
** [http://tantek.com/presentations/2005/12/syndicate-microformats/ Microformats - Emerging syndication types]
* November 26, [http://barcamp.org/index.cgi?TorCamp TorCamp], Teehan+Lax, 460 Richmond St. W, Toronto, ON, CA
** [http://www.davidjanes.com/docs/2005.11.25%20Microformats%20Presentation.ppt powerpoints] (sorry)
** [http://blog.davidjanes.com/mtarchives/2005_12.html#003467 photo]
* November 12, THINK Conference, Santa Cruz room, Chaminade hotel, Santa Cruz, CA, USA
** [[presentation-think-2005-11-12]]
* November 10, (location unknown), by Kevin Yank of SitePoint Pty. Ltd.
** [http://www.sitepoint.com/examples/innovation-on-standards/ Innovating on top of standards - Not around them]
* October 5, [http://web2con.com Web 2.0 Conference], Olympic Room, Argent Hotel, San Francisco, CA, USA
** [http://tantek.com/presentations/2005/10/microformats-examples/ Microformats Examples]
* October 4, [http://osafoundation.org/ OSAF], San Francisco, CA, USA
** [http://tantek.com/presentations/2005/10/microformats-evolution/ Microformats: Evolving the Web]
* September 30, [http://we05.com/ Web Essentials 05], Guthrie auditorium, University of Technology, Sydney, Australia
** [http://tantek.com/presentations/2005/09/microformats-evolution/ Microformats: Evolving the Web] ([http://we05.com/podcast/mp3/we05-14-tantek-celik2.mp3 MP3 - incomplete])
* September 29, [http://we05.com/ Web Essentials 05], Guthrie auditorium, University of Technology, Sydney, Australia
** [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] ([http://we05.com/podcast/mp3/we05-2-tantek-celik.mp3 MP3])
* September 25, [http://webzine2005.com/ Webzine 2005], Valhalla Room, Swedish American Hall, San Francisco, CA, USA
** [http://theryanking.com/presentations/2005/webzine/ Microformats @ Webzine 2005]
* September 21, Web Intelligence Conference, Compiegne, France
** [http://moloko.itc.it/paoloblog/presentations/presentation_wi05/presentation_wi05.html Page-reRank: using trusted links to re-rank authority] ([http://sra.itc.it/people/massa/publications/wi05_page_rerank_massa_hayes.pdf paper]) - A discussion of using [[vote-links]] to improve [http://www-db.stanford.edu/~backrub/google.html PageRank]
* June 20: Supernova 2005 ([http://supernova2005.com/ Supernova2005 site]), Microformats [http://supernova2005.com/workshops.htm Workshop], Wharton West, Suite 500, San Francisco, CA, USA
** "[http://tantek.com/presentations/2005/06/what-are-microformats/ What are Microformats?]"
** "[http://homepage.mac.com/kevinmarks/supernovatags.html A microformat for tags]"
** [http://wiki.commerce.net/wiki/ZCommerceWS#Microformats commercenet wiki page on the workshop] ([http://labs.commerce.net/wiki/index.php/ZCommerceWS#Microformats 2])
* May 14: Fourteenth International World Wide Web Conference ([http://www2005.org/ WWW2005]), 2005, Microformats Dev-Day Track, Makuhari Messe Room 303, Chiba, JAPAN
** "[http://tantek.com/presentations/2005/05/what-are-microformats/ What are Microformats?]"
** "[http://westciv.com/WWW2005/linkmf.html Link Microformats]"
** "[http://complexspiral.com/events/archive/2005/www2005/potential.html The Potential of Microformats]"
** "Distributed Social Networks (XFN Implementations)"
*** Demonstrations of [http://wordpress.org WordPress] & [http://metafilter.com Metafilter]'s builtin XFN support, and XFN search engines [http://rubhub.com/ RubHub] & [http://xhtmlfriends.net/ xhtmlfriends.net].
** "[http://tantek.com/presentations/2005/05/hcard-hcalendar/ People and Events (hCard & hCalendar)]"
** "[http://cnlabs.commerce.net/~rohit/hReview-in-Review/ hReview in Review]"
** "Bibliographies ([''hbib'')"
** "[http://westciv.com/WWW2005/xml2mf.html a more meaningful web with microformats]"
** "Semantic Web and Microformats" panel, Room 201

* March 15: "[http://tantek.com/presentations/2005/03/decentralizednetworks/ Decentralized Social Networks]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 17AB, Austin TX

* March 14: "[http://2005.sxsw.com/interactive/conference/panels/?action=show&id=IAP0060 How to Trick-Out Your Blog]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 16B, Austin TX

* March 13
** "[http://complexspiral.com/events/archive/2005/sxsw/ Emergent Semantics]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 15, Austin TX
** "[http://tantek.com/presentations/2005/03/leveragingtags.html Leveraging Tags]", as part of the "How to Leverage Solipsism" panel, South by South West Conference (SXSW) 2005, Austin Convention Center Room 18A, Austin TX
** "[http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 16B, Austin TX

* January 21: [http://tantek.com/presentations/2005/01/attentionxml.html Attention.xml Technology Overview], private presentation, Yahoo! campus, Santa Clara, CA

== 2004 ==

* September 28: "[http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean]", SD Forum Web Services SIG, eBay's Silicon Valley Conference Center 2161 North First Street San Jose, CA 95131

* September 12: "[http://wiki.oreillynet.com/foocamp04/index.cgi?MVCeqXHTMLCSSJS Model+View+Controller = XHTML+CSS+JS]", O'Reilly Media Foo Camp 2004, O'Reilly Campus, Wallcreeper room, Sebastopol CA

* September 11: "[http://wiki.oreillynet.com/foocamp04/index.cgi?AttentionXML Attention.XML]", O'Reilly Media Foo Camp 2004, O'Reilly Campus, Appaloosa room, Sebastopol CA

* September 10: "[http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats Simple Semantic Formats]", O'Reilly Media Foo Camp 2004, O'Reilly Campus, Camel room, Sebastopol CA

* March 15: "[http://tantek.com/presentations/2004sxsw/xfn.html Ridiculously Easy Social Software]", South by South West Conference (SXSW) 2004, Austin Convention Center Room 17B, Austin TX

* February 11th: "[http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics]", O'Reilly Emerging Technology Conference (ETech) 2004 Westin Horton Plaza, San Diego, CA. This presentation was the first public discussion and introduction of the terms "microformat" and "lowercase semantic web". Reprised as a five-minute lightning talk at [http://wiki.oreillynet.com/etech/index.cgi?ConCon ConCon], Rx Gallery, San Francisco CA (16 February 2004).

This page was contributed from [http://developers.technorati.com/wiki/MicroFormatsPresentations the Technorati developers wiki].

hcalendar-ja

2008-12-20T09:20:36Z

Hr.takahashi: Undo revision 35760 by CoracBasol (Talk)

<h1>hCalendar</h1>
http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

hCalendarはiCalendar ([http://www.ietf.org/rfc/rfc2445.txt RFC2445])を基とした、シンプルでオープンなカレンダー・イベント情報配信用の[[microformats-ja|microformat]]です。(X)HTMLやAtom, RSS, 任意のXMLなど、広範囲に適用可能なフォーマットとなっています。

hCalendarでイベント情報を配信するにはいくつかの方法があります。手っ取り早いのは、「[http://microformats.org/code/hcalendar/creator hCalendar クリエーター]」ツールを使うこと。でももし、すでにイベントの情報を自分のブログやwikiなどに書いている場合は、[[hcalendar-authoring|hCalendarを書くコツ]]を読み、hCalendarに沿うようマークアップをし直しましょう。

__TOC__

== 仕様 ==

; 編者 : [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])
; 作者 : [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]
: [http://suda.co.uk/ Brian Suda]

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

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

=== 謝辞 ===
以下の方に感謝します。
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOOキャンプ 2004の「カレンダー表示のためのHTML」]を先導してくれた、アダム・ブロスウォース。このおかげでhCalendarへの関心が本格的な者になりました。

== 概要 ==
iCalendar ([http://www.ietf.org/rfc/rfc2445.txt RFC2445])はAppleのiCalなど、スケジュール管理用アプリケーションに広く採用され、また実装上の相互運用性も高いフォーマットになっています。

この広く使われているフォーマットを、ブログで言及されるイベント情報に応用できないでしょうか。今後行われるイベントや、これまでに参加したイベントについて自分のブログ上に記事を書くブロガーはたくさんいます。それらのイベント情報を少し構造化し、iCalendarとして出力可能にすれば、アプリケーションやWebサービスが自動的にその情報を利用できるようになります。

この'''hCalendar'''という仕様は、XHTMLによってiCalendarを表現する書式です。ブロガーはhCalendarを直接webページに埋め込んだり、またその情報をCSSでデザインすることが可能です。それだけではありません。アプリケーションはイベント情報を直接そのhCalendarから取ってくることができるようになります。イベントについて書かれたファイルを、webページと別に用意する必要はもうありません。

== セマンティックXHTMLデザイン指針 ==

{{semantic-xhtml-design-principles}}

実用的な導入を考えた場合、Internet Explorerでは <code><nowiki><abbr></nowiki></code> 要素のCSSスタイリングがきちんとサポートされていないため、別の追加要素が必要になることがあるのを覚えておくと良いでしょう。

== 書式 ==

=== 通例 ===

iCalendar 標準規約（[http://www.ietf.org/rfc/rfc2445.txt RFC2445]）がhCalendarのもととなっています。

注意：この仕様書の編集者および執筆者は、[http://lists.osafoundation.org/pipermail/ietf-calsify/ 「iCal-Basic」の取り組み]を追い、 hCalendarのコア・プロファイルを iCal-Basic に基づいたものにしようとしています。リンク先にある現在の草稿をご覧ください。

hCalendarの基本的な書式は、iCalendarのオブジェクトおよび変数名をclass名として小文字で書くようにしたものです。また、iCalendarの入れ子方式に配置されたオブジェクトを、そのまま入れ子方式のXHTMLにマッピングします。

=== More Semantic Equivalents ===

However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <code>URL</code> in iCalendar becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vevent"</code> in hCalendar.
* <code>ATTENDEE</code>, <code>CONTACT</code>, and <code>ORGANIZER</code> in iCalendar may be represented by an [[hcard|hCard]] in hCalendar .
* A named <code>LOCATION</code> (potentially with an address and/or geo) in iCalendar may be represented by a nested [[hcard|hCard]] in hCalendar. Similarly, an address <code>LOCATION</code> may be represented by an [[adr]], and a geo (latitude and longitude) <code>LOCATION</code> may be represented by a [[geo]].
* <code>UID</code> in iCalendar simply becomes another semantic applied to a specific URL for an hCalendar event.

=== Singular vs. Plural Properties ===

For properties which are singular (e.g. "N" and "FN" from vCard), the first descendant element with that class should take effect, any others being ignored.

For properties which can be plural (e.g. "TEL" from vCard), each class instance should create a instance of that property. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL from vCard) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===
If an <code><nowiki><abbr></nowiki></code> element is used for a property, then the '<code>title</code>' attribute of the <code><nowiki><abbr></nowiki></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value. This specification recommends that such <code><nowiki><abbr></nowiki></code> elements be used for the following iCalendar properties:
* DTSTART, DTEND, DURATION, RDATE, RRULE

== 例 ==

以下は、iCalendarの例です。
<pre><nowiki>
BEGIN:VCALENDAR
PRODID:-//XYZproduct//EN
VERSION:2.0
BEGIN:VEVENT
URL:http://www.web2con.com/
DTSTART:20071005
DTEND:20071020
SUMMARY:Web 2.0 カンファレンス
LOCATION:アージェントホテル\, サンフランシスコ\, カリフォルニア州
END:VEVENT
END:VCALENDAR
</nowiki></pre>

hCalendar書式で同様のイベントを表示する場合、各種要素が最適化され、以下のようになります。元になった内容については、[[hcalendar-example1-steps]]をご覧ください。

<pre><nowiki>
<div class="vevent">
<a class="url" href="http://www.web2con.com/">http://www.web2con.com/</a>
Web 2.0 カンファレンス ：
<abbr class="dtstart" title="2007-10-05">10月5日</abbr>〜
<abbr class="dtend" title="2007-10-20">19日</abbr>、
アージェントホテル（カリフォルニア州サンフランシスコ）にて。
</div>
</nowiki></pre>

これは、以下のように表示されます。

<div class="vevent">
http://www.web2con.com/ 
Web 2.0 カンファレンス ：
<abbr class="dtstart" title="2007-10-05">10月5日</abbr>〜
<abbr class="dtend" title="2007-10-20"> 19日 </abbr>、 アージェントホテル（カリフォルニア州サンフランシスコ）にて。
</div>

これは、'''本物''の'hCalendarマイクロフォーマットであり、パーサーがこのページ内から検出できることに注意してください。

=== Example 2===

The following example specifies a scheduled meeting that begins
at 8:30 AM EST on March 12, 1998 and ends at 9:30 AM EST on March 12,
1998.

<pre><nowiki>
BEGIN:VCALENDAR
BEGIN:VEVENT
UID:guid-1.host1.com
DTSTAMP:19980309T231000Z
DESCRIPTION:Project XYZ Review Meeting
SUMMARY:XYZ Project Review
DTSTART:19980312T133000Z
DTEND:19980312T143000Z
LOCATION:1CP Conference Room 4350
END:VEVENT
END:VCALENDAR
</nowiki></pre>

The equivalent in hCalendar:

<pre><nowiki>
<div class="vevent">
<h3 class="summary">XYZ Project Review</h3>
Project XYZ Review Meeting
To held on <abbr class="dtstart" title="1998-03-12T08:30:00-05:00">12 March 1998 from 8:30am EST</abbr>
until <abbr class="dtend" title="1998-03-12T09:30:00-05:00">9:30am EST</abbr>
Location: 1CP Conference Room 4350
Booked by: guid-1.host1.com on
<abbr class="dtstamp" title="19980309T231000Z">9 Mar 1998 6:00pm</abbr>
</div>
</nowiki></pre>

This could be displayed as:

----

<div class="vevent">

<h3 class="summary">XYZ Project Review</h3>
Project XYZ Review Meeting
To held on <abbr class="dtstart" title="1998-03-12T08:30:00-05:00">12 March 1998 from 8:30am EST</abbr>
until <abbr class="dtend" title="1998-03-12T09:30:00-05:00">9:30am EST</abbr>
Location: 1CP Conference Room 4350
Booked by: guid-1.host1.com on
<abbr class="dtstamp" title="19980309T231000Z">9 Mar 1998 6:00pm</abbr></div>

----

Note 1: The product information is not necessary since hCalendar is an interchange format. When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.

Note 2: A surrounding <code><nowiki></nowiki></code> element is optional, and is left out as such. It is optional since the context of a vcalendar is implied when a vevent is encountered. The implied context/scope is that of the document. Authors may explicitly use elements with class="vcalendar" to wrap sets of vevents that all belong to the same calendar, e.g. when publishing multiple calendars on the same page.

Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.

Note 4: ISO8601 dates (required by iCalendar) are not very human friendly. In addition, the year is often understood implicitly by humans from the context. Thus <code><nowiki><abbr></nowiki></code> elements are used to simultaneously provide a human friendly date and/or time in the visible contents of the element, while placing the respective machine parsable comprehensive ISO8601 datetime in the 'title' attribute.
The notation <code>YYYY-MM-DDThh:mm:ss</code> should be used for better readability, following the format of RFC 3339.

Note 5: The difference between the DTEND ISO8601 date (2005-10-08) and the human readable date (7) is NOT a mistake. [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive], meaning, that the event ends just before the DTEND. Thus for events which start on one day and end on another day, the DTEND date must be specified as the day after the day that a human would say is the last day of the event.

Note 6: The location in this example contains implicit structure (venue name, city, state) which could be marked up explicitly as an [[hcard|hCard]]. See [http://microformats.org/wiki/hcalendar-brainstorming#hCard_locations hCalendar brainstorming: hCard locations] for a informative explanation of how to do this.

==Buttons==
Don't forget that you can add one of our [[buttons#hCalendar|buttons]] to the page, to indicate the presence of hCalendar microformats. For example: http://www.boogdesign.com/images/buttons/microformat_hcalendar.png. If you can link it back to this page (or even page on your website, about your use of the microformat), so much the better!

=== More Examples ===
See [[hcalendar-examples|hCalendar examples]] for more examples, including examples from iCalendar RFC 2445 converted into hCalendar.

== Examples in the wild ==
This section is '''informative'''. The number of hCalendar examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hcalendar-examples-in-wild|separate page]].

See [[hcalendar-examples-in-wild|hCalendar Examples in the wild]].

== Implementations ==
This section is '''informative'''. The number of hCalendar implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hcalendar-implementations|separate page]].

See [[hcalendar-implementations|hCalendar Implementations]].

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [[hcard|hCard]]
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]

=== Informative References ===
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcalendar hCalendar term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* [http://ietfreport.isoc.org/idref/draft-royer-ical-basic/ iCal-Basic (latest)] [http://www.faqs.org/ftp/pub/pub/internet-drafts/draft-royer-ical-basic-04.txt (draft 04)]
* Contributed from http://developers.technorati.com/wiki/hCalendar
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]
* [http://www.imc.org/pdi/ Internet Mail Consortium Personal Data Interchange vCard and vCalendar]

==== Specifications That Use hCalendar ====
* [[hreview|hReview]]

==== Similar Work ====
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]

== Further Reading ==
* [http://www.jwz.org/doc/groupware.html Groupware Bad by Jamie Zawinski] crystalizes the reason for hCalendar ('''emphasis''' added):
<blockquote>Right now people can do that by publishing .ics files, but it's not trivial to do so, and it's work on the part of other people to look at them. '''If it's not HTML hanging off our friend's home page that can be viewed in any browser on a public terminal in a library, the bar to entry is too high and it's useless.'''</blockquote>

* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]
* [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcalendar hCalendar tag]
* [http://en.wikipedia.org/wiki/HCalendar Wikipedia article on hCalendar] (requires expansion)

== Related Pages ==
{{hcalendar-related-pages}}

rel-nofollow-ja

2008-12-20T09:18:17Z

Hr.takahashi: Undo revision 36058 by BasliRicpa (Talk)

= rel="nofollow" =
__TOC__

== 2005-01-10版 ==

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

=== 原案 ===
* [http://www.google.com/googleblog/ Matt Cutts] ([http://google.com Google, Inc])
* [http://www.shellen.com/ Jason Shellen] ([http://www.blogger.com Blogger]/[http://www.google.com Google])

=== 著作権 ===
{{MicroFormatCopyrightStatement2005}}
* [[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}}

== 概要 ==
rel-nofollowは[[microformats-ja|microformats]]のひとつで、[[elemental-microformat|単純microformat]]に属するものです。<code>rel="nofollow"</code>をハイパーリンクに加えることで、検索エンジンなどリンクを解析するユーザーエージェントが、リンク先を重み付けやランキングの指標として用いないようにします。ユースケースとして、第三者がblogにつけたコメントや、作者が推奨はしないもののリンクしておきたいものがあります。より詳しく賛成や反対の意味づけを行いたい場合は、[[vote-links|VoteLinks]]をご覧ください。

== XMDPプロファイル==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.
<dl>
<dt id="nofollow">nofollow</dt>
<dd>Indicates that the referred resource was not necessarily linked to
by the author of the page, and thus said reference should not afford
the referred resource any additional weight or ranking by user agents. </dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== 規範的な情報 ==
* [http://gmpg.org/xmdp/ XMDP]
* http://googleblog.blogspot.com/2005/01/preventing-comment-spam.html

== 参考情報 ==
*リンク先の文書について、賛成や反対を表したい場合には、[[vote-links|VoteLinks]]を用います。rel-nofollowとVoteLinksを実装する方は、<code>rev="vote-abstain"</code>や<code>rev="vote-against"</code>などの値を、重み付けやランキングに用いないようにしてください。
* このフォーマットは、http://developers.technorati.com/wiki/RelNoFollow からの寄稿です。

== 未解決の問題 ==
rel-nofollowに関し、[http://lists.w3.org/Archives/Public/www-html W3C www-html メーリングリスト]をはじめいくつかのフォーラムから問題提起がなされています。問題は、大きく4つのカテゴリに分けられます。

* '''定義''' - nofollowは関係よりも、ユーザーエージェントが取るべき挙動の指定を意味するように感じる。relの値はソースとリンク先の関係を表す名詞であるべきだ。
* '''名前''' - nofollow はよい名前ではない。
** 車輪の再発明だ。他のロボットよけ仕様 (robots.txt, meta robots) と変わりない。
** 名前ががきちんと目的を説明していない。「このリンクをたどるな」ではなく「このリンクに重み付けを行うな」であるべきだ。[http://www.w3.org/mid/opsk3cccj9lo81gp@quark Asbjørn Ulsberg]
** 名詞ではない。
** 代替案:
*** noendorse - [http://lists.w3.org/Archives/Public/www-html/2005Jan/0046.html Micah Dubinko]
*** none
*** noweight
*** unendorsed - [http://lists.w3.org/Archives/Public/www-html/2005Jan/0057.html Lachlan Hunt]
*** unrelated - [http://lists.w3.org/Archives/Public/www-html/2005Jan/0049.html Jens Meiert]
*** untrusted
*** nonauth - [http://www.mnot.net/blog/2003/12/29/comment_spam_and_google Mark Baker]
*** norank - [http://www.digitalburg.com/ Ben Pierce]
* '''有効性''' - nofollowはspamに対し効果がない。
* '''巻き添え''' - ツールが自動的に第三者からのリンクにnofollowをつけた場合、spamではない正当なリンクが無視されたり、重み付けを行われなくなる。その結果、そのリンク先において、あまり良くない事が起こる可能性がある。

=== その他の問題 ===
rel-nofollowに関し述べられている問題は、次のサイトでも見つけることが出来ます。
* http://www.nonofollow.net/

vote-links-ja

2008-12-20T09:16:36Z

Hr.takahashi: Undo revision 35734 by LiorbOclet (Talk)

= 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><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.
<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]]に関して、いくつかの提案があります。