[uf-discuss] hCards within hCalendar (was: Nested Microformats and Operator)

[Andy Mabbett]

In message <fVT9sQr$VA1GFwo1 at pigsonthewing.org.uk>, Andy Mabbett
<andy at pigsonthewing.org.uk> writes

>I note that "attendee", "contact" and "organizer" are listed in the
>hCalendar spec, but not the cheat-sheet.

Fixed; but their status needs to be codified; and examples provided on
the relevant 'wiki' pages.

I note that the iCalendar RFC <http://www.ietf.org/rfc/rfc2445.txt>
states that :

        4.8.4.1

        ATTENDEE.

        Conformance: This property MUST be specified in an iCalendar
        object that specifies a group scheduled calendar entity. This
        property MUST NOT be specified in an iCalendar object when
        publishing the calendar information (e.g., NOT in an iCalendar
        object that specifies the publication of a calendar user's busy
        time, event, to-do or journal). This property is not specified
        in an iCalendar object that specifies only a time zone
        definition or that defines calendar entities that are not group
        scheduled entities, but are entities only on a single user's
        calendar.

and:

        4.8.4.2

        CONTACT

        Description: The property value consists of textual contact
        information. An alternative representation for the property
        value can also be specified that refers to a URI pointing to an
        alternate form, such as a vCard [RFC 2426], for the contact
        information.

and:

        4.8.4.3

        ORGANIZER

        Conformance: This property MUST be specified in an iCalendar
        object that specifies a group scheduled calendar entity. This
        property MUST be specified in an iCalendar object that specifies
        the publication of a calendar user's busy time. This property
        MUST NOT be specified in an iCalendar object that specifies only
        a time zone definition or that defines calendar entities that
        are not group scheduled entities, but are entities only on a
        single user's calendar.


So we need to decide whether we adhere to those rules or adopt a more
relaxed approach, and leave it to parsers to adhere to them when
exporting vEvents.

-- 
Andy Mabbett