I have a potential use case where it might be useful to read/write OpenVX graphs to some file format (say xml).
This is to allow offline processing which could be used to generate custom architectures for specific graphs.
Has such a case been considered, or would you expect vendors to provide their own API's?
Here's a bit more detail on what I was thinking;
* Develop OpenVX application on a PC
* Save graph after testing
* Run through a compiler tool chain to produce a custom hardware design
* Run hardware on embedded platform, potentially re-loading graph to derive interfaces
Graph import/export is a very useful feature. I imagine that it will remain vendor specific until Khronos can agree on a schema (perhaps something like GraphML?) then it would be relatively easy to standardize. It will be great to be able to produce/comsume/exchange these with externally tooling.
One issue to settle is included data within a graph. Matricies and small data structures would not be too hard to represent in some manner, but large images may have to be base64 encoded.