Skip to main content

Home/ OpenDocument/ Group items tagged Configuration

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Slamming the door shut on MS OOXML - 0 views

lists.oasis-open.org/...msg00033.html

cdf interoperability iso odf odf-tc officeopenxml ooxml opendocument xml

shared by Gary Edwards on 24 Aug 07 - Cached
  • So your goal is a networked world where metadata is routinely trashed by apps developed by those who are too dumb or otherwise disabled to preserve metadata and only the big boys get to do interoperability, right? So if I send you a document for your editing, I can't count on getting it back with xml:id attributes intact. No thanks, Patrick. That sounds way too much like how things have worked ever since office productivity software first came on the market. In your world, interoperability belongs only to those who can map features 1:1 with the most featureful apps. And that is precisely why OpenDocument never should have been approved as a standard. Your kind of interoperability makes ODF a de facto Sun Microsystems standard wearing the clothing of a de jure standard. Why not just standardize the whole world on Microsoft apps and be done with it? Are two monopolies maintained by an interoperability barrier between them better than one? Fortunately, we don't have to debate the issue because the Directives resolve the issue. You lose under the rules of the game.
  • Gary Edwards on 24 Aug 07
     
    Marbux on metadata and the language of universal interoperability: Few people are aware of the raging debate that has pushed ODF to the edge. The OASIS ODF TC is split between those who support Universal Interoperability, and those who insist on continuing with limited ODF interoperability.

    ODF (OpenDocument), formally known as Open Office XML, began it's standards life in the fall of 2002 when Sun submitted the OpenOffice file format to OASIS for consideration as a office suite XML fiel format standard. The work on ODF did not start off as a clean slate in that there were near 600 pages of application specific specification from day one of the standards work. The forces of universal interop have sought for years to separate ODF from the application specific features and implementation model of OpenOffice that began with those early specification volumes, and continues through the undue influence Sun continues to have over the ODF specification work.

    Many mistakenly believed that submission of ODF to ISO and subsequent approval as an international standard would provide an effective separation, putting ODF on the track of a truly universal file format.

    Marbux is one of those Universal Interop soldiers who has dug in his heels, cried to the heavens that enough is enough, and demanded the necessary changes to ODF interoperability language.

    This post he recently submitted to the OASIS ODF Metadata SC is a devastating rebuttal to the arguments of those who support the status quo of limited interoperability.

    In prior posts, marbux argues that ISO directives demand without compromise universal interoperability. This demand is also shared by the World Trade Organization directives regarding international trade laws and agreements. Here he brings those arguments together with the technical issues for achieving universal interop.

    It's a devastating argument.

Gary Edwards

Bringing Open Source to SOAs - 0 views

www.eweek.com/...0,1895,2155922,00.asp

apache eclipse opensource oss soa

shared by Gary Edwards on 15 Jul 07 - Cached
  • Vendors such as Iona Technologies, Red Hat, MuleSource, WSO2, Sun Microsystems and even IBM are pushing open-source components as key pieces of service-oriented architecture implementations.
  • Iona is heading the Eclipse Foundation's SOA Tools Platform Project, which is building frameworks and tools that enable the design, configuration, assembly, deployment, monitoring and management of software designed around a service-oriented architecture.
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      This is certainly a big win for IBM hardware and Services.   I wonder how IONA plans to compete against IBM when IBM hardware and services can combine a one tow enterprise punch usign IONA open source efforts?

      I hope the IONA guys know what they're doing.  Or this could get ughly.

  • MuleSource CEO Dave Rosenberg, in San Francisco, agreed. "One of the key goals of SOA is to free up your IT environment from burdensome proprietary standards and vendor stacks that lock you in," he said. "In order to truly control your environment, open source is the only answer." MuleSource maintains the open-source Mule ESB.
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      1

      A big 1
  • ...1 more annotation...
  • Shaun Connolly, vice president of JBoss, said that the company's "application platform, Web apps, Web services, portal and the overall SOA platform provides more service bus integration for a more open and integrated platform."
    • Gary Edwards
      Gary Edwards on 15 Jul 07
       
      This is sad.  Red Hat does not yet understand how important the portable XML dcoument/data file format wars are to the future of SOA.  The Microsoft Vista Stack, based on OOXML-Smart Documents as the inter application stack transport, will effectively lock Red Hat out of any enterprise transitioning from MSOffice bound business processes.

      I guess it's because open source vendors don't see the MSOffice <> MS Exchange/SharePoint Hub as part of a SOA solution, that they don't see the importance of OOXML-SmartDocs.

      Red Hat Servers are under assault throughout the USA as Exchange/SharePoint Hub server system move in.  The E/S Hubs have an extraordinary connectivity to existing MSOffice desktops, with OOXML-Smart Docs as the transport connecting the two.

      The only way Red Hat could ever hope to crack that Vista Stack is by using ODF plugins at the head point; MSOffice bound business processes.

      The idea being to let the plugin convert existing documents and business processes to ODF in much the same way that the OOXML plugin for MSOffice carries out the non disruptive conversion to OOXML.

  • Gary Edwards on 15 Jul 07
     
    An eWEEK must read.  I think the recent aquisition is having a positive impact on the eWEEK journalist and reporters.   What a great series they've put together on SOA. SaaS and the Web 2.0
