View source for hcalendar-pl

{{DISPLAYTITLE:hCalendar 1.0}}
<dfn style="font-style:normal;font-weight:bold">hCalendar</dfn> jest prostym, otwartym, rozpowszechnionym formatem kalendarzowo-zdarzeniowym, używającym 1:1 reprezentacji standardowego formatu iCalendar ([[rfc-2445|RFC2445]]) "VEVENT" właściwości i wartości zapisywane są w standardzie z [[semantic-xhtml|HTML lub XHTML]]. hCalendar jest jednym z kilku otwartych [[microformats|Mikroformatów]] okazujących się standardem przy osadzaniu danych w: HTML, XHTML, Atom, RSS i "arbitrary XML".

'''Chciał byś już w tym momencie zacząć pisać zdarzenia w zgodniości z [[hcalendar-pl|hCalendar]]?''' Użyj: [http://microformats.org/code/hcalendar/creator hCalendar creatora] aby napisać zdarzenie oraz opublikować je, lub podążaj za [[hcalendar-authoring|hCalendar wskazówkami]] aby dodać hCalendar na swoją stronę zawierającą daty zdarzeń.

<div class="vcard">
; <span class="role">Edytował:</span> 
: <span class="fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="url">http://tantek.com/</span>, and before at [http://technorati.com Technorati, Inc.], and at [http://microsoft.com/ Microsoft Corporation])
: <span class="fn">[[User:Sahadar|Wojciech Dłubacz]]</span> (<span class="url">http://www.sahadar.pl/moowindows</span>)
</div>
; Autorzy: [http://tantek.com/ Tantek Çelik] (powiązanie powyżej)
: <span class="vcard"><span class="fn">[[User:Brian|Brian Suda]]</span> (<span class="url">http://suda.co.uk/</span>)</span>

; Podziękowania: Zobacz [[hcalendar#Inspiration_and_Acknowledgments|podziękowania]].

"[[hcalendar#Copyright|copyright]] and [[hcalendar#Patents|patents]] statements apply".

== Przykład ==
Oto prosty przykład:
<blockquote><p>Strona microformats.org została zapoczątkowana dnia 2005-06-20 podczas "Konferencji Supernova" w San Francisco, CA, USA</p></blockquote>
napisany zgodnie z konwencją hCalendar

<source lang=html4strict>
<span class="vevent">
 <span class="summary">Strona microformats.org została zapoczątkowana</span>
 dnia <span class="dtstart">2005-06-20</span> 
 podczas "Konferencji Supernova" 
 w <span class="location">San Francisco, CA, USA</span>.
</span>
</source>

== Status ==
hCalendar 1.0 jest specyfikacją microformats.org. Publiczna dyskusja na temat hCalendar mieści się w [[hcalendar-feedback]], kanał #microformats [[irc]] na irc.freenode.net, oraz [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Dostępne języki ===
Angielska wersja tej specyfikacji jest jedyną poprawną wersją. By zobaczyć resztę tłumaczeń tej strony, przejrzyj  [[#translations]] sekcje.

=== Poprawki i aktualizacje ===
Znane oraz wychwycone błędy jak i problemy zostały poprawione w [[hcalendar-issues-resolved|rozwiązanych]] i [[hcalendar-issues-closed|zamkniętych]] wątkach. Zanim zaczniesz zgłaszać jakikolwiek [[hcalendar-issues|błąd/problem]], proszę sprawdź powyższe linki.

Szczególnie zwróć uwagę na wątek "[[dtend-issue]]" poruszający kwestie dat końcowych. Implementacje powinny implementować poprawione błędy możliwie jak najszybciej oraz [http://ufxtract.com/testsuite/hcalendar/hcalendar1.htm powinny być przetestowane].

Aktualnie zajmujemy się aktualizacją do hCalendar 1.0.1 włączając w to również korekcje zarówno składni jak i [[value-class-pattern]].

== Introduction ==
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), has been broadly interoperably implemented (e.g. Apple's "iCal" application built into MacOSX).

In addition, bloggers often discuss events on their blogs -- upcoming events, writeups of past events, etc.  With just a tad bit of structure, bloggers can discuss events in their blog(s) in such a way that spiders and other aggregators can retrieve such events, automatically convert them to iCalendar, and use them in any iCalendar application or service.

This specification introduces the '''hCalendar''' format, which is a 1:1 representation of the aforementioned iCalendar standard, in semantic HTML.  Bloggers can both embed hCalendar events directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCalendar enables applications to retrieve information about such events directly from web pages without having to reference a separate file.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==

{{semantic-xhtml-design-principles}}

For practical implementations, it should be noted that Internet Explorer's support for styling <code><nowiki><abbr></nowiki></code> elements is poor, and may require wrapper elements.

== Format ==
=== In General ===
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.

Note: 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.

The basic format of hCalendar is to use iCalendar object/property names in lower-case for class names, and to map the nesting of iCalendar objects directly into nested XHTML elements.

=== Root Class Name ===
The root class name for hCalendar is "vcalendar".  An element with a class name of "vcalendar" is itself called an ''hCalendar''. 

The root class name for events is "vevent". An element with a class name of "vevent" is itself called an ''hCalendar event''.

For authoring convenience, both "vevent" and "vcalendar" are treated as root class names for parsing purposes.  If a document contains elements with class name "vevent" but not "vcalendar", the entire document has an implied "vcalendar" context.

'''vevent''' should be considered required for each event listing.

=== Properties and Sub-properties ===
The properties of an hCalendar are represented by elements inside the hCalendar.  Elements with class names of the listed properties represent the values of those properties.  Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
hCalendar properties (sub-properties in parentheses like this)

'''Required:'''
* '''dtstart''' ([[iso-8601|ISO date]])
* '''summary'''
Optional:
* location
* url
* dtend (ISO date), duration (ISO date duration)
* rdate, rrule
* category, description
* uid
* geo (latitude, longitude)
* attendee (partstat, role), contact, organizer
* attach
* status
* ... editor's note: this list is incomplete (an incomplete list is better than no list) and is being currently edited from RFC2445 to here.  The above list of properties are those that are often used in hCalendar on the web.

=== Profile ===
The hCalendar XMDP profile is at http://microformats.org/profile/hcalendar

Content that uses hCalendar {{should}} reference this profile, e.g.
<source lang=html4strict>
<head profile="http://microformats.org/profile/hcalendar">
</source>
or
<source lang=html4strict>
<link rel="profile" href="http://microformats.org/profile/hcalendar">
</source>
or
<source lang=html4strict>
This content uses <a rel="profile" href="http://microformats.org/profile/hcalendar">hCalendar</a>.
</source>
Content may combine the above methods as well.

=== More Semantic Equivalents ===
For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <code>URL</code> in iCalendar becomes  <code>&lt;a class="url" href="..."&gt;...&lt;/a&gt;</code> inside the element with <code>class="vevent"</code> in hCalendar.
* <code>ATTENDEE</code>, <code>CONTACT</code>, and <code>ORGANIZER</code> in iCalendar {{may}} be represented by an [[hcard|hCard]] in hCalendar .
* A named <code>LOCATION</code> (potentially with an address and/or geo) in iCalendar {{may}} be represented by a nested [[hcard|hCard]] in hCalendar. Similarly, an address <code>LOCATION</code> {{may}} be represented by an [[adr]], and a geo (latitude and longitude) <code>LOCATION</code> may be represented by a [[geo]].
* <code>UID</code> in iCalendar simply becomes another semantic applied to a specific URL for an hCalendar event.
* <code>ATTACH</code> in iCalendar becomes an img or object element (where the value is stored ito / retrieved from the 'src' or 'data' attributes respectively). An <code>&lt;a class="attach"                           href="..."&gt;...&lt;/a&gt;</code> may also be used, in which case the 'href' attribute is used for the property value.

=== Singular vs. Plural Properties ===

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

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

==== Plural Properties Singularized ====

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

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

== Examples ==

Here is a sample multiple-day event in an iCalendar:
<pre>
<nowiki>
BEGIN:VCALENDAR
PRODID:-//XYZproduct//EN
VERSION:2.0
BEGIN:VEVENT
URL:http://conferences.oreillynet.com/pub/w/40/program.html
DTSTART:20051005
DTEND:20051008
SUMMARY:Web 2.0 Conference
LOCATION:Argent Hotel\, San Francisco\, CA
END:VEVENT
END:VCALENDAR
</nowiki>
</pre>

and an equivalent event in hCalendar format with various elements optimized appropriately. See [[hcalendar-example1-steps]] for the derivation.

<source lang=html4strict>
<div class="vevent">
 <a class="url" href="http://conferences.oreillynet.com/pub/w/40/program.html">
  http://conferences.oreillynet.com/pub/w/40/program.html
 </a>
 <span class="summary">Web 2.0 Conference</span>: 
 <abbr class="dtstart" title="2005-10-05">October 5</abbr>-
 <abbr class="dtend" title="2005-10-07">7</abbr>,
 at the <span class="location">Argent Hotel, San Francisco, CA</span>
</div>
</source>

which could be displayed as:

<div class="vevent">
<span class="url">http://conferences.oreillynet.com/pub/w/40/program.html</span>&nbsp;<!-- note modified to account for idiosyncrasy of wiki software -->
<span class="summary">Web 2.0 Conference</span>: 
<abbr class="dtstart" title="2005-10-05">October 5</abbr>-
<abbr class="dtend" title="2005-10-07">7</abbr>,
at the <span class="location">Argent Hotel, San Francisco, CA</span>
</div>

Note 1: that this is a '''live''' hCalendar microformat, which will be found on this page by parsers.

Note 2: This example used to have "2005-10-08" as the value of the dtend, but per the resolution to the [[dtend-issue]], has been changed to "2005-10-07" in order to encourage publishers/implementers to update their markup/code immediately and [http://ufxtract.com/testsuite/hcalendar/hcalendar1.htm test it].

Note 3: Note that the iCalendar in the first part of the example has the code <code>DTEND:20051008</code>. That "8" is not a typo. iCalendar uses <em>exclusive</em> whole end dates (DTEND values) and thus requires that the DTEND value be set to a whole day <em>after</em> what content publishers visibly display as the ending date of an event. iCalendar's exclusive end dates convention has shown to be [[dtend-issue|problematic and confusing]] for content authors and publishers. Thus per the resolution to the [[dtend-issue]], in hCalendar, the end date is stated exactly as existing events publish visible end dates to humans, with an <em>inclusive</em> end date (dtend property value), in this example, 2005-10-07.

=== Meeting Example ===
The following <span id="Example_2">example</span> specifies a scheduled meeting that begins
at 8:30 AM EST on March 12, 1998 and ends at 9:30 AM EST on March 12,
1998. 

<source lang=html4strict>
     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
</source>

The equivalent in hCalendar:

'''Note: This example needs to be updated to use the [[value-class-pattern]]. Use of full ISO8601 datetimes in abbr title attributes is deprecated in lieu of separate dates and times per the value-class-pattern.'''

<source lang=html4strict>
<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>
</source>

This could be displayed as:

----

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

----

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

Note 2: A surrounding <code><nowiki><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.

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

Note 4: [[iso-8601|ISO8601]] datetimes (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.  '''Update: Per the [[value-class-pattern]], separate dates and times {{should}} be used by authors rather than a full ISO8601 datetime, for better readability and listenability.'''

Note 5: Per the [[dtend-issue]] resolution, DTEND dates are provided as humans expecte them to be (consistent with what day an event ends on), rather than iCalendar's confusing definition (the day after). Thus hCalendar processors which produce iCalendar must make the transformation, which is to treat a whole hCalendar <code>dtend</code> end date as *inclusive*, and convert it to an *[http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html exclusive DTEND]* end date when producing iCalendar.

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


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

== Articles ==
This section is <strong>informative</strong>. Articles and blog posts on hCalendar, most recent first. When it gets too big, we can move it to a page like [[hcalendar-articles]].

* <span class="hentry"><span class="published">2009-08-19</span> (Updated: <span class="updated">2009-09-10</span>) <cite class="entry-title">[http://dev.opera.com/articles/view/styling-and-extracting-hcalendar/ Styling and extracting hCalendar]</cite> by  <span class="vcard author"><span class="fn org">[http://dev.opera.com/author/1048426 Christopher Schmitt]</span></span></span>
* 2008-11-17 [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]
* 2008-10-01 [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]
* 2008-02-01 [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]
* 2006-01-11 [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]

==Buttons==
This section is <strong>informative</strong>. 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!

== Copyright ==
Per the public domain release on the authors' user pages ([[User:Tantek|Tantek Çelik]], [[User:Brian|Brian Suda]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== 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 ===
This section is <strong>informative</strong>.
* [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]

== Inspiration and Acknowledgments ==
Thanks to:
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties.

== Related Reading ==
This section is <strong>informative</strong>.
Some <span id="Further_Reading">further reading</span> on the broader topic of calendars and calendaring formats.
* [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>

== Related Pages ==
{{hcalendar-related-pages}}
* [http://en.wikipedia.org/wiki/HCalendar Wikipedia article on hCalendar]

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

== Translations ==
Read the hCard specification in additional <span id="languages">languages</span>:
* [[hcalendar-fr|français]]
* [[hcalendar-ru|Русский]]
* [[hcalendar-ja|日本語]]