@northguild/gmt 1.18.0 → 1.20.0

package/dist/intermodal/validate/isValidEdifactDtmFormat.d.ts

@@ -0,0 +1,39 @@
+import type { EdifactDtmFormat } from "../../types/edi.js";
+/**
+ * Return true when `format` is a UN/EDIFACT data element 2379 format code that the EDIFACT
+ * functions read and write.
+ *
+ * - The 11 supported codes are `102` (a date); `401`, `402` (a time); `203`, `204` (a date and
+ *   time with no offset); `205`, `208`, `303`, `304` (a date and time with an offset); `718` (a
+ *   period of dates) and `719` (a period of date-times). `classifyEdifactDtmFormat` names the
+ *   kind of a code, and each kind has its own parser, formatter and validator.
+ * - A code with a two-digit year returns false: `101`, `201`, `202`, `206`, `207`, `301`,
+ *   `302`, `713` and `717`. UN/EDIFACT does not say which century `YY` belongs to; read such a
+ *   value with `parseDateWithPattern` or `parseDateTimeWithPattern`, a `yy` pattern and its
+ *   `yearWindow` option.
+ * - `209` and `404` (a time with an offset and no date) and `406` (an offset alone) return
+ *   false: none names a date, a time, a date-time or an instant.
+ * - Every other 2379 code returns false: the day-first and month-first dates `2`–`5`, `10`
+ *   (`CCYYMMDDTHHMM`), `103`, the ordinal date `105`, `210`, `307`, `308`, the time spans
+ *   `501`–`503`, `711`, the partial values, the weekday period `720` and the quantities (`801`
+ *   and up).
+ * - Matching is exact: `" 203"`, `"0203"` and the number `203` are not codes.
+ * - Accepts any input type and returns false for non-string values.
+ * - A parser returns its sentinel for a code it does not read, the same sentinel it returns for
+ *   a value that does not fit its code. Check the code here to tell an unsupported format apart
+ *   from bad data.
+ *
+ * @param format candidate value of any type
+ * @returns boolean indicating validity
+ *
+ * @example isValidEdifactDtmFormat("203") // true
+ * @example isValidEdifactDtmFormat("718") // true
+ * @example isValidEdifactDtmFormat("208") // true
+ * @example isValidEdifactDtmFormat("101") // false (a two-digit year: not read)
+ * @example isValidEdifactDtmFormat("602") // false (a partial value: not supported)
+ * @example isValidEdifactDtmFormat("801") // false (a quantity: not supported)
+ * @example isValidEdifactDtmFormat("0203") // false (matching is exact)
+ * @example isValidEdifactDtmFormat(203) // false (a code is a string)
+ * @example isValidEdifactDtmFormat(null) // false
+ */
+export declare function isValidEdifactDtmFormat(format: unknown): format is EdifactDtmFormat;

package/dist/intermodal/validate/isValidEdifactDtmFormat.js

@@ -0,0 +1,42 @@
+import { EDIFACT_DTM_FORMATS } from "../../internal/index.js";
+/**
+ * Return true when `format` is a UN/EDIFACT data element 2379 format code that the EDIFACT
+ * functions read and write.
+ *
+ * - The 11 supported codes are `102` (a date); `401`, `402` (a time); `203`, `204` (a date and
+ *   time with no offset); `205`, `208`, `303`, `304` (a date and time with an offset); `718` (a
+ *   period of dates) and `719` (a period of date-times). `classifyEdifactDtmFormat` names the
+ *   kind of a code, and each kind has its own parser, formatter and validator.
+ * - A code with a two-digit year returns false: `101`, `201`, `202`, `206`, `207`, `301`,
+ *   `302`, `713` and `717`. UN/EDIFACT does not say which century `YY` belongs to; read such a
+ *   value with `parseDateWithPattern` or `parseDateTimeWithPattern`, a `yy` pattern and its
+ *   `yearWindow` option.
+ * - `209` and `404` (a time with an offset and no date) and `406` (an offset alone) return
+ *   false: none names a date, a time, a date-time or an instant.
+ * - Every other 2379 code returns false: the day-first and month-first dates `2`–`5`, `10`
+ *   (`CCYYMMDDTHHMM`), `103`, the ordinal date `105`, `210`, `307`, `308`, the time spans
+ *   `501`–`503`, `711`, the partial values, the weekday period `720` and the quantities (`801`
+ *   and up).
+ * - Matching is exact: `" 203"`, `"0203"` and the number `203` are not codes.
+ * - Accepts any input type and returns false for non-string values.
+ * - A parser returns its sentinel for a code it does not read, the same sentinel it returns for
+ *   a value that does not fit its code. Check the code here to tell an unsupported format apart
+ *   from bad data.
+ *
+ * @param format candidate value of any type
+ * @returns boolean indicating validity
+ *
+ * @example isValidEdifactDtmFormat("203") // true
+ * @example isValidEdifactDtmFormat("718") // true
+ * @example isValidEdifactDtmFormat("208") // true
+ * @example isValidEdifactDtmFormat("101") // false (a two-digit year: not read)
+ * @example isValidEdifactDtmFormat("602") // false (a partial value: not supported)
+ * @example isValidEdifactDtmFormat("801") // false (a quantity: not supported)
+ * @example isValidEdifactDtmFormat("0203") // false (matching is exact)
+ * @example isValidEdifactDtmFormat(203) // false (a code is a string)
+ * @example isValidEdifactDtmFormat(null) // false
+ */
+export function isValidEdifactDtmFormat(format) {
+    return (typeof format === "string" &&
+        EDIFACT_DTM_FORMATS.includes(format));
+}

