Skip to main content

Home/ Document Wars/ Group items tagged OASIS

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

State's move to open document formats still not a mass migration - 0 views

www.computerworld.com/...article.do

california iso lai massachusetts oasis odf officeopenxml ooxml opendocument openxml xml

shared by Gary Edwards on 12 Dec 07 - Cached
  • Only a tiny fraction of the PCs at Massachusetts government agencies are able to use the Open Document Format (ODF) for Office Applications, despite an initial deadline of this month for making sure that all state agencies could handle the file format.
    • Gary Edwards
      Gary Edwards on 12 Dec 07
       
      Hey, nice comments!
  • Gary Edwards on 12 Dec 07
     
    Eric Lai keesp pokign at that Massachusetts hornets nest. One of these days he's going to crack it open, and it will be back to square one for the ODF Community.  Still missing from his research is the infoamous 300 page pilot study and accompanying web site where comments and professional observations document a year long study concernign the difficulties of implementing ODF solutions and making the migration.  <br><br>

    The study was focused on OpenOffice, StarOffice, Novell Office, and a IBM WorkPlace prototype.<br><br>

    The results of the year long pilot have never seen the public light of day.  But ComputerWorld is one of the media orgs that successfully filed a court action to invoke the freedom of information act in Massachusetts.  How come they can't find the Pilot Study?<br><br>

    At the end of the pilot study period, Massachusetts issued their infamous RFi; the request for information regarding the possiblity of a ODF plugin for MSOffice!  Meaning, the Pilot Study did not go well for the heroes of ODF - OpenOffice, StarOffice, Novell Office and WorkPlace.  Instead, Massachusetts sought an ODF plugin that would no doubt extend the life of MSOffice for years to come.  No rip out and replace here folks!<br><br>

    ~ge~
Gary Edwards

BetaNews | Course Change for OpenDocument Developers Seen as Emerging Rift - 0 views

www.betanews.com/...1193761026

cdf odf ooxml opendocument

shared by Gary Edwards on 12 Dec 07 - Cached
  • A presentation made two weeks ago by two members of OASIS' OpenDocument technical committee, and founding members of the OpenDocument Foundation, made it clear that the foundation would be turning its attention away from developing the ODF format and translators for it. Instead, in a course change instigated as far back as last May, the Foundation is steering back toward a project launched in 1995 by the World Wide Web Consortium, in hopes of recapturing the momentum toward document interoperability for all existing word processor users.
  • Gary Edwards on 12 Dec 07
     
    Excellent coverage.  Fair and balanced, even as the storm lords of IBM thunder across the Web with rage, smear and slander.
Gary Edwards

Former OpenDocument advocates bolt for W3C standard | Martin Lamonica - 0 views

www.news.com/8301-10784_3-9806369-7.html

cdf iso ms-ooxml oasis odf opendocument openofficexml

shared by Gary Edwards on 12 Dec 07 - Cached
  • Adding a twist to a high-stakes conflict over document formats, some advocates for OpenDocument, or ODF, are abandoning the standard in favor of the World Wide Web Consortium's Compound Document Formats standard. The reason? Technical limitations in sharing ODF files with Microsoft Office applications.
  • Gary Edwards on 12 Dec 07
     
    Great comments!
Gary Edwards

ODF infighting could help Microsoft's OOXML - zdnet Mary Jo - 0 views

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

cdf iso microsoft ms-ooxml odf opendocuemnt

shared by Gary Edwards on 12 Dec 07 - Cached
  • As a result of the latest infighting, is Microsoft now all-but-guaranteed that OOXML will sail through the ISO standardization vote in Feburary 2008 because ODF — and its backers — will be in disarray? This has nothing to do with the outcome of the Ballot Resolution Meeting.
  • But we also oppose adoption of ODF 1.2 as an ISO standard in the form we expect it to emerge from OASIS.
    • Gary Edwards
      Gary Edwards on 12 Dec 07
       
      Bad phrasing. We would really like to see ODF 1.2 succeed at ISO, but this would require compliance with ISO Interoperability Requirements. Today, ODF 1.2 is not compliant with those requirements, and we fully expect it to be defeated at ISO due to the obvious shortcoming. In May of 2006, ISO Directorate issued a clear and unequivocal statement tha tODF must conform to ISO Interoeprability Requirements. ODF 1.2 work was closed in July of 2007, without the needed changes.
  • Matusow sounds reasonable only if you are not a file format congnoscenti. He uses an appeal to ignorance. A single universal set of formats is entirely feasible from a technical standpoint; e.g., the example of HTML. But the chances of getting there by opening application-specific formats are dim at best, as the ODF experience teaches. You might acquire an entirely different perspective if you spent some time viewing the short sets of slides from the IDABC Open Document Exchange Formats Workshop 2007, which laid down the market requirements for 21 European government IT national bodies. http://ec.europa.eu/idabc/en/document/6474 (.) I particularly recommend Dr. Barbara Held's report to the plenary session linked from this page, http://ec.europa.eu/idabc/en/document/6704/5935 and the four workshop reports linked from the bottom of this page, http://ec.europa.eu/idabc/en/document/6702/5935 (.) Those slides reflect a lot of careful research into the issue you and Matusow discuss.
  • Gary Edwards on 12 Dec 07
     
    Hey, great comments! 
