What DevOp.ICalendar does with each standard, taken from the code, not from intentions. Supported means
written and read as typed members; partial means a typed subset, with the rest as described;
preserved means not modelled, but kept verbatim inside a modelled component through a parse and a serialize;
not supported means not modelled and not kept.
| Standard | Status | What is covered |
|---|---|---|
| RFC 5545 iCalendar | Partial | VEVENT, VTODO, VJOURNAL with the properties on the model page; content lines and nested components inside them that are not modelled are preserved. RRULE subset (FREQ daily to yearly, INTERVAL, COUNT or UNTIL, plain BYDAY) typed; a rule outside it is read as far as the subset goes and preserved verbatim, as are EXDATE and RDATE. VTIMEZONE written for zoned series, not read. VALARM display subset typed, other alarms preserved. 75-octet folding by UTF-8 octets, TEXT escaping, DATE and UTC DATE-TIME values, TZID read through the host's zone database. Other top-level components (VFREEBUSY, VTIMEZONE and so on) and calendar properties other than PRODID and METHOD are not supported. |
| RFC 5546 iTIP | Partial | All eight methods on METHOD; a REPLY with a typed alarm is refused and verbatim alarms are left out of it (§3.2.3). UID and SEQUENCE are the caller's. Scheduling processing (applying a reply, sequence rules, delegation) is not part of the library. |
| RFC 6047 iMIP | Supported (compose and classify) | multipart/alternative with an inline text/calendar part, method= matching the payload's METHOD (§2.4, a mismatch is refused), charset=utf-8, Content-Class. Inbound: classifies one MIME part; walking a MIME tree is not part of the library. |
| RFC 6868 parameter encoding | Supported | ^^, ^n and ^' written and read on every parameter value, quoting only where needed. |
| RFC 7986 new properties | Partial | CONFERENCE with FEATURE and LABEL typed (other features or parameters preserved). IMAGE written through a typed property, preserved on parse. COLOR, NAME, REFRESH-INTERVAL, SOURCE not modelled: preserved inside a component, not supported at calendar level. |
| RFC 7529 non-Gregorian recurrence | Preserved | An RRULE with RSCALE or SKIP is kept verbatim, not interpreted. |
| RFC 7953 VAVAILABILITY | Not supported | A top-level VAVAILABILITY is skipped on parse. |
| RFC 9073 event publishing extensions | Partial | DERIVED=TRUE on DESCRIPTION typed. STYLED-DESCRIPTION written through a typed property, preserved on parse. STRUCTURED-DATA, PARTICIPANT, VLOCATION, VRESOURCE preserved inside a component. |
| RFC 9074 VALARM extensions | Partial | Alarm UID typed (TEXT). ACKNOWLEDGED, RELATED-TO, PROXIMITY and snooze alarms preserved: an alarm carrying any of them is kept verbatim. |
| RFC 9253 relationships | Preserved | LINK, CONCEPT, REFID and RELATED-TO with RELTYPE kept verbatim inside a component. |
| RFC 10051 task extensions | Preserved | The new VTODO properties and components are kept verbatim inside a VTODO. The extended PARTSTAT values on ATTENDEE are not kept: an unknown PARTSTAT reads as NEEDS-ACTION. |
| RFC 6350 vCard | Not applicable | ContentLine exposes the shared content-line primitives (escape, fold, unfold, parse) for a vCard writer; there is no vCard model. |
| RFC 7265 jCal, RFC 6321 xCal | Not supported | The model round-trips through System.Text.Json in its own shape; see JSON. |
net10.0, net8.0 and netstandard2.0, with one public API (checked by package validation and a public API
baseline). Folding never splits a grapheme cluster: on net8.0 and later through the runtime's UAX #29
segmentation; on netstandard2.0 through the library's own subset of those rules (emoji ZWJ sequences, flags,
skin tones, variation selectors, combining marks and Hangul syllables stay whole; Indic conjuncts and prepend
characters may fold between code points, which unfolding restores exactly). On .NET Framework a TZID resolves
only if the host's zone database knows the id, which for IANA ids usually means it does not.
The roadmap lists what is planned beyond this.