Microsoft Office Formats Not Really Being Opened
Contradicting this earlier article claiming otherwise, smith_barney writes "Contrary to reports, Microsoft is not opening up its proprietary Office XML schemas. Essentially, the state of Massachusetts is simply repositioning what it considers an 'open format.' According to a report in BetaNews, Microsoft told the state it would ease licensing restrictions, but only for 'end users who merely open and read government documents.' This hasn't stopped Microsoft from tooting its horn, but Jupiter Research senior analyst Joe Wilcox says, 'Buzz about so-called open formats is little more than PR FUD.'"
Nothing for you to see here. Please move along
That is probablly what your going to get when you try to work with one of these "open" formats from MS.
Bush not really a Muslim.
Babies not really delivered by storks.
Bears do not actually have modern sanitation.
By summer it was all gone...now shesmovedon. --
Looks like an 'open and shut' case to me...
Seriously, how many people need stuff in Office that isn't in OpenOffice.org?
Almost everyone uses Microsoft Office as opposed to the various flavors of OpenOffice, StarOffice, etc. Not speaking of its fairness, this is a very effective strategy from Microsoft and not at all surprising.
It's a blatant abuse of their virtual monopoly, but there hasn't really been an effective incentive for them to stop taking such actions in the past. Why would they refrain from continuing such behavior?
I'm a big tall mofo.
"open" is a four letter word, and to Mr. Gates, it is an obscene four letter word.
www.eFax.com are spammers
If this is their understanding of an open format, then what would a closed format be in Microsoft's book? A write-only one?
Man is a slave because freedom is difficult, whereas slavery is easy.
I would think that even the NEW Office will still be able to create good ol' .doc files, so wouldn't it burn their biscuits if people just continued to use that instead? (They'll make some minor feature .newdoc only -playing solitaire while working on a doc?- and everyone will use it, anyway, no wishful thinking here...)
Microsoft is joking with us again or we are joking with ourself on beliving this?
http://www.michel.eti.br
"..it is our expectation that the next iteration of the Open Format standard will include some Microsoft proprietary formats."
**TILT**
I guess Proprietary is Open and War is Peace?
Let us all hope that Massachusetts doesn't accept Microsoft's formats if they aren't completely open when it undertakes its review of the decision. If Microsoft are seen to have open office formats in the eye of the public when they are not really open, it can only be a bad thing for OpenDocument and other truly open efforts.
Everyone who lives in MA, go and write to your appropriate representative now!
One good turn - gets all the covers.
Bill said "Suprise! what did you expect fuckers?" :-) *bang goes my karma!*
Really, Microsoft always say they will do some things, to basically spread FUD, to make managers have an excuse for not jumping ship.
Why do they do this?
Hmmm, lets read my crystal ball, aaaah here is a M$ press release:
"Closed format is more secure! Plus it locks you into Office, which we have no bundled with Windows, which is now etched into the core of every processor! *stiffled manic laughter*"
Translation:
"We really don't want to allow people to easily leave Office behind and we want to make it harder for OpenOffice to import etc, because when people realise they don't need office, we will loose money
Also we don't want people to easily crack our DRM and embarrass us as we extort money from publishing companies and spread FUD amongst authors, so people can no longer read stuff without money coming to us
Plus world domination is fun!"
#hostfile 0.0.0.0 primidi.com 0.0.0.0 www.primidi.com 0.0.0.0 radio.weblogs.com
Isn't this like saying, "we wrote the English Dictionary so no one is allowed to read English without our approval?" To me, if you want to copyright an idea for a product, go ahead, if you want to protect intelluctual property, that's fine too, but formats for files? Come on! So what if my program can read and write files that your program reads and writes. As long as I didn't take your way of writing those files, I should be fine.
VD
Could we all endeavor to remember that "FUD" is an acronym for "fear, uncertainty, and doubt" and not simply a synonym for "lying". There is little of the usual Microsoft "end of the world" blather here; it's just deceptive marketing.
In other words, business as usual.
The Mongrel Dogs Who Teach
I installed Open Office for a staff member of a customer's company. She had been using a computer with Microsoft Word before. She didn't notice that anything had changed.
Probably a lot of us on Slashdot are very sensitive to GUI design, but many people aren't.
1) crawl to the File menu
2) click on Open document
3) select a document
Voila... the document is now open. Yes it's THAT simple.
Home of Faramir Paint Shop Pro scripts
<office>??????????????</office>
</xml>
The MS Office open XML file format consists of an XML branch, followed by an Office branch.
Unfortunately, due to the complexities of parsing this branch, it should be passed directly as a parameter into our improved Office ActiveX object.
We are currently developing an addin for firefox as well.
Thank you for looking at this documentation, that will be all.
liqbase
The Future Is Open: What OpenDocument Is And Why You Should Care ~ by Daniel Carrera
How do you verify the accuracy of Slashdot stories?
Boring, I know. But I live here so I get to have at least one pet peeve.
I was actually quite hopefully that Microsoft would open the format. As a developer, a completely open format would have been wonderful. This is sad news. Not surprised, just upset.
The last version of Microsoft Word I used was in Office 2000. I got tired of it because it is so quirky with layout.
Open Office is a bit quirky, too, and they are different quirks. Many times people forget the many, many hours they spent learning to avoid the Office 2000 quirks. They want Open Office to be perfect, and they have forgotten how imperfect Microsoft Word is.
If you test Open Office, be sure you test the latest version, 1.1.4. Version 2.0 will be available in April or May of this year.
It's understandable that people who have invested hours in learning Microsoft Word don't want to invest hours again. They just want to get the job done. On the other hand, it would be crazy for the Open Office developers to implement the hundreds of ways Microsoft Office is quirky.
Generally, when you send documents outside your company, you should send PDF files. That guards against accidental changes. To do this in Open Office, just click the PDF icon in the toolbar. To do this in Microsoft Word, install an extra-cost package.
"...Massachusetts is simply repositioning what it considers an 'open format.' [...] This hasn't stopped Microsoft from tooting its horn [...]'Buzz about so-called open formats is little more than PR FUD.'"
Although the borg are doing something bad, this time they are doing it by making something bad of theirs sound good, instead of making something good of someone else's sound bad. Should there be a word which represents the contrapositive of "FUD"? Like LAC, for Lying About Crap, or something? (maybe it's the inverse, not the contrapositive, it's been a while, feel free to correct me)
"A witty saying proves nothing." ~Voltaire
"d'Oh!" ~Homer
Whilst the annoucement in yesterdays /. was a licence that was gpl-incompatible, it was (afaict) within the scope of existing open licences (it didn't read too disimilar to an old-style bsd licence) - I certainly didn't notice any restrictions on writing, and since that is still up on MS's page, i'm guessing that possibly the chap quoted here was speaking unaware of that announcement. either that or MS's site was hacked or maybe I've just misread something.
"Success is based on knowing how far to go in going too far"
Essentially, the state of Massachusetts is simply repositioning what it considers an 'open format.'
How does Bill Gates screw in a lightbulb?
He doesn't. He declares darkness the industry standard.
___
It's the end of my comment as I know it and I feel fine.
Cue all the "I really need [obscure function XYZZY] in {Word, Excel}" bots from Microsoft!
Not everybody who uses M$ Office is doing trivial work, some of the secretaries where I work use it's advanced features to save immense amounts of time. You can moan about people that need functions that OpenOffice doesn't have but it still won't make OpenOffice better than M$ Office. Tossing about pharses like: "Well then don't use that function" is not an option for a poweruser, he/she will bin OpenOffice and write it off. The day that OpenOffice supports all the advanced features in M$ Office that I use and does so without falling apart I'll switch. Until then M$ Office is a superior product, be it on Windows, Linux or my prefferred OS.X. So let's keep things in perspective. I'm hoping OpenOffice will be able to compete with M$ Office sooner rather than later but hyping OpenOffice up will only hurt it.
Only to idiots, are orders laws.
-- Henning von Tresckow
It's clear that too many important people have had their heads up their arses for too long.
..... Mandate open data formats first, then guarantees of performance, then source code escrow to back up the performance guarantees and protect against vendor , then slowly tighten the screws on the escrow agencies and software companies till it's no longer economically viable to sell closed-source software.}
We need to have it made law that file formats are not secrets and not patentable, but form as much a part of the specification for interacting with the software as, say, the key bindings. {I personally would like to see it become law that software vendors must supply full annotated source code with their products, but let's take it one step at a time
It wouldn't surprise me if some software vendor had tried at some stage seriously to claim in an EULA that all the rights in any document created with their software belonged to them. I know that it used to be a breach of EULA to use a certain software company's programming languages to develop applications that competed directly with that company's offerings.
The good news is that EULAs aren't legally enforceable in any sane jurisdiction anyway, so you can go ahead and exercise your inalienable statutory right to reverse-engineer documents -- for the purposes of study, creation of interoperable software or just morbid curiosity -- to your heart's content. In fact, you can even refuse to accept the EULA at all. You can still quite legally use the software under your inalienable statutory right of Fair Dealing -- you just don't get any benefits that were only promised to you in the EULA.
Je fume. Tu fumes. Nous fûmes!
We probably were all wishing for the same, but that said, "opening" the format is probably harder than it sounds.
My understanding of the Office document formats -- which comes entirely from reading rants by OO.org and other projects to write office suites so take it with a big grain of salt -- is that the format itself is made up of serializations of stuff like activex control states. In other words, non-trivial.
I don't know if you or anybody here ever wrote a BeOS "replicant", but it was sort of like ActiveX in that they were serializable classes which could be instantiated by any program, by dlopening the replicant's source executable and running the exported code with the serialized state as initialization parameters. It was really cool -- an app could send a replicant to another app and whammo, you had stuff like a web-browser embedded on the desktop running in the desktop process, or a tray-item using your app's code, but running in the deskbar's process.
Anyway, given that Office uses this kind of approach, it would be near 100% *impossible* to get the state out without the source activex component. Unless the state itself is described in a 100% abstract manner. Which I doubt. The data is almost certainly just a serialization of the internal state of the activex control which created/modified/rendered it.
Now, I know that this kind of stuff only applies to Office when Word or Excel is embedding charts or whatnot from other parts of the office suite, but the fact is this is a useful ( and good ) way to get interoperability, even if it means that it's completely non-portable. Given MS's history, I doubt they've taken a simple approach.
I'm sure there could be better ways, and I imagine OO.org is taking a maximum-interoperability approach...
Anyway, I'm just saying. I don't think MS *could* open the format -- at least not as regards document embedding.
Rant over.
lorem ipsum, dolor sit amet
I'm no big fan of MS, but this is nothing more than good 'ol jump on the bandwagon MS bashing. This all comes from a letter from MS' XML guru explaining recent clarifications to the license to address concerns from MA. The exact quote is:
"We are acknowledging that end users who merely open and read government documents that are saved as Office XML files within software programs will not violate the license."
Here's the exact line from the license:
"By way of clarification of the foregoing, given the unique role of government institutions, end users will not violate this license by merely reading government documents that constitute files that comply with the Microsoft specifications for the Office Schemas, or by using (solely for the purpose of reading such files) any software that enables them to do so. The term "government documents" includes public records."
Does this statement preclude someone from using the file format for other purpose, such as say import/export from OpenOffice.org? Nope. It just gaurantees that open/reading government files will not violate the license.
Look before you leap...
From NPR...
y Id=4471963
"Morning Edition, January 31, 2005 The government of Brazil says it will switch 300,000 government computers from Microsoft's Windows operating system to open source software like Linux. Microsoft founder Bill Gates wants to meet with Brazil's president to discuss the change. Brazil is dropping all proprietary software."
Listen here: http://www.npr.org/templates/story/story.php?stor
The Brazilians are just saying no!
Anyone can use MS schemas too, and even distribute software that does so. Not without conditions, naturally. Where's the difference?
The license (two licenses, actually; one for the specification, and another for all MS patents that cover it) may not be GPL compatible, but it sure looks compatible with other open source licenses, including so-called viral licenses.
The catch with the GPL is the additional restrictions part. Microsoft adds two restrictions, both of which are more-or-less reasonable. The first is the obnoxious BSD-like advertising clause; that's irritating, but not a showstopper except for the GPL. The second restriction is that implementations must be conformant to be distributable. That is, reading and writing done by implementations based on the spec must read or write valid Office XML files. Since the format is a well-designed XML format, this is trivially easy to do. The requirement is to prevent forking of Office XML formats, which is obviously a concern of Microsoft's. Again, it would be nice for developers if this restriction was removed, but it would be detrimental to both Microsoft and Microsoft's customers.
Whoever corrects a mocker invites insult;
whoever rebukes a wicked man incurs abuse.
--Proverbs 9:7
We have the latest version of Office installed here (whatever it happens to be. I try to avoid Windows systems whenever possible). A few weeks ago someone brought in their thesis, saved in the version of Office they use at home to print. Loading it completely destroyed the formatting throughout the document. The only solution we found was to install PDFCreator on his home machine and bring in the PDF. Office has always had problems with backwards compatibility (I recall a number of Word 2 documents that didn't open correctly in Word 6), and this seems not to have improved. A number of organisations are still using Office 97 because they have standardised on the Office 97 file format for internal use and don't want to break things.
I am TheRaven on Soylent News
Probably the dweebs who generate and print your paycheck.
How do you spell your name? (clickety-clack)
Standards often get bogged down in politics. For EBCDIC, it was IBM vs. the competition, who pushed ASCII. Everyone could have standardized on EBCDIC, but that wouldn't have served the interests of IBM's competitors. It's the same logic that led the Europeans to create a whole library of communications standards that were similar, but incompatible, with the Bell System's standards. They were trying to protect their domestic markets and telecommunications companies.
Mea navis aericumbens anguillis abundat
'Buzz about so-called open formats is little more than PR FUD.'
... but chrissakes, could people stop overusing this term? It's just become idiotic, and I've started to get this knee-jerk reaction to knock lots of credence off any argument that uses it.
Show me where Fear, Uncertaintity, and Doubt is being employed as a tactic there? Maybe a bit of uncertaintity, all right
"FUD" seems to have the same connotation and baggage as "counterrevolutionary" does in a banana republic.
I am no longer wasting my time with slashdot
Anyway, I'm just saying. I don't think MS *could* open the format -- at least not as regards document embedding.
Even if everything thing you've said is true, your conclusion is unjustified.
M$ is getting $35,000,000,000+ per year. They could reverse engineer and document their own format with their small change, even if it was serialized Brainfuck. To claim that because it involves activex controls this somehow makes the format undescribable is simply wrong. If the format contains state, that state can be described. Period.
If M$ is claiming what you say they are then they are lying. To technically naive people. Business as usual for them.
---
It's wrong that an intellectual property creator should not be rewarded for their work.
It's equally wrong that an IP creator should be rewarded too many times for the one piece of work, for exactly the same reasons.
Reform IP law and stop the M$/RIAA abuse.
Strict meanings of both irony and begging the question have been used for millennia--literally, for they both originated in ancient Greece--so I wouldn't exactly call them gray areas. But while the (re)definition of "irony" one is more familiar with might indeed be a question of whether one prefers texts written by Plato or Alanis Morissette, copyright infringement is a completely different matter. Copyright infringement is by definition a violation of copyright law which is not a property law. Violating copyright is not theft because duplicating data is not appropriation of any property, much less a dishonest appropriation of property belonging to someone else with the intention of permanently depriving the other of said property. The key word here is "depriving," for theft is wrong not because the thief gets something without paying (the real goal of any theft), but because the victim no longer has that something (a side effect of every theft)--this is crucial. Furthermore, the copyright law was meant to protect authors from publishers, not from readers so reading a book without paying for the right to read or listening to music without paying for the right to listen is not only not theft, but not even a copyright infringment. The "copy-" in "copyright" is rather unfortunate, and should it have been called "publishing rights" there would be much less confusion today when "copying" is something we must do in order to play any kind of digital media. So, copyright infringement is not theft by any stretch of imagination. Nor is it piracy, for that matter, because it has very little to do with robbing or plundering at sea without a commission from a recognised sovereign nation, and quite frankly I have no idea why has that word been chosen in the first place. I know that in the "Don't Copy That Floppy" era, writing "piracy is a crime"--which is true, even if copying floppies is not--on BSA propaganda posters must have had a strong influence on people, but why using piracy and not just theft? My point is that--unlike irony--copyright infringment, theft and piracy, as well as trade secrets and patents, are all very strictly defined by law in any given jurisdiction and it is impossible to confuse them without clear malicious intents. This is not a question of definition or preference, but a matter of fact. So I fully agree with your point, but I wouldn't use the same examples.
Sincerely,
Pan Tarhei Hosé, PhD.
"Homo sum et cogito ergo odi profanum vulgus et libido."