Pozdrav svima,

Vrlo mi je zao ali sa ovim ne mogu da se slozim. Kada se cak i ovlas pogleda trenutna
specifikacija, za koju sam vec napomenuo da od marta prosle godine menjala vise puta, ovo "YES"
odozdo ne drzi bas vodu. Na osnovu trenutne specifikacije ono sto se moze zakljuciti jeste da
standard ne garantuje mogucnost implementacije bez dodatnih informacija od Majkrosofta. Problem kod
mnogih delova ovog standarda jeste bas jedna recenica iz poslednjeg pasusa teksta koji je gospodin
Cvetkovic naveo: "Microsoft will make the information broadly available via Microsoft.com, as
well as to place these formats under the Open Specification Promise (OSP)."

Za previse stvari u OOXML se kaci futur glagola biti - "Majkrosoft ce". Ne dovodim u pitanje da li
ce kompanija to uraditi ili ne. Mozda hoce, mozda nece. Ne umem da predvidjam buducnost. Ali jedan
standard ne sme imati obecanja da ce nesto biti uradjeno. Ako ce OOXML biti standard onda mora
odgovarati svim zahtevima koje jedan standard mora ispuniti da bi bio to sto jeste.

Suma price, OOXML specifikacija u ovom trenu ne garantuje totalno nezavisno implementiranje samo na
osnovu te specifikacije. Bez ulazenja u diskusiju da li ce kompanija omoguciti pristup svim
informacijama vezanim za OOXML ili ne ono sto ovog trena imamo na stolu nije dovoljno
"transparentno"(popularna rec u ovoj zemlji poslednjih godina) za jedan standard.

> Pozdrav svima. Jedna od Markovih tema je bila vezana za sledece pitanje: On the grounds of the
> existing MS-OOXML specification, can any third party regardless of business model, without access
> to additional information and without the cooperation of Microsoft implement full backward
> compatibility and conversion of such legacy documents into MS-OOXML comparable to what Microsoft
> can offer?
> 
> Enjoy - Dejan
> 
> In short the answer is YES.
> 
> In detail:
> The backwards compatibility support found  in Open XML was included to preserve the large volume
> of documents that around 400,000,000 users around the world have already created using the binary
> file formats of prior versions of Office and the common capabilities utilized in those files.
> With Open XML, they can successfully migrate the document to ECMA's Open XML file format to
> ensure no loss of data and high fidelity to any application that chooses to implement support for
> the Open XML file format. This provides them the capability to utilize their application of
> choice that supports the Open XML file format.
> 
> The very reason of having several features (e.g. dates, VML, autonum etc) in a special section
> called "Deprecated" and not omit them altogether, is exactly because ECMA/Microsoft want everyone
> to be able to have access to this kind of information and be able to faithfully simulate the
> behavior of the binary doc files in their apps. Having these features as part of the
> specification means that all related patents are under OSP, thus anyone can implement them. In
> addition to this, Microsoft plans to make it even easier to obtain the documentation for its
> Office binary file formats (.doc, .xls, .ppt). While this information has previously been
> available on a request basis, interested parties who wanted this information have had to request
> it and sign a contract to receive the binary documentation.  Microsoft will make the information
> broadly available via Microsoft.com, as well as to place these formats under the Open
> Specification Promise (OSP).