Expand description
iCalendar (RFC 5545) and vCard (RFC 6350 / 2426) objects as CalDAV and CardDAV need them: content lines unfolded and parsed, components nested and checked, the UID found, and the properties the REPORT filters read.
Structs§
Constants§
Functions§
- check_
calendar - A calendar object resource (RFC 4791 §4.1): VCALENDAR with VERSION and PRODID, components of one type (timezones aside) sharing one UID. Returns (component type, UID).
- check_
vcard - A vCard address object (RFC 6352 §5.1): one VCARD with VERSION 3.0 or 4.0, FN and UID.
- duration
- RFC 5545 §3.3.6 duration in seconds (
P1D,PT1H30M,-P1W). - overlaps
- Whether a component overlaps
[start, end)(RFC 4791 §9.9). A recurring component (RRULE or RDATE) is treated as extending without end from its first start — recurrence sets are not expanded, so a query may return a recurring object whose instances miss the range, never the reverse. - parse
- Parse one top-level component (
BEGIN:<root>…END:<root>). - text_
match - CalDAV/CardDAV text-match with the default
i;unicode-casemapcollation, approximated by Unicode lower-casing;match_typeis equals, contains, starts-with or ends-with. - timestamp
- iCalendar DATE or DATE-TIME as seconds since the epoch (floating and TZID times read as UTC, which the CalDAV query documentation states).