Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Microsoft Programming IT Technology

Microsoft Word Document ML Schemas Published 439

Lars Munch writes "On Monday the 17th November the xml schemas for the Word Document ML along with documentation, was uploaded to the Infostructurebase (ISB). With the Word Document ML specification anybody can generate, view and process Microsoft word documents on any format." (Here are the legal terms under which the schemas can be used.) "The Word Document ML is based on the W3C specification eXtensible Markup Language (XML), there by providing documents that are easy to integrate into a large variety of systems. The Danish Government Infostructurebase is the first schema repository to make the schemas accessible to the public. The Microsoft Office Document ML schemas and documentation can now be downloaded from the ISB Repository." There are more links on this page.
This discussion has been archived. No new comments can be posted.

Microsoft Word Document ML Schemas Published

Comments Filter:
  • by tcopeland ( 32225 ) * <tom@@@thomasleecopeland...com> on Monday November 17, 2003 @12:18PM (#7493324) Homepage
    ....seems like all you have to do is put a notice in the code [microsoft.com] about using the spec. Sounds kind of like the original BSD license - i.e., with the advertising clause.
  • legal terms (Score:3, Informative)

    by Anonymous Coward on Monday November 17, 2003 @12:24PM (#7493388)
    Legal Notice

    Permission to copy, display and distribute the contents of this document (the "Specification"), in any medium for any purpose without fee or royalty is hereby granted, provided that you include the following notice on ALL copies of the Specification, or portions thereof, that you make:

    Copyright (C) Microsoft Corporation. All rights reserved. Permission to copy, display and distribute this document is available at: [here] [microsoft.com].

    No right to create modifications or derivatives of this Specification is granted herein.

    There is a separate patent license available to parties interested in implementing software programs that can read and write files that conform to the Specification. This patent license is available at this location: [here] [microsoft.com].

    THE SPECIFICATION IS PROVIDED "AS IS" [blah blah blah]

    The name and trademarks of Microsoft may NOT be used in any manner, including advertising or publicity pertaining to the Specification or its contents without specific, written prior permission. Title to copyright in the Specification will at all times remain with Microsoft.

    No other rights are granted by implication, estoppel or otherwise.

    following that second link...

    Patent License

    Microsoft may have patents and/or patent applications that are necessary for you to license in order to make, sell, or distribute software programs that read or write files that comply with the Microsoft specifications for the Office Schemas.

    Except as provided below, Microsoft hereby grants you a royalty-free license under Microsoft's Necessary Claims to make, use, sell, offer to sell, import, and otherwise distribute Licensed Implementations solely for the purpose of reading and writing files that comply with the Microsoft specifications for the Office Schemas. A "Licensed Implementation" means only those specific portions of a software product that read and writes files that are fully compliant with the specifications for the Office Schemas. The term "Necessary Claims" means claims of a patent or patent application that are owned or controlled by Microsoft and that are necessarily infringed by reading or writing files pursuant to the requirements of the Office Schemas. A claim is necessarily infringed only when it is not possible to avoid infringing when conforming to the specification because there is no technically reasonable non-infringing alternative for reading or writing such files. Notwithstanding the foregoing, "Necessary Claims" do not include any claims: (i) that would require a payment of royalties by Microsoft to unaffiliated third parties; (ii) covering any enabling technologies that may be necessary to make or use any product incorporating a Licensed Implementation (e.g., word processing, spreadsheet or presentation features or functionality, programming interfaces, protocols), or (iii) covering the reading or writing of files generally or covering the reading or writing of files other than those complying with the requirements of the specifications for the Office Schemas.

    If you distribute, license or sell a Licensed Implementation, this license is conditioned upon you requiring that the following notice be prominently displayed in all copies and derivative works of your source code and in copies of the documentation and licenses associated with your Licensed Implementation:

    "This product may incorporate intellectual property owned by Microsoft Corporation. The terms and conditions upon which Microsoft is licensing such intellectual property may be found at http://msdn.microsoft.com/library/en-us/odcXMLRef/ html/odcXMLRefLegalNotice.asp?frame=true."

    By including the above notice in a Licensed Implementation, you will be deemed to have accepted the terms and conditions of this license. You are not licensed to distr
  • Comment removed (Score:4, Informative)

    by account_deleted ( 4530225 ) on Monday November 17, 2003 @12:25PM (#7493398)
    Comment removed based on user account deletion
  • by terraformer ( 617565 ) <tpb@pervici.com> on Monday November 17, 2003 @12:25PM (#7493399) Journal
    I believe you are refering to the security DRM that they were placing on documents. AFAIK that is an optional feature that your friends would have to enable. The likelihood of your friends using that feature is small. It is more for big co's and other folk wanting to limit leaks of documents. ie; those with something to hide...

    Now do you or your friends have anything to hide...
    ;-)

  • Re:Hmph (Score:1, Informative)

    by Anonymous Coward on Monday November 17, 2003 @12:27PM (#7493423)
    The reason it's in all caps is because in a lot of states in the US, warranty disclaimers by law need to be emphasized in contrast to the rest of the text in a license or contract or whatever. Their lawyers are just doing their job. Leaving aside what you may think of Microsoft's lawyers and the use of lawyers generally, they are pretty thorough -- I've dealt with them a couple times now.

    And yes, IAL.
  • Re:Not so fast (Score:5, Informative)

    by Chokolad ( 35911 ) on Monday November 17, 2003 @12:28PM (#7493434)
    > Wait a second ... I think the XML-format document types are only available for corporate versions of MS office. If that is true there still will be a lot of propiertary binary-only .DOCuments around in the future.

    You are wrong. Word Standard Edition can save into WordML (which schema has been published). Enterprise version allows you to map certain parts of documents into Xml with customer specified schema.
  • by David Jao ( 2759 ) * <djao@dominia.org> on Monday November 17, 2003 @12:29PM (#7493442) Homepage
    GPL 7 requires the right to sublicence patent rights to the people who obtain a GPL program from you.

    Not true. Section 7 of the GPL requires that patent rights be publicly available, but it does not require that you personally sublicense those patent rights.

    Specifically, GPL section 7 says:

    ... if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
    Since the Microsoft patent license does permit royalty-free redistribution, it does not contradict the GPL in this regard (although it may have other incompatibilities; I have not looked at the whole thing thoroughly yet).
  • by narrowhouse ( 1949 ) on Monday November 17, 2003 @12:33PM (#7493483) Homepage
    From the Legal info link.
    "There is a separate patent license available to parties interested in implementing software programs that can read and write files that conform to the Specification. This patent license is available at this location: http://www.microsoft.com/mscorp/ip/format/xmlpaten tlicense.asp."
    (And just for giggles that link is no good)
    An "Open" XML schema that needs a patent license to write software that can read or write it is rapidly approaching the speed of useless. So if you had a plan to start work on an Openoffice filter find out what that patent license entails.
  • by KagakuNinja ( 236659 ) on Monday November 17, 2003 @12:40PM (#7493542)
    Word will now allow anyone to create XML Schemas and "Solutions" (groups of schemae)...

    Just thought you would like to know, the plural of schema is schemata.

    Mr. Language Person
  • by evanbd ( 210358 ) on Monday November 17, 2003 @12:44PM (#7493574)
    The intent of the GPL is to guarantee that if I give you a program under a GPL license, then no one can take away your freedoms as regards that program. Microsoft's intent here is to license the patents in such a way that they can revoke the license if desired. These goals are rather incompatible. Whether that makes it MS's fault... that's up to you. Personally, it doesn't surprise me; I think it's bad, I think it's an abuse of the patent system, and I think it is exactly in keeping with the habits of MS and much of other big business of late.
  • by Utopia ( 149375 ) on Monday November 17, 2003 @12:49PM (#7493617)
    Use a newer version of Textpad.

    The new version of Textpad can read UTF-8 encoded files. The old version can only read Latin 1 character set.

  • I call bullshit (Score:5, Informative)

    by jrumney ( 197329 ) on Monday November 17, 2003 @01:12PM (#7493813)
    This schema is patented.

    Microsoft knows full well that an XML schema cannot be patented. The patent nonsense is a way to scare off open source developers. They may hold patents on some algorithms they've used to implement this in MS Office, but we don't have to use those same algorithms to read those documents with an XML schema capable parser and do whatever we like with them.

  • by dabadab ( 126782 ) on Monday November 17, 2003 @01:16PM (#7493850)
    Don't forget that in the EU patents can not be abused in this, since the nice people from FFII and others got through an amendment that you are free to use patented technologies for interoperability - and I can't really imagine any other uses for a fileformat besides of interoperability.
  • by Anonymous Coward on Monday November 17, 2003 @01:34PM (#7494017)
    I've done some investigating and discovered that
    editdata.mso is "activemime" format (nice, that).
    If you base64 decode it, you get something with
    a 50 byte header (sometimes it's 54 bytes; not sure why).
    The first part of this header is the string "ActiveMime".
    Following the header is a zip-deflated OLE stream; zlib can handle it. Open-source
    code for reading these OLE streams exists.
    But believe me, this is *not* actually documented anywhere...
  • by thebatlab ( 468898 ) on Monday November 17, 2003 @01:39PM (#7494065)
    Did you read the licence?

    From: http://www.microsoft.com/mscorp/ip/format/xmlpaten tlicense.asp [microsoft.com]

    "Except as provided below, Microsoft hereby grants you a royalty-free license under Microsoft's Necessary Claims to make, use, sell, offer to sell, import, and otherwise distribute Licensed Implementations solely for the purpose of reading and writing files that comply with the Microsoft specifications for the Office Schemas."

    Maybe you were just trying for a quick mod up for being anti-MS. Maybe I missed something in what you're trying to say.
  • by superyooser ( 100462 ) on Monday November 17, 2003 @01:45PM (#7494107) Homepage Journal
    Slight clarification: Only the Pro edition can create XML Office documents, but any edition of Office 2003 can read them.
  • by ciaran_o_riordan ( 662132 ) on Monday November 17, 2003 @02:08PM (#7494373) Homepage
    First, remember that file formats in general are patentable. The ASF video format is one example.

    Some might say: "But that's a binary format."

    Doesn't matter. Microsofts Office-xml format has plenty of binary data. They uuencode it so that it's official XML, but it's still encrypted or command content, not cleartext.

    What if Microsoft embedded an ASF video in the word format?
    They'd have to uuencode it first, then stick it in. Would this suddenly make the ASF format non-patented? no. And once parts of a format are patented, you can't recreate the whole format without negotiating a patent deal with the holder.

    Yes, the law is an ass. No, you can't circumvent it with clever words.
  • by superyooser ( 100462 ) on Monday November 17, 2003 @02:12PM (#7494414) Homepage Journal
    Oops, I need to clarify my clarification. I'm talking only about XML schemas (customer-defined XSDs, not the Office ML standards) and maybe XSLT (XML Stylesheet Language Transformations) files too, but not regular Office documents! To my knowledge, all editions of Office 2003 can create regular Office files in XML.
  • Re:Namespaces... (Score:3, Informative)

    by Jack William Bell ( 84469 ) on Monday November 17, 2003 @02:26PM (#7494555) Homepage Journal
    You missed the entire point. Namespaces are not a derivative format, they are a separate format embedded in the original file; like embedding a graphic. Please read up on XML namespaces and google for 'Namespace Modules' before continuing this conversation.
  • by Scarblac ( 122480 ) <slashdot@gerlich.nl> on Monday November 17, 2003 @02:28PM (#7494575) Homepage

    Remember, they got that amendment through in the European Parliament. While that is a victory, the EP does not have a whole lot of real power, unfortunately. It's the European Commission that decides. And it's quite likely that they'll eventually endorse a version that doesn't have the good amendments.

    The EU sucks. They should make it democratic before expanding it.

  • by Anonymous Coward on Monday November 17, 2003 @04:31PM (#7495735)
    If you look closely at the license
    (http://rep.oio.dk/Microsoft.com/officeschemas/L egalNotice.htm),
    you will see that it referrs you to another license
    (http://www.microsoft.com/mscorp/ip/format/xmlpa tentlicense.asp)
    if you wish to create "software that reads or writes files in the format".
    That license contains language that MAY SPECIFICALLY PROHIBIT OPEN SOURCE IMPLEMENTATIONS - it is hard to tell though because the license to which you "explicitly agree" by distributing software under this patent license is NOT AVAILABLE AT THE URL LISTED
    (http://msdn.microsoft.com/library/en-us/odcXMLR ef/html/odcXMLRefLegalNotice.asp?frame=true)
    Always remember to read the details before making assumptions. Especially with M$.

    Publishing the schema without giving free license to read and write documents in the format is NOT an open license.
  • Re:Compressed? (Score:3, Informative)

    by Narcissus ( 310552 ) on Monday November 17, 2003 @04:49PM (#7495882) Homepage
    OpenOffice doesn't compress the data before storing it in XML: it generates the various XML (and XML related?) files then compresses them together.

    If you change the extension on an OpenOffice document you can uncompress it and read through the XML (ie. the data is definitely not compressed before going into the XML).
  • by Pharmboy ( 216950 ) on Monday November 17, 2003 @05:39PM (#7496450) Journal
    Now, with the opening of the format, that "mostly compatible" becomes "compatible."

    Did any of you read the actual Microsoft patent statement? It says you must obtain a license if you USE the information in a seperate application for compatability. Quoting them:

    "There is a separate patent license available to parties interested in implementing software programs that can read and write files that conform to the Specification."

    Technically, anyone that looks at it, and uses it to put compatability for Open Office, are infringing on their patent. And now that the spec is in the open, its very easy for microsoft to say "we opened it up, and they infringed, this is why we dont like open source". This also means, that if you DON'T look at it, and instead do manage to reverse engineer it, it is likely that a judge will believe MS that you are lying and instead just read their "open" standard.

    Its open, as long as you don't use it.
  • by Anonymous Coward on Monday November 17, 2003 @07:36PM (#7497618)
    Be fair. If you're a company that's buying 400 copies of office, you sure won't be paying $600 per seat. Where I work we get a full licence for Office Pro for $55. 400*$55= $22,000. Not a trivial amount by any means, but a drop in the bucket compared the the cost of buying and aministering that many computers.

Never call a man a fool. Borrow from him.

Working...