package/dist/intermodal/validate/isValidEdifactOffsetDateTime.d.ts

@@ -0,0 +1,36 @@
+import type { EdifactOffsetDateTimeFormat } from "../../types/edi.js";
+/**
+ * Return true when `value` is a UN/EDIFACT `DTM` value (data element 2380) that states a real
+ * date and time with an offset from UTC, in a format code that carries one (data element 2379).
+ *
+ * ### Format codes
+ * | Code | Mask | The directory's description |
+ * |---|---|---|
+ * | `205` | `CCYYMMDDHHMMZHHMM` | "Calendar date including time and time zone expressed in hours and minutes." |
+ * | `208` | `CCYYMMDDHHMMSSZHHMM` | "Calendar date including time with seconds, with Time Zone" (D.12A and later) |
+ * | `303` | `CCYYMMDDHHMMZZZ` | "See 203 plus Z=Time zone." |
+ * | `304` | `CCYYMMDDHHMMSSZZZ` | "See 204 plus Z=Time zone." |
+ *
+ * - True exactly when `parseEdifactOffsetDateTime` returns a value for the same arguments: the
+ *   validator calls the parser, so the two cannot disagree.
+ * - The three `ZZZ` characters of `303` and `304` are valid only as an offset: a signed hour
+ *   from `00` to `23`, `UTC` or `GMT`. An abbreviation such as `CET`, a broken offset (`+24`)
+ *   and a lone `Z` are false.
+ * - Takes the unescaped element value: `"202406151430?+02"` is false.
+ * - Checks the calendar as well as the shape: 29 February 2023, hour 24 and second 60 are
+ *   false.
+ * - False for any other code, a code of another kind included; check a code alone with
+ *   `isValidEdifactDtmFormat`. False for a non-string argument.
+ *
+ * @param value The data element 2380 value, unescaped (e.g. "202406151430+0200")
+ * @param format The data element 2379 format code
+ * @returns boolean indicating validity
+ *
+ * @example isValidEdifactOffsetDateTime("202406151430+0200", "205") // true
+ * @example isValidEdifactOffsetDateTime("20240615143045+0530", "208") // true
+ * @example isValidEdifactOffsetDateTime("202406151430UTC", "303") // true
+ * @example isValidEdifactOffsetDateTime("20240615143045-05", "304") // true
+ * @example isValidEdifactOffsetDateTime("202406151430CET", "303") // false (an abbreviation names no offset)
+ * @example isValidEdifactOffsetDateTime("202406151430", "205") // false (no offset)
+ */
+export declare function isValidEdifactOffsetDateTime(value: string, format: EdifactOffsetDateTimeFormat): boolean;

package/dist/intermodal/validate/isValidEdifactOffsetDateTime.js

@@ -0,0 +1,38 @@
+import { parseEdifactOffsetDateTime } from "../parse/parseEdifactOffsetDateTime.js";
+/**
+ * Return true when `value` is a UN/EDIFACT `DTM` value (data element 2380) that states a real
+ * date and time with an offset from UTC, in a format code that carries one (data element 2379).
+ *
+ * ### Format codes
+ * | Code | Mask | The directory's description |
+ * |---|---|---|
+ * | `205` | `CCYYMMDDHHMMZHHMM` | "Calendar date including time and time zone expressed in hours and minutes." |
+ * | `208` | `CCYYMMDDHHMMSSZHHMM` | "Calendar date including time with seconds, with Time Zone" (D.12A and later) |
+ * | `303` | `CCYYMMDDHHMMZZZ` | "See 203 plus Z=Time zone." |
+ * | `304` | `CCYYMMDDHHMMSSZZZ` | "See 204 plus Z=Time zone." |
+ *
+ * - True exactly when `parseEdifactOffsetDateTime` returns a value for the same arguments: the
+ *   validator calls the parser, so the two cannot disagree.
+ * - The three `ZZZ` characters of `303` and `304` are valid only as an offset: a signed hour
+ *   from `00` to `23`, `UTC` or `GMT`. An abbreviation such as `CET`, a broken offset (`+24`)
+ *   and a lone `Z` are false.
+ * - Takes the unescaped element value: `"202406151430?+02"` is false.
+ * - Checks the calendar as well as the shape: 29 February 2023, hour 24 and second 60 are
+ *   false.
+ * - False for any other code, a code of another kind included; check a code alone with
+ *   `isValidEdifactDtmFormat`. False for a non-string argument.
+ *
+ * @param value The data element 2380 value, unescaped (e.g. "202406151430+0200")
+ * @param format The data element 2379 format code
+ * @returns boolean indicating validity
+ *
+ * @example isValidEdifactOffsetDateTime("202406151430+0200", "205") // true
+ * @example isValidEdifactOffsetDateTime("20240615143045+0530", "208") // true
+ * @example isValidEdifactOffsetDateTime("202406151430UTC", "303") // true
+ * @example isValidEdifactOffsetDateTime("20240615143045-05", "304") // true
+ * @example isValidEdifactOffsetDateTime("202406151430CET", "303") // false (an abbreviation names no offset)
+ * @example isValidEdifactOffsetDateTime("202406151430", "205") // false (no offset)
+ */
+export function isValidEdifactOffsetDateTime(value, format) {
+    return parseEdifactOffsetDateTime(value, format) !== "";
+}

package/dist/intermodal/validate/isValidEdifactTime.d.ts

@@ -0,0 +1,28 @@
+import type { EdifactTimeFormat } from "../../types/edi.js";
+/**
+ * Return true when `value` is a UN/EDIFACT `DTM` value (data element 2380) that states a real
+ * time of day in a time format code (data element 2379).
+ *
+ * ### Format codes
+ * | Code | Mask | The directory's description |
+ * |---|---|---|
+ * | `401` | `HHMM` | "Time without seconds: H = Hour; m = Minute." |
+ * | `402` | `HHMMSS` | "Time with seconds: H = Hour; m = Minute; s = Seconds." |
+ *
+ * - True exactly when `parseEdifactTime` returns a time for the same arguments: the validator
+ *   calls the parser, so the two cannot disagree.
+ * - A value is valid only against its code: `"1430"` is a `401` value and not a `402` one.
+ * - Hour 24, minute 60 and second 60 are false.
+ * - False for any other code, a code of another kind included; check a code alone with
+ *   `isValidEdifactDtmFormat`. False for a non-string argument.
+ *
+ * @param value The data element 2380 value (e.g. "1430")
+ * @param format The data element 2379 format code
+ * @returns boolean indicating validity
+ *
+ * @example isValidEdifactTime("1430", "401") // true
+ * @example isValidEdifactTime("143045", "402") // true
+ * @example isValidEdifactTime("1430", "402") // false (four digits is a 401 value)
+ * @example isValidEdifactTime("2400", "401") // false (hour 24)
+ */
+export declare function isValidEdifactTime(value: string, format: EdifactTimeFormat): boolean;

package/dist/intermodal/validate/isValidEdifactTime.js

@@ -0,0 +1,30 @@
+import { parseEdifactTime } from "../parse/parseEdifactTime.js";
+/**
+ * Return true when `value` is a UN/EDIFACT `DTM` value (data element 2380) that states a real
+ * time of day in a time format code (data element 2379).
+ *
+ * ### Format codes
+ * | Code | Mask | The directory's description |
+ * |---|---|---|
+ * | `401` | `HHMM` | "Time without seconds: H = Hour; m = Minute." |
+ * | `402` | `HHMMSS` | "Time with seconds: H = Hour; m = Minute; s = Seconds." |
+ *
+ * - True exactly when `parseEdifactTime` returns a time for the same arguments: the validator
+ *   calls the parser, so the two cannot disagree.
+ * - A value is valid only against its code: `"1430"` is a `401` value and not a `402` one.
+ * - Hour 24, minute 60 and second 60 are false.
+ * - False for any other code, a code of another kind included; check a code alone with
+ *   `isValidEdifactDtmFormat`. False for a non-string argument.
+ *
+ * @param value The data element 2380 value (e.g. "1430")
+ * @param format The data element 2379 format code
+ * @returns boolean indicating validity
+ *
+ * @example isValidEdifactTime("1430", "401") // true
+ * @example isValidEdifactTime("143045", "402") // true
+ * @example isValidEdifactTime("1430", "402") // false (four digits is a 401 value)
+ * @example isValidEdifactTime("2400", "401") // false (hour 24)
+ */
+export function isValidEdifactTime(value, format) {
+    return parseEdifactTime(value, format) !== "";
+}

package/dist/intermodal/validate/isValidEpcisEvent.d.ts

