Skip to main content

Home/ Groups/ OpenDocument
Rss Feed
Sort By: Most Recent | Popular Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Brian Jones: Open XML Formats : OASIS ODF committee considering joining DIN to help wit... - 0 views

blogs.msdn.com/...h-translation-and-interop.aspx

shared by Gary Edwards on 31 Jan 08 - Cached
  • OASIS ODF committee considering joining DIN to help with translation and interop This is very cool. It looks like the OASIS committee is looking at coming on board to help out with the work going on in DIN to help understand the translation between Open XML and ODF: http://www.oasis-open.org/archives/office/200801/msg0004
Gary Edwards

ODF Alliance on the Microsoft Disposition of ISO Comments on OOXML - 0 views

www.odfalliance.org/...isposition%20of%20Comments.pdf

brm odf odf-alliance ooxml opendocument openxml

shared by Gary Edwards on 30 Jan 08 - No Cached
  • Gary Edwards on 30 Jan 08
     
    The ever audacious and prevaricating lobbyist group known as the ODF Alliance has posted their critique of Ecma's (Microsoft's) proposed disposition of ISO comments rejecting OOXML. The critique's appeal to ignorance is breath-taking in scope. E.g., whilst slamming DIS-29500 on the subject of interoperability, the same document pushes for harmonization using the following argument: "Harmonization starts from looking at where the two formats overlap - and there is a significant, perhaps 90 percent or more, area where OOXML and ODF do overlap - and expressing this functional overlap identically. This common functionality between ODF and OOXML would also include a common extensibility mechanism. The remaining 10 percent of the functionality, where these standards do not overlap, would represent the focus of the harmonization effort. That portion of it which represents a widespread need could be brought into the core of ODF. That remaining portion which only serves one vendor's needs, such as flags for deprecated legacy formatting options, could be represented using the common extensibility mechanism." And precisely how do vendor-specific extensions aid interoperability, particularly when the proposed "harmonization" does not require profiles and an interoperability framework?
Gary Edwards

IT set to 'take their heads out of the sand' and embrace Web 2.0 - 0 views

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

interop interoperability open soa standards xml

shared by Gary Edwards on 29 Jan 08 - Cached
  • IT managers and CIOs in large companies who have actively resisted embracing Web 2.0 technologies like wikis, RSS, blogs and social networks will likely begin adding them to their priority lists in 2008, according to a report released Friday by Forrester Research Inc.
Gary Edwards

Wizard of ODF: OASIS invited to join Microsoft in the DIN technical report - harmoniz... - 0 views

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

din eu harmonization iso oasis odf ooxml xml

shared by Gary Edwards on 29 Jan 08 - Cached
  • the WG is busy working on a first draft. This'll include mainly work in Wordprocessing. Spreadsheet and Presentation is still in the very early work. So help from the ODF TC would be great --- and a liaison would make sense IMHO. To give you an idea why help from the ÓDF TC would be needed I'll briefly outline some questions which arose: * Need for more use-cases, i.e. feasable interop scenarios * Discussions of unspecified behaviour (e.g numbering in 1.0, spreadsheet formulas, compatibilty options, etc.) and their impact on interop scenarios * Questions regaring generic settings like e.eg. form:control-implementation="ooo:com.sun.star.form.component.Form", or tweaking a la http://www.openoffice.org/issues/show_bug.cgi?id=51726. * Possible interop problems not handled by the specs (e.g. graphics, WMF, EMF, SVM, etc.) or e.g. font metrics and font embedding. As you see there are a lot of overlapping areas with eg. the "ODF interop" we dealt with in the workshop in Barcelona. [This issue is hosted in the Adoption TC, right? Maybe this TC is also suited as a liaison partner?]
    • Gary Edwards
      Gary Edwards on 29 Jan 08
       
      Uh Oh. Microsoft and Novell joined the EU's call to harmonize ODF and OOXML, but Sun and IBM refused the invite. Now we have the invite in front of the OASIS ODF TC!. Is there any rock big enough for them to hide under if they also refuse?
      And if the OASIS ODF does join the EU-DIN-ISO effort, where doe stha tleave IBM, Sun and their inistance on a politically mandated "rip out and replace" as the only acceptable solution?
Gary Edwards

Harmonizing ODF and OOXML: The DIN - ISO "Harmonization" Project - 0 views

www.fokus.fraunhofer.de/...DIN-E.pdf

