Difference between revisions of "hcalendar"

From Microformats Wiki
hcalendar
Jump to navigation Jump to search
m (Reverted edit of Robindranatt, changed back to last version by Tantek)
Line 27: Line 27:
  
 
== Introduction ==
 
== 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).
+
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.
 
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.
Line 43: Line 43:
 
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.
 
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.
+
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.
 
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.
Line 50: Line 50:
  
 
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
 
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <code>URL</code> in iCalendar becomes  <code><a class="url" href="...">...</a></code> inside the element with <code>class="vevent"</code> in hCalendar.
+
* <code>URL</code> in iCalendar becomes  <code><a class=&quot;url&quot; href=&quot;...&quot;>...</a></code> inside the element with <code>class=&quot;vevent&quot;</code> in hCalendar.
 
* <code>ATTENDEE</code> in iCalendar may in hCalendar be represented by an [[hcard]].
 
* <code>ATTENDEE</code> in iCalendar may in hCalendar be represented by an [[hcard]].
  
 
=== Singular vs. Plural Properties ===
 
=== 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 are singular (e.g. &quot;N&quot; and &quot;FN&quot; 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.  
+
For properties which can be plural (e.g. &quot;TEL&quot; 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.  
  
 
=== Human vs. Machine readable ===
 
=== Human vs. Machine readable ===
If an <code>&lt;abbr&gt;</code> element is used for a property, then the '<code>title</code>' attribute of the <code>&lt;abbr&gt;</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>&lt;abbr&gt;</code> elements be used for the following iCalendar properties:
+
If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute of the <code><abbr></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><abbr></code> elements be used for the following iCalendar properties:
 
* DTSTART, DTEND, DURATION, RDATE, RRULE
 
* DTSTART, DTEND, DURATION, RDATE, RRULE
  
Line 82: Line 82:
  
 
<pre><nowiki>
 
<pre><nowiki>
<span class="vevent">
+
<span class=&quot;vevent&quot;>
  <a class="url" href="http://www.web2con.com/">
+
  <a class=&quot;url&quot; href=&quot;http://www.web2con.com/&quot;>
   <span class="summary">Web 2.0 Conference</span>:  
+
   <span class=&quot;summary&quot;>Web 2.0 Conference</span>:  
   <abbr class="dtstart" title="2005-10-05">October 5</abbr>-
+
   <abbr class=&quot;dtstart&quot; title=&quot;2005-10-05&quot;>October 5</abbr>-
   <abbr class="dtend" title="2005-10-08">7</abbr>,
+
   <abbr class=&quot;dtend&quot; title=&quot;2005-10-08&quot;>7</abbr>,
  at the <span class="location">Argent Hotel, San Francisco, CA</span>
+
  at the <span class=&quot;location&quot;>Argent Hotel, San Francisco, CA</span>
 
  </a>
 
  </a>
 
</span>
 
</span>
Line 97: Line 97:
 
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 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 &lt;span class="vcalendar"&gt; 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 2: A surrounding <span class=&quot;vcalendar&quot;> 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=&quot;vcalendar&quot; 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 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.
  
Note 4: ISO8601 dates (required by iCalendar) are not very human friendly.  In addition, the year is often understood implicitly by humans from the context.  Thus <code>&lt;abbr&gt;</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.
+
Note 4: ISO8601 dates (required by iCalendar) are not very human friendly.  In addition, the year is often understood implicitly by humans from the context.  Thus <code><abbr></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 YYYY-MM-DD should be used for better readability.
 
The notation YYYY-MM-DD should be used for better readability.
  
Line 111: Line 111:
 
This section is '''informative'''.
 
This section is '''informative'''.
  
The following sites have implemented hCalendar, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc.  If events on your pages are marked up with hCalendar, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.
+
The following sites have implemented hCalendar, and thus are a great place to start for anyone looking for examples &quot;in the wild&quot; to try parsing, indexing, organizing etc.  If events on your pages are marked up with hCalendar, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.
  
 
* [http://www.webanalyticsassociation.org/en/calendarevents/search.asp  Web Analytics Association] - hCalendar microformat is in place on all Tendenci sites on the calendar events search page and consolidated list page.
 
* [http://www.webanalyticsassociation.org/en/calendarevents/search.asp  Web Analytics Association] - hCalendar microformat is in place on all Tendenci sites on the calendar events search page and consolidated list page.
Line 133: Line 133:
 
* [http://paulschreiber.com/ Paul] Schreiber's [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCalendar event information for upcoming concerts.  In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCalendar events for all past concerts.
 
* [http://paulschreiber.com/ Paul] Schreiber's [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCalendar event information for upcoming concerts.  In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCalendar events for all past concerts.
 
* [http://paulschreiber.com/ Paul] Schreiber's [http://iceoasis.shrub.ca/ unofficial schedule site] publishes hCalendar information for upcoming hockey games at [http://www.iceoasis.com/ Ice Oasis]
 
* [http://paulschreiber.com/ Paul] Schreiber's [http://iceoasis.shrub.ca/ unofficial schedule site] publishes hCalendar information for upcoming hockey games at [http://www.iceoasis.com/ Ice Oasis]
* [http://www.complexspiral.com/ Complex Spiral Consulting], both in the "Events" box on left side, and the separate [http://www.complexspiral.com/events/ Events page].  
+
* [http://www.complexspiral.com/ Complex Spiral Consulting], both in the &quot;Events&quot; box on left side, and the separate [http://www.complexspiral.com/events/ Events page].  
* [http://tantek.com/log Tantek's Thoughts], specifically the "Events" roll in the right-most column.
+
* [http://tantek.com/log Tantek's Thoughts], specifically the &quot;Events&quot; roll in the right-most column.
 
* [http://suda.co.uk/projects/holidays/ Lesser Known Holidays], a list of holidays on [http://suda.co.uk suda.co.uk] that can be imported via iCal and hCal so you can compare actual transformation versus intended.
 
* [http://suda.co.uk/projects/holidays/ Lesser Known Holidays], a list of holidays on [http://suda.co.uk suda.co.uk] that can be imported via iCal and hCal so you can compare actual transformation versus intended.
 
* [http://norman.walsh.name/2005/itinerary/ Norm Walsh's travel schedule] use hCalendar as well as GRDDL.
 
* [http://norman.walsh.name/2005/itinerary/ Norm Walsh's travel schedule] use hCalendar as well as GRDDL.
Line 185: Line 185:
 
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (required 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):
 
* [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>
+
<blockquote>&quot;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.'''&quot;</blockquote>
  
 
* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]
 
* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]
Line 207: Line 207:
 
=== Issues ===
 
=== Issues ===
 
* Please add any issues with the specification to the separate [[hcalendar-issues]] document.
 
* Please add any issues with the specification to the separate [[hcalendar-issues]] document.
 +
Leica Digital M announcement for PMA? <b>beach photography wedding san jose</b> EOS-1D Mark II N also fixes <b>8mp digital slr camera with ef s 18</b> a file numbering error that occurred accessories for kodak digital camera during bulb shooting. Lively discussion forums. <b>best choice digital camera below ?150</b> As well as exhibitors such as <u>beach photography wedding san jose</u> Kodak, Fujifilm, HP, Nikon, Olympus, Panasonic <strong>35mm digital camera accessories</strong> and Sony on the show floor. <strong>bay area wedding photography in san jose</strong> Sigma has confirmed that there is <b>35mm point and shoot camera reviews</b> an incompatibility issue between its HSM <strong>8mp digital slr camera</strong> equipped lenses and the new Nikon <b>6 mp olympus digital camera</b> D200. DS2 and Sony DSC-R1. Chinese <b>best digital camera for firework pictures</b> consumers who purchased these cameras can <u>350d digital rebel xt digital slr camera</u> return them to Sony for a <strong>aiptek 4000 4.0 megapixel digital camera</strong> refund. Aperture fits into a day 8 mg digital camera comparison long event showcasing the wide range 5 megapixel digital camera comparison of complementary services which can be <b>bay area wedding photography bay area</b> applied to digital imaging, an Industry <strong>123 digital imaging</strong> Insider session presented by Antonio Perez, <u>best compact digital camera</u> president and CEO of Eastman Kodak <i>absolute digital imaging</i> as well as exhibitors such as <u>american idol camcorder</u> Kodak, Fujifilm, HP, Nikon, Olympus, Panasonic <b>best digital camera photo</b> and Sony on the show floor. <b>best deal digital camera</b> Nine Sony cameras were selected for <u>10d camera eos slr</u> inspection and six failed. Net Consulting best deal digital camera Ltd. The affected cameras are the <i>4300 camera coolpix digital nikon review</i> DSC-H1, DSC-L1, DSC-P200, DSC-W7, DSC-W5 and <u>accessories for olympus digital cameras</u> DSC-S90. We expect to hear more <b>8mp digital slr camera with ef s 18</b> at PMA in February. EOS-1D Mark <u>amateur cameras</u> II N and EOS 5D. D <i>best digital camera comparison</i> also has a smaller body, re-worked <i>a95 camera canon digital review</i> design, DIGIC II, new features and <b>best 3-4 mp digital camera</b> custom functions. Apple has updated its <b>anamolies in digital photography</b> professional photo application, Aperture. Anybody besides <strong>35mm point and shoot camera reviews</strong> me HATE shooting RAW? Sigma has <strong>beach photography wedding san jose</strong> stated that this is due to <b>a345 digital camera reviews</b> a report by Interfax China. Leica <u>bell & howell digital cameras</u> are readying a digital version of <strong>35 mm slr camera and lens $200</strong> dpreview. Is Zooming the same as <i>1ds mark ii digital slr camera</i> getting closer? Canon has today posted <strong>5x optical zoom digital cameras reviews</strong> firmware updates for the EOS-1D Mark best camera reviews II N and EOS 5D. Sigma <strong>8mp digital slr camera with ef s 18</strong> has confirmed that there is an bell howell keychain digital camera review incompatibility issue between its HSM equipped <i>accessory camera digital jvc video</i> lenses and the new image stabilizing <b>best digital camera for under $150</b> feature the P850 boasts RAW file <strong>300d digital slr camera</strong> capture and a flash hot shoe, best digital camera greens slr plus a real wealth of photographic <strong>accessory camera digital kit</strong> controls. National Camera Quality Supervision and <u>bell and howell digital camera reviews</u> Inspection Center, according to a firmware <u>35mm digital camera accessories</u> bug in the lens itself and <i>10 best digital camera</i> will soon be introducing a free best digital camcorder of charge firmware update for affected <b>american idol camcorder</b> lenses. Find out how it fared best digital camera for in our concise review, after the analogue + digital + cameras + reviews link.
 +
<A href='http://getpaid5.white.prohosting.com/'>digital camera review</A>
 +
<A href='http://getpaid5.white.prohosting.com/best-deals-digital-cameras.html'>digital camera review</A>
 +
<A href='http://busines5.white.prohosting.com/'>digital camera review</A>
 +
<A href='http://busines5.white.prohosting.com/best-digital-camera-review.html'>digital camera review</A>
 +
<A href='http://200money.white.prohosting.com/'>digital camera review</A>
 +
<A href='http://200money.white.prohosting.com/cameras.html'>digital camera review</A>

Revision as of 00:55, 2 January 2006

hCalendar

hCalendar is a simple open, distributed calendaring and events format, based on the iCalendar standard (RFC2445), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open microformat standards.

Draft Specification

Editor

Tantek Çelik (Technorati, Inc)

Authors

Copyright

This specification is (C) 2004-2020 by the authors. However, the authors intend to submit (or already have submitted, see details in the spec) this specification to a standards body with a liberal copyright/licensing policy such as the GMPG, IETF, and/or W3C. Anyone wishing to contribute should read their copyright principles, policies and licenses (e.g. the GMPG Principles) and agree to them, including licensing of all contributions under all required licenses (e.g. CC-by 1.0 and later), before contributing.

Patents

This specification is subject to a royalty free patent policy, e.g. per the W3C Patent Policy, and IETF RFC3667 & RFC3668.

Inspiration and Acknowledgments

Thanks to:


Introduction

The iCalendar standard (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 XHTML. 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.

Semantic XHTML Design Principles

Note: the Semantic XHTML Design Principles were written primarily within the context of developing hCard and hCalendar, thus it may be easier to understand these principles in the context of the hCard design methodology (i.e. read that first). Tantek

XHTML is built on XML, and thus XHTML based formats can be used not only for convenient display presentation, but also for general purpose data exchange. In many ways, XHTML based formats exemplify the best of both HTML and XML worlds. However, when building XHTML based formats, it helps to have a guiding set of principles.

  1. Reuse the schema (names, objects, properties, values, types, hierarchies, constraints) as much as possible from pre-existing, established, well-supported standards by reference. Avoid restating constraints expressed in the source standard. Informative mentions are ok.
    1. For types with multiple components, use nested elements with class names equivalent to the names of the components.
    2. Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.
  2. Use the most accurately precise semantic XHTML building block for each object etc.
  3. Otherwise use a generic structural element (e.g. <span> or <div>), or the appropriate contextual element (e.g. an <li> inside a <ul> or <ol>).
  4. Use class names based on names from the original schema, unless the semantic XHTML building block precisely represents that part of the original schema. If names in the source schema are case-insensitive, then use an all lowercase equivalent. Components names implicit in prose (rather than explicit in the defined schema) should also use lowercase equivalents for ease of use. Spaces in component names become dash '-' characters.
  5. Finally, if the format of the data according to the original schema is too long and/or not human-friendly, use <abbr> instead of a generic structural element, and place the literal data into the 'title' attribute (where abbr expansions go), and the more brief and human readable equivalent into the element itself. Further informative explanation of this use of <abbr>: Human vs. ISO8601 dates problem solved

Format

In General

The iCalendar standard (RFC2445) forms the basis of hCalendar.

Note: the editor and authors of this specification are tracking the "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.

More Semantic Equivalents

However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

  • URL in iCalendar becomes <a class="url" href="...">...</a> inside the element with class="vevent" in hCalendar.
  • ATTENDEE in iCalendar may in hCalendar be represented by an hCard 1.0.

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.

Human vs. Machine readable

If an element is used for a property, then the 'title' attribute of the 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 elements be used for the following iCalendar properties:

  • DTSTART, DTEND, DURATION, RDATE, RRULE

Example

Here is a sample event in an iCalendar:

BEGIN:VCALENDAR
PRODID:-//XYZproduct//EN
VERSION:2.0
BEGIN:VEVENT
URL:http://www.web2con.com/
DTSTART:20051005
DTEND:20051008
SUMMARY:Web 2.0 Conference
LOCATION:Argent Hotel\, San Francisco\, CA
END:VEVENT
END:VCALENDAR

and an equivalent event in hCalendar format with various elements optimized appropriately. See hCalendar Example 1 Steps for the derivation.

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

which could be displayed as:

Web 2.0 Conference: October 5-7, at the Argent Hotel, San Francisco, CA

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

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

Note 4: ISO8601 dates (required by iCalendar) are not very human friendly. In addition, the year is often understood implicitly by humans from the context. Thus 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 YYYY-MM-DD should be used for better readability.

Note 5: The difference between the DTEND ISO8601 date (2005-10-08) and the human readable date (7) is NOT a mistake. 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.

See hCalendar examples for more hCalendar examples

Examples in the wild

This section is informative.

The following sites have implemented hCalendar, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If events on your pages are marked up with hCalendar, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

Implementations

This section is informative.

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

Generation

Conversion and consumption

Investigation:

References

Normative References

Informative References

Related

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

Similar Work

Discussions

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

Q&A

  • If you have any questions about hCalendar, check the hcalendar-faq, and if you don't find answers, add your questions!

Issues

  • Please add any issues with the specification to the separate hCalendar issues document.

Leica Digital M announcement for PMA? beach photography wedding san jose EOS-1D Mark II N also fixes 8mp digital slr camera with ef s 18 a file numbering error that occurred accessories for kodak digital camera during bulb shooting. Lively discussion forums. best choice digital camera below ?150 As well as exhibitors such as beach photography wedding san jose Kodak, Fujifilm, HP, Nikon, Olympus, Panasonic 35mm digital camera accessories and Sony on the show floor. bay area wedding photography in san jose Sigma has confirmed that there is 35mm point and shoot camera reviews an incompatibility issue between its HSM 8mp digital slr camera equipped lenses and the new Nikon 6 mp olympus digital camera D200. DS2 and Sony DSC-R1. Chinese best digital camera for firework pictures consumers who purchased these cameras can 350d digital rebel xt digital slr camera return them to Sony for a aiptek 4000 4.0 megapixel digital camera refund. Aperture fits into a day 8 mg digital camera comparison long event showcasing the wide range 5 megapixel digital camera comparison of complementary services which can be bay area wedding photography bay area applied to digital imaging, an Industry 123 digital imaging Insider session presented by Antonio Perez, best compact digital camera president and CEO of Eastman Kodak absolute digital imaging as well as exhibitors such as american idol camcorder Kodak, Fujifilm, HP, Nikon, Olympus, Panasonic best digital camera photo and Sony on the show floor. best deal digital camera Nine Sony cameras were selected for 10d camera eos slr inspection and six failed. Net Consulting best deal digital camera Ltd. The affected cameras are the 4300 camera coolpix digital nikon review DSC-H1, DSC-L1, DSC-P200, DSC-W7, DSC-W5 and accessories for olympus digital cameras DSC-S90. We expect to hear more 8mp digital slr camera with ef s 18 at PMA in February. EOS-1D Mark amateur cameras II N and EOS 5D. D best digital camera comparison also has a smaller body, re-worked a95 camera canon digital review design, DIGIC II, new features and best 3-4 mp digital camera custom functions. Apple has updated its anamolies in digital photography professional photo application, Aperture. Anybody besides 35mm point and shoot camera reviews me HATE shooting RAW? Sigma has beach photography wedding san jose stated that this is due to a345 digital camera reviews a report by Interfax China. Leica bell & howell digital cameras are readying a digital version of 35 mm slr camera and lens $200 dpreview. Is Zooming the same as 1ds mark ii digital slr camera getting closer? Canon has today posted 5x optical zoom digital cameras reviews firmware updates for the EOS-1D Mark best camera reviews II N and EOS 5D. Sigma 8mp digital slr camera with ef s 18 has confirmed that there is an bell howell keychain digital camera review incompatibility issue between its HSM equipped accessory camera digital jvc video lenses and the new image stabilizing best digital camera for under $150 feature the P850 boasts RAW file 300d digital slr camera capture and a flash hot shoe, best digital camera greens slr plus a real wealth of photographic accessory camera digital kit controls. National Camera Quality Supervision and bell and howell digital camera reviews Inspection Center, according to a firmware 35mm digital camera accessories bug in the lens itself and 10 best digital camera will soon be introducing a free best digital camcorder of charge firmware update for affected american idol camcorder lenses. Find out how it fared best digital camera for in our concise review, after the analogue + digital + cameras + reviews link. <A href='http://getpaid5.white.prohosting.com/'>digital camera review</A> <A href='http://getpaid5.white.prohosting.com/best-deals-digital-cameras.html'>digital camera review</A> <A href='http://busines5.white.prohosting.com/'>digital camera review</A> <A href='http://busines5.white.prohosting.com/best-digital-camera-review.html'>digital camera review</A> <A href='http://200money.white.prohosting.com/'>digital camera review</A> <A href='http://200money.white.prohosting.com/cameras.html'>digital camera review</A>