main schema e-service developers Freeflow Project. UTMC XML working Group. See main package headers United Kingdom Drafted for version 1.0 FREEFLOW. Nick Knowles Kizoom mailto:schemer@/www.utmc.uk.com/ 2009-04-01 2009-05-09

UtmcXml is an XML representation of the Urban Traffic Management Control model that can be used to exchange data objects between UTMC databases and other services.

.

This subschema describes the Freeflow Alert Data Object (Freeflow). An Alert object sends information from an Intelligent Decision Support Subsystem to a UTMC database on order to inform a network operator or other agent.

It is based on the UTMC Traffic Event Object, and may include one or more update elements, each containing:

  • The default attributes for an alert (identification, description, location) are covered by the generic data attributes.
  • Information about the triggering objects
  • Information about the affected objects

A Traffic Event comprises one or more Traffic Event Elements, representing updates to the Traffic event. Any values specified on each subsequent Traffic event. element supercede the previous values Element Instances can be kept for audit purposes

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.utmc.uk.com/schemas/1.0/utmc/}utmc_traffic_event_alert-v1.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.utmc.uk.com/schemas/1.0/utmc/utmc_traffic_event-v1.0.xsd http://www.utmc.uk.com/schemas/1.0/utmc/utmc_data_object_intervention-v1.0.xsd http://www.utmc.uk.com/schemas/1.0/utmc/utmc_all_objects-v1.0.xsd http://www.siri.org.uk/schemas/1.3/siri/siri_situationActions-v1.0.xsd Unclassified Freeflow, UTMC 2009

Derived from the UTMC specification and SIRI standards.

  • UTMC Data Object specification: ts004.003annexdapr07.xls
  • UTMC UML specification: ts004-004a-annexd-sep08.pdf -

Version 1.0 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Public transport, Bus services, Coach services, Bus stops and stations, Business and industry, Transport, Roads and road transport Freeflow UtmcXml Interface UTMC XML schema. Subschema describing a Freeflow Alert Traffic Event. Standard Type for Identifier for Alert. Simple reference to a Alert. Unique within system and type. Freeflow Extension. Type for full reference to a Alert . Freeflow Extension. Alert Data Object. Freeflow Extension. An Alert object sends information from an Intelligent Decision Support Subsystem to UTMC database on order to inform a network operator or other agent. Unique Identifier of a system providing data. If absent, given by context. Participant identifiers should be chosen to be unique across all systems so that together with SystemCodeNumber there is a unique reference to each UTMC data object. Identifier of data object, unique within system and type. Identifier of object on originating system. Unique within originating system and object type. Type for Freeflow Alert. Elements specific to Alert. Updates to base Alert. Alert Dynamic Values. Freeflow extension. Identifier of Data Object. Unique within System and type. Only needs to be specified if not given by context. Type of Data Object. Quality statement of Data Object. UTMC Object textual description elements. Type for Alert Element. Elements specific to Base Alert Further comment Time that Alert is intended to apply Elements specific to Alert Element. Elements specific to Alert Element relating to classifcationof alert. Numeric ranking of relative priority of alert 0-100. Assessment of impact of alert. Reference to a Type of Verification Status. Impact Severity - Scale of zero low to 9 high Type for assessment of Impact. Lower Bound for severity assessment. Inclusive. Scale of Zero (none) to 9 (highest) Lower Bound for severity assessment. Inclusive. Scale of Zero (none) to 9 (highest) Elements specific to Alert Element relating to effect of alert. Identifier of data objects affected by Alert. e.g. For VMS can indicate VMS to use. Reference Object affected by alert, annotated with effect. Interventions to which alert relates. Predictions relating to alert Elements specific to Alert Element relating to cause of alert. Identifier of one or more data objects that triggered the alert. Object affecte dby alert. Elements specific to Alert Element relating to description content of alert. Content that can be used to create an incident or other notrice associated with Alert. Publishing Actions recommended for alert. Type for content summary. Human readable name traffic .for event UTMC Object textual description elements. Affected Object List Entry Freeflow Extension. Unique Identifier of a system providing data. If absent, given by context. Participant identifiers should be chosen to be unique across all systems so that together with SystemCodeNumber there is a unique reference to each UTMC data object. Reference to Data Object. Unique within Participant system and type. Onlyneeds to be specified if not given by Context Type for affected Object. Associatesa refernce withan effect type. Affected Object list elements. Reference to an external object. Can be used to identify arbitrary objects eg bus stop Naptan id. Nature of effect on object. eg. Jump to CCTV camera, congestion on link on route, etc, show on VMs etc Brief description of effect. Alert Intervention List Entry. Freeflow Extension. Type for Alert Intervention List Entry. Alert Intervention list Entry elements. Alert Prediction List Entry. Freeflow Extension. Unique Identifier of a system providing data. If absent, given by context. Participant identifiers should be chosen to be unique across all systems so that together with SystemCodeNumber there is a unique reference to each UTMC data object. Reference to Data Object. Unique within Participant system and type. Onlyneeds to be specified if not given by Context Type for Alert Prediction List Entry. Alert Prediction List Entry elements. Alert Publishing Action List Entry. Freeflow Extension. Unique Identifier of a system providing data. If absent, given by context. Participant identifiers should be chosen to be unique across all systems so that together with SystemCodeNumber there is a unique reference to each UTMC data object. Reference to Data Object. Unique within Participant system and type. Onlyneeds to be specified if not given by Context Type forAlert Publishing Action List Entry. Alert Publishing Action List Entry elements. Records Operator response to action Alert Publishing Action List Entry elements. Time presented to operator Whether operator accepted alrt intervention. Refernce to an Intervention Evaluation associated with Alert Alert Data Object Static Data. Freeflow Extension. Static Elements specific to Alert. Freeflow extension. Types of Alert. Quality Statements. Alert Quality Statements Type definition Elements specific to Alert. Verification Status Type Definition. Identifier for Object Type definition. Reference to a Type of Alert. Freeflow Extension. Identifier of Alert Type Definition. Enumeration of allowed Alert Types Alert Type Definition. Freeflow extension. Identifier for Object Type definition. Reference to a Type of Verification Status. Freeflow Extension.Used on ALert. 1 = Unknown, 2 = Unverified, 3 = Verified as duplicate, 4 = Verified. Type for Identifier of Verification Status Definition. Values for Verification Status Corresponds to TPEG pti_table 32. Verification Status Type Definition. Used in Alert. Freeflow extension. 1 = Unknown, 2 = Unverified, 3 = Verified as duplicate, 4 = Verified. Identifier for Object Type definition. Reference to a Type of Effect. Freeflow Extension. Type for Identifier of Alert Effect Type Definition. Alert Effect Type Definition. Used in Alert. Freeflow extension. Identifier for Object Type definition. Type for Identifier of Alert Quality. Alert Quality. Freeflow Extension. identifier of quality Statement. Unique within object type and system.