Normalisation transport Information voyageur

(christophe.duquesne@aurigetech.com)

22/03/20121

22/03/20122

22/03/20123

Have both RPC-Literal and Document-Literal wrapped

• http://www.ibm.com/developerworks/webservices/library/ws-usagewsdl/index.html?ca=drs-

• Both will be compatible with each other (except Soap Fault)

• Decision: Document-Literal as additional is ok. Test with W3C tool, if ok. 2 pages in the document to explain 2 files in schema.

Deprecate SOAP Fault

• Decision: ok Add a new generic GetSiriService() SOAP Port

• The GetMultipleStopMonitoring could then be deprecated (but kept for compatibility issues)

• Decision: ok Add Siri Discovery Services to WSDL

Decision:, ok Proposal Sent by Christophe: XSD and document

22/03/20124

22/03/20125

Alignment is needed between the XSD/WSDL and the document• cardinalities

• Typographic

• Also needed for part 4&5

• Need for a global XSD-Document check

•Decision: Refresh document by the update readme of the XSD, check by CEN if part 4+5 are really adopted, change xsd in any case, may be document 4 m+5 later; Change request document from France is of 2011 and has not yet been dicussed

22/03/20126

22/03/20127

Onward and Previous Calls• Some use it based on the StopMonitorig requested Stop• Others use it from the vehicle location• You can find both explanations in the TS• Which is the right one ? Is it different from SM to VM ? • Then meaning is probably different between SM and VMDecision: Yes, it is different

•What is the MonitoredCall in Vehical Monitoring ? Decision: The one you just left

22/03/20128

There is a need for a stronger Discovery service•NeTEX is perfect for this purpose•However, SIRI/NeTEx articulation needs to be clarified

Need for clarification between SIRI and NeTEx scope regarding dated information• Mainly for SIRI Production Timetable service• Possibly deprecate SIRI PT (prefer NeTEx and create a Production Timetable Frame)•Decision: Do not deprecate. It is already implemented! Put hint into SIRI document when to use SIRI PT (update a timetabel transfered via another interface) and when to use NeTEx

22/03/20129

The ProgressStatusEnumeration (used on arrivals and departure status in Calls) has a an “arrived” value («early», «delayed», «cancelled», «arrived» or «noReport»)

• does it mean that the vehicle ist at Stop or does this information needs to be kept once the vehicle has left ?• What does « arrived » means in Departure ? (don’t we need a « left » value ?)Decision: add element ‘presentation status’ with explanation in the document.

• What difference with « Wehicle at Stop » in MonitoredCall ?

22/03/201210

What is the meaning of VehicleAtStop for OnwardCall• Clarifying if it is useless or not

• Is it only for requests on a past time ? But is ther any use case for this ?

Need to clearly state how to define train numbers• being consistant with NeTEx

•Decision: add explanation in document, add elemts TrainNumber and publishedTrainNumber

22/03/201211

Better describe how to combine MaximumStopVisits, MinimumStopVisitsPerLine and PreviewInterval• isn’t the MinimumStopVisitsPerLine a RequestedStopVisitsPerLine ?

•Proposal for the clarification comes from Christophe

22/03/201212

Provide examples et process description for subscription • On what field change is an update needed ?

• Describe the messages sequence when vehicle is passing at Stop

• Describe how to managed connexion loss and reconnexion from both sides

•Decision: Examples will be delivered from Christophe, but some are allready in part 2

22/03/201213

22/03/201214

Provide first and last journey informationDecision: On StopMonitoring Service but may be

also in other services. Connected to line. There is a need for additional information on answers :• No service today (on a Stop or a Line)• Service not yet started• Service terminated today

Need for a MinimumStopVisitPerJourneyPattern filter in the SM request• also possible “via” filter

Decision: to be done by via Filter

22/03/201215

Need for a way of having several Operators for one single Journey• Paris RER, and EBSF requirement….• Probably requires the use of JourneyPart

Decision: Needed, e. x. different operators on a long distance train going through several countries. Use NeTEx structure in SIRI.

Propose a non mandatory “demo” GeneralMessage message structure• France has one example to propose, including a small

request extension• May also be an input for SIRI Lite

Decision: Example comes from Christophe. Careful not to interfere with SIRI SX

Need for GroupOfLine information (attached to line, same level as NetworkRef)

Decision: Will be added.

22/03/201216

EBSF needs for

• check in / check out times

• earliest departure / latest arrival times

•Decision: e. x. for passengers to check in at Eurostar Train. OK, will be added in call for estimated and target times.

•State use clearly (!) in the documentation

22/03/201217

22/03/201218

How to model the SNCF “parit锕 Odd = to Paris

• Even = from Paris

• May change during the Journey (Odd => Odd => Odd => (paris) => Even => Even)

• Specific extension proposed in France for now (group Calls, with a CallGroupCode ….)

• Any cleaner way to do it in SIRI ?

• How to manage Direction change inside a Journey ?Answer: Add TechnicalTrainNumber element to JourneyPart

and journey part direction

22/03/201219

22/03/201220

See « FR comments on CEN_TS 15531-5.doc »