Gary Edwards

IBM's Potempkin Village | Florian Reuter's Weblog - Flock - 0 views

florianreuter.blogspot.com/...ibms-symphony.html

ibm oasis odf odf-civil-war opendocument weird

shared by Gary Edwards on 12 Dec 07 - Cached
  • I think that contradicts the SISSL :-)
  • Gary Edwards on 12 Dec 07
     
    Recently IBM held a ODF Interoperability Workshop at the OpenOffice annual conference in Barcelona, Spain. The Workshop was organized by IBM's Rob Weir. In this blog, uber document processing expert Florian Reuter opens the lid for a peek at what really happened at the Workshop. And it wasn't "interoperability". As a Novell employee, Florian is unable to comment publicly as to what really happened in Barcelona. But to those who are not under IBM's oppressive thumb, the results of this fiasco are laughable. Sure IBM and Rob Weir are busy threatening individuals, and bribing the press to suppress the reality of this horrific ODF ZERO Interop demonstration. But that doesn't mean those who really care can't talk about it. The OpenDocument Foundation has of course been screaming about the ODF interop problems. But we've been focused on the big picture of world wide market requirements; the need for ODF to be compatible with existing file formats and interoperable with existing applications - including Microsoft documents and applications. Of course, this level of interoperability was outside the scope of ODF purpose and work. We apologize for daring to suggest that real world implementation issues are important and ought to be considered. but there remains the issue of ODF interoperability which also sucks beyond belief. The exact same principles apply. ODF interop depends on complete application independence, and ODF remains bound to OpenOffice. Now i'm someone who has publicly championed ODF interoperability. I've spent years championing the fact that ODF can meet all market requirements for interoperability. And whatever credibility i thought i might have is now destroyed by that very public and very in your face lack of interoperability.

    So here i am, with any credibility i might have ever had resting on the pretensions of a self proclaimed clown (a hef="http://wordnet.princeton.edu/perl/webwn?s=antic">his description not mine). Can R
  • Gary Edwards on 12 Dec 07
     
    Let's do this again:

    Recently IBM held a ODF Interoperability Workshop at the OpenOffice annual conference in Barcelona, Spain. The Workshop was organized by IBM's Rob Weir. In this blog, uber document processing expert Florian Reuter opens the lid for a peek at what really happened at the Workshop. And it wasn't "interoperability".

    As a Novell employee, Florian is unable to comment publicly as to what really happened in Barcelona. But to those who are not under IBM's oppressive thumb, the results of this fiasco are laughable. Sure IBM and Rob Weir are busy threatening individuals, and bribing the press to suppress the reality of this horrific ODF ZERO Interop demonstration. But that doesn't mean those who really care can't talk about it.

    The OpenDocument Foundation has of course been screaming about the ODF interop problems. But we've been focused on the big picture of world wide market requirements; the need for ODF to be compatible with existing file formats and interoperable with existing applications - including Microsoft documents and applications.

    Of course, this level of interoperability was way outside the scope of ODF purpose and work. We apologize for daring to suggest that real world implementation issues are important and ought to be considered. But there remains the issue of ODF interoperability which also sucks beyond belief.

    The exact same principles apply. ODF interop depends on complete application independence, and ODF remains bound to OpenOffice.

    Now i'm someone who has publicly championed ODF interoperability. I've spent years championing the fact that ODF can meet all market requirements for interoperability. And whatever credibility i thought i might have is now destroyed by that very public and very in your face lack of interoperability.

    So here i am, with any credibility i might have ever had resting on the pretensions of a self proclaimed clown (http://wordnet.princ
Gary Edwards

An Antic Disposition : Clowns, Criminals, Slanderers and the disguise of guilt - 0 views

erichmusick.com/...antic_disposition.html

oasis odf opendocument

shared by Gary Edwards on 12 Dec 07 - Cached
  • "Antic Disposition" Many criminal suspects today divert guilt from themselves by attributing their actions to some sort of insanity. Prince Hamlet, of Shakespeare's The Tragedy of Hamlet: Prince of Denmark, puts on a similar fake lunacy that eventually takes over Hamlet, controls him, and leads to his downfall.
  • Ophelia explains he possessed at one time a "noble mind" and was a "soldier," and a "scholar" – all the terms by which any young man at that time would like to be known (3.1.64). Now, though, Hamlet lashes out at others, speaks harshly with those to whom he is supposedly close, and even thoughtlessly kills a man.
    • Gary Edwards
      Gary Edwards on 12 Dec 07
       
      Ouch!
  • Though Hamlet fails to disclose his reasoning behind displaying the "antic disposition," his words and actions point to a few possible motives
    • Gary Edwards
      Gary Edwards on 12 Dec 07
       
      aha! Ulterior motives!
  • ...4 more annotations...
  • though this be madness, yet there is method in 't"
  • As his madness controls more and more of his life, Hamlet treats those whom he should treat with dignity and respect as if they were trash.
    • Gary Edwards
      Gary Edwards on 12 Dec 07
       
      Jody Goldberg, Miguel de Icaza, Michael Meeks, and the two guys without a garage at the Foundation
  • Hamlet vows to slander Ophelia
    • Gary Edwards
      Gary Edwards on 12 Dec 07
       
      There you go!
  • If Hamlet had never put on the "antic disposition," he may not have gotten revenge, but the play would not have ended in tragedy – Hamlet, himself, as well as those he loved, would not have died.
  • Gary Edwards on 12 Dec 07
     
    Who knew?  :)

    Hey buddy can you spare me a garage?