Gary Edwards

What IBM VP Bob Sutor does not want you to read | Universal Interoperability Council - 0 views

www.universal-interop-council.org/?q=node/1

shared by Gary Edwards on 01 Feb 08 - Cached
  • What IBM VP Bob Sutor does not want you to read Submitted by marbux on Thu, 01/31/2008 - 23:36. This site is now live, although there's a ton of customization and configuration work to be done. But we might as well kick off by reprinting a comment I unsuccessfully attempted to post on IBM vice president Bob Sutor's blog today. I'm flattered that my post was the apparent triggering event for Sutor's announcement later in the day that he will now only allow comments from people who use their "real names."
    • Gary Edwards
      Gary Edwards on 01 Feb 08
       
      A must read post from the legendary marbux!
Gary Edwards

Independent study advises IT planners to go OOXML | All about Microsoft | ZDNet.com - 0 views

blogs.zdnet.com/microsoft

burtongorup cdf css garyedwards maryjo odf okelly ooxml w3c xhtml

shared by Gary Edwards on 20 Jan 08 - Cached
  • “ODF represents laudable design and standards work. It’s a clean and useful design, but it’s appropriate mostly for relatively unusual scenarios in which full Microsoft Office file format fidelity isn’t a requirement. Overall, ODF addresses only a subset of what most organizations do with productivity applications today.” The report continues: “ODF is insufficient for complex real-world enterprise requirements, and it is indirectly controlled by Sun Microsystems, despite also being an ISO standard. It’s possible that IBM, Novell, and other vendors may be able to put ODF on a more customer-oriented trajectory in the future and more completely integrate it with the W3C content model, but for now ODF should be seen as more of an anti-Microsoft political statement than an objective technology selection.”
    • Gary Edwards
      Gary Edwards on 20 Jan 08
       
      Mary Jo takes on the recently released Burton Group Report comparing OOXML and ODF. Peter O'Kelly, one of the Burton Group authors, once famously said, "ODF is a great format if you live in an alternative universe where MSOffice doesn't exist!" This observation speaks to the core problem facing ODF and those who seek to implement the ODF standard: ODF was not designed for the conversion of MSOffice documents. Nor was ODF designed to work with MSOffice applications. Another way of saying this is to state that ODF was not designed to be interoperable with MSOffice documents, applications and bound processes. The truth is that ODF was designed for OpenOffice/StarOffice. It is an application specific format. Both OOXML and ODF do a good job of separating content from presentation (style). The problem is that the presentation - layout layers of both ODF and OOXML remains bound to specific applications producing it. While the content layers are entirely portable and can be exchanged without information loss, the presentation layers can not. Microsoft makes no bones about the application specific design and purpose of OOXML. It's stated right in the Ecma 376 charter that OOXML was designed to be compatible with MSOffice and the billions of binary documents in MSOffice specific binary formats. The situation however is much more confusing with ODF. ODF is often promoted as being application, platform and vendor independent. After five years of development though, the OASIS ODF TC has been unable to strip ODF of it's OpenOffice/StarOffice specific aspects. ODF 1.0 - ISO 26300 had three areas that were under specified; meaning these areas were described in syntax only, and lacked the full semantics demanded by interoperable implementations. Only OpenOffice and StarOffice code base applications are able to exchange documents with an acceptable fidelity. The three under specified areas of ODF are: Lists (numbered), F
