Graph-building syntax simpler for web developers #16
rama: proposal to hide implementation details, i.e. that the operands are represented by integers
ningxin_hu: agree proposal (1) from rama is a good improvement for ergonomics
rama: addOperation can create and return an result operators it creates
ningxin_hu: for (2) feedback is, how to support optional output of tensors, batch normalization etc.
ningxin_hu: addition comment, as mentioned, foundation spec is direct derivative from Android NN API which is a C style API, inherits its style
… due to this background, my suggestion is to survey other graph-building APIs in native ecosystem to learn API design patterns
paul: would love to contribute our learnings from two Microsoft's graph-building APIs
PROPOSED RESOLUTION: open a separate issue for surveying other graph-building APIs from native ecosystem
Resolved: open a separate issue for surveying other graph-building APIs from native ecosystem
Define the set of operations and their specification
gregwhitworth: don't want to duplicate effort, many folks representing ONNX on the call who have done definition of operations
… prefer keep us focused on JS API and reference pre-existing other spec for a set of operations
kainino: not working on TF, not able to give Google's position
Jonathan: heard a concern internally, that not sure if by depending on external reference we can keep up with rapidly developing set of ops
Jonathan: I'm volunteering to take an action to find out internally at Google whether referencing ONNX would be reasonable
paul: thanks for digging in
ningxin_hu: as mentioned in this issue, in our POC we've studied TF Lite and ONNX model support
… we've looked at models for use cases identified by this group, there's a spreadsheet with mapping
… maybe could start with a subset of ops driven by use cases
anssik: how is the ONNX set of operations evolved, what is the process?
paul: use case driven, surveyed existing frameworks, common denominator
<ningxin_hu> this is the models and required op spreadsheet: /docs.google.com/spreadsheets/d/1nthZOwgIKsj34EB-SymEwoNTPsxo4X8Pxavm-JaBwME/edit?usp=sharing/(removed)//docs.google.com/spreadsheets/d/1S4WOyyQpAQy7Ac56KVTApv-M691ItTLpFzrrH7aAi6Y/edit?usp=sharing
paul: evolving the set is community-driven in the open
… releases every ~2 months
W3C Workshop on Web & Machine Learning
dom: W3C Staff, working with Anssi on many other projects e.b. WebVR
… a year ago started project how to use ML in the context of web browsers
… target of the workshop would be to bring the broader community together
<dom> dom: would be useful to get input on dates
<dom> ... what events to avoid clash with
paul: not aware of any October dates that would block
rafael: no bandwidth to organize, but +1 to participate if dates work
<dom> dom@w3.org
Succeeded: s/https://docs.google.com/spreadsheets/d/1nthZOwgIKsj34EB-SymEwoNTPsxo4X8Pxavm-JaBwME/edit?usp=sharing/(removed)
Maybe present: anssik, dom, gregwhitworth, Jonathan, kainino, paul, rafael, rama