@@ -0,0 +1,41 @@
+/**
+ * Validate whether a value carries the two required time fields of a GS1 EPCIS 2.0 event, each in
+ * the grammar GS1 publishes for it.
+ *
+ * EPCIS (ISO/IEC 19987) is GS1's event standard for supply-chain visibility. True exactly when
+ * `isValidEpcisEventTime` is true of `eventTime` and `isValidEpcisTimeZoneOffset` is true of
+ * `eventTimeZoneOffset`: this validator calls the two, and no check needs both fields at once.
+ * `parseEpcisEvent` returns a result for exactly the same values.
+ *
+ * - `eventTime` must match `epcisEventTime` (the `DateTimeStamp` pattern of the EPCIS XSD, the
+ *   XML binding; the JSON schema says only `format: date-time`) and name a real instant: `YYYY-MM-DDTHH:MM:SS`, an optional fraction of up to nine digits, then
+ *   `Z` or a `±HH:MM` offset. A day the month does not have (`2024-02-30`) is false, although the
+ *   pattern matches it.
+ * - `eventTimeZoneOffset` must match `epcisTimeZoneOffset` (the pattern the EPCIS JSON schema
+ *   gives; the XSD types the field as a bare `xsd:string`): `±HH:MM` from `-14:00` to `+14:00`,
+ *   the rule of EPCIS Standard Release 2.0 §7.4.1 (https://ref.gs1.org/standards/epcis/). A
+ *   missing offset, `Z`, `+0200` and `+02` are false.
+ * - The two fields are independent: an `eventTime` written with one offset and an
+ *   `eventTimeZoneOffset` that is another is valid. EPCIS 2.0 §7.4.1.1 (non-normative): "there
+ *   is no requirement that the time zone specifier in the XML representation of eventTime be the
+ *   local time zone offset where the event was captured".
+ * - **GMT rule:** a fraction longer than nine digits is false. The XSD allows any length; an
+ *   instant holds nanoseconds, and `parseEpcisEvent` does not drop digits.
+ * - Only the two fields are checked. `recordTime` and every other member are ignored, so this
+ *   does not validate a whole event against the EPCIS schema.
+ * - Returns false for a value that is not an object.
+ *
+ * @param event candidate EPCIS event, or any object with `eventTime` and `eventTimeZoneOffset`
+ * @returns boolean indicating whether `parseEpcisEvent` reads the event, or false on invalid input
+ *
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30:00Z", eventTimeZoneOffset: "-05:00" }) // true
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T10:00:00+02:00", eventTimeZoneOffset: "-05:00" }) // true (the two offsets need not agree)
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30:00.123456789Z", eventTimeZoneOffset: "+14:00" }) // true
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30:00Z" }) // false (eventTimeZoneOffset is required)
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30:00Z", eventTimeZoneOffset: "Z" }) // false (a designator, not an offset)
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30:00Z", eventTimeZoneOffset: "+0200" }) // false (no colon)
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30Z", eventTimeZoneOffset: "-05:00" }) // false (seconds are required)
+ * @example isValidEpcisEvent({ eventTime: "2024-02-30T14:30:00Z", eventTimeZoneOffset: "-05:00" }) // false (30 February)
+ * @example isValidEpcisEvent("2024-06-15T14:30:00Z") // false (not an event)
+ */
+export declare function isValidEpcisEvent(event: unknown): boolean;

package/dist/intermodal/validate/isValidEpcisEvent.js

@@ -0,0 +1,58 @@
+import { isObject } from "../../internal/index.js";
+import { isValidEpcisEventTime } from "./isValidEpcisEventTime.js";
+import { isValidEpcisTimeZoneOffset } from "./isValidEpcisTimeZoneOffset.js";
+/**
+ * Validate whether a value carries the two required time fields of a GS1 EPCIS 2.0 event, each in
+ * the grammar GS1 publishes for it.
+ *
+ * EPCIS (ISO/IEC 19987) is GS1's event standard for supply-chain visibility. True exactly when
+ * `isValidEpcisEventTime` is true of `eventTime` and `isValidEpcisTimeZoneOffset` is true of
+ * `eventTimeZoneOffset`: this validator calls the two, and no check needs both fields at once.
+ * `parseEpcisEvent` returns a result for exactly the same values.
+ *
+ * - `eventTime` must match `epcisEventTime` (the `DateTimeStamp` pattern of the EPCIS XSD, the
+ *   XML binding; the JSON schema says only `format: date-time`) and name a real instant: `YYYY-MM-DDTHH:MM:SS`, an optional fraction of up to nine digits, then
+ *   `Z` or a `±HH:MM` offset. A day the month does not have (`2024-02-30`) is false, although the
+ *   pattern matches it.
+ * - `eventTimeZoneOffset` must match `epcisTimeZoneOffset` (the pattern the EPCIS JSON schema
+ *   gives; the XSD types the field as a bare `xsd:string`): `±HH:MM` from `-14:00` to `+14:00`,
+ *   the rule of EPCIS Standard Release 2.0 §7.4.1 (https://ref.gs1.org/standards/epcis/). A
+ *   missing offset, `Z`, `+0200` and `+02` are false.
+ * - The two fields are independent: an `eventTime` written with one offset and an
+ *   `eventTimeZoneOffset` that is another is valid. EPCIS 2.0 §7.4.1.1 (non-normative): "there
+ *   is no requirement that the time zone specifier in the XML representation of eventTime be the
+ *   local time zone offset where the event was captured".
+ * - **GMT rule:** a fraction longer than nine digits is false. The XSD allows any length; an
+ *   instant holds nanoseconds, and `parseEpcisEvent` does not drop digits.
+ * - Only the two fields are checked. `recordTime` and every other member are ignored, so this
+ *   does not validate a whole event against the EPCIS schema.
+ * - Returns false for a value that is not an object.
+ *
+ * @param event candidate EPCIS event, or any object with `eventTime` and `eventTimeZoneOffset`
+ * @returns boolean indicating whether `parseEpcisEvent` reads the event, or false on invalid input
+ *
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30:00Z", eventTimeZoneOffset: "-05:00" }) // true
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T10:00:00+02:00", eventTimeZoneOffset: "-05:00" }) // true (the two offsets need not agree)
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30:00.123456789Z", eventTimeZoneOffset: "+14:00" }) // true
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30:00Z" }) // false (eventTimeZoneOffset is required)
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30:00Z", eventTimeZoneOffset: "Z" }) // false (a designator, not an offset)
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30:00Z", eventTimeZoneOffset: "+0200" }) // false (no colon)
+ * @example isValidEpcisEvent({ eventTime: "2024-06-15T14:30Z", eventTimeZoneOffset: "-05:00" }) // false (seconds are required)
+ * @example isValidEpcisEvent({ eventTime: "2024-02-30T14:30:00Z", eventTimeZoneOffset: "-05:00" }) // false (30 February)
+ * @example isValidEpcisEvent("2024-06-15T14:30:00Z") // false (not an event)
+ */
+export function isValidEpcisEvent(event) {
+    try {
+        if (!isObject(event)) {
+            return false;
+        }
+        // Each field is read once, in the order `parseEpcisEvent` reads them.
+        const { eventTime, eventTimeZoneOffset } = event;
+        return (isValidEpcisEventTime(eventTime) &&
+            isValidEpcisTimeZoneOffset(eventTimeZoneOffset));
+    }
+    catch {
+        // Never throws (Core Rule 3): a hostile argument is invalid input, not an exception.
+        return false;
+    }
+}

