1 / 8

Open Telematics API: Collaborative Machine-Readable Specification

Explore the collaborative effort to create a machine-readable REST API spec for LTL motor freight carriers and TSP integration. Discover the OTAPI release, data model, security aspects, contributors, and future work. Thank you for your interest!

mosterman
Download Presentation

Open Telematics API: Collaborative Machine-Readable Specification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Open Telematics API Lightning Talk @ W3C Workshop

  2. What We’ve Done • Collaborated to create: • Machine-readable REST API specification for how LTL motor freight carriers can integrate with TSPs

  3. OTAPI Release • github/nmfta-repo/nmfta-opentelematics-api • Source of specification • Offline HTML documentation • opentelematicsapi.docs.apiary.io • Interactive HTML documentation • apimatic.io/apidocs/nmfta-opentelematics-api • Client libraries • github/nmfta-repo/nmfta-opentelematics-prototype • Prototype server implementation

  4. The Data Model • Vehicle • Fleet • Driver • Log Event (‘ELD’ events) • Vehicle Performance Event (idle time summaries etc.) • Vehicle Fault Code Event (e.g. DTCs) • Vehicle Status Event (e.g. battery V) • Accessible via use-case focused streaming APIs

  5. Security-First • Security Manifest of OTAPI Design Decisions • Mandatory Fine-grained Access Controls • Mandatory Client-Side Security Requirements • Mandatory Sever-Side Security Requirements • Published prototype satisfies server-sider security requirements

  6. Contributors • Many revisions in many pull requests • A couple face to face sessions • Several unnamed contributors • Many conference calls 

  7. Future Work • Find a home for future revisions of OTAPI • Adding support for on-boarding and off-boarding of devices/vehicles (common when vehicles come from truck leasing companies)

  8. Thank You! github/nmfta-repo/nmfta-opentelematics-api Ben Gardiner ben.gardiner@nmfta.org (no, I don’t know why this needs to be clickable in a presentation either) www.nmfta.org

More Related