Skip to main content

Currently Skimming:


Pages 116-134

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 116...
... 116 A P P E N D I X E XML Listing of Specification The specification is presented in XML, which is commonly referred to as a "markup" language. A markup language is a computer language that uses tags to define elements within a document.
From page 117...
... XML Listing of Specification 117 [This is the first telegram] Telegram #: 1A; From: ordering client; To: trip provider(s)
From page 118...
... 118 Development of Transactional Data Specifications for Demand-Responsive Transportation Telegram #: 2A; From: ordering client; To: trip provider(s) ; Purpose: order confirmation unique ID from ordering client Telegram #: 2A1; From: ordering client; To: trip provider(s)
From page 119...
... XML Listing of Specification 119 Telegram #: 2B; From: trip provider; To: ordering client; Purpose: confirm trip is scheduled unique ID from ordering client Telegram #: 2BB; From: trip provider; To: ordering client; Purpose: confirm vehicle
From page 120...
... 120 Development of Transactional Data Specifications for Demand-Responsive Transportation Telegram #: 3A; From: trip provider; To: vehicle; Purpose: control vehicle unique ID from provider unique ID from ordering client
From page 121...
... XML Listing of Specification 121 Free-form long text field for notes to driver concerning customer service needs Telegram #: 3B; From: vehicle; To: trip provider; Purpose: confirm vehicle performed task unique ID from provider unique ID from ordering client
From page 122...
... 122 Development of Transactional Data Specifications for Demand-Responsive Transportation Telegram #: 4A; From: trip provider(s) ; To: ordering client; Purpose: performed trip data unique ID from ordering client Telegram #: 4B; From: trip provider; To: ordering client; Purpose: confirm trip is scheduled for vehicle unique ID from ordering client
From page 123...
... XML Listing of Specification 123 Telegram #: 5; From: vehicle; To: trip provider; Purpose: GPS and trip status unique ID from provider current value current value current value current value current value
From page 124...
... 124 Development of Transactional Data Specifications for Demand-Responsive Transportation XML Data Types The address known to receiving system Id identifying Country. Source (src)
From page 125...
... XML Listing of Specification 125 The coordinates for the address and potentially a known zone Shall be of type WGS84. See documentation in Use Cases. See documentation in Use Cases. Precision shall be from GPS-unit in vehicle and measured in meter. This is the deviation in position measured by the GPS-unit.
From page 126...
... 126 Development of Transactional Data Specifications for Demand-Responsive Transportation Speed shall be from GPS-unit in vehicle and measured in meter per second. Speed measured at GPS or VEHICLE. Direction shall be from GPS-unit in vehicle and measured in degrees (0 - 360 degrees) . Height shall be from GPS-unit in vehicle and measured in meter.
From page 127...
... XML Listing of Specification 127 Timezone used in communication. Default is local timezone.
From page 128...
... 128 Development of Transactional Data Specifications for Demand-Responsive Transportation Mobility Aid: Ambulatory Mobility Aid: Ambulatory lift Mobility Aid: Cane Mobility Aid: Crutches Service Needs: Door to door Service Needs: Driver Alert Service Needs: Door THROUGH door
From page 129...
... XML Listing of Specification 129 Mobility Aid: Electric wheelchair Service Needs: hearing impaired Medical: intellectually or developmentally disabled Medical: Kidney disease Medical: Mental health Medical: Dementia (memory impaired) Medical: Neurologic and degenerative diseases Service Needs: Never leave alone/ no leave alone Service Needs: Oxygen
From page 130...
... 130 Development of Transactional Data Specifications for Demand-Responsive Transportation Mobility Aid: Scooter Service Needs: Service Animal Service Needs: Seizure disorder Medical: Speech impaired Medical: Temporary Disability Service Needs: Unstable needs assistance Medical: Vision impaired Mobility Aid: Wheelchair Mobility Aid: Walker
From page 131...
... XML Listing of Specification 131 Mobility Aid: Knee walker Mobility Aid: Extended leg w/c = Extended Leg Wheelchair Mobility Aid: Wheelchair, can transfer Mobility Aid: Wide wheelchair Adult Day Program Dialysis Employment
From page 132...
... 132 Development of Transactional Data Specifications for Demand-Responsive Transportation Grocery Health-Related (includes dentist, pharmacy, etc.) Medical Personal Recreation Public transit General type identificationelement
From page 133...
... XML Listing of Specification 133 Any text aimed for operators, drivers etc True = message shall be sent to invoicing True = message shall be sent to vehicle True = message shall be sent to operator True = confirmation that the recipient has been notified shall be sent to client.
From page 134...
... 134 Development of Transactional Data Specifications for Demand-Responsive Transportation Attribute to send identity of the operator that has sent this manual text. The time period to propose car starts The time period to propose car stops The distance within which an unoccupied vehicle shall be proposed Type of unit in range.

Key Terms



This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.