Skip to main content

Home/ OpenDocument/ Group items tagged pdf

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

BetaNews | ECMA to Begin Drafting XPS as Alternative Standard to PDF - 0 views

www.betanews.com/...1183144526

shared by Gary Edwards on 30 Jun 07 - Cached
  • "Be that as it may," Updegrove continues, "perpetuating one monopolistic market position after another seems wholly incompatible with the role of a global standards body, tasked with protecting the interests of all stakeholders. If OOXML, and now Microsoft XML Paper Specification, each sail through ECMA and are then adopted by ISO/IEC JTC1, then it may be time to wonder whether the time has come to declare 'game over' for open standards."
  • Gary Edwards on 30 Jun 07
     
    More on Andy UpDegrove's "Game Over for open standards" comment.
Gary Edwards

EC on Microsoft Interoperability Declaration: Is It April Fools' Day Already? | John Pa... - 0 views

digitaldaily.allthingsd.com/...microsoft-reacts

ecis interoperability microsoft odf ooxml

shared by Gary Edwards on 22 Feb 08 - Cached
  • “We have heard high-profile commitments from Microsoft a half-dozen times over the past two years, but have yet to see any lasting change in Microsoft’s behavior in the marketplace,” ECIS Legal Counsel and Spokesman Thomas Vinje said in a statement.
  • Gary Edwards on 22 Feb 08
     
    Thomas Vinge, the counsel for the ECIS, comments on Microsoft's most recent restatement of their enduring commitment to interoperability and transparency.
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

Is HTML in a Race to the Bottom? A Large-Scale Survey of Open Web Formats - 0 views

dsonline.computer.org/...index.jsp

cdf css html ooxml xaml xhtml

shared by Gary Edwards on 18 Apr 08 - Cached
  • The "race to the bottom" is a familiar phenomenon that occurs when multiple standards compete for acceptance. In this environment, the most lenient standard usually attracts the greatest support (acceptance, usage, and so on), leading to a competition among standards to be less stringent. This also tends to drive competing standards toward the minimum possible level of quality. One key prerequisite for a race to the bottom is an unregulated market because regulators mandate a minimum acceptable quality for standards and sanction those who don't comply.1,2 In examining current HTML standards, we've come to suspect that a race to the bottom could, in fact, be occurring because so many competing versions of HTML exist. At this time, some nine different versions of HTML (including its successor, XHTML) are supported as W3C standards, with the most up-to-date being XHTML 1.1. Although some versions are very old and lack some of the newer versions' capabilities, others are reasonably contemporaneous. In particular, HTML 4.01 and XHTML 1.0 both have "transitional" and "strict" versions. Clearly, the W3C's intent is to provide a pathway to move from HTML 4.01 to XHTML 1.1, and the transitional versions are steps on that path. It also aims to develop XHTML standards that support device independence (everything from desktops to cell phones), accessibility, and internationalization. As part of this effort, HTML 4.01's presentational elements (used to adjust the appearance of a page for older browsers that don't support style sheets) are eliminated in XHTML 1.1. Our concern is that Web site designers might decline to follow the newer versions' more stringent formatting requirements and will instead keep using transitional versions. To determine if this is likely, we surveyed the top 100,000 most popular Web sites to discover what versions of HTML are in widespread use.
    • Gary Edwards
      Gary Edwards on 18 Apr 08
       
      The summary statement glosses over the value of a highly structured portable XML document. A value that goes far beyond the strict separation of content and presentation. The portable document model is the essential means by which information is exchanged over the Web. It is the key to Web interop. Up till now, Web docuemnts have been very limited. With the advent of XHTML-2, CSS-3, SVG, XForms and CDF (Compound Document Framework for putting these pieces together), the W3C has provisioned the Web with the means of publishing and exchanging highly interactive but very complex docuemnts. The Web documents of the future will be every bit as complex as the publishing industry needs. The transition of complex and data rich desktop office suite documents to the Web has been non existent up till now. With ISO approval of MSOffice-OOXML, Microsoft is now ready to transition billions of business process rich "office" documents to the Web. This transition is accomplished by a very clever conversion component included in the MSOffice SDK. MS Developers can easily convert OOXML documents to Web ready XAML documents, adn back again, without loss of presentation fidelity, or data. No matter what the complexity! The problem here is that while MSOffice-OOXML is now an ISO/IEC International Standard, XAML "fixed/flow" is a proprietary format useful only to the IE-8 browser, the MS Web Stack (Exchange, SharePoint, MS SQL, and Windows Server), and the emerging MS Cloud. Apache, J2EE, Mozilla Firefox, Adobe and Open Source Servers in general will not be able to render these complex, business process rich, office suite documents. MSOffice-OOXML itself is far to complicated and filled with MS application-platform-vendor specific dependencies to be usefully converted to Open Web XHTML-CSS, ePUB or CDF. XAML itself is only the tip of the iceberg. The Microsoft Web Stack also implements Silverlight, Smart Tags and other WPF - .NET
  • Gary Edwards on 18 Apr 08
     
    What makes the Internet so extraordinary is the interoperability of web ready data, content, media and the incredible sprawl of web applications servicing the volumes of information. The network of networks has become the information system connecting and converging all information systems. The Web is the universal platform of access, exchange and now, collaborative computing. This survey exammines the key issue of future interoperability; Web Document Formats.
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

