Description
Resolve one exact supplied language token against a caller-provided channel map.
Travel records use explicit dates, time axes, offsets, operating-day boundaries, durations, and capacity assumptions. A scheduling or validity term is meaningful only under those conventions. Actual operator rules, bookings, local conditions, and availability require separate information.
Resolve one exact supplied language token against a caller-provided channel map.
When to use this tool
Use Audio Guide Language Channel Token when you need the stated date, clock, scheduling, language, or capacity check from already supplied travel records.
How to use the tool and how it works
- Enter requestedLanguage, channelLanguages, channelIds. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read found, channelId. Inspect found before interpreting the associated values.
Look up requestedLanguage exactly in distinct channelLanguages aligned with channelIds. Return found and the corresponding channel ID, or empty ID when absent.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| requestedLanguage | Requested Language | Required. Text; maximum UTF-16 length 8192. |
| channelLanguages | Channel Languages | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| channelIds | Channel Ids | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| found | Whether an exact language match was found; a found channel ID can itself be empty. | Required. Boolean. |
| channelId | Channel Id | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"requestedLanguage": "fr",
"channelLanguages": [
"en",
"fr"
],
"channelIds": [
"1",
"2"
]
},
"output": {
"found": true,
"channelId": "2"
}
}Limitations and assumptions
- A found channel may itself have an empty ID, so inspect found. No language normalization, channel availability, translation quality, or device access is verified.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.
Alternative or Complementary methods
Use the actual schedule, calendar, booking record, and operator conditions for a real travel decision. Keep numeric clock conventions explicit when comparing this term with another method.
References
Similar or alternative tools
- Attraction Slot Buffer Share
Return usableDuration=slotDuration-bufferDuration and bufferShare=bufferDuration/slotDuration.
- Attraction Ticket Validity Overlap Days
Intersect supplied half-open absolute-day trip and ticket windows without inferring ticket terms.