Basically, the backend really need to access resources (files etc.) through an interface which don't expose exactly where it gets it's data from. This is because depending on the way the backend is used, it can come from files or from online uris etc.
The backend should work with streams of data and just push and receive these streams.
By default, AOS Designer would just use an implementation that put things into the filesystem. But depending on the use, the interface should make it clear that data might not be from or saved to the same locations.
As abstract location value, use URIs exclusively even if they are in the filesystem.
Basically, the backend really need to access resources (files etc.) through an interface which don't expose exactly where it gets it's data from. This is because depending on the way the backend is used, it can come from files or from online uris etc.
The backend should work with streams of data and just push and receive these streams.
By default, AOS Designer would just use an implementation that put things into the filesystem. But depending on the use, the interface should make it clear that data might not be from or saved to the same locations.
As abstract location value, use URIs exclusively even if they are in the filesystem.