package/dist/intermodal/validate/isValidEpcisEventTime.d.ts

@@ -0,0 +1,33 @@
+/**
+ * Return true when `value` is a real GS1 EPCIS 2.0 `eventTime`: the moment a supply-chain event
+ * happened, written as a date and time with `Z` or a UTC offset.
+ *
+ * EPCIS (ISO/IEC 19987) is GS1's event standard for supply-chain visibility. This is the check
+ * `isValidEpcisEvent` applies to the event's `eventTime` field: that validator calls this one.
+ *
+ * - The value must match `epcisEventTime`, the `DateTimeStamp` pattern of the EPCIS XSD:
+ *   `YYYY-MM-DDTHH:MM:SS`, an optional fraction, then `Z` or a `±HH:MM` offset up to `14:00`.
+ *   Seconds are required, `T` and `Z` are upper-case, and nothing may follow.
+ * - Checks the calendar as well as the shape. The pattern proves the shape alone, so it matches
+ *   a day the month does not have: `2024-02-30` and `2023-02-29` are false here.
+ * - **GMT rule:** a fraction longer than nine digits is false, although the pattern matches a
+ *   fraction of any length. An instant holds nanoseconds, and `parseEpcisEvent` does not drop
+ *   digits.
+ * - False for a leap second (`:60`), a space separator, an expanded year and a bracketed zone,
+ *   none of which the pattern matches.
+ * - An event also needs an `eventTimeZoneOffset`: check it with `isValidEpcisTimeZoneOffset`, or
+ *   both fields with `isValidEpcisEvent`. Read an event with `parseEpcisEvent`.
+ * - False for a non-string.
+ *
+ * @param value candidate EPCIS `eventTime` string
+ * @returns boolean indicating validity
+ *
+ * @example isValidEpcisEventTime("2024-06-15T14:30:00Z") // true
+ * @example isValidEpcisEventTime("2024-06-15T10:00:00.123+02:00") // true
+ * @example isValidEpcisEventTime("2024-02-30T14:30:00Z") // false (30 February; the epcisEventTime pattern matches it)
+ * @example isValidEpcisEventTime("2023-02-29T00:00:00Z") // false (2023 has no 29 February; the epcisEventTime pattern matches it)
+ * @example isValidEpcisEventTime("2024-06-15T14:30:00.1234567891Z") // false (finer than a nanosecond; the epcisEventTime pattern matches it)
+ * @example isValidEpcisEventTime("2024-06-15T14:30Z") // false (seconds are required)
+ * @example isValidEpcisEventTime("2024-06-15T14:30:00") // false (Z or an offset is required)
+ */
+export declare function isValidEpcisEventTime(value: string): boolean;

package/dist/intermodal/validate/isValidEpcisEventTime.js

@@ -0,0 +1,48 @@
+import { Temporal } from "../../internal/temporal.js";
+import { epcisEventTime } from "../../regex/index.js";
+/**
+ * Return true when `value` is a real GS1 EPCIS 2.0 `eventTime`: the moment a supply-chain event
+ * happened, written as a date and time with `Z` or a UTC offset.
+ *
+ * EPCIS (ISO/IEC 19987) is GS1's event standard for supply-chain visibility. This is the check
+ * `isValidEpcisEvent` applies to the event's `eventTime` field: that validator calls this one.
+ *
+ * - The value must match `epcisEventTime`, the `DateTimeStamp` pattern of the EPCIS XSD:
+ *   `YYYY-MM-DDTHH:MM:SS`, an optional fraction, then `Z` or a `±HH:MM` offset up to `14:00`.
+ *   Seconds are required, `T` and `Z` are upper-case, and nothing may follow.
+ * - Checks the calendar as well as the shape. The pattern proves the shape alone, so it matches
+ *   a day the month does not have: `2024-02-30` and `2023-02-29` are false here.
+ * - **GMT rule:** a fraction longer than nine digits is false, although the pattern matches a
+ *   fraction of any length. An instant holds nanoseconds, and `parseEpcisEvent` does not drop
+ *   digits.
+ * - False for a leap second (`:60`), a space separator, an expanded year and a bracketed zone,
+ *   none of which the pattern matches.
+ * - An event also needs an `eventTimeZoneOffset`: check it with `isValidEpcisTimeZoneOffset`, or
+ *   both fields with `isValidEpcisEvent`. Read an event with `parseEpcisEvent`.
+ * - False for a non-string.
+ *
+ * @param value candidate EPCIS `eventTime` string
+ * @returns boolean indicating validity
+ *
+ * @example isValidEpcisEventTime("2024-06-15T14:30:00Z") // true
+ * @example isValidEpcisEventTime("2024-06-15T10:00:00.123+02:00") // true
+ * @example isValidEpcisEventTime("2024-02-30T14:30:00Z") // false (30 February; the epcisEventTime pattern matches it)
+ * @example isValidEpcisEventTime("2023-02-29T00:00:00Z") // false (2023 has no 29 February; the epcisEventTime pattern matches it)
+ * @example isValidEpcisEventTime("2024-06-15T14:30:00.1234567891Z") // false (finer than a nanosecond; the epcisEventTime pattern matches it)
+ * @example isValidEpcisEventTime("2024-06-15T14:30Z") // false (seconds are required)
+ * @example isValidEpcisEventTime("2024-06-15T14:30:00") // false (Z or an offset is required)
+ */
+export function isValidEpcisEventTime(value) {
+    if (typeof value !== "string" || !epcisEventTime.test(value)) {
+        return false;
+    }
+    try {
+        // The two checks the pattern cannot make: a day the month does not have, and a fraction past
+        // nine digits (Temporal's grammar stops at nanoseconds). Both are a RangeError.
+        Temporal.Instant.from(value);
+        return true;
+    }
+    catch {
+        return false;
+    }
+}

