Team driving support

[pnc]

This implements the design from opencab#17 in the sample consumer and provider.

At a high level, it provides a way for:

1. Identity providers to indicate when a second (or third, etc.) driver has logged into the device.
2. HOS providers to return HOS information for each logged-in user, including duty status and hours-of-service clocks.

It aims to be backwards compatible, so that single-driver functionality will continue to work between an older consumer app and a newer provider or vice-versa.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
opencab	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 4, 2023 5:21pm

[pnc]

Thanks a ton @ZonarTimH!

Fixing the docs so they can be easily browsed is still on my list.

[pnc]

@Mehantp @BoKlassen Please see the latest commit, which fixes the docs for the HOS "manage action" and "logout action" to specify that it's a URI, not an "intent string." (Android seems to have pretty completely eradicated the old intent: URI scheme for security reasons, so I don't think it's a good idea to pin the spec to that.)

https://github.com/opencabstandard/opencab/pull/21/commits/ae1a215989eab7a2374a9554dcc8d2d5e4d93b8f

[BoKlassen]

@Mehantp @BoKlassen Please see the latest commit, which fixes the docs for the HOS "manage action" and "logout action" to specify that it's a URI, not an "intent string." (Android seems to have pretty completely eradicated the old intent: URI scheme for security reasons, so I don't think it's a good idea to pin the spec to that.)

ae1a215

Awesome, thanks. This works better for us.

[pnc]

Good deal, that matches real-world usage of that property today, so it should be net no change for @ZonarTimH et al.

It does leave open the possibility of users seeing a disambiguation dialog if two apps try to use the register for the same URI scheme in their manifests, but I think that risk is fairly remote.

[pnc]

This resolves #17.