Unbreaking the Web: IE 8 passes ACID 2 Test | John Resig - 0 views

ejohn.org/unbreaking-the-web

cdf css iso microsoft odf ooxml w3c xhtml

shared by Gary Edwards on 07 Mar 08 - Cached
  • IMHO, the key to Microsoft's OOXML strategy can be seen in the recently released MSOffice SDK. The SDK provides a component for the fluid conversion of OOXML to something called fixed/flow. The fixed part of this interesting conjunction is also known as XPS, which is designed as a proprietary alternative to PDF. The flow part is a fascinating and highly proprietary replacement for (X)HTML - CSS. Reading further through the MSOffice SDK, one can't help but be amazed at the lack of W3C technologies; especially (X)HTML, CSS, XForms and SVG. What we have instead is an entangling cascade of stuff like OOXML, fixed/flow, silverlight, XAML, and WPF. And then there is that recent promise of other high volume API's probably delivered through future Exchange, SharePoint, and MS SQL Server SDK's. So, at the end of the day, what are we looking at here? IMHO, Microsoft has figured out that the smart thing to do is leverage and extend their existing desktop monopoly into the next generation of cloud computing where the Internet platform rules. To pull this off, they have a number of problems to overcome; not the least of which is that they need to catch a break on anti trust, and, get OOXML through ISO. And oh yeah, there's that little problem that Windows can't do cloud computing.
Gary Edwards

Prince: What's New - Docuemnt Publishing on Steroids with XHTML - CSS 3.0 (CDF+) - 0 views

www.princexml.com

cdf css w3c xhtml

shared by Gary Edwards on 02 Dec 07 - Cached
  • Prince is a computer program that converts XML and HTML into PDF documents. Prince can read many XML formats, including XHTML and SVG. Prince formats documents according to style sheets written in CSS. Standards support HTML, CSS, SVG, MathML Web enabled Load documents, style sheets, images and fonts over HTTP Publishing features Hyphenation, crop marks, columns, page floats and footnotes Eye candy Rounded borders, small caps, CMYK and RGBA colors
Gary Edwards

ODF versus OOXML: Don't forget about HTML! - O'Reilly XML Blog - 1 views

www.oreillynet.com/...ersus_ooxml_dont_forget_a.html

iso microsoft msoffice oasis odf ooxml opendocument openxml xml