Gary Edwards

IBM In Denial Over Lotus Notes - Forbes.com - 0 views

www.forbes.com/...cz_dl_0406notes.html

exchange ibm lotus microsoft

shared by Gary Edwards on 12 Dec 07 - Cached
  • The marketing folks in IBM's Lotus division are starting to sound like the Black Knight in Monty Python and the Holy Grail, who insists he's winning a fight even as he loses both arms and legs: "'Tis but a scratch," the Black Knight declares after one arm is lopped off. "Just a flesh wound," he says after losing the other. "I'm invincible!" The same goes for IBM's (nyse: IBM - news - people ) Lotus, which keeps declaring victory even as Microsoft (nasdaq: MSFT - news - people ) carves it up.
  • Gary Edwards on 12 Dec 07
     
    Want to know the real reason why IBM and Microsoft are going at it hammer and tong over document formats?  Here it is.  Lotus Notes is getting clobbered by the Exchange/SharePoint juggernaut. 

    The article is old, but the point is well taken.  Today the Exchange/SharePoint juggernaut i sover 65% marketshare.  IBM is struggling to protect the Lotus Stack against an impossible foe.

    The thing is, Microsoft E/S will ALWAYS have better integration with the MSOffice - Outlook desktop monopoly base (550 M and counting).  Most of this "integration" is due to the high fidelity exchange of documents in Microsoft's proprietary XML mode known as MS-OOXML.   Forget the charade that MS-OOXML is an open standard called Ecma 376.  MSOffice and infamous XML Compatibility Pack Plug-in do not implement Ecma 376.  The Pack implements MS-OOXML.

    One key differnece between MS-OOXML and Ecma 376 us that MS-OOXML is infused with the Smart Tags components.  These are for metadata, data binding, data extraction, workflow, intelligent routing and on demand re purposing of docuemnt components.  In effect, MS-OOXML :: Smart Tags combines with proprietary .NET Libraries, XAML and soon enough Silverlight to replace the entire span of W3C Open Internet Technologies. 

    Can you say "HTML"?

    Okay, so why does this matter to IBM and the future of Lotus Notes?

    The end game of the document format wars is that of a stack model that converges desktop, server, devices and web information systems.  The MS Stack uses MS-OOXML as the primary transport of accelerated content/data/multi media streams running across the MS Stack of desktop, server, device and web application systems.  It's the one point of extreme interoperability.

    It's also a barrier that no non MS applicatio or service can penetrate or interoperate with except on terms Microsoft dictates. 
Gary Edwards

Brendan's Roadmap Updates: My @media Ajax Keynote - 0 views

weblogs.mozillazine.org/...my_media_ajax_keynote.html