package/dist/intermodal/validate/isValidEpcisTimeZoneOffset.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Return true when `value` is a GS1 EPCIS 2.0 `eventTimeZoneOffset`: the UTC offset the local
+ * clock ran at where a supply-chain event happened, written `±HH:MM`.
+ *
+ * EPCIS (ISO/IEC 19987) is GS1's event standard for supply-chain visibility. This is the check
+ * `isValidEpcisEvent` applies to the event's `eventTimeZoneOffset` field: that validator calls
+ * this one.
+ *
+ * - The value must match `epcisTimeZoneOffset`, the pattern the EPCIS JSON schema gives: `±HH:MM`
+ *   from `-14:00` to `+14:00`, the rule of EPCIS Standard Release 2.0 §7.4.1
+ *   (https://ref.gs1.org/standards/epcis/).
+ * - **The pattern is the whole rule for a string.** Every value it matches is an offset Temporal
+ *   reads, so this validator and `epcisTimeZoneOffset.test` agree on every string; the validator
+ *   adds only the answer false for a non-string.
+ * - `Z`, `+0200`, `+02`, an offset with seconds and an offset past `14:00` are false.
+ * - `-00:00` is true: the GS1 pattern matches it. `parseEpcisEvent` returns it as `+00:00`.
+ * - It need not agree with an offset written in the event's `eventTime`. Check that field with
+ *   `isValidEpcisEventTime`, or both with `isValidEpcisEvent`.
+ *
+ * @param value candidate EPCIS `eventTimeZoneOffset` string
+ * @returns boolean indicating validity
+ *
+ * @example isValidEpcisTimeZoneOffset("-05:00") // true
+ * @example isValidEpcisTimeZoneOffset("+14:00") // true
+ * @example isValidEpcisTimeZoneOffset("+14:01") // false (past the range GS1 allows)
+ * @example isValidEpcisTimeZoneOffset("Z") // false (a designator, not an offset)
+ * @example isValidEpcisTimeZoneOffset("+0200") // false (no colon)
+ * @example isValidEpcisTimeZoneOffset("+05:30:00") // false (seconds)
+ */
+export declare function isValidEpcisTimeZoneOffset(value: string): boolean;

package/dist/intermodal/validate/isValidEpcisTimeZoneOffset.js

@@ -0,0 +1,38 @@
+import { parseUtcOffsetNanoseconds } from "../../internal/index.js";
+import { epcisTimeZoneOffset } from "../../regex/index.js";
+/**
+ * Return true when `value` is a GS1 EPCIS 2.0 `eventTimeZoneOffset`: the UTC offset the local
+ * clock ran at where a supply-chain event happened, written `±HH:MM`.
+ *
+ * EPCIS (ISO/IEC 19987) is GS1's event standard for supply-chain visibility. This is the check
+ * `isValidEpcisEvent` applies to the event's `eventTimeZoneOffset` field: that validator calls
+ * this one.
+ *
+ * - The value must match `epcisTimeZoneOffset`, the pattern the EPCIS JSON schema gives: `±HH:MM`
+ *   from `-14:00` to `+14:00`, the rule of EPCIS Standard Release 2.0 §7.4.1
+ *   (https://ref.gs1.org/standards/epcis/).
+ * - **The pattern is the whole rule for a string.** Every value it matches is an offset Temporal
+ *   reads, so this validator and `epcisTimeZoneOffset.test` agree on every string; the validator
+ *   adds only the answer false for a non-string.
+ * - `Z`, `+0200`, `+02`, an offset with seconds and an offset past `14:00` are false.
+ * - `-00:00` is true: the GS1 pattern matches it. `parseEpcisEvent` returns it as `+00:00`.
+ * - It need not agree with an offset written in the event's `eventTime`. Check that field with
+ *   `isValidEpcisEventTime`, or both with `isValidEpcisEvent`.
+ *
+ * @param value candidate EPCIS `eventTimeZoneOffset` string
+ * @returns boolean indicating validity
+ *
+ * @example isValidEpcisTimeZoneOffset("-05:00") // true
+ * @example isValidEpcisTimeZoneOffset("+14:00") // true
+ * @example isValidEpcisTimeZoneOffset("+14:01") // false (past the range GS1 allows)
+ * @example isValidEpcisTimeZoneOffset("Z") // false (a designator, not an offset)
+ * @example isValidEpcisTimeZoneOffset("+0200") // false (no colon)
+ * @example isValidEpcisTimeZoneOffset("+05:30:00") // false (seconds)
+ */
+export function isValidEpcisTimeZoneOffset(value) {
+    // `parseEpcisEvent` reads the offset through Temporal after the pattern, so this does too. No
+    // string the pattern matches fails that read: it is here so the two cannot drift.
+    return (typeof value === "string" &&
+        epcisTimeZoneOffset.test(value) &&
+        parseUtcOffsetNanoseconds(value) !== null);
+}

package/dist/intermodal/validate/isValidX12Date.d.ts

@@ -0,0 +1,28 @@
+import type { X12DateFormat } from "../../types/edi.js";
+/**
+ * Return true when `value` is an X12 Date Time Period value (data element 1251) that states a
+ * real calendar date in a date format qualifier (data element 1250).
+ *
+ * ### Format codes
+ * | Code | Mask | The dictionary's definition |
+ * |---|---|---|
+ * | `D8` | `CCYYMMDD` | "Date Expressed in Format CCYYMMDD" |
+ * | `DB` | `MMDDCCYY` | "Date Expressed in Format MMDDCCYY" |
+ *
+ * - True exactly when `parseX12Date` returns a date for the same arguments: the validator calls
+ *   the parser, so the two cannot disagree.
+ * - A value is valid only against its code: `"06152024"` is a `DB` value and not a `D8` one.
+ * - Checks the calendar as well as the shape: 31 June and 29 February 2023 are false.
+ * - False for any other code, a code of another kind included; check a code alone with
+ *   `isValidX12DateTimePeriodFormat`. False for a non-string argument.
+ *
+ * @param value The data element 1251 value (e.g. "20240615")
+ * @param format X12 data element 1250 format qualifier
+ * @returns boolean indicating validity
+ *
+ * @example isValidX12Date("20240615", "D8") // true
+ * @example isValidX12Date("06152024", "DB") // true
+ * @example isValidX12Date("06152024", "D8") // false (20 is not a month)
+ * @example isValidX12Date("20230229", "D8") // false (2023 has no 29 February)
+ */
+export declare function isValidX12Date(value: string, format: X12DateFormat): boolean;

package/dist/intermodal/validate/isValidX12Date.js

@@ -0,0 +1,30 @@
+import { parseX12Date } from "../parse/parseX12Date.js";
+/**
+ * Return true when `value` is an X12 Date Time Period value (data element 1251) that states a
+ * real calendar date in a date format qualifier (data element 1250).
+ *
+ * ### Format codes
+ * | Code | Mask | The dictionary's definition |
+ * |---|---|---|
+ * | `D8` | `CCYYMMDD` | "Date Expressed in Format CCYYMMDD" |
+ * | `DB` | `MMDDCCYY` | "Date Expressed in Format MMDDCCYY" |
+ *
+ * - True exactly when `parseX12Date` returns a date for the same arguments: the validator calls
+ *   the parser, so the two cannot disagree.
+ * - A value is valid only against its code: `"06152024"` is a `DB` value and not a `D8` one.
+ * - Checks the calendar as well as the shape: 31 June and 29 February 2023 are false.
+ * - False for any other code, a code of another kind included; check a code alone with
+ *   `isValidX12DateTimePeriodFormat`. False for a non-string argument.
+ *
+ * @param value The data element 1251 value (e.g. "20240615")
+ * @param format X12 data element 1250 format qualifier
+ * @returns boolean indicating validity
+ *
+ * @example isValidX12Date("20240615", "D8") // true
+ * @example isValidX12Date("06152024", "DB") // true
+ * @example isValidX12Date("06152024", "D8") // false (20 is not a month)
+ * @example isValidX12Date("20230229", "D8") // false (2023 has no 29 February)
+ */
+export function isValidX12Date(value, format) {
+    return parseX12Date(value, format) !== "";
+}

package/dist/intermodal/validate/isValidX12DateAndTime.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Return true when the date and the time of an X12 segment, sent as two elements, together
+ * state a real local date and time.
+ *
+ * ### The two elements
+ * | Element | Name | The dictionary's definition |
+ * |---|---|---|
+ * | [373](https://www.stedi.com/edi/x12-005010/element/373) | Date | "Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year" |
+ * | [337](https://www.stedi.com/edi/x12-005010/element/337) | Time | "Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD" |
+ *
+ * - True exactly when `parseX12DateAndTime` returns a date-time for the same arguments: the
+ *   validator calls the parser, so the two cannot disagree.
+ * - **Both elements are required.** A missing or empty date or time is false: check a date alone
+ *   with `isValidX12Date(value, "D8")` and a time alone with `isValidX12Time`.
+ * - Checks the calendar as well as the shape: 29 February 2023, 31 June, hour 24 and minute or
+ *   second 60 are false.
+ * - The date has a four-digit year and the time is 4, 6, 7 or 8 digits: a date of six digits and
+ *   a time of 5 or 9 digits are false.
+ * - False for a non-string argument.
+ *
+ * @param date The data element 373 date as transmitted, `CCYYMMDD` (e.g. "20240615")
+ * @param time The data element 337 time as transmitted (e.g. "1430")
+ * @returns boolean indicating validity
+ *
+ * @example isValidX12DateAndTime("20240615", "1430") // true
+ * @example isValidX12DateAndTime("20240615", "14300012") // true (hundredths of a second)
+ * @example isValidX12DateAndTime("20240615", "") // false (both elements are required)
+ * @example isValidX12DateAndTime("20230229", "1430") // false (2023 has no 29 February)
+ * @example isValidX12DateAndTime("20240615", "2430") // false (hour 24)
+ * @example isValidX12DateAndTime("240615", "1430") // false (the date element has a four-digit year)
+ */
+export declare function isValidX12DateAndTime(date: string, time: string): boolean;

package/dist/intermodal/validate/isValidX12DateAndTime.js

@@ -0,0 +1,35 @@
+import { parseX12DateAndTime } from "../parse/parseX12DateAndTime.js";
+/**
+ * Return true when the date and the time of an X12 segment, sent as two elements, together
+ * state a real local date and time.
+ *
+ * ### The two elements
+ * | Element | Name | The dictionary's definition |
+ * |---|---|---|
+ * | [373](https://www.stedi.com/edi/x12-005010/element/373) | Date | "Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year" |
+ * | [337](https://www.stedi.com/edi/x12-005010/element/337) | Time | "Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD" |
+ *
+ * - True exactly when `parseX12DateAndTime` returns a date-time for the same arguments: the
+ *   validator calls the parser, so the two cannot disagree.
+ * - **Both elements are required.** A missing or empty date or time is false: check a date alone
+ *   with `isValidX12Date(value, "D8")` and a time alone with `isValidX12Time`.
+ * - Checks the calendar as well as the shape: 29 February 2023, 31 June, hour 24 and minute or
+ *   second 60 are false.
+ * - The date has a four-digit year and the time is 4, 6, 7 or 8 digits: a date of six digits and
+ *   a time of 5 or 9 digits are false.
+ * - False for a non-string argument.
+ *
+ * @param date The data element 373 date as transmitted, `CCYYMMDD` (e.g. "20240615")
+ * @param time The data element 337 time as transmitted (e.g. "1430")
+ * @returns boolean indicating validity
+ *
+ * @example isValidX12DateAndTime("20240615", "1430") // true
+ * @example isValidX12DateAndTime("20240615", "14300012") // true (hundredths of a second)
+ * @example isValidX12DateAndTime("20240615", "") // false (both elements are required)
+ * @example isValidX12DateAndTime("20230229", "1430") // false (2023 has no 29 February)
+ * @example isValidX12DateAndTime("20240615", "2430") // false (hour 24)
+ * @example isValidX12DateAndTime("240615", "1430") // false (the date element has a four-digit year)
+ */
+export function isValidX12DateAndTime(date, time) {
+    return parseX12DateAndTime(date, time) !== "";
+}

package/dist/intermodal/validate/isValidX12DateRange.d.ts

@@ -0,0 +1,29 @@
+import type { X12DateRangeFormat } from "../../types/edi.js";
+/**
+ * Return true when `value` is an X12 Date Time Period value (data element 1251) that states a
+ * range between two real calendar dates, in a date range format qualifier (data element 1250).
+ *
+ * ### Format codes
+ * | Code | Mask | The dictionary's definition |
+ * |---|---|---|
+ * | `RD8` | `CCYYMMDD-CCYYMMDD` | "Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD" |
+ * | `RD` | `MMDDCCYY-MMDDCCYY` | "Range of Dates Expressed in Format MMDDCCYY-MMDDCCYY" |
+ *
+ * - True exactly when `parseX12DateRange` returns a range for the same arguments: the validator
+ *   calls the parser, so the two cannot disagree.
+ * - A range is valid with exactly one hyphen: `"2024061520240620"` is false.
+ * - A range whose end precedes its start is false; an end equal to its start is true.
+ * - Checks the calendar as well as the shape: 29 February 2023 in either date is false.
+ * - False for any other code, a code of another kind included; check a code alone with
+ *   `isValidX12DateTimePeriodFormat`. False for a non-string argument.
+ *
+ * @param value The data element 1251 value (e.g. "20240615-20240620")
+ * @param format X12 data element 1250 format qualifier
+ * @returns boolean indicating validity
+ *
+ * @example isValidX12DateRange("20240615-20240620", "RD8") // true
+ * @example isValidX12DateRange("06152024-06202024", "RD") // true
+ * @example isValidX12DateRange("2024061520240620", "RD8") // false (a range is transmitted with its hyphen)
+ * @example isValidX12DateRange("20240620-20240615", "RD8") // false (the end precedes the start)
+ */
+export declare function isValidX12DateRange(value: string, format: X12DateRangeFormat): boolean;