junction
Enable an agent to recognise a traffic junction, record the routes, directions or modes it connects, assess its usability, and determine which movements and interactions are permitted.
Bundle → Layer → Finding → Questions Filled
5 bundles · 9 layers · 14 findings · 23 questions
Junction identity and extent Establish the intended physical sense of junction and delimit its connection region.
Physical sense
Identify what meeting or connection makes this thing a junction.
Qualifying connection
Record the domain-specific criterion by which the meeting elements constitute a junction.
- What physical connection does 'junction' denote in the registry's originating record? definition
- What evidence distinguishes this connection from mere proximity or an unconnected crossing? boundary
Connection region
Locate the junction's limits relative to incident elements and neighbouring junctions.
Junction boundary
Record an explicit boundary convention for the physical meeting region.
- Where does each incident element end for the purposes of this model and the junction region begin? boundary
- Does the evidence describe one compound junction or several separately identifiable junctions? boundary
Interfaces and topology Represent the elements entering the junction and the connections established among them.
Incident interfaces
Identify each attachment, entry, exit, or terminal under the relevant domain convention.
Interface inventory
Record incident elements with stable local interface identifiers and a stated counting basis.
- Which physical elements meet here, and through which identifiable interfaces? definition
- How many interfaces are present when counted by the chosen convention, such as road arms, pipe openings, or electrical terminals? measurement
Connection map
Describe direct connections, separations, and directional relationships between interfaces.
Pairwise connectivity
Represent which interface pairs or groups are connected without assuming universal connectivity.
- Which interfaces connect directly, and which remain separated within the junction region? definition
- Which connections are directional or depend on a selectable configuration? definition
Coupling and transfer Describe what the junction transmits or accommodates and the physical conditions required.
Connection mechanism
Identify how continuity or attachment is physically established.
Coupling basis
Record the applicable connection mechanism and the interface properties it requires.
- What passes through or is transmitted across this junction, or what attachment does it establish? definition
- Which geometric, material, or contact properties are necessary for the incident interfaces to connect as intended? measurement
Transfer envelope
Record domain-specific limits on usable connection performance.
Junction limits
Associate each verified limit with its connection, conditions, and evidence.
- Which measurable limits constrain use here, such as clearance, current, pressure, or transmitted load, and in what units? measurement
- Which drawing, test, specification, or observation supports each limit and its applicability to this junction? provenance
Connection state and intervention Assess current connection availability and the conditions for using or changing it.
Connection condition
Record evidence of continuity, interruption, and deterioration at individual connections.
Usable connection state
Distinguish observed physical condition from assumed availability.
- Which connections are currently established, interrupted, restricted, or unverified, and when was that state observed? measurement
- Which observed defects or obstructions affect passage, conduction, sealing, or load transfer in the applicable domain? measurement
Junction actions
Relate proposed use or modification to permissions, configuration, and effects on connected elements.
Action prerequisites
Record what must be established before an agent uses, isolates, switches, disconnects, or modifies a connection.
- Which proposed interactions are permitted, by whose authority, and under which connection states? action
- Before changing this junction, which incident elements require isolation, support, diversion, or other domain-specific preparation? action
- What verification is required before an altered connection can return to use? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of junction this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these kinds and varieties hold for the sense of junction this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of junction this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these failure modes and hazards hold for the sense of junction this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these regional variation hold for the sense of junction this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of junction this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Physical world and living systems
- Entry kind
- thing
- Plane
- PHY
- Domain
- PHY.BLT
- Other names and narrower kinds
- three-way interchange, motorway forks, Toeristisch Overstappunt, motorway junction, canal junction
What it is Filled
A junction is a location where traffic can change between different routes, directions, or sometimes modes of travel.
In scope
- The physical area where traffic routes connect or travel directions or modes can change.
- Connected routes, access points and local transport topology.
- Permitted movements and transfers between routes, directions or modes.
- Local traffic controls, separation arrangements and operating states.
- Condition and constraints that affect the junction's usability.
Out of scope
- The full transport networks containing the junction.
- The complete roads, tracks, paths or waterways connected by the junction.
- Vehicles and travellers considered independently of their interaction with the junction.
- Abstract graph vertices without a physical transport referent.
- Electrical connections, pipe joints and structural joints.
- Network-wide scheduling, optimisation and operating policy.
Why it exists Filled
Enable an agent to recognise a traffic junction, record the routes, directions or modes it connects, assess its usability, and determine which movements and interactions are permitted.
Distinguishing features Filled
- Identify a bounded location where traffic can change routes, directions or modes; proximity alone does not establish a junction.
- Establish an actual transport connection; a crossing with no possible movement between the crossing routes is not a junction between them.
- Distinguish the junction area from equipment that merely supports, controls or labels it.
- Record the available movements and whether they involve merging, branching, turning or changing modes.
- Distinguish a junction instance from a junction design or diagram symbol.
What robots and AI may and may not do Filled
Must not
- Switch, close or modify a junction it is not authorized to operate.
- Disregard traffic controls, access restrictions or the priority of other users.
- Report a junction as usable when its condition or limits are unknown.
- Leave a junction cover or barrier open where people can be hurt.
Only with a human decision
- Closing a junction or changing traffic routing in ways that affect other users.
May
- Record the routes, directions or modes connected at a junction and their operating state.
- Report damage, blockage or faults at a junction to its operator.
Moral aspects Filled
- Junctions are where conflicts and failures concentrate, putting users and workers at risk.
- Closing a junction can cut off access to essential destinations and services.
Who is affected
- Affected parties include travellers across the connected transport modes and pedestrians.
- Affected parties include workers maintaining transport networks.
- Affected parties include communities relying on access through the junction.
Owners Filled
Steward
The owner or operator of the network the junction belongs to.
Master systems
- Network asset registers of the operator
Links to other meta-models Filled
parent
- Q2221906 - registry parent class
- Q83620 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.junction
- Wikidata: Q1777515 (https://www.wikidata.org/wiki/Q1777515)
Direct properties required Filled
- Junction sense: transport | electrical | fluid | mechanical | other specified | unresolved
- Incident elements: References to connected physical elements, with locally identified interfaces
- Interface count: Count of interfaces under an explicitly stated counting convention
- Connection topology: Interface pairs or groups that are physically connected, including direction where applicable
- Transfer or coupling mode: movement | fluid passage | electrical conduction | force transmission | other specified
- Physical extent: Domain-appropriate dimensions in m or mm, or a spatial boundary with coordinate reference
- Connection state: Per connection: established | interrupted | restricted | unknown; domain-specific substates where supported
- Operating limits: Domain-specific limits with units, applicability conditions, and evidence; unknown where unverified
- Permitted interactions: Allowed interface-to-interface actions with conditions and governing authority
Recognition required Filled
- Connected roads, tracks, paths or waterways may provide visible opportunities to merge, turn or change routes.
- Signs, signals, markings or transfer facilities may identify permitted movements and connections.
- A visible crossing alone does not establish that traffic can transfer between its routes.
Capabilities and actions required Filled
- Identify which incident elements connect at the junction.
- Trace a proposed passage or transfer through its interfaces.
- Check whether a crossing constitutes a connection or remains separated.
- Assess whether a connection is usable under recorded conditions and limits.
- Determine prerequisites and authority for traversing, isolating, switching, or modifying the junction where applicable.
Hazards and failure modes required Filled
- Collisions can occur where traffic routes cross or merge.
- Conflicting movements or misunderstood controls can endanger travellers and workers.
- Blockage or closure can interrupt access and delay emergency services.
- Inaccessible or unclear transfer arrangements can exclude travellers or expose them to danger.
Standards and interfaces required Filled
- Vienna Convention on Road Signs and Signals, United Nations, for signing road junctions.
- IEC 60364 Low-voltage electrical installations, International Electrotechnical Commission.
Context of use required Filled
- A transport junction occurs where roads, railway lines or other travel routes meet and permit movement between connected routes.
- It supports route selection, turning, merging or transfers between transport modes where suitable facilities exist.
- Navigation and transport planning use junction information to describe connectivity, permitted movements and traffic control.
Sources Filled
- Wikidata item Q1777515: junction - identity and sense of the item
- Wikipedia: Junction (traffic) - general description of the item
Open questions
- Does the originating registry record intend a road or railway junction, an electrical or semiconductor junction, a mechanical connection, or another physical sense?
- Does an existing Vercy world model already own the intended concept, requiring this registry entry to link to it?
- For the intended sense, can a two-element connection qualify, and what distinguishes a junction from a joint, connector, crossing, or intersection?
- What authoritative convention determines the boundary of one junction and the counting of its interfaces?
- Which domain-specific sources establish applicable operating limits, condition criteria, and intervention requirements?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q1777515/spec.json