Skip to main content

Home/ OpenDocument/ Group items tagged wicd

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Open Document Foundation Gives Up | Linux Magazine - 0 views

www.linux-magazine.com/...n_document_foundation_gives_up

cdf odf ooxml w3c

shared by Gary Edwards on 16 Nov 07 - Cached
  • The reasons for the move to CDF was improved compatibility with Microsoft’s OOXML format the foundation claimed at the time. Cris Lilley from W3C contradicted. CDF is not an office format, and thus not an alternative to the Open Document Format. This turn-down is likely the reason for the abrupt ditching of the foundation.
  • Gary Edwards on 16 Nov 07
     
    I've got to give this one extra points for creativity!  All anyone has to do is visit the W3C web sites for CDF WICD Full 1.0 to realize that there is in fact a CDf profile for desktops.  CDF WICD Mobile is the profile for devices.

    My guess is that Chris Lilley is threading the needle here.  IBM, Groklaw, and the lawyer for OASIS have portrayed the Foundation's support for CDF WICD Full as a replacement for ODF - as in native file format for OpenOffice kind of replacement.  Mr. Lilley insists that CDF WiCD Full was not designed for that purpose.  It's for export only!  As in a conversion of native desktop file formats.

    Which is exactly what the da Vinci group was doing with MSOffice.  The Foundation's immediate interest in CDF WICD was based on the assumption that a similar conversion would be possible between OpenOffice ODF and CDF WICD.

    The Foundation's thinking was that if the da Vinci group could convert MSOffice documents and processes to CDF WICD Full, and, a similar conversion of OpenOffice ODF documents and processes to CDF WICD could be done, then near ALL desktop documents could be converted into a highly interoperable web platform ready format.

    Web platform ready documents from OpenOffice?  What's not to like?  And because the conversion between ODF and CDF WICD Full is so comparatively clean, OpenOffice would in effect, (don't go native file format now) become ahighly integrated rich client end user interface to advancing web platforms.

    The Foundation further reasoned that this conversion of OpenOffice ODF to CDF WICD Full would solve many of the extremely problematic interoperability problems that plague ODF.  Once the documents are in CDF WICD Full, they are cloud ready and portable at a level certain to diminish the effects of desktop applications specific feature sets and implementation models.

    In Massachusetts, the Foundation took
Gary Edwards

Greg McNevin : Open Document Foundation Abandons Namesake, Closes up Shop - 0 views

www.idm.net.au/story.asp

cdf odf ooxml

shared by Gary Edwards on 15 Nov 07 - Cached
  • The decision to go with CDF has left some industry commentators scratching their heads, with arstechnica.com’s Ryan Paul noting that the decision is curious as CDF doesn't support “the full range of functionality required for office compatibility”. Paul does add, however, that the formats broad use of formats such as XHTML and SVG does give it a compelling edge.
  • Gary Edwards on 15 Nov 07
     
    The W3C's Chris Lilley, IBM and the lawyer for OASIS have been making quite a bit of noise claiming that CDF doesn't support "the full range of functionality required for office compatibility". 

    This a strange claim, especially when considering IBM as the primary source.  CDF WiCD Full 1.0 is a desktop profile for CDF.  Other profiles include WICD Mobile and WICD Core.  The call for implementations for WICD core, mobile and full went out on Monday, November 12, 2007. 

    To understand cdf, one must first get a handle on the terms used to describe cdf technologies.
    ..... CDF= compound document formats
    ..... CDRF= compound document by reference framework
    ..... WICD = Web Integration Compound Document
    ..... CDR using WICD = Compound Document by Reference using a WICD profile, (Core, Full or Mobile)
    ..... Compound Document by Reference Framework 1.0
    ..... WICD Core 1.0
    ..... WICD Mobile 1.0 Profile
    ..... WICD Full 1.0 Profile

    The WICD Full 1.0 Profile is the "DESKTOP" profile for CDF.
    Some interesting Quotes:

    "WICD Full 1.0 is targeted at desktop agents".

    "The WICD Full 1.0 profile is designed to enable rich multimedia content on desktop and high capability handheld agents."

    From the Compound Document by Reference Use Cases and Requirements Version 1.0 :

    "The capability to view documents with preserved formatting, layout, images and graphics and interactive features such as zooming in and out and multi-page handling."

    "
    <
Gary Edwards

Behind Putting the OpenDocument Foundation to Bed (without its supper) : Updegroove | L... - 0 views

