Description
Audit distinct supplied payloads for equal UID/SEQUENCE observations; no calendar merge, latest revision or recurrence resolution claim.
iCalendar separates content-line framing, property values, parameters and component nesting. TEXT escaping protects separators, while line folding is based on encoded octets. DATE, floating time, UTC and named-zone representations carry different information; a token-level operation does not resolve a timezone or expand recurrence rules.1
Audit distinct supplied payloads for equal UID/SEQUENCE observations; no calendar merge, latest revision or recurrence resolution claim.
When to use this tool
Use this tool to audit distinct supplied payloads for equal UID/SEQUENCE observations; no calendar merge, latest revision or recurrence resolution claim.
How to use the tool and how it works
- Enter eventsJson using the field definitions below. For JSON text, serialize the explicit records in the shown shape.
- Run the operation. Correct input errors before interpreting an output.
- Read result.conflicts. Use the ordering, boundary rules and absence conditions described below.
Group event records by exact UID and sequence, then return groups with more than one distinct payload string.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| eventsJson | JSON text encoding array of {uid: string, sequence: number, payload: string}. Keep the record keys and value types shown in the decoded example below. | Text, at most 8,192 UTF-16 code units; the operation’s grammar also applies. |
These are the decoded structures used in the example’s JSON text fields. Supply the corresponding serialized JSON strings as input.
{
"eventsJson": [
{
"uid": "x",
"sequence": 1,
"payload": "a"
},
{
"uid": "x",
"sequence": 1,
"payload": "b"
}
]
}| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.conflicts | UID/sequence groups containing different exact payload strings. |
{
"input": {
"eventsJson": "[{\"uid\":\"x\",\"sequence\":1,\"payload\":\"a\"},{\"uid\":\"x\",\"sequence\":1,\"payload\":\"b\"}]"
},
"output": {
"result": {
"conflicts": [
{
"key": "[\"x\",1]",
"indexes": [
0,
1
]
}
]
}
}
}Limitations and assumptions
- Payloads are compared literally; no calendar parsing, revision selection or conflict resolution occurs.
- Content spans use zero-based UTF-16 offsets; fold limits use UTF-8 bytes including the continuation space. Token helpers handle the stated subset only, without a timezone database, recurrence engine or calendar import.
- Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Keep content-line syntax, value escaping and timezone interpretation separate. Use a complete iCalendar implementation for recurrence expansion, timezone transitions and property-specific validation.
References
Similar or alternative tools
- iCalendar Component Boundary Stack Audit
Audit explicit iCalendar BEGIN/END boundary tokens using a stack, retaining mismatches and unclosed components; not complete property/component semantic validation.
- iCalendar Content Line Name Parameter Split
Split an unfolded iCalendar content line at its unquoted first colon and semicolon parameter boundaries; value remains opaque, raw parameters retain quote-aware spelling, no RFC 6868 decoding or component validation.