Description
Audit strict-positive period order on already resolved same-scale numeric endpoint observations, retaining signed duration; does not parse iCalendar timestamps or resolve zones.
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 strict-positive period order on already resolved same-scale numeric endpoint observations, retaining signed duration; does not parse iCalendar timestamps or resolve zones.
When to use this tool
Use this tool to audit strict-positive period order on already resolved same-scale numeric endpoint observations, retaining signed duration; does not parse iCalendar timestamps or resolve zones.
How to use the tool and how it works
- Enter periodsJson 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.periods. Use the ordering, boundary rules and absence conditions described below.
For each numeric start/end record, return end minus start and ordered indicating whether end is strictly greater than start.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| periodsJson | JSON text encoding array of {start: number, end: number}. 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.
{
"periodsJson": [
{
"start": 4,
"end": 2
}
]
}| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.periods | Input-order numeric periods with index, duration and ordered flag. |
{
"input": {
"periodsJson": "[{\"start\":4,\"end\":2}]"
},
"output": {
"result": {
"periods": [
{
"start": 4,
"end": 2,
"index": 0,
"ordered": false,
"duration": -2
}
]
}
}
}Limitations and assumptions
- Equal or reversed endpoints are reported, not rejected; values must already use a consistent time scale and unit.
- 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.