din harmonization iso odf ooxml

shared by Gary Edwards on 27 Jan 08 - No Cached
  • Gary Edwards on 27 Jan 08
     
    Contact: Gerd Schürmann Fraunhofer Institute FOKUS Tel +49 (0)30 3463 7213 gerd.schuermann@fokus.fraunhofer.de Berlin
  • Gary Edwards on 27 Jan 08
     
    At a recent meeting in Berlin, The DIN Fraunhoffer Institute pushed forward with the EU project to harmonize ODF and OOXML. Microsoft and Novell attended the harmonization effort. Sun and IBM did not. This in spite of invitations and pleas to cooperate coming into Sun and IBM from government officials across the European continent. We've long insisted that inside the OASIS ODF Technical Committee walls there have been years of discussions concerning ODF compatibility with the billions of MS binary documents, and ODF interoperability with MSOffice. Sun in particular has been very clear that they will not compromise OpenOffice application innovations to improve interoperability with MSOffice and MSOffice documents. The infamous List Enhancement Proposal donnybrook that dominated OASIS ODF discussions from November 20th, 2006, to the final vote in April of 2007, actually begins with a statement from Sun arguing that application innovation is far more important than market demands for interoperability. The discussions starts here: Suggested ODF1.2 items The first of many responses declaring Sun's position that innovation trumps interop, and that if anyone needs to change their application it should be Microsoft: see here DIN will submit a "harmonization" report with recommendations to ISO JTC1. I wonder if IBM and Sun will continue to insist on government mandated "rip out and replace" solutions based on their ODF applications when ISO and the EU have set a course for "harmonization"?
Gary Edwards

Aptana Jaxer | Aptana - 0 views

www.aptana.com/jaxer

ajax server

shared by Gary Edwards on 25 Jan 08 - Cached
  • Jaxer is the world's first true Ajax server. HTML, JavaScript, and CSS are native to Jaxer, as are XMLHttpRequests, JSON, DOM scripting, etc. And as a server it offers access to databases, files, and networking, as well as logging, process management, scalability, security, integration APIs, and extensibility.
Gary Edwards

Issue 51726: OpenOffice ODF Graphics Nightmare - 0 views

www.openoffice.org/...show_bug.cgi

application-specific din florian-reuter graphics odf openoffice

shared by Gary Edwards on 25 Jan 08 - Cached
  • Currently, the above given specification is a draft and has to be adjusted. Beside the change of the context menu and the navigator it's is needed to adjust the import of the XML file formats (OpenDocument and OpenOffice.org) and the export to the OpenOffice.org file format. The import needs adjustment, because the existence of name is used to distinguish Writer graphics/text boxes and Draw graphics/text boxes. The new criterium is now, that Draw graphics/text boxes of Writer documents doesn't have a parent style. The export to the OpenOffice.org file format needs adjustment, because a Writer document in the OpenOffice.org file format doesn't contain names for shapes.
    • Gary Edwards
      Gary Edwards on 25 Jan 08
       
      The EU DIN effort to harmonize or merge ODF and OOXML has uncovered some incredible inconsistencies in OpenOffice ODF tht will break interop every time, guaranteed. This particular issue has to do with problems naming graphics, and the hack solution now in use. It's hacks like this that make it impossible to convert MSOffice binaries to ODF.
Gary Edwards

» Government turns to SaaS to salvage IT failures | IT Project Failures | ZDN... - 0 views

blogs.zdnet.com/projectfailures

shared by Gary Edwards on 25 Jan 08 - Cached
  • As Administrator of E-Government and Information Technology, for the Office of Management and Budget, Evans oversees the government’s CIO Council, comprised of Chief Information Officers from various agencies. In September, 2007, she testified before the Senate, about high-risk IT projects:
Gary Edwards

[office] The infamous list-override list enhancement proposal - 0 views

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

application-specific florian-reuter foundation list-enhancement michael-brauer oasis-odf odf opendocument openoffice

shared by Gary Edwards on 25 Jan 08 - Cached
  • Well, I think the problem we face is that there are different interpretations of the 1.1 specification regarding the numbering of numbered paragraphs that have different list styles assigned. We therefore cannot say that the one or the other proposal is backward-compatible to the ODF 1.1 specification regarding the number or the style. We can only say whether it is backward-compatible to a certain _interpretation_ of the ODF 1.1 specification regarding the number or the style.
