Skip to main content

Home/ OpenDocument/ Group items tagged open

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Alan Cox on open-source development vs. proprietary development | The Open Road - The B... - 0 views

erichmusick.com/...antic_disposition.html

oasis odf opendocument

shared by Gary Edwards on 24 Oct 07 - Cached
  • 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 24 Oct 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 24 Oct 07
       
      aha! Ulterior motives!
  • though this be madness, yet there is method in 't"
  • ...3 more annotations...
  • 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 24 Oct 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 24 Oct 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

Can IBM save OpenOffice.org from itself? - 0 views

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

shared by Gary Edwards on 11 Jan 08 - Cached
  • OpenOffice.org's biggest foe may be Microsoft Office, but critics say the open-source organization has, from its inception, also been one of its application suite's own worst enemies -- a victim of a development culture that differs radically from the open-source norm. Observers now wonder if IBM's entry into OpenOffice.org can make the necessary changes.
    • Gary Edwards
      Gary Edwards on 11 Jan 08
       
      good article from Eric Lai of ComputerWorld. Written on the eve of the infamous Barcelona OpenOffice.org developers conference, Eric argues that OOo isn't a real open source community. Instead, OOo is a owned and operated by Sun.
      One of the more important control points Sun insists on is that of commit rights and project managers. Only Sun employees have these rights and can hold these important positions..
      The more important point is made by Marbux (below: ODF is an application specific format designed exactly for OpenOffice. While other applications might partially implement ODF, interoperability and successful ODF document exchange require the OOo code base!
      From Marbux: This is the only article I've found to date where IBM (Heintzman) flat out says IBM wants changes in OOo licensing, more in line with the Eclipse and Apache licenses. See pg. 2. Significant because it feeds the meme that IBM's own ODF-based development goal is proprietary closed source built on the OOo code base, e.g., Symphony, et cet.
      And that has huge signficance once you realize that ODF is not the real standard; the OOo code base is the real ODF standard. Look around the world and you see that ODF adoption decisions by governments are all in reality decisions to go with StarOffice, OOo, or OOo clones. I haven't, for example, seen a single instance where a government decided to ride with KOffice. Why would they, with the interop issues between KOffice and OOo? The fact that OOo's code base is the real ODF standard will figure strongly in the comments. Couple it with Sun's iron-fisted control of the OOo code base, and you have vendor lock-in with a Microsoft partner.
      But with 70 developers committed in China, where developers salaries are inexpensive, IBM will soon be in a position to threaten to fork the OOo code base using proprietary extensions. Is that their real tactic to force changes in licensing and gov
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 06 Nov 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

Novell adds fuel to the fire in OOXML feud - News - Builder AU - 0 views

www.builderau.com.au/...0,339028227,339284338,00.htm

shared by Gary Edwards on 11 Dec 07 - Cached
  • Microsoft has created its own proprietary document format, Office Open XML (OOXML), as a rival to the community-developed OpenDocument Format (ODF). OOXML is used in Microsoft's latest applications suite, Office 2007. Despite some efforts by the two camps, ODF and OOXML are, for the most part, not interoperable, meaning documents that are created in one format cannot be successfully read by applications based on the other format. According to Novell's vice president of developer platforms, Miguel de Icaza, the situation won't change in the foreseeable future. Want to know more? For all the latest news, analysis and opinion on open source, click here "There's no end in sight to the ongoing disputes between the two camps," said de Icaza, speaking at XML 2007, a Microsoft-sponsored event, on Tuesday. "In 2006, there was lots of FUD [fear, uncertainty and doubt] about the problems behind OOXML and it went downhill from there," Icaza said. "Neither group is willing to make the big changes required for real compatibility," de Icaza added.
    • Gary Edwards
      Gary Edwards on 11 Dec 07
       
      What efforts are you talking about? The last time any effort was made to accomodate interoperability was in 2003 with the establishment of the ODF "Compatibilty clause" (Section 1.5). "Despite some efforts by the two camps, ODF and OOXML are, for the most part, not interoperable, meaning documents that are created in one format cannot be successfully read by applications based on the other format......" Section 1.5 authorizes the use of "foreign elements" and "alien attributes". These techniques were specifically written into ODF for handling unknown characteristics of existing MSOffice documents (binary and/or xml) on conversion to ODF. Since the Section 1.5 addition in 2003, every other suggestion to improve interop between ODF and MSOffice documents has been rejected by the OASIS ODF TC and Sub Committees. There are three problems with Section 1.5. The first is that there is only so much that can be done with foreign elements and alien attributes. There are still remaining compatibility issues relating to the basic structures of lists, tables, fields, sections and page dymnamics. The OpenDocument Foundaiton spent over a year trying to get approval for five generic elements relating to these structures, without success. As i said, there has not been a single successful comatibility - interoperability effort since 2003, although many have been proposed. The second reason for the failure of Section 1.5 is that OpenOffice only partially implements the "Compatibility Clause". OOo only recognizes "foreign elements and alien attributes" with text spans and paragraphs. The third reason is that "compatibility" is optional in ODF. The clause does not have any teeth. Applications can implement only those aspects of the spec they feel like implementing, and still be in total "compliance". This creates serious interop problem not only for MSOffice plug-in comverted documents, but also renders as
Gary Edwards

Microsoft Details Open Document Format Support For Office -- Microsoft Office -- Inform... - 0 views

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

shared by Gary Edwards on 16 Dec 08 - Cached
  • Gary Edwards on 16 Dec 08
     
    With the release of documentation Tuesday describing the company's implementation of the Open Document Format in Office 2007 Service Pack 2, Microsoft (NSDQ: MSFT) continues to deliver tangible results of a set of interoperability principles it announced in February 2008. Microsoft unveiled a Web site that goes into great detail about how Microsoft will implement ODF in Office, describing things like how Word does text formatting, how it determines and sets margins in ODF documents, or what font weight gradations describe bold and normal text. Though Microsoft doesn't have default ODF support in Office 2007, it will add support in Office 2007 SP2 (service pack 2).
Paul Merrell

Matusow's Blog : Open XML, ODF, PDF, and XPS in Office - 0 views

blogs.msdn.com/...odf-pdf-and-xps-in-office.aspx

shared by Paul Merrell on 22 May 08 - Cached
    • Paul Merrell
      Paul Merrell on 22 May 08
       
      Whoopee! Everyone gets to add vendor-specific extensions to standards like ODF to enable some quality of Sharepoint/Exchange/Outlook interop in their apps, just as soon as Microsoft gets around to offering adequate specfications. History teaches that may be a very long time, and of course the relevant Microsoft patent RAND terms apply, because the disclosures are made outside the context of a standard that requires otherwise. And of course the OASIS RF on RAND policy does not forbid new ODF features subject to RAND terms and the policy is silent on the subject of vendor-specific extensions. Methinks FOSS may have just lost its "open standard" ODF.
  • Office is NOT implementing ODF 1.0 from ISO. That spec is not representative of the marketplace today, it is not what is implemented in OpenOffice, it is not what IBM is using for Symphony, and it is not referenced in the Massachusetts ETRM policy.
    • Paul Merrell
      Paul Merrell on 22 May 08
       
      As I have been arguing, there are no full featured implementations in existence of the ISO/IEC:26300 OpenDocument standard and every government that has adopted the international standard as its own internal standard or procurement specification is subject to legal challenge because of the lack of implementations.
  • In my opinion, the continued interest in innovation presented by those solutions will speak much louder than the formats themselves.
    • Paul Merrell
      Paul Merrell on 22 May 08
       
      You can have standards and you can have innovation. But you can't have interop if you embrace and extend standards. The need for stable, fully-specified formats for document interchange purposes apparently is not part of Microsoft's plan. Scant wonder, neither ODF nor OOXML is designed for document interchange among competing vendors' apps. They are both standards designed to allow a single vendor to maintain dominant market share among implementors of those standards. Microsoft will soon diominate market share in both so-called "standards." The embrace of a standard is necessary to extend and extinguish it.
  • ...3 more annotations...
  • While this is a big deal announcement for the Office product team (check out Doug Mahugh's blog), my take on it is predictably focused on the longer-term interoperability factors.
  • the API that will allow ANY document format to register itself with Office and be set as the default will be made available as planned. Additionally, the work with DAISY and other specialized document formats will move forward as well.
    • Paul Merrell
      Paul Merrell on 22 May 08
       
      I was wrong. The API is for more than ODF plugo-ins.
  • The documentation of client/server protocols for Office-related technologies (such as SharePoint and Exchange/Outlook communications) will remain available to the public.
  • Paul Merrell on 22 May 08
     
    "Clearly the Press Announcement today from Microsoft will bring about another wave of discourse on the future of document formats. " Jason Matusow presents the long-term view of the announcement's significance.
Paul Merrell

Doug Mahugh : Office support for document format standards - 0 views

blogs.msdn.com/...document-format-standards.aspx

interop microsoft odf strategy

shared by Paul Merrell on 22 May 08 - Cached
  • Third-party translators. We anticipate that some developers may want to take over the default ODF load and save paths, so that they can plug in their own translators for ODF, and we'll be providing an API in SP2 that enables this scenario. This means that if a developer disagrees with the details of our approach and would like to implement ODF for Office in a different way, they're free to do so and can set it up such that when a user opens an ODT attached to an email or from their desktop, it will be loaded through their ODF code path.
    • Paul Merrell
      Paul Merrell on 22 May 08
       
      The Third-party translators discussion of the forthcoming new API suggests that it is for ODF only, and thereby implicitly that it will not be a tool for accessing the full functionaolity of MS Word, i.e., that only the functionality specified in ODF 1.1 will be available. E.g., no control of Sharepoint functionality or manipulation of the Microsoft cloud through the API from OpenOffice.org via ODF. .
    • Jesper Lund Stocholm
      Jesper Lund Stocholm on 23 May 08
       
      The Microsoft cloud depends heavily on OOXML, and that is likely not going to change. Are you saying that you'd prefer a plug-in mechanism in SharePoint as well? I believe the protocols used by SharePoint are included in the specs now provided. Won't that do (apart from the non-commercial usage of the specs)
  • If you're an Office 2007 user, the image above probably looks pretty familiar. But look close, and you'll see some Save-As options you've not seen before here: OpenDocument, and (unless you have the existing add-in) PDF & XPS.
  • There is new information today about the planned release of v2.0 of the ODF translator on the ODF translator team blog. The SourceForge translator projects will continue to move forward, and Microsoft will continue to be an active participant in these projects.
  • ...2 more annotations...
  • This is a screen shot of a pre-release copy of SP2 (Service Pack 2) for the 2007 Microsoft Office System, showing the new document format standards that we'll be supporting starting with SP2.
    • Paul Merrell
      Paul Merrell on 23 May 08
       
      Hi, Jesper. according to another article I found later, the new APIs (I assume it should be plural rather than singlular) will allow addition of formats other than ODF, so I apparently got that part wrong. On the Sharepoint example, I wasn't sufficiently clear and apologize. Assume you create a document in MS Office that invokes Sharepoint functionality, then you save it as ODF and ship it off to a co-worker using OOo. The OOo user wants to send it back to you for further processing. But if saving to ODF in Office wipes the Sharepoint metadata, you've got data loss on the outbound trip. The path you suggest would work at least in theory (I haven't heard any reports yet of the documentation on the Sharepoint APIs) if Sharepoint were used as an intermediary hub. But the Sharepoiint document may not be accessible to the co-worker, e.g., because of page security settings. I anticipate that there would be many cases where only one end of the trip has access to the hub, so there's a need to keep the path open that bypasses the hub and for it to be non-lossy. There is an article on BetaNews by Scott Fulton that interviews a couple of the Softies. They said that there will be lots of Office functionality that won't be able to be saved in ODF, that they're not planning a compatability mode that would block use of features that can't be saved to ODF, and that they're not planning to go beyond the features specified in ODF 1.1. So if they carry through on what they said, the outbound trip to ODF implementations will be lossy. I think the real problem with the Sharepoint specs and other documentation Microsoft is releasing is that it isn't in a standard where a technical committee could say yea or nay on whether it is suffiiciently specific and where the specs can be made vendor-neutral. In other words, that Micrsooft is in control of the specifiation rather than a standards body. Microsoft got away so far with creating a de facto standard for the line of business functional
    • Paul Merrell
      Paul Merrell on 23 May 08
       
      Hi, Jesper. according to another article I found later, the new APIs (I assume it should be plural rather than singlular) will allow addition of formats other than ODF, so I apparently got that part wrong. On the Sharepoint example, I wasn't sufficiently clear and apologize. Assume you create a document in MS Office that invokes Sharepoint functionality, then you save it as ODF and ship it off to a co-worker using OOo. The OOo user wants to send it back to you for further processing. But if saving to ODF in Office wipes the Sharepoint metadata, you've got data loss on the outbound trip. The path you suggest would work at least in theory (I haven't heard any reports yet of the documentation on the Sharepoint APIs) if Sharepoint were used as an intermediary hub. But the Sharepoiint document may not be accessible to the co-worker, e.g., because of page security settings. I anticipate that there would be many cases where only one end of the trip has access to the hub, so there's a need to keep the path open that bypasses the hub and for it to be non-lossy. There is an article on BetaNews by Scott Fulton that interviews a couple of the Softies. They said that there will be lots of Office functionality that won't be able to be saved in ODF, that they're not planning a compatability mode that would block use of features that can't be saved to ODF, and that they're not planning to go beyond the features specified in ODF 1.1. So if they carry through on what they said, the outbound trip to ODF implementations will be lossy. I think the real problem with the Sharepoint specs and other documentation Microsoft is releasing is that it isn't in a standard where a technical committee could say yea or nay on whether it is suffiiciently specific and where the specs can be made vendor-neutral. In other words, that Micrsooft is in control of the specifiation rather than a standards body. Microsoft got away so far with creating a de facto standard for the line of business functional
  • Paul Merrell on 22 May 08
     
    "This is a screen shot of a pre-release copy of SP2 (Service Pack 2) for the 2007 Microsoft Office System, showing the new document format standards that we'll be supporting starting with SP2."
  • Jesper Lund Stocholm on 23 May 08
     
    "This is a screen shot of a pre-release copy of SP2 (Service Pack 2) for the 2007 Microsoft Office System, showing the new document format standards that we'll be supporting starting with SP2."
Paul Merrell

Brian Jones: Open XML Formats : More on yesterday's ODF announcement - 0 views

blogs.msdn.com/...terday-s-odf-announcement.aspx

interop microsoft strategy

shared by Paul Merrell on 22 May 08 - Cached
  • Paul Merrell on 22 May 08
     
    "Even though ODF 1.0 is the official ISO version of the format, the decision was made to use version 1.1 which had some accessibility improvements. Hopefully future versions of ODF will be brought back to ISO so that we have a more current ISO version soon. You also may have noticed that we as Microsoft plan to start participating in the ODF standardization efforts, whether that happens in OASIS or ISO. ... I've heard different opinions though on what to do if the standard says one thing and Open Office does something else. I think the right thing to do is to follow the standard, but I'd be curious to hear what other folks have to say." Note that this Jones post includes several links to commentary on the ODF support announcement written by other Softies
Gary Edwards

Forget file formats. The battle is Sharepoint | The Open Road - The Business and Politi... - 0 views

www.cnet.com/8301-13505_1-9949736-16.html

microsoft oasis odf ooxml sharepoint

shared by Gary Edwards on 22 May 08 - Cached
  • People are agog that Microsoft has announced support for Open Document Format (ODF), but I'm not sure why. This was a foregone conclusion once Microsoft figured out how to move lock-in above the file level to the content network. In other words, to Sharepoint. Microsoft has been hell-bent on getting enterprises to dump content into its proprietary Sharepoint repository, calling it the next Windows operating system. I call it the future of Microsoft lock-in.
Paul Merrell

Is our idea of "Open Standards" good enough? Verifiable vendor-neutrality - O'Reilly XM... - 0 views

www.oreillynet.com/...ur_idea_of_open_standards.html

dita docbook interop jelliffe odf ooxml uof vendor neutrality

shared by Paul Merrell on 23 May 08 - Cached
  • Paul Merrell on 23 May 08
     
    In light of the Microsoft announcement of ODF support, a prescient July, 2007 blog article by Rick Jelliffe deserves revisiting. Jelliffe surveyed the pressure points for various players that he saw in the File Format War and made a set of suggestions that bear a remarkable resemblance to subsequent events. The goal he recommended for eGovernment and open standards advocates was to push to get ODF and OOXML out of the hands of Ecma and OASIS and into the hands of ISO for harmonization work, arguing that it is the most vendor-neutral eligible forum for such work.
Paul Merrell

The No. 4 Reason to Move to Open Source is the Reduced Cost - 0 views

blogs.sun.com/...the_no_4_reason_to

OOo market penetration

shared by Paul Merrell on 31 May 09 - Cached
  • Open source enterprise products are ready to support your mission critical applications, in the operating system area there's Solaris, Linux, in the middleware area there's Glassfish, JBoss, in the database area there's MySQL, PostgreSQL and even in the desktop area...which has been lagging behind in open source, but is starting to gain some ground with over 220 Million OpenOffice users.
  • Paul Merrell on 31 May 09
     
    Sun claims there are 220 million OpenOffice.org users.
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

Re: [office-metadata] Suggested Changes on the Metadata proposal - 0 views

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

conformance interoperability metadata odf-tc

shared by Gary Edwards on 23 Aug 07 - Cached
  • - A metadata aware ODF implementation *shall* not remove the xml:id attributes defined in sections [?] or change its values unless the removal or modification is the result of an edit operation caused be the user, or a similar action taken by some automatic processing of the document.
    • Gary Edwards
      Gary Edwards on 23 Aug 07
       
      The road to universal interoperability! Document exchange demands that applications preserve information that other applications need.
  • Gary Edwards on 23 Aug 07
     
    Surprising post from Sun's Michael Brauer supporting the mandatory "shall - must" preservation of the metadata XML:id. Preservation of metadata information is critical to the high fidelity "round trip" interoperable exchange of ODF documents.

    Marbux is currently locked into a raging interoperability battle with the ODF Metadata Sub Committee where it's been proposed that preservation of metadata be optional!

    The entire thread is located here:
    ODF-Metadata-Proposal-22August2007

    This is one worth watching. The fight to limit ODF interoperability continues. Marbux is a distinguished Universal Interoperability expert with a blazing background in International Trade Agreements and anti trust based on interoperability violations.
Gary Edwards

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

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

shared by Gary Edwards on 09 Jun 07 - Cached
  • June 08, 2007 (Computerworld) -- 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 on 09 Jun 07
     
    Use of ODF remains minimal on government PCs in Massachusetts
    Eric Lai ....... June 8, 2007

    Bummer!  Do you think IBM is silent on this because they are busy cutting sweetheart deals with MS?  Are they going to hang Sun on this?  I'm sure that by next week IBM will have to respond to ODEF.   This just keeps getting better.  So in both Texas and California they wonder if it's even possible to implement ODF solutions.  No one wants to get into that hole with Massachusetts.

    ~ge~


Gary Edwards

Knowledge base - 0 views

opendocument.xml.org/...21

shared by Gary Edwards on 07 Jun 07 - Cached
  • he OpenDocument Format (ODF) is an open XML-based document file format for office applications to be used for documents containing text, spreadsheets, charts, and graphical elements. The file format makes transformations to other formats simple by leveraging and reusing existing standards wherever possible. As an open standard under the stewardship of OASIS, ODF also creates the possibility for new types of applications and solutions to be developed other than traditional office productivity applications.
  • Gary Edwards on 07 Jun 07
     
    The Knowledge Base description and history of OpenDocuemnt
Gary Edwards

EU-IDABC ODEF Workshop 2007 in Berlin - Documentation - presentations - 0 views

ec.europa.eu/...5935

california davinci interop iso massachusetts oasis odef odf ooxml opendocument politics xml

shared by Gary Edwards on 09 Jun 07 - Cached
  • As information exchange in and with public administrations is very often bound to documents, editing, archiving and exchange possibilities for documents are crucial for the optimum function of administrations, both in terms of practicality and cost. Initiatives such as the PEGSCO Recommendations on Open Document Formats published by the IDABC Management Committee, demonstrate public administrations preference for "open" document exchange and storage formats that are subject to formal standardisation via international standardisation procedures.   The primary objectives of the Berlin event, held at the German Federal Ministry of the Interior (BMI), were to: compile further input from Member State public administrations on their experiences and strategies on ODEF gather industry viewpoints on the initiatives relating to ODEF standardization and information on future standardisation developments provide a platform for exchange between stakeholders in public administrations and main industry players The program of the workshop included, among other: ODEF Strategies: Examples from European Administration Practical Experiences with the implementation of ODEF Report on ODEF-Standardisation activities  4 parallel sessions with participants   A panel discussion with stakeholders 
  • IDABC ODEF Workshop 2007 in Berlin
  • Gary Edwards on 09 Jun 07
     
    ODF officially died on February 28, 2007, at the Advanced eGovernment Conference in Berlin.  Hellow ODEF
Gary Edwards

Suggested ODF1.2 items - 0 views

www.oasis-open.org/...msg00048.html

shared by Gary Edwards on 09 Jun 07 - Cached
  • Subject: Suggested ODF1.2 items From: "Florian Reuter" <freuter@novell.com> To: <office@lists.oasis-open.org> Date: Mon, 20 Nov 2006 17:03:24 +0100 Suggested enhancement for OpenDocument V1.2
    • Gary Edwards
      Gary Edwards on 09 Jun 07
       
      This message was submitted to the ODF-OOo/SO OASIS TC the day Florian joined Novell. His Novell contract allowed him to continue his work as the OpenDcoument Foundation's CTO. Take note of the response from Sun's Michael Brauer. It's a classic. The link is at the bottom of the page. ~ge~
  • Gary Edwards on 09 Jun 07
     
    Part of the sad but enduring "History of Failed ODF Interoperability Attempts".  This particular message is dated November 20th, 2006. 

    The OpenDocument Foundation was notified a week earlier that the "benefactor" ODF Community group Louis Gutierrez had asked IBM and Oracle to put together in Massachusetts had failed.  This was the group Louis formed around the da Vinci plugin and our InfoSet APi. 

    Florian has been hired by Novell, and his first day on the job he finds out about the IBM - Novell deal with Microsoft.  Now he has write the MOOXML plugin for OpenOffice using the MS-CleverAge Translator Project work.  So he writes this message to the ODF TC [office] list. 

    The interoperability enhancements Florian suggests are based on the <interoperability eXtensions> submitted in August to the ODF Metadata SC for consideration.

    The first element in this list tha tFlorian chose to tackle related to "Lists".  He called it the "LIst Override Proposal".  This became the now infamous "List Enhancement Proposal War" that resulted in Sun having OASIS boot out the Foundation.

    Such is life in big vendor ODF'dom

    ~ge~

Gary Edwards

Microsoft Partners with Atlassian & NewsGator - SharePoint Goes Web 2.0 - Flock - 0 views

www.readwriteweb.com/...ft_partners_with_atlassian.php

exchange html ms-ooxml sharepoint w3c web20

shared by Gary Edwards on 20 Oct 07 - Cached
  • 4) Linking; Within Confluence, users can access SharePoint document facilities. By including SharePoint lists and content within Confluence, users can (in a single click) edit Microsoft Office documents.
  • Gary Edwards on 20 Oct 07
     
    Pay close attention here boys and girls because here it is.  Wonder why Microsoft is wealing, dealing and ready to shell out billions for Web 20 collaboration software?  It's to tie them into the MS Stack of MSOffice, IE, Exchange/SharePoint, MS LIve, MS Dynamics, MS SQL Server, etc.

    Grand convergence is the convergence of desktop, server, device and web systems.  It increasing looks like were going to have to live with the MS Stack and the Open Stack of grand convergence interoperability.  One will be able to have perfect interop within it's walls, with all applications able to handle the same compound XML document.  The other will be totally unable to implement an inteoperable version of MS-OOXML. 

    Members of the MS Stack will be able to access everything in the Open Stacks, but outside systems will have limited (crippled) access into the MS Stack.  Embrace, Extend, Extinguish.  Here we go again.

    ~ge~



Gary Edwards

Microsoft trounces pro-ODF forces in state battles over open document formats - 0 views

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

shared by Gary Edwards on 09 Jun 07 - Cached
  • Microsoft trounces pro-ODF forces in state battles over open document formats Eric Lai and Gregg Keizer &nbsp; document.write(''); if (navigator.userAgent.indexOf("Gecko")==-1) { document.write(''); } document.write(''); if (document.getElementById('dclk999')) { document.getElementById('dclk999').src = 'http://ad.doubleclick.net/adi/idg.us.cpw.desktopapplications/index;pos=imu;tile=3;sz=336x280;ord=' + ord + '?'; } document.write(''); if ((!document.images && navigator.userAgent.indexOf('Mozilla/2.') >= 0)|| navigator.userAgent.indexOf("WebTV") >= 0) {document.write('');} June 03, 2007 (Computerworld)
  • Keeping it private The other problem, Mathers said, was the jargon-laden disinformation that committee members felt they were being fed by lobbyists for both IBM and Microsoft. Although lobbyists would tell the committee one thing in private, they got cold feet when asked to verify the information publicly, under oath. "Suddenly, nobody wanted to sign witness affirmation forms and testify," he said. That undermined the credibility of each side, but it particularly damaged the position of ODF proponents. After Wyne testified publicly that in Massachusetts, only a handful of computers had thus far been converted over to using ODF,&nbsp;IBM declined to dispute her claims, Mathers said -- despite having earlier given "gleaming" reports on the progress of ODF in Massachusetts. "That's when I really started to question the whole bill," he said.
  • Gary Edwards on 09 Jun 07
     
    Uh Oh.  They got IBM dead to rights in Massachusetts.  I guess the truth about Massachusetts will be told!  Finally.  ODF failed in Massachusetts because there isn't a reasonable  means of implementing ODF.  Same in California.
  • Gary Edwards on 09 Jun 07
     
    A must read.  And yes, the ODF Vendors are the reason ODF lost.  They didn't provide useful solutions.  In fact, the applicaitons they proposed were seen by government CIO's as cstly and disruptive "rip out and replace" non starters.  In California, CIO's asked if it was even possible to implement ODF!!!
Gary Edwards

The X Factor: ODF, OOXML, CDF | Redmond Developer News - 0 views

reddevnews.com/...article.aspx

cdf odf ooxml w3c xml

shared by Gary Edwards on 16 Oct 07 - Cached
  • XML expert, consultant and Microsoft MVP Don Demsak argues that both technologies share a fundamental flaw-they're not really striving to be standards at all. "I think this whole OOXML versus ODF thing is a non-issue. Both formats are just serialization formats for the object models they're associated with, and are not designed as impartial, interoperable formats," Demsak writes in an e-mail. Gary Edwards, president of the OpenDocument Foundation, which drives ODF development, believes codified document standards should not carry forward old flaws and application nuances. "The world is not a clean slate, but it's going to somehow make that transition of existing documents, applications and processes to XML," he says in an e-mail. "To us, that is an open XML file format consistent with the continuing work of the W3C that also meets the following criteria: open, unencumbered, universally interoperable, totally application-platform-vendor independent, with an acceptable citizen-driven governance," Edwards writes.
  • Being XML, it should be easy to convert between the two formats."
    • Gary Edwards
      Gary Edwards on 16 Oct 07
       
      UH, excuse me. ODF and OOXML might be XML, but they are both application specific XML. Converting between the two means somehow being able to reconcile the different application models for handling basic document sturctures such as lists, fields, tables, sections, and page dynamics. The problem is that the two file formats are irreconcilable on these issues. What's needed is a move towards a basic generic elements/attribute model able to layer these application specific nuances into a more flexible attibute descriptive. Or, we could just move to XML/RDF and never look back :)
  • Gary Edwards on 16 Oct 07
     
    Now you're talking!
« First ‹ Previous 81 - 100 of 226 Next › Last »
Showing 20▼ items per page