linux-foundation.org/...tion-to-bed-without-its-supper

cdf foundation marbux odf ooxml updegrove

shared by Gary Edwards on 30 May 08 - Cached
  • CDF is one of the very many useful projects that W3C has been laboring on, but not one that you would have been likely to have heard much about. Until recently, that is, when Gary Edwards, Sam Hiser and Marbux, the management (and perhaps sole remaining members) of the OpenDocument Foundation decided that CDF was the answer to all of the problems that ODF was designed to address. This announcement gave rise to a flurry of press attention that Sam Hiser has collected here. As others (such as Rob Weir) have already documented, these articles gave the OpenDocument Foundation’s position far more attention than it deserved. The most astonishing piece was written by ZDNet’s Mary Jo Foley. Early on in her article she stated that, “the ODF camp might unravel before Microsoft’s rival Office Open XML (OOXML) comes up for final international standardization vote early next year.” All because Gary, Sam and Marbux have decided that ODF does not meet their needs. Astonishing indeed, given that there is no available evidence to support such a prediction.
  • Gary Edwards on 30 May 08
     
    Uh?  The ODF failure in Massachusetts doesn't count as evidence that ODF was not designed to be compatible with existing MS documents or interoperable with existing MSOffice applications?

    And it's not just the da Vinci plug-in that failed to implement ODF in Massachusetts!  Nine months later Sun delivered their ODF plug-in for MSOffice to Massachusetts.  The next day, Massachusetts threw in the towel, officially recognizing MS-OOXML (and the MS-OOXML Compatibility Pack plug-in) as a standard format for the future.

    Worse, the Massachusetts recognition of MS-OOXML came just weeks before the September 2nd ISO vote on MS-OOXML.  Why not wait a few more weeks?  After all, Massachusetts had conducted a year long pilot study to implement ODF using ODF desktop office sutie alternatives to MSOffice.  Not only did the rip out and replace approach fail, but they were also unable to integrate OpenOffice ODF desktops into existing MSOffice bound workgroups.

    The year long pilot study was followed by another year long effort trying to implement ODF using the plug-in approach.  That too failed with Sun's ODF plug-in the final candidate to prove the difficulty of implementing ODF in situations where MSOffice workgroups dominate.

    California and the EU-IDABC were closely watching the events in Massachusetts, as was most every CIO in government and private enterprise.  Reasoning that if Massachusetts was unable to implement ODF, California CIO's totally refused IBM and Sun's effort to get a pilot study underway.

    Across the pond, in the aftermath of Massachusetts CIO Louis Guiterrez resignation on October 4th, 2006, the EU-IDABC set about developing their own file format, ODEF.  The Open Document Exchange Format splashed into the public discussion on February 28th, 2007 at the "Open Document Exchange Workshop" held in Berlin, Germany.

    Meanwhile, the Sun ODF plug-in is fl
  • Gary Edwards on 30 May 08
     
    Marbux sets the record straight. These are the facts: Putting Andy Updegrove to Bed (without his supper) ..... http://www.universal-interop-council.org/node/4
  • Gary Edwards on 30 May 08
     
    Response from the OpenDocument Foundation setting the record straight. See "copmments" with this bookmark
Gary Edwards

OpenDocument Foundation folds; will Microsoft benefit? - Mary Jo ZDNet - 0 views

talkback.zdnet.com/5206-12558-0.html

cdf odf ooxml w3c wicd