Gary Edwards

Most Business Tech Pros Wary About Web 2.0 Tools In Business - Technology News by Infor... - 0 views

www.informationweek.com/...showArticle.jhtml

exchange iso microsoft msoffice oasis odf ooxml opendocument openxml sharepoint vista xml

shared by Gary Edwards on 06 Mar 07 - Cached
  • How should an IT team start thinking about an Enterprise 2.0 strategy? One way is to carve it into two main areas. The first is Web-based information sharing--think business versions of Wikipedia, MySpace, and Flickr. A sizable minority of companies are finding effective business uses for blogs, wikis, syndicated feeds, pervasive search, social networking, collaborative content portals like SharePoint, and mashups that use easier-to-integrate APIs and fast-response development techniques such as Ajax. One example: Wikis, which let multiple people access and edit a document online, are widely used at 6% of companies in our survey and used effectively by a few employees at 25% of companies. The second area is voice and messaging, where voice over IP, instant messaging, presence, videoconferencing, and unified communications can make it possible to connect people in more relevant ways. Unified communications entails the blending of voice calls, video, and messages, coupled with functionality like embedded click-to-call links in documents and contact lists and the ability to see if colleagues and partners are available to chat. It's widely used at 13% of companies surveyed and effectively by a few at 24%.
  • Gary Edwards on 06 Mar 07
     
    Great coverage from InformationWeek about the emerging Enterprise 2.0 arena.  Author Michael Hoover does not get too deep into the Information Processing Chain, as exampled by the integrated Vista Stack of desktop, server, device,Internet systems and services.  But he provides a more than adequate framework for evaluating chain components.

    As the ODF - OOXML battle contiues to expand, engulfing swallowing and swamping near everythign in it's path, the day is not too far off when the battle will move to the center of Enterprise 2.0 considerations.  It has to.  XML Hubs are how these converging technologies are going to be gathered, integrated and configured to impact rapidly changing business processes.  There has to be a universal transport in these systems that all applications can work, and nothig matches the highly portable and interactive document/data capabilities of ODF and OOXML.  They alone own the desktop prodcutivity environment migration to XML.  And it will be through XML - RDF/XML that the Hubs finally integrate the flow of information between desktops, servers, devices and Internet systems.

    ~ge~

Gary Edwards

ongoing · Life Is Complicated - 0 views

www.tbray.org/...Mixup

iso microsoft oasis odf ooxml opendocument openxml xml

