Skip to main content

diigo

Add to browser

okay ... seriously now ... what is this supposed to be? ( OpenDocument) Join Group To Post

You are here: Diigo Home > Groups > OpenDocument > Forum > okay ... seriously now ... what is this supposed to be?

  • #1mazyar hedayat said ...(on 09-01-2007)

    mazyar hedayat
    I'm not an IT professional. I'm not a techi. I'm a lawyer and writer. I just became aware of Microsoft's use of the "Open Document" concept (which appears to have something to do with .xml ...). But what is it really? Does it actually represent something new? Or is it just a rehash of someone else's idea?
  • #2Gary Edwards said ...(on 12-11-2007, replying to mazyar hedayat on #1)

    Gary Edwards
    mhedayat wrote:

    I'm not an IT professional. I'm not a techi. I'm a lawyer and writer. I just became aware of Microsoft's use of the "Open Document" concept (which appears to have something to do with .xml ...). But what is it really? Does it actually represent something new? Or is it just a rehash of someone else's idea?



    Hi mhedayat,


    There are two important XML file formats designed for traditional desktop office suite use. One is known as Open Document, which was designed for Sun's OpenOffice.org / StarOffice desktop office suite. The other is Microsoft Office Open XML which was designed for MSOffice.



    In November of 2002, Sun submitted what was then Open Office XML to OASIS for consideration as a standard file format. After years of work and a name change to Open Document (ODF) in September of 2004, OASIS approved ODF as a standard on April 30th, 2005. This work was then sent to ISO as DIS 26300, for consideration as an International Standard.



    In December of 2004, at the time ODF was just then coming out of the OASIS technical committee as ODF 1.0, and heading for consideration by the OASIS general membership, Microsoft submitted their XML format to Ecma for consideration. It was called Office Open XML", which is eerily similar to the original OASIS Open Office XML name.



    Microsoft had actually introduced their xml formats with the MSOffice 2003 beta release in early 2003. The formats were called WordProcessingML and SpreadsheetML. In December of 2004, Microsoft submitted their newly renamed Office Open XML spec to Ecma for consideration. Ecma is similar to OASIS in that both are corporate vendor driven standards consortia. Both groups also have fast track access to ISO.



    A year after OASIS approved ODF 1.0 and sent the spec on to ISO, ISO approved ODF 1.0 as an International Standard (May of 2006).



    In December of 2006, Ecma approved MS-OOXML (Office Open XML), and it was sent to ISO as DIS 29500. On September 2nd, 2007, ISO voted down MS-OOXML, with a considerable number of comments (3,600). A February Ballot Resolution meeting has been planned to try to resolve these comments. If resolved, MS-OOXML will come up for a second ISO vote.



    The question becomes that of why desktop applications are moving from the traditions of binary formats to a more open and standardized XML file format. Although there are many reasons for this, the primary reason is that XML is the language for Internet. The W3C's (another standards group the equivalent of ISO) HTML is moving to XHTML and the many Compound Document Format (CDF+) variations now becoming available. Highly structured documents that are Internet ready would be extremely valuable, enabling easy re purposing and processing as well as providing a very high level of interoperability and exchange. The W3C invented XML and approved it as a standard in 1998.



    A very powerful idea called the Grand Convergence of desktop, server, device and web information systems is currently driving the work on the web platform. The core of this convergence is the ability to shuttle portable XML documents across desktop, server, device and web systems without loss of content or presentation fidelity. The portable document model itself could perhaps break the old application – document – data dependency model in that data binding and workflow routing are document specific characteristics instead of being application specific.



    Grand Convergence also enables SaaS, SOA, Web 2.0 and the integration of enterprise publication, content and archive management systems.



    Here's the thing. OpenDocument is OpenOffice application specific and is not web ready! MS-OOXML is also application specific, but is web ready only in the sense that it's useful to the emerging MS Stack of desktop, server, device and web application. MS-OOXML is not useful outside of the MS Stack.



    A third format from the W3C called CDF+ is capable of handling the full richness of desktop office suites, and is definitely web ready. CDF+ is also on it's way to becoming an open international standard. The problem is that the WAR between ODF and MS-OOXML camps is so contentious and partisan, that CDF is routinely attacked by both groups! Even though it's possible to solve the very nasty ODF and MS-OOXML interoperability problems using fluid conversions to a CDF+ desktop profile known as WICD Full.



    I hope this answers your question. This is one very important world changing issue!



    ~ge~

  • #3mazyar hedayat said ...(on 12-12-2007, replying to Gary Edwards on #2)

    mazyar hedayat
    Gary

    Thank you for the insightful (and exhaustive) overview. Question. Would you allow me to publish all or part of your response on my practice management blog at http://dcbalpm.wordpress.com? Or maybe you would like to write up something slightly different. I think the topic is important and worth noting for my readers. On another (related?) note - have you heard of APML (attention profiling markup language)? I've begun looking into it and mentioned it in my last post because of the looming 'attention economy.' Just wondering.

    M. Hedayat
    mmhedayat1@gmail.com
    http://www.mha-law.com

    garyedwards wrote:
    > mhedayat wrote:
    >

    I'm not an IT professional. I'm not a techi. I'm a lawyer and writer. I just became aware of Microsoft's use of the "Open Document" concept (which appears to have something to do with .xml ...). But what is it really? Does it actually represent something new? Or is it just a rehash of someone else's idea?


    >
    >

    Hi mhedayat,


    >

    There are two important XML file formats designed for traditional desktop office suite use. One is known as Open Document, which was designed for Sun's OpenOffice.org / StarOffice desktop office suite. The other is Microsoft Office Open XML which was designed for MSOffice.


    >
    >

    In November of 2002, Sun submitted what was then Open Office XML to OASIS for consideration as a standard file format. After years of work and a name change to Open Document (ODF) in September of 2004, OASIS approved ODF as a standard on April 30th, 2005. This work was then sent to ISO as DIS 26300, for consideration as an International Standard.


    >
    >

    In December of 2004, at the time ODF was just then coming out of the OASIS technical committee as ODF 1.0, and heading for consideration by the OASIS general membership, Microsoft submitted their XML format to Ecma for consideration. It was called Office Open XML", which is eerily similar to the original OASIS Open Office XML name.


    >
    >

    Microsoft had actually introduced their xml formats with the MSOffice 2003 beta release in early 2003. The formats were called WordProcessingML and SpreadsheetML. In December of 2004, Microsoft submitted their newly renamed Office Open XML spec to Ecma for consideration. Ecma is similar to OASIS in that both are corporate vendor driven standards consortia. Both groups also have fast track access to ISO.


    >
    >

    A year after OASIS approved ODF 1.0 and sent the spec on to ISO, ISO approved ODF 1.0 as an International Standard (May of 2006).


    >
    >

    In December of 2006, Ecma approved MS-OOXML (Office Open XML), and it was sent to ISO as DIS 29500. On September 2nd, 2007, ISO voted down MS-OOXML, with a considerable number of comments (3,600). A February Ballot Resolution meeting has been planned to try to resolve these comments. If resolved, MS-OOXML will come up for a second ISO vote.


    >
    >

    The question becomes that of why desktop applications are moving from the traditions of binary formats to a more open and standardized XML file format. Although there are many reasons for this, the primary reason is that XML is the language for Internet. The W3C's (another standards group the equivalent of ISO) HTML is moving to XHTML and the many Compound Document Format (CDF+) variations now becoming available. Highly structured documents that are Internet ready would be extremely valuable, enabling easy re purposing and processing as well as providing a very high level of interoperability and exchange. The W3C invented XML and approved it as a standard in 1998.


    >
    >

    A very powerful idea called the Grand Convergence of desktop, server, device and web information systems is currently driving the work on the web platform. The core of this convergence is the ability to shuttle portable XML documents across desktop, server, device and web systems without loss of content or presentation fidelity. The portable document model itself could perhaps break the old application – document – data dependency model in that data binding and workflow routing are document specific characteristics instead of being application specific.


    >
    >

    Grand Convergence also enables SaaS, SOA, Web 2.0 and the integration of enterprise publication, content and archive management systems.


    >
    >

    Here's the thing. OpenDocument is OpenOffice application specific and is not web ready! MS-OOXML is also application specific, but is web ready only in the sense that it's useful to the emerging MS Stack of desktop, server, device and web application. MS-OOXML is not useful outside of the MS Stack.


    >
    >

    A third format from the W3C called CDF+ is capable of handling the full richness of desktop office suites, and is definitely web ready. CDF+ is also on it's way to becoming an open international standard. The problem is that the WAR between ODF and MS-OOXML camps is so contentious and partisan, that CDF is routinely attacked by both groups! Even though it's possible to solve the very nasty ODF and MS-OOXML interoperability problems using fluid conversions to a CDF+ desktop profile known as WICD Full.


    >
    >

    I hope this answers your question. This is one very important world changing issue!


    >
    >

    ~ge~

  • #4Gary Edwards said ...(on 04-16-2008, replying to mazyar hedayat on #3)

    Gary Edwards
    Hi Mazyar,

    Feel free to publish whatever you need. I should point out that the recent ISO approval of Ecma 376, now ISO 29500, is game changing. ISO approval establishes MSOffice as a standards compliant "editor".

    Interestingly, ISO 29500 is different than Ecma 376 because of the many changes Microsoft made to the Ecma 376 specification to get approval. The one thing that didn't change however is a clause in the Ecma 376 charter that sets defining boundaries as to what changes can be made. The charter clause simply states that Ecma 376 must be compatible with Office Open XML (OOXML).

    So what is Office Open XML?

    What we have today are three specifications: ISO 29500, Ecma 376, and the defining OOXML.

    Since there is no date or printed specification for OOXML in the Ecma 376 charter, "OOXML" can only be defined by whatever Microsoft (and MSOffice) say OOXML is. In essence, OOXML is a moving target that Ecma 376 and now ISO 29500 must remain compatible with.

    Ecma recently turned all maintenance and control of Ecma 376 over to ISO, so effectively "Ecma 376" no longer exists. Approval of Ecma 376 as ISO 29500 includes approval of the Ecma 376 charter.

    The binding boundaries of maintaining "compatibility with OOXML" continue with ISO 29500. The test of this assertion can be found in the many Microsoft-Ecma responses voted on during the Geneva ISO BRM (Ballot Resolution Meeting) held in late February 2008. The September 2nd, 2007 vote on Ecma 376 was defeated by ISO NB members (National Bodies). All "NO" votes with a comment went to the Geneva BRM for resolution, which was followed by a second vote on Ecma 376 in March of 2008.

    Looking through the Microsoft-Ecma responses to NB comments, we see that many comments and requests were ruled out by Microsoft-Ecma precisely because of the "compatible with OOXML" requirement!!!!

    Perhaps even more interesting is the fact that not one of the ISO NB's demanded that the "compatibility with OOXML" clause in the Ecma 376 be removed.

    Breaking the Web and Riding the Fifth Wave:
    The importance of ISO approval of what in essence is a dynamic and undefined MSOffice specific OOXML, is that this provides Microsoft with a rare opportunity to break the web, and control the transition of most client/server business processes to the MS Web Stack - MS Cloud model.

    First, how is it that Microsoft uses ISO OOXML to "break the web"?

    In December of 2007, Microsoft released the MSOffice SDK beta. Included in the beta is a easy to implement OOXML <> XAML conversion component. XAML is a proprietary WPF technology (Windows Presentation Foundation) that is often referred to as "fixed/flow". XPS, Silverlight, WinForms and Smart Tags are other closely related proprietary WPF technologies.

    Together, the WPF technologies provide Web ready alternatives to open web technologies from the W3C, Mozilla, and Adobe.

    For instance, XAML is a proprietary alternative to W3C HTML, XHTML-CSS and CDF. Silverlight is an alternative to W3C SVG and Adobe Flash-Flex-AIR. Winforms is an alternative to W3C XForms. Smart Tags (and related LINQ) is an alternative to W3C semantic web technologies RDF. RDFa, SPARQL, and XQuery.

    The thing is, the W3C and Adobe technologies do not have a desktop "editor" the equivalent of MSOffice. Note that with a 95% marketshare, the MSOffice desktop defines and binds most of the "client" side of the existing client/server equation. No doubt the legacy client/server systems are going to transition to the emerging "client/ Web-Stack /server" model essential to all SOA, SaaS, and Web 2.0 systems.

    Somehow Microsoft has managed to delay client/server transition of MSOffice bound or intertwined business processes to this emerging client/ Web-Stack /server model until such time as they were in position to control the transition. ISO standardization of MSOffice OOXML nails down the "client" side of this massive transition. The successful introduction of the MS Web-Stack comprised of Exchange-SharePoint-MS SQL Server nails down the core of the new equation. This will be followed by MS Dynamics, MS Live and MS Communications Server, MS Mobil and other web centric service providers.

    Another key to the MS equation is the recently released IE-8 beta. Interestingly IE-8 supports bits of HTML-5 and CSS 2.1, but with NO support for XHTML, JavaScript, CSS-3, SVG, XForms or RDF.

    Oh yeah, IE-8 supports XAML "fixed/flow", Silverlight, WinForms and Smart Tags.

    IMHO, IE-8 will "dumb down" the open web through this telling lack of support for advanced W3C technologies which are needed for complex web documents. The kind of documents produced by MSOffice! Note that OpenOffice ODF is not "web ready". Nor does OpenOffice support advanced XHTML-CSS-SVG-XForms! These W3C technologies are only partially implemented or are export only in OpenOffice.

    Web developers trying to target cross browser use will have to dumb down their work to meet the restrictions of IE-8. Meanwhile, the very rich and complex capable (but proprietary) XAML will be useful to all MS Web-Stack developers. IE-8 users will have access to the open web as well as the MS Web.

    And what is the MS Web?

    IMHO, the control MS has over the client/server transition to client/ Web-Stack /server models will break the Web into two domains; consumer and business. Google will own the "consumer" portion of the Web unless the Microsoft attempt to acquire Yahoo! succeeds. Microsoft will of course own the "business" web through their control of the business process transition. Control is maintained by not having to implement W3C open web technologies. ISO approval of MSOffice OOXML enables Microsoft to usher in the proprietary sweep of WPF - .NET protocols and formats. This will create an insurmountable barrier for Google, Mozilla, Apache, Oracle, IBM and SalesForce.com when it comes to "business systems" seeking the advantages of a clent/ Web-Stack /server model.

    In other words, we will have a Google "consumer" cloud computing model, and, a Microsoft "business" cloud computing model. Cloud computing being defined as an efficient "hosting" of advanced web applications and services. In Nicholas Carr terms, Microsoft will own the "big switch" for business systems.

    The Yahoo! acquisition would enable Microsoft to provide a convergence of consumer-business services. The idea being that every business user is also a consumer. Convergence enables many views of such things like eMail, calendar, schedules, projects and document management. It's a great idea.

    About the "Fifth Wave":
    In 1998 the Economist Magazine published an article that included a graph called "The Fourth Wave". The graph tracked the advance of computing through four great waves; central "mainframe-workstation", pc, network-workgroup, and end user Internet. Each wave overlaped and exceeded the previous by magnitudes.

    What i'm suggesting is that we are about to enter a fifth wave where consumer-business systems converge. We can now see that the fourth wave was artificially limited to consumer oriented services and systems. Microsoft refused to put the MSOffice bound "client/server" systems into play until they could fully control the transition.

    Now they're ready. The pieces are in place. The transition is underway. The fight to save our open web is before us.

    You might want to study carefully this podcast-document: "XML-Empowered Documents Extend SOA’s Connection to People and Processes" @
    http://briefingsdirect.blogspot.com/2008/03/xml-empowered-documents-extend-soas.html

    It's the best discussion yet on the importance of the portable XML document. The one thing they seriously miss in this discussion is the value of the MSOffice "editor", the importance of structured XML formats for Office Suite "editors", and the importance MSOffice holds in existing business processes.

    As a side note, i will be moving from "OpenDocument" bookmarks to a new group, "SOA, Clouds and the Open Web".

    ISO approval of MSOffice OOXML and the unbending control IBM and Sun have over ODF has ended my interest in ODF. I've moved to W3C Open Web technologies.

    Note that Microsoft, IBM and Sun share one "vendor" common interest. They want to claim compliance with an international format standard for document interchange without having to ever disclose or document application-platform-vendor specific eXtensions. Those proprietary eXtensions will break interoperability. And interop is the entire reason for having a standard!

    Hope this helps, and thanks for your interests,

    ~ge~

    mazyar hedayat wrote:
    > Gary
    >
    > Thank you for the insightful (and exhaustive) overview. Question. Would you allow me to publish all or part of your response on my practice management blog at http://dcbalpm.wordpress.com? Or maybe you would like to write up something slightly different. I think the topic is important and worth noting for my readers. On another (related?) note - have you heard of APML (attention profiling markup language)? I've begun looking into it and mentioned it in my last post because of the looming 'attention economy.' Just wondering.
    >
    > M. Hedayat
    > mmhedayat1@gmail.com
    > http://www.mha-law.com
    >
    > garyedwards wrote:
    > > mhedayat wrote:
    > >

    I'm not an IT professional. I'm not a techi. I'm a lawyer and writer. I just became aware of Microsoft's use of the "Open Document" concept (which appears to have something to do with .xml ...). But what is it really? Does it actually represent something new? Or is it just a rehash of someone else's idea?


    > >
    > >

    Hi mhedayat,


    > >

    There are two important XML file formats designed for traditional desktop office suite use. One is known as Open Document, which was designed for Sun's OpenOffice.org / StarOffice desktop office suite. The other is Microsoft Office Open XML which was designed for MSOffice.


    > >
    > >

    In November of 2002, Sun submitted what was then Open Office XML to OASIS for consideration as a standard file format. After years of work and a name change to Open Document (ODF) in September of 2004, OASIS approved ODF as a standard on April 30th, 2005. This work was then sent to ISO as DIS 26300, for consideration as an International Standard.


    > >
    > >

    In December of 2004, at the time ODF was just then coming out of the OASIS technical committee as ODF 1.0, and heading for consideration by the OASIS general membership, Microsoft submitted their XML format to Ecma for consideration. It was called Office Open XML", which is eerily similar to the original OASIS Open Office XML name.


    > >
    > >

    Microsoft had actually introduced their xml formats with the MSOffice 2003 beta release in early 2003. The formats were called WordProcessingML and SpreadsheetML. In December of 2004, Microsoft submitted their newly renamed Office Open XML spec to Ecma for consideration. Ecma is similar to OASIS in that both are corporate vendor driven standards consortia. Both groups also have fast track access to ISO.


    > >
    > >

    A year after OASIS approved ODF 1.0 and sent the spec on to ISO, ISO approved ODF 1.0 as an International Standard (May of 2006).


    > >
    > >

    In December of 2006, Ecma approved MS-OOXML (Office Open XML), and it was sent to ISO as DIS 29500. On September 2nd, 2007, ISO voted down MS-OOXML, with a considerable number of comments (3,600). A February Ballot Resolution meeting has been planned to try to resolve these comments. If resolved, MS-OOXML will come up for a second ISO vote.


    > >
    > >

    The question becomes that of why desktop applications are moving from the traditions of binary formats to a more open and standardized XML file format. Although there are many reasons for this, the primary reason is that XML is the language for Internet. The W3C's (another standards group the equivalent of ISO) HTML is moving to XHTML and the many Compound Document Format (CDF+) variations now becoming available. Highly structured documents that are Internet ready would be extremely valuable, enabling easy re purposing and processing as well as providing a very high level of interoperability and exchange. The W3C invented XML and approved it as a standard in 1998.


    > >
    > >

    A very powerful idea called the Grand Convergence of desktop, server, device and web information systems is currently driving the work on the web platform. The core of this convergence is the ability to shuttle portable XML documents across desktop, server, device and web systems without loss of content or presentation fidelity. The portable document model itself could perhaps break the old application – document – data dependency model in that data binding and workflow routing are document specific characteristics instead of being application specific.


    > >
    > >

    Grand Convergence also enables SaaS, SOA, Web 2.0 and the integration of enterprise publication, content and archive management systems.


    > >
    > >

    Here's the thing. OpenDocument is OpenOffice application specific and is not web ready! MS-OOXML is also application specific, but is web ready only in the sense that it's useful to the emerging MS Stack of desktop, server, device and web application. MS-OOXML is not useful outside of the MS Stack.


    > >
    > >

    A third format from the W3C called CDF+ is capable of handling the full richness of desktop office suites, and is definitely web ready. CDF+ is also on it's way to becoming an open international standard. The problem is that the WAR between ODF and MS-OOXML camps is so contentious and partisan, that CDF is routinely attacked by both groups! Even though it's possible to solve the very nasty ODF and MS-OOXML interoperability problems using fluid conversions to a CDF+ desktop profile known as WICD Full.


    > >
    > >

    I hope this answers your question. This is one very important world changing issue!


    > >
    > >

    ~ge~