shared by Gary Edwards on 11 Jan 08 - Cached
  • Standards often are made by insiders, established players, vendors with something to sell and so something to lose. Web standards bodies organized as pay-to-play consortia thus leave out developers and users, although vendors of course claim to represent everyone fully and fairly. I've worked within such bodies and continue to try to make progress in them, but I've come to the conclusion that open standards need radically open standardization processes. They don't need too many cooks, of course; they need some great chefs who work well together as a small group. Beyond this, open standards need transparency. Transparency helps developers and other categories of "users" see what is going on, give corrective feedback early and often, and if necessary try errant vendors in the court of public opinion.
    • Gary Edwards
      Gary Edwards on 11 Jan 08
       
      Brendan's comment about the open standards process and the control big vendors have over that process is exactly right. The standards contsortia are pay to play orgs controlled entirely by big vendors. OASIS and the OpenDocuemnt Technical Committee are not exceptions to this problematic and troublesome truth.
      The First Law of the Internet is that Interoperability trumps everything - including innovation. The problem with vendor driven open standards is that innovation ontinually trumps interoperability. So much so that interop is pretty much an after thought - as is the case with ODF and OOXML!
      The future of the Open Web will depend on open source communities banding together with governemnts and user groups to insist on the First Law of the Internet: Interoeprability. If they don't, vendors will succeed in creating slow moving web standards designed to service their product lines. Vendor product lines compete and are differentiated by innovative features. Interoeprability on the other hand is driven by sameness - the sharing of critical features. Driving innovation down into the interop layer is what the open standards process should be about. But as long as big vendors control that process, those innovations will reside at the higher level of product differentiation. A level tha tcontinues to break interoperability!
Gary Edwards

Debate Simmers on Why ODF Shuttered its Doors - Peter Galli eWEEK - 0 views

www.eweek.com/...0,1759,2223042,00.asp

cdf galli good ms-ooxml odf

shared by Gary Edwards on 12 Dec 07 - Cached
  • Did the OpenDocument Foundation recently shutter its doors for good because it was unable to convince Oasis to support its converter, known as Da Vinci? Or was it because OpenDocument Format was simply not designed for the conversion of Microsoft Office documents, applications, and processes?
Gary Edwards

Ripped Off by Rob Weir - Again - 0 views

www.robweir.com/...nd-and-monicas-blue-dress.html

cdf da-vinci hamlet ibm massachusetts odf ooxml opendocument pdf pilot rfi weir

shared by Gary Edwards on 12 Dec 07 - Cached
  • An intriguing idea is whether we can have it both ways. Suppose you are in an ODF editor and you have a "Save for archiving..." option that would save your ODF document as normal, but also generate a PDF version of it and store it in the zip archive along with ODF's XML streams. Then digitally sign the archive along with a time stamp to make it tamper-proof. You would need to define some additional access conventions, but you could end up with a single document that could be loaded in an ODF editor (in read-only mode) to allow examination of the details of spreadsheet formulas, etc., as well as loaded in a PDF reader to show exactly how it was formated.
  • Gary Edwards on 12 Dec 07
     
    Intriguing?  Rob Weir knows full well that the Foundation proposed this exact same feature set as part of the da Vinci Plug-in design for Massachusetts, July of 2006!!!!!!!!!

    The Complete Feature list of the da Vinci plug-in for MSOffice that was proposed and signed off on by CIO Louis Gutierrez in early August of 2006 was well known by IBM's representatives who were working hand in hand with us at the time: Rob Weir, Don Harbison and Doug Heintzman. 

    Louis Gutierrez had asked IBM and Oracle to create a "benefactors Group" to overcome the challenge that Massachusetts ITD did not have a budget.  IBM and Oracle selected Google, Sun, Novell, Intel, and Nokia as key benefactors.  The group was provided with the complete feature set and roadmap for da Vinci development. 

    The da Vinci roadmap was the schedule announced by Louis Gutierrez in his mid year report, August 17th, 2006.

    The da Vinci plug-in feature set, in order of priority, consisted of:
    ODF iX Approval at OASISPlug-in for MS WORDAccessibility Interface for all ODF documents in MS WordPDF - ODF iX Digital Signature containerPlug-in for MS ExcelInteroperability Wizard for OpenOfficePlug-in for PowerPointXForms InterfaceThe roadmap we provided Louis and the "benefactors" was sceduled out with deliverables, test periods, and cost per deliverable.  The buy-in per "benefactor" was set at $350,000, and i
Gary Edwards

