Slashdot Mirror

← Back to Stories (view on slashdot.org)

XML Support In Office 2003 Isn't For Everyone

Posted by ryuzaki0 on from the market-will-bear-a-lot dept.

0x0d0a writes "Unfortunately, it seems that Microsoft's recent campaign to promote Office 2003 based on its XML support may be a bit misleading. Only the Enterprise and Professional releases will have this support -- not Standard. Microsoft will still be leveraging file format compatibility for at least another Office release."

41 of 213 comments (clear)

  1. Chant the mantra, brethren by numbski · · Score: 3, Interesting

    "But analysts contend that WordML's compliance with industry standards is a misnomer. Because the schema isn't fully documented, people who want to edit files created in Office 2003 will only be able to do that with Office itself, as before. Text in Office 2003 files stored in XML format might be viewable in other desktop programs, but all document formatting would be lost and most other files would be unreadable."

    Love thy neighbor. Embrace and extend my brothers.

    Amen.

    --

    Karma: Chameleon (mostly due to the fact that you come and go).

    1. Re:Chant the mantra, brethren by torpor · · Score: 5, Insightful

      Right, like we couldn't have seen this coming from a looong way off.

      I've given up on Office completely. I even try to reject .DOC files completely - thanks to .PDF, it's been mostly successful.

      "Compatability" is still a bitches game.

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    2. Re:Chant the mantra, brethren by Anonymous Coward · · Score: 5, Insightful


      Text in Office 2003 files stored in XML format might be viewable in other desktop programs, but all document formatting would be lost

      Actually, this is entirely the point of XML. XML is not Yet Another Word Processor Format. It's intended to store "content" as opposed to "presentation", leaving "presentation" up to the app, much as was the original intent of HTML. Rather than an evil Microsoft plot, they are in fact conforming to the spec when they produce such a file.

      The semi-trailer truck sized hole in the notion is, of course, that "presentation" isn't really entirely separable from "content", especially in a modern document. All that graphic-artist stuff like layout and font choice and formatting actually affects the value and usefulness of the document. That's why we put it in in the first place. And that's why everyone always whines when Word strips out all the "presentation" they've spent all that effort putting into the document and just leaving them with the raw XML "content" -- a bunch of text.

      The flaw here is in the attempt to erect too high of a wall between presentation and content, not in Word.

      By the time you get fine-grained enough control over the presentation to create documents that actually look the way you want, the "content" usually becomes illegible. Alternatively, you have only coarse control over the presentation, in which case the content most often looks like crap. This problem is easily seen in any number of web pages that feel obliged to include some little rant at the top about bloated HTML and how they concentrate on "pure content", which usually means a sea of unreadable and undiffentiated Times Roman.

      The flip side is if you actually do break up the content enough to get control over the presentation. The last time sometimes tried to create a human-readable ASCII-text format for documents, they wound up with Postscript. A typical document actually looks something like: /Euro.Helvetica
      [556 0 24 -19 541 703 ]

      AddEuroGlyph /Euro /Helvetica /Helvetica-Copy BuildNewFont
      } if
      F /F4 0 /256 T /Helvetica mF /F4S53 F4 [83 0 0 -83 0 0 ] mFS
      F4S53 Ji
      688 1320 M ( )S
      F2S53 Ji
      800 1518 M (802.3z Gigabit Eth)[42 42 42 21 42 36 21 60 23 41 37 42 23 23 21 51 23 0]xS
      1431 1518 M (ernet local)[37 28 41 37 23 21 23 42 37 37 0]xS
      1781 1518 M (-)S
      1809 1518 M (side interface)[32 23 42 37 21 23 41 23 37 29 27 37 37 0]xS
      2255 1518 M ( )S
      F3S53 Ji
      650 1620 M S
      F4S53 Ji
      688 1620 M ( )S
      F2S53 Ji
      800 1620 M (Supports f)[46 41 42 42 42 28 23 32 21 0]xS
      1145 1620 M (ull Gigabit line rate)[41 23 23 21 60 24 41 37 42 23 23 21 23 24 41 37 21 28 37 23 0]xS
      1795 1620 M ( )S
      F3S53 Ji
      650 1722 M S
      F4S53 Ji
      688 1722 M ( )S
      F2S53 Ji
      800 1722 M (Operates in either media convert)[60 42 37 28 37 23 37 32 21 23 41 21 37 23 24 41 37 28 22 63 37 42 23 37 21 37 42 42 42 37 28 0]xS
      1888 1722 M (er)[37 0]xS
      1953 1722 M ( or line)[21 42 28 21 23 23 41 0]xS
      2189 1722 M (-)S
      2216 1722 M (card )[37 37 28 42 0]xS
      800 1817 M (mode)[63 42 42 0]xS

      Here's a hint. The "content" is clearly delimited by parentheses (instead of, oh, "") Easily readable by humans, right? A cinch to import into other applications, right? Guess what: a real XML word processing document that kept the presentation information isn't going to be any more readable. You're not just going to whip out vi and fix it up any more than you can do that to your Postscript documents now.

      XML is not magic application pixie dust that makes all features transparently interoperable when you sprinkle it on.

    3. Re:Chant the mantra, brethren by Erik+Hollensbe · · Score: 4, Informative

      It's great to see someone else gets it. Postscript is actually a language which describes layout -- really, nothing is stopping you from doing all your work in it. Same with TeX. Of course, both languages (and they are true languages) are extremely complex and generally benefit from a middle-ground tool to do the real work (LyX, TeXinfo, Acrobat, Dia (?) etc).

      Treat XML like a database. It has rules of operation, but what you contain and how you describe the data are completely arbitrary.

      That said, if office is really aiming for interoperability, they would publish the XML schema and layout rules. However, as most of us already know, it's just yet another business with the desire to put "XML" on their "Corporate Resume" to make them look more "open".

      Sorry for all the double-quoted words. :)

    4. Re:Chant the mantra, brethren by torpor · · Score: 5, Insightful

      Treat XML like a database. It has rules of operation, but what you contain and how you describe the data are completely arbitrary.

      Anyone who has used XML knows perfectly well that it's entirely possible to describe the complete dataset for content, layout, and presentation, within an XML document, in a form which can be easily parsed by humans and software alike. Completely. Using open standards, even.

      Consequently, it's also possible to wrap it all up in 'parseable', yet 'unhandleable-unless-you're-on-the-inside' data blobs which mean nothing to no-one, yet still use 'XML' as a wrapper.

      It's a liability of having such an open design, and Microsoft are exploiting this fact, in the context of *CLEAR* market-division tactics.

      *They* created the artificial 'Professional/Enterprise/Standard' labels. Not the Users.

      MS' use of XML here is perverted. It serves no purpose other than to give MS an opportunity to blag press release points about how their software uses 'the latest open standards' to people who have *NO CLUE* what they're talking about ...

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    5. Re:Chant the mantra, brethren by nightcrawler77 · · Score: 3, Informative

      I disagree.

      Of course, opening the XML file in another application would ignore formatting...just like opening a .DOC file in a hex or text editor would ignore formatting.

      The issue here is the documentation of the formatting-related tags. Take the two following XML 1.0 fragments:

      1:

      <content>Hello! This text is <style add="italic">different</style>.</content>

      2:

      <content>Hello! This text is <msft secretFormattingCode="0x3B">different</msft>.</con tent>

      Both are XML, both would "lose" formatting when opened in another editor, and both are probably just as easy for Office to generate. The problem is, in the absence of a published schema, the second one is much harder to understand.

      MS certainly knows that their XML format will be "reverse-engineered", so I would assume they are going to make it as hard as possible to understand.

      Of course, I haven't seen the actual XML format used by Office 2003, but I have to assume that if there were a nice, easy to userstand XML dialect in use, we wouldn't have all of this commotion to begin with.

      --

      "Power corrupts, and absolute power corrupts absolutely." -- Lord Acton

  2. Propoganda by ahkbarr · · Score: 4, Funny

    This is not reliable source! This is US led propoganda campaign!

    Seriously, though, who here could not have predicted this?

    --
    Compared to war, all other forms of human endeavor shrink to insignificance. God, how I love it. - Gen. George Patton
    1. Re:Propoganda by superyooser · · Score: 5, Funny
      Mohammed Saeed al-Sahaf, Iraqi Minister of Information:
      "I triple guarantee you, there are no American soldiers in Baghdad."

      Mohsen Khalil, Iraqi Ambassador to the Arab League:
      "Iraq will not be defeated. Iraq has now already achieved victory - apart from some technicalities."

      Jean Paoli, Microsoft's XML architect:
      "I'm out of the business of creating formats. Our focus on Office is on data exchange. There is no more difference between documents and data."

      ... apart from some.. err umm "technicalities"?

  3. Not to snipe here... by MrLint · · Score: 3, Insightful

    Of course sniping is way to eay here.. so i will,

    For the love of B0B how hard is it to deploythe feature across the entire suite. What can we conclude here?

    1) Its not really ready and the high end versions will ship later.
    OR
    2) its a cheap ploy to rake in more money later on.

    *sigh*

  4. XML Support In Office 2003 Isn't For Everyone... by Anonymous Coward · · Score: 5, Informative

    but XML support in OpenOffice is.

    ------------
    This is guarenteed to not be the first post.

  5. In other fast breaking news.... by ralphart · · Score: 5, Funny

    The sun rose this morning; sunset predicted for later today!

  6. Schools? by shibbydude · · Score: 5, Insightful
    I really like the idea of human-readable code, but who really wants to lose backward compatability with all the rest of the versions? At my highschool, there are about five versions of Office, all which save in different formats. Most people save as rich text just for compatability, because even the small releases or updates do not save in a compatible format for the older releases. If we introduce a format which is absolutely not readable by older versions, it will not only baffle our techies for months, but I know productivity will take a hit when students *accidentally* save in the wrong format and then cannot open it for the life of them.

    This is one reason I use openoffice (openoffice.org at home as it supports most word versions flawlessly, without promting me to "insert office cd 2" to install the feature.

    --
    We're only gonna die from our own arrogance, that's why we might as well take our time...
  7. On file formats by bogie · · Score: 4, Insightful

    The entire business world is still being held hostage or pushed around by a proprietary file format. How sad, annoying, and wasteful.

    I always said during the DOJ trial all I wanted was to have the Office file formats opened. That would have really lead to some change.

    Btw in case your new here, try OpenOffice you might like it.

    www.openoffice.org

    --
    If you wanna get rich, you know that payback is a bitch
  8. Office 2003 Beta by bamberg29 · · Score: 3, Funny

    I've been using Office 2003 Beta 2 for about a month now and the XML support seems fairly poor. I've saved some of my Word documents in XML format and tried opening them in some other XML supported programs , but had a hard time opening them. I guess MS needs to work some more on the XML support in Office.

    David

    1. Re:Office 2003 Beta by sciwhiz007 · · Score: 5, Insightful

      We have to remember that this is Microsoft we are talking about here. Any time they say "we are going to switch to an open format", there's always a catch to it.

      Is Microsoft ever going to switch to an open format? No, why would they? They will only lose money. As for the people complaining about competition, why should a company with 90 - 95% of the desktop Office suite market care?

      People with little or no knowledge about what Microsoft has done in the past might think that Microsoft is taking a great step forward. But remember, this isn't going to be complete XML, it is "Microsoft XML"

      All this about Microsoft doing a great thing by switching to an "Open XML base" is all hype, nothing more.

      --
      Read my journal here.
  9. In related news ... by DogIsMyCoprocessor · · Score: 5, Funny

    Microsoft announced that only the Enterprise and Professional versions of Office 2003 would support the feature of saving files to industry-standard media such as IDE and SCSI hard disks. The Standard version of Office 2003 will allow the user to save document files only to Microsoft Zippo (TM), a new proprietary USB-based external removable media device. "We believe this is an innovative way to provide extra value to our customers." said Microsoft spokesman Hugh Jass.

    --

    "And this is my boy, Sherman. Speak, Sherman." "Hello." "Good boy."

  10. And when... by Black+Parrot · · Score: 4, Insightful


    If they ever do make it general they'll encumber the components with so many patents and copyrights that it will be a proprietary format in spite of being XML based.

    The people running Microsoft might not be "nice", but they certainly aren't stupid. Moving to an open file format would immediately saw one of the legs out from under their monopoly. Expect them instead to vaporize the file format issue and drag it out as long as possible, so that people and companies tempted to switch to a WP with an open format will think they can get the open formats without switching, if only they wait a little longer and pay for a few more upgrades.

    --
    Sheesh, evil *and* a jerk. -- Jade
  11. Oh Come On by Snowspinner · · Score: 3, Funny

    The reason you don't have all versions of Office be identical is that then you wouldn't need different versions. The Standard versions of programs contain fewer features than the Professional and other shiny versions. This is to help justify charging more for the professional versions. This is not unreasonable. As with much of capitalism, paying more gets you more. Jesus, some days I think MS could liquidate and give all their money to the EFF and still get flamed by you people.

    --
    Philip Sandifer's academic website
  12. Now the big question.... by neurostar · · Score: 5, Funny

    Swimming with a very big shark is always guaranteed to be interesting, not necessarily good or bad. This is just throwing a few drops of blood in the water to spice things up.

    ...do penguins eat sharks?

  13. I'm cringing again: XML != anyone can read it by Trailer+Trash · · Score: 5, Insightful

    Microsoft will still be leveraging file format compatibility for at least another Office release.

    Here we go again. "If Microsoft would just use an open format like XML then anyone could read the documents with any program and the world would be a better place."

    XML is a format for creating data formats. It is not a data format. The fact that a particular format is XML compliant says nothing for its readability, it simply means that it can be parsed into a document tree by an XML parser. That doesn't mean that anybody can determine what the tree represents, only that it can be created. My favorite analogy: "If Microsoft would just start using 8-bit bytes, then anybody could read their file formats."

    Microsoft has made it clear that the dollar value of secret file formats isn't lost on them. They will continue to use secret file formats, even if they're XML-based, until someone makes them stop. At the same time, they'll be able to harvest the stupidity of PHB's who will claim that Microsoft file formats are open because they're XML. It's surprising how many people on Slashdot foolishly believe the same.

    Michael

    --
    Do you have ESP?
    1. Re:I'm cringing again: XML != anyone can read it by jkarlin · · Score: 5, Interesting

      Excellent points. I'm using the Beta of Office 2003 Pro and I just saved 'Hello World' as an Office XML file. Thought it would be nice to actually see what we're talking about.

      <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
      <?mso-application progid="Word.Document"?>
      <w:wordDocument xmlns:w="http://schemas.microsoft.com/office/word/ 2003/2/wordml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:w10="urn:schemas-microsoft-com:office:word" xmlns:SL="http://schemas.microsoft.com/schemaLibra ry/2003/2/core" xmlns:aml="http://schemas.microsoft.com/aml/2001/c ore" xmlns:wx="http://schemas.microsoft.com/office/word /2003/2/auxHint" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C1488 2" xml:space="preserve"><o:DocumentProperties><o:Titl e>Hello World</o:Title><o:Author>Jason Karlin</o:Author><o:LastAuthor>Jason Karlin</o:LastAuthor><o:Revision>1</o:Revision><o: TotalTime>0</o:TotalTime><o:Created>2003-04-13T23: 29:00Z</o:Created><o:LastSaved>2003-04-13T23:29:00 Z</o:LastSaved><o:Pages>1</o:Pages><o:Words>1</o:W ords><o:Characters>11</o:Characters><o:Lines>1</o: Lines><o:Paragraphs>1</o:Paragraphs><o:CharactersW ithSpaces>11</o:CharactersWithSpaces><o:Version>11 .4920</o:Version></o:DocumentProperties><w:fonts>< w:defaultFonts w:ascii="Times New Roman" w:fareast="Times New Roman" w:h-ansi="Times New Roman" w:cs="Times New Roman"/><w:font w:name="Tahoma"><w:panose-1 w:val="020B0604030504040204"/><w:charset w:val="00"/><w:family w:val="Swiss"/><w:pitch w:val="variable"/><w:sig w:usb-0="21007A87" w:usb-1="80000000" w:usb-2="00000008" w:usb-3="00000000" w:csb-0="000101FF" w:csb-1="00000000"/></w:font></w:fonts><w:styles>< w:versionOfBuiltInStylenames w:val="3"/><w:latentStyles w:defLockedState="off" w:latentStyleCount="156"/><w:style w:type="paragraph" w:default="on" w:styleId="Normal"><w:name w:val="Normal"/><w:rPr><wx:font wx:val="Times New Roman"/><w:sz w:val="24"/><w:sz-cs w:val="24"/><w:lang w:val="EN-US" w:fareast="EN-US" w:bidi="AR-SA"/></w:rPr></w:style><w:styl e w:type="character" w:default="on" w:styleId="DefaultParagraphFont"><w:name w:val="Default Paragraph Font"/><w:semiHidden/></w:style><w:sty le w:type="table" w:default="on" w:styleId="TableNormal"><w:name w:val="Normal Table"/><wx:uiName wx:val="Table Normal"/><w:semiHidden/><w:rPr><wx:fon t wx:val="Times New Roman"/></w:rPr><w:tblPr><w:tblI nd w:w="0" w:type="dxa"/><w:tblCellMar><w:top w:w="0" w:type="dxa"/><w:left w:w="108" w:type="dxa"/><w:bottom w:w="0" w:type="dxa"/><w:right w:w="108" w:type="dxa"/></w:tblCellMar></w:tblPr></w:style>< w:style w:type="list" w:default="on" w:styleId="NoList"><w:name w:val="No List"/><w:semiHidden/></w:style><w:sty le w:type="paragraph" w:styleId="BalloonText"><w:name w:val="Balloon Text"/><w:basedOn w:val="Normal"/><w:semiHidden/><w:rsid w:val="4E5A63"/><w:pPr><w:pStyle w:val="BalloonText"/></w:pPr><w:rPr><w:rFont s w:ascii="Tahoma" w:h-ansi="Tahoma" w:cs="Tahoma"/><wx:font wx:val="Tahoma"/><w:sz w:val="16"/><w:sz-cs w:val="16"/></w:rPr></w:style></w:styles><w:docPr> <w:view w:val="print"/><w:zoom w:percent="100"/><w:doNotEm

      --
      Things fall down...People look up... And when it rains, it pours.
  14. Not quite as clear cut as it seems... by ignatz · · Score: 3, Informative

    This is the user schema support we're talking about here - which allows users to build Word templates from XML schema and then use them to save schema-compliant XML from documents. This is only being included in the professional and enterprise SKUs, not the home and SME SKUs.

    User schema aren't really suitable for home and SME users - it's the sort of thing you need if you're dumping XML output into enterprise applications, and want your data entry folk to use their usual Office applications.

    For XML transfer WordML is still supported in all SKUs, which is defined by a schema at a specific URI, so it will validate in most parsers.

    What will be much more interesting will be uderstanding the pricing for InfoPath...

  15. Some alternatives by stonebeat.org · · Score: 5, Informative

    I m not counting on MS Office Suite to provide me with a XML editor. Here are some alternatives:
    DocSoft's W2XML Version 2
    Authentic by Altova
    i4i Tagless Editor
    XMLWriter by Wattle Software
    Opensource Extensible XML Modeling Application

    If you know of any other GUI based XML modeling/editing apps, please feel free to add them to this list.

    --


    Consensus is good, but informed dictatorship is better
  16. First rule of running a software business by littleRedFriend · · Score: 4, Funny



    Develop once, sell many times...

    --
    IANAL, but imagine a beowulf cluster of in Soviet Russia all your belong are base to us welcoming the new SCO overlords.
  17. Re:XML Support In Office 2003 Isn't For Everyone.. by the+uNF+cola · · Score: 4, Insightful

    It makes sense actually for usefullness.

    If you xlink to another XML document or some binary data, then you need the "other document". If you need the dtd, or stylesheet information, you need the other document as well.

    Zipping one XML document only has space saving as its only advantage. But for many, ensuring they are in the same place ensures you dont' get errors interpretting them and their required children/siblings/parents.

    --

    --
    "I'm not bright. Big words confuse me. But Wanda loves me and that should be enough for you." - Cosmo

  18. Open Office by Anonymous Coward · · Score: 5, Informative

    This is as good-a-time as any to migrate away from Microsoft Office. Open Office 1.1 is about to come out and it looks brilliant!! (the beta is currently available at http://www.openoffice.org/ ) It supports open standards (eg. XML), Microsoft Documents (word/excel/powerpoint) and exports to PDF (both text and graphics) at the press of a button! It also manages to count page numbers correctly when printing (* cough - word, cough *).

    On the other hand, my wife prefers Word and I prefer Open Office. The only time she likes open office is when she asks me to convert a document from one word format to another - because word won't do it at all, or word converts it very badly.

    Also, I save several hundred dollars every few years :)

    AC

  19. 2 xml or not 2 xml, that is the question ... by 2TecTom · · Score: 5, Funny

    lemme see ...

    there's MS Java, then there's the other version
    there's MS HTML, then there's the other version
    there's MS VC++, then there's the other version
    there's MS OS's then there's the other OS ...

    same ol same ol ... see Bill, see Bill emulate.

    Nope, nuthin new here folks, move along ... ;)

    --
    Words to men, as air to birds.
  20. What does that mean? by wouterke · · Score: 5, Insightful

    Even if XML was supported in all versions of Office, would that mean that Office would suddenly have an open file format? I don't think so. It's perfectly possible for me to write anything in XML in a way that you will not be able to read it.

    Which is normal. XML is a way to describe data. If you have the DocType Definition (DTD) of an XML file, the only thing you know is whether that XML file is structured correctly, and how you would create another XML file that would look like the same thing for an XML parser. Nothing more.

    In the long run, XML is nothing more than a standard you can use to base other standards on. XML can be put in the same row as ASCII, bytes, the file concept, or even SGML: it's a standard intended for the creation of other standards.

    Nothing more, nothing less

    Therefore, I think the argument that Microsoft Office will 'support XML' is just a marketing joke. It won't do anything out of the ordinary...

  21. Re:I think it would be better by gilroy · · Score: 3, Insightful
    Blockquoth the poster:

    as your employees struggle to get even rudimentary things like printing working,

    Hmmm. About once a week, Windows 2000 Server randomly reassigns my default printer. About once every three weeks, Windows XP suddenly fails to see my USB printer unless I reboot -- no explanation, no change in configuration.


    If Microsoft products -- which, as everyone likes to point out, run almost all machines -- is so wonderful, and if their software is so easy and useful for the ordinary joe, then why oh why after ten years of outright dominance do people still hate and fear computers?


    The only "innovation" Microsoft has developed is its ability to convince regular users that (a) the complexities and difficulties of, say, Linux, result from the innate design (and a flawed one at that), but (b) any complications or errors encountered using Windows must be the fault of the user.

    --
    The Mongrel Dogs Who Teach
  22. XML just a feature, not a change in file format by cyberformer · · Score: 4, Insightful

    Microsoft will still be leveraging file format compatibility for at least another Office release.

    They'll do this as long as they have a monopoly (or near-monopoly). The XML support isn't about making file formats compatible with competitors, or even about pretending to. It's just one more feature that MS has added to Office, in an attempt to persuade existing users to upgrade. It means that Office can be used to edit XML documents. It doesn't mean that Office's proprietary file formats are disappearing.

    XML editing is a useful feature for some people, and from what I've heard it works better than the horrible HTML support in previous versions of Office, but it's still a niche. (True, it can be used to help with cross-platform compatability, but so can RTF and other existing "save as" options.) Most users just want to write a letter or design a presentation, and aren't concerned with markup languages.

  23. Re:I think it would be better by syrinx · · Score: 3, Insightful

    What *are* you on about? I've had far more trouble printing in Windows than in FreeBSD. And OpenOffice has nothing to do with printing, and since this article is about Office, things like printing (and KDE and Linux, for that matter) are not really the point.

    Have you actually tried the things you disparage, or do you just listen to FUD?

    --
    Quidquid latine dictum sit, altum sonatur.
  24. New Microsoft Position by Bob9113 · · Score: 4, Funny

    Microsoft's Leach emphasized that this change in positioning doesn't negate that "customer-defined XML schema support is a feature of Pro." On the other hand...

    Cool, they've actually appointed a corporate leach. Perhaps that explains why MS Office came out with XML support after it was released in OpenOffice.

    --
    Stop-Prism.org: Opt Out of Surveillance
  25. Re:Rubbish! by MrWa · · Score: 4, Insightful
    It's just not true. XML is *NOT* 'just' a presentation format, a la HTML (nice smear), nor is it 'inevitable' that the fileformat ends up like Postscript.

    So wait a second - the original post stated that XML is ALL about the content and specifically NOT the presentation. Now you are saying that XML is apparently *self documenting* and the USER decides how the content should be displayed.

    So, according to your post, Microsoft is correct when their XML file output includes the *content* and the *user* can display it however they want.

  26. Re:Rubbish! by torpor · · Score: 3, Insightful

    No, what I'm saying is that there's no reason for Microsoft to not have used the parseability features of XML to make their document formats more open - to do so would have fulfilled the actual purpose of XML.

    These other posts are out of field. XML can be used to store content, as well as all significant details about how that content should be displayed/portrayed to the user in various scenarios, in a way in which the details can be easily parsed - both by software and by human.

    XML is an attempt to prolong the longevity of data, forever. The thinking goes that if the data is described in a meta-language (which can also be described), it's easier to - many, many years into the future - parse the details from those documents and render them appropriately.

    Microsoft aren't doing it. They're just wrapping up the users data in incomprehensible data formats, within XML, and then 'playing the Open Standards' card...

    There's no justification for not including presentation details - content and layout - within the context of XML. It's perfectly applicable in this regard, parent posts notwithstanding...

    --
    ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
  27. I love this quote... by 26199 · · Score: 3, Funny

    "By only having this in the Pro version, customers who don't want this aren't paying for it."

    I wonder how much more Microsoft would be forced to charge for Office with XML support? It's truly good of them to try and save us money this way...

  28. Maybe next year... by b3h · · Score: 3, Interesting

    This is what happens when you have complete market control. Why innovate when you can duplicate and still rake in hundreds of dollars per copy of the same suite you released last year?
    OpenOffice, the world needs you!

  29. Re:Rubbish! by tinrib · · Score: 5, Informative

    XML is a text-based system for data storage and retrieval, intended to be *self documenting*. In other words, the details on what fonts are used, what settings The User has set for individual parts of the documents, the parameters for those setting, etc. ARE ALL SUPPOSED TO BE STORED IN READABLE FORMAT WITHIN XML TAGS, CONFORMING TO A KNOWN, PUBLISHED DOCUMENT DESCRIBING THE CONTENT.

    No it's not. XML is not supposed to store information such as 'font' and other presentational features. This is the job of the XSL stylesheets or CSS etc. XML is designed to store data in a structured way. So for instance you may have a <chapter> tag, but what font to use for chapter tags is only supposed to be specified in the XSLT. If I did an XML export of my word document, I would expect (hope for) an XML document, and either an XSLT stylesheet transforming the XML to HTML, or an XSL:FO stylesheet so that I can turn the XML into a pdf or postscript file. However, the stylesheets would be the 'icing on the cake'. The essential item is the XML formatted data, not the presentational information.

  30. True, true... by Chordonblue · · Score: 3, Informative

    "This just isn't true."

    The hell it isn't. Ever try to open an older works document in 'X' version of MS Office?

    How about support of international versions? Can a Japanese student use their version of Office 97 to write an English document, printable in our labs? Dunno. Sometimes.

    How about opening say, a Word 97/2000/XP doc in Office 95? Oh, right, that doesn't work either.

    Schools aren't like your average corporation. We can't always afford to go out and get the latest and greatest. I also have to question WHY we'd even bother doing so and I wish our public schools would seriously consider this question as well - our tax dollars can be better spent. To be honest, Office 97 was all we ever really needed functionality-wise.

    Then there's what happens when a student goes home and works on a paper. Who knows WHAT format it'll come back in. The biggest problem for us has been when an upgrade cycle comes around and some of my students (or parents) end up with it (came with their brand new PC).

    Last year I posed a question to the teachers: Why not use Open/StarOffice? This has (for the most part), solved our compatibility issues. As I work for an international school, we have students with every version of MS Office, Works, Wordperfect, hell, even NOTEPAD!

    Standardizing everyone (teachers, parents, students) on OpenOffice.org was the smartest thing we've ever done. Document compatibility was major factor in that decision.

    --
    "...Well, there's egg and bacon; egg sausage and bacon; egg and spam; egg bacon and spam; egg bacon sausage and spam..."
  31. Re:OMG....! by Larthallor · · Score: 3, Funny

    Insist they call it GNU/Microsoft Rights Management Services, of course.

    What? You didn't see that coming? :)

  32. XML in Word 2003 is actually pretty good by unfortunateson · · Score: 3, Informative

    I haven't looked at the XML generated by saving 'normal' docs to XML, but I'm rather impressed by Word's ability to edit XML.

    You need a schema, which is a bit of a pain, but it's at least as friendly as most of the XML editors out there. Plus you can embed all the 'normal' Word formatting content where any CDATA would go.

    I'd like to see a better UI for entering attributes rather than having to right-click the tag -- there's this handy-dandy task pane on the right, why not default to attribute entry there?

    The live validation is pretty good, the pick-and-choose entities is just fine. The best part, is that the XML is accessible from VBA, .Net, and anything else that can talk COM/OLE.

    I'm starting to look into their "SmartDocs" SDK, where you can have behaviors appear in that task pane (probably can do the attribute editing there), based on the XML tags. It's an extension of their SmartTag interface, and not the most straightforward interface I've ever seen, because the tag is just a parameter to a generic call, but I think I can make it work.

    I'm less impressed with their XML form editor Infowhatever -- it appears to be limited to usability with certain kinds of schemas (and never DTDs, it seems), more database-like, less document-like. If its forms could be embedded ito Word, it would be even nicer.

    FYI, the DTD I'm working with is the International Council of Harmonization's Electronic Common Technical Document, which is not a document, but the table of contents for submissions of data to the Food and Drug Administration and regulatory agencies worldwide (Ok, only Europe and Japan, with Canada and Australia and others riding the coattails).

    --
    Design for Use, not Construction!
  33. OO output by IamTheRealMike · · Score: 4, Interesting

    For comparison, here is the equivalent (empty) document in OpenOffice.

    content.xml:

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE office:document-content PUBLIC "-//OpenOffice.org//DTD OfficeDocument 1.0//EN" "office.dtd">
    <office:document-content xmlns:office="http://openoffice.org/2000/office" xmlns:style="http://openoffice.org/2000/style" xmlns:text="http://openoffice.org/2000/text" xmlns:table="http://openoffice.org/2000/table" xmlns:draw="http://openoffice.org/2000/drawing" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:number="http://openoffice.org/2000/datastyle " xmlns:svg="http://www.w3.org/2000/svg" xmlns:chart="http://openoffice.org/2000/chart" xmlns:dr3d="http://openoffice.org/2000/dr3d" xmlns:math="http://www.w3.org/1998/Math/MathML" xmlns:form="http://openoffice.org/2000/form" xmlns:script="http://openoffice.org/2000/script" office:class="text" office:version="1.0">
    <office:script/>
    <office:font-decls>
    <style:font-decl style:name="Arial Unicode MS" fo:font-family="'Arial Unicode MS'" style:font-pitch="variable"/>
    <style:font-decl style:name="HG Mincho Light J" fo:font-family="'HG Mincho Light J'" style:font-pitch="variable"/>
    <style:font-decl style:name="Nimbus Roman No9 L" fo:font-family="'Nimbus Roman No9 L'" style:font-family-generic="roman" style:font-pitch="variable"/>
    </office:font-decls>
    <office:automatic-styles/>
    <office:body>
    <text:sequence-decls>
    <text:sequence-decl text:display-outline-level="0" text:name="Illustration"/>
    <text:sequence-decl text:display-outline-level="0" text:name="Table"/>
    <text:sequence-decl text:display-outline-level="0" text:name="Text"/>
    <text:sequence-decl text:display-outline-level="0" text:name="Drawing"/>
    </text:sequence-decls>
    <text:p text:style-name="Standard"/>
    </office:body>
    </office:document-content>

    meta.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE office:document-meta PUBLIC "-//OpenOffice.org//DTD OfficeDocument 1.0//EN" "office.dtd"><office:document-meta xmlns:office="http://openoffice.org/2000/office" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:meta="http://openoffice.org/2000/meta" office:version="1.0"><office:meta><meta:generator> OpenOffice.org 1.0.1 (Linux)</meta:generator><!--SRC641_[7663]_LINUX_IN TEL__stripples.devel.redhat.com_at_9/10/02_8:50:05 --><meta:creation-date>2003-04-14T09:09:00</meta:c reation-date><dc:language>en-GB</dc:language><meta :editing-cycles>1</meta:editing-cycles><meta:editi ng-duration>PT0S</meta:editing-duration><meta:user -defined meta:name="Info 1"/><meta:user-defined meta:name="Info 2"/><meta:user-defined meta:name="Info 3"/><meta:user-defined meta:name="Info 4"/><meta:document-statistic meta:table-count="0" meta:image-count="0" meta:object-count="0" meta:page-count="1" meta:paragraph-count="1" meta:word-count="0" meta:character-count="0"/></office:meta></office:d ocument-meta>

    That is only 2 out of the 4 or 5 files openoffice saves. Oh, and for all those who made sucky Base64 jokes about MS WordML, take a look at this:

    <config:config-item config:name="PrinterSetup" config:type="base64Binary">ugL+/0dlbmVyaWMgUHJpbnR lcgAAAA
    AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAA
    AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAU0 dFTlBSVAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAWAAMAAAIAAAAA