bhack

So protobuf is the de facto standard? I believe only in something more formal where all major framework are involved by design without to/from converters (or only optional for back...

Yes but every framework write whatever they want with protobuf. Converters don't avoid framework feature disaligment. Actually in production seems that cudnn versions defines what it is really important to...

I will like a common roundtable like for containers format hosted by linux foundation. I'm sure that this format need to be always a little bit behind state of the...

@forresti Exactly what I have told. Standard need to stay behind state of the art. Is cudnn really cutting edge (excluding the performance point of view)? No, arxiv is cutting...

This @vrv [comment](https://github.com/tensorflow/tensorflow/pull/2002#issuecomment-218783825) it is quite auto explicative of some of the standardization posts in this thread

1) Yes but why all the frameworks need to do it on cudnn? :) 2) Sure but there is no space for this cause frameworks still don't has started a...

Yes we have diverted the discussion at some point. I hope that the framework with more starts on github on day could restart that topic in a more appropriate context...

/cc @nyanp if he is interested for tinycnn. But I don't know if could be ready for this with full models coverage and GPU backend support.

There is now an official Intel Opencl PR at https://github.com/BVLC/caffe/pull/3355. /cc @gongzg

@scott-gray @andravin A vendor neutral API would really be a game changer. In the Vulkan era do you think that will be enougth to target SPIR-V? /cc @naibaf7 @keryell