Linux Foundation Legal : Behind Putting the OpenDocument Foundation to Bed (without its... - 0 views

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

cdf foundation odf ooxml updegrove

shared by Gary Edwards on 12 Dec 07 - 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 12 Dec 07
     
    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

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

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

cdf foundation maryjo odf ooxml w3c wicd zdnet

shared by Gary Edwards on 12 Dec 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

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 12 Dec 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 12 Dec 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

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

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

cdf odf ooxml opendocument updegrove w3c

shared by Gary Edwards on 12 Dec 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

ODF 1.2 Metadata? You're Dreaming! Microsoft starts rolling out more OOXML translators... - 0 views

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

cdf ge mary-jo metadata microsoft odf ooxml opendocument shish

shared by Gary Edwards on 12 Dec 07 - No Cached
  • Sorry Shish, you're wrong about ODF 1.2 Try ODF 1.5 or ODF 2.0, maybe. The metadata requirements for ODF 1.2 actually did include two way lossless translation capability. Unfortunately these features did not survive the final cut, and were not included in the April 2007 submission. You might also want to check the February 23, 2007 metadata proposal from Florian Reuter. That also would have delivered the goods and perhaps put ODF that grand convergence category of usefulness across desktops, servers, devices and web systems currently the exclusive domains of MS-OOXML and CDF+. Florian had devised a means of using metadata to describe the presentation aspects of content and structural objects. Very revolutionary. And based on the simple notion that bold, font, margins etc. are simply metadata about content and style objects. Where the train came off the track had to do with the concept of an XML ID means of linking metadata to content. Not that there was anything wrong with this mechanism. It's actually quite clever. What went wrong was that Sun insisted that only those elements approved and supported by OpenOffice would be allowed to make use of XML ID metadata. For independent developers, this is a serious constraint. Because of this constraint, the metatdata sub committee started off with six elements supported by OOo that metadata could be appied to. IBM then came in and asked for eleven more elements having to do with charts and graphs. The OpenOffice crew decided they could support this, so in they went. Then an interesting question was posed, "How are independent developers supposed to submit elements for metadata consideration?"
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 12 Dec 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 12 Dec 07
       
      This will make marbux happy!
  • Gary Edwards on 12 Dec 07
     
    Now this is interesting.  I wonder if IBM and the OASIS Lawyer have seen this page?
Gary Edwards

Open Document Foundation Dumps ODF for CDF - Open for Business - Lora Bentley - 0 views

www.itbusinessedge.com/...osb

cdf odf ooxml w3c

shared by Gary Edwards on 12 Dec 07 - Cached
  • Five years after it was formed specifically to promote OpenDocument Format as an alternative to Microsoft Office formats, those behind the Open Document Foundation are abandoning the OASIS- and ISO-approved document standard in favor of the World Wide Web Consortium’s Compound Document Format.
Gary Edwards

BetaNews | Course Change for OpenDocument Developers Seen as Emerging Rift - Scott Fulton - 0 views

www.betanews.com/...1

cdf odf ooxml w3c

shared by Gary Edwards on 12 Dec 07 - Cached
  • A presentation made two weeks ago by two members of OASIS' OpenDocument technical committee, and founding members of the OpenDocument Foundation, made it clear that the foundation would be turning its attention away from developing the ODF format and translators for it. Instead, in a course change instigated as far back as last May, the Foundation is steering back toward a project launched in 1995 by the World Wide Web Consortium, in hopes of recapturing the momentum toward document interoperability for all existing word processor users.
Gary Edwards

ODF and differences of opinion | TalkBack on ZDNet - 0 views

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

cdf odf ooxml w3c

shared by Gary Edwards on 12 Dec 07 - Cached
  • Just because we are garage challenged doesn't mean we can't find the back door to the big house :) The larger issue at stake here is not whether or not we have a garage, or what our contribution to ODF has been over the course of five years as active members of OASIS ODF. What it really comes down to is the implementation of ODF in the real world.
  • Gary Edwards on 12 Dec 07
     
    Lengthy comment explaining once again why we moved from ODF to CDF. 
Gary Edwards

Whoops?! IBM products support Microsoft's Open XML doc format! Lotushpere - 0 views

www.computerworld.com/...article.do

cdf ibm iso oasis odf ooxml opendocument openoffice sun symphony

shared by Gary Edwards on 20 Jan 08 - Cached
  • Nobody has invested more to defeat Microsoft Corp.'s Open XML document format than IBM Corp. So why is IBM supporting Open XML in a handful of its products? According to technical documentation on IBM's own Web sites, Big Blue already supports Open XML, the native file format of Microsoft Office 2007, in at least four of its software. However, Microsoft Office users interested in testing or switching to Lotus Symphony, IBM's upcoming challenger to Office, may be disheartened by signs that IBM won't budge from its stance that it will only support documents created in Office 2003 and prior versions.
« First ‹ Previous 101 - 120 of 166 Next › Last »
Showing 20▼ items per page