Microformats Wiki - User contributions [en]

vcard-implementations

2017-02-18T13:39:57Z

Lowongankerjalampung:

<h1> vCard implementations </h1>
{{TOC-right}}
In the development of [[hcard|hCard]] and proxies like X2V, we have discovered various behaviors and quirks of [[vCard]] implementations. See also the [[vcard-errata]].

== Conventions ==
'''Conventions for this page.''' When documenting a specific implementation, use the name of the implementation as the header including minimal version information. Provide an abbreviation of the implementation name (in parantheses) for use in subheadings for property names and other general subsections. Prefix subheadings with aforementioned abbreviation followed by vCard property name (if applicable) in ALL CAPS as vCard properties are typically fully uppercased in both vCard files and implementations (but are actually case-insensitive per RFC 2426).

== General Suggestions ==
General implementation guidelines and suggestions for vCard implementations. (Note: it might be useful to separate the more generic aspects of of these general vCard implementation suggestions into a "contact application" section on the [[user-interface]] page.)
# Fully implement RFC 2426, including all properties, sub-properties, and type values for properties, on both import and export with 100% roundtrip fidelity.
# Support <em>subscribing</em> to vCard URLs on the Web in addition to importing so that your local address book can have automatically current (fresh) information of the contacts that you've added from the Web.
# Use a rendering engine (e.g. Trident, Gecko, Webkit) to render PHOTO URLs and other properties which have URL values live from the Web for similar freshness.
# When syncing to another device that supports contact information (iPod, iPhone, BlackBerry etc.), downsample PHOTOs (and other images or binary data) to whatever small size works best on those devices so as to not bloat the space on those devices. Note that such downsampling is best done closest to the point of synchronization, e.g. by the Address Book application when syncing, instead of upfront by a web service like X2V, so that maximum data fidelity is maintained until the last minute when the data can be compressed for the specific device purely for efficiency reasons.

== Microsoft Outlook ==
Microsoft Outlook (MSOutlook).
version? platform?

