Slashdot Mirror


Microsoft Partially Opens Proprietary XML Format

eschasi writes "Groklaw has an article up reporting that Microsoft is going to open up their XML representation of the DOC format in response to Massachusetts' demand for open formats. According to Groklaw there are some interesting caveats involved in the move. From the license: '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'. While opening up the format even partially is a good idea, it's still a far cry from folks being able to write programs that create DOC-compatible files."

71 of 369 comments (clear)

  1. Opening? by wzzrd · · Score: 5, Insightful

    Mind you, this is - as I understand it at Groklaw - merely an opening to make GPL-applications able to read (not write!) government made (nothing else) documents, without interfering with MS patents. 'Open' might not be the best word for this...

    1. Re:Opening? by CDarklock · · Score: 5, Insightful

      I find it strange that they say "fully compliant". What if you create a document that is NOT fully compliant? Maybe that substitutes one tag for another? You'd probably need a lawyer to answer that question, but it's an interesting question.

      --
      Microsoft cheerleader, blue flag waving, you got a problem with that?
    2. Re:Opening? by Technician · · Score: 5, Interesting

      'Open' might not be the best word for this...

      The best word is "tip" as in the tip of the wedge. Someone somewhere will need to fill out a government form and send it back. The file will be opened to be exported. It will be exported to an open format. The Government will need to open the document. This will either cause the demand for open format support in government by using 3rd party software or Microsoft in order to keep the applications will have to change to meed the consumer requirements to fully support open formats. Tip of the wedge is the best description. The tip is in place. Now the pressure mounts. Let's see what gives next.

      --
      The truth shall set you free!
    3. Re:Opening? by mrchaotica · · Score: 4, Insightful
      You'd probably need a lawyer to answer that question, but it's an interesting question.
      And that very fact means it's not open at all...
      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    4. Re:Opening? by DaveLV · · Score: 3, Informative

      http://www.microsoft.com/Office/xml/faq.mspx

      Q. Are the licenses that Microsoft offers under the Open and Royalty-Free Office 2003 XML Reference Schema program perpetual in nature?
      A. Yes. The licenses for the Office 2003 XML Reference Schemas are perpetual. There is no term limit on the licenses.

      Q. Can the licenses for the Office 2003 XML Reference Schemas be used by open source developers?
      A. Yes. Open source developers who wish to participate in a community development project can enter into the agreements and then work in a collaborative fashion on development of a program or programs.

      Q. Can I distribute a program that can read and/or write files that support the Office 2003 XML Reference Schemas in source code form?
      A. Yes. You can distribute your program in source code form. But, note that the patent and copyright provisions in the license for the Office 2003 XML Reference Schemas require you to include a notice of attribution in your program.

  2. Proprietary XML? by sugapablo · · Score: 5, Funny

    Proprietary XML? Leave it to Microsoft to completely miss the whole damn point.

    1. Re:Proprietary XML? by 0x461FAB0BD7D2 · · Score: 5, Funny

      They got the wrong definition. Redmond thought it meant "eXclusive Markup Language".

      Small typos like that get passed around in memos and next thing you know, you have patents for numerous things.

    2. Re:Proprietary XML? by cablepokerface · · Score: 3, Interesting

      Proprietary XML? Leave it to Microsoft to completely miss the whole damn point

      Be damned if I know what proprietary has to do with it being humanly readable. Leave it to slashdot readers to think Xml has much to do with open source because you can "look at it".

    3. Re:Proprietary XML? by plague3106 · · Score: 2, Interesting

      You can have xml and still be properitary. In otherwords its their schema that is propertery (they claim no one else can use that schema).

      Of course given enough word docs you could probably figure out the schema...but they have a patent on it.

    4. Re:Proprietary XML? by iabervon · · Score: 3, Insightful

      The relevant point of using XML is that it's a standard for serializing and deserializing structured data in a way that doesn't depend on the type of data. So it's an advantage in maintainability over their old binary formats, and makes it easier for different Office versions to be compatible with each other.

      The only benefit to them of XML being commonly associated with public standards is PR.

    5. Re:Proprietary XML? by SolusSD · · Score: 4, Insightful

      XML was designed to alleviate problems exchanging data between different formats. Using namespaces to define what different fields meant data could be exchanged by simply translating the namespaces. It is almost pointless, aside form being human readable, for microsoft to use XML if they are going to make it proprietary and not allow any other programs to read/write it. allowing readability of the format is one step forward.

    6. Re:Proprietary XML? by amembleton · · Score: 2, Interesting
      The simple fact is that, making your format open to anyone has consequences, one of them being integrators who do not correctly implement the standard you set forth. In other words, 3rd party software that can't read _your_ documents because of bugs / misapplications in _their_ code can, unfortunately sometimes be construed as being _your_ fault.

      If that is the case, why doesn't Microsoft publish the XML schema and allow any other application to read and write to those XML files on the conditions that they fully implement the schema. AFAIK, this appears to be some kind of token gesture that Microsoft has carried out in order to sell their software to the government.

    7. Re:Proprietary XML? by idlake · · Score: 2, Informative

      The relevant point of using XML is that it's a standard for serializing and deserializing structured data in a way that doesn't depend on the type of data.

      XML is a markup language, not a language for serializing data structures. The two are not the same: most of XML is completely unnecessary for serializing data structures, so something much simpler would do, while at the same time, XML lacks primitives for common data structures found in real programming languages. That makes XML a really poor choice for serializing data structures.

      XML has been misused for the purpose of serializing data structures, but that's fitting a square peg into a round hole.

      XML is designed for document interchange. It's an idiosyncracy of MS Word that it is currently using data structure serialization ("marshalling") for its storage format. Actually, it's not even an idiosyncracy, it is plainly idiotic. But that's not the worst problem with MS Word anyway.

  3. The most important is reading... by vidarlo · · Score: 5, Insightful
    This at least gives us the right to our own data back, since we can then convert it to a more useable format. So it seems like we've won the first battle, but not the war!

    The right to own data was lost with closed format, since it did require a license to read something you might have produced yourself. For a private person, it might be sad. For a corporate needy of its archives of past correspondance, it can be catastrofal. That microsoft opens up their format for reading, and specifies parts of it, makes it possible to write software to convert this data to a open format, or index it and such. Therefor, we can still save in MS format, but have much-less tie in.

    I'm only wondering how far it goes, if it goes as far as to say that I'm allowed to make a non-MS certified opensourced bot that crawls my disk, and indexes office XML files... And what if a corporate does so, will they be allowed?

  4. Interesting Quote by Rude+Turnip · · Score: 5, Insightful

    "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."

    It seems that the ability for a citizen to read and access government documents should surpass all other interests, regardless of licensing issues. In other words, even if a government employee was boneheaded enough to save a document in a proprietary format, my ability access to the information in that document should be guaranteed no matter what, licenses be damned.

    1. Re:Interesting Quote by hab136 · · Score: 2, Insightful
      The First Ammendment expands your rights.

      It is exactly that type of thinking that was the argument against the Bill of Rights - that enumerating them would cause people to think that the amendments granted the rights as opposed to simply recognized them.

      It has been objected also against a bill of rights, that, by enumerating particular exceptions to the grant of power, it would disparage those rights which were not placed in that enumeration, and it might follow by implication, that those rights which were not singled out, were intended to be assigned into the hands of the general government, and were consequently insecure. This is one of the most plausible arguments I have ever heard urged against the admission of a bill of rights into this system; but, I conceive, that may be guarded against. I have attempted it, as gentlemen may see by turning to the last clause of the 4th resolution.

      from http://odur.let.rug.nl/~usa/P/jm4/speeches/amend.h tm

    2. Re:Interesting Quote by uncqual · · Score: 2, Informative

      The First Ammendment expands your rights.

      The First Amendment (along with the rest of the Bill of Rights) was not intended to expand rights but to clarify rights that already existed.

      Some of the Founders felt that the Bill of Rights was unnecessary because the Federal Government's role was so limited by the body of the Constitution that it wasn't possible for the Federal government to impose on any of the rights itemized in the Bill of Rights. At the time, there were concerns (valid, as it turns out) that itemizing a subset of one's rights in the Bill of Rights could lead to actually limiting the rights of states and individuals to those listed (although the Ninth and Tenth Amendments tried to address these concerns, they have not met this goal very successfully as they have been increasingly ignored by the courts).

      The adoption of the Bill of Rights was mostly to address the concerns of the Antifederalists and "take the wind out of their sails". By the time the Bill of Rights was ratified, there was relatively little interest in it since the Federalists had prevailed already -- but since they had prevailed, in part, based on the promise to consider a Bill of Rights, it went ahead. I think today we might consider the Bill of Rights as something arising from "cloakroom politics".

      --
      Why is there an "insightful" mod and why isn't it "-1"? If I wanted insight, I wouldn't be reading /.
  5. Sneaky by danbond_98 · · Score: 4, Insightful

    Ah, and once again Microsoft do what they do best: create a solution to a demand which doesn't actually solve the problem but your average politician can point at and say "they've cooperated". Bit like their server licencing and the judgement against them in the EU, it's providing a solution which is useless yet looks good on paper.

  6. Re:Fully off topic, but... by Enigma_Man · · Score: 2, Informative

    The MS Game "Allegiance" was actually 100% open-sourced by MS a while ago, just for your info too. I know it's not a document format, but MS (especially the developers section) does open-source stuff on occasion.

    -Jesse

    --
    Nothing says "unprofessional job" like wrinkles in your duct tape.
  7. Re:What Open by Winckle · · Score: 2, Insightful

    Yes, and no. There are some issues with formatting and the positioning of content, I hope that this partial release of information can help the OO.org team to improve OO write.

  8. a usefull start by FidelCatsro · · Score: 2, Insightful

    If they open up the format just enough so we can read it , it will be a nice enough start so we can officaly open the documents then save them as a fully open format.
    As much as i would love them to be made to play fair and open the format fully ,
    Opening it enough to make it easy to parse gives us all we need incase of the disapearence of word , or MS trying to force an upgrade by breaking compatability in some way.

    --
    The only things certain in war are Propaganda and Death. You can never be sure which is which though
  9. DOC format question by mzwaterski · · Score: 2, Interesting

    I'm a little confused on the whole .DOC being a closed format issue. If OpenOffice can write documents in the proprietary .DOC format, why can't other programs? Am I missing the picture completely? Thanks for any explanation!

    1. Re:DOC format question by NanoGator · · Score: 2, Insightful

      "Also, MS has some bogus patents on their .doc format and we all know how many years they can tie things up in the courts for."

      Gee, if that were true, you'd think OpenOffice, an app that threaten's one of MS's actual monopolies, would have been ceased and desisted by now.

      --
      "Derp de derp."
    2. Re:DOC format question by hepwori · · Score: 2, Informative

      OK, there seems to be a lot of confusion here. I have heard, but do not have confirmation that the MS Word license includes a clause that says you will not open/modify any files you create in anything but Word.

      You are contributing to the confusion. I have just read the Word 2003 EULA and no such clause exists.

  10. Hopefully Governments will force this further by Albanach · · Score: 4, Interesting
    With luck, other government agencies can force this position further. For example if you can't write in these formats, it emans Governemnts can't exchange doccuments for editing to anyone without effectively insisting they own a copy of Microsoft Office.If a governemnt organisation wishes to distribute a form to be completed, a spreadsheet to be filled in etc there are immediate problems.

    Equally this still presents a roblem for QUANGOS. Non government organisations that perform the delegated work of governments will not be able to produce doccuments without restriction on which programs can read them. This could present huge confusion for end users who can't be expected to know where that blurry line between organisations lies.

  11. Keep DOC closed by SunPin · · Score: 2, Insightful

    Does anybody really want to keep this format going? Let Microsoft do whatever the hell they want and focus on moving people to open source one person at a time.

    --
    Laws are for people with no friends.
    1. Re:Keep DOC closed by SCHecklerX · · Score: 4, Insightful

      Yes, but allowing read-only access is great, because it is a win for the people. They can read their old stuff in word/excel/powerpoint, and then save it to a new open format. They can then ditch microsoft software entirely without having lost their work and without the need to spend endless hours reformatting a bad import.

  12. Re:What Open by garcia · · Score: 3, Informative

    Sort of but that's not the point. They are crappy work arounds for the proprietary format. If the XML isn't all fucked up like MSFT probably wants it to be then anyone can easily view the documents (and write them) in any current AND future program that can read standardized XML.

    If MSFT can't close the document format and any program can correctly read/write documents in the way they were intended what advantage does MSFT have.

    That's why MSFT doesn't want this and everyone else does.

  13. Re:What Open by tobiasly · · Score: 3, Informative

    Yes, but they did this through reverse-engineering. IANAL but this probably leaves them open to DMCA lawsuits.

    Microsoft has simply left this alone because OO.o and the others aren't yet a threat. If they ever become one, you'll see the floodgates open.

  14. Re:What Open by mcslappy · · Score: 2, Funny

    Clippy!

    now if i could only find that old copy of microsoft bob...

  15. Re:Off-Topic but curious by MyLongNickName · · Score: 3, Funny

    Simple. He simply uses Windows Calculator, and translates from binary 10001100001111110101011000010111101011111010010 to hex. Simple when you think about it.

    --
    See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
  16. Toilets by SunPin · · Score: 4, Funny
    Is there even anything as ubiquitous as Word that we can compare to?


    Toilets. I believe toilets are as ubiquitous as Microsoft Word.

    --
    Laws are for people with no friends.
    1. Re:Toilets by Ohreally_factor · · Score: 5, Funny

      And at $40 per seat on average, toilets are much cheaper than Word.

      --
      It's not offtopic, dumbass. It's orthogonal.
  17. Re:Not enough - write Mass. Govt.! by mmkkbb · · Score: 4, Funny

    using proper English grammer and spelling.

    How about, you handle the grammar and I handle the, Spelling. "OK"

    --
    -mkb
  18. XML patented by microsoft? by khrtt · · Score: 2

    What, the party invented the aeroplane?

    Can someone explain (I'm not trolling here) how the heck did M$ manage to shove a patent in on a public format that's been around for ages?

    Or, is it some other issue than patents this time? I mean, XML-based formats are easily hackable, so M$ doesn't really need to spec it for you to write a converter, even though for a state government it would be logical to ask for a spec.

  19. Re:XML by yagu · · Score: 2, Informative
    xml itself is designed to be easy to use, easy to read in "human" form...

    The problem with the MS implementation as I have understood it is Microsoft has used xml as transport for their proprietary DOC format, not defined their DOC structure in xml. There's a difference here. The former being the case, yes, you can get to the xml and "see" the DOC, but it is just an ascii encoded binary... so, you really get nothing more than the old proprietary stuff, AND an extra layer of obfuscation! Hardly what xml was supposed to be about.

  20. I'm sure this all makes sense to lawyers... by Mrs.+Grundy · · Score: 3, Interesting

    ...but I'm a little confused. Suppose I get a copy of a document in a format with a closed license. In what way am I bound to that license? When did I agree to it? Why would I ever need permission to from the creator of the format to read it? Is there some mysterious EULA that I accepted by being born? Or does this license only apply to people who create the documents with a microsoft application who have presumably agreed to some byzantine concept of ownership?

    1. Re:I'm sure this all makes sense to lawyers... by drawfour · · Score: 3, Informative

      Standard disclaimer: IANAL, and this is my intepretation from reading patent law.

      That said, patents have an interesting way of working. The patent holder can prevent the USE of his/her patent, even if it's non-commercial (aka private) use. This means that if the patent holder (Microsoft) gives a patent license that says you can READ them, then it doesn't matter who created the original Word document to begin with -- Microsoft has patented the format of that document, and any use of the propritary format falls under patent law. And patent law explicitely states that even USE of such a patent can enforced by the patent holder.

      The magic "EULA" that you accepted is US patent law, which applies to anyone in the United States. Just living here is the EULA.

      So, in a nutshell, the creator of that document owns a copyright on that document, but the format used to create that document is patented by Microsoft, so they get to enforce that patent and anyone who did not agree to their EULA can be sued.

      Of course, Microsoft doesn't really care about an individual user, but anyone writing a tool to write a file into their patented document type falls under the "distribution" clause of patents, and that company is fair game.

  21. Re:What Open by IamTheRealMike · · Score: 2, Interesting

    I always got the impression most of the remaining work was being bug-for-bug compatible with the Word layout engine, eg agreeing on what margins are and so on rather than actually reading the file data itself.

  22. Toilets: Total cost of ownership by SunPin · · Score: 2, Funny
    And at $40 per seat on average, toilets are much cheaper than Word.


    I agree with your assessment of toilet seats being cheaper than Microsoft seat licenses but shouldn't we wait until Microsoft releases a study on the total cost of ownership between toilets and Microsoft Office?

    --
    Laws are for people with no friends.
  23. And speaking of formats... by dteichman2 · · Score: 2, Interesting

    Wouldn't it just be SO easy to ditch DOC and start using HTML? All you'd need to do is have major corporations remove other options from the menu, so HTML would be the only option. Welcome to the new format. It's really easy. It's 100% compatable with even the most basic text editors. Although, Office does seem to produce butchered HTML (but only with images). Until they resolve this issue, I can dream.

    --


    Silence is golden... and duct tape is silver.
    1. Re:And speaking of formats... by sremick · · Score: 2, Insightful

      We can't both preach that "HTML is a Markup Language, not a layout language" (which is true) and at the same time propose it as an alternative format for documents from programs in which exact fixed layout on a given medium (printed paper of a certain size) is expected. Web pages on the other hand resize and reflow and are supposed to adapt to different screen sizes and devices of different capabilities/fonts/etc.

      Two different types of files for two different purposes.

  24. DMCA does not ban Reverse Engineering! by Xoder · · Score: 4, Informative

    Reverse-engineering for compatibility purposes is still legal under the DMCA. Reverse-engineering is OK as long as you don't do it to infringe upon copyright.

    Source, The text of the DMCA, Chapter 12, Section 1201.f (find within page for "reverse engineering")

    --
    The previous sig has been removed due to /. protecting your best interests
  25. Still not GPL compatible by Anonymous Coward · · Score: 2, Informative
    The FAQ states:
    Q. Can I distribute a program that can read and/or write files that support the Office 2003 XML Reference Schemas in source code form?

    A. Yes. You can distribute your program in source code form. But, note that the patent and copyright provisions in the license for the Office 2003 XML Reference Schemas require you to include a notice of attribution in your program.

    The GPL does not allow any additional restrictions beyond those of the GPL. The requirement for attribution is an additional restriction.

    Also, any software that implements this is violating the spirit of the GPL. The license explicitly restricts use of the patents to reading and writing MS documents. Noone may take such an application and modify it to make their own XML document format.

    - krafty

  26. One thing I don't get.... by SQLz · · Score: 3, Interesting

    Here is my question, the MS patent on this XML format has not been fully accept right? The patent office is awaiting public comment. Has anyone gone to make a comment?

    Also, I don't even see how you can patent using open standard. I mean, XML was designed as method of storing data,amoung other things. How could the patent office possibly accept a patent where XML is simply being used to do what it was designed to do?

    I mean, to draw a parallel. The 110w outlet in the US is an industry standard right? I mean, everyone can make plugs and outlets royalty free and all the appliances and devices can plug into them for power. MS patenting XML to store a word processing file is like Sony patenting a TV that uses the 110w outlet, thereby blocking anyone else from doing it even though they didn't invent the outlet or the TV. The same holds true here. MS didn't invent XML, they didn't invent the word processor, nor did they invent storing a word processing file in XML. So, how in the hell can they apply for a patent on it? Just by paying money?

    1. Re:One thing I don't get.... by qodfathr · · Score: 2

      You are a little off the mark. MS does not have a patent on using XML to store a word processing document -- rather, they have a patent on their PARTICULAR format. In your example, it would be like Sony creating a very special power supply that plus into 110 (well, 120 these days, and, geez, I hope you meant volts and not watts...) and can drive a 100" TV at 5000 lumens but consumes only 12w. THAT they could patent.

      --
      Yes, it's true. This man has no dick.
  27. 99% open... by pgilman · · Score: 3, Insightful

    ...is 100% closed.

    --
    if i'm a grammar nazi, you're an illiteracy nazi.
  28. Re:What Open by hal9000(jr) · · Score: 3, Insightful

    I think that the reason it became so popular was the close file format.

    Whaaaa? Cart or horse, which comes first?

    Dude, Word did not get popular because of proprietary file format. Users don't give a rats ass about file format until they need to export/import from one to the other. That the file format is commonly used is a result of the programs popularity. Word got popular for other reasons such as aggressive marketing, aggressive pricing, aggressive positioning, feature richness, useability, blah, blah.

  29. Why is so hard to drop MSOfifce? by vhogemann · · Score: 5, Interesting

    I work for the municipal healthcare dep. at Rio de Janeiro City. Here at Brasil the federal gov. has stabilished a deadline to change most software to opensource or free equivalents by 2007.

    So, we started by enforcing the use of OpenOffice in every desktop. The process is simple, if someone want that old 450MHz Duron replaced by a new 2GHz Athlon they must use OpenOffice instead of MSOffice. Its amazing how this argument work!

    Mind you that we don't forbid the installation of MSOffice on this new machines. No sir, anyone can BUY and DONATE the licente to the city, so the software can be installed legaly on the computer. Heh, imagine how often it happens!

    The next step was to replace Lotus Notes (argh!) with PostFix + Cyrus running on Debian, and installing ThunderBird on every desktop. Most users just loved the change, because the Lotus Notes Client realy suck.

    To add an nice touch, every DOC file that pass trough the email system is converted into a PDF, for tha sake of virus-prevention... The only way to pass an editable document thought is to use OpenOffice native format!

    One day, I dream of substitute all W2k desktops with Ubuntu Hoary... and tell its just a new version of WindowsXP. With most of the users already using OpenOffice, ThunderBird and Firefox I gess none of the users will notice the change! ;-)

    --
    ---- You know how some doctors have the Messiah complex - they need to save the world? You've got the "Rubik's" complex
    1. Re:Why is so hard to drop MSOfifce? by Duckman5 · · Score: 2, Interesting
      every DOC file that pass trough the email system is converted into a PDF

      How exactly are you going about doing that? I've been trying to find a Free/OSS implementation of a program that does that, but can't. They are all either commercial programs or require the use of Windows and the MS Word viewer.
    2. Re:Why is so hard to drop MSOfifce? by vhogemann · · Score: 5, Interesting

      We just use wordview to convert from DOC to HTML, then pipe the output to htmldoc. The conversion is FAR from perfect. But thats the point... to get perfect documents the user must use OpenOffice, or zip the file.

      --
      ---- You know how some doctors have the Messiah complex - they need to save the world? You've got the "Rubik's" complex
  30. Re:I'll never understand some arguments by m50d · · Score: 4, Insightful

    You forget one thing: it's not their document that people wants to read, it's the customers', just stored in their format. It's like the guy who built my house refusing to tell me what size bricks he used, so that I have to hire him to do all the repairs.

    --
    I am trolling
  31. You never lost the right to your data ... by AHumbleOpinion · · Score: 2, Insightful

    This at least gives us the right to our own data back, since we can then convert it to a more useable format. So it seems like we've won the first battle, but not the war!

    You never lost the right to your data, you could always output your data into something else. Text, RTF if you wanted to preserve formatting. RTF's specification and a sample reader are published by Microsoft, http://msdn.microsoft.com/library/default.asp?url= /library/en-us/dnrtfspec/html/rtfspec.asp. You have won nothing, you do know that Microsoft used to publish word and excel formats on their website? It did not impeded MS's dominance, it did not help the competition.

  32. One big non-issue here by AHumbleOpinion · · Score: 2, Insightful

    If you cared, and few really do, you could always have written an RTF file with word. RTF is documented and sample readers are available from Microsoft, http://msdn.microsoft.com/library/default.asp?url= /library/en-us/dnrtfspec/html/rtfspec.asp. Word and excel format used to be published, it hardly mattered with respect to Microsoft achieving dominance or helping the competition.

  33. You're using the word "data" incorrectly. by mosel-saar-ruwer · · Score: 2, Interesting

    This at least gives us the right to our own data back, since we can then convert it to a more useable format...

    That microsoft opens up their format for reading, and specifies parts of it, makes it possible to write software to convert this data to a open format, or index it and such. Therefor, we can still save in MS format, but have much-less tie in.

    You seem to be under the impression that ".DOC" documents use something other than eight bit ASCII characters to store data. Try this: Open up WINWORD.EXE, type in "abcdefg", save the file as "abcdefg.DOC", then open up "abcdefg.DOC" with NOTEPAD.EXE.

    Guess what? NOTEPAD.EXE will show you that your data, the string "abcdefg" is there in the file just as it ought to be.

    There is no loss of data when using WINWORD.EXE; rather, there is a gain of typesetting [or markup, or "formatting"] structure that other typesetting [or markup, or "formatting"] programs might not be able to understand.

    Microsoft owns the rights to their own proprietary typesetting [or markup, or "formatting"] algorithms, but they make absolutely no claims whatsoever on the underlying data that those algorithms act upon.

    If you don't like Microsoft's typesetting algorithms, then use Corel's [WordPerfect], or IBM's [Lotus Word Pro], or Apple's [iWork], or hell, even Donald Knuth's.

    And after you've tried those other proprietary algorithms, ask yourself whether Microsoft's proprietary typesetting algorithms failed to offer you any value for your money.

    Besides, even if none of what I've said is true, you can still always take your ".DOC" documents, open them in WINWORD.EXE, and click on "File | Save As... | Save as type | Text Only (*.txt)" and never have to deal with Microsoft for the remainder of the life of your data.

    1. Re:You're using the word "data" incorrectly. by shutdown+-p+now · · Score: 2, Insightful

      You miss the fact that formatting of the document is also part of the data contained in that document.

  34. Re:Hey thanks by Anonymous Coward · · Score: 2, Funny
    No, the purpose of XML is to get rid of languages like C and shell scripts by making otherwise simple configuration files cumbersome and difficult to parse without a full blown OOP based parser.

    It's also to force people to migrate from text files and commandlines to full blown GUIs by turning simple stuff like:

    #
    #minute hour mday month wday who command
    #
    #*/5 * * * * root /usr/libexec/atrun
    #
    # Run daily/weekly/monthly jobs.
    15 3 * * * root periodic daily
    30 4 * * 6 root periodic weekly
    30 5 1 * * root periodic monthly
    to
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//SCO, Inc.//DTD PLIST 1.0//EN" "http://www.sco.com/DTDs/cronxml-1.0.dtd">
    <cront ab version=1.0>
    <job minute=15
    hour=3
    user=root>periodic daily</job>
    <job minute=30
    hour=4
    weekday=6
    user=root>periodic weekly</job>
    <job minute=30
    hour=5
    monthday=1
    user=root>periodic monthly</job>
    </crontab>
    (That's me trying to format it nicely, btw.)
  35. Re:XML by Quiet_Desperation · · Score: 2, Informative
    OK. That's amazingly silly, but it still seems like a doable reverse engineer job for a dedicated group of programmers.

    There appears to be nothing at http://schemas.microsoft.com/office/word/2003/word ml

    wordml. Is that like Manimal? Never mind. :)

  36. FUD by ad0gg · · Score: 2, Informative

    Offic outputs real xml with no base64 encoded or cdata blocks

    --

    Have you ever been to a turkish prison?

  37. Legality of Propietary Standards? by adorai · · Score: 2, Interesting

    Could someone point me to a reference about the laws regarding proprietary standards in the first place? Can't I write my own program to manipulate files in any format, whether or not the file format was created by someone else? Then is it illegal to create a program where Ctrl+C means copy, since ____ (Apple?) invented that?

  38. Patent should be rejected by NoMercy · · Score: 3, Interesting

    Patenting something is good, to protect inovation, if microsoft has created a invention which allows amazingly wierd complex data structures to be stored in a higherical structure easilly then they can patent that, but that wouln't be a patent on the XML file which stored the resulting structure.

    This patent seems to be on the arragement of data, if that arangement was chosen so a specific process can work on the data then patent that process with the data arangement, if not then this patent is for one thing and one thing only, anti-competitive behaviour, and as such shouln't be granted.

  39. Re:I'll never understand some arguments by Anonymous Coward · · Score: 3, Insightful

    > Why does Microsoft have to open up their file format anyway?

    They don't have to. Let them keep it.

    On the other hand, I want the right to participate in my country's politics without having to pay the Microsoft tax. Hence, government must use open standards.

    I personally believe that government should avoid software that uses proprietary formats from the outset. Some people, however, believe otherwise, and they are lobbying for a compromise that will make it legit for government to use Microsoft software.

  40. WTF? by roguer · · Score: 5, Informative

    XML is a W3C recommendation (not an open standard; W3C makes that distinction for a reason). It is based on SGML (not UML). XML is a meta-markup language like SGML; it is a means of specifying markup languages such as HTML or WML (not a markup language like HTML). Being a W3C recommendation, XML is copyrighted... by the W3C (not it cannot be copyrighted). Patenting and licensing of XML schemas or DTDs (which is what Microsoft did) is not the same thing as copyrighting anything (tools, formats used by tools, whatever) As for You can write anything on paper but it still doesn't make it true? I couldn't agree more. In fact that statement is as true of Slashdot comments as it is of paper. Jeez, I hate Microsoft as much as any Slashdotter, but at least get your facts straight!

    --
    It's a penny for your thoughts, but you put in your two cents worth. Somebody, somewhere is making a penny. SteveWright
    1. Re:WTF? by mlyle · · Score: 2, Informative

      US Copyright law no longer requires a notice of copyright on the copyrighted work for it to be protected by copyright law; nonetheless, the XML specification is protected by copyright. Anything someone creates is copyrighted by default under the current copyright regime; one has to explicitly put it into the public domain to disclaim copyright.

      However, the documents are licensed under very permissive terms-- see the W3C Document License.

      See the W3 IPR FAQ:

      2. Who holds the copyright on W3C documents?

      The original author of the document. Many documents are created by the W3C and we consequently hold the copyright. Owners who allow their works to be published on the W3C site retain the copyright, but agree to the W3C license for the redistribution of those materials from our site.

  41. Office 2003 XML Reference is already available by I'm+Don+Giovanni · · Score: 2, Informative

    Office 2003 XML Reference Schemas:
    http://www.microsoft.com/office/xml/default.mspx

    --
    -- "I never gave these stories much credence." - HAL 9000
  42. May not be GPL compatible by hey! · · Score: 2, Interesting
    The patent license says:

    You are not licensed to sublicense or transfer your rights.


    It's hard to say, but I'd read this to say that I can write GPL'd software, but anybody who wants to create a derivative work. would have to go the Microsoft web site and agree to the license.

    This is probably splitting hairs, but unless the format is released into the public domain or into an open licensed format, there is nothing that says Microsoft couldn't change their mind later and stop granting licneses. My license may be perpetual, but anyone who doesn't make it in the gate may be out of luck.

    Furthermore, this might allow Microsft to halt distribution of GPL'd implementations of their formats to people using the program for non-government purposes. Note this clarification:


    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.


    So, you can distribute your OpenOffice filter to people, but presumably only under the condition that they use it to read government documents.
    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  43. Not correct... by Eric+Damron · · Score: 2, Insightful

    "This at least gives us the right to our own data back, since we can then convert it to a more useable format."

    Not correct. "We" will have no right to read or write data in their format. Only "Government documents" may be read. That doesn't give most of us shit.

    --
    The race isn't always to the swift... but that's the way to bet!
  44. this goes to show that MS is scared of OSS by xutopia · · Score: 2, Insightful

    specifically of GPLed software. They are putting loads of effort to get around that but GPL software is creeping up everywhere and they don't know how to stop it.

  45. Microsoft Wins Again! by mpapet · · Score: 3, Interesting

    Microsoft can now say, "Office XML file format is available for anyone to read. This proves Microsoft is promoting open standards."

    Decision makers who don't care about the nuances of open standards or this issue, will put a check mark next to Open Standards in their features matrix.

    Meanwhile, MS develops MSXML solutions to extend their reach into lucrative corporate markets now populated by small companies.

    Don't mod me down (again) for the following, because this is the harsh reality.

    Alternative office suites may be able to read and write M$ XML all they want some day. Microsoft simply doesn't care because they aren't a real threat to their bottom line. *No* Office application competitor redefines the broad market or adds new overwhelming feature/value to the broad Office applications market. Period. You can imagine what MS would do if such a thing existed.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  46. Re:So what ... by TheRaven64 · · Score: 3, Informative

    Microsoft can not prevent you from writing software that creates .doc files. What the can do, is prevent you from writing software that creates .doc files if you read the .doc file specification. They own the specification, and can put any conditions on it they like (up to those permitted by law). You then have to choose between reverse engineering the format (assuming you live somewhere where it is still legal), or getting a copy of the spec and only adding read support.

    --
    I am TheRaven on Soylent News
  47. Obviously... by rice_burners_suck · · Score: 2, Insightful
    They are obviously doing this to shut up the European courts that want to fine them about $5,000,000 bucks per day for failing to comply.

    I think the courts should under no circumstances let this pass. This is a bunch of BS, and I think that unless Microsoft complies fully and delivers the complete format of the data files, they should be fined not $5,000,000 per day until they comply but $5,000,000 per day until at least 100 independant open source computer programs exist that can handle Microsoft document files in their entirety, with no major user complaints about the functionality of these programs.