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

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

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

  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.

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

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

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

  9. 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
  10. 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.
  11. 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
  12. 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.

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

  14. 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
  15. 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?

  16. 99% open... by pgilman · · Score: 3, Insightful

    ...is 100% closed.

    --
    if i'm a grammar nazi, you're an illiteracy nazi.
  17. 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.

  18. 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 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
  19. 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
  20. 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.

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

  22. 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
  23. 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
  24. 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