Skip to main content

Home/ OpenDocument/ Group items tagged firefox

Rss Feed Group items tagged

Gary Edwards

Document Interoperability Initiative Demonstrates Momentum and Results: Industry collab... - 0 views

  •  
    Through the Document Interoperability Initiative (DII) global forums, technology leaders have been working together to promote interoperability between different document format implementations to provide greater value and choice to customers, and the events - including one held in Belgium this week - are yielding practical results. Interoperability solutions announced today translate Open XML documents to a Web page (HTML) allowing readability on Web-friendly browsers such as Firefox, improve translations between different formats through optimized templates, and enable features that provide greater choice for customers and opportunities for independent software developers as they create and use business applications built on Java that manipulate business documents. At the DII events, discussions were also held about developing document test libraries and schema validators, and vendors had the opportunity to test their implementations of document formats in a lab environment to identify potential issues to be addressed.
Gary Edwards

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

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

The Document Interoperability Initiative: "DII" - 0 views

  •  
    Vendor - developer group sponsored by Microsoft ... "What's seriously lacking is a conversion or locking of scripts, macros, OLE, data - media bindings, and security settings .... the logic parts so important to any business process or productivity environment setting embedded in the original MSOffice document."
Gary Edwards

OpenXML Viewer Project - 0 views

  •  
    Technology Considerations The Microsoft OpenXml Viewer is a cross browser cross OS plugin. The core of the application has to be OS independent. Therefore, the application is developed using C++. Future possibilities The generated html from the docx file can be rendered using silverlight and similar rich platforms. The same can be used in a server scenario to render docx files as html.
  •  
    Interesting project based on an XSLT "one-way" conversion from OOXML to HTML. The conversion process will break any kind of business or application specific logic embedded in the document. There is a conversion of VML to SVG that i think will be important to watch.
  •  
    What's seriously lacking is a conversion or locking of scripts, macros, OLE, data - media bindings, and security settings .... the logic parts so important to any business process or productivity environment setting embedded in the original MSOffice document.
Gary Edwards

Microsoft OOXML viewers, translators, SDK to help interop with Firefox and OpenOffice? - 0 views

  •  
    On Dec 3, Microsoft officially announced the availability of its Open XML Document Viewer, Open XML/ODF Translators Version 2.5 and the Apache POI Java SDKfor OpenXML.
1 - 5 of 5
Showing 20 items per page