shared by Gary Edwards on 06 Mar 07 - Cached
  • But Lie is right, I think, to be alarmed by the prospect that if OOXMLfails MS will revert away from open formats. I don’t see them adopting ODF as the default format for general sale. for a start, current ODF simply does not have matching capabilities. This issue of fit is strong enough that we don’t even need to get to the issue of control. We have this nice little window now where MS is inclined to open up its formats, something that the document processing community has been pleading for for years. The ODF sideshow runs the risk of screwing this up; I’ve said it before, but I say it again: being pro-ODF does not mean you have have to be anti-OOXML. ODF has not been designed to be a satisfactory dump format for MS Office; OOXMLhas not been designed to be a suitable format for Sun’s Star Office or Open Office or IBM’s products. HTML is the format ｏｆ choice for interchange of simple documents; ODF will evolve to be the format of choice for more complicated documents; OOXML is the format of choice for full-fidelity dumps from MS Office; PDF is the format of choice for non-editable page-faithful documents; all of them are good candidates for standardization, all have overlap but are worthwhile to have as cards in the deck of standards. But systems for custom markup trumps all.
  • Gary Edwards on 06 Mar 07
     
    Famed Microsoft WikiPedia editor Rick Jellife takes on the HTML-CSS proposal put forth by Opera Browser CTO Håkon Wium Lie's in his recent CNET column.

    Rick claims that the Opera proposal is "solid in its ultimate premise .... that inspite of .. all the talk about ODF and OOXML, it is important not to lose track of HTML's potential and actual suitability for much document interchange.

    Good discussion except that MS Rick can't help himself when it comes to the tired moral equivocation argument that the world can and should accept and use two ISO/IEC desktop productivity environment file format standards, ODF and OOXML.  Once again he puts forward the claim that ODF is OPenOffice specific and OOXML is MSOffice specific - each having it's place and value as an international standard.

    Are we standardizing applications here?  I thought it was about creating a universal XML file format that all application can use::  One file format  for OpenOffice, MSOffice, KOffice, Writer, WordPerfect Office, Novell Office, GNOME Office, and even the Flash-Apollo based " Virtual Ubiquity " from Rick Treitman.

    ODF does need to provide the marketplace with at least three profiles; desktop productivity environments, server side portal publication-content-archive management systems, and devices.  This would greatly improve interoperability as ODF documents transition across desktops, servers, devices and Internet information domains.  It would also help the implementation of ODF by SOA, SaaS and Web 2.0 systems.

    But having two file formats that irreconcilably incompatible servicing the exact same market categories?  Doesn't make sense.  And can only end in massive end user confusion where the application with dominant marketshare end up crushing any and all competitive alternative
Gary Edwards

CDF: The common format you've never heard of - O'Reilly XML Blog - Flock - 0 views

www.oreillynet.com/...he_common_format_youve_ne.html

cdf odf ooxml

shared by Gary Edwards on 30 Nov 07 - Cached
  • Quick! Do you use the Compound Document Format?! You, know, CDF … surely you use CDF, right? Chances are pretty good that you have no idea about what I’m talking about. Everyone knows Microsoft’s word document format and Adobe’s PDF, chances are pretty good that if you’re reading this on XML.com you’ve heard of ODF and OOXML, especially after the fairly rancorous discussions about ISO status for these two formats. Yet CDF, hmmmm … that’s a rough one. Didn’t it belong to Corel, once upon a time?
  • CDF was in the news recently with the implosion of the Open Document Foundation, originally established to endorse ODF, though in its death throes it briefly highlighted the CDF format as perhaps a better format for documents than either OOXML or ODF. This is admittedly one of those areas where it may be justified in looking at XHTML especially and going “huh”? How can that be a full document format - it’s used for web pages, after all - you wouldn’t want to use it to mark up a full book, would you? Document formats are a lot like religions - people are ready to defend them to the death if need be, yet at the same time it becomes easy to dismiss certain religions that don’t even seem to be religions at all (such as my personal favorite, the rather philosophical Tao). Could you mock up a brochure in XHTML and CSS? Actually, it turns out that its surprisingly easy to do just that - especially if you throw a little SVG into the mix and allow the possibility of embedding XHTML within SVG (for all those odd little bits of rotation and other special effects).
Gary Edwards

Open Document Foundation Gives Up | Linux Magazine - 0 views

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

cdf odf ooxml w3c

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

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

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

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

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

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

    In Massachusetts, the Foundation took
Gary Edwards

Whither OpenDocument Format? Say Hello To a Truly Universal File Format - CDF! - 0 views

www.technewsworld.com/...60938.html

cdf corel odf ooxml opendocument w3c xhtml