Gary Edwards

» Getting enveloped by the potential of Cloud computing | Web 2.0 Explorer | ... - 0 views

blogs.zdnet.com/web2explorer

client-server cloud-computing realestate web20

shared by Gary Edwards on 25 Jan 08 - Cached
  • By taking a fundamentally Web-based approach to the development of applications, we shift from bolting Web capabilities onto the silo toward a mode in which data and functionality are native to the Web: a mode in which the design decisions are more about modelling business requirements for limiting the ways in which data flows from one point to another rather than trying to anticipate the places in which it might be needed in order to design those pathways into software from the outset.
  • How do we change the mindset of today’s application developers, in order that they stop building ‘old’ applications in the new world?
Gary Edwards

IBM's Stance Against OpenXML Is Increasingly Confusing : Oliver Bell's weblog - 0 views

osrin.net/...nxml-is-increasingly-confusing

cdf heintzman ibm odf ooxml opendocument openxml symphony weir

shared by Gary Edwards on 25 Jan 08 - Cached
  • Events have played out in the media and in the blogosphere over the last couple of weeks that represent a breakdown of some of those anti-OpenXML arguments that have been played back so frequently over the last year. Arguments that there is a lack of demand for Open XML, the specification is too complex to implement, the specification can’t be deployed cross platform and the long running but baseless claim that the Ecma-376 specification might be encumbered by IPR and patent threats all appear to have been cast aside as big blue steps up to meet the demands of their own customers and the market in general. Here is a blow by blow review of the relevant activity over the last two weeks…
Gary Edwards

IBM's Director of Strategy comes clean on OpenXML - IBM *WILL* support OpenXML in its L... - 0 views

notes2self.net/...lotus-and-portal-products.aspx

cdf heintzman ibm odf ooxml openxml

shared by Gary Edwards on 25 Jan 08 - Cached
  • Well, if that's IBM's plan they're going to need more than ODF, that's for sure - and that brings us to the announcement I've been wondering about: IBM favors ODF as a file format because it is "truly open" and technically elegant, Heintzman said. But IBM will support Open XML, which is the current document format in Office 2007, in its Lotus collaboration and portal products. IBM already supports older versions of Office. I feel a Pamela Jones moment coming on .... there it is, as plain as day for the world to see, Doug Heintzman breaks through all IBM's doublespeak and hypocrisy and admits it. I don't know about "Beyond Office" as a plan, I think the real game here is "Beyond ODF"
Gary Edwards

office by thread - 0 views

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

archives oasis odf openoffice

shared by Gary Edwards on 25 Jan 08 - Cached
  • [Fwd: clarification: OpenDocument and SVG] From Lars Oppermann <Lars.Oppermann@Sun.COM> on 2 Feb 2005 10:31:44 -0000 Re: [office] [Fwd: clarification: OpenDocument and SVG] From Michael Brauer <Michael.Brauer@Sun.COM> on 2 Feb 2005 12:16:44 -0000 Message not available. Message not available. Message not available. Re: [office] [Fwd: clarification: OpenDocument and SVG] From Michael Brauer <Michael.Brauer@Sun.COM> on 3 Feb 2005 10:14:18 -0000 Message not available. Re: [office] [Fwd: clarification: OpenDocument and SVG] From Michael Brauer <Michael.Brauer@Sun.COM> on 3 Feb 2005 14:01:24 -0000 Propsal regarding the use of the SVG namespace in OpenDocument From Michael Brauer <Michael.Brauer@Sun.COM> on 3 Feb 2005 13:49:10 -0000 Use of SVG namespace From Patrick Durusau <Patrick.Durusau@sbl-site.org> on 7 Feb 2005 13:34:56 -0000
Gary Edwards

[office-comment] ODF Public Comment - Where's the Interop Guys? What the hell happened... - 0 views

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

oasis odf opendocument ouch

shared by Gary Edwards on 25 Jan 08 - Cached
  • Regarding section 1.5 itself: The Open Office TC decided to use the term MAY rather than MUST (or will) at the mentioned location, because it wanted to ensure that the OpenDocument specification can be used by as many implementations as possible. This means that the format should also be usable by applications that only support a very small subset of the specification, as long as the information that these applications store can be represented using the OpenDocument format. A requirement that all foreign elements and attributes must be preserved actually would mean that some applications may not use the format, although the format itself would be suitable. Therefor, we leave it up to the implementations, which elements and attributes of the specification they support, and whether they preserve foreign element and attributes. Some more information about this can be found in appendix D of the specification.
