Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
main schemae-service developersWaldemar Isajkin (INIT GmbH)Europe>Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:[email protected]2004-09-292004-10-012007-05-142008-07-05
- correct data tupe to be particpant ref not participant pair
- add missing scopeType to classifier
2011-04-18
- AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org
2012-03-23
+SIRI v2.0
Use revised 2.0 definitions
Update to use DATEXII V 2.0 schema
Namespace changed from http://datex2.eu/schema/1_0/1_0 to http://datex2.eu/schema/2_0RC1/2_0
- D2LogicalModel:ReferencePointLinear has been renamed to D2LogicalModel:ReferencePointLinear
- DelayCodeENum renamed to DelayBandEnum
- InformationUsageOverride / D2LogicalModel:InformationUsage dropped for D2
- D2LogicalModel:SourceInformation renamed to D2LogicalModel:Source
- D2LogicalModel:SourceInformation values wrapped in valuse tag
- D2LogicalModel:Advcie dropped.
- D2LogicalModel:Imppact ImpactDetails wrapper tag dropped.
- D2 trafficResstrictionType renamed to trafficConstrictionType
Correct type on easementref to normalized string.
Allow transalatiobs of NLString elements
2013-02-11
Correction: Certain elements of DescriptionGroup unbounded.
2013-10-01
- [VDV] Added TpegSubReasonGroup to the ReasonGroup as described in the SX Documentation
SIRI-SX is an XML schema for the exchange of structured SITUATIONs
Version 2.0 DraftArts, recreation and travel, Tourism, Travel (tourism), Transport,
Air transport, Airports,
Ports and maritime transport, Ferries (marine),
Public transport, Bus services, Coach services, Bus stops and stations,
Rail transport, Railway stations and track, Train services, Underground trains,
Business and industry, Transport, Air transport, Ports and maritime transport, Public transport,
Rail transport, Roads and road transport
CEN TC278 WG3 SG7SIRI-SX Xml Schema for PT SITUATIONs. Common element subschemaStandardSIRI-SX Situation Model.Type for abstract EntryAbstract type.Time of creation of SITUATION.Type for loggable Entry.Time at which SITUATION element was versioned. Once versioned, no furtr changes can be made.situation Informatiion.Associations with other SITUATIONs.Information about source of information, that is, where the agent using the capture client obtained an item of information, or in the case of an automated feed, an identifier of the specific feed. Can be used to obtain updates, verify details or otherwise assess relevance.Type for references.A reference to another SITUATION with an indication of the nature of the association, e.g. a cause, a result, an update. Note that a Entry that is an update, i.e. has the same IdentifierNumber but a later version number as a previous Entry alway has a supercedes relationship and this does not need to be expliciitly coded.Type for a reference.Time of creation of 'related to' assocation.Elements identifying a SITUATION element or an update to a SITUATION. Participant reference is optional and may be supplied from context.A single string that identifiers the referenced SITUATION.Relationship of refercence to the referncing SITUATION e.Values for Type of Source.Type for individual IPT ncident.Type for individual PT SITUATION.Body of SITUATION.Body of SITUATION.Structured model identifiying parts of transport network affected by SITUATION. OPERATOR and NETWORK values will be defaulted to values in general Context unless explicitly overridden.Structured model describing effect of the SITUATION on PT system.Structured model describing distribution actions to handle SITUATION. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used.Type for individual IPT ncident.Type for individual PT SITUATION.Body of SITUATION.Datex 2 SITUATION.Structured model identifiying parts of transport network affected by SITUATION. Operator and Network values will be defaulted to values in general Context unless explicitly overridden.Structured model describing effect of the SITUATION on PT system.Structured model describing distribution actions to handle SITUATION. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used.Datex2 SITUATION Record.Datex2 SITUATION management elements.A unique alphanumeric reference (either an external reference or GUID) of the SITUATIONRecord object (the first version of the record) that was created by the original supplier.The date/time that the SITUATIONRecord object (the first version of the record) was created by the original supplier.The date/time that the information represented by the current version of the SITUATIONRecord was observed by the original (potentially external) source of the information.Each record within a SITUATION may iterate through a series of versions during its life time. The SITUATION record version uniquely identifies the version of a particular record within a SITUATION. It is generated and used by systems external to DATEX 2.The date/time that this current version of the SITUATIONRecord was written into the database of the supplier which is involved in the data exchange.The date/time that the current version of the SITUATION Record was written into the database of the original supplier in the supply chain.Datex2 SITUATION common elements.An assessment of the degree of likelihood that the reported event will occur.Datex2 Trrffic element road.Impact of Road SITUATION as specified by Datex2.Impact of Road SITUATION as specified by Datex2 model. Datex 2 comments for public use.Ccomments not for public use.Datex 2 model of where event ois taking place on the road.Datex2 Tarffic element.Type for Raod scope for scope of SITUATION or effect.Optional spatial projection of road. Can be used to distriute the path of the road to systems that do not already hold it. To pass just a Reference, use Datex2 location.An event which is not planned by the traffic OPERATOR, which is affecting, or has the potential to affect traffic flow. This SIRI-SX element embeds the Datex2 TrafficElement, making all elements optional because they may alternatvielky be specified by common SIRI-SRX SITUATION elements.Values for Type of Source.Type for a source, i.e. provider of information.Country of origin of source element.Nature of Source.Further contact details about source. May be used for udpoates or verifcation.Nature of method used to get Source.Reference to an Agent, i.e. Capture client user who input an SITUATION. Available for use in intranet exchange of SITUATIONs.Name of for source.Job title of Source.Time of communication of message, if different from creation time.External system reference to SITUATION.Electronic file / attachment containing information about SITUATION.Group of source details.Email of Supplier of information.Phone number of Supplier of information.Fax number of Supplier of information.Information was obtained from a web site URL of site and/or page.Other information about source.Status elements.Whether the SITUATION has been verified.ProgressStatus. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION.Assessement of likely correctness of data.Whether SITUATION is real or a test.Likellihoo of a future sutuation happening.Publishing status one of a specified set of substates to which an SITUATION can be assigned.Values for Entry Status.Type for Publication status.Type for Quality of data indication. Elements affecting temporal scope of SITUATION.Overall inclusive Period of applicability of SITUATION.situation applies only on the repeated day types within the overall validity period(s). For example Sunday.Publication Window for SITUATION if different from validity period.Structured Classification Elements. Corresponds to TPEG 18 Event Reason.Arbitrary rating of priority 1-High.Confidentiality of SITUATION.Intended audience of SITUATION.Nature of scope, e.g. general, network.Whether the SITUATION was planned (eg engineering works) or unplanned (eg service alteration). Default is 'false', i.e. unplanned.Arbitrary application specific classifiers.additioanl reasons.Reason.StructuredReason Elements.Classifier of Pub;ic Event.Text explanation of SITUATION reason. Not normally needed. (Unbounded since SIRI 2.0)Values for Sensitivity.Values for Audience.Type for Quality of data indication. Values for ScopeType.Type for Location model for scope of SITUATION or effect.Affected overall Geographic scope.Affected OPERATORs, If absent, taken from context. If present, any OPERATORs stated completely replace those from context.All OPERATORs.Operators of services affected by SITUATION.Networks affected by SITUATION.Nrtworks and Route(s) affected by SITUATION.STOP POINTs affected by SITUATION.Stop affected by SITUATION.Places other than STOP POINTs affected by SITUATION.Stop affected by SITUATION.Places other than STOP POINTs affected by SITUATION.Stop affected by SITUATION.Specific journeys affected by SITUATION.Journeys affected by the SITUATIONjSpecific vehicles affected by SITUATION.Vehicles affected by the SITUATIONjRoads affected by.Type for Location model for scope of SITUATION or effect.Refereences to road network locations affected by the SITUATION.Description of affected road.Type for image.Reference to an image.Embedded image.Categorisation of image content.Text description of SITUATION. Some or all of this may have been generated from the other structured content elements. Where text has been overriden this is indicated.Default language.Summary of SITUATION. If absent should be generated from structure elements / and or by condensing Description. (Unbounded since SIRI 2.0)Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0)Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0).Further advice to passengers. (Unbounded since SIRI 2.0)Further advice to passengers.Any images associated with SITUATION.Image description.Hyperlinks to other resources associated with SITUATION.Hyperlink description.Values for image content.Type for a text that may be overridden.Whether the text value has been overridden from the generated default. Default is 'true'.Values for image content.Type for a general hyperlink.URI for link.Label for Link. (Unbounded since SIRI 2.0)Image to use when presenting hyperlink.Categorisation of link content.Type for list of effects.Nature of the effect to disrupt (or restore) service, and further details.Type for disruption.Period of effect of disruption, if different from that of SITUATION.Severity of disruption if different from that of SITUATION. TPEG pti26Parts of transport network affected by disruption if different from that of SITUATION.Effect on different passenger needs.Effect on a passenger need.Advice to passengers.How Disruption should be handled in Info systems.Change to normal boarding activity allowed at stop.Information on casualties.Description of fare exceptions allowed because of disruption.Type for boarding restrictions.Type of boarding and alighting allowed at stop. Default is 'Alighting'.Type of alighting allowed at stop. Default is 'Boarding'.Type for advice.Reference to a standardis advisory NOTICE to be given to passengers if a particular condition arises .Further Textual advice to passengers. (Unbounded since SIRI 2.0)Type for blocking.Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-tiem feed of the SITUATIONs. Default is 'false'; do not suppress.Whether information about parts of the network identified by Affects should be blocked from real-time departureinfo systems. Default is 'false'; do not suppress.Type for easement info.Ticket restriction conditiosn in effect. TPEG pti table pti25.Description of fare exceptions allowed because of disruption. (Unbounded since SIRI 2.0)Refernce to a fare exceptions code that is allowed because of the disruption. An easement may relax a fare condition, for exampel "You may use your metro ticket on the bus', or 'You may use your bus ticket in teh metro between these two stops'. Type for easement info.Time band into which delay will fall.Category of delay.Additional journey time needed to overcome disruption.