shared by Gary Edwards on 28 Dec 07 - Cached
  • Filtering vs. Standards Corel's policy is to focus on what its customers want rather than get overly involved in any one document format, Larock explained. WordPerfect uses Corel's proprietary document format but makes that code available. "We have filters built in to translate into more than 65 different file formats, including OOXML and ODF," he said. "That list included some legacy WordPerfect, AMIPro, PDF, multiple MS Word earlier formats and numerous graphic file formats." Maintaining filters for legacy document formats is important. People have lots of older files in archive that they still want to access, said Larock. Up for Grabs The evolution of text on the Internet along with the use of Web 2.0 applications is starting to have an impact. It is becoming a contest between a desktop presence and a Web-based format, according to Larock. He compared the situation to the transition from analog to digital formats in the telephone industry.
    • Gary Edwards
      Gary Edwards on 28 Dec 07
       
      Another big endorsement for the W3C's CDF as the universal file format!
Gary Edwards

Does ODF 1.2 Metadata Solve the Interop Problem? - Microsoft starts rolling out more O... - 0 views

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

afnor cdf iso maryjo merger metadata odf ooxml opendocument talkback zdnet

shared by Gary Edwards on 11 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 on 11 Dec 07
     
    A Second response to Mary Jo's, "Microsoft starts rolling out more OOXML translators" is also posted here. The title is "Standardization by Corporation". Shish-Ka-Bob makes the assertion the ODF 1.2 metadata model will enable lossless two way conversion between MSOffice and ODF. While it's true that that intent was a key component of the original July of 2006 Metadata Requirements, the proposal was eventually stripped from the final submission made in April of 2007. I try to explain to Shish how that came about. The second post here, "Standardization by Corporation", is a follow on to statements made to Shish. The statements have to do with the events at ISO, and what i think will eventually happen. IMHO, ISO will follow either the AFNOR or Brittish proposals to merge ODF and OOXML. To do this they will remove entirely the coproarate vendor influence of Ecma and OASIS, and perfect the merger entirely at ISO. My post just happened to coincide with ISO Governor Mark Bryan's "Standardization by Corporations" letter. A derpressing but nevertheless very true concern. In fact, the OpenDocument Foundation was created specifically to address our concerns about the undue influence big application vendors were exerting on ODF following the April 30th, 2005 approval of ODF 1.0 (which went on to become ISO 26300). ~ge~
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 11 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?"
Jesper Lund Stocholm

The Forrester Blog For Information & Knowledge Management Professionals - 0 views

blogs.forrester.com/...microsoft-crash.html

interop odf ooxml

shared by Jesper Lund Stocholm on 23 May 08 - Cached
  • Wow. Microsoft opened up today, taking a nearly 180-degree turn to announce its intent to support ODF, PDF, and XPS. Overall, this is a great, positive move. While unexpected, it's not surprising. Microsoft has been moving towards more open standards, like with its recent DAISY XML initiative. But it's also a no-brainer. Sticking exclusively with its competing Open XML was divisive, complicating IT's efforts to leverage the benefits that open source XML provides.
  • Jesper Lund Stocholm on 23 May 08
     
    Reading this I suddenly thought of the phrase "Internet tidal wave" from Bill Gates in the late 90's . I know the rest of the world don't give a damn about the document format war (as much as we do), but the move from Microsoft here is actually quite substantial.
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

What to do now - Rick Jelliffe - 0 views

www.oreillynet.com/...what_to_do_now.html

harmonization jelliffe odf ooxml

shared by Paul Merrell on 30 May 08 - Cached
  • Now that ODF and OOXML are both set to be on the ISO/IEC books, it is useful to consider what the next productive steps are. For genuine ODF Supporters who are concerned that ODF has languished a little out of the limelight during 2007, there are a lot of useful things to be done. You don’t even need to join the OASIS groups or your local National Body or SC34 to begin. I suggest here are some things that will help the ODF effort coming into ODF 1.2.
Graham Perrin

An Antic Disposition: OpenDocument Format: The Standard for Office Documents - 0 views

www.robweir.com/...ormat-standard-for-office.html

shared by Graham Perrin on 12 May 09 - Cached
  • OpenDocument Format: The Standard for Office Documents
    • Graham Perrin
      Graham Perrin on 12 May 09
       
      PDF
  • published in IEEE Internet Computing
  • introduction to ODF, what it is, where it came from and why it is important
‹ Previous 21 - 37 of 37
Showing 20▼ items per page