shared by Gary Edwards on 06 Mar 07 - Cached
  • Fortunately for Microsoft, the DaVinci plugin is coming, which will enable Microsoft office applications to comply with ISO 26300. We all understand the financial issues that prompted the push to make OOXML a standard (see Tim's comment above and http://lnxwalt.wordpress.com/2007/01/21/whose-finances-are-on-the-line/ for more on this) and ensure continued vendor lock-in. However, OOXML is not the answer.
  • ODF can handle everything and anything Microsoft Office can throw at it. Including the legacy billions of binary documents, years of MSOffice bound business processes, and even tricky low level reaching add-ons represented by assistive technologies.
  • Gary Edwards on 06 Mar 07
     
    Yes!  It's Da Vinci time.  I wonder if W^ has downloaded ACME 376 and taken the Da Vinci conversion engine out for a test run?  Belgium and Adobe took a look, and have expressed an interest in getting their hands on the ODF 1.2 version of Da Vinci.  California and Massachusetts have yet to comment about ACME 376, but of course they are also waiting for Da Vinci.

    I'll thank W^ for his kind comments, and make sure he knows about the ACME 376 proof of concept.  If DaVinci can hit perfect conversion fidelity with those billions of binary documents using XML encoded RTF, there is no reason why Da Vinci can't do the same with ODF.  We do however need ODF 1.2 to insure that perfect interoperability with other ODF ready applications.
  • ...1 more comment...
  • Gary Edwards on 06 Mar 07
     
    Yes!  It's Da Vinci time.  I wonder if W^ has downloaded ACME 376 and taken the Da Vinci conversion engine out for a test run?  Belgium and Adobe took a look, and have expressed an interest in getting their hands on the ODF 1.2 version of Da Vinci.  California and Massachusetts have yet to comment about ACME 376, but of course they are also waiting for Da Vinci.

    I'll thank W^ for his kind comments, and make sure he knows about the ACME 376 proof of concept.  If DaVinci can hit perfect conversion fidelity with those billions of binary documents using XML encoded RTF, there is no reason why Da Vinci can't do the same with ODF.  We do however need ODF 1.2 to insure that perfect interoperability with other ODF ready applications.
  • Gary Edwards on 06 Mar 07
     
    Yes!  It's Da Vinci time.  I wonder if W^ has downloaded ACME 376 and taken the Da Vinci conversion engine out for a test run?  Belgium and Adobe took a look, and have expressed an interest in getting their hands on the ODF 1.2 version of Da Vinci.  California and Massachusetts have yet to comment about ACME 376, but of course they are also waiting for Da Vinci.

    I'll thank W^ for his kind comments, and make sure he knows about the ACME 376 proof of concept.  If DaVinci can hit perfect conversion fidelity with those billions of binary documents using XML encoded RTF, there is no reason why Da Vinci can't do the same with ODF.  We do however need ODF 1.2 to insure that perfect interoperability with other ODF ready applications.
  • Gary Edwards on 06 Mar 07
     
    Hi guys,

    There is an interesting discussion triggered by Tim Bray's "ongoing · Life Is Complicated" blog piece.  Our good friend Mike Champion has some interesting comments defending ISO/IEC approval of MS Ecma 376 based on many arguments.  But this one seems to be the bottom line;

    <mike> "there is not an official standard for one that (in the opinion of the people who actually dug deeply into the question, and I have not) represents all the features supported in the MS Office binary formats and can be efficiently loaded and processed without major redesign of MS Office.

    ..... So, if you want a clean XML format that represents mainstream office document use cases, use ODF. If you want a usable XML foormat that handles existing Word documents with full fidelity and optimal performance in MS Office, use OOXML. If you think this fidelity/performance argument is all FUD, try it with your documents in Open Office / ODF and MS Office 2007 / OOXML and tell the world what you learn." </mike>

    Mike's not alone in this.  This seems to be the company line for Microsoft's justification that ISO/IEC should have two conflicting file formats each pomising to do the same thing, becaus eonly one of those formats can handle the bilions of binary documents conversion to XML with an acceptable fidelity. 

    This is not true, and we can prove it.  And if we're right  that you can convert the billions of binaries to ODF without loss of fidelity, then there was no "technology" argument for Microsoft not implementing ODF natively and becoming active in the OASIS ODF TC process to improve application interoperability.

    <diigo_
Gary Edwards

Flow Document Overview - 0 views

msdn2.microsoft.com/...aa970909.aspx

cdf flash flow-document ms-ooxml pdf silverlight svg winforms xforms xps xslfo

shared by Gary Edwards on 18 Dec 07 - Cached
  • Gary Edwards on 18 Dec 07
     
    Uh OH! Look what Microsoft has put into the new .NET 3.0 SDK! Flow Documents is a Microsoft specific version of HTML that is part of the Windows Presentation Foundation Browser Developers Framework. XAML - XPS-XABL. It also looks as though Microsoft has reserved MS-OOXML MSOffice level integration for themselves. Another thought is that MSOffice is being positioned as a developers framework for Web 2.0 development. This docuemnt is goign to take some serious study. Bad news for IBM and Adobe for sure. PDF, Flash and AJAX are all going to be in the fight of their lives. The conversion tools are going to become of critical importance. Some initial thoughts are that we could convert MSOffice documents to CDF+; convert OpenOffice documents to CDF+; and convert Flow Documents to CDF+, using the same XHTML 2.0 - CSS desktop profile (WICD Full). Converting MS-OOXML to Flow Documents however appears to be next to impossible by design. The easy approach would be to let the da Vinci plug-in perfect an internal conversion to either CDF+ or Flow. It will be interesting to see if Microsoft provides a Flow plug-in for MSOffice. I doubt it, but perhaps there will be a demand from Flow developers. da Vinci could of course be configured to produce Flow Documents. At first glance, my assumption would be that the ability to convert native MSOffice documents and allication genrated Flow Documents to CDF+ would be the most important course to take. We''ll see. This is no doubt explosive stuff. Microsoft is truly challenging the W3C for the Web.
1 - 9 of 9
Showing 20▼ items per page