Slashdot Mirror


Interview with Sun's Florian Reuter

silentbob4 writes "Mad Penguin is running a series of three interviews with people in the trenches working to bring you OpenOffice.org 2.0. The first of these interviews, with Sun's Florian Reuter, covers some of the differences between the truly open XML found in OpenOffice.org 2.0, and the closed MS Word ML found in the upcoming Microsoft Office 12. He also discusses the importance of simple end users in the process of improving the code with bug reports."

10 of 132 comments (clear)

  1. Could be a goodie. by holy+zarquon's+singi · · Score: 4, Insightful

    With the critical mass that the adoption of the open document format by Massachusets, google and others implies, the embracement of standards like XML and Xforms in OO.o that makes it pretty easy to create organisational workflows, this could be a real microsoft hobbler. Particularly if as seems likely, Microsoft keeps failing to adapt to an open standards world, and the price tag of OO.o stays lower than M$O.

    Bring it on, I say.

    --
    "...we should just trust our president in every decision that he makes and we should just support that." B.Spears 2003
  2. OK, so what IS different? by Moraelin · · Score: 4, Insightful

    I've actually RTFA, and I'm still at a loss about exactly _what_ is better about OOo's XML Schema, or wrong about MS's.

    In TFA the guy just goes on about how his own XML Schema is, you know, lovingly handcrafted and how he _cares_ about your data. Which is just a content-free judgment call. Yeah, so he likes his own XML Schema better. Whop-de-do, that's such a total surprise.

    It's not like if I went around the office and asked 10 guys I wouldn't get 10 different schemas, and each loves his own more and is convinced that everyone else's sucks. Just the proper way to use attributes alone has everyone polarized in three camps, with everyone in one camp arguing that the other two are awfully wrong and against the very idea of OOP or of XML itself. Handling validation and showing which fields are wrong to the user who filled the form? Yep, another clean three-way split, and I've actually had to implement three different ways to handle it, to please all three camps. And so on.

    So that he loves his own more and thinks it's a better way to store my data, is very much expected there. I was already sure he thinks that. In fact, I'd be worried if he said he didn't.

    What really interests me is exactly which concrete problems should I expect with MS's, that supposedly aren't there if I use OOo's format. If I try to retrieve that data in 5, 10 or 100 years, as in his answer, exactly in which way is OOo's format better? Exactly _what_ kind of data gets more benefits from his schema than from MS's in that context? In which way, and for what concrete reasons does he foresee that MS's own converters (which so far still import Word 6 documents with no problems) will break down and cry like little girls if fed a Word 12 document some 10 years from now?

    No, really, it's not a flame. I want to know. If I'm to go there and pester my boss to switch from MS Office to OOo, I damn better have some very concrete arguments and use-cases. If my whole argument is "but some guy from Sun likes Sun's format more" and "but Sun's format is lovingly handcrafted with love and care for your data", chances are I'll get laughed out of his office.

    So can anyone shed some more light on that issue?

    --
    A polar bear is a cartesian bear after a coordinate transform.
    1. Re:OK, so what IS different? by WARM3CH · · Score: 2, Insightful
      This making it impossible to implement in Free and most Open Source software? Not very useful to OpenOffice.
      Which is not really the point here, is it? The question was if generating/reading MS XML as simple as generating/reading OO.o XML or not. With documentations of both formats publicly available, I don't see any difference here. What you refer to is the distribution of the source of any such program, which is an entirely different topic.
    2. Re:OK, so what IS different? by Moraelin · · Score: 1, Insightful

      "OK, first things first; let's have a little lesson on what XML is. XML is not really that big a deal. All it means really is that the less-than and more-than signs are reserved symbols; one writes constructs such as ..... to indicate a bounded block of type foo, or to indicate a single instance of type bar. The meanings of different foo and bar are what constitute a schema. The HTML used for web pages is actually just a bastardised dialect of XML. End of lesson."

      At a _very_ superficial level, yes. But it's actually a massive over-simplification, missing such aspects as having a standard parser or a standard way to transform it via XSLT and about a dozen other key points. Or that unlike the binary formats it can be read by a human. (Not comfortably, but it can be done.) Or that there are a thousand and one tools that can generate a schema for me from the XML documents, without requiring me to pay a dime to Microsoft. (It won't have all the possible nuances, but it will have all that appear in my documents. That's good enough for me.) Etc.

      And that's exactly why I ask. As long as I know I'll expect <foo>..</foo> constructs, exactly how is my data in peril there. I keep getting being told about some scary bullshit scenarios in which MS owns all my data, and I can't possibly get it ever again from their evil clutches. Well, that's the whole question: exactly how _are_ they going to do that, then? I can just run the whole thing through Xerces and get my data out of there myself.

      "You can expect the problem with Microsoft's format that only Microsoft -- and a chosen few appointed by Microsoft -- are allowed to write programs that can retrieve your data once it has been saved in Microsoft's proprietary format. OpenOffice.org's format is better because any competent programmer can help you to retrieve that data, without being beholden to anyone."

      You mean they can legally prevent Xerces or libxml from parsing that file? Or they can prevent Xalan or libxslt from transforming it? How?

      "Any data that belongs to you rather than to Microsoft."

      It will still belong to me just as much after it's stored in XML. Regardless of whether it's with MS's schema, or Sun's, or my own.

      "That is not the problem. The problem is if, five or ten years down the line, you decide for some reason to move away from Microsoft."

      Yep, I'm listening. That's in fact why I'm asking.

      "Now someone else's document converter may well not be able to handle Microsoft's proprietary format correctly. Your data might become inaccessible!"

      And this is the very thing I'm not convinced of. As long as that data is in XML anyway, _how_ are they going to prevent me from getting at least my text out of it?

      "In five, fifty or a hundred years, any competent programmer will still be able to obtain the schema which will enable them to make sense of an OpenOffice.org document, because no one person or organisation controls that schema. No such guarantee can be made in respect of Microsoft's schema."

      In 5, 50 or 100 years, any competent programmer can still feed the document into XMLSpy and get a good enough schema for it. Heck, even without automated tools for that, if anyone so completely retarded as to look at a plaintext file and not possibly be able to get the data out (even if by copy-and-paste in Notepad, if that's all their IQ allows), they have no business getting paid as a programmer. I know that competence went out of style somewhere during the dot-com boom, but ffs, we're talking elementary logic and/or the ability to google for something that can generate a schema for them. Not even necessarily both. If anyone can tell me with a straight face that the company's data is lost and forever captured by MS when staring at an XML file, I'll say he/she needs to go back to flipping burgers or whatever job they were qualified for before they faked a resume.

      --
      A polar bear is a cartesian bear after a coordinate transform.
  3. Re:And what makes you think that MS won't... by killjoe · · Score: 3, Insightful

    There is no google web office. However there is and has been for many years think free office. Contrary to your prediction it has not been adopted rapidly or widely despite being available over the web and despite being a decent product.

    --
    evil is as evil does
  4. Re:And what makes you think that MS won't... by TarrySingh · · Score: 2, Insightful

    There are more Web Office related tools on the web , indeed BUT it's Google who has the market-say these days and they have to cash on it. Web is the next stop and people ought to get that straight before it's too late.

    --
    Scott McNealy to Michael: "Suck my Sun!" Michael Dell to Scott : "Lick my Dell!"
  5. Re:And what makes you think that MS won't... by TarrySingh · · Score: 2, Insightful
    to reiterate my point.

    People want something new! In the corporate and in their homes. It makes NO sense at all to tell all those word, excel and powerpoint experts that there's yet another Office suite which does JUST THE SAME. Whoaahh, now we're really excited. NOT!!!

    MS Office product has a 90% domination in the World market! And that's a lot. There is no friggin way you can tell the *already tuned people/staff* to start working with a NEW breed of product. It's a challenging option. Lot's of desktop migrations from Windows to Linux see this as a MAJOR challenge.

    --
    Scott McNealy to Michael: "Suck my Sun!" Michael Dell to Scott : "Lick my Dell!"
  6. Re:And what makes you think that MS won't... by Kefaa · · Score: 2, Insightful

    And what makes you think MS won't follow suit

    Because they said so? While that may mean nothing, at this point it is MS' position that they will not support OpenDocument formats, regardless of requirements by governments. MS Not supporting OpenDocument

    Now MS is claiming the open document standard is inferior, yet they sit on the standards committee. Instead they support the MS XML standard which is a standard for MS documents. Which means it owns (under copyright and soon patent), the format and standard.

    Office 12 XML documents will not have an easy introduction into many non-Microsoft products. To do so, you will need to license the format from MS, who has said it sees no reason to support OSS in this regard and the use of MS XML in a GPL'd product would invalidate the GPL, and the MS license. (Microsoft does have some very smart lawyers writing their EULAs and contracts). All the others would need to pay a fee and it is doubtful MS would provide a discount to the disadvantage of their own products.

    A better read on OpenDocument vs. MS XML is found on Wheeler's page

    The format matters because a company, in part due to its responsibility to stockholders, must have planned obsolescence. MS documents from the 80s are difficult to open and read, even in MS products. An open standard ensures that my documents are available to me, through many companies, for a very long time. Governments need this and are now getting smart enough about technology to understand and demand it. And while no one can imagine MS being gone, the same was said of dozens of top 20 companies over the past 20 years.

    As for the comment about the learning curve between open office and MS Office, we can now thank MS. With office 12, they cannot claim an easy transition, the product takes a new direction and whether it is better or not, is irrelevant. The learning curve of going to 12 will be greater than moving to Open Office which retains the current MS office look and feel for the vast majority of users.

  7. Re:Hurry hurry by civilizedINTENSITY · · Score: 2, Insightful

    Outlining that works. Save to PDF. The ability to hand a CD to a friend who needs an office application. LaTeX. The ability to tell the BSA to go to hell when they knock open your door at 4AM. Not having to deal with "You can run this program 50 times until you prove you aren't a thief" popups. Being able to wipe the hard disk and reinstall without being told "you can run this program 50 times until you prove you aren't a thief", again. Being able to add hard drives and RAM and upgrade to your hearts content and never hearing, "This is not the computer I was installed in, you are a thief". The ability to install the software on my other machine without worrying that wiping the first doesn't quite cover the license to install on one machine only.

  8. Re:Forms routing is not that new by civilizedINTENSITY · · Score: 2, Insightful
    I think that the point is supposed to be that the "backend technical details" which are necessary with Sharepoint (which requires you to be an asp.net programmer) aren't necessary with X-Forms creation built into the Office suite. The idea is that it gives everyone and their kid sister the ability to build XForms with a simple drag and drop interface.
    Open Office supports XForms. Not just in a, well if you have an XForms document that you handcrafted especially and spent many many hours on trying to get the damned constraints all working against the complex model scenario type of thing. Oh, no! Open Office lets you design XForms with a handy-dandy toolbar based drag and drop editor, let's you set up multiple models through simple to use dialog boxes, lets you set up XPath constraints with a try it and see type of editor, and even better, let's you add these things directly into a standard Open Office text document - or let's you export it to XHTML. Nice live XForms content, completely XForms 1.0 compatible.