A driver interface defines the actions automation code needs and the data those actions accept and return. Because these needs can be independent of the application interface, multiple drivers can support the same logical scenario through different application interfaces. section 15.6
Authentication drivers
An authentication interface can define Login and Register actions. REST API and service drivers can implement that contract, letting scenarios use the same actions while the implementation varies. section 15.6 section 15.6
Figure 15.5 Polymorphic driver interface with multiple implementations

Use the diagram to see how one driver interface can connect to multiple implementations. section 15.6
