http://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=SevenovaMicroformats Wiki - User contributions [en]2026-04-14T22:15:57ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=xoxo-id&diff=40724xoxo-id2009-09-06T12:06:53Z<p>Sevenova: /* Sample Code */</p>
<hr />
<div><entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title><br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Contoh Kode ===<br />
<br />
* Lihat halaman [[xoxo-sample-code]] untuk contoh kode open source untuk membaca dan menulis berkas XOXO.<br />
* Lihat juga halaman [[xoxo-compact-sample]] dengan sumber untuk CSS dan JS yang mengubah tampilan dan nuansa XOXO yang sangat polos agar memiliki segitiga twiddlable untuk sekumpulan daftar yang menghargai attribut dengan baik.<br />
<br />
== Skema XOXO ==<br />
Bagian ini adalah informatif.<br />
<br />
Catatan: mungkin sudah usang dan perlu diperbaharui untuk mencerminkan penggunaan &lt;dl&gt; untuk membubuhi keterangan tiap-tiap XOXO dengan properti secara acak.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Skema (Relax NG dan DTDs)]<br />
<br />
== Referensi ==<br />
=== Referensi yang normatif ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Referensi yang Informatif ===<br />
Bagian ini adalah '''informatif'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Kontribusi dari http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Bacaan yang terkait ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan menuliskan Mengapa kedua ekstensi OPML dan Microsoft Lists extension tidak diperlukan].<br />
<br />
=== Bacaan yang tidak terkait ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - ternyata karakter Faye adalah penggemar XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Tanya Jawab ===<br />
* Jika Anda memiliki pertanyaan seputar XOXO, silahkan kunjungi [[xoxo-faq]] dan jika Anda tidak menemukan jawabannya, tambahkan pertanyaan Anda pada halaman tersebut.<br />
<br />
=== Isu ===<br />
* Silahkan menambahkan isu dengan spesifikasi apapun ke dokumen terpisah [[xoxo-issues]].<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=xoxo-id&diff=40723xoxo-id2009-09-06T11:57:57Z<p>Sevenova: /* XOXO Schemas */</p>
<hr />
<div><entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title><br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Sample Code ===<br />
<br />
* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.<br />
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.<br />
<br />
== Skema XOXO ==<br />
Bagian ini adalah informatif.<br />
<br />
Catatan: mungkin sudah usang dan perlu diperbaharui untuk mencerminkan penggunaan &lt;dl&gt; untuk membubuhi keterangan tiap-tiap XOXO dengan properti secara acak.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Skema (Relax NG dan DTDs)]<br />
<br />
== Referensi ==<br />
=== Referensi yang normatif ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Referensi yang Informatif ===<br />
Bagian ini adalah '''informatif'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Kontribusi dari http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Bacaan yang terkait ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan menuliskan Mengapa kedua ekstensi OPML dan Microsoft Lists extension tidak diperlukan].<br />
<br />
=== Bacaan yang tidak terkait ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - ternyata karakter Faye adalah penggemar XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Tanya Jawab ===<br />
* Jika Anda memiliki pertanyaan seputar XOXO, silahkan kunjungi [[xoxo-faq]] dan jika Anda tidak menemukan jawabannya, tambahkan pertanyaan Anda pada halaman tersebut.<br />
<br />
=== Isu ===<br />
* Silahkan menambahkan isu dengan spesifikasi apapun ke dokumen terpisah [[xoxo-issues]].<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=xoxo-id&diff=40722xoxo-id2009-09-06T11:51:51Z<p>Sevenova: /* References */</p>
<hr />
<div><entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title><br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Sample Code ===<br />
<br />
* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.<br />
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.<br />
<br />
== XOXO Schemas ==<br />
This section is informative.<br />
<br />
Note: these may be out of date and require updating to reflect the use of &lt;dl&gt; for annotating XOXO items with arbitrary properties.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]<br />
<br />
<br />
== Referensi ==<br />
=== Referensi yang normatif ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Referensi yang Informatif ===<br />
Bagian ini adalah '''informatif'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Kontribusi dari http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Bacaan yang terkait ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan menuliskan Mengapa kedua ekstensi OPML dan Microsoft Lists extension tidak diperlukan].<br />
<br />
=== Bacaan yang tidak terkait ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - ternyata karakter Faye adalah penggemar XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Tanya Jawab ===<br />
* Jika Anda memiliki pertanyaan seputar XOXO, silahkan kunjungi [[xoxo-faq]] dan jika Anda tidak menemukan jawabannya, tambahkan pertanyaan Anda pada halaman tersebut.<br />
<br />
=== Isu ===<br />
* Silahkan menambahkan isu dengan spesifikasi apapun ke dokumen terpisah [[xoxo-issues]].<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=xoxo-id&diff=40721xoxo-id2009-09-06T11:51:29Z<p>Sevenova: /* Normative References */</p>
<hr />
<div><entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title><br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Sample Code ===<br />
<br />
* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.<br />
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.<br />
<br />
== XOXO Schemas ==<br />
This section is informative.<br />
<br />
Note: these may be out of date and require updating to reflect the use of &lt;dl&gt; for annotating XOXO items with arbitrary properties.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]<br />
<br />
<br />
== References ==<br />
=== Referensi yang normatif ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Referensi yang Informatif ===<br />
Bagian ini adalah '''informatif'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Kontribusi dari http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Bacaan yang terkait ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan menuliskan Mengapa kedua ekstensi OPML dan Microsoft Lists extension tidak diperlukan].<br />
<br />
=== Bacaan yang tidak terkait ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - ternyata karakter Faye adalah penggemar XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Tanya Jawab ===<br />
* Jika Anda memiliki pertanyaan seputar XOXO, silahkan kunjungi [[xoxo-faq]] dan jika Anda tidak menemukan jawabannya, tambahkan pertanyaan Anda pada halaman tersebut.<br />
<br />
=== Isu ===<br />
* Silahkan menambahkan isu dengan spesifikasi apapun ke dokumen terpisah [[xoxo-issues]].<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=xoxo-id&diff=40720xoxo-id2009-09-06T11:49:33Z<p>Sevenova: /* Informative References */</p>
<hr />
<div><entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title><br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Sample Code ===<br />
<br />
* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.<br />
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.<br />
<br />
== XOXO Schemas ==<br />
This section is informative.<br />
<br />
Note: these may be out of date and require updating to reflect the use of &lt;dl&gt; for annotating XOXO items with arbitrary properties.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]<br />
<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Referensi yang Informatif ===<br />
Bagian ini adalah '''informatif'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Kontribusi dari http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Bacaan yang terkait ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan menuliskan Mengapa kedua ekstensi OPML dan Microsoft Lists extension tidak diperlukan].<br />
<br />
=== Bacaan yang tidak terkait ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - ternyata karakter Faye adalah penggemar XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Tanya Jawab ===<br />
* Jika Anda memiliki pertanyaan seputar XOXO, silahkan kunjungi [[xoxo-faq]] dan jika Anda tidak menemukan jawabannya, tambahkan pertanyaan Anda pada halaman tersebut.<br />
<br />
=== Isu ===<br />
* Silahkan menambahkan isu dengan spesifikasi apapun ke dokumen terpisah [[xoxo-issues]].<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=xoxo-id&diff=40719xoxo-id2009-09-06T11:48:16Z<p>Sevenova: /* Related Reading */</p>
<hr />
<div><entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title><br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Sample Code ===<br />
<br />
* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.<br />
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.<br />
<br />
== XOXO Schemas ==<br />
This section is informative.<br />
<br />
Note: these may be out of date and require updating to reflect the use of &lt;dl&gt; for annotating XOXO items with arbitrary properties.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]<br />
<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Informative References ===<br />
This section is '''informative'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Contributed from http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Bacaan yang terkait ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan menuliskan Mengapa kedua ekstensi OPML dan Microsoft Lists extension tidak diperlukan].<br />
<br />
=== Bacaan yang tidak terkait ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - ternyata karakter Faye adalah penggemar XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Tanya Jawab ===<br />
* Jika Anda memiliki pertanyaan seputar XOXO, silahkan kunjungi [[xoxo-faq]] dan jika Anda tidak menemukan jawabannya, tambahkan pertanyaan Anda pada halaman tersebut.<br />
<br />
=== Isu ===<br />
* Silahkan menambahkan isu dengan spesifikasi apapun ke dokumen terpisah [[xoxo-issues]].<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=xoxo-id&diff=40718xoxo-id2009-09-06T11:44:57Z<p>Sevenova: /* Unrelated Reading */</p>
<hr />
<div><entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title><br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Sample Code ===<br />
<br />
* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.<br />
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.<br />
<br />
== XOXO Schemas ==<br />
This section is informative.<br />
<br />
Note: these may be out of date and require updating to reflect the use of &lt;dl&gt; for annotating XOXO items with arbitrary properties.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]<br />
<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Informative References ===<br />
This section is '''informative'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Contributed from http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Related Reading ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan on why OPML and a Microsoft Lists extension are both unnecessary].<br />
<br />
=== Bacaan yang tidak terkait ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - ternyata karakter Faye adalah penggemar XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Tanya Jawab ===<br />
* Jika Anda memiliki pertanyaan seputar XOXO, silahkan kunjungi [[xoxo-faq]] dan jika Anda tidak menemukan jawabannya, tambahkan pertanyaan Anda pada halaman tersebut.<br />
<br />
=== Isu ===<br />
* Silahkan menambahkan isu dengan spesifikasi apapun ke dokumen terpisah [[xoxo-issues]].<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=xoxo-id&diff=40717xoxo-id2009-09-06T11:38:50Z<p>Sevenova: /* Q&A */</p>
<hr />
<div><entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title><br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Sample Code ===<br />
<br />
* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.<br />
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.<br />
<br />
== XOXO Schemas ==<br />
This section is informative.<br />
<br />
Note: these may be out of date and require updating to reflect the use of &lt;dl&gt; for annotating XOXO items with arbitrary properties.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]<br />
<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Informative References ===<br />
This section is '''informative'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Contributed from http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Related Reading ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan on why OPML and a Microsoft Lists extension are both unnecessary].<br />
<br />
=== Unrelated Reading ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - apparently the Faye character is a fan of XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Tanya Jawab ===<br />
* Jika Anda memiliki pertanyaan seputar XOXO, silahkan kunjungi [[xoxo-faq]] dan jika Anda tidak menemukan jawabannya, tambahkan pertanyaan Anda pada halaman tersebut.<br />
<br />
=== Isu ===<br />
* Silahkan menambahkan isu dengan spesifikasi apapun ke dokumen terpisah [[xoxo-issues]].<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=xoxo-id&diff=40716xoxo-id2009-09-06T11:35:30Z<p>Sevenova: /* Issues */</p>
<hr />
<div><entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title><br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Sample Code ===<br />
<br />
* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.<br />
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.<br />
<br />
== XOXO Schemas ==<br />
This section is informative.<br />
<br />
Note: these may be out of date and require updating to reflect the use of &lt;dl&gt; for annotating XOXO items with arbitrary properties.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]<br />
<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Informative References ===<br />
This section is '''informative'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Contributed from http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Related Reading ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan on why OPML and a Microsoft Lists extension are both unnecessary].<br />
<br />
=== Unrelated Reading ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - apparently the Faye character is a fan of XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Q&A ===<br />
* If you have any questions about XOXO, check the [[xoxo-faq]], and if you don't find answers, add your questions!<br />
<br />
=== Isu ===<br />
* Silahkan menambahkan isu dengan spesifikasi apapun ke dokumen terpisah [[xoxo-issues]].<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=how-to-play-id&diff=40715how-to-play-id2009-09-06T11:17:41Z<p>Sevenova: /* Pedoman */</p>
<hr />
<div>__NOTOC__<br />
Jika ini kunjungan pertama Anda, harap membaca halaman [[introduction-id|pendahuluan]].<br />
<entry-title>Cara Penggunaan</entry-title><br />
== Pedoman ==<br />
Sebelum memulai kontribusi dimohon untuk mematuhi pedoman berikut:<br />
<br />
# Anda haru membuat akun sebelum melakukan penyuntingan/menambahkan halaman. Gunakan nama Anda dengan seksama, misalnya PemberianNama (Awal-Akhir), lihat juga [http://en.wikipedia.org/wiki/Wikipedia:Username panduan username Wikipedia]. Anda juga dipersilahkan menggunakan alias (misalnya [[User:Adactio]], [[User:Phae]]). Dimohon untuk tidak menggunakan nama organisasi atau kata benda (misalnya produk, teknologi).<br />
# Baca tentang [[:Category:public_domain_license|Deklarasi Domain Publik]] microformats.org dan silahkan menambah [[Template:cc-public-domain-release]] ke halaman pengguna Anda untuk melepaskan kontribusi Anda kepada microformats.org sebelum 2008 menjadi domain publik.<br />
# Coba terlebih dahulu [http://microformats.org/discuss kanal irc (lebih baik) atau mailing lists] (dan baca halaman [[mailing-lists]] sebelum melalukannya).<br />
# Jika Anda ingin menuliskan sebuah opini yang bukan alasan logis, tandai dengan username Anda - Anda juga dapat melakukannya dengan mudah dengan datetimestamp pada MediaWiki dengan empat tildes, contohnya: <nowiki>~~~~</nowiki> <br />
#* Pada beberapa kasus hal ini diperlukan ketika mengedit tanda tangan kontribusi lainnya (sebagai lawan dari konten umum), berhati-hatilah untuk tidak mengubah maknanya.<br />
#* Jika pernyataan alasan logis Anda adalah bagian dari diskusi dimana pernyataan tersebut tidak setuju dengan komentar sebelumnya, Anda dapat menandatanganinya dengan username Anda. Namun penandatanganan pernyataan seperti itu tidak diperlukan dan mungkin mengurangi alasan pernyataan logis berdiri sendiri (berkaitan: [[#avoid-personalizing-proposals|avoid personalizing proposals]]) dan dengan demikian dianggap meninggalkan pernyataan tersebut tanpa tanda tangan. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
<br />
# Please only create pages directly relating to [[POSH]], microformats (and [[picoformats]]) on this wiki. [[data-portability]] in line with microformats [[principles]] is also encouraged. Other pages will likely be deleted.<br />
# <span id="naming">Please obey the [[naming-conventions| naming conventions]] for pages. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span><br />
# Don't use talk pages. See #3. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Please try to ensure that you produce valid XHTML.<br />
# When you paste code, add some line breaks at a reasonable width.<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <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><br />
# Headings may be explicitly marked up with &lt;h1&gt; &lt;h2&gt; tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please <strong style="text-transform:uppercase">do not</strong> change them to "=" or "==" style headings. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. If you change a heading please leave a <code><nowiki><div id="oldheadingID"></div></nowiki></code> around the new heading with oldHeadingID set to the necessary value to maintain heading permalinks.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Start headings with a letter (or underscore a letter doesn't work), in order to generate valid ID attributes on heading elements.<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <span id="avoid-simple-contradictions">Please avoid simple contradictory responses</span> 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. 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>]<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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>]. Previously: Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Check "what links here" before moving pages, and fix any links to the page you're moving, if appropriate.<br />
# 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])]<br />
# Use [[rfc-2119#Templates|templates]] for RFC 2119 terms such as {{must}}.<br />
# 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].<br />
# 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.<br />
# 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>&lt;nowiki&gt;</code> tags, e.g.: <code><nowiki>&lt;nowiki&gt;http://example.org/&lt;/nowiki&gt;</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>.<br />
# 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>]<br />
# 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>]<br />
# <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>]<br />
# <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])]<br />
# 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])]<br />
# 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>]<br />
<br />
== Accessibility ==<br />
#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>.<br />
#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.<br />
<br />
== Membersihkan Wiki ==<br />
Kunjungi [[spam-removal]].<br />
<br />
If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list rather than doing it yourself. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
<br />
== Terkait ==<br />
* [[mediawiki-customization]] - 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]].<br />
* [[wiki2]]<br />
* [[wiki-better-than-email]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=how-to-play-id&diff=40669how-to-play-id2009-09-02T17:59:59Z<p>Sevenova: /* Pedoman */</p>
<hr />
<div>__NOTOC__<br />
Jika ini kunjungan pertama Anda, harap membaca halaman [[introduction-id|pendahuluan]].<br />
<entry-title>Cara Penggunaan</entry-title><br />
== Pedoman ==<br />
Sebelum memulai kontribusi dimohon untuk mematuhi pedoman berikut:<br />
<br />
# Anda haru membuat akun sebelum melakukan penyuntingan/menambahkan halaman. Gunakan nama Anda dengan seksama, misalnya PemberianNama (Awal-Akhir), lihat juga [http://en.wikipedia.org/wiki/Wikipedia:Username panduan username Wikipedia]. Anda juga dipersilahkan menggunakan alias (misalnya [[User:Adactio]], [[User:Phae]]). Dimohon untuk tidak menggunakan nama organisasi atau kata benda (misalnya produk, teknologi).<br />
# Baca tentang [[:Category:public_domain_license|Deklarasi Publik Domain]] microformats.org dan silahkan menambah [[Template:cc-public-domain-release]] ke halaman pengguna Anda untuk melepaskan kontribusi Anda kepada microformats.org sebelum 2008 menjadi domain publik.<br />
# Coba terlebih dahulu [http://microformats.org/discuss kanal irc (lebih baik) atau mailing lists] (dan baca halaman [[mailing-lists]] sebelum melalukannya).<br />
<br />
# If you write something more opinion rather than logically reasoned, sign it with your username - you can easily do so with a datetimestamp in MediaWiki with four tildes, e.g.: <nowiki>~~~~</nowiki>.<br />
#*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.<br />
#*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>]<br />
# Please only create pages directly relating to [[POSH]], microformats (and [[picoformats]]) on this wiki. [[data-portability]] in line with microformats [[principles]] is also encouraged. Other pages will likely be deleted.<br />
# <span id="naming">Please obey the [[naming-conventions| naming conventions]] for pages. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span><br />
# Don't use talk pages. See #3. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Please try to ensure that you produce valid XHTML.<br />
# When you paste code, add some line breaks at a reasonable width.<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <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><br />
# Headings may be explicitly marked up with &lt;h1&gt; &lt;h2&gt; tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please <strong style="text-transform:uppercase">do not</strong> change them to "=" or "==" style headings. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. If you change a heading please leave a <code><nowiki><div id="oldheadingID"></div></nowiki></code> around the new heading with oldHeadingID set to the necessary value to maintain heading permalinks.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Start headings with a letter (or underscore a letter doesn't work), in order to generate valid ID attributes on heading elements.<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <span id="avoid-simple-contradictions">Please avoid simple contradictory responses</span> 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. 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>]<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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>]. Previously: Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Check "what links here" before moving pages, and fix any links to the page you're moving, if appropriate.<br />
# 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])]<br />
# Use [[rfc-2119#Templates|templates]] for RFC 2119 terms such as {{must}}.<br />
# 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].<br />
# 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.<br />
# 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>&lt;nowiki&gt;</code> tags, e.g.: <code><nowiki>&lt;nowiki&gt;http://example.org/&lt;/nowiki&gt;</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>.<br />
# 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>]<br />
# 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>]<br />
# <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>]<br />
# <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])]<br />
# 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])]<br />
# 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>]<br />
<br />
== Accessibility ==<br />
#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>.<br />
#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.<br />
<br />
== Membersihkan Wiki ==<br />
Kunjungi [[spam-removal]].<br />
<br />
If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list rather than doing it yourself. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
<br />
== Terkait ==<br />
* [[mediawiki-customization]] - 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]].<br />
* [[wiki2]]<br />
* [[wiki-better-than-email]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=how-to-play-id&diff=40668how-to-play-id2009-09-02T17:58:07Z<p>Sevenova: /* Pedoman */</p>
<hr />
<div>__NOTOC__<br />
Jika ini kunjungan pertama Anda, harap membaca halaman [[introduction-id|pendahuluan]].<br />
<entry-title>Cara Penggunaan</entry-title><br />
== Pedoman ==<br />
Sebelum memulai kontribusi dimohon untuk mematuhi pedoman berikut:<br />
<br />
# Anda haru membuat akun sebelum melakukan penyuntingan/menambahkan halaman. Gunakan nama Anda dengan seksama, misalnya PemberianNama (Awal-Akhir), lihat juga [http://en.wikipedia.org/wiki/Wikipedia:Username panduan username Wikipedia]. Anda juga dipersilahkan menggunakan alias (misalnya [[User:Adactio]], [[User:Phae]]). Dimohon untuk tidak menggunakan nama organisasi atau kata benda (misalnya produk, teknologi).<br />
# Baca tentang [[:Category:public_domain_license|Deklarasi Publik Domain]] microformats.org dan dipersilahkan untuk menambahkan [[Template:cc-public-domain-release]] ke halaman pengguna Anda untuk melepaskan kontribusi Anda kepada microformats.org sebelum 2008 menjadi domain publik.<br />
# Coba terlebih dahulu [http://microformats.org/discuss kanal irc (lebih baik) atau mailing lists] (dan baca halaman [[mailing-lists]] sebelum melalukannya).<br />
<br />
# If you write something more opinion rather than logically reasoned, sign it with your username - you can easily do so with a datetimestamp in MediaWiki with four tildes, e.g.: <nowiki>~~~~</nowiki>.<br />
#*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.<br />
#*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>]<br />
# Please only create pages directly relating to [[POSH]], microformats (and [[picoformats]]) on this wiki. [[data-portability]] in line with microformats [[principles]] is also encouraged. Other pages will likely be deleted.<br />
# <span id="naming">Please obey the [[naming-conventions| naming conventions]] for pages. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span><br />
# Don't use talk pages. See #3. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Please try to ensure that you produce valid XHTML.<br />
# When you paste code, add some line breaks at a reasonable width.<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <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><br />
# Headings may be explicitly marked up with &lt;h1&gt; &lt;h2&gt; tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please <strong style="text-transform:uppercase">do not</strong> change them to "=" or "==" style headings. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. If you change a heading please leave a <code><nowiki><div id="oldheadingID"></div></nowiki></code> around the new heading with oldHeadingID set to the necessary value to maintain heading permalinks.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Start headings with a letter (or underscore a letter doesn't work), in order to generate valid ID attributes on heading elements.<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <span id="avoid-simple-contradictions">Please avoid simple contradictory responses</span> 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. 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>]<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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>]. Previously: Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Check "what links here" before moving pages, and fix any links to the page you're moving, if appropriate.<br />
# 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])]<br />
# Use [[rfc-2119#Templates|templates]] for RFC 2119 terms such as {{must}}.<br />
# 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].<br />
# 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.<br />
# 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>&lt;nowiki&gt;</code> tags, e.g.: <code><nowiki>&lt;nowiki&gt;http://example.org/&lt;/nowiki&gt;</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>.<br />
# 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>]<br />
# 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>]<br />
# <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>]<br />
# <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])]<br />
# 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])]<br />
# 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>]<br />
<br />
== Accessibility ==<br />
#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>.<br />
#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.<br />
<br />
== Membersihkan Wiki ==<br />
Kunjungi [[spam-removal]].<br />
<br />
If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list rather than doing it yourself. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
<br />
== Terkait ==<br />
* [[mediawiki-customization]] - 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]].<br />
* [[wiki2]]<br />
* [[wiki-better-than-email]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=how-to-play-id&diff=40665how-to-play-id2009-09-02T17:37:06Z<p>Sevenova: </p>
<hr />
<div>__NOTOC__<br />
Jika ini kunjungan pertama Anda, harap membaca halaman [[introduction-id|pendahuluan]].<br />
<entry-title>Cara Penggunaan</entry-title><br />
== Pedoman ==<br />
Sebelum memulai kontribusi dimohon untuk mematuhi pedoman berikut:<br />
<br />
# You have to create an account before editing/creating pages. Please consider using your name, e.g. GivenFamily (FirstLast), see also [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).<br />
# Read about microformats.org [[:Category:public_domain_license|Public Domain Declarations]] and please consider adding the [[Template:cc-public-domain-release]] to your User page accordingly to release your contributions to microformats.org before 2008 into the public domain.<br />
# Try the [http://microformats.org/discuss irc channel (preferable) or mailing lists] first (and read the [[mailing-lists]] page before doing so).<br />
# If you write something more opinion rather than logically reasoned, sign it with your username - you can easily do so with a datetimestamp in MediaWiki with four tildes, e.g.: <nowiki>~~~~</nowiki>.<br />
#*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.<br />
#*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>]<br />
# Please only create pages directly relating to [[POSH]], microformats (and [[picoformats]]) on this wiki. [[data-portability]] in line with microformats [[principles]] is also encouraged. Other pages will likely be deleted.<br />
# <span id="naming">Please obey the [[naming-conventions| naming conventions]] for pages. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span><br />
# Don't use talk pages. See #3. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Please try to ensure that you produce valid XHTML.<br />
# When you paste code, add some line breaks at a reasonable width.<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <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><br />
# Headings may be explicitly marked up with &lt;h1&gt; &lt;h2&gt; tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please <strong style="text-transform:uppercase">do not</strong> change them to "=" or "==" style headings. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. If you change a heading please leave a <code><nowiki><div id="oldheadingID"></div></nowiki></code> around the new heading with oldHeadingID set to the necessary value to maintain heading permalinks.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Start headings with a letter (or underscore a letter doesn't work), in order to generate valid ID attributes on heading elements.<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <span id="avoid-simple-contradictions">Please avoid simple contradictory responses</span> 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. 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>]<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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>]. Previously: Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Check "what links here" before moving pages, and fix any links to the page you're moving, if appropriate.<br />
# 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])]<br />
# Use [[rfc-2119#Templates|templates]] for RFC 2119 terms such as {{must}}.<br />
# 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].<br />
# 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.<br />
# 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>&lt;nowiki&gt;</code> tags, e.g.: <code><nowiki>&lt;nowiki&gt;http://example.org/&lt;/nowiki&gt;</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>.<br />
# 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>]<br />
# 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>]<br />
# <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>]<br />
# <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])]<br />
# 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])]<br />
# 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>]<br />
<br />
== Accessibility ==<br />
#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>.<br />
#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.<br />
<br />
== Membersihkan Wiki ==<br />
Kunjungi [[spam-removal]].<br />
<br />
If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list rather than doing it yourself. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
<br />
== Terkait ==<br />
* [[mediawiki-customization]] - 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]].<br />
* [[wiki2]]<br />
* [[wiki-better-than-email]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=how-to-play-id&diff=40649how-to-play-id2009-09-02T08:53:21Z<p>Sevenova: /* Related */</p>
<hr />
<div>__NOTOC__<br />
Jika ini kunjungan pertama Anda, dimohon untuk membaca halaman [[introduction-id|pendahuluan]].<br />
<entry-title>Cara Penggunaan</entry-title><br />
== Pedoman ==<br />
Sebelum memulai kontribusi dimohon untuk mematuhi pedoman berikut:<br />
<br />
# You have to create an account before editing/creating pages. Please consider using your name, e.g. GivenFamily (FirstLast), see also [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).<br />
# Read about microformats.org [[:Category:public_domain_license|Public Domain Declarations]] and please consider adding the [[Template:cc-public-domain-release]] to your User page accordingly to release your contributions to microformats.org before 2008 into the public domain.<br />
# Try the [http://microformats.org/discuss irc channel (preferable) or mailing lists] first (and read the [[mailing-lists]] page before doing so).<br />
# If you write something more opinion rather than logically reasoned, sign it with your username - you can easily do so with a datetimestamp in MediaWiki with four tildes, e.g.: <nowiki>~~~~</nowiki>.<br />
#*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.<br />
#*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>]<br />
# Please only create pages directly relating to [[POSH]], microformats (and [[picoformats]]) on this wiki. [[data-portability]] in line with microformats [[principles]] is also encouraged. Other pages will likely be deleted.<br />
# <span id="naming">Please obey the [[naming-conventions| naming conventions]] for pages. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span><br />
# Don't use talk pages. See #3. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Please try to ensure that you produce valid XHTML.<br />
# When you paste code, add some line breaks at a reasonable width.<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <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><br />
# Headings may be explicitly marked up with &lt;h1&gt; &lt;h2&gt; tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please <strong style="text-transform:uppercase">do not</strong> change them to "=" or "==" style headings. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. If you change a heading please leave a <code><nowiki><div id="oldheadingID"></div></nowiki></code> around the new heading with oldHeadingID set to the necessary value to maintain heading permalinks.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Start headings with a letter (or underscore a letter doesn't work), in order to generate valid ID attributes on heading elements.<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <span id="avoid-simple-contradictions">Please avoid simple contradictory responses</span> 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. 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>]<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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>]. Previously: Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Check "what links here" before moving pages, and fix any links to the page you're moving, if appropriate.<br />
# 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])]<br />
# Use [[rfc-2119#Templates|templates]] for RFC 2119 terms such as {{must}}.<br />
# 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].<br />
# 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.<br />
# 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>&lt;nowiki&gt;</code> tags, e.g.: <code><nowiki>&lt;nowiki&gt;http://example.org/&lt;/nowiki&gt;</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>.<br />
# 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>]<br />
# 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>]<br />
# <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>]<br />
# <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])]<br />
# 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])]<br />
# 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>]<br />
<br />
== Accessibility ==<br />
#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>.<br />
#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.<br />
<br />
== Membersihkan Wiki ==<br />
Kunjungi [[spam-removal]].<br />
<br />
If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list rather than doing it yourself. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
<br />
== Terkait ==<br />
* [[mediawiki-customization]] - 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]].<br />
* [[wiki2]]<br />
* [[wiki-better-than-email]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=how-to-play-id&diff=40648how-to-play-id2009-09-02T08:51:37Z<p>Sevenova: /* Wiki Cleaning */</p>
<hr />
<div>__NOTOC__<br />
Jika ini kunjungan pertama Anda, dimohon untuk membaca halaman [[introduction-id|pendahuluan]].<br />
<entry-title>Cara Penggunaan</entry-title><br />
== Pedoman ==<br />
Sebelum memulai kontribusi dimohon untuk mematuhi pedoman berikut:<br />
<br />
# You have to create an account before editing/creating pages. Please consider using your name, e.g. GivenFamily (FirstLast), see also [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).<br />
# Read about microformats.org [[:Category:public_domain_license|Public Domain Declarations]] and please consider adding the [[Template:cc-public-domain-release]] to your User page accordingly to release your contributions to microformats.org before 2008 into the public domain.<br />
# Try the [http://microformats.org/discuss irc channel (preferable) or mailing lists] first (and read the [[mailing-lists]] page before doing so).<br />
# If you write something more opinion rather than logically reasoned, sign it with your username - you can easily do so with a datetimestamp in MediaWiki with four tildes, e.g.: <nowiki>~~~~</nowiki>.<br />
#*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.<br />
#*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>]<br />
# Please only create pages directly relating to [[POSH]], microformats (and [[picoformats]]) on this wiki. [[data-portability]] in line with microformats [[principles]] is also encouraged. Other pages will likely be deleted.<br />
# <span id="naming">Please obey the [[naming-conventions| naming conventions]] for pages. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span><br />
# Don't use talk pages. See #3. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Please try to ensure that you produce valid XHTML.<br />
# When you paste code, add some line breaks at a reasonable width.<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <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><br />
# Headings may be explicitly marked up with &lt;h1&gt; &lt;h2&gt; tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please <strong style="text-transform:uppercase">do not</strong> change them to "=" or "==" style headings. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. If you change a heading please leave a <code><nowiki><div id="oldheadingID"></div></nowiki></code> around the new heading with oldHeadingID set to the necessary value to maintain heading permalinks.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Start headings with a letter (or underscore a letter doesn't work), in order to generate valid ID attributes on heading elements.<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <span id="avoid-simple-contradictions">Please avoid simple contradictory responses</span> 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. 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>]<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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>]. Previously: Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Check "what links here" before moving pages, and fix any links to the page you're moving, if appropriate.<br />
# 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])]<br />
# Use [[rfc-2119#Templates|templates]] for RFC 2119 terms such as {{must}}.<br />
# 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].<br />
# 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.<br />
# 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>&lt;nowiki&gt;</code> tags, e.g.: <code><nowiki>&lt;nowiki&gt;http://example.org/&lt;/nowiki&gt;</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>.<br />
# 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>]<br />
# 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>]<br />
# <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>]<br />
# <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])]<br />
# 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])]<br />
# 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>]<br />
<br />
== Accessibility ==<br />
#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>.<br />
#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.<br />
<br />
== Membersihkan Wiki ==<br />
Kunjungi [[spam-removal]].<br />
<br />
If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list rather than doing it yourself. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
<br />
== Related ==<br />
* [[mediawiki-customization]] - 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]].<br />
* [[wiki2]]<br />
* [[wiki-better-than-email]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=how-to-play-id&diff=40647how-to-play-id2009-09-02T08:50:02Z<p>Sevenova: </p>
<hr />
<div>__NOTOC__<br />
Jika ini kunjungan pertama Anda, dimohon untuk membaca halaman [[introduction-id|pendahuluan]].<br />
<entry-title>Cara Penggunaan</entry-title><br />
== Pedoman ==<br />
Sebelum memulai kontribusi dimohon untuk mematuhi pedoman berikut:<br />
<br />
# You have to create an account before editing/creating pages. Please consider using your name, e.g. GivenFamily (FirstLast), see also [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).<br />
# Read about microformats.org [[:Category:public_domain_license|Public Domain Declarations]] and please consider adding the [[Template:cc-public-domain-release]] to your User page accordingly to release your contributions to microformats.org before 2008 into the public domain.<br />
# Try the [http://microformats.org/discuss irc channel (preferable) or mailing lists] first (and read the [[mailing-lists]] page before doing so).<br />
# If you write something more opinion rather than logically reasoned, sign it with your username - you can easily do so with a datetimestamp in MediaWiki with four tildes, e.g.: <nowiki>~~~~</nowiki>.<br />
#*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.<br />
#*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>]<br />
# Please only create pages directly relating to [[POSH]], microformats (and [[picoformats]]) on this wiki. [[data-portability]] in line with microformats [[principles]] is also encouraged. Other pages will likely be deleted.<br />
# <span id="naming">Please obey the [[naming-conventions| naming conventions]] for pages. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span><br />
# Don't use talk pages. See #3. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Please try to ensure that you produce valid XHTML.<br />
# When you paste code, add some line breaks at a reasonable width.<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <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><br />
# Headings may be explicitly marked up with &lt;h1&gt; &lt;h2&gt; tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please <strong style="text-transform:uppercase">do not</strong> change them to "=" or "==" style headings. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. If you change a heading please leave a <code><nowiki><div id="oldheadingID"></div></nowiki></code> around the new heading with oldHeadingID set to the necessary value to maintain heading permalinks.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Start headings with a letter (or underscore a letter doesn't work), in order to generate valid ID attributes on heading elements.<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <span id="avoid-simple-contradictions">Please avoid simple contradictory responses</span> 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. 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>]<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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>]. Previously: Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Check "what links here" before moving pages, and fix any links to the page you're moving, if appropriate.<br />
# 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])]<br />
# Use [[rfc-2119#Templates|templates]] for RFC 2119 terms such as {{must}}.<br />
# 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].<br />
# 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.<br />
# 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>&lt;nowiki&gt;</code> tags, e.g.: <code><nowiki>&lt;nowiki&gt;http://example.org/&lt;/nowiki&gt;</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>.<br />
# 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>]<br />
# 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>]<br />
# <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>]<br />
# <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])]<br />
# 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])]<br />
# 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>]<br />
<br />
== Accessibility ==<br />
#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>.<br />
#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.<br />
<br />
== Wiki Cleaning ==<br />
See [[spam-removal]].<br />
<br />
If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list rather than doing it yourself. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
<br />
== Related ==<br />
* [[mediawiki-customization]] - 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]].<br />
* [[wiki2]]<br />
* [[wiki-better-than-email]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=how-to-play-id&diff=40646how-to-play-id2009-09-02T08:49:32Z<p>Sevenova: </p>
<hr />
<div>__NOTOC__<br />
Jika ini kunjungan pertama Anda, dimohon untuk membaca halaman [[introduction-id|pendahuluan]].<br />
<br />
<entry-title>Cara Penggunaan</entry-title><br />
== Pedoman ==<br />
Sebelum memulai kontribusi dimohon untuk mematuhi pedoman berikut:<br />
<br />
# You have to create an account before editing/creating pages. Please consider using your name, e.g. GivenFamily (FirstLast), see also [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).<br />
# Read about microformats.org [[:Category:public_domain_license|Public Domain Declarations]] and please consider adding the [[Template:cc-public-domain-release]] to your User page accordingly to release your contributions to microformats.org before 2008 into the public domain.<br />
# Try the [http://microformats.org/discuss irc channel (preferable) or mailing lists] first (and read the [[mailing-lists]] page before doing so).<br />
# If you write something more opinion rather than logically reasoned, sign it with your username - you can easily do so with a datetimestamp in MediaWiki with four tildes, e.g.: <nowiki>~~~~</nowiki>.<br />
#*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.<br />
#*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>]<br />
# Please only create pages directly relating to [[POSH]], microformats (and [[picoformats]]) on this wiki. [[data-portability]] in line with microformats [[principles]] is also encouraged. Other pages will likely be deleted.<br />
# <span id="naming">Please obey the [[naming-conventions| naming conventions]] for pages. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span><br />
# Don't use talk pages. See #3. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Please try to ensure that you produce valid XHTML.<br />
# When you paste code, add some line breaks at a reasonable width.<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <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><br />
# Headings may be explicitly marked up with &lt;h1&gt; &lt;h2&gt; tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please <strong style="text-transform:uppercase">do not</strong> change them to "=" or "==" style headings. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. If you change a heading please leave a <code><nowiki><div id="oldheadingID"></div></nowiki></code> around the new heading with oldHeadingID set to the necessary value to maintain heading permalinks.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Start headings with a letter (or underscore a letter doesn't work), in order to generate valid ID attributes on heading elements.<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <span id="avoid-simple-contradictions">Please avoid simple contradictory responses</span> 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. 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>]<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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>]. Previously: Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Check "what links here" before moving pages, and fix any links to the page you're moving, if appropriate.<br />
# 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])]<br />
# Use [[rfc-2119#Templates|templates]] for RFC 2119 terms such as {{must}}.<br />
# 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].<br />
# 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.<br />
# 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>&lt;nowiki&gt;</code> tags, e.g.: <code><nowiki>&lt;nowiki&gt;http://example.org/&lt;/nowiki&gt;</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>.<br />
# 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>]<br />
# 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>]<br />
# <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>]<br />
# <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])]<br />
# 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])]<br />
# 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>]<br />
<br />
== Accessibility ==<br />
#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>.<br />
#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.<br />
<br />
== Wiki Cleaning ==<br />
See [[spam-removal]].<br />
<br />
If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list rather than doing it yourself. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
<br />
== Related ==<br />
* [[mediawiki-customization]] - 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]].<br />
* [[wiki2]]<br />
* [[wiki-better-than-email]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=how-to-play-id&diff=40645how-to-play-id2009-09-02T08:46:04Z<p>Sevenova: New page: __NOTOC__ If this is your first visit, please see the introduction page. <entry-title>Cara Penggunaan</entry-title> == Pedoman == Sebelum memulai kontribusi dimohon untuk mematuhi pedo...</p>
<hr />
<div>__NOTOC__<br />
If this is your first visit, please see the [[introduction]] page.<br />
<entry-title>Cara Penggunaan</entry-title><br />
== Pedoman ==<br />
Sebelum memulai kontribusi dimohon untuk mematuhi pedoman berikut:<br />
<br />
# You have to create an account before editing/creating pages. Please consider using your name, e.g. GivenFamily (FirstLast), see also [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).<br />
# Read about microformats.org [[:Category:public_domain_license|Public Domain Declarations]] and please consider adding the [[Template:cc-public-domain-release]] to your User page accordingly to release your contributions to microformats.org before 2008 into the public domain.<br />
# Try the [http://microformats.org/discuss irc channel (preferable) or mailing lists] first (and read the [[mailing-lists]] page before doing so).<br />
# If you write something more opinion rather than logically reasoned, sign it with your username - you can easily do so with a datetimestamp in MediaWiki with four tildes, e.g.: <nowiki>~~~~</nowiki>.<br />
#*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.<br />
#*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>]<br />
# Please only create pages directly relating to [[POSH]], microformats (and [[picoformats]]) on this wiki. [[data-portability]] in line with microformats [[principles]] is also encouraged. Other pages will likely be deleted.<br />
# <span id="naming">Please obey the [[naming-conventions| naming conventions]] for pages. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>] </span><br />
# Don't use talk pages. See #3. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Please try to ensure that you produce valid XHTML.<br />
# When you paste code, add some line breaks at a reasonable width.<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <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><br />
# Headings may be explicitly marked up with &lt;h1&gt; &lt;h2&gt; tags etc. in order to avoid having them show up / pollute the Table of Contents. If you find such headings in a page, please <strong style="text-transform:uppercase">do not</strong> change them to "=" or "==" style headings. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Avoid renaming/changing heading text, including even just their capitalization or to comply with above rules that apply to headings. Headings are often used as permalinks, and changing the heading breaks such permalinks that have already been used. Thus be careful when creating headings. If you change a heading please leave a <code><nowiki><div id="oldheadingID"></div></nowiki></code> around the new heading with oldHeadingID set to the necessary value to maintain heading permalinks.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Start headings with a letter (or underscore a letter doesn't work), in order to generate valid ID attributes on heading elements.<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# <span id="avoid-simple-contradictions">Please avoid simple contradictory responses</span> 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. 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>]<br />
# 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. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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>]. Previously: Do not use the MediaWiki "Categories" mechanism. As with "Talk" pages, this community does not use all the features of MediaWiki.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# 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.[<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
# Check "what links here" before moving pages, and fix any links to the page you're moving, if appropriate.<br />
# 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])]<br />
# Use [[rfc-2119#Templates|templates]] for RFC 2119 terms such as {{must}}.<br />
# 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].<br />
# 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.<br />
# 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>&lt;nowiki&gt;</code> tags, e.g.: <code><nowiki>&lt;nowiki&gt;http://example.org/&lt;/nowiki&gt;</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>.<br />
# 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>]<br />
# 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>]<br />
# <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>]<br />
# <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])]<br />
# 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])]<br />
# 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>]<br />
<br />
== Accessibility ==<br />
#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>.<br />
#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.<br />
<br />
== Wiki Cleaning ==<br />
See [[spam-removal]].<br />
<br />
If you see something which you think needs massive cleanup on the wiki, please point it out to admins on the irc channel or microformats-discuss list rather than doing it yourself. [<abbr title="guideline created due to one or more actions by Andy Mabbett">src:A</abbr>]<br />
<br />
== Related ==<br />
* [[mediawiki-customization]] - 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]].<br />
* [[wiki2]]<br />
* [[wiki-better-than-email]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40644Main Page-id2009-09-02T08:40:35Z<p>Sevenova: /* Spesifikasi */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[introduction-id|pendahuluan]] dan baca juga [[how-to-play-id|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pengantar==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations-id|presentasi]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo-id|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep mencakup hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses). Stabilitas pada dokumen ini tidak dapat dijamin, dan pengguna harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40643Main Page-id2009-09-02T08:40:12Z<p>Sevenova: /* Spesifikasi */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[introduction-id|pendahuluan]] dan baca juga [[how-to-play-id|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pengantar==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations-id|presentasi]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO-id]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep mencakup hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses). Stabilitas pada dokumen ini tidak dapat dijamin, dan pengguna harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=xoxo-id&diff=40642xoxo-id2009-09-02T08:38:42Z<p>Sevenova: New page: <entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title> XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan ...</p>
<hr />
<div><entry-title>XOXO 1.0: Extensible Open XHTML Outlines</entry-title><br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Sample Code ===<br />
<br />
* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.<br />
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.<br />
<br />
== XOXO Schemas ==<br />
This section is informative.<br />
<br />
Note: these may be out of date and require updating to reflect the use of &lt;dl&gt; for annotating XOXO items with arbitrary properties.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]<br />
<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Informative References ===<br />
This section is '''informative'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Contributed from http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Related Reading ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan on why OPML and a Microsoft Lists extension are both unnecessary].<br />
<br />
=== Unrelated Reading ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - apparently the Faye character is a fan of XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Q&A ===<br />
* If you have any questions about XOXO, check the [[xoxo-faq]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[xoxo-issues]] document.<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Sevenovahttp://microformats.org/wiki/index.php?title=presentations-id&diff=40628presentations-id2009-09-01T17:11:17Z<p>Sevenova: </p>
<hr />
<div><entry-title>Presentasi</entry-title><br />
<br />
Halaman ini mencatat berbagai presentasi, sesi, naskah dan poster mengenai diskusi dan penjelasan tentang [[microformats|Microformats]] secara umum dan terperinci. Kunjungi [[events|kegiatan]] Microformats untuk kegiatan presentasi berikutnya. Kunjungi juga [[podcasts]] dan [[screencast]] Microformats untuk presentasi dan diskusi video/audio.<br />
<br />
'''Catatan: Banyak tautan yang hilang pada halaman ini.''' Selebihnya, tautan presentasi dapat ditemukan dengan cara mengunjungi langsung halaman [[events|kegiatan]].<br />
<br />
Presentasi terbaru/sesi yang pertama tercatat.<br />
<br />
== 2009 ==<br />
* 2009-06-03 <cite lang="pt">[http://e.yq.sl.pt/ Microformatos - 2009 - Juntando as Peças do Puzzle]</cite> by [http://twitter.com/andr3 André Luís] at SAPO Sessions ([http://twitter.com/andr3/status/2017551933 as tweeted by @andr3])<br />
<br />
* 2009-03-12 [http://csarven.ca/presentations/microformats-06/ microformats: #towerofbabel #pareto #dataportability] presentation by [[User:Csarven|Sarven Capadisli]] at [http://mcgill.ca GLIS 663 Knowledge Taxonomies, McGill], Montr&#233;al, Canada<br />
<br />
* 2009-03-05 [http://csarven.ca/presentations/microformats-05/ Website data through the looking-glass] presentation by [[User:Csarven|Sarven Capadisli]] at [http://conf.phpquebec.com PHP Québec Conference 2009], Montr&#233;al, Canada<br />
<br />
* 2009-01-08 [http://csarven.ca/presentations/microformats-04/ Interacting with microformats] presentation by [[User:Csarven|Sarven Capadisli]] at [http://phpquebec.org PHP Qu&#233;bec Monthly Meetup], Montr&#233;al, Canada<br />
<br />
== 2008 ==<br />
* 2008-11-18 [http://cdharrison.com/presentations/microformats/ microformats: What are they and why should you use them?] during [http://refreshaugusta.com/ RefreshAugusta] at PowerServe, Augusta, Georgia.<br />
* 2008-09-05 [http://tantek.com/presentations/2008/09/social-network-portability Social Network Portability] during [[events/2008-09-05-dconstruct-social-network-portability|dConstruct 2008]].<br />
* 2008-08-19 [http://tantek.com/presentations/2008/08/microformats Better User Experience Through Microformats] during day 2 of [[events/2008-08-19-better-user-experience|An Event Apart San Francisco]].<br />
* 2008-08-16 [http://tantek.com/presentations/2008/08/wordpress-microformats/ WordPress and Microformats: Past, Present, Future] during [[events/2008-08-16-wordcamp|WordCamp 2008]]<br />
* 2008-07-02 [http://www.slideshare.net/andr3/microformatos-pequenas-peas-do-puzzle Microformatos - pequenças peças do puzzle] presentation in Portuguese, by André Luís for a training session at SAPO.pt (Lisbon, Portugal)<br />
* 2008-05-15 [http://csarven.ca/presentations/microformats-03/ Creating next generation Web sites] presentation by [[User:Csarven|Sarven Capadisli]] at [http://www.nstein.com/summit2008/ Nstein Innovation Leaders Summit 2008], Montreal, Canada<br />
* 2008-04-16 [http://slideshow.rubyforge.org/microformats.html Microformats - Adding Semantics to Your Web Site - Web 3.0 in Action] presentation by Gerald Bauer (Vancouver Software Developers Network/VanDev at University of British Columbia)<br />
* 2008-03-17 [http://csarven.ca/presentations/microformats-02/ Microformats overview: how to help machines recognise common data formats in Web documents] presentation by [[User:Csarven|Sarven Capadisli]] at [http://station-c.com/ Coder's Saturday], Montreal, Canada<br />
* 2008-02-19 [http://www.glennjones.net/Post/835/SemanticCampLondon.htm Can your website be your API and real life] presentation by Glenn Jones (Semantic Camp London) covers social network portability and date portability<br />
* 2008-02-19 [http://www.slideshare.net/garethr/parsing-microformats Parsing Microformats] presentation by Gareth Rushgrove (Semantic Camp London) includes an overview of available parsers<br />
<br />
== 2007 ==<br />
* 2007-11-17 [http://www.slideshare.net/56k/mromanello-ecal-presentation Linking Text References to Relevant Digital Resources Over The Web (Proposal of a Microformat for Canonical Texts References)] presentation by Matteo Romanello at [http://enlil.ff.cuni.cz/ecal Electronic Corpora of Ancient Languages] conference held in Prague on November 2007.<br />
* 2007-11-06 [http://www.slideshare.net/guest897d73/microformats-a-web-of-data Microformats: A Web of Data] presentation by Brian Suda at [[events/2007-11-06-microfomats-a-web-of-data|Web 2.0 Expo Berlin]].<br />
* 2007-10-31 [http://video.google.com/videoplay?docid=4912491017216716477 Microformats - The What, Where, Why and How] This is a recording of a presentation given by Mark Meeker on Microformats. Mark is an Architect on the UI Engineering team at Orbitz Worldwide. OrbitzTech talk Chicago Il.<br />
* 2007-10-04 [http://tantek.com/presentations/2007/10/social-network-portability/ Social Network Portability] presentation by Tantek Çelik at [[events/2007-10-04-fundamentos-web-social-network-portability|Fundamentos Web 2007]].<br />
* 2007-10-04 [http://www.slideshare.net/mattb/coding-on-the-shoulders-of-giants Coding on the Shoulders of Giants] presentation by Matt Biddulph at [[events/2007-10-04-future-of-web-apps|Future of Web Apps London 2007]] - mentions their implementation of hCard, hCalendar and how their support gives them more features.<br />
* 2007-10-02 [http://www.slideshare.net/cgriego/microformats-building-blocks-of-the-semantic-web/ Microformats, building blocks of the semantic web] presentation by Chris Griego at [[events/2007-10-02-dallas-ruby-brigade|Dallas Ruby Brigade October 2007]]<br />
* 2007-08-30 GeekUp presentation by [http://www.ts0.com Thom Shannon] - [http://www.ts0.com/2007/09/microformats-whats-point.asp Microformats: What's the point?]<br />
* 2007-06-.. http://tantek.com/presentations/2007/06/microformats-bb-you/<br />
* 2007-05-.. http://tantek.com/presentations/2007/05/microformats-bb-you/<br />
* 2007-06-02 BarCamp San Diego presentation by Joshua Brewer: [http://www.slideshare.net/jbrewer/barcamp-sd-microformats Microformats: Building a Better Web].<br />
* 2007-05-16 [[events/2007-05-16-XTech|XTech 2007]] presentation by Jeremy Keith: [http://adactio.com/extras/slides/nanotech.pdf Microformats: the nanotechnology of the semantic web].<br />
* 2007-04-30 [[events/2007-04-30-mix07|Microformats: Data Formats That Put Humans First]] [http://tantek.com/presentations/2007/04/microformats/ presentation by Tantek Çelik]<br />
* 2007-03-23 [[events/2007-03-23-stanford|Microformats at Stanford]] [http://tantek.com/presentations/2007/03/microformats/ presentation by Tantek Çelik]<br />
* 2007-03-22 [http://www.webdu.com.au/go/session/microformats--hidden-treasures Microformats—the hidden treasure] by Dmitry Baranovskiy at the [http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia, 3:00pm–4:00pm<br />
* 2007-03-16 [http://www.afroginthevalley.com/fr/2007/03/16/presentation-microformats-a-php-quebec/ Métadonnées pour Humains & Machines] (dead link ?) presentation in French by Sylvain Carle at the [http://conf.phpquebec.com/fr/archive/conf2007/ PHP Québec 2007] conference in Montréal, Canada.<br />
* 2007-02-23 [http://bluesmoon.info/talks/microformats/ Microformats at the CSI Web 2.0 Conference in Bangalore] presentation by Philip Tellis<br />
* 2007-02-19, [http://www.glennjones.net/Post/825/DestroyingWalledGardens-MicroformatssyndicationandAPI%e2%80%99s.htm Destroying Walled Gardens - Microformats syndication and API’s] at [http://barcamp.org/BarCampLondon2 BarCamp London 2], UK by Glenn Jones<br />
* 2007-02-13, [http://groups.google.com/group/bristolskillswap/web/february-skillswap-microformats Microformats: The Semantic Web for the Rest of Us] Bristol Skillswap [rtsp://stream.watershed.co.uk/skillswap/2007.02.13.microformats.mov Streaming Video]<br />
* 2007-02-07, [http://north.webdirections.org Web Directions North 2007], [http://north.webdirections.org/detail/venue/ Renaissance Vancouver Hotel Harbourside], 1133 West Hastings Street, Vancouver, British Columbia, V6E3T3, Canada<br />
** [[events/2007-02-07-web-directions-north|Microformats at Web Directions North 2007]], 11:45am-12:45pm, 1:45pm-3:45pm<br />
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2007/02/microformats/ Microformats — The Big Picture]"<br />
*** John Allsopp (Westciv) - "[http://north07.webdirections.org/presentations/MicroformatsForDevelopers.pdf Microformats For Developers]"<br />
*** Dan Cederholm (Simplebits) - "[http://north07.webdirections.org/presentations/MicroformatsForDesigners.pdf Microformats For Designers]"<br />
* 2007-02-03 [http://www.glennjones.net/Post/823/Microformats%2ctheAK-47oftheweb-WebDD.htm Microformats HTML to API] at [http://www.webdd.org.uk/ WebDD], Reading UK by Glenn Jones<br />
<br />
== 2006 ==<br />
* 2006-11-24, Taichi Kaminogoya presented to [http://2xup.org/log/2006/11/27-2219 microformats に触れてみよう] at [http://www.asahi-net.or.jp/~eb2m-mrt/kaihatsu9.html XML Developers' Day #9], Tokyo, JAPAN.<br />
* October 28th, [http://www.keepthebyte.ch/2006/10/microformats-speech-at-barcamp-zurich.html Microformats Speech at Barcamp Zurich]<br />
* October 10th, Taichi Kaminogoya presented to [http://2xup.org/log/2006/10/10-1800 microformatsがもたらすドキドキする未来] at [http://lp1.cssnite.jp/ CSS Nite LP Disk 1], Tokyo, JAPAN.<br />
* September 28th, [http://www.webdirections.org/microformats/ Microformats] at Web Directions South, Sydney Australia by John Allsopp. [http://www.webdirections.org/microformats/ slides, podcast, live blogging transcript all online now]<br />
* September 27th, [http://tantek.com/presentations/2006/09/microformats-intro/ Microformats Intro] at New Context 2006, Radisson Miyako Hotel, Minato-ku, Tokyo, JAPAN. See also [http://flickr.com/photos/tags/microformatsnewcontext2006 photos].<br />
* September 16th, [http://fredericdevillamil.com/presentations/2006/que-sont-les-microformats/index.html Introducing Microformats for resume publishing] in French by Frederic de Villamil at Barcamp Paris 4. Location: 43 rue d'Aboukir, 75002 Paris France<br />
* September 13th, [http://tantek.com/presentations/2006/09/microformats-practices/ Microformats Practices] at [[events/2006-09-13-future-of-web-apps-microformats|Future of Web Apps]] in San Francisco. Location: Palace of Fine Arts Theatre, Lyon Street, San Francisco CA 94123.<br />
* September 3th, Backnetwork and Microformats by Glenn Jones at Barcamp London. demo of hCard subscription idea for social networks. <br />
* 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].<br />
* 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]]<br />
* 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<br />
* June 15th, Phil Wilson presented to the [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ Institutional Web Management Workshop]<br />
* June 8, Pete Prodoehl presented [http://rasterweb.net/raster/presentations/microformats-20060608/ Microformats] to the Milwaukee Web Design Meetup Group<br />
* 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.<br />
* 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)<br />
* May 24, Kevin Lawver presented [http://presentations.lawver.net/standards/a_microformat_and_proposal_for/ A Microformat and Proposal For Interoperable Widgets]<br />
* 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]).<br />
* 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]<br />
* May 16, [http://theryanking.com/presentations/2006/xtech/tutorial/ Microformats from the Ground Up] by Brian Suda and Ryan King @ XTech 2006<br />
* 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]).<br />
* 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)<br />
* 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])<br />
* 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<br />
** Building with MicroFormats, [http://www.chaddickerson.com/blog/2006/03/17/reading-20-and-microformats/ Chad Dickerson], Yahoo <br />
* March 13, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX<br />
** [[events/2006-03-13-sxsw-microformats|Microformats: Evolving the Web]], 11:30am-12:30pm <br />
* March 11, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX<br />
** [http://tantek.com/presentations/2006/03/building-blocks Creating Building Blocks For Independents], 5pm-6pm<br />
** [http://flickr.com/photos/tags/microformatssxsw photos]<br />
* March 7, O'Reilly Emerging Technologies (ETech) Conference, Manchester Grand Hyatt, Ballroom, San Diego, CA<br />
** [[events/2006-03-07-etech-microformats|Microformats intro and lightning demos at O'Reilly ETech conf.]], 5:30pm-6:15pm <br />
** [http://flickr.com/photos/tags/microformatsetech photos]<br />
* 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<br />
** [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Technical Plenary Day]], 10:30am-11:30am<br />
*** Ian Hickson (Google) - "A billion documents and no semantics anywhere" (NEED LINK TO SLIDES OR STUDY)<br />
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2006/03/what-are-microformats/ What are microformats?]"<br />
*** Håkon Wium Lie (Opera) - "Cascading Markup Languages — boom!" (NEED LINK TO SLIDES)<br />
*** Rohit Khare (CommerceNet) - "[http://labs.commerce.net/~rohit/Angstro-W3C-TP/ Where Angle Brackets Fear to Tread]"<br />
*** Dan Connolly (W3C) - "[http://www.w3.org/2003/g/talk62/slides Microformats for practical Semantic Web deployment]"<br />
*** Q&A<br />
**** "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)<br />
** "Services and the Web" by Mark Nottingham (Yahoo), 12:05pm-12:10pm.<br />
*** Request to W3T/W3M: Go After The "Real" Web: Apache, PHP, Mozilla, Intermediaries and Caches, '''Microformats''', JSON... ('''emphasis''' added)<br />
** Attendees voted the "Microformats" session the best session of the Plenary Day. 6:17pm.<br />
* February 24, Yahoo Speakers Series, Yahoo Mission College Campus, 2nd floor conference room, 2821 Mission College Blvd., Santa Clara, CA 95054<br />
** [http://tantek.com/presentations/2006/02/microformats-evolution/ Microformats: Evolving the Web]<br />
* January 18, Apple Web Publishers internal meeting, Apple Computer, Star Trek conference room, 1 Infinite Loop, Cupertino, CA 95014, 12-1:40pm<br />
** [http://tantek.com/presentations/2006/01/microformats-evolution/ Microformats: Evolving the Web]<br />
* January 10, SD Forum Emerging Technologies SIG, Room H1, Cubberley Community Center, Palo Alto, CA, 7-9pm<br />
** Ryan King's presentation, Ernie Prabhakar's presentation, Rohit Khare's presentation<br />
** Microformats panel: Ryan King, Ernie Prabhakar, Rohit Khare, Tantek Çelik, Kevin Marks<br />
<br />
== 2005 ==<br />
* December 15, Syndicate Conference, San Francisco, CA<br />
** [http://tantek.com/presentations/2005/12/syndicate-microformats/ Microformats - Emerging syndication types]<br />
* November 26, [http://barcamp.org/index.cgi?TorCamp TorCamp], Teehan+Lax, 460 Richmond St. W, Toronto, ON, CA<br />
** [http://www.davidjanes.com/docs/2005.11.25%20Microformats%20Presentation.ppt powerpoints] (sorry)<br />
** [http://blog.davidjanes.com/mtarchives/2005_12.html#003467 photo]<br />
* November 12, THINK Conference, Santa Cruz room, Chaminade hotel, Santa Cruz, CA, USA<br />
** [[presentation-think-2005-11-12]]<br />
* November 10, (location unknown), by Kevin Yank of SitePoint Pty. Ltd.<br />
** [http://www.sitepoint.com/examples/innovation-on-standards/ Innovating on top of standards - Not around them]<br />
* October 5, [http://web2con.com Web 2.0 Conference], Olympic Room, Argent Hotel, San Francisco, CA, USA<br />
** [http://tantek.com/presentations/2005/10/microformats-examples/ Microformats Examples]<br />
* October 4, [http://osafoundation.org/ OSAF], San Francisco, CA, USA<br />
** [http://tantek.com/presentations/2005/10/microformats-evolution/ Microformats: Evolving the Web]<br />
* September 30, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia<br />
** [http://tantek.com/presentations/2005/09/microformats-evolution/ Microformats: Evolving the Web] (<nowiki>http://we05.com/podcast/mp3/we05-14-tantek-celik2.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 - incomplete, mirror: http://microformats.org/media/2005/09/we05-14-tantek-celik2.mp3)<br />
* September 29, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia<br />
** [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (<nowiki>http://we05.com/podcast/mp3/we05-2-tantek-celik.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 mirror: http://microformats.org/media/2005/09/we05-2-tantek-celik.mp3 )<br />
* September 25, [http://webzine2005.com/ Webzine 2005], Valhalla Room, Swedish American Hall, San Francisco, CA, USA<br />
** [http://theryanking.com/presentations/2005/webzine/ Microformats @ Webzine 2005]<br />
* September 21, Web Intelligence Conference, Compiegne, France <br />
** [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]<br />
* June 20: Supernova 2005 ([http://supernova2005.com/ Supernova2005 site]), Microformats [http://supernova2005.com/workshops.htm Workshop], Wharton West, Suite 500, San Francisco, CA, USA<br />
** "[http://tantek.com/presentations/2005/06/what-are-microformats/ What are Microformats?]"<br />
** "[http://homepage.mac.com/kevinmarks/supernovatags.html A microformat for tags]"<br />
** [http://wiki.commerce.net/wiki/ZCommerceWS#Microformats commercenet wiki page on the workshop] ([http://labs.commerce.net/wiki/index.php/ZCommerceWS#Microformats 2])<br />
* May 14: Fourteenth International World Wide Web Conference ([http://www2005.org/ WWW2005]), 2005, Microformats Dev-Day Track, Makuhari Messe Room 303, Chiba, JAPAN<br />
** "[http://tantek.com/presentations/2005/05/what-are-microformats/ What are Microformats?]" - Tantek Çelik <br />
** "[http://westciv.com/WWW2005/linkmf.html Link Microformats]" - John Allsopp<br />
** "[http://complexspiral.com/events/archive/2005/www2005/potential.html The Potential of Microformats]" - Eric Meyer<br />
** "Distributed Social Networks (XFN Implementations)"<br />
*** 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].<br />
** "[http://tantek.com/presentations/2005/05/hcard-hcalendar/ People and Events (hCard & hCalendar)]" - Tantek Çelik<br />
** "[http://cnlabs.commerce.net/~rohit/hReview-in-Review/ hReview in Review]" - Rohit Khare<br />
** "Bibliographies (hBib)" - notes captured: [[hbib-discussion-2005-05-14|hBib Discussion 2005-05-14]]<br />
** "[http://westciv.com/WWW2005/xml2mf.html a more meaningful web with microformats]"<br />
** "Semantic Web and Microformats" panel, Room 201<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* March 13<br />
** "[http://complexspiral.com/events/archive/2005/sxsw/ Emergent Semantics]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 15, Austin TX<br />
** "[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<br />
** "[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<br />
<br />
* January 21: [http://tantek.com/presentations/2005/01/attentionxml.html Attention.xml Technology Overview], private presentation, Yahoo! campus, Santa Clara, CA<br />
<br />
== 2004 ==<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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).<br />
<br />
Halaman ini dikontribusi oleh [http://developers.technorati.com/wiki/MicroFormatsPresentations The Technorati developers wiki].</div>Sevenovahttp://microformats.org/wiki/index.php?title=presentasi&diff=40605presentasi2009-09-01T04:59:35Z<p>Sevenova: /* 2004 */</p>
<hr />
<div>{{TOC-right}}<br />
<br />
Halaman ini mencatat berbagai presentasi, sesi, naskah dan poster mengenai diskusi dan penjelasan tentang [[microformats|Microformats]] secara umum dan terperinci. Kunjungi [[events|kegiatan]] Microformats untuk kegiatan presentasi berikutnya. Kunjungi juga [[podcasts]] dan [[screencast]] Microformats untuk presentasi dan diskusi video/audio.<br />
<br />
'''Catatan: Banyak tautan yang hilang pada halaman ini.''' Selebihnya, tautan presentasi dapat ditemukan dengan cara mengunjungi langsung halaman [[events|kegiatan]].<br />
<br />
Presentasi terbaru/sesi yang pertama tercatat.<br />
<br />
== 2009 ==<br />
* 2009-06-03 <cite lang="pt">[http://e.yq.sl.pt/ Microformatos - 2009 - Juntando as Peças do Puzzle]</cite> by [http://twitter.com/andr3 André Luís] at SAPO Sessions ([http://twitter.com/andr3/status/2017551933 as tweeted by @andr3])<br />
<br />
* 2009-03-12 [http://csarven.ca/presentations/microformats-06/ microformats: #towerofbabel #pareto #dataportability] presentation by [[User:Csarven|Sarven Capadisli]] at [http://mcgill.ca GLIS 663 Knowledge Taxonomies, McGill], Montr&#233;al, Canada<br />
<br />
* 2009-03-05 [http://csarven.ca/presentations/microformats-05/ Website data through the looking-glass] presentation by [[User:Csarven|Sarven Capadisli]] at [http://conf.phpquebec.com PHP Québec Conference 2009], Montr&#233;al, Canada<br />
<br />
* 2009-01-08 [http://csarven.ca/presentations/microformats-04/ Interacting with microformats] presentation by [[User:Csarven|Sarven Capadisli]] at [http://phpquebec.org PHP Qu&#233;bec Monthly Meetup], Montr&#233;al, Canada<br />
<br />
== 2008 ==<br />
* 2008-11-18 [http://cdharrison.com/presentations/microformats/ microformats: What are they and why should you use them?] during [http://refreshaugusta.com/ RefreshAugusta] at PowerServe, Augusta, Georgia.<br />
* 2008-09-05 [http://tantek.com/presentations/2008/09/social-network-portability Social Network Portability] during [[events/2008-09-05-dconstruct-social-network-portability|dConstruct 2008]].<br />
* 2008-08-19 [http://tantek.com/presentations/2008/08/microformats Better User Experience Through Microformats] during day 2 of [[events/2008-08-19-better-user-experience|An Event Apart San Francisco]].<br />
* 2008-08-16 [http://tantek.com/presentations/2008/08/wordpress-microformats/ WordPress and Microformats: Past, Present, Future] during [[events/2008-08-16-wordcamp|WordCamp 2008]]<br />
* 2008-07-02 [http://www.slideshare.net/andr3/microformatos-pequenas-peas-do-puzzle Microformatos - pequenças peças do puzzle] presentation in Portuguese, by André Luís for a training session at SAPO.pt (Lisbon, Portugal)<br />
* 2008-05-15 [http://csarven.ca/presentations/microformats-03/ Creating next generation Web sites] presentation by [[User:Csarven|Sarven Capadisli]] at [http://www.nstein.com/summit2008/ Nstein Innovation Leaders Summit 2008], Montreal, Canada<br />
* 2008-04-16 [http://slideshow.rubyforge.org/microformats.html Microformats - Adding Semantics to Your Web Site - Web 3.0 in Action] presentation by Gerald Bauer (Vancouver Software Developers Network/VanDev at University of British Columbia)<br />
* 2008-03-17 [http://csarven.ca/presentations/microformats-02/ Microformats overview: how to help machines recognise common data formats in Web documents] presentation by [[User:Csarven|Sarven Capadisli]] at [http://station-c.com/ Coder's Saturday], Montreal, Canada<br />
* 2008-02-19 [http://www.glennjones.net/Post/835/SemanticCampLondon.htm Can your website be your API and real life] presentation by Glenn Jones (Semantic Camp London) covers social network portability and date portability<br />
* 2008-02-19 [http://www.slideshare.net/garethr/parsing-microformats Parsing Microformats] presentation by Gareth Rushgrove (Semantic Camp London) includes an overview of available parsers<br />
<br />
== 2007 ==<br />
* 2007-11-17 [http://www.slideshare.net/56k/mromanello-ecal-presentation Linking Text References to Relevant Digital Resources Over The Web (Proposal of a Microformat for Canonical Texts References)] presentation by Matteo Romanello at [http://enlil.ff.cuni.cz/ecal Electronic Corpora of Ancient Languages] conference held in Prague on November 2007.<br />
* 2007-11-06 [http://www.slideshare.net/guest897d73/microformats-a-web-of-data Microformats: A Web of Data] presentation by Brian Suda at [[events/2007-11-06-microfomats-a-web-of-data|Web 2.0 Expo Berlin]].<br />
* 2007-10-31 [http://video.google.com/videoplay?docid=4912491017216716477 Microformats - The What, Where, Why and How] This is a recording of a presentation given by Mark Meeker on Microformats. Mark is an Architect on the UI Engineering team at Orbitz Worldwide. OrbitzTech talk Chicago Il.<br />
* 2007-10-04 [http://tantek.com/presentations/2007/10/social-network-portability/ Social Network Portability] presentation by Tantek Çelik at [[events/2007-10-04-fundamentos-web-social-network-portability|Fundamentos Web 2007]].<br />
* 2007-10-04 [http://www.slideshare.net/mattb/coding-on-the-shoulders-of-giants Coding on the Shoulders of Giants] presentation by Matt Biddulph at [[events/2007-10-04-future-of-web-apps|Future of Web Apps London 2007]] - mentions their implementation of hCard, hCalendar and how their support gives them more features.<br />
* 2007-10-02 [http://www.slideshare.net/cgriego/microformats-building-blocks-of-the-semantic-web/ Microformats, building blocks of the semantic web] presentation by Chris Griego at [[events/2007-10-02-dallas-ruby-brigade|Dallas Ruby Brigade October 2007]]<br />
* 2007-08-30 GeekUp presentation by [http://www.ts0.com Thom Shannon] - [http://www.ts0.com/2007/09/microformats-whats-point.asp Microformats: What's the point?]<br />
* 2007-06-.. http://tantek.com/presentations/2007/06/microformats-bb-you/<br />
* 2007-05-.. http://tantek.com/presentations/2007/05/microformats-bb-you/<br />
* 2007-06-02 BarCamp San Diego presentation by Joshua Brewer: [http://www.slideshare.net/jbrewer/barcamp-sd-microformats Microformats: Building a Better Web].<br />
* 2007-05-16 [[events/2007-05-16-XTech|XTech 2007]] presentation by Jeremy Keith: [http://adactio.com/extras/slides/nanotech.pdf Microformats: the nanotechnology of the semantic web].<br />
* 2007-04-30 [[events/2007-04-30-mix07|Microformats: Data Formats That Put Humans First]] [http://tantek.com/presentations/2007/04/microformats/ presentation by Tantek Çelik]<br />
* 2007-03-23 [[events/2007-03-23-stanford|Microformats at Stanford]] [http://tantek.com/presentations/2007/03/microformats/ presentation by Tantek Çelik]<br />
* 2007-03-22 [http://www.webdu.com.au/go/session/microformats--hidden-treasures Microformats—the hidden treasure] by Dmitry Baranovskiy at the [http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia, 3:00pm–4:00pm<br />
* 2007-03-16 [http://www.afroginthevalley.com/fr/2007/03/16/presentation-microformats-a-php-quebec/ Métadonnées pour Humains & Machines] (dead link ?) presentation in French by Sylvain Carle at the [http://conf.phpquebec.com/fr/archive/conf2007/ PHP Québec 2007] conference in Montréal, Canada.<br />
* 2007-02-23 [http://bluesmoon.info/talks/microformats/ Microformats at the CSI Web 2.0 Conference in Bangalore] presentation by Philip Tellis<br />
* 2007-02-19, [http://www.glennjones.net/Post/825/DestroyingWalledGardens-MicroformatssyndicationandAPI%e2%80%99s.htm Destroying Walled Gardens - Microformats syndication and API’s] at [http://barcamp.org/BarCampLondon2 BarCamp London 2], UK by Glenn Jones<br />
* 2007-02-13, [http://groups.google.com/group/bristolskillswap/web/february-skillswap-microformats Microformats: The Semantic Web for the Rest of Us] Bristol Skillswap [rtsp://stream.watershed.co.uk/skillswap/2007.02.13.microformats.mov Streaming Video]<br />
* 2007-02-07, [http://north.webdirections.org Web Directions North 2007], [http://north.webdirections.org/detail/venue/ Renaissance Vancouver Hotel Harbourside], 1133 West Hastings Street, Vancouver, British Columbia, V6E3T3, Canada<br />
** [[events/2007-02-07-web-directions-north|Microformats at Web Directions North 2007]], 11:45am-12:45pm, 1:45pm-3:45pm<br />
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2007/02/microformats/ Microformats — The Big Picture]"<br />
*** John Allsopp (Westciv) - "[http://north07.webdirections.org/presentations/MicroformatsForDevelopers.pdf Microformats For Developers]"<br />
*** Dan Cederholm (Simplebits) - "[http://north07.webdirections.org/presentations/MicroformatsForDesigners.pdf Microformats For Designers]"<br />
* 2007-02-03 [http://www.glennjones.net/Post/823/Microformats%2ctheAK-47oftheweb-WebDD.htm Microformats HTML to API] at [http://www.webdd.org.uk/ WebDD], Reading UK by Glenn Jones<br />
<br />
== 2006 ==<br />
* 2006-11-24, Taichi Kaminogoya presented to [http://2xup.org/log/2006/11/27-2219 microformats に触れてみよう] at [http://www.asahi-net.or.jp/~eb2m-mrt/kaihatsu9.html XML Developers' Day #9], Tokyo, JAPAN.<br />
* October 28th, [http://www.keepthebyte.ch/2006/10/microformats-speech-at-barcamp-zurich.html Microformats Speech at Barcamp Zurich]<br />
* October 10th, Taichi Kaminogoya presented to [http://2xup.org/log/2006/10/10-1800 microformatsがもたらすドキドキする未来] at [http://lp1.cssnite.jp/ CSS Nite LP Disk 1], Tokyo, JAPAN.<br />
* September 28th, [http://www.webdirections.org/microformats/ Microformats] at Web Directions South, Sydney Australia by John Allsopp. [http://www.webdirections.org/microformats/ slides, podcast, live blogging transcript all online now]<br />
* September 27th, [http://tantek.com/presentations/2006/09/microformats-intro/ Microformats Intro] at New Context 2006, Radisson Miyako Hotel, Minato-ku, Tokyo, JAPAN. See also [http://flickr.com/photos/tags/microformatsnewcontext2006 photos].<br />
* September 16th, [http://fredericdevillamil.com/presentations/2006/que-sont-les-microformats/index.html Introducing Microformats for resume publishing] in French by Frederic de Villamil at Barcamp Paris 4. Location: 43 rue d'Aboukir, 75002 Paris France<br />
* September 13th, [http://tantek.com/presentations/2006/09/microformats-practices/ Microformats Practices] at [[events/2006-09-13-future-of-web-apps-microformats|Future of Web Apps]] in San Francisco. Location: Palace of Fine Arts Theatre, Lyon Street, San Francisco CA 94123.<br />
* September 3th, Backnetwork and Microformats by Glenn Jones at Barcamp London. demo of hCard subscription idea for social networks. <br />
* 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].<br />
* 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]]<br />
* 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<br />
* June 15th, Phil Wilson presented to the [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ Institutional Web Management Workshop]<br />
* June 8, Pete Prodoehl presented [http://rasterweb.net/raster/presentations/microformats-20060608/ Microformats] to the Milwaukee Web Design Meetup Group<br />
* 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.<br />
* 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)<br />
* May 24, Kevin Lawver presented [http://presentations.lawver.net/standards/a_microformat_and_proposal_for/ A Microformat and Proposal For Interoperable Widgets]<br />
* 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]).<br />
* 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]<br />
* May 16, [http://theryanking.com/presentations/2006/xtech/tutorial/ Microformats from the Ground Up] by Brian Suda and Ryan King @ XTech 2006<br />
* 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]).<br />
* 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)<br />
* 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])<br />
* 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<br />
** Building with MicroFormats, [http://www.chaddickerson.com/blog/2006/03/17/reading-20-and-microformats/ Chad Dickerson], Yahoo <br />
* March 13, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX<br />
** [[events/2006-03-13-sxsw-microformats|Microformats: Evolving the Web]], 11:30am-12:30pm <br />
* March 11, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX<br />
** [http://tantek.com/presentations/2006/03/building-blocks Creating Building Blocks For Independents], 5pm-6pm<br />
** [http://flickr.com/photos/tags/microformatssxsw photos]<br />
* March 7, O'Reilly Emerging Technologies (ETech) Conference, Manchester Grand Hyatt, Ballroom, San Diego, CA<br />
** [[events/2006-03-07-etech-microformats|Microformats intro and lightning demos at O'Reilly ETech conf.]], 5:30pm-6:15pm <br />
** [http://flickr.com/photos/tags/microformatsetech photos]<br />
* 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<br />
** [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Technical Plenary Day]], 10:30am-11:30am<br />
*** Ian Hickson (Google) - "A billion documents and no semantics anywhere" (NEED LINK TO SLIDES OR STUDY)<br />
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2006/03/what-are-microformats/ What are microformats?]"<br />
*** Håkon Wium Lie (Opera) - "Cascading Markup Languages — boom!" (NEED LINK TO SLIDES)<br />
*** Rohit Khare (CommerceNet) - "[http://labs.commerce.net/~rohit/Angstro-W3C-TP/ Where Angle Brackets Fear to Tread]"<br />
*** Dan Connolly (W3C) - "[http://www.w3.org/2003/g/talk62/slides Microformats for practical Semantic Web deployment]"<br />
*** Q&A<br />
**** "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)<br />
** "Services and the Web" by Mark Nottingham (Yahoo), 12:05pm-12:10pm.<br />
*** Request to W3T/W3M: Go After The "Real" Web: Apache, PHP, Mozilla, Intermediaries and Caches, '''Microformats''', JSON... ('''emphasis''' added)<br />
** Attendees voted the "Microformats" session the best session of the Plenary Day. 6:17pm.<br />
* February 24, Yahoo Speakers Series, Yahoo Mission College Campus, 2nd floor conference room, 2821 Mission College Blvd., Santa Clara, CA 95054<br />
** [http://tantek.com/presentations/2006/02/microformats-evolution/ Microformats: Evolving the Web]<br />
* January 18, Apple Web Publishers internal meeting, Apple Computer, Star Trek conference room, 1 Infinite Loop, Cupertino, CA 95014, 12-1:40pm<br />
** [http://tantek.com/presentations/2006/01/microformats-evolution/ Microformats: Evolving the Web]<br />
* January 10, SD Forum Emerging Technologies SIG, Room H1, Cubberley Community Center, Palo Alto, CA, 7-9pm<br />
** Ryan King's presentation, Ernie Prabhakar's presentation, Rohit Khare's presentation<br />
** Microformats panel: Ryan King, Ernie Prabhakar, Rohit Khare, Tantek Çelik, Kevin Marks<br />
<br />
== 2005 ==<br />
* December 15, Syndicate Conference, San Francisco, CA<br />
** [http://tantek.com/presentations/2005/12/syndicate-microformats/ Microformats - Emerging syndication types]<br />
* November 26, [http://barcamp.org/index.cgi?TorCamp TorCamp], Teehan+Lax, 460 Richmond St. W, Toronto, ON, CA<br />
** [http://www.davidjanes.com/docs/2005.11.25%20Microformats%20Presentation.ppt powerpoints] (sorry)<br />
** [http://blog.davidjanes.com/mtarchives/2005_12.html#003467 photo]<br />
* November 12, THINK Conference, Santa Cruz room, Chaminade hotel, Santa Cruz, CA, USA<br />
** [[presentation-think-2005-11-12]]<br />
* November 10, (location unknown), by Kevin Yank of SitePoint Pty. Ltd.<br />
** [http://www.sitepoint.com/examples/innovation-on-standards/ Innovating on top of standards - Not around them]<br />
* October 5, [http://web2con.com Web 2.0 Conference], Olympic Room, Argent Hotel, San Francisco, CA, USA<br />
** [http://tantek.com/presentations/2005/10/microformats-examples/ Microformats Examples]<br />
* October 4, [http://osafoundation.org/ OSAF], San Francisco, CA, USA<br />
** [http://tantek.com/presentations/2005/10/microformats-evolution/ Microformats: Evolving the Web]<br />
* September 30, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia<br />
** [http://tantek.com/presentations/2005/09/microformats-evolution/ Microformats: Evolving the Web] (<nowiki>http://we05.com/podcast/mp3/we05-14-tantek-celik2.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 - incomplete, mirror: http://microformats.org/media/2005/09/we05-14-tantek-celik2.mp3)<br />
* September 29, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia<br />
** [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (<nowiki>http://we05.com/podcast/mp3/we05-2-tantek-celik.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 mirror: http://microformats.org/media/2005/09/we05-2-tantek-celik.mp3 )<br />
* September 25, [http://webzine2005.com/ Webzine 2005], Valhalla Room, Swedish American Hall, San Francisco, CA, USA<br />
** [http://theryanking.com/presentations/2005/webzine/ Microformats @ Webzine 2005]<br />
* September 21, Web Intelligence Conference, Compiegne, France <br />
** [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]<br />
* June 20: Supernova 2005 ([http://supernova2005.com/ Supernova2005 site]), Microformats [http://supernova2005.com/workshops.htm Workshop], Wharton West, Suite 500, San Francisco, CA, USA<br />
** "[http://tantek.com/presentations/2005/06/what-are-microformats/ What are Microformats?]"<br />
** "[http://homepage.mac.com/kevinmarks/supernovatags.html A microformat for tags]"<br />
** [http://wiki.commerce.net/wiki/ZCommerceWS#Microformats commercenet wiki page on the workshop] ([http://labs.commerce.net/wiki/index.php/ZCommerceWS#Microformats 2])<br />
* May 14: Fourteenth International World Wide Web Conference ([http://www2005.org/ WWW2005]), 2005, Microformats Dev-Day Track, Makuhari Messe Room 303, Chiba, JAPAN<br />
** "[http://tantek.com/presentations/2005/05/what-are-microformats/ What are Microformats?]" - Tantek Çelik <br />
** "[http://westciv.com/WWW2005/linkmf.html Link Microformats]" - John Allsopp<br />
** "[http://complexspiral.com/events/archive/2005/www2005/potential.html The Potential of Microformats]" - Eric Meyer<br />
** "Distributed Social Networks (XFN Implementations)"<br />
*** 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].<br />
** "[http://tantek.com/presentations/2005/05/hcard-hcalendar/ People and Events (hCard & hCalendar)]" - Tantek Çelik<br />
** "[http://cnlabs.commerce.net/~rohit/hReview-in-Review/ hReview in Review]" - Rohit Khare<br />
** "Bibliographies (hBib)" - notes captured: [[hbib-discussion-2005-05-14|hBib Discussion 2005-05-14]]<br />
** "[http://westciv.com/WWW2005/xml2mf.html a more meaningful web with microformats]"<br />
** "Semantic Web and Microformats" panel, Room 201<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* March 13<br />
** "[http://complexspiral.com/events/archive/2005/sxsw/ Emergent Semantics]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 15, Austin TX<br />
** "[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<br />
** "[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<br />
<br />
* January 21: [http://tantek.com/presentations/2005/01/attentionxml.html Attention.xml Technology Overview], private presentation, Yahoo! campus, Santa Clara, CA<br />
<br />
== 2004 ==<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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).<br />
<br />
Halaman ini dikontribusi oleh [http://developers.technorati.com/wiki/MicroFormatsPresentations The Technorati developers wiki].</div>Sevenovahttp://microformats.org/wiki/index.php?title=presentasi&diff=40604presentasi2009-09-01T04:58:59Z<p>Sevenova: </p>
<hr />
<div>{{TOC-right}}<br />
<br />
Halaman ini mencatat berbagai presentasi, sesi, naskah dan poster mengenai diskusi dan penjelasan tentang [[microformats|Microformats]] secara umum dan terperinci. Kunjungi [[events|kegiatan]] Microformats untuk kegiatan presentasi berikutnya. Kunjungi juga [[podcasts]] dan [[screencast]] Microformats untuk presentasi dan diskusi video/audio.<br />
<br />
'''Catatan: Banyak tautan yang hilang pada halaman ini.''' Selebihnya, tautan presentasi dapat ditemukan dengan cara mengunjungi langsung halaman [[events|kegiatan]].<br />
<br />
Presentasi terbaru/sesi yang pertama tercatat.<br />
<br />
== 2009 ==<br />
* 2009-06-03 <cite lang="pt">[http://e.yq.sl.pt/ Microformatos - 2009 - Juntando as Peças do Puzzle]</cite> by [http://twitter.com/andr3 André Luís] at SAPO Sessions ([http://twitter.com/andr3/status/2017551933 as tweeted by @andr3])<br />
<br />
* 2009-03-12 [http://csarven.ca/presentations/microformats-06/ microformats: #towerofbabel #pareto #dataportability] presentation by [[User:Csarven|Sarven Capadisli]] at [http://mcgill.ca GLIS 663 Knowledge Taxonomies, McGill], Montr&#233;al, Canada<br />
<br />
* 2009-03-05 [http://csarven.ca/presentations/microformats-05/ Website data through the looking-glass] presentation by [[User:Csarven|Sarven Capadisli]] at [http://conf.phpquebec.com PHP Québec Conference 2009], Montr&#233;al, Canada<br />
<br />
* 2009-01-08 [http://csarven.ca/presentations/microformats-04/ Interacting with microformats] presentation by [[User:Csarven|Sarven Capadisli]] at [http://phpquebec.org PHP Qu&#233;bec Monthly Meetup], Montr&#233;al, Canada<br />
<br />
== 2008 ==<br />
* 2008-11-18 [http://cdharrison.com/presentations/microformats/ microformats: What are they and why should you use them?] during [http://refreshaugusta.com/ RefreshAugusta] at PowerServe, Augusta, Georgia.<br />
* 2008-09-05 [http://tantek.com/presentations/2008/09/social-network-portability Social Network Portability] during [[events/2008-09-05-dconstruct-social-network-portability|dConstruct 2008]].<br />
* 2008-08-19 [http://tantek.com/presentations/2008/08/microformats Better User Experience Through Microformats] during day 2 of [[events/2008-08-19-better-user-experience|An Event Apart San Francisco]].<br />
* 2008-08-16 [http://tantek.com/presentations/2008/08/wordpress-microformats/ WordPress and Microformats: Past, Present, Future] during [[events/2008-08-16-wordcamp|WordCamp 2008]]<br />
* 2008-07-02 [http://www.slideshare.net/andr3/microformatos-pequenas-peas-do-puzzle Microformatos - pequenças peças do puzzle] presentation in Portuguese, by André Luís for a training session at SAPO.pt (Lisbon, Portugal)<br />
* 2008-05-15 [http://csarven.ca/presentations/microformats-03/ Creating next generation Web sites] presentation by [[User:Csarven|Sarven Capadisli]] at [http://www.nstein.com/summit2008/ Nstein Innovation Leaders Summit 2008], Montreal, Canada<br />
* 2008-04-16 [http://slideshow.rubyforge.org/microformats.html Microformats - Adding Semantics to Your Web Site - Web 3.0 in Action] presentation by Gerald Bauer (Vancouver Software Developers Network/VanDev at University of British Columbia)<br />
* 2008-03-17 [http://csarven.ca/presentations/microformats-02/ Microformats overview: how to help machines recognise common data formats in Web documents] presentation by [[User:Csarven|Sarven Capadisli]] at [http://station-c.com/ Coder's Saturday], Montreal, Canada<br />
* 2008-02-19 [http://www.glennjones.net/Post/835/SemanticCampLondon.htm Can your website be your API and real life] presentation by Glenn Jones (Semantic Camp London) covers social network portability and date portability<br />
* 2008-02-19 [http://www.slideshare.net/garethr/parsing-microformats Parsing Microformats] presentation by Gareth Rushgrove (Semantic Camp London) includes an overview of available parsers<br />
<br />
== 2007 ==<br />
* 2007-11-17 [http://www.slideshare.net/56k/mromanello-ecal-presentation Linking Text References to Relevant Digital Resources Over The Web (Proposal of a Microformat for Canonical Texts References)] presentation by Matteo Romanello at [http://enlil.ff.cuni.cz/ecal Electronic Corpora of Ancient Languages] conference held in Prague on November 2007.<br />
* 2007-11-06 [http://www.slideshare.net/guest897d73/microformats-a-web-of-data Microformats: A Web of Data] presentation by Brian Suda at [[events/2007-11-06-microfomats-a-web-of-data|Web 2.0 Expo Berlin]].<br />
* 2007-10-31 [http://video.google.com/videoplay?docid=4912491017216716477 Microformats - The What, Where, Why and How] This is a recording of a presentation given by Mark Meeker on Microformats. Mark is an Architect on the UI Engineering team at Orbitz Worldwide. OrbitzTech talk Chicago Il.<br />
* 2007-10-04 [http://tantek.com/presentations/2007/10/social-network-portability/ Social Network Portability] presentation by Tantek Çelik at [[events/2007-10-04-fundamentos-web-social-network-portability|Fundamentos Web 2007]].<br />
* 2007-10-04 [http://www.slideshare.net/mattb/coding-on-the-shoulders-of-giants Coding on the Shoulders of Giants] presentation by Matt Biddulph at [[events/2007-10-04-future-of-web-apps|Future of Web Apps London 2007]] - mentions their implementation of hCard, hCalendar and how their support gives them more features.<br />
* 2007-10-02 [http://www.slideshare.net/cgriego/microformats-building-blocks-of-the-semantic-web/ Microformats, building blocks of the semantic web] presentation by Chris Griego at [[events/2007-10-02-dallas-ruby-brigade|Dallas Ruby Brigade October 2007]]<br />
* 2007-08-30 GeekUp presentation by [http://www.ts0.com Thom Shannon] - [http://www.ts0.com/2007/09/microformats-whats-point.asp Microformats: What's the point?]<br />
* 2007-06-.. http://tantek.com/presentations/2007/06/microformats-bb-you/<br />
* 2007-05-.. http://tantek.com/presentations/2007/05/microformats-bb-you/<br />
* 2007-06-02 BarCamp San Diego presentation by Joshua Brewer: [http://www.slideshare.net/jbrewer/barcamp-sd-microformats Microformats: Building a Better Web].<br />
* 2007-05-16 [[events/2007-05-16-XTech|XTech 2007]] presentation by Jeremy Keith: [http://adactio.com/extras/slides/nanotech.pdf Microformats: the nanotechnology of the semantic web].<br />
* 2007-04-30 [[events/2007-04-30-mix07|Microformats: Data Formats That Put Humans First]] [http://tantek.com/presentations/2007/04/microformats/ presentation by Tantek Çelik]<br />
* 2007-03-23 [[events/2007-03-23-stanford|Microformats at Stanford]] [http://tantek.com/presentations/2007/03/microformats/ presentation by Tantek Çelik]<br />
* 2007-03-22 [http://www.webdu.com.au/go/session/microformats--hidden-treasures Microformats—the hidden treasure] by Dmitry Baranovskiy at the [http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia, 3:00pm–4:00pm<br />
* 2007-03-16 [http://www.afroginthevalley.com/fr/2007/03/16/presentation-microformats-a-php-quebec/ Métadonnées pour Humains & Machines] (dead link ?) presentation in French by Sylvain Carle at the [http://conf.phpquebec.com/fr/archive/conf2007/ PHP Québec 2007] conference in Montréal, Canada.<br />
* 2007-02-23 [http://bluesmoon.info/talks/microformats/ Microformats at the CSI Web 2.0 Conference in Bangalore] presentation by Philip Tellis<br />
* 2007-02-19, [http://www.glennjones.net/Post/825/DestroyingWalledGardens-MicroformatssyndicationandAPI%e2%80%99s.htm Destroying Walled Gardens - Microformats syndication and API’s] at [http://barcamp.org/BarCampLondon2 BarCamp London 2], UK by Glenn Jones<br />
* 2007-02-13, [http://groups.google.com/group/bristolskillswap/web/february-skillswap-microformats Microformats: The Semantic Web for the Rest of Us] Bristol Skillswap [rtsp://stream.watershed.co.uk/skillswap/2007.02.13.microformats.mov Streaming Video]<br />
* 2007-02-07, [http://north.webdirections.org Web Directions North 2007], [http://north.webdirections.org/detail/venue/ Renaissance Vancouver Hotel Harbourside], 1133 West Hastings Street, Vancouver, British Columbia, V6E3T3, Canada<br />
** [[events/2007-02-07-web-directions-north|Microformats at Web Directions North 2007]], 11:45am-12:45pm, 1:45pm-3:45pm<br />
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2007/02/microformats/ Microformats — The Big Picture]"<br />
*** John Allsopp (Westciv) - "[http://north07.webdirections.org/presentations/MicroformatsForDevelopers.pdf Microformats For Developers]"<br />
*** Dan Cederholm (Simplebits) - "[http://north07.webdirections.org/presentations/MicroformatsForDesigners.pdf Microformats For Designers]"<br />
* 2007-02-03 [http://www.glennjones.net/Post/823/Microformats%2ctheAK-47oftheweb-WebDD.htm Microformats HTML to API] at [http://www.webdd.org.uk/ WebDD], Reading UK by Glenn Jones<br />
<br />
== 2006 ==<br />
* 2006-11-24, Taichi Kaminogoya presented to [http://2xup.org/log/2006/11/27-2219 microformats に触れてみよう] at [http://www.asahi-net.or.jp/~eb2m-mrt/kaihatsu9.html XML Developers' Day #9], Tokyo, JAPAN.<br />
* October 28th, [http://www.keepthebyte.ch/2006/10/microformats-speech-at-barcamp-zurich.html Microformats Speech at Barcamp Zurich]<br />
* October 10th, Taichi Kaminogoya presented to [http://2xup.org/log/2006/10/10-1800 microformatsがもたらすドキドキする未来] at [http://lp1.cssnite.jp/ CSS Nite LP Disk 1], Tokyo, JAPAN.<br />
* September 28th, [http://www.webdirections.org/microformats/ Microformats] at Web Directions South, Sydney Australia by John Allsopp. [http://www.webdirections.org/microformats/ slides, podcast, live blogging transcript all online now]<br />
* September 27th, [http://tantek.com/presentations/2006/09/microformats-intro/ Microformats Intro] at New Context 2006, Radisson Miyako Hotel, Minato-ku, Tokyo, JAPAN. See also [http://flickr.com/photos/tags/microformatsnewcontext2006 photos].<br />
* September 16th, [http://fredericdevillamil.com/presentations/2006/que-sont-les-microformats/index.html Introducing Microformats for resume publishing] in French by Frederic de Villamil at Barcamp Paris 4. Location: 43 rue d'Aboukir, 75002 Paris France<br />
* September 13th, [http://tantek.com/presentations/2006/09/microformats-practices/ Microformats Practices] at [[events/2006-09-13-future-of-web-apps-microformats|Future of Web Apps]] in San Francisco. Location: Palace of Fine Arts Theatre, Lyon Street, San Francisco CA 94123.<br />
* September 3th, Backnetwork and Microformats by Glenn Jones at Barcamp London. demo of hCard subscription idea for social networks. <br />
* 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].<br />
* 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]]<br />
* 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<br />
* June 15th, Phil Wilson presented to the [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ Institutional Web Management Workshop]<br />
* June 8, Pete Prodoehl presented [http://rasterweb.net/raster/presentations/microformats-20060608/ Microformats] to the Milwaukee Web Design Meetup Group<br />
* 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.<br />
* 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)<br />
* May 24, Kevin Lawver presented [http://presentations.lawver.net/standards/a_microformat_and_proposal_for/ A Microformat and Proposal For Interoperable Widgets]<br />
* 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]).<br />
* 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]<br />
* May 16, [http://theryanking.com/presentations/2006/xtech/tutorial/ Microformats from the Ground Up] by Brian Suda and Ryan King @ XTech 2006<br />
* 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]).<br />
* 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)<br />
* 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])<br />
* 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<br />
** Building with MicroFormats, [http://www.chaddickerson.com/blog/2006/03/17/reading-20-and-microformats/ Chad Dickerson], Yahoo <br />
* March 13, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX<br />
** [[events/2006-03-13-sxsw-microformats|Microformats: Evolving the Web]], 11:30am-12:30pm <br />
* March 11, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX<br />
** [http://tantek.com/presentations/2006/03/building-blocks Creating Building Blocks For Independents], 5pm-6pm<br />
** [http://flickr.com/photos/tags/microformatssxsw photos]<br />
* March 7, O'Reilly Emerging Technologies (ETech) Conference, Manchester Grand Hyatt, Ballroom, San Diego, CA<br />
** [[events/2006-03-07-etech-microformats|Microformats intro and lightning demos at O'Reilly ETech conf.]], 5:30pm-6:15pm <br />
** [http://flickr.com/photos/tags/microformatsetech photos]<br />
* 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<br />
** [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Technical Plenary Day]], 10:30am-11:30am<br />
*** Ian Hickson (Google) - "A billion documents and no semantics anywhere" (NEED LINK TO SLIDES OR STUDY)<br />
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2006/03/what-are-microformats/ What are microformats?]"<br />
*** Håkon Wium Lie (Opera) - "Cascading Markup Languages — boom!" (NEED LINK TO SLIDES)<br />
*** Rohit Khare (CommerceNet) - "[http://labs.commerce.net/~rohit/Angstro-W3C-TP/ Where Angle Brackets Fear to Tread]"<br />
*** Dan Connolly (W3C) - "[http://www.w3.org/2003/g/talk62/slides Microformats for practical Semantic Web deployment]"<br />
*** Q&A<br />
**** "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)<br />
** "Services and the Web" by Mark Nottingham (Yahoo), 12:05pm-12:10pm.<br />
*** Request to W3T/W3M: Go After The "Real" Web: Apache, PHP, Mozilla, Intermediaries and Caches, '''Microformats''', JSON... ('''emphasis''' added)<br />
** Attendees voted the "Microformats" session the best session of the Plenary Day. 6:17pm.<br />
* February 24, Yahoo Speakers Series, Yahoo Mission College Campus, 2nd floor conference room, 2821 Mission College Blvd., Santa Clara, CA 95054<br />
** [http://tantek.com/presentations/2006/02/microformats-evolution/ Microformats: Evolving the Web]<br />
* January 18, Apple Web Publishers internal meeting, Apple Computer, Star Trek conference room, 1 Infinite Loop, Cupertino, CA 95014, 12-1:40pm<br />
** [http://tantek.com/presentations/2006/01/microformats-evolution/ Microformats: Evolving the Web]<br />
* January 10, SD Forum Emerging Technologies SIG, Room H1, Cubberley Community Center, Palo Alto, CA, 7-9pm<br />
** Ryan King's presentation, Ernie Prabhakar's presentation, Rohit Khare's presentation<br />
** Microformats panel: Ryan King, Ernie Prabhakar, Rohit Khare, Tantek Çelik, Kevin Marks<br />
<br />
== 2005 ==<br />
* December 15, Syndicate Conference, San Francisco, CA<br />
** [http://tantek.com/presentations/2005/12/syndicate-microformats/ Microformats - Emerging syndication types]<br />
* November 26, [http://barcamp.org/index.cgi?TorCamp TorCamp], Teehan+Lax, 460 Richmond St. W, Toronto, ON, CA<br />
** [http://www.davidjanes.com/docs/2005.11.25%20Microformats%20Presentation.ppt powerpoints] (sorry)<br />
** [http://blog.davidjanes.com/mtarchives/2005_12.html#003467 photo]<br />
* November 12, THINK Conference, Santa Cruz room, Chaminade hotel, Santa Cruz, CA, USA<br />
** [[presentation-think-2005-11-12]]<br />
* November 10, (location unknown), by Kevin Yank of SitePoint Pty. Ltd.<br />
** [http://www.sitepoint.com/examples/innovation-on-standards/ Innovating on top of standards - Not around them]<br />
* October 5, [http://web2con.com Web 2.0 Conference], Olympic Room, Argent Hotel, San Francisco, CA, USA<br />
** [http://tantek.com/presentations/2005/10/microformats-examples/ Microformats Examples]<br />
* October 4, [http://osafoundation.org/ OSAF], San Francisco, CA, USA<br />
** [http://tantek.com/presentations/2005/10/microformats-evolution/ Microformats: Evolving the Web]<br />
* September 30, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia<br />
** [http://tantek.com/presentations/2005/09/microformats-evolution/ Microformats: Evolving the Web] (<nowiki>http://we05.com/podcast/mp3/we05-14-tantek-celik2.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 - incomplete, mirror: http://microformats.org/media/2005/09/we05-14-tantek-celik2.mp3)<br />
* September 29, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia<br />
** [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (<nowiki>http://we05.com/podcast/mp3/we05-2-tantek-celik.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 mirror: http://microformats.org/media/2005/09/we05-2-tantek-celik.mp3 )<br />
* September 25, [http://webzine2005.com/ Webzine 2005], Valhalla Room, Swedish American Hall, San Francisco, CA, USA<br />
** [http://theryanking.com/presentations/2005/webzine/ Microformats @ Webzine 2005]<br />
* September 21, Web Intelligence Conference, Compiegne, France <br />
** [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]<br />
* June 20: Supernova 2005 ([http://supernova2005.com/ Supernova2005 site]), Microformats [http://supernova2005.com/workshops.htm Workshop], Wharton West, Suite 500, San Francisco, CA, USA<br />
** "[http://tantek.com/presentations/2005/06/what-are-microformats/ What are Microformats?]"<br />
** "[http://homepage.mac.com/kevinmarks/supernovatags.html A microformat for tags]"<br />
** [http://wiki.commerce.net/wiki/ZCommerceWS#Microformats commercenet wiki page on the workshop] ([http://labs.commerce.net/wiki/index.php/ZCommerceWS#Microformats 2])<br />
* May 14: Fourteenth International World Wide Web Conference ([http://www2005.org/ WWW2005]), 2005, Microformats Dev-Day Track, Makuhari Messe Room 303, Chiba, JAPAN<br />
** "[http://tantek.com/presentations/2005/05/what-are-microformats/ What are Microformats?]" - Tantek Çelik <br />
** "[http://westciv.com/WWW2005/linkmf.html Link Microformats]" - John Allsopp<br />
** "[http://complexspiral.com/events/archive/2005/www2005/potential.html The Potential of Microformats]" - Eric Meyer<br />
** "Distributed Social Networks (XFN Implementations)"<br />
*** 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].<br />
** "[http://tantek.com/presentations/2005/05/hcard-hcalendar/ People and Events (hCard & hCalendar)]" - Tantek Çelik<br />
** "[http://cnlabs.commerce.net/~rohit/hReview-in-Review/ hReview in Review]" - Rohit Khare<br />
** "Bibliographies (hBib)" - notes captured: [[hbib-discussion-2005-05-14|hBib Discussion 2005-05-14]]<br />
** "[http://westciv.com/WWW2005/xml2mf.html a more meaningful web with microformats]"<br />
** "Semantic Web and Microformats" panel, Room 201<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* March 13<br />
** "[http://complexspiral.com/events/archive/2005/sxsw/ Emergent Semantics]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 15, Austin TX<br />
** "[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<br />
** "[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<br />
<br />
* January 21: [http://tantek.com/presentations/2005/01/attentionxml.html Attention.xml Technology Overview], private presentation, Yahoo! campus, Santa Clara, CA<br />
<br />
== 2004 ==<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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).<br />
<br />
Halaman ini dikontribusi oleh [http://developers.technorati.com/wiki/MicroFormatsPresentations the Technorati developers wiki].</div>Sevenovahttp://microformats.org/wiki/index.php?title=presentasi&diff=40603presentasi2009-09-01T04:44:21Z<p>Sevenova: New page: {{TOC-right}} This page lists various presentations, sessions, papers and posters which have provided explanations and discusions of both microformats in general, and specific microfor...</p>
<hr />
<div>{{TOC-right}}<br />
This page lists various presentations, sessions, papers and posters which have provided explanations and discusions of both [[microformats]] in general, and specific microformats. Check out microformats [[events]] for upcoming presentations. See also microformats [[podcasts]] and [[screencasts]] for audio/video presentations and discussions.<br />
<br />
'''Note: This page is missing a lot of presentation links.''' More presentation links can be found by going through specific [[events]] pages.<br />
<br />
Most recent presentations/sessions listed first.<br />
<br />
== 2009 ==<br />
* 2009-06-03 <cite lang="pt">[http://e.yq.sl.pt/ Microformatos - 2009 - Juntando as Peças do Puzzle]</cite> by [http://twitter.com/andr3 André Luís] at SAPO Sessions ([http://twitter.com/andr3/status/2017551933 as tweeted by @andr3])<br />
<br />
* 2009-03-12 [http://csarven.ca/presentations/microformats-06/ microformats: #towerofbabel #pareto #dataportability] presentation by [[User:Csarven|Sarven Capadisli]] at [http://mcgill.ca GLIS 663 Knowledge Taxonomies, McGill], Montr&#233;al, Canada<br />
<br />
* 2009-03-05 [http://csarven.ca/presentations/microformats-05/ Website data through the looking-glass] presentation by [[User:Csarven|Sarven Capadisli]] at [http://conf.phpquebec.com PHP Québec Conference 2009], Montr&#233;al, Canada<br />
<br />
* 2009-01-08 [http://csarven.ca/presentations/microformats-04/ Interacting with microformats] presentation by [[User:Csarven|Sarven Capadisli]] at [http://phpquebec.org PHP Qu&#233;bec Monthly Meetup], Montr&#233;al, Canada<br />
<br />
== 2008 ==<br />
* 2008-11-18 [http://cdharrison.com/presentations/microformats/ microformats: What are they and why should you use them?] during [http://refreshaugusta.com/ RefreshAugusta] at PowerServe, Augusta, Georgia.<br />
* 2008-09-05 [http://tantek.com/presentations/2008/09/social-network-portability Social Network Portability] during [[events/2008-09-05-dconstruct-social-network-portability|dConstruct 2008]].<br />
* 2008-08-19 [http://tantek.com/presentations/2008/08/microformats Better User Experience Through Microformats] during day 2 of [[events/2008-08-19-better-user-experience|An Event Apart San Francisco]].<br />
* 2008-08-16 [http://tantek.com/presentations/2008/08/wordpress-microformats/ WordPress and Microformats: Past, Present, Future] during [[events/2008-08-16-wordcamp|WordCamp 2008]]<br />
* 2008-07-02 [http://www.slideshare.net/andr3/microformatos-pequenas-peas-do-puzzle Microformatos - pequenças peças do puzzle] presentation in Portuguese, by André Luís for a training session at SAPO.pt (Lisbon, Portugal)<br />
* 2008-05-15 [http://csarven.ca/presentations/microformats-03/ Creating next generation Web sites] presentation by [[User:Csarven|Sarven Capadisli]] at [http://www.nstein.com/summit2008/ Nstein Innovation Leaders Summit 2008], Montreal, Canada<br />
* 2008-04-16 [http://slideshow.rubyforge.org/microformats.html Microformats - Adding Semantics to Your Web Site - Web 3.0 in Action] presentation by Gerald Bauer (Vancouver Software Developers Network/VanDev at University of British Columbia)<br />
* 2008-03-17 [http://csarven.ca/presentations/microformats-02/ Microformats overview: how to help machines recognise common data formats in Web documents] presentation by [[User:Csarven|Sarven Capadisli]] at [http://station-c.com/ Coder's Saturday], Montreal, Canada<br />
* 2008-02-19 [http://www.glennjones.net/Post/835/SemanticCampLondon.htm Can your website be your API and real life] presentation by Glenn Jones (Semantic Camp London) covers social network portability and date portability<br />
* 2008-02-19 [http://www.slideshare.net/garethr/parsing-microformats Parsing Microformats] presentation by Gareth Rushgrove (Semantic Camp London) includes an overview of available parsers<br />
<br />
== 2007 ==<br />
* 2007-11-17 [http://www.slideshare.net/56k/mromanello-ecal-presentation Linking Text References to Relevant Digital Resources Over The Web (Proposal of a Microformat for Canonical Texts References)] presentation by Matteo Romanello at [http://enlil.ff.cuni.cz/ecal Electronic Corpora of Ancient Languages] conference held in Prague on November 2007.<br />
* 2007-11-06 [http://www.slideshare.net/guest897d73/microformats-a-web-of-data Microformats: A Web of Data] presentation by Brian Suda at [[events/2007-11-06-microfomats-a-web-of-data|Web 2.0 Expo Berlin]].<br />
* 2007-10-31 [http://video.google.com/videoplay?docid=4912491017216716477 Microformats - The What, Where, Why and How] This is a recording of a presentation given by Mark Meeker on Microformats. Mark is an Architect on the UI Engineering team at Orbitz Worldwide. OrbitzTech talk Chicago Il.<br />
* 2007-10-04 [http://tantek.com/presentations/2007/10/social-network-portability/ Social Network Portability] presentation by Tantek Çelik at [[events/2007-10-04-fundamentos-web-social-network-portability|Fundamentos Web 2007]].<br />
* 2007-10-04 [http://www.slideshare.net/mattb/coding-on-the-shoulders-of-giants Coding on the Shoulders of Giants] presentation by Matt Biddulph at [[events/2007-10-04-future-of-web-apps|Future of Web Apps London 2007]] - mentions their implementation of hCard, hCalendar and how their support gives them more features.<br />
* 2007-10-02 [http://www.slideshare.net/cgriego/microformats-building-blocks-of-the-semantic-web/ Microformats, building blocks of the semantic web] presentation by Chris Griego at [[events/2007-10-02-dallas-ruby-brigade|Dallas Ruby Brigade October 2007]]<br />
* 2007-08-30 GeekUp presentation by [http://www.ts0.com Thom Shannon] - [http://www.ts0.com/2007/09/microformats-whats-point.asp Microformats: What's the point?]<br />
* 2007-06-.. http://tantek.com/presentations/2007/06/microformats-bb-you/<br />
* 2007-05-.. http://tantek.com/presentations/2007/05/microformats-bb-you/<br />
* 2007-06-02 BarCamp San Diego presentation by Joshua Brewer: [http://www.slideshare.net/jbrewer/barcamp-sd-microformats Microformats: Building a Better Web].<br />
* 2007-05-16 [[events/2007-05-16-XTech|XTech 2007]] presentation by Jeremy Keith: [http://adactio.com/extras/slides/nanotech.pdf Microformats: the nanotechnology of the semantic web].<br />
* 2007-04-30 [[events/2007-04-30-mix07|Microformats: Data Formats That Put Humans First]] [http://tantek.com/presentations/2007/04/microformats/ presentation by Tantek Çelik]<br />
* 2007-03-23 [[events/2007-03-23-stanford|Microformats at Stanford]] [http://tantek.com/presentations/2007/03/microformats/ presentation by Tantek Çelik]<br />
* 2007-03-22 [http://www.webdu.com.au/go/session/microformats--hidden-treasures Microformats—the hidden treasure] by Dmitry Baranovskiy at the [http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia, 3:00pm–4:00pm<br />
* 2007-03-16 [http://www.afroginthevalley.com/fr/2007/03/16/presentation-microformats-a-php-quebec/ Métadonnées pour Humains & Machines] (dead link ?) presentation in French by Sylvain Carle at the [http://conf.phpquebec.com/fr/archive/conf2007/ PHP Québec 2007] conference in Montréal, Canada.<br />
* 2007-02-23 [http://bluesmoon.info/talks/microformats/ Microformats at the CSI Web 2.0 Conference in Bangalore] presentation by Philip Tellis<br />
* 2007-02-19, [http://www.glennjones.net/Post/825/DestroyingWalledGardens-MicroformatssyndicationandAPI%e2%80%99s.htm Destroying Walled Gardens - Microformats syndication and API’s] at [http://barcamp.org/BarCampLondon2 BarCamp London 2], UK by Glenn Jones<br />
* 2007-02-13, [http://groups.google.com/group/bristolskillswap/web/february-skillswap-microformats Microformats: The Semantic Web for the Rest of Us] Bristol Skillswap [rtsp://stream.watershed.co.uk/skillswap/2007.02.13.microformats.mov Streaming Video]<br />
* 2007-02-07, [http://north.webdirections.org Web Directions North 2007], [http://north.webdirections.org/detail/venue/ Renaissance Vancouver Hotel Harbourside], 1133 West Hastings Street, Vancouver, British Columbia, V6E3T3, Canada<br />
** [[events/2007-02-07-web-directions-north|Microformats at Web Directions North 2007]], 11:45am-12:45pm, 1:45pm-3:45pm<br />
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2007/02/microformats/ Microformats — The Big Picture]"<br />
*** John Allsopp (Westciv) - "[http://north07.webdirections.org/presentations/MicroformatsForDevelopers.pdf Microformats For Developers]"<br />
*** Dan Cederholm (Simplebits) - "[http://north07.webdirections.org/presentations/MicroformatsForDesigners.pdf Microformats For Designers]"<br />
* 2007-02-03 [http://www.glennjones.net/Post/823/Microformats%2ctheAK-47oftheweb-WebDD.htm Microformats HTML to API] at [http://www.webdd.org.uk/ WebDD], Reading UK by Glenn Jones<br />
<br />
== 2006 ==<br />
* 2006-11-24, Taichi Kaminogoya presented to [http://2xup.org/log/2006/11/27-2219 microformats に触れてみよう] at [http://www.asahi-net.or.jp/~eb2m-mrt/kaihatsu9.html XML Developers' Day #9], Tokyo, JAPAN.<br />
* October 28th, [http://www.keepthebyte.ch/2006/10/microformats-speech-at-barcamp-zurich.html Microformats Speech at Barcamp Zurich]<br />
* October 10th, Taichi Kaminogoya presented to [http://2xup.org/log/2006/10/10-1800 microformatsがもたらすドキドキする未来] at [http://lp1.cssnite.jp/ CSS Nite LP Disk 1], Tokyo, JAPAN.<br />
* September 28th, [http://www.webdirections.org/microformats/ Microformats] at Web Directions South, Sydney Australia by John Allsopp. [http://www.webdirections.org/microformats/ slides, podcast, live blogging transcript all online now]<br />
* September 27th, [http://tantek.com/presentations/2006/09/microformats-intro/ Microformats Intro] at New Context 2006, Radisson Miyako Hotel, Minato-ku, Tokyo, JAPAN. See also [http://flickr.com/photos/tags/microformatsnewcontext2006 photos].<br />
* September 16th, [http://fredericdevillamil.com/presentations/2006/que-sont-les-microformats/index.html Introducing Microformats for resume publishing] in French by Frederic de Villamil at Barcamp Paris 4. Location: 43 rue d'Aboukir, 75002 Paris France<br />
* September 13th, [http://tantek.com/presentations/2006/09/microformats-practices/ Microformats Practices] at [[events/2006-09-13-future-of-web-apps-microformats|Future of Web Apps]] in San Francisco. Location: Palace of Fine Arts Theatre, Lyon Street, San Francisco CA 94123.<br />
* September 3th, Backnetwork and Microformats by Glenn Jones at Barcamp London. demo of hCard subscription idea for social networks. <br />
* 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].<br />
* 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]]<br />
* 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<br />
* June 15th, Phil Wilson presented to the [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ Institutional Web Management Workshop]<br />
* June 8, Pete Prodoehl presented [http://rasterweb.net/raster/presentations/microformats-20060608/ Microformats] to the Milwaukee Web Design Meetup Group<br />
* 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.<br />
* 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)<br />
* May 24, Kevin Lawver presented [http://presentations.lawver.net/standards/a_microformat_and_proposal_for/ A Microformat and Proposal For Interoperable Widgets]<br />
* 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]).<br />
* 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]<br />
* May 16, [http://theryanking.com/presentations/2006/xtech/tutorial/ Microformats from the Ground Up] by Brian Suda and Ryan King @ XTech 2006<br />
* 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]).<br />
* 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)<br />
* 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])<br />
* 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<br />
** Building with MicroFormats, [http://www.chaddickerson.com/blog/2006/03/17/reading-20-and-microformats/ Chad Dickerson], Yahoo <br />
* March 13, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX<br />
** [[events/2006-03-13-sxsw-microformats|Microformats: Evolving the Web]], 11:30am-12:30pm <br />
* March 11, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX<br />
** [http://tantek.com/presentations/2006/03/building-blocks Creating Building Blocks For Independents], 5pm-6pm<br />
** [http://flickr.com/photos/tags/microformatssxsw photos]<br />
* March 7, O'Reilly Emerging Technologies (ETech) Conference, Manchester Grand Hyatt, Ballroom, San Diego, CA<br />
** [[events/2006-03-07-etech-microformats|Microformats intro and lightning demos at O'Reilly ETech conf.]], 5:30pm-6:15pm <br />
** [http://flickr.com/photos/tags/microformatsetech photos]<br />
* 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<br />
** [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Technical Plenary Day]], 10:30am-11:30am<br />
*** Ian Hickson (Google) - "A billion documents and no semantics anywhere" (NEED LINK TO SLIDES OR STUDY)<br />
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2006/03/what-are-microformats/ What are microformats?]"<br />
*** Håkon Wium Lie (Opera) - "Cascading Markup Languages — boom!" (NEED LINK TO SLIDES)<br />
*** Rohit Khare (CommerceNet) - "[http://labs.commerce.net/~rohit/Angstro-W3C-TP/ Where Angle Brackets Fear to Tread]"<br />
*** Dan Connolly (W3C) - "[http://www.w3.org/2003/g/talk62/slides Microformats for practical Semantic Web deployment]"<br />
*** Q&A<br />
**** "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)<br />
** "Services and the Web" by Mark Nottingham (Yahoo), 12:05pm-12:10pm.<br />
*** Request to W3T/W3M: Go After The "Real" Web: Apache, PHP, Mozilla, Intermediaries and Caches, '''Microformats''', JSON... ('''emphasis''' added)<br />
** Attendees voted the "Microformats" session the best session of the Plenary Day. 6:17pm.<br />
* February 24, Yahoo Speakers Series, Yahoo Mission College Campus, 2nd floor conference room, 2821 Mission College Blvd., Santa Clara, CA 95054<br />
** [http://tantek.com/presentations/2006/02/microformats-evolution/ Microformats: Evolving the Web]<br />
* January 18, Apple Web Publishers internal meeting, Apple Computer, Star Trek conference room, 1 Infinite Loop, Cupertino, CA 95014, 12-1:40pm<br />
** [http://tantek.com/presentations/2006/01/microformats-evolution/ Microformats: Evolving the Web]<br />
* January 10, SD Forum Emerging Technologies SIG, Room H1, Cubberley Community Center, Palo Alto, CA, 7-9pm<br />
** Ryan King's presentation, Ernie Prabhakar's presentation, Rohit Khare's presentation<br />
** Microformats panel: Ryan King, Ernie Prabhakar, Rohit Khare, Tantek Çelik, Kevin Marks<br />
<br />
== 2005 ==<br />
* December 15, Syndicate Conference, San Francisco, CA<br />
** [http://tantek.com/presentations/2005/12/syndicate-microformats/ Microformats - Emerging syndication types]<br />
* November 26, [http://barcamp.org/index.cgi?TorCamp TorCamp], Teehan+Lax, 460 Richmond St. W, Toronto, ON, CA<br />
** [http://www.davidjanes.com/docs/2005.11.25%20Microformats%20Presentation.ppt powerpoints] (sorry)<br />
** [http://blog.davidjanes.com/mtarchives/2005_12.html#003467 photo]<br />
* November 12, THINK Conference, Santa Cruz room, Chaminade hotel, Santa Cruz, CA, USA<br />
** [[presentation-think-2005-11-12]]<br />
* November 10, (location unknown), by Kevin Yank of SitePoint Pty. Ltd.<br />
** [http://www.sitepoint.com/examples/innovation-on-standards/ Innovating on top of standards - Not around them]<br />
* October 5, [http://web2con.com Web 2.0 Conference], Olympic Room, Argent Hotel, San Francisco, CA, USA<br />
** [http://tantek.com/presentations/2005/10/microformats-examples/ Microformats Examples]<br />
* October 4, [http://osafoundation.org/ OSAF], San Francisco, CA, USA<br />
** [http://tantek.com/presentations/2005/10/microformats-evolution/ Microformats: Evolving the Web]<br />
* September 30, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia<br />
** [http://tantek.com/presentations/2005/09/microformats-evolution/ Microformats: Evolving the Web] (<nowiki>http://we05.com/podcast/mp3/we05-14-tantek-celik2.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 - incomplete, mirror: http://microformats.org/media/2005/09/we05-14-tantek-celik2.mp3)<br />
* September 29, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia<br />
** [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (<nowiki>http://we05.com/podcast/mp3/we05-2-tantek-celik.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 mirror: http://microformats.org/media/2005/09/we05-2-tantek-celik.mp3 )<br />
* September 25, [http://webzine2005.com/ Webzine 2005], Valhalla Room, Swedish American Hall, San Francisco, CA, USA<br />
** [http://theryanking.com/presentations/2005/webzine/ Microformats @ Webzine 2005]<br />
* September 21, Web Intelligence Conference, Compiegne, France <br />
** [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]<br />
* June 20: Supernova 2005 ([http://supernova2005.com/ Supernova2005 site]), Microformats [http://supernova2005.com/workshops.htm Workshop], Wharton West, Suite 500, San Francisco, CA, USA<br />
** "[http://tantek.com/presentations/2005/06/what-are-microformats/ What are Microformats?]"<br />
** "[http://homepage.mac.com/kevinmarks/supernovatags.html A microformat for tags]"<br />
** [http://wiki.commerce.net/wiki/ZCommerceWS#Microformats commercenet wiki page on the workshop] ([http://labs.commerce.net/wiki/index.php/ZCommerceWS#Microformats 2])<br />
* May 14: Fourteenth International World Wide Web Conference ([http://www2005.org/ WWW2005]), 2005, Microformats Dev-Day Track, Makuhari Messe Room 303, Chiba, JAPAN<br />
** "[http://tantek.com/presentations/2005/05/what-are-microformats/ What are Microformats?]" - Tantek Çelik <br />
** "[http://westciv.com/WWW2005/linkmf.html Link Microformats]" - John Allsopp<br />
** "[http://complexspiral.com/events/archive/2005/www2005/potential.html The Potential of Microformats]" - Eric Meyer<br />
** "Distributed Social Networks (XFN Implementations)"<br />
*** 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].<br />
** "[http://tantek.com/presentations/2005/05/hcard-hcalendar/ People and Events (hCard & hCalendar)]" - Tantek Çelik<br />
** "[http://cnlabs.commerce.net/~rohit/hReview-in-Review/ hReview in Review]" - Rohit Khare<br />
** "Bibliographies (hBib)" - notes captured: [[hbib-discussion-2005-05-14|hBib Discussion 2005-05-14]]<br />
** "[http://westciv.com/WWW2005/xml2mf.html a more meaningful web with microformats]"<br />
** "Semantic Web and Microformats" panel, Room 201<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* March 13<br />
** "[http://complexspiral.com/events/archive/2005/sxsw/ Emergent Semantics]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 15, Austin TX<br />
** "[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<br />
** "[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<br />
<br />
* January 21: [http://tantek.com/presentations/2005/01/attentionxml.html Attention.xml Technology Overview], private presentation, Yahoo! campus, Santa Clara, CA<br />
<br />
== 2004 ==<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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).<br />
<br />
This page was contributed from [http://developers.technorati.com/wiki/MicroFormatsPresentations the Technorati developers wiki].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40602Main Page-id2009-09-01T04:44:08Z<p>Sevenova: /* Persiapan */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[pendahuluan]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pengantar==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentasi]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep mencakup hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses). Stabilitas pada dokumen ini tidak dapat dijamin, dan pengguna harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40598Main Page-id2009-08-31T22:02:18Z<p>Sevenova: /* Persiapan */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[pendahuluan]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pengantar==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[penyajian]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep mencakup hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses). Stabilitas pada dokumen ini tidak dapat dijamin, dan pengguna harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=penyajian&diff=40597penyajian2009-08-31T22:00:52Z<p>Sevenova: New page: {{TOC-right}} This page lists various presentations, sessions, papers and posters which have provided explanations and discusions of both microformats in general, and specific microfor...</p>
<hr />
<div>{{TOC-right}}<br />
This page lists various presentations, sessions, papers and posters which have provided explanations and discusions of both [[microformats]] in general, and specific microformats. Check out microformats [[events]] for upcoming presentations. See also microformats [[podcasts]] and [[screencasts]] for audio/video presentations and discussions.<br />
<br />
'''Note: This page is missing a lot of presentation links.''' More presentation links can be found by going through specific [[events]] pages.<br />
<br />
Most recent presentations/sessions listed first.<br />
<br />
== 2009 ==<br />
* 2009-06-03 <cite lang="pt">[http://e.yq.sl.pt/ Microformatos - 2009 - Juntando as Peças do Puzzle]</cite> by [http://twitter.com/andr3 André Luís] at SAPO Sessions ([http://twitter.com/andr3/status/2017551933 as tweeted by @andr3])<br />
<br />
* 2009-03-12 [http://csarven.ca/presentations/microformats-06/ microformats: #towerofbabel #pareto #dataportability] presentation by [[User:Csarven|Sarven Capadisli]] at [http://mcgill.ca GLIS 663 Knowledge Taxonomies, McGill], Montr&#233;al, Canada<br />
<br />
* 2009-03-05 [http://csarven.ca/presentations/microformats-05/ Website data through the looking-glass] presentation by [[User:Csarven|Sarven Capadisli]] at [http://conf.phpquebec.com PHP Québec Conference 2009], Montr&#233;al, Canada<br />
<br />
* 2009-01-08 [http://csarven.ca/presentations/microformats-04/ Interacting with microformats] presentation by [[User:Csarven|Sarven Capadisli]] at [http://phpquebec.org PHP Qu&#233;bec Monthly Meetup], Montr&#233;al, Canada<br />
<br />
== 2008 ==<br />
* 2008-11-18 [http://cdharrison.com/presentations/microformats/ microformats: What are they and why should you use them?] during [http://refreshaugusta.com/ RefreshAugusta] at PowerServe, Augusta, Georgia.<br />
* 2008-09-05 [http://tantek.com/presentations/2008/09/social-network-portability Social Network Portability] during [[events/2008-09-05-dconstruct-social-network-portability|dConstruct 2008]].<br />
* 2008-08-19 [http://tantek.com/presentations/2008/08/microformats Better User Experience Through Microformats] during day 2 of [[events/2008-08-19-better-user-experience|An Event Apart San Francisco]].<br />
* 2008-08-16 [http://tantek.com/presentations/2008/08/wordpress-microformats/ WordPress and Microformats: Past, Present, Future] during [[events/2008-08-16-wordcamp|WordCamp 2008]]<br />
* 2008-07-02 [http://www.slideshare.net/andr3/microformatos-pequenas-peas-do-puzzle Microformatos - pequenças peças do puzzle] presentation in Portuguese, by André Luís for a training session at SAPO.pt (Lisbon, Portugal)<br />
* 2008-05-15 [http://csarven.ca/presentations/microformats-03/ Creating next generation Web sites] presentation by [[User:Csarven|Sarven Capadisli]] at [http://www.nstein.com/summit2008/ Nstein Innovation Leaders Summit 2008], Montreal, Canada<br />
* 2008-04-16 [http://slideshow.rubyforge.org/microformats.html Microformats - Adding Semantics to Your Web Site - Web 3.0 in Action] presentation by Gerald Bauer (Vancouver Software Developers Network/VanDev at University of British Columbia)<br />
* 2008-03-17 [http://csarven.ca/presentations/microformats-02/ Microformats overview: how to help machines recognise common data formats in Web documents] presentation by [[User:Csarven|Sarven Capadisli]] at [http://station-c.com/ Coder's Saturday], Montreal, Canada<br />
* 2008-02-19 [http://www.glennjones.net/Post/835/SemanticCampLondon.htm Can your website be your API and real life] presentation by Glenn Jones (Semantic Camp London) covers social network portability and date portability<br />
* 2008-02-19 [http://www.slideshare.net/garethr/parsing-microformats Parsing Microformats] presentation by Gareth Rushgrove (Semantic Camp London) includes an overview of available parsers<br />
<br />
== 2007 ==<br />
* 2007-11-17 [http://www.slideshare.net/56k/mromanello-ecal-presentation Linking Text References to Relevant Digital Resources Over The Web (Proposal of a Microformat for Canonical Texts References)] presentation by Matteo Romanello at [http://enlil.ff.cuni.cz/ecal Electronic Corpora of Ancient Languages] conference held in Prague on November 2007.<br />
* 2007-11-06 [http://www.slideshare.net/guest897d73/microformats-a-web-of-data Microformats: A Web of Data] presentation by Brian Suda at [[events/2007-11-06-microfomats-a-web-of-data|Web 2.0 Expo Berlin]].<br />
* 2007-10-31 [http://video.google.com/videoplay?docid=4912491017216716477 Microformats - The What, Where, Why and How] This is a recording of a presentation given by Mark Meeker on Microformats. Mark is an Architect on the UI Engineering team at Orbitz Worldwide. OrbitzTech talk Chicago Il.<br />
* 2007-10-04 [http://tantek.com/presentations/2007/10/social-network-portability/ Social Network Portability] presentation by Tantek Çelik at [[events/2007-10-04-fundamentos-web-social-network-portability|Fundamentos Web 2007]].<br />
* 2007-10-04 [http://www.slideshare.net/mattb/coding-on-the-shoulders-of-giants Coding on the Shoulders of Giants] presentation by Matt Biddulph at [[events/2007-10-04-future-of-web-apps|Future of Web Apps London 2007]] - mentions their implementation of hCard, hCalendar and how their support gives them more features.<br />
* 2007-10-02 [http://www.slideshare.net/cgriego/microformats-building-blocks-of-the-semantic-web/ Microformats, building blocks of the semantic web] presentation by Chris Griego at [[events/2007-10-02-dallas-ruby-brigade|Dallas Ruby Brigade October 2007]]<br />
* 2007-08-30 GeekUp presentation by [http://www.ts0.com Thom Shannon] - [http://www.ts0.com/2007/09/microformats-whats-point.asp Microformats: What's the point?]<br />
* 2007-06-.. http://tantek.com/presentations/2007/06/microformats-bb-you/<br />
* 2007-05-.. http://tantek.com/presentations/2007/05/microformats-bb-you/<br />
* 2007-06-02 BarCamp San Diego presentation by Joshua Brewer: [http://www.slideshare.net/jbrewer/barcamp-sd-microformats Microformats: Building a Better Web].<br />
* 2007-05-16 [[events/2007-05-16-XTech|XTech 2007]] presentation by Jeremy Keith: [http://adactio.com/extras/slides/nanotech.pdf Microformats: the nanotechnology of the semantic web].<br />
* 2007-04-30 [[events/2007-04-30-mix07|Microformats: Data Formats That Put Humans First]] [http://tantek.com/presentations/2007/04/microformats/ presentation by Tantek Çelik]<br />
* 2007-03-23 [[events/2007-03-23-stanford|Microformats at Stanford]] [http://tantek.com/presentations/2007/03/microformats/ presentation by Tantek Çelik]<br />
* 2007-03-22 [http://www.webdu.com.au/go/session/microformats--hidden-treasures Microformats—the hidden treasure] by Dmitry Baranovskiy at the [http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia, 3:00pm–4:00pm<br />
* 2007-03-16 [http://www.afroginthevalley.com/fr/2007/03/16/presentation-microformats-a-php-quebec/ Métadonnées pour Humains & Machines] (dead link ?) presentation in French by Sylvain Carle at the [http://conf.phpquebec.com/fr/archive/conf2007/ PHP Québec 2007] conference in Montréal, Canada.<br />
* 2007-02-23 [http://bluesmoon.info/talks/microformats/ Microformats at the CSI Web 2.0 Conference in Bangalore] presentation by Philip Tellis<br />
* 2007-02-19, [http://www.glennjones.net/Post/825/DestroyingWalledGardens-MicroformatssyndicationandAPI%e2%80%99s.htm Destroying Walled Gardens - Microformats syndication and API’s] at [http://barcamp.org/BarCampLondon2 BarCamp London 2], UK by Glenn Jones<br />
* 2007-02-13, [http://groups.google.com/group/bristolskillswap/web/february-skillswap-microformats Microformats: The Semantic Web for the Rest of Us] Bristol Skillswap [rtsp://stream.watershed.co.uk/skillswap/2007.02.13.microformats.mov Streaming Video]<br />
* 2007-02-07, [http://north.webdirections.org Web Directions North 2007], [http://north.webdirections.org/detail/venue/ Renaissance Vancouver Hotel Harbourside], 1133 West Hastings Street, Vancouver, British Columbia, V6E3T3, Canada<br />
** [[events/2007-02-07-web-directions-north|Microformats at Web Directions North 2007]], 11:45am-12:45pm, 1:45pm-3:45pm<br />
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2007/02/microformats/ Microformats — The Big Picture]"<br />
*** John Allsopp (Westciv) - "[http://north07.webdirections.org/presentations/MicroformatsForDevelopers.pdf Microformats For Developers]"<br />
*** Dan Cederholm (Simplebits) - "[http://north07.webdirections.org/presentations/MicroformatsForDesigners.pdf Microformats For Designers]"<br />
* 2007-02-03 [http://www.glennjones.net/Post/823/Microformats%2ctheAK-47oftheweb-WebDD.htm Microformats HTML to API] at [http://www.webdd.org.uk/ WebDD], Reading UK by Glenn Jones<br />
<br />
== 2006 ==<br />
* 2006-11-24, Taichi Kaminogoya presented to [http://2xup.org/log/2006/11/27-2219 microformats に触れてみよう] at [http://www.asahi-net.or.jp/~eb2m-mrt/kaihatsu9.html XML Developers' Day #9], Tokyo, JAPAN.<br />
* October 28th, [http://www.keepthebyte.ch/2006/10/microformats-speech-at-barcamp-zurich.html Microformats Speech at Barcamp Zurich]<br />
* October 10th, Taichi Kaminogoya presented to [http://2xup.org/log/2006/10/10-1800 microformatsがもたらすドキドキする未来] at [http://lp1.cssnite.jp/ CSS Nite LP Disk 1], Tokyo, JAPAN.<br />
* September 28th, [http://www.webdirections.org/microformats/ Microformats] at Web Directions South, Sydney Australia by John Allsopp. [http://www.webdirections.org/microformats/ slides, podcast, live blogging transcript all online now]<br />
* September 27th, [http://tantek.com/presentations/2006/09/microformats-intro/ Microformats Intro] at New Context 2006, Radisson Miyako Hotel, Minato-ku, Tokyo, JAPAN. See also [http://flickr.com/photos/tags/microformatsnewcontext2006 photos].<br />
* September 16th, [http://fredericdevillamil.com/presentations/2006/que-sont-les-microformats/index.html Introducing Microformats for resume publishing] in French by Frederic de Villamil at Barcamp Paris 4. Location: 43 rue d'Aboukir, 75002 Paris France<br />
* September 13th, [http://tantek.com/presentations/2006/09/microformats-practices/ Microformats Practices] at [[events/2006-09-13-future-of-web-apps-microformats|Future of Web Apps]] in San Francisco. Location: Palace of Fine Arts Theatre, Lyon Street, San Francisco CA 94123.<br />
* September 3th, Backnetwork and Microformats by Glenn Jones at Barcamp London. demo of hCard subscription idea for social networks. <br />
* 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].<br />
* 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]]<br />
* 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<br />
* June 15th, Phil Wilson presented to the [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ Institutional Web Management Workshop]<br />
* June 8, Pete Prodoehl presented [http://rasterweb.net/raster/presentations/microformats-20060608/ Microformats] to the Milwaukee Web Design Meetup Group<br />
* 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.<br />
* 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)<br />
* May 24, Kevin Lawver presented [http://presentations.lawver.net/standards/a_microformat_and_proposal_for/ A Microformat and Proposal For Interoperable Widgets]<br />
* 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]).<br />
* 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]<br />
* May 16, [http://theryanking.com/presentations/2006/xtech/tutorial/ Microformats from the Ground Up] by Brian Suda and Ryan King @ XTech 2006<br />
* 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]).<br />
* 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)<br />
* 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])<br />
* 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<br />
** Building with MicroFormats, [http://www.chaddickerson.com/blog/2006/03/17/reading-20-and-microformats/ Chad Dickerson], Yahoo <br />
* March 13, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX<br />
** [[events/2006-03-13-sxsw-microformats|Microformats: Evolving the Web]], 11:30am-12:30pm <br />
* March 11, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX<br />
** [http://tantek.com/presentations/2006/03/building-blocks Creating Building Blocks For Independents], 5pm-6pm<br />
** [http://flickr.com/photos/tags/microformatssxsw photos]<br />
* March 7, O'Reilly Emerging Technologies (ETech) Conference, Manchester Grand Hyatt, Ballroom, San Diego, CA<br />
** [[events/2006-03-07-etech-microformats|Microformats intro and lightning demos at O'Reilly ETech conf.]], 5:30pm-6:15pm <br />
** [http://flickr.com/photos/tags/microformatsetech photos]<br />
* 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<br />
** [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Technical Plenary Day]], 10:30am-11:30am<br />
*** Ian Hickson (Google) - "A billion documents and no semantics anywhere" (NEED LINK TO SLIDES OR STUDY)<br />
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2006/03/what-are-microformats/ What are microformats?]"<br />
*** Håkon Wium Lie (Opera) - "Cascading Markup Languages — boom!" (NEED LINK TO SLIDES)<br />
*** Rohit Khare (CommerceNet) - "[http://labs.commerce.net/~rohit/Angstro-W3C-TP/ Where Angle Brackets Fear to Tread]"<br />
*** Dan Connolly (W3C) - "[http://www.w3.org/2003/g/talk62/slides Microformats for practical Semantic Web deployment]"<br />
*** Q&A<br />
**** "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)<br />
** "Services and the Web" by Mark Nottingham (Yahoo), 12:05pm-12:10pm.<br />
*** Request to W3T/W3M: Go After The "Real" Web: Apache, PHP, Mozilla, Intermediaries and Caches, '''Microformats''', JSON... ('''emphasis''' added)<br />
** Attendees voted the "Microformats" session the best session of the Plenary Day. 6:17pm.<br />
* February 24, Yahoo Speakers Series, Yahoo Mission College Campus, 2nd floor conference room, 2821 Mission College Blvd., Santa Clara, CA 95054<br />
** [http://tantek.com/presentations/2006/02/microformats-evolution/ Microformats: Evolving the Web]<br />
* January 18, Apple Web Publishers internal meeting, Apple Computer, Star Trek conference room, 1 Infinite Loop, Cupertino, CA 95014, 12-1:40pm<br />
** [http://tantek.com/presentations/2006/01/microformats-evolution/ Microformats: Evolving the Web]<br />
* January 10, SD Forum Emerging Technologies SIG, Room H1, Cubberley Community Center, Palo Alto, CA, 7-9pm<br />
** Ryan King's presentation, Ernie Prabhakar's presentation, Rohit Khare's presentation<br />
** Microformats panel: Ryan King, Ernie Prabhakar, Rohit Khare, Tantek Çelik, Kevin Marks<br />
<br />
== 2005 ==<br />
* December 15, Syndicate Conference, San Francisco, CA<br />
** [http://tantek.com/presentations/2005/12/syndicate-microformats/ Microformats - Emerging syndication types]<br />
* November 26, [http://barcamp.org/index.cgi?TorCamp TorCamp], Teehan+Lax, 460 Richmond St. W, Toronto, ON, CA<br />
** [http://www.davidjanes.com/docs/2005.11.25%20Microformats%20Presentation.ppt powerpoints] (sorry)<br />
** [http://blog.davidjanes.com/mtarchives/2005_12.html#003467 photo]<br />
* November 12, THINK Conference, Santa Cruz room, Chaminade hotel, Santa Cruz, CA, USA<br />
** [[presentation-think-2005-11-12]]<br />
* November 10, (location unknown), by Kevin Yank of SitePoint Pty. Ltd.<br />
** [http://www.sitepoint.com/examples/innovation-on-standards/ Innovating on top of standards - Not around them]<br />
* October 5, [http://web2con.com Web 2.0 Conference], Olympic Room, Argent Hotel, San Francisco, CA, USA<br />
** [http://tantek.com/presentations/2005/10/microformats-examples/ Microformats Examples]<br />
* October 4, [http://osafoundation.org/ OSAF], San Francisco, CA, USA<br />
** [http://tantek.com/presentations/2005/10/microformats-evolution/ Microformats: Evolving the Web]<br />
* September 30, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia<br />
** [http://tantek.com/presentations/2005/09/microformats-evolution/ Microformats: Evolving the Web] (<nowiki>http://we05.com/podcast/mp3/we05-14-tantek-celik2.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 - incomplete, mirror: http://microformats.org/media/2005/09/we05-14-tantek-celik2.mp3)<br />
* September 29, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia<br />
** [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (<nowiki>http://we05.com/podcast/mp3/we05-2-tantek-celik.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 mirror: http://microformats.org/media/2005/09/we05-2-tantek-celik.mp3 )<br />
* September 25, [http://webzine2005.com/ Webzine 2005], Valhalla Room, Swedish American Hall, San Francisco, CA, USA<br />
** [http://theryanking.com/presentations/2005/webzine/ Microformats @ Webzine 2005]<br />
* September 21, Web Intelligence Conference, Compiegne, France <br />
** [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]<br />
* June 20: Supernova 2005 ([http://supernova2005.com/ Supernova2005 site]), Microformats [http://supernova2005.com/workshops.htm Workshop], Wharton West, Suite 500, San Francisco, CA, USA<br />
** "[http://tantek.com/presentations/2005/06/what-are-microformats/ What are Microformats?]"<br />
** "[http://homepage.mac.com/kevinmarks/supernovatags.html A microformat for tags]"<br />
** [http://wiki.commerce.net/wiki/ZCommerceWS#Microformats commercenet wiki page on the workshop] ([http://labs.commerce.net/wiki/index.php/ZCommerceWS#Microformats 2])<br />
* May 14: Fourteenth International World Wide Web Conference ([http://www2005.org/ WWW2005]), 2005, Microformats Dev-Day Track, Makuhari Messe Room 303, Chiba, JAPAN<br />
** "[http://tantek.com/presentations/2005/05/what-are-microformats/ What are Microformats?]" - Tantek Çelik <br />
** "[http://westciv.com/WWW2005/linkmf.html Link Microformats]" - John Allsopp<br />
** "[http://complexspiral.com/events/archive/2005/www2005/potential.html The Potential of Microformats]" - Eric Meyer<br />
** "Distributed Social Networks (XFN Implementations)"<br />
*** 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].<br />
** "[http://tantek.com/presentations/2005/05/hcard-hcalendar/ People and Events (hCard & hCalendar)]" - Tantek Çelik<br />
** "[http://cnlabs.commerce.net/~rohit/hReview-in-Review/ hReview in Review]" - Rohit Khare<br />
** "Bibliographies (hBib)" - notes captured: [[hbib-discussion-2005-05-14|hBib Discussion 2005-05-14]]<br />
** "[http://westciv.com/WWW2005/xml2mf.html a more meaningful web with microformats]"<br />
** "Semantic Web and Microformats" panel, Room 201<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* March 13<br />
** "[http://complexspiral.com/events/archive/2005/sxsw/ Emergent Semantics]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 15, Austin TX<br />
** "[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<br />
** "[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<br />
<br />
* January 21: [http://tantek.com/presentations/2005/01/attentionxml.html Attention.xml Technology Overview], private presentation, Yahoo! campus, Santa Clara, CA<br />
<br />
== 2004 ==<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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<br />
<br />
* 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).<br />
<br />
This page was contributed from [http://developers.technorati.com/wiki/MicroFormatsPresentations the Technorati developers wiki].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40595Main Page-id2009-08-31T21:57:59Z<p>Sevenova: </p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[pendahuluan]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pengantar==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep mencakup hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses). Stabilitas pada dokumen ini tidak dapat dijamin, dan pengguna harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40594pendahuluan2009-08-31T21:56:31Z<p>Sevenova: /* Lihat juga */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah salah satu cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi pada halaman web sehingga informasi di dalamnya dapat diekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, bertukaran-referensi, atau dikombinasi.<br />
<br />
Secara teknis, hal-hal tersebut adalah bagian dari penandaan semantik yang hanya menggunakan standar "Plain Old Semantic (X)HTML" (yaitu "[[POSH]]") saja dengan nilai "rel" dan satu set [[class-names|penamaan-kelas]] yang umum. Mereka digunakan dengan terbuka dan tersedia, bebas bagi siapa saja.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats adalah karya sederhana dimana pertimbangan karya kompleks sebelumnya telah membuat banyak kesalahan. Satu persamaan yang dapat ditarik adalah REST layanan di dunia web - untuk lebih memahami [[suggested-reading#REST|bacaan yang disarankan untuk REST]].<br />
<br />
* Lihat juga: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] oleh Justin Leavesley<br />
<br />
==Lihat juga==<br />
* Daftar [[notable-users|some notable users]].<br />
* Interview [[press|pers]] dan [[articles|artikel]] terbaru juga bisa menjadi pengantar yang bagus.<br />
* Lihat [[presentations|presentasi]] Microformats untuk mengetahui latar belakang dan bahan pengantar pada [[Microformats]].<br />
* Dengarkan [[podcasts]] tentang Microformats.<br />
* Baca [[faq|FAQs]] sebagai pernyataan Microformat secara umum.<br />
* Kemudian [[suggested-reading|sarankan pembaca]]<br />
* [[implement|Apakah Anda ingin mengimplementasikan Microformats?]]<br />
* [[presentations|presentasi]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== Pranala luar ==<br />
* Sitepoint memiliki tutorial pengantar yang bagus: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar telah menulis: [http://premasagar.com/microformats/compound/ some nice microformats examples with source]..</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40593pendahuluan2009-08-31T21:55:35Z<p>Sevenova: /* Lihat juga */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah salah satu cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi pada halaman web sehingga informasi di dalamnya dapat diekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, bertukaran-referensi, atau dikombinasi.<br />
<br />
Secara teknis, hal-hal tersebut adalah bagian dari penandaan semantik yang hanya menggunakan standar "Plain Old Semantic (X)HTML" (yaitu "[[POSH]]") saja dengan nilai "rel" dan satu set [[class-names|penamaan-kelas]] yang umum. Mereka digunakan dengan terbuka dan tersedia, bebas bagi siapa saja.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats adalah karya sederhana dimana pertimbangan karya kompleks sebelumnya telah membuat banyak kesalahan. Satu persamaan yang dapat ditarik adalah REST layanan di dunia web - untuk lebih memahami [[suggested-reading#REST|bacaan yang disarankan untuk REST]].<br />
<br />
* Lihat juga: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] oleh Justin Leavesley<br />
<br />
==Lihat juga==<br />
* Daftar [[notable-users|some notable users]].<br />
* Interview [[press|pers]] dan [[articles|artikel]] terbaru juga bisa menjadi pengantar yang bagus.<br />
* See microformat presentations for more background and introductory material on microformats. <br />
<br />
* Lihat [[presentations|presentasi]] Microformats untuk mengetahui latar belakang dan bahan pengantar pada [[Microformats]].<br />
* Dengarkan [[podcasts]] tentang Microformats.<br />
* Baca [[faq|FAQs]] sebagai pernyataan Microformat secara umum.<br />
* Kemudian [[suggested-reading|sarankan pembaca]]<br />
* [[implement|Apakah Anda ingin mengimplementasikan Microformats?]]<br />
* [[presentations|presentasi]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== Pranala luar ==<br />
* Sitepoint memiliki tutorial pengantar yang bagus: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar telah menulis: [http://premasagar.com/microformats/compound/ some nice microformats examples with source]..</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40592pendahuluan2009-08-31T21:52:33Z<p>Sevenova: /* Lihat juga */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah salah satu cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi pada halaman web sehingga informasi di dalamnya dapat diekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, bertukaran-referensi, atau dikombinasi.<br />
<br />
Secara teknis, hal-hal tersebut adalah bagian dari penandaan semantik yang hanya menggunakan standar "Plain Old Semantic (X)HTML" (yaitu "[[POSH]]") saja dengan nilai "rel" dan satu set [[class-names|penamaan-kelas]] yang umum. Mereka digunakan dengan terbuka dan tersedia, bebas bagi siapa saja.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats adalah karya sederhana dimana pertimbangan karya kompleks sebelumnya telah membuat banyak kesalahan. Satu persamaan yang dapat ditarik adalah REST layanan di dunia web - untuk lebih memahami [[suggested-reading#REST|bacaan yang disarankan untuk REST]].<br />
<br />
* Lihat juga: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] oleh Justin Leavesley<br />
<br />
==Lihat juga==<br />
* Daftar [[notable-users|beberapa pengguna terkenal]].<br />
* Interview [[press|pers]] dan [[articles|artikel]] terbaru juga bisa menjadi pengantar yang bagus.<br />
* See microformat presentations for more background and introductory material on microformats. <br />
<br />
* Lihat [[presentations|presentasi]] Microformats untuk mengetahui latar belakang dan bahan pengantar pada [[Microformats]].<br />
* Dengarkan [[podcasts]] tentang Microformats.<br />
* Baca [[faq|FAQs]] sebagai pernyataan Microformat secara umum.<br />
* Kemudian [[suggested-reading|sarankan pembaca]]<br />
* [[implement|Apakah Anda ingin mengimplementasikan Microformats?]]<br />
* [[presentations|presentasi]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== Pranala luar ==<br />
* Sitepoint memiliki tutorial pengantar yang bagus: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar telah menulis: [http://premasagar.com/microformats/compound/ some nice microformats examples with source]..</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40591pendahuluan2009-08-31T21:50:56Z<p>Sevenova: /* Lihat juga */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah salah satu cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi pada halaman web sehingga informasi di dalamnya dapat diekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, bertukaran-referensi, atau dikombinasi.<br />
<br />
Secara teknis, hal-hal tersebut adalah bagian dari penandaan semantik yang hanya menggunakan standar "Plain Old Semantic (X)HTML" (yaitu "[[POSH]]") saja dengan nilai "rel" dan satu set [[class-names|penamaan-kelas]] yang umum. Mereka digunakan dengan terbuka dan tersedia, bebas bagi siapa saja.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats adalah karya sederhana dimana pertimbangan karya kompleks sebelumnya telah membuat banyak kesalahan. Satu persamaan yang dapat ditarik adalah REST layanan di dunia web - untuk lebih memahami [[suggested-reading#REST|bacaan yang disarankan untuk REST]].<br />
<br />
* Lihat juga: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] oleh Justin Leavesley<br />
<br />
==Lihat juga==<br />
* Daftar [[notable-users|some notable users]].<br />
* Interview [[press|pers]] and [[articles|artikel]] terbaru juga bisa menjadi pengantar yang bagus.<br />
* See microformat presentations for more background and introductory material on microformats. <br />
<br />
* Lihat [[presentations|presentasi]] Microformats untuk mengetahui latar belakang dan bahan pengantar pada [[Microformats]].<br />
* Dengarkan [[podcasts]] tentang Microformats.<br />
* Baca [[faq|FAQs]] sebagai pernyataan Microformat secara umum.<br />
* Kemudian [[suggested-reading|sarankan pembaca]]<br />
* [[implement|Apakah Anda ingin mengimplementasikan Microformats?]]<br />
* [[presentations|presentasi]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== Pranala luar ==<br />
* Sitepoint memiliki tutorial pengantar yang bagus: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar telah menulis: [http://premasagar.com/microformats/compound/ some nice microformats examples with source]..</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40588pendahuluan2009-08-31T21:39:05Z<p>Sevenova: /* Seruan untuk sederhana */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah salah satu cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi pada halaman web sehingga informasi di dalamnya dapat diekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, bertukaran-referensi, atau dikombinasi.<br />
<br />
Secara teknis, hal-hal tersebut adalah bagian dari penandaan semantik yang hanya menggunakan standar "Plain Old Semantic (X)HTML" (yaitu "[[POSH]]") saja dengan nilai "rel" dan satu set [[class-names|penamaan-kelas]] yang umum. Mereka digunakan dengan terbuka dan tersedia, bebas bagi siapa saja.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats adalah karya sederhana dimana pertimbangan karya kompleks sebelumnya telah membuat banyak kesalahan. Satu persamaan yang dapat ditarik adalah REST layanan di dunia web - untuk lebih memahami [[suggested-reading#REST|bacaan yang disarankan untuk REST]].<br />
<br />
* Lihat juga: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] oleh Justin Leavesley<br />
<br />
==Lihat juga==<br />
* Daftar [[notable-users|some notable users]].<br />
* Interview [[press|pers]] and [[articles|artikel]] terbaru juga bisa menjadi pengantar yang bagus.<br />
* Lihat [[presentations|presentasi]] Microformats for more background and introductory material on [[microformats]].<br />
* Listen to [[podcasts]] about microformats.<br />
* Read the [[faq|FAQs]] for general microformat queries.<br />
* More [[suggested-reading|suggested reading]]<br />
* [[implement|So you want to implement microformats?]]<br />
* [[presentations]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== Pranala luar ==<br />
* Sitepoint memiliki tutorial pengantar yang bagus: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar telah menulis: [http://premasagar.com/microformats/compound/ some nice microformats examples with source]..</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40585pendahuluan2009-08-31T21:07:00Z<p>Sevenova: /* Pranala Luar */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah salah satu cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi pada halaman web sehingga informasi di dalamnya dapat diekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, bertukaran-referensi, atau dikombinasi.<br />
<br />
Secara teknis, hal-hal tersebut adalah bagian dari penandaan semantik yang hanya menggunakan standar "Plain Old Semantic (X)HTML" (yaitu "[[POSH]]") saja dengan nilai "rel" dan satu set [[class-names|penamaan-kelas]] yang umum. Mereka digunakan dengan terbuka dan tersedia, bebas bagi siapa saja.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world - for more on REST see [[suggested-reading#REST|suggested reading on REST]].<br />
* See: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley<br />
<br />
==Lihat juga==<br />
* Daftar [[notable-users|some notable users]].<br />
* Interview [[press|pers]] and [[articles|artikel]] terbaru juga bisa menjadi pengantar yang bagus.<br />
* Lihat [[presentations|presentasi]] Microformats for more background and introductory material on [[microformats]].<br />
* Listen to [[podcasts]] about microformats.<br />
* Read the [[faq|FAQs]] for general microformat queries.<br />
* More [[suggested-reading|suggested reading]]<br />
* [[implement|So you want to implement microformats?]]<br />
* [[presentations]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== Pranala luar ==<br />
* Sitepoint memiliki tutorial pengantar yang bagus: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar telah menulis: [http://premasagar.com/microformats/compound/ some nice microformats examples with source]..</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40580pendahuluan2009-08-31T19:15:41Z<p>Sevenova: /* Lihat juga */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah salah satu cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi pada halaman web sehingga informasi di dalamnya dapat diekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, bertukaran-referensi, atau dikombinasi.<br />
<br />
Secara teknis, hal-hal tersebut adalah bagian dari penandaan semantik yang hanya menggunakan standar "Plain Old Semantic (X)HTML" (yaitu "[[POSH]]") saja dengan nilai "rel" dan satu set [[class-names|penamaan-kelas]] yang umum. Mereka digunakan dengan terbuka dan tersedia, bebas bagi siapa saja.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world - for more on REST see [[suggested-reading#REST|suggested reading on REST]].<br />
* See: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley<br />
<br />
==Lihat juga==<br />
* Daftar [[notable-users|some notable users]].<br />
* Interview [[press|pers]] and [[articles|artikel]] terbaru juga bisa menjadi pengantar yang bagus.<br />
* Lihat [[presentations|presentasi]] Microformats for more background and introductory material on [[microformats]].<br />
* Listen to [[podcasts]] about microformats.<br />
* Read the [[faq|FAQs]] for general microformat queries.<br />
* More [[suggested-reading|suggested reading]]<br />
* [[implement|So you want to implement microformats?]]<br />
* [[presentations]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== Pranala Luar ==<br />
* Sitepoint memiliki tutorial pengantar yang bagus: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar telah menulis: [http://premasagar.com/microformats/compound/ some nice microformats examples with source]..</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40578pendahuluan2009-08-31T19:11:24Z<p>Sevenova: /* external */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah salah satu cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi pada halaman web sehingga informasi di dalamnya dapat diekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, bertukaran-referensi, atau dikombinasi.<br />
<br />
Secara teknis, hal-hal tersebut adalah bagian dari penandaan semantik yang hanya menggunakan standar "Plain Old Semantic (X)HTML" (yaitu "[[POSH]]") saja dengan nilai "rel" dan satu set [[class-names|penamaan-kelas]] yang umum. Mereka digunakan dengan terbuka dan tersedia, bebas bagi siapa saja.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world - for more on REST see [[suggested-reading#REST|suggested reading on REST]].<br />
* See: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley<br />
<br />
==Lihat juga==<br />
* A list of [[notable-users|some notable users]].<br />
* Recent [[press]] interviews and [[articles]] are also a good introduction.<br />
* See microformat [[presentations]] for more background and introductory material on [[microformats]].<br />
* Listen to [[podcasts]] about microformats.<br />
* Read the [[faq|FAQs]] for general microformat queries.<br />
* More [[suggested-reading|suggested reading]]<br />
* [[implement|So you want to implement microformats?]]<br />
* [[presentations]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== Pranala Luar ==<br />
* Sitepoint memiliki tutorial pengantar yang bagus: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar telah menulis: [http://premasagar.com/microformats/compound/ some nice microformats examples with source]..</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40576pendahuluan2009-08-31T19:02:44Z<p>Sevenova: /* Apakah Microformats itu? */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah salah satu cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi pada halaman web sehingga informasi di dalamnya dapat diekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, bertukaran-referensi, atau dikombinasi.<br />
<br />
Secara teknis, hal-hal tersebut adalah bagian dari penandaan semantik yang hanya menggunakan standar "Plain Old Semantic (X)HTML" (yaitu "[[POSH]]") saja dengan nilai "rel" dan satu set [[class-names|penamaan-kelas]] yang umum. Mereka digunakan dengan terbuka dan tersedia, bebas bagi siapa saja.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world - for more on REST see [[suggested-reading#REST|suggested reading on REST]].<br />
* See: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley<br />
<br />
==Lihat juga==<br />
* A list of [[notable-users|some notable users]].<br />
* Recent [[press]] interviews and [[articles]] are also a good introduction.<br />
* See microformat [[presentations]] for more background and introductory material on [[microformats]].<br />
* Listen to [[podcasts]] about microformats.<br />
* Read the [[faq|FAQs]] for general microformat queries.<br />
* More [[suggested-reading|suggested reading]]<br />
* [[implement|So you want to implement microformats?]]<br />
* [[presentations]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== external ==<br />
* Sitepoint has a nice introductory tutorial: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar has written up [http://premasagar.com/microformats/compound/ some nice microformats examples with source].</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40535pendahuluan2009-08-30T18:06:30Z<p>Sevenova: /* See also */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi, pada halaman web sehingga informasi di dalamnya dapat di ekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, pertukaran-referensi, atau dikombinasi.<br />
<br />
More technically, they are items of semantic markup, using just standard "plain old semantic (X)HTML" (i.e. "[[POSH]]") with a set of common [[class-names]] and "[[rel]]" values. They are open and available, freely, for anyone to use.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world - for more on REST see [[suggested-reading#REST|suggested reading on REST]].<br />
* See: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley<br />
<br />
==Lihat juga==<br />
* A list of [[notable-users|some notable users]].<br />
* Recent [[press]] interviews and [[articles]] are also a good introduction.<br />
* See microformat [[presentations]] for more background and introductory material on [[microformats]].<br />
* Listen to [[podcasts]] about microformats.<br />
* Read the [[faq|FAQs]] for general microformat queries.<br />
* More [[suggested-reading|suggested reading]]<br />
* [[implement|So you want to implement microformats?]]<br />
* [[presentations]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== external ==<br />
* Sitepoint has a nice introductory tutorial: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar has written up [http://premasagar.com/microformats/compound/ some nice microformats examples with source].</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40534pendahuluan2009-08-30T18:06:09Z<p>Sevenova: /* The Appeal to Simplicity */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi, pada halaman web sehingga informasi di dalamnya dapat di ekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, pertukaran-referensi, atau dikombinasi.<br />
<br />
More technically, they are items of semantic markup, using just standard "plain old semantic (X)HTML" (i.e. "[[POSH]]") with a set of common [[class-names]] and "[[rel]]" values. They are open and available, freely, for anyone to use.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== Seruan untuk sederhana ==<br />
<br />
* Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world - for more on REST see [[suggested-reading#REST|suggested reading on REST]].<br />
* See: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley<br />
<br />
==See also==<br />
* A list of [[notable-users|some notable users]].<br />
* Recent [[press]] interviews and [[articles]] are also a good introduction.<br />
* See microformat [[presentations]] for more background and introductory material on [[microformats]].<br />
* Listen to [[podcasts]] about microformats.<br />
* Read the [[faq|FAQs]] for general microformat queries.<br />
* More [[suggested-reading|suggested reading]]<br />
* [[implement|So you want to implement microformats?]]<br />
* [[presentations]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== external ==<br />
* Sitepoint has a nice introductory tutorial: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar has written up [http://premasagar.com/microformats/compound/ some nice microformats examples with source].</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40533pendahuluan2009-08-30T18:05:08Z<p>Sevenova: /* Why Microformats */</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi, pada halaman web sehingga informasi di dalamnya dapat di ekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, pertukaran-referensi, atau dikombinasi.<br />
<br />
More technically, they are items of semantic markup, using just standard "plain old semantic (X)HTML" (i.e. "[[POSH]]") with a set of common [[class-names]] and "[[rel]]" values. They are open and available, freely, for anyone to use.<br />
<br />
== Mengapa Microformats ==<br />
<br />
Mengapa kita menghadirkan Microformats?<br />
<br />
Singkatnya, Microformats adalah konvergensi dari sejumlah tren:<br />
# langkah logis berikutnya dalam evolusi desain web dan informasi arsitektur<br />
# cara manusia dan organisasi untuk mempublikasikan informasi yang lebih beragam dengan sendirinya, tanpa harus bergantung pada layanan terpusat<br />
# pengakuan bahwa (di luar area <span class="notspam">spesialis</span>) upaya metadata "tradisional" memiliki kegagalan atau akan memakan banyak waktu untuk mengumpulkannya dengan berbagi adopsi apapun, oleh karena itu pendekatan baru akan dibutuhkan<br />
# salah satu cara penggunaan [[(X)HTML]] untuk data.<br />
<br />
== The Appeal to Simplicity ==<br />
<br />
* Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world - for more on REST see [[suggested-reading#REST|suggested reading on REST]].<br />
* See: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley<br />
<br />
==See also==<br />
* A list of [[notable-users|some notable users]].<br />
* Recent [[press]] interviews and [[articles]] are also a good introduction.<br />
* See microformat [[presentations]] for more background and introductory material on [[microformats]].<br />
* Listen to [[podcasts]] about microformats.<br />
* Read the [[faq|FAQs]] for general microformat queries.<br />
* More [[suggested-reading|suggested reading]]<br />
* [[implement|So you want to implement microformats?]]<br />
* [[presentations]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== external ==<br />
* Sitepoint has a nice introductory tutorial: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar has written up [http://premasagar.com/microformats/compound/ some nice microformats examples with source].</div>Sevenovahttp://microformats.org/wiki/index.php?title=pendahuluan&diff=40532pendahuluan2009-08-30T17:48:03Z<p>Sevenova: New page: <entry-title>Pendahuluan Microformats</entry-title> __TOC__ == Apakah Microformats itu? == Microformats adalah cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manus...</p>
<hr />
<div><entry-title>Pendahuluan Microformats</entry-title><br />
__TOC__<br />
== Apakah Microformats itu? ==<br />
<br />
Microformats adalah cara menambahkan penandaan sederhana agar tiap data mudah terbaca oleh manusia seperti peristiwa, rincian kontak atau lokasi, pada halaman web sehingga informasi di dalamnya dapat di ekstraksi oleh perangkat lunak dan diindeks, dicari, disimpan, pertukaran-referensi, atau dikombinasi.<br />
<br />
More technically, they are items of semantic markup, using just standard "plain old semantic (X)HTML" (i.e. "[[POSH]]") with a set of common [[class-names]] and "[[rel]]" values. They are open and available, freely, for anyone to use.<br />
<br />
== Why Microformats ==<br />
<br />
Why did we come up with microformats?<br />
<br />
In short, microformats are the convergence of a number of trends:<br />
# a logical next step in the evolution of web design and information architecture<br />
# a way for people and organisations to publish richer information themselves, without having to rely upon centralized services<br />
# an acknowledgement that (outside of speci<span class="notspam">alist</span> areas) "traditional" metadata efforts have either failed or taken so long to garner any adoption, that a new approach was necessary<br />
# a way to use [[(X)HTML]] for data.<br />
<br />
== The Appeal to Simplicity ==<br />
<br />
* Microformats are a simple effort which has appealed to many frustrated with previous complex efforts. One parallel that can be drawn is to REST in the web services world - for more on REST see [[suggested-reading#REST|suggested reading on REST]].<br />
* See: [http://www.justinleavesley.com/journal/2005/7/28/web-services-and-the-innovators-dilemma.html Web Services and the Innovators Dilemma] by Justin Leavesley<br />
<br />
==See also==<br />
* A list of [[notable-users|some notable users]].<br />
* Recent [[press]] interviews and [[articles]] are also a good introduction.<br />
* See microformat [[presentations]] for more background and introductory material on [[microformats]].<br />
* Listen to [[podcasts]] about microformats.<br />
* Read the [[faq|FAQs]] for general microformat queries.<br />
* More [[suggested-reading|suggested reading]]<br />
* [[implement|So you want to implement microformats?]]<br />
* [[presentations]]<br />
* [[podcasts]]<br />
* [[testimonials]]<br />
<br />
== external ==<br />
* Sitepoint has a nice introductory tutorial: [http://reference.sitepoint.com/html/microformats Microformats - Plugging the Gaps in HTML]<br />
* Premasagar has written up [http://premasagar.com/microformats/compound/ some nice microformats examples with source].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40531Main Page-id2009-08-30T17:35:42Z<p>Sevenova: </p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[introduction|pendahuluan]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pengantar==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep mencakup hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses). Stabilitas pada dokumen ini tidak dapat dijamin, dan pengguna harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40530Main Page-id2009-08-30T17:34:11Z<p>Sevenova: /* Pendahuluan */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[introduction|pengantar]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pengantar==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep mencakup hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses). Stabilitas pada dokumen ini tidak dapat dijamin, dan pengguna harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40514Main Page-id2009-08-30T04:34:41Z<p>Sevenova: /* Konsep */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[introduction|pengantar]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pendahuluan==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep mencakup hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses). Stabilitas pada dokumen ini tidak dapat dijamin, dan pengguna harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40513Main Page-id2009-08-30T04:33:29Z<p>Sevenova: /* Konsep */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[introduction|pengantar]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pendahuluan==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep mencakup hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses). Stabilitas pada dokumen ini tidak dapat dijamin, dan pelaksananya harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40512Main Page-id2009-08-30T04:32:41Z<p>Sevenova: /* Konsep */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[introduction|pengantar]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pendahuluan==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep mencakup hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses).<br />
<br />
(see [[exploratory-discussions]] for additional efforts that are not as far along in the process). Stabilitas pada dokumen ini tidak dapat dijamin, dan pelaksananya harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40511Main Page-id2009-08-30T04:31:02Z<p>Sevenova: /* Konsep */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[introduction|pengantar]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pendahuluan==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep adalah hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lazim dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions|diskusi eksplorasi]] bahwa upaya peningkatan tersebut tak jauh dari sebuah proses).<br />
<br />
(see [[exploratory-discussions]] for additional efforts that are not as far along in the process). Stabilitas pada dokumen ini tidak dapat dijamin, dan pelaksananya harus siap mengkiuti perubahan yang akan datang. Silahkan mengamati halaman wiki untuk melihat tiap perubahannya.<br />
<br />
* [[adr|adr]] - untuk menandai informasi alamat<br />
* [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geografi (latitude; longitude)<br />
* [[hatom|hAtom]] - sindikasi episodik isi (contohnya catatan weblog)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - Format publikasi media yang berhubungan dengan Gambar, Video, dan Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - untuk resep masak memasak<br />
* [[hresume|hResume]] - untuk publikasi resume dan CV<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - untuk mengindikasikan lampiran (contohnya berkas) untuk diunduh dan disembunyikan<br />
* [[rel-home]] - indikasi sebuah hyperlink halaman utama pada sebuah situs<br />
* [[rel-payment]] - indikasi mekanisme pembayaran<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40510Main Page-id2009-08-30T04:05:42Z<p>Sevenova: /* Konsep */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[introduction|pengantar]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pendahuluan==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
<br />
Konsep adalah hal baru pada Microformats, dimana rumusan spesifikasinya belum lengkap. Konsep adalah sesuatu yang lumrah dalam [[process|proses]] pengembangan (lihat [[exploratory-discussions]] )<br />
<br />
(see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.<br />
<br />
* [[adr|adr]] - for marking up address information<br />
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)<br />
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - for cooking+baking recipes<br />
* [[hresume|hResume]] - for publishing resumes and CVs<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache<br />
* [[rel-home]] - indicate a hyperlink to the homepage of the site<br />
* [[rel-payment]] - indicate a payment mechanism<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenovahttp://microformats.org/wiki/index.php?title=Main_Page-id&diff=40509Main Page-id2009-08-30T02:18:43Z<p>Sevenova: /* Rancangan */</p>
<hr />
<div><entry-title>Selamat datang di wiki Microformats!</entry-title><br />
__TOC__<br />
Silahkan awali dengan halaman [[introduction|pengantar]] dan baca juga [[how-to-play|cara penggunaan]] sebelum menyunting halaman.<br />
<br />
==Pendahuluan==<br />
Wiki ini adalah sumber pengetahuan komunitas Microformats. Anda akan menemukan spesifikasi versi terbaru yang diterbitkan microformat, spesifikasi rancangan dan pola penerbitan. Wiki juga menjadi tuan rumah pengembangan, seperti halaman gagasan untuk format baru dan menerbitkan halaman pelacakan untuk semua dan yang saat ini sedang dalam pengembangan Microformats.<br />
<br />
==Persiapan==<br />
Untuk mulai menggunakan Microformats:<br />
<br />
* Pertama, biasakan menulis halaman dan aplikasi yang penuh semantik, deskriptif, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Belajar tentang Microformats dari [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] halaman.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definisi==<br />
Microformats adalah pola sederhana pada HTML yang mewakili hal-hal publikasi umum seperti [[hcard|orang]], [[hcalendar|kegiatan]], [[hatom|blog posts]], [[hreview|tinjauan]] dan [[rel-tag|label]] pada halaman web.<br />
<br />
Microformats memungkinkan ketepatan publikasi informasi pada web lebih akurat; lebih cepat dan sederhana untuk diberikan kepada feeds dan APIs pada informasi website Anda.<br />
<br />
* Baca penjelasan selanjutnya pada [[what-are-microformats|apakah Microformats itu]], dan [[what-can-you-do-with-microformats|apa saja yang dapat Anda lakukan]].<br />
<br />
==Bagaimana caranya berbagi==<br />
Apakah Anda ingin membantu Microformats ketingkat selanjutnya? Anda dapat:<br />
<br />
* [[get-started|Memulai]] dengan menambahkan Microformats ke website, layanan, dan produk Anda.<br />
* [[advocacy|Anjurkan]] penggunaan Microformats pada situs web lainnya, terutama yang Anda gunakan.<br />
* Tulislah sebuah [[testimonial|tanda penghargaan]].<br />
* Lakukan sesuatu pada [[to-do|daftar yang harus dilakukan]].<br />
* Bergabung di [[irc|IRC Channel]] dan [[mail|milis]] untuk mempelajari dan menjawab pertanyaan (baca [[mailing-lists#General_guidelines|pedoman umum]] sebelum mengirimkan).<br />
* [[Main_Page#microformats_wiki_translations|Terjemahkan Wiki Microformats ini kedalam bahasa lainnya]] agar Microformats lebih mudah diakses pembaca bahasa di seluruh dunia.<br />
* Sebelum mengajukan Microformats baru, pastikan website Anda adalah [[POSH]], [[get-started|menggunakan Microformats yang sudah ada]], kemudian bacalah [[process|prosesnya]].<br />
<br />
Wiki ini memiliki sejumlah perangkat tambahan untuk membantu pembangunan dan kontribusi untuk Microformats. Sebelum Anda mulai mengedit, lihat [[wiki-2|halaman pendahuluan wiki]] sebagai petunjuk.<br />
<br />
== Spesifikasi ==<br />
Daftar saat ini, [[microformats|Microformats]] yang stabil dengan spesifikasi standar terbuka.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''Jika Anda ingin mencoba berlatih menggunakan Microformats silahkan baca halaman '''[[process|proses]]''' untuk pertama kalinya!''<br />
<br />
==Konsep==<br />
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.<br />
<br />
* [[adr|adr]] - for marking up address information<br />
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)<br />
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio. <br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - for cooking+baking recipes<br />
* [[hresume|hResume]] - for publishing resumes and CVs<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache<br />
* [[rel-home]] - indicate a hyperlink to the homepage of the site<br />
* [[rel-payment]] - indicate a payment mechanism<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
==Pola Rancangan==<br />
{{design_patterns-id}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
==Eksplorasi Diskusi==<br />
Lihat: rincian [[exploratory-discussions|eksplorasi diskusi]] untuk riset dan analisa pada [[examples|contoh]] dunia-nyata, format yang ada, dan diskusi kemungkinan adanya Microformats yang baru, per [[process|proses]] microformats.<br />
<br />
== Contoh ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Sumber ==<br />
Lihat [[resources|sumber]].<br />
<br />
==Pusat pengembangan pengguna==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
==Berbagi area kerja==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
==Peralatan, uji kasus, riset tambahan==<br />
<br />
<br />
Tempat pertama untuk mencari contoh-contoh, kode, dan uji kasus berada pada tiap halaman individu Microformat. Hanya ada beberapa lintas sektor [[tools|peralatan dan layanan]] yang dibutuhkan untuk memproses lebih dari satu format. Bagian tersebut dimaksudkan untuk penyunting, [[parsers]], [[validators]], uji kasus, dan informasi lainnya yang berhubungan other di beberapa Microformats.<br />
<br />
==Terjemahan Wiki Microformats==<br />
<span id="microformats_wiki_translations_in_other_languages">Anda dapat membaca atau menyunting artikel Microformats dalam berbagai bahasa:</span><br />
<br />
* Bahasa yang lebih dari 100 artikel:<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* Bahasa yang lebih dari 10 artikel:<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* Bahasa yang lebih dari 2 artikel:<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
* Bahasa yang baru saja dimulai:<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* Lainnya<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] telah diterjemahkan ke dalam beberapa bahasa.<br />
<br />
Kungungi juga [[other-languages|bahasa lainnya]], dan [[how-to-start-new-translation|bagaimana-memulai-bahasa-baru]].</div>Sevenova