On Feb 25, 5:59 pm, Roy Schestowitz <newsgro...@xxxxxxxxxxxxxxx>
wrote:
> ____/ Jesper Lund Stocholm on Monday 25 February 2008 22:01 : \____
>
> > Roy Schestowitz <newsgro...@xxxxxxxxxxxxxxx> wrote in
> >news:1326774.0QbyTOpFNq@xxxxxxxxxxxxxxx:
>
> >> ____/ Jesper Lund Stocholm on Monday 25 February 2008 07:34 : \____
>
> >>> How would you embed another application in a file? OOXML is a
> >>> document format - not an application or platform.
>
> >> The file can contain a description of an executable (or a pointer to a
> >> peripheral one). OOXML can contain arbitrary binaries, as well as
> >> Windows-only bits of code. I'll provide examples if you requires them.
>
> ^
> typo.
>
> > Please do. Any document format can contain arbitrary binary chunks and if
> > you feel like it, you can stuff an ODF-file with Linux-only bits of code
> > until it makes your face blue.
>
> > I don't see why it is a problem. Any document producer can put anything
> > they wish in the files.
>
> > What do you think the alternative should be?
>
> With all the Microsoft agents in this newsgroup, I don't know what noise you
> get exposed to (I filter them out), but here are some pointers taken from the
> past week (ish) alone:
>
> This binary part supports the storage of arbitrary user-defined data.
>
> ,----[ Quote ]
> | <Relationships xmlns="...">
> | <Relationship Id="rId7"
> | Type="http://.../customProperty" Target="CustomProperty.bin"/>
> | </Relationships>
> |
> | [...]
> |
> | Conclusion: Since there is no requirement on the format of the content, any
> | vendor can put its proprietary binary extensions in there.
> |
> | Good Bye Interoperability!
> `----
>
> http://www.noooxml.org/forum/t-41994/good-bye-interoperability-3-with...
>
> OOXML Contains Proprietary Microsoft Codecs (as 'Standard')
>
> http://www.noooxml.org/forum/t-41316/good-bye-interoperability-2-with...
>
> DIS-29500: Deprecated before use?
>
> ,----[ Quote ]
> | Simultaneously, ECMA addresses this in Response 34 of its proposed
> | Disposition of Comments by removing all references to idiosyncrasies from the
> | specification and placing them in a newly formed Annex for deprecated
> | information. With the removal of this information from the DIS-29500, the
> | design goal of MS-OOXML can no longer be met. The entire specification has
> | therefore effectively become obsolete.
> `----
>
> http://fsfeurope.org/documents/msooxml-idiosyncrasies
>
> I can find you comments from the DIS-29500 Web sites which clearly indicate
> that there are deprecated Windows-only printing functions right there inside
> OOXML. There are many similar examples, but given the flood here of Microsoft
> agents I don't think it's the right place to discuss this.
>
> --
> ~~ Best of wishes
>
> Roy S. Schestowitz | "The only source is Open Source"http://Schestowitz.com | Open Prospects | PGP-Key: 0x74572E8E
> Tasks: 148 total, 1 running, 147 sleeping, 0 stopped, 0 zombie
> http://iuron.com- knowledge engine, not a search engine
Why do you keep trying to deflect attention from the fact that ODF
allows the EXACT same thing? It does - read the spec. People in
glass houses and all that...
--
Tom Shelton
|
|