Development of Transactional Data Specifications for Demand-Responsive Transportation (2020) / Chapter Skim
Currently Skimming:
Pages 18-27
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 18... ...
18 This chapter begins a more in-depth discussion of the general principles and considerations applicable to data specifications for software applications, as well as functional and technical factors relevant to a demand-responsive transportation transactional specification. The focus changes in this chapter from all stakeholders to those stakeholders who will actively use the specification and most likely be involved in some manner in the process of specification development, formal adoption, and subsequent governance.
|
From page 19... ...
Principles and Considerations in Developing the Transactional Data Specification 19 all the data elements needed for each party to accomplish that specific transaction. A specification is sufficient if it is capable of handling all "use cases" that typically occur within its transactional domain; each "use case" describes a scenario in which two or more parties interact for purposes of transacting among themselves or exchanging information.
|
From page 20... ...
20 Development of Transactional Data Specifications for Demand-Responsive Transportation • Specifications must build on trusted relationships and provide gatekeeping mechanisms to mediate collaborative system-to-system interactions among parties. Given their potential -- and often actual -- impact on technology suppliers and their customers, new specifications in particular are the opposite of business as usual.
|
From page 21... ...
Principles and Considerations in Developing the Transactional Data Specification 21 there will be a strong need to ensure that concerns such as data privacy and security are handled appropriately by the technical solution. In some cases, transactions can be routed through certified gateways, such as with standards-compliant payment processors.
|
From page 22... ...
22 Development of Transactional Data Specifications for Demand-Responsive Transportation delivery times. Later in the scheduling process, a specific vehicle will be assigned to the trip.
|
From page 23... ...
Principles and Considerations in Developing the Transactional Data Specification 23 that the latter perform some specific action(s) related to a business transaction or potential transaction.
|
From page 24... ...
24 Development of Transactional Data Specifications for Demand-Responsive Transportation Model 2 -- Publish and Subscribe In a publish and subscribe model, an application registers with another system/application -- similar to an individual signing up for an online service that requires them to provide an email address and mobile phone number as part of their account -- and subscribes to a service that informs it of events of interest. The events can be of specific interest to the external application or more general in nature.
|
From page 25... ...
Principles and Considerations in Developing the Transactional Data Specification 25 Over the past 25 years, APIs have become the most common method for business applications to communicate with external software systems/applications. An open API is simply one in which the technical details of the API are published and available to a large community of other systems.
|
From page 26... ...
26 Development of Transactional Data Specifications for Demand-Responsive Transportation The latter means that each step in the process is well-defined and that all entities using the specification must adopt the same approach in their external-facing transactional interactions. Moreover, given that this is the first step toward a common transactional data specification, the approach should be relatively granular and support data interchanges that are atomic, meaning each transactional step is self-contained.
|
From page 27... ...
Principles and Considerations in Developing the Transactional Data Specification 27 suppliers and users today and in the future. Market conditions and technical functionality that will affect the development of a transactional data specification for the DRT industry were also discussed; industry buy-in and governance considerations will be critical to the overall success of development and adoption of a specification for DRT transactional data.
|
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.