22 May 2020 / 9:00 AM PDT / Zoom meeting

Attendees

Jane Shen, Neal Oliver, Tim Epkes, Dan Druta, Jiafeng Zhu, Tina Tsou, Jeff Brower

Meeting Notes - Zhu, Brower

Agenda

OpenNESS API introduction - Neal
Infrastructure API portal discussion, continued

Meeting Notes

Whitepaper co-authors’ draft ready
OpenNESS API introduction (Neal): PDF will be uploaded to file archive

-includes microservices, SDKs, reference hardware specs
-SDKs include OpenVINO, DPDK, IPP, MKL

Present the map and categories of API portal (Jane)

Do we consider domain specific (AR/VR) frameworks or applications? How to categorize them?
https://www.khronos.org/openxr/
Business aspects makes them unique
Android native platform running on Edge is different from application enablers

OpenNESS overview and Q&A

Group - AF and NEF API discussion
Tim - nature of closed source behind AF and NEF APIs, is it for platform-to-platform communication ?
Tina - what versioning is used ? Neal - none yet
Tim - host routing and URI content are options
Group - discussion about authentication, Neal - APIs must authenticate, Jiafeng - is Intel is using OAUTH protocol, Neal - no
Jane - how can we avoid incompatibility between application API data models, for example OpenNESS compared to MobileEdgeX

API portal discussion notes

Jane - shared MindMap generated HTML that she may use for the portal
Dan - some apps need infrastructure info from APIs, an example is an AR/VR “app manager” or framework. They are still an app but they manage other apps. Should the app enabler in the white paper diagrams reflect this ?
Dan - Chronos OpenXR is an example
Jeff - the current API portal content on api.akraino.org is hosted on MobileEdgeX servers. We will need Akraino web guys to add ToC links at top for 2 main categories: APIs for mobile app developers and infrastructure app developers
Tina - OpenGL ES2.0 and ES3.x APIs are needed by IEC blueprint

Action Items

Neal will post OpenNESS slide presentation on the API subcommittee file archive

Browser not supported