=== MSOutlook single import ===
Outlook (either 2003 or 2007 beta version) appears to only support one vCard per VCF. There are some
third-party products that attempt to fix this [http://www.sperrysoftware.com/Outlook/Vcard-Converter.asp]

=== MSOutlook URL handling ===
URL without non-standard TYPE parameter seems to be ignored.

=== MSOutlook ADR handling ===
Appears to not support the '''post-office-box''' sub-property of ADR.

=== MSOutlook escaped commas ===
Outlook 2003 does not strip the backslashes from escaped commas (i.e., SR-PS\, Inc.) on import.

== Microsoft Outlook 2003 ==
Microsoft Outlook 2003 (MSOutlook2k3)
The following was verified on Outlook 2003 SP2 running on Windows XP Pro SP2

=== MSOutlook2k3 URL ===
URL is changed to URL;HOME: and is not visible anywhere normally in Outlook. It is visible in the Contact Properties window under the "All Fields" when selecting "Frequently-used fields" from the "Select from:" drop-down box. It is also exported when exporting as a vCard.

=== MSOutlook2k3 ADR ===
ADR; is changed to ADR;POSTAL:

ADR; is copied to LABEL;POSTAL;ENCODING=QUOTED-PRINTABLE: with city/state/zip changed to use carriage return and comma seperation. IE:
<pre>ADR;CHARSET=utf-8:;;address1;city;state;zip;</pre>
is changed to:
<pre>ADR;POSTAL:;;address1;city;state;zip
LABEL;POSTAL;ENCODING=QUOTED-PRINTABLE:address1=0D=0Acity, state zip</pre>

=== MSOutlook2k3 N ===
When exporting a vCard, copies FN into N when N is blank. Does not do this when importing a vCard.

Outlook 2003 does not handle comma separation in the properties of N. For this vCard.

<pre>
BEGIN:VCARD
FN;CHARSET=UTF-8:Mr. Dr. John Maurice Benjamin Doe Ph.D.\, J.D.
N;CHARSET=UTF-8:Doe;John;Maurice,Benjamin;Mr.,Dr.;Ph.D.,J.D.
END:VCARD
</pre>

The result in Outlook is:

Mr.,Dr. Mr. Dr. John Maurice Benjamin Doe Ph.D.\, J.D.

=== MSOutlook2k3 TEL ===
Drops TEL if TYPE is not explicitly specified.

TEL;TYPE=work: is changed to TEL;WORK;VOICE:

=== MSOutlook2k3 GEO ===
'''Unsupported.''' GEO is unsupported and is ignored.

=== MSOutlook2k3 LOGO ===
'''Unsupported.''' Will not import nor export vCard image references, but does support images internally in it's own contact management system.

== Windows Address Book ==
Windows Address Book (WAB) Version 6.00.X Win98 and Win XP Pro

=== WAB vCard ENCODING ===
UTF-8 encoded vCard import prompts error as unrecognised vCard format. US ASCII 20127 encoded vCard successfully imported

=== WAB ADR ===
If you do NOT specify TYPE=HOME,WORK,... then no address information is imported

=== WAB TEL ===
If you do NOT specify TYPE=HOME,WORK,... then no address information is imported

=== WAB PHOTO ===
'''Unsupported.''' Does not support images.

=== WAB NOTE ===
According to the example in the RFC spec, all commas should be escaped, but WAB does not Un-escape them, leaving \, in the notes field.

== Microsoft Entourage ==
On Mac OS X. Entourage versions 10 and 11.

=== Entourage general comments ===
* Entourage versions 10 and 11 export vCard files as UTF-16, big endian, with Mac classic line endings (a single CR). The file does contain the proper UTF-16 BE BOM at the start, making identification of the file contents simpler.
* Importing vCards: Entourage 11 will look for a BOM when importing a vCard file. It respects UTF-16 BE, UTF-16 LE, and UTF-8 BOMs. With no BOM, Entourage 11 will attempt to import the vCard file as an 8-bit stream using the current system encoding (for example, Mac Roman).
* Entourage 12 (under development) is expected to have better vCard standard conformance, exporting vCard files as UTF-8 (with individual fields properly labelled with "charset=utf-8") and using Windows (CR+LF) line endings. When importing vCard files without a BOM, it wil assume UTF-8 encoding but will respect "charset=" tags if present.

== Apple Address Book ==
Apple Address Book (AAB) on Mac OS X 10.3 (Panther) and 10.4 (Tiger).

=== AAB general comments ===
* There are issues with importing UTF-8 vCards. Apple Address Book appears to treat .vcf files in the file system NOT as UTF-8, but rather perhaps Mac Roman?
** Workaround: Explicitly specify the UTF-8 charset for vCard properties/fields that have non-ASCII-7 characters. This is allowed per [[vcard-errata]], and encouraged to enable higher fidelity character set handling.
* Importing multiple vCards with the same fn/n results in duplicate entries in the Address Book. Basically, Address Book assumes that every vCard present in a single .vcf file represents a different person, even if the fn/n are the same etc.
** Workarounds:
*** Only markup one hCard per person, per page (has potential implications for [[hresume|hResume]]).
*** Have the converting application/service (e.g. X2V), do automerging of hCards with the same fn/n and generate a .vcf stream with one vCard per unique fn/n.
* Apple Address Book 4.0.4 (Mac OS X 10.4) exports vCard files as UTF-16 big endian with no BOM and Mac (CR) line endings, if the vCard record contains any non-ASCII data (for example Japanese characters). If the entire vCard record can be represented in ASCII, it is exported as an ASCII encoded file with Windows (CR+LF) line endings.

Several properties appear to have no or limited support, see below for specifics.

=== AAB organization vs individual ===
Summary: FN==ORG organization semantic supported for both import and export.

For organization contact info, sets the FN and ORG to the name of the organization and N to empty on exported vCards.

Also treats imported vCards like that as organization contact info cards visibly in the UI.

=== AAB GEO ===
'''Unsupported.''' The GEO field is ignored on imported vCards. It is only saved as part of the NOTE.

=== AAB SOURCE ===
'''Unsupported.''' The SOURCE property is not supported on imported vCards. It is only saved as part of the NOTE.

=== AAB LOGO ===
'''Unsupported.''' The LOGO property is totally ignored and not even saved as part of the NOTE.

=== AAB PHOTO ===
'''Partial support.''' The PHOTO property is only supported when it has inline encoded data. URL values appear to be ignored.

=== AAB URL ===
'''Lack of support for aim protocol'''. URLs starting with "aim:" are imported but then when clicked, Address Book prepends them with <nowiki>http://</nowiki> before "activating" them thus rendering them non-functional.

'''Non-standard restriction to one value.''' (Version 3.0 and below only. Works fine in v4.0+): Only ONE URL property value is supported for vCard import (whereas multiple *should* be supported, just like EMAIL).

=== AAB ADR ===
'''Quirky.''' If you do NOT specify which type of address information it is (like HOME or WORK) it is assumed to be a WORK address, whereas [[vcard|vCard]] specifies that the default type for adr is all of: INTL, POSTAL, PARCEL, WORK.

=== AAB CATEGORIES ===
'''Quirky.''' Behavior confirmed on versions:
* default on OSX.3
* Version 4.03 (483) on OSX.

Summary: Exports native "Groups" as vCard CATEGORIES. Ignores CATEGORIES field when importing a vCard.

The UI lets you create distinct "Groups" which you can then drag contacts into. Contacts can be in more than one group. Upon exporting a contact that is in one or more Groups, those Groups are listed in the CATEGORIES field.

However, when importing vCards, the CATEGORIES field is totally ignored by Address Book.
# It does not add vCards with a category that matches a current Group to that Group.
# It does not create new Groups for vCards with new categories.
# It does not even add the CATEGORIES to the end of the notes field.
Though presumably it SHOULD do #1 and #2. Would also be nice if it simply let you edit the groups/categories for a contact simply as a list of tags for that contact.

== Evolution ==
Evolution (Evo)
On Linux.

=== Evo GEO ===
'''Unsupported.'''
* ichigo, Frederic to fill in details

=== Evo KEY ===

Evolution uses GnuPG to manage GPG/PGP keys

== Nokia series 60 address book ==
Nokia series 60 address book (N60AB).

=== N60AB line endings ===
The Contacts application on Nokia series 60 handsets will only open vCards with Windows (\r\n) line endings. Any other line ending styles will cause an error message.

This is actually reasonable behavior because the vCard spec explicitly states \r\n should be used, but many applications will accept \n delimited vCards without complaint, and may microformat services produce \n delimited output.

== Palm Desktop 4.1.4 ==
Palm Desktop 4.1.4 (PD414).

=== PD414 vCard import ===
Palm Desktop 4.1.4 appears to fail importing a vcard if it has a NAME specified in the vcard.

== CSV to vCard ==
[http://tempatservicehpdibandarlampung.blogspot.co.id CSV to vCard] web service takes CSV (or tab-delimited) contacts and turns them into vCard format. This was originally written to take information from Outlook Express for Mac OS 9 and bring it into the address book in OS X.

== contributors==
* [[User:Tantek|Tantek Çelik]]
* Brian Suda
* Steve Robillard

== related pages ==
{{hcard-related-pages}}

hcalendar-de

2017-02-18T13:38:06Z

Lowongankerjalampung:

'''hCalendar''' ist ein enfaches, offenes Format zur Auszeichnung von Kalender- und Veranstaltungsdaten. Es basiert auf dem iCalendar-Standard (RFC2445) und passt diesen auf die Benutzung in HTML oder XHTML, Atom, RSS oder anderen XML-Dialekten an. hCalendar ist eines von vielen [[microformats|Mikroformaten]].

Wer mit dem Schreiben eines hCalendar-Eintrags beginnen will, benutze den [http://microformats.org/code/hcalendar/creator hCalendar creator] oder folge den [[hcalendar-authoring|Autorenhinweisen für hCalendar]].

__TOC__

== Spezifikation ==

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

=== Copyright ===

Mit der Veröffentlichung auf den Seiten der Autoren ([[User:Tantek|Tantek Çelik]], [[User:Brian|Brian Suda]]) wurde diese Spezifikation als public domain freigegeben.

{{MicroFormatPublicDomainContributionStatement}}

=== Patente ===
{{MicroFormatPatentStatement}}

=== Danksagungen ===

Unser Dank geht an:
* Adam Bosworth für die Leitung der [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation], die eine kritische Masse von interessierten Gruppen zusammenbrachte.

== Einführung ==

Der iCalendar-Standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) steht auf vielen Plattformen zur Verfügung.

Blogger besprechen oft Termine und Veranstaltungen in ihren Blogs. Egal, ob es sich dabei um bevorstehende Termine oder Nachbesprechungen bereits stattgefunden habender Veranstaltungen handelt, eine einfache Struktur macht es möglich, dass diese Beiträge und Diskussionen auch von Spidern und anderen Aggregatoren gelesen und in das iCalendar-Format überführt werden können. Somit sind sie in Programmen, die den iCalendar-Standard unterstützen, weiterverwendbar.

Diese Spezifikation führt das hCalendar-Format ein, welches den iCalendar-Standard in sematischem HTML abbildet. Autoren von Webinhalten, zum Beispiel Blogger, können mit hCalendar Termine auf ihren Seiten auszeichnen, die so ausgezeichneten Termine gesondert mit CSS formatieren sowie auf diese Informationen mit Programmen zugreifen, ohne diese Informationen noch einmal --beispielsweise in einer Datei-- gesondert zur Verfügung stellen zu müssen.

{{rfc-2119-intro}}

== Designprinzipien für semantisches XHTML ==

{{semantic-xhtml-design-principles}}

Für die Praxis wird darauf hingewiesen, dass die Unterstützung des Microsoft Internet Explorers für <code><nowiki><abbr></nowiki></code> fehlt und daher Container-Elemente für <code><nowiki><abbr></nowiki></code> benötigt werden.

== Format ==

=== Allgemein ===

Der iCalendar-Standard ([http://www.isric.org/users/kitssupplies isric.org]) bildet die Grundlage für hCalendar.

Anmerkung: the editor and authors of this specification are tracking the [http://lists.osafoundation.org/pipermail/ietf-calsify/ "iCal-Basic" effort] and intend to base the core hCalendar profile on iCal-Basic. See references for a link to the current draft.

Die grundlegende Regel ist, die Namen der iCalendarobjekte und -eigenschaften mit Kleinschreibung in hCalendar weiter zu verwenden und die Verschachtelung der iCalendar-Struktur direkt mittels XHTML-Elementen abzubilden.

=== Root Class Name ===

Der Root Class Name von hCalendar ist "vcalendar". Ein mit diesem Namen klassifiziertes Element wird ''hCalendar'' genannt.

Der Root Class Name eines Termins ist "vevent". Ein mit diesem Namen klassifiziertes Element wird ''hCalendar event'' genannt.

Um die Auszeichnung mit hCalendar zu vereinfachen, werden beide Namen --"vcalendar" und "vevent"-- als Root Class Names angesehen. Falls ein Dokument Elemente der Klasse "vevent" aber keine Elemente der Klasse "vcalendar" enthält, wird angenommen, dass das ganze Dokument zur Klasse "vcalendar" gehört.

Ein '''vevent'''-Element wird für jeden einzelnen Termin benötigt.

=== Einzelne Eigenschaften ===

Die Einträge eines hCalendars werden durch im hCalendar befindliche Elemente, die mit den folgend aufgezählten Klassennamen ausgezeichnet sind, repräsentiert. Einige Eigenschaften haben Untereigenschaften. Diese werden durch Elemente innerhalb der Elemente der Eigenschaften dargestellt.

=== Eigenschaftenliste ===

hCalendar Eigenschaften (Untereigenschaften sind wie hier in Klammern gesetzt)

'''vorgeschrieben:'''
* '''dtstart''' ([[iso-8601|ISO Datum]])
* '''summary'''

Optional:
* location
* url
* dtend (ISO-Datum), duration (ISO-Datum Dauer)
* rdate, rrule
* category, description
* uid
* geo (latitude, longitude)
* ... Anmerkung des Herausgebers: diese Liste ist nicht komplett (die Liste wird [[hcalendar|auf der englischen Originalseite dieses Artikels]] komplettiert). Die hier aufgezählten Eigenschaften sind die gebräuchlichsten.

=== Weitere, genauere semantische Entsprechungen ===

Einige Eigenschaften können noch konkreter ausgezeichnet werden. Die entsprechenden Informationen erfahren weitere Aufbereitungen, z. B.:

* <code>URL</code> aus iCalendar wird in hCalendar zu <code><a class="url" href="...">...</a></code> innerhalb des Elements der Klasse <code>class="vevent"</code>.
* <code>ATTENDEE</code>, <code>CONTACT</code> und <code>ORGANIZER</code> aus iCalendar {{may}} (können) in hCalendar durch einen [[hcard|hCard]]-Eintrag ausgezeichnet werden.
* Ein namentlich genannter, eventuell auch mit Adresse oder Geoinformationen aufgeführter (Veranstaltungs-)Ort {{may}} (kann) mit einem verschachtelten [[hcard|hCard]]-Eintrag dargestellt werden.
* Da es für <code>LOCATION</code> unterschiedliche Formen gibt, {{may}} (kann) eine Adresse als [[adr]] ausgezeichnet werden and für Geo-<code>LOCATION</code> (Breiten- und Längengrade) kann [[geo]] benutzt werden.
* Für <code>UID</code> aus iCalendar wird in hCalendar bei einem Termin eine URL angegeben.

=== Singular vs. Plural Properties ===

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

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

==== Plural Properties Singularized ====

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

=== Menschen- und Maschinenlesbarkeit ===

Wenn ein <code><nowiki><abbr></nowiki></code>-Element für eine Eigenschaft benutzt wird, wird im '<code>title</code>'-Attribut des <code><nowiki><abbr></nowiki></code>-Elements der zur maschinellen Auswertung vorgesehene Wert gesetzt. Der Inhalt des Elements selbst enthält hingegen den für Menschen vorgesehenen Text. Diese Spezifikation empfiehlt, <code><nowiki><abbr></nowiki></code>-Elemente für folgende iCalendar-Eigenschaften zu benutzen:

* DTSTART, DTEND, DURATION, RDATE, RRULE

== Beispiel 1 ==

Ein Terminbeispiel in iCalendar-Notation:

<pre>
<nowiki>
BEGIN:VCALENDAR
PRODID:-//XYZproduct//EN
VERSION:2.0
BEGIN:VEVENT
URL:http://www.web2con.com/
DTSTART:20071005
DTEND:20071020
SUMMARY:Web 2.0 Conference
LOCATION:Argent Hotel\, San Francisco\, CA
END:VEVENT
END:VCALENDAR
</nowiki>
</pre>

... und eine mögliche Entsprechung im hCalendar-Format mit einigen angebrachten Optimierungen. See [[hcalendar-example1-steps]] for the derivation.

<pre><nowiki>
<div class="vevent">
<a class="url" href="http://www.web2con.com/">http://www.web2con.com/</a>
<span class="summary">Web 2.0 Conference</span>:
<abbr class="dtstart" title="2007-10-05">October 5</abbr>-
<abbr class="dtend" title="2007-10-20">19</abbr>,
at the <span class="location">Argent Hotel, San Francisco, CA</span>
</div>
</nowiki></pre>

was wie folgt ausgegeben werden kann:

----

<div class="vevent">
<span class="url">http://www.web2con.com/</span> 
<span class="summary">Web 2.0 Conference</span>:
<abbr class="dtstart" title="2007-10-05">October 5</abbr>-
<abbr class="dtend" title="2007-10-20">19</abbr>,
at the <span class="location">Argent Hotel, San Francisco, CA</span>
</div>

----

Dieser Eintrag ist im Quelltext dieser Seite enthalten und wird deshalb von Programmen, die Mikroformate aus Webseiten lesen können (Parser), hier auch gefunden.

=== Beispiel 2 ===

Das folgende Beispiel zeigt ein angesetztes Treffen, welches am 12. März 1998 um 08:30 EST (Eastern Standard Time) beginnt und am selben Tag um 09:30 Ortszeit endet.

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

Das Gleiche in hCalendar:

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

Dies könnte so ausgegeben werden:

----

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

----

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

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

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

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

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

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

==Buttons==

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

=== More Examples ===

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

== Examples in the wild ==

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

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

== Implementations ==

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

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

== References ==

=== Normative References ===

* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [[hcard|hCard]]
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]
* [[rfc-2119| RFC 2119]]
* [[iso-8601|ISO8601]]

=== Informative References ===

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

==== Specifications That Use hCalendar ====

* [[hreview|hReview]]

==== Related Work ====

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

== Further Reading ==

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

* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]
* [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcalendar hCalendar tag]
* [http://en.wikipedia.org/wiki/HCalendar Wikipedia article on hCalendar] (requires expansion)
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-4-hcalendar/ Getting Semantic With Microformats, Part 4: hCalendar] by [http://www.ablognotlimited.com/ Emily Lewis]
* [http://www.peachpit.com/guides/content.aspx?g=webdesign&seqNum=356 Microformats: The Art of Markup: hCalendar] by [http://www.stuffandnonsense.co.uk/ Andy Clarke]
* [http://forabeautifulweb.com/blog/about/a_tribute_to_microformats_a_reader_question_answered/ A tribute to Microformats (a reader question answered)] by [http://www.stuffandnonsense.co.uk/ Andy Clarke]

== Related Pages ==

{{hcalendar-related-pages}}

[[Category:Specifications]]
[[Category:hCalendar]]

work-of-art-fr

2017-02-18T13:36:21Z

Lowongankerjalampung:

= Oeuvre d'Art =

Beaucoup de muséums d'art utilisent les métadonnées pour décrire les oeuvres d'art dans leurs collections. Néanmoins la présentation des oeuvres d'art sur le web ne bénéficie pas souvent de ce travail de catégorisation. Nous aimerions développer un balisage xthml standard pour la présentation des oeuvres d'art sur le web.

Cette page est un index pour un effort communautaire de créer un microformat oeuvre d'art.

Selon le [[process-fr|processus]] des microformats :

* [[workofart-brainstorming-fr|workoofart-brainstorming]] (Un endroit pour proposer et discuter des standards de balisage xhtml pour les oeuvres d'art.)
* [[workofart-examples-fr|workofart-exemples]] (une liste d'exemples de balisage (x)html pour les oeuvres d'art.)
* [[workofart-formats-fr]] (une liste de formats existant de métadonnées d'oeuvres d'art.)

SVP, jetez un oeil et contribuez vos pensées et idées.

* [[http://lowongankerjalampung161289.blogspot.co.id]]
* [[http://www.jsponsel.com/2017/02/lowongan-kerja-lampung.html]]
* [[http://www.jsponsel.com/ lowongan kerja lampung]]