Gary Edwards

Independent study advises IT planners to go OOXML | A pos on both your houses! - 0 views

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

application-specific cdf ge odf ooxml pox

shared by Gary Edwards on 25 Jan 08 - Cached
  • What you've posted are examples of MSOffice ”compatibility settings” used to establish backwards compatibility with older documents, and, for the conversion of alien file formats (such as various versions of WordPerfect .wpd). These compatibility settings are unspecified in that we know the syntax but have no idea of the semantics. And without the semantic description there is no way other developers can understand implementation. This of course guarantees an unacceptable breakdown of interoperability. But i would be hesitant to make my stand of rejecting OOXML based on this issue. It turns out that there are upwards of 150 unspecified compatibility settings used by OpenOffice/StarOffice. These settings are not specified in ODF, but will nevertheless show up in OpenOffice ODF documents – similarly defying interoperability efforts! Since the compatibility settings are not specified or even mentioned in the ODF 1.0 – ISO 26300 specification, we have to go to the OOo source code to discover where this stuff comes from. Check out lines 169-211. Here you will find interesting settings such as, “UseFormerLineSpacing, UseFormerObjectPositioning, and UseFormerTextWrapping”.
Gary Edwards

A gadfly's take on IBM's 'support' for Open XML | Computerworld Blogs - 0 views

blogs.computerworld.com/gadfly_ibm_open_xml_support

cdf ibm odf ooxml opendocument sam

shared by Gary Edwards on 25 Jan 08 - Cached
  • On the revelation that some of IBM's products would support a document format that it officially, adamantly opposes, Hiser is not surprised one bit. IBM and Sun have both had "the magic blueprints" to Microsoft's document formats, including Open XML, for the past several years, Hiser said. With that key technical interoperability information, "how could you not expect IBM to start coding around OOXML?" he asked.
Gary Edwards

Q&A: Nicholas Carr on the big switch to utility computing - 0 views

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

carr cloud switch utility web-platform

shared by Gary Edwards on 25 Jan 08 - Cached
  • I think we’re at the early stages of a fundamental shift in the nature of computing, which is going from something that people and businesses had to supply locally, through their own machines and their own installed software, to much more of a utility model where a lot of the computer functions we depend on are supplied from big, central stations, big central utilities over the Internet.
Gary Edwards

A Closer Look At Those "Single Standard" Policy Mandates : Oliver Bell's weblog - 0 views

osrin.net/...ingle-standard-policy-mandates

shared by Gary Edwards on 25 Jan 08 - Cached
  • 2. Achieving interoperability is rarely as straight forward as selecting a single technical standard, and many of the policy positions around the world recognize this. Applications need to be designed to work together, groups need a solid framework for collaboration and the standards need to be ready to support these two objectives.
    • Gary Edwards
      Gary Edwards on 25 Jan 08
       
      Hold on there Oliver. You've got the cart before the horse here. You say that, "standards need to be ready to support these two objectives". The objectives you sight are that of applications being desinged for interop (exchange) and collaboration. This observation is consistent with the vendor mantra coming out of Microsoft, Sun, and IBM: that interoperability is an application problem - not a standards issue. My view is that the only way we will have interoperability is if we design standards as totally application, platform and vendor independent. This demands a clean room approach, even to the extent of not allowing application vendors participation. At least not direct particpation where vendor business objectives might influence the standard. The first law of the Internet is that Interoperability rules. Interop must trump innovation. And innovation must be within the boundaries of the interoperability framework. Meaning, innovate on top of interop, but don't break that interop. Ever! This is exactly the opposite of how applications want to operate. They want innovation first, with interop as secondary feature based entirely on dooperative deals between vendors. That's not good enough for me or anyone else who believes that a universal fiel format is possible. The W3C approach is to focus entirely on the standards use requirements, completely shutting out application demands. With formats, this comes down to focusing on the basic document structures carried over from a few hundred years of document publication experience. The only proven formula for interop is to first write and establish the base standard. Then, let the applications adapt. Let the applications compete on how well they implement interoeprability standards, and build innovative features without disrupting or compromising that interop.
« First ‹ Previous 161 - 180 of 433 Next › Last »
Showing 20▼ items per page