Why not saving in V1 format?

[walt.farrell]

21 minutes ago, BofG said:

I'd personally be in favour of all such apps using either PDF or SVG for their native formats, give us proper interoperability.

Neither of those formats support enough functions to use them as native formats.

[R C-R]

Just now, walt.farrell said:

Neither of those formats support enough functions to use them as native formats.

For example, no way to include history in the file or many of the non-destructive features.

[Pšenda]

15 minutes ago, walt.farrell said:

Neither of those formats support enough functions to use them as native formats.

This, by the way, is the main reason why every company makes its own format for its application with specific functions and needs. If it were true that there is one open, well-documented and highly efficient format that enables absolutely everything and forever (if someone would object, for example, to xml, then it is only a way of writing information - their content and interpretation is already completely specific), then why would anyone waste time and money inventing and maintaining their own formátu?

[walt.farrell]

38 minutes ago, BofG said:

PDF can do history,

What standardized function in PDF would allow History? 

If the function and format are not part of the actual standard, then other apps won't be able to interpret it properly, and it doesn't help if PDF were used as the native format. So it's no good if it simply allows a chunk of data with unknown content.

[R C-R]

19 minutes ago, BofG said:

I'm not so naïve to think any of this would happen, but I'm also not naïve enough to believe that it's only not happening because it's technically impossible - it's not happening because it doesn't make business sense.

It is in part also about what is most efficient in terms of memory & file storage space, & what can be made highly responsive or incur unacceptable lags that might make some sort of 'universal' standard technically feasible but unacceptable in real world use.