I'd assume that some sort of ODF capability will make it into iWork '09 (or '10, whenever we see a new version) since Leopard's TextEdit supports it. But does anyone speculate that Apple will provide anything close to complete support for ODF? After all, everyone seems to be moving toward a more open, data-portable way of doing things, and although Apple's iWork format is documented it's not implemented across platforms. Seems to me like native ODF support (or even native OOXML support) would do nothing but foster Apple's place in the Office program industry since files could be exchanged with everyone. Especially when you consider the alternative that we now have three different variations on Apple's own iWork document format (take yer choice, save in iWork '05, iWork '06' or iWork '08 formats!)
Thing is, is Apple's feature set even implementable in ODF? I mean, I don't know much about the XML-based Office specs, but using Numbers as an example, all other spreadsheets support a one-table-per-sheet model. Could a many-tables-per-sheet model even be expressed in ODF? What would it look like to other applications?
The sad thing about open standards is that they collide with innovation. I completely see Apple's need to make their own format so that they can bring an innovative, new user experience to the table. It's just a shame that they had to create their own format to do it rather than working with the ODF group to implement something like this in the spec.
Thing is, is Apple's feature set even implementable in ODF? I mean, I don't know much about the XML-based Office specs, but using Numbers as an example, all other spreadsheets support a one-table-per-sheet model. Could a many-tables-per-sheet model even be expressed in ODF? What would it look like to other applications?
The sad thing about open standards is that they collide with innovation. I completely see Apple's need to make their own format so that they can bring an innovative, new user experience to the table. It's just a shame that they had to create their own format to do it rather than working with the ODF group to implement something like this in the spec.