The model round-trips through System.Text.Json with default options, so a component can be stored or queued as
JSON and read back with the same values. This is the library's own shape, not jCal (RFC 7265).
string json = JsonSerializer.Serialize(component);
IcalComponent? restored = JsonSerializer.Deserialize<IcalComponent>(json);
Kind, Uid, Sequence, Start, Attendees,UnknownProperties and so on. Enums are numbers unless you add a JsonStringEnumConverter; their numeric valuesDateTimeOffset values use the System.Text.Json ISO 8601 form; TimeSpan (alarm triggers) its hh:mm:ss form.UnknownProperties and OverrideComponents are arrays of strings, exactly as on the wireIcalProperty serializes Name, Value, Kind and Parameters.IcalParameter has its own converter, IcalParameterJsonConverter, applied by attribute:
{ "Name": "FEATURE", "Values": ["AUDIO", "VIDEO"] }
On the way in it also reads the single-value form { "Name": "FMTTYPE", "Value": "text/html" }, so JSON written
before parameters were multi-valued still deserializes. Property names are matched case-insensitively; unknown
properties are skipped; Name is required, and a missing one is a JsonException. Value is never written; it
is the first of Values.
The JSON shape follows the public model, which is covered by package validation and a public API baseline: a
member is never removed or renamed within a major version, so JSON written by an earlier 1.x deserializes in a
later one. New members may appear; with default options an older reader ignores them.