shared by Gary Edwards on 17 Nov 07 - Cached
  • +1 gary.edwards - 11/16/07 Thanks for the consideration Anton. You might want to follow an emerging discussion now taking place at the OpenDocument Fellowship: Interop between multiple standards and multiple applications Check on the follow up post and understand that this is the same problem the da Vinci group tried to overcome in Massachusetts, when ODF hung by a thread in the summer of 2006; with the sole hope being a plug-in conversion process capable of very high "round trip" fidelity. To assist Massachusetts and the da Vinci Group, the OpenDocument Foundation introduced to the OASIS ODF TC a series of discussions and proposals collectively known as the ODF iX interoperability enhancements. A total of six comprehensive iX enhancements were introduced between July of 2006 and March of 2007. The first three sets of iX enhancements were signed off on by CIO Louis Gutierrez, with the full knowledge and awareness of IBM (they participated directly in those discussions and i do have the emails and conference schedules to verify this . Also, if you're interested in other issues surrounding the da Vinci groups use of CDF WICD Full as an in-process conversion target for MSOffice documents, there is a series of recent responses posted in the comments section of this blog, "Going to Bed (without my supper). One last note; I do have a response to AlphaDog sitting in the blog que, where i try to put the MSOffice to CDF WICD Full conversion, and the OpenOffice ODF to CDF WICD Full conversion into the larger context of the web platform and universal interoperability. This post will also briefly explain the events immediately preceding the decision to shut the Foundation down. Hope this helps, ~ge~
Gary Edwards

WICD Full 1.0 - CDF Desktop Profile - 0 views

www.w3.org/WICDFull

cdf odf ooxml w3c wicd

shared by Gary Edwards on 13 Nov 07 - Cached
  • WICD Full 1.0 is targeted at desktop agents
  • The WICD Full 1.0 profile is designed to enable rich multimedia content on desktop and high capability handheld agents.
  • The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "may", and "OPTIONAL" in this document are to be interpreted as described in RFC&nbsp;2119 (see http://www.ietf.org/rfc/rfc2119.txt). However, for readability, these words do not appear in all uppercase letters in this specification.
    • Gary Edwards
      Gary Edwards on 13 Nov 07
       
      This will make marbux happy!
  • Gary Edwards on 13 Nov 07
     
    Now this is interesting.  I wonder if IBM and the OASIS Lawyer have seen this page?
Gary Edwards

CDI WICD 2.0 - 0 views

www.w3.org/...Overview.html

cdf css svg w3c wicd xforms xhtml

shared by Gary Edwards on 20 Jan 08 - Cached
  • This document defines a generic language-independent processing model for combining arbitrary document formats. The Compound Document Framework is language-independent. While it is clearly meant to serve as the basis for integrating W3C's family of XML formats within its Interaction Domain (e.g., MathML, SMIL, SVG, VoiceXML, XForms, XHTML, XSL) with each other, together with CSS and the DOM; it can also be used to integrate non-W3C formats with W3C formats or integrate non-W3C formats with other non-W3C formats. 1.1. Conformance Everying in this specification is normative except for diagrams, examples, notes and sections marked non-normative. The key words must, must not, required, shall, shall not, should, should not, recommended, may and optional in this document are to be interpreted as described in RFC 2119 [RFC2119]. This specification defines the following classes of products: conforming implementation A user agent that implements all interfaces described in this specification and follows all must-, required- and shall-level of critera in this specification. conforming document A document that follows all must-, required- and shall-level of critera in this specification that apply to document authors. conforming authoring tool One that produces conforming documents.
Gary Edwards

CDF and WICD FAQ - Flock - 0 views

www.w3.org/cdf-faq.html

cdf odf ooxml w3c wicd

shared by Gary Edwards on 13 Nov 07 - Cached
  • What is CDF's relationship with ODF and OOXML? They occupy different spaces. ODF and OOXML are office applications formats, while CDF is a W3C Working Group defining a framework for extensibility on the Web. Compound Documents such as WICD may be appropriate as ODF/OOXML export formats for Web presentation.
  • Gary Edwards on 13 Nov 07
     
    Thanks to the CDF Workgroup! 
Paul Merrell

Putting Andy Updegrove to Bed (without his supper) | Universal Interoperability Council - 0 views

www.universal-interop-council.org/...4

cdf foundation updegrove w3c wicd

shared by Paul Merrell on 27 May 08 - Cached
  • by OASIS attorney Andy Updegrove claimed that W3C Compound Document Formats: [i] are non-editable formats; [ii] are not designed for conversions to other formats; and [iii] are therefore unsuitable as office formats. Updegrove could not have been more wrong.
  • Shorn to essentials, Updegrove in effect argues for the existence of some sort of immaculately conceived data, that data cannot be generated by software editing tools if a homo sapiens operating a keyboard is somehow involved.
  • Conversions — Updegrove hedged somewhat on this issue, attributing a statement to Lilly that the "CDF working group was not chartered to achieve conversion between formats." But one might as well argue that because claw hammers were designed to drive and pull nails they can not be used to hit anything else.
  • ...3 more annotations...
  • To suggest that only W3C WICD profiles can be used with the Framework either flows from or is an appeal to ignorance. There is no wiggle room between those two conclusions.
  • While the Framework specification does require that markup languages combined to create conforming documents be profiled following strict rules, there is no requirement that the profiles thus used superset one or more of the WICD profiles. It may be preferable to do so for purposes of compatibility and interoperability with web applications, but to repeat, that is not required. In fact, virtually any plain text-based markup language that can be profiled can be used within the structure of the Framework. But more importantly, a combination of cutting edge W3C markup language versions such as XHTML 2.0, CSS 3.0, XForms, SVG, etc. can, with only trivial extensions, serve as the full-featured metalanguage superset every expert who has spoken to the subject agrees is necessary to convert between ODF and OOXML with high fidelity.
  • ODF and OOXML are designed for apps from the sneaker net era. Do we choose formats designed for the dinosaurs or formats designed for tomorrow's needs? ODF and OOXML are about the past; CDF is about the future. And yes, there are fully interoperable editors in that future.
Gary Edwards

Harmonization Wars : Is it jetlag? | Brian Jones: Open XML- Open Document Formats - 0 views

blogs.msdn.com/...is-it-jetlag.aspx

harmonization jones odf ooxml opendocument openxml weir

shared by Gary Edwards on 01 Feb 08 - Cached
  • if you actually read the Ecma response, you'll see that TC45's position is actually quite the opposite. Harmonization is not as simple as just adding a few tags here and there. It's going to be a lot of hard work, and the German Standard Body (DIN) is already working on the first step, which is to identify the differences. This isn't something to take lightly. Here is Ecma's full response to this issue (emphasis added): There are currently several XML-based document formats in use, each designed to address a different set of goals or requirements. These include ISO/IEC IS 26300 (ODF), China's UOF, and ECMA-376 (DIS 29500 – Open XML). All these formats have numerous implementations in multiple tools and multiple platforms (Linux, Windows, Mac OS, hand-held devices). The Ecma Response Document from the Fast Track 30-Day contradiction phase for DIS29500 addressed the question of harmonization by explaining the differences between the ODF and Open XML formats as follows:
  • Gary Edwards on 01 Feb 08
     
    Brian Jones responds to Rob Weir's very strange demand that he be put in charge of any harmonization effort involving ODF and OOXML.
    In his response, Brian points to the Ecma official statement in support of harmonization provided in February of 2007. The harmonization response was directed at ISO National Body members objecting to the proposed fast tracking of OOXML.
    In late February -early March of 2007, the EU held an "interoeprability Workshop" in Berlin, Germany.The session was attended by IBM, Sun and Microsoft, as well as Ecma and OASIS.
    The EU took a very hard line position on "harmonization", embracing a position put forward by the French ISO NB group known as AFNOR. The WorkShop was followed by the EU establishment of DIN Workgroup NIA-01-34, headed by the Fraunhoffer Fokus Institute.
    The DIN WG sent out invites to all the major players, with Microsoft and Novell accepting the invitation to particpate in the harmonizatioon effort. IBM and Sun refused the invitation.
    Recently DIN invited the OASIS ODF Technical Committee to join the harmonization effort. The OASIS TC responded by asking Novell developer (and DIN participant) Florian Reuter to act as liaison to DIN. ODF grand puba Rob Weir himself put forward this request.
    Here's the thread: http://www.oasis-open.org/archives/office/200801/msg00040.html
    Now it looks like the grand puba is backtracking! Rob Weir wants to put himself in charge of harmonization. And we all know where that would lead.
    Harmonization will be difficult. It might even be impossible. As indicated by the Ecma statement Brian copiies in his post.
    The dynamics of harmonization are fairly simple to understand; you can't harmonize two application specific formats without also harmonizing the applications. This problem is further complicated by the fact that the presentation layers (styles) of both ODF
Gary Edwards

Blake Matheny : OpenDocument Foundation to Drop ODF for W3C CDF WICD | Blogging success - 0 views

blogging.compendiumblog.com/...ocument-foundation-to-drop-odf

cdf foundation odf ooxml w3c wicd

shared by Gary Edwards on 19 Nov 07 - Cached
  • Now, Sam Hiser, VP of the ODF, has said that he sees the W3C standard CDF (Compound Document Format) as a more viable universal format than ODF. He stated simply that, "ODF is not the open format with the open process we thought it was". Why is this significant? First, I think it speaks to how important the W3C is and has become over the past several years. The number of web standards in particular that have been formalized by the W3C is remarkable, whether they have been successful or not. Second, it (CDF) addresses an issue that I see on a daily basis in my role here at Compendium Blogware.
  • Gary Edwards on 19 Nov 07
     
    Wow!  Does Blake Matheny ever get it!  Maybe it's time for the W3C CDF Community to speak up?  
Gary Edwards

ConsortiumInfo.org - Putting the OpenDocument Foundation to Bed (without its supper) - ... - 0 views

www.consortiuminfo.org/...article.php

cdf odf ooxml w3c

shared by Gary Edwards on 14 Nov 07 - Cached
  • Here's what Chris Lilley had to say, reconstructed from my notes (in other words, this is not a direct quote): So we were in a meeting when these articles about the Foundation and CDF started to appear, and we were really puzzled.&nbsp; CDF isn't anything like ODF at all – it's an "interoperability agreement," mainly focused on two other specifications - XHTML and SVG.&nbsp; You'd need to use another W3C specification, called Web Interactive Compound Document (WICD, pronounced "wicked"), for exporting, and even then you could only view, and not edit the output.&nbsp; The one thing I'd really want your readers to know is that CDF (even together with WICD) was not created to be, and isn't suitable for use, as an office format.&nbsp; Here are some other takeaways from my conversation with Chris: Although they would be welcome to become members, Neither Gary, Sam nor Marbux are members of W3C or the CDF working group The W3C has never been contacted by anyone from the Foundation about CDF.&nbsp; After the articles began appearing, the W3C sent an inquiry to the Foundation, and received only a general reply in response The CDF working group was not chartered to achieve conversion between formats Although he hasn't spent a lot of time trying to unravel what Gary has written on the subject, he can't make any sense out of why the Foundation thinks that CDF makes sense as a substitute for ODF
Gary Edwards

okay ... seriously now ... what is this supposed to be? - 229 views

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...

OpenDocument

started by mazyar hedayat on 01 Sep 07 3 follow-ups, last by Gary Edwards on 16 Apr 08
Gary Edwards

Compound Document Formats (CDF) - W3C - 0 views

www.w3.org/...CDR-implementations.html

cdf da-vinci w3c

shared by Gary Edwards on 21 Oct 07 - Cached
  • Compound Documents by Reference (CDR) Implementation report. This is a preliminary implementation report for Compound Documents by Reference (CDR) WICD. It will be expanded in the course of the Candidate Recommendation phase.
  • Gary Edwards on 21 Oct 07
     
    Mid November
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.
Gary Edwards

OpenDocument Foundation drops support for ODF, backs obscure W3C format - Flock - 0 views

arstechnica.com/...-backs-obscure-w3c-format.html

cdf odf ooxml opendocment

shared by Gary Edwards on 31 Oct 07 - Cached
  • The OpenDocument Foundation has decided to end its support for OASIS's OpenDocument Format (ODF) and instead support W3C's Compound Document Format (CDF), which is currently described in the Web Integration Compound Document Core 1.0 draft. This move reflects growing concerns within the interoperability advocacy community about the long-term viability of both ODF and Microsoft's Office Open XML (OOXML).
Gary Edwards

The Future is CDF | Metaphorical Web - Kurt Cagle - 0 views

metaphoricalweb.blogspot.com

cdf ms-ooxml odf officeopenxml opendocument wicd

shared by Gary Edwards on 03 Dec 07 - Cached
  • As editing increasingly moves onto the web, its safe to say that the document of choice will be neither ODF nor OOXML, both of which gain their power on the basis of supporting legacy word processing systems. Instead, what seems to be emerging from the W3C is something that is not an office suite because it didn’t evolve from one, but that nonetheless is capable of most if not all of the same functions that office suite documents pose.
Gary Edwards

Play the tape!!! The W3C eMails to the Foundation tell a differenct story | OpenDocumen... - 0 views

talkback.zdnet.com/5208-10741-0.html

cdf ms-ooxml odf schepers w3c wicd

shared by Gary Edwards on 03 Dec 07 - Cached
  • An honest misunderstanding? Hardly! Play the tape! Instead of arguing about who said what when, let's just go to the record and see exactly what the W3C's Doug Schepers said to us in an eMail introducing himself. Keep in mind that we did not contact the W3C or Mr. Schepers. The following eMail was most welcome, but entirely unsolicited.
  • Gary Edwards on 03 Dec 07
     
    The W3C's Doug Schepers joins the discussion claiming that the Foundation misunderstood his eMail messages.   We say otherwise!

    There is of course one way to settle this: PLAY THE TAPE!

    So here it is.

    ~ge~

1 - 17 of 17
Showing 20▼ items per page