Skip to main content

Home/ Document Wars/ Group items matching "Web" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
2More

CIO Wakeup Call: Burton Group ODF/OOXML report | The CIO Weblog - 0 views

  • Although most of the ruckus over the paper has focused on the prediction that OOXML will beat out ODF, the more intriguing and meaningful conclusion is in fact that the World Wide Web Consortium (W3C) model, built on open and broadly accepted Web standards already in broad use, will in fact "...be more influential and pervasive than ODF and OOXML." This implicit acknowledgment that the SaaS delivery model will dominate productivity and document storage applications is less supportive of Microsoft's approaches than many of the documents detractors care to acknowledge and suggests the entire debate is essentially a sideshow.
  • CIOs who are truly concerned with data preservation and open standards need to take a hard look at Microsoft's historical business practices and the remaining questions hanging over OOXML and ask themselves if it's worth making such a major transition to a format that is fraught with the same potential for vendor (rather than consumer) control in the future. SaaS options, it's worth noting, hardly escape this issue, so regardless of the very real potential that SaaS will eclipse any of the stand-alone office applications that are currently involved in this debate, it's still going to be necessary to pick a format for long-term, corporate control of vital data and documents.
2More

Independent study advises IT planners to go OOXML | All about Microsoft | ZDNet.com - 0 views

  • “ODF represents laudable design and standards work. It’s a clean and useful design, but it’s appropriate mostly for relatively unusual scenarios in which full Microsoft Office file format fidelity isn’t a requirement. Overall, ODF addresses only a subset of what most organizations do with productivity applications today.” The report continues: “ODF is insufficient for complex real-world enterprise requirements, and it is indirectly controlled by Sun Microsystems, despite also being an ISO standard. It’s possible that IBM, Novell, and other vendors may be able to put ODF on a more customer-oriented trajectory in the future and more completely integrate it with the W3C content model, but for now ODF should be seen as more of an anti-Microsoft political statement than an objective technology selection.”
    • Gary Edwards
       
      Mary Jo takes on the recently released Burton Group Report comparing OOXML and ODF. Peter O'Kelly, one of the Burton Group authors, once famously said, "ODF is a great format if you live in an alternative universe where MSOffice doesn't exist!" This observation speaks to the core problem facing ODF and those who seek to implement the ODF standard: ODF was not designed for the conversion of MSOffice documents. Nor was ODF designed to work with MSOffice applications. Another way of saying this is to state that ODF was not designed to be interoperable with MSOffice documents, applications and bound processes. The truth is that ODF was designed for OpenOffice/StarOffice. It is an application specific format. Both OOXML and ODF do a good job of separating content from presentation (style). The problem is that the presentation - layout layers of both ODF and OOXML remains bound to specific applications producing it. While the content layers are entirely portable and can be exchanged without information loss, the presentation layers can not. Microsoft makes no bones about the application specific design and purpose of OOXML. It's stated right in the Ecma 376 charter that OOXML was designed to be compatible with MSOffice and the billions of binary documents in MSOffice specific binary formats. The situation however is much more confusing with ODF. ODF is often promoted as being application, platform and vendor independent. After five years of development though, the OASIS ODF TC has been unable to strip ODF of it's OpenOffice/StarOffice specific aspects. ODF 1.0 - ISO 26300 had three areas that were under specified; meaning these areas were described in syntax only, and lacked the full semantics demanded by interoperable implementations. Only OpenOffice and StarOffice code base applications are able to exchange documents with an acceptable fidelity. The three under specified areas of ODF are: Lists (numbered), F
2More

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

  • 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
       
      Another big endorsement for the W3C's CDF as the universal file format!
7More

ODF and OOXML - The Final Act - 0 views

  • The format war between Microsoft’s Open Office XML (OOXML) and the open source OpenDocument Format (ODF) has flared up again, right before the looming second OOXML ISO vote in March.
  • “ISO has a policy that, wherever possible, there should only be one standard to maximise interoperability and functionality. We have an international standard for digital documentation, ODF,” IBM’s local government programs executive Kaaren Koomen told AustralianIT.
  • ODF has garnered some criticism for being a touch limited in scope, however, one of its strengths is that it has already been accepted as a worldwide ISO standard. Microsoft’s format on the other hand, has been criticised for being partially proprietary, and even a sly attempt by the software giant to hedge its bets and get in on open standards while keeping as many customers locked into its solutions as possible.
    • Gary Edwards
       
      A "touch limited in scope"? Youv'e got to be kidding. ODF was not defined to be compatible with the billions of MSOffice binary (BIN) documents. Nor was it designed to further interoperability with MSOffice.
      Given that there are over 550 million MSOffice desktops, representing upwards of 95% of all desktop productivity environments, this discrepancy of design would seem to be a bit more than a touch limited in scope!
      Many would claim that this limitation was due to to factors: first that Microsoft refused to join the OASIS ODF TC, which would have resulted in an expanded ODF designed to meet the interoperability needs of the great herd of 550 million users; and second, that Microsoft refused to release the secret binary blueprints.
      Since it turns out that both IBM and Sun have had access to the secret binary blueprints since early 2006, and in the two years since have done nothing to imptove ODF interop and conversion fidelity, this second claim doesn't seem to hold much water.
      The first claim that Microsoft didn't participate in the OASIS ODF process is a bit more interesting. If you go back to the first OASIS ODF Technical Committee meeting, December 16th, 2002, you'll find that there was a proposal to ammend the proposed charter to include the statemnt that ODF (then known as Open Office XML) be compatible with existing file formats, including those of MSOffice. The "MSOffice" reference was of course not included because ODF sought to be application, platform and vendor independent. But make no mistake, the discussion that day in 2002 was about compatibility and the conversion of the legacy BIN's into ODF.
      The proposal to ammend the charter was tabled. Sun objected, claiming that people would interpret the statement as a direct reference to the BIN's, clouding the charter's purpose of application, platform and vendor independence. They proposed that the charter ammendment b
    • Gary Edwards
       
      Will harmonization work? I don't think so. The problem is that the DIN group is trying to harmonize two application specific formats. OpenOffice has one way of implementing basic document structures, and MSOffice another. These differences are directly reflected in the related formats, ODF and OOXML. Any attempts to harmonize ODF and OOXML will require that the applications, OpenOffice and MSOffice, be harmonized! There is no other way of doing this unless the harmonized spec has two different methods for implementing basic structures like lists, tables, fields, sections and page dynamics. Not to mention the problems of feature disparities. If the harmonized spec has two different implementation models for basic structures, interoeprability will suffer enormously. And interoperability is after all the prupose of the standardization effort. That brings us to a difficult compromise. Should OpenOffice compromise it's "innovative" features and methods in favor of greater interoperability with MSOffice and billions of binary documents? Let me see, 100 million OpenOffice installs vs. 550 MSOffice installs bound to workgroup-workflow business processes - many of which are critical to day to day business operations? Sun and IBM have provided the anser to this question. They are not about to compromise on OpenOffice innovation! They believe that since their applications are free, the cost of ODF mandated "rip out and replace" is adequately offset. Events in Massachusetts prove otherwise! On July 2nd, 2007, Sun delivered to Massachusetts the final version of their ODF plug-in for MSOffice. That night, after reviewing and testing the 135 critical documents, Massachusetts made a major change to their ETRM web site. They ammended the ETRM to fully recognize OOXML as an acceptable format standard going forward. The Massachusetts decision to overturn th
  • ...1 more annotation...
    • Gary Edwards
       
      The Burton Group did not recommend that ISO recognize OOXML as a standard! They pointed out that the marketplace is going to implement OOXML by default simply because it's impossible to implement ODF in situations where MSOffice dominates. ISO should not go down the slippery slope of recognizing application-platform-vendor specific standards. They already made that mistake with ODF, and recognizing OOXML is hardly the fix. What ISO should be doign is demanding that ODF fully conform with ISO Interoeprability Requirements, as identified in the May 2006 directive! Forget OOXML. Clean up ODF first.
  •  
    Correcto mundo! There should be only one standard to maximise interoeprability and functionality. But ODF is application specific to the way OpenOffice works. It was not designed from a clean slate. Nor was the original 2002 OpenOffice XML spec designed as an open source effort! Check the OOo source code if you doubt this claim. The ONLY contributors to Open Office XML were Sun employees! What the world needs is in fact a format standard designed to maximise interoperability and functionality. This requires a total application-platofrm-vendor independence that neither ODF or OOXML can claim. The only format that meets these requirements is the W3C's family of HTML-XML formats. These include advancing Compound Docuemnt Framework format components such as (X)HTML-5, CSS-3, XForms, SVG and SMiL.. The W3C's CDF does in fact meet the markeplace needs of a universal format that is open, unencumbered and totally application, platform and vendor independent. The only trick left for CDF is proving that legacy desktop applications can actually implement conversions from existing in-memory-binary-representations to CDF without loss of information.
1More

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

  • 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.
2More

How Microsoft Lost the API War - Joel on Software - 0 views

  • Most .NET developers are ASP.NET developers, developing for Microsoft's web server. ASP.NET is brilliant; I've been working with web development for ten years and it's really just a generation ahead of everything out there. But it's a server technology, so clients can use any kind of desktop they want. And it runs pretty well under Linux using Mono. None of this bodes well for Microsoft and the profits it enjoyed thanks to its API power. The new API is HTML, and the new winners in the application development marketplace will be the people who can make HTML sing.
    • Gary Edwards
       
      How Microsoft lost the API War is one of the most important and influential commentaries ever published by Joel On Software. Always worth looking back to, even now in 2008!
2More

Most Business Tech Pros Wary About Web 2.0 Tools In Business - Technology News by Infor... - 0 views

  • How should an IT team start thinking about an Enterprise 2.0 strategy? One way is to carve it into two main areas. The first is Web-based information sharing--think business versions of Wikipedia, MySpace, and Flickr. A sizable minority of companies are finding effective business uses for blogs, wikis, syndicated feeds, pervasive search, social networking, collaborative content portals like SharePoint, and mashups that use easier-to-integrate APIs and fast-response development techniques such as Ajax. One example: Wikis, which let multiple people access and edit a document online, are widely used at 6% of companies in our survey and used effectively by a few employees at 25% of companies. The second area is voice and messaging, where voice over IP, instant messaging, presence, videoconferencing, and unified communications can make it possible to connect people in more relevant ways. Unified communications entails the blending of voice calls, video, and messages, coupled with functionality like embedded click-to-call links in documents and contact lists and the ability to see if colleagues and partners are available to chat. It's widely used at 13% of companies surveyed and effectively by a few at 24%.
  •  
    Great coverage from InformationWeek about the emerging Enterprise 2.0 arena.  Author Michael Hoover does not get too deep into the Information Processing Chain, as exampled by the integrated Vista Stack of desktop, server, device,Internet systems and services.  But he provides a more than adequate framework for evaluating chain components.

    As the ODF - OOXML battle contiues to expand, engulfing swallowing and swamping near everythign in it's path, the day is not too far off when the battle will move to the center of Enterprise 2.0 considerations.  It has to.  XML Hubs are how these converging technologies are going to be gathered, integrated and configured to impact rapidly changing business processes.  There has to be a universal transport in these systems that all applications can work, and nothig matches the highly portable and interactive document/data capabilities of ODF and OOXML.  They alone own the desktop prodcutivity environment migration to XML.  And it will be through XML - RDF/XML that the Hubs finally integrate the flow of information between desktops, servers, devices and Internet systems.

    ~ge~

6More

PlexNex: Analyzing the Microsoft Office Open XML License - 0 views

  • There are many other warts in the Microsoft covenant not to sue. E.g., the covenant applies only to Ecma Office Open XML; it does not apply to any future version, including a version that might be approved by ISO or a variant that might be actually implemented by Microsoft in MS Office. So Microsoft makes no guarantee that it will not move the goal posts at any time.
  •  
    Whoa!  This has already happened.  In his blog titled, "The Formats of Excel 2007",  XML expert Rob Weir demonstrates for us that MSOffice 2007 Excel has a new file format.  Rob demonstrates that there are four file format choices in Excel; EOOXML, Legacy XLS binary, and two  new binary extensions of EOOXML: "Excel Macro-Enabled Workbook" - xlsxm, and "Excel Binary Workbook" - xlsb.

    The new binaries are proprietary extensions to EOOXML.  xlsb in particular looks to be something known as a XML Binary InfoSet..  XBiS is a compressed form of an XML file used in situations where bandwidth and device cpu constraints demand such an extreme.  We can't be sure about xlsb, but it looks like a duck, walks like a duck, quacks like a duck and thherefore....

    This must be some kind of record.  EOOXML isn't yet 30 days old and Micrsoft has eXtended it with a proprietary binary representation not available to the rest of the world.  And XBiS was designed so that implementations would be open and application and platform independent.  But that's not what we see with Microsoft's xlsb.

    What Marbux is pointing out here is that only Micrsoft has the legal rights to do this proprietary eXtension of EOOXML.  Beat the drums.  Sound the alarms.  Hide the women and children.  Nothing has changed.  The longboats are fancier, there are more of them. The swords of the pillagers remain just as sharp.  Their determination and drive just as strong.

    Some quick backgroud references:  Compression, XML</b
  • ...2 more comments...
  •  
    Whoa!  This has already happened.  In his blog titled, "The Formats of Excel 2007",  XML expert Rob Weir demonstrates for us that MSOffice 2007 Excel has a new file format.  Rob demonstrates that there are four file format choices in Excel; EOOXML, Legacy XLS binary, and two  new binary extensions of EOOXML: "Excel Macro-Enabled Workbook" - xlsxm, and "Excel Binary Workbook" - xlsb.

    The new binaries are proprietary extensions to EOOXML.  xlsb in particular looks to be something known as a XML Binary InfoSet..  XBiS is a compressed form of an XML file used in situations where bandwidth and device cpu constraints demand such an extreme.  We can't be sure about xlsb, but it looks like a duck, walks like a duck, quacks like a duck and thherefore....

    This must be some kind of record.  EOOXML isn't yet 30 days old and Micrsoft has eXtended it with a proprietary binary representation not available to the rest of the world.  And XBiS was designed so that implementations would be open and application and platform independent.  But that's not what we see with Microsoft's xlsb.

    What Marbux is pointing out here is that only Micrsoft has the legal rights to do this proprietary eXtension of EOOXML.  Beat the drums.  Sound the alarms.  Hide the women and children.  Nothing has changed.  The longboats are fancier, there are more of them. The swords of the pillagers remain just as sharp.  Their determination and drive just as strong.

    Some quick backgroud references:  Compression, XML</b
  •  
    There are many other warts in the Microsoft covenant not to sue. E.g., the covenant applies only toEcmaOffice Open XML; it does not apply to any future version, including a version that might be approved by ISO or a variant that might be actually imple
  •  
    There are many other warts in the Microsoft covenant not to sue. E.g., the covenant applies only toEcmaOffice Open XML; it does not apply to any future version, including a version that might be approved by ISO or a variant that might be actually imple
  •  
    There are many other warts in the Microsoft covenant not to sue. E.g., the covenant applies only toEcmaOffice Open XML; it does not apply to any future version, including a version that might be approved by ISO or a variant that might be actually imple
2More

Gray Matter : Compatibility Pack for Open XML passes 100 million downloads - 0 views

  • The Compatibility Pack, software that allows you to open, edit and save Open XML format documents in Office XP and 2003 has now been downloaded over 100 million times.
  •  
    Also includes stats in table form indicating that according to Google Search OOXML documents now outnumber ODF documents on the Web, for word processor documents, spreadsheet documents, and presentation documents.
1More

Google's Microsoft Fight Starts With Smartphones | BNET Technology Blog | BNET - 0 views

  •  
    .... "I recently described how Google's Wave, a collaboration tool based on the new HTML 5 standard, demonstrated the potential for Web applications to unglue Microsoft's hold on customers. My post quoted Gary Edwards, the former president of the Open Document Foundation, a first-hand witness to the failed attempt by Massachusetts to dump Microsoft and as experienced a hand at Microsoft-tilting as anyone I know......"
1More

OASIS ODF: List Proposal Enhancement Vote Deadline on Wednesday | Gary Edwards - 0 views

  •  
    Thanks to Paul for digging this up. Who would have guessed that years later, these same issues hang like a dark shroud on the future of ODF? Note also that June 1st of 2007 was the cut off date for ODF 1.2 proposals and recommendations. The OpenFormula and Metadata SC's were rushing to make the cutoff. The List Enhancement proposal itself was just one of many enhancements submitted by Florian Reuter in November of 2006, designed to greatly improve ODF compatibility with MSOffice "ODF". By November of 2006, thanks largely to the Massachusetts Pilot Study, there were a number of ODF plug-ins for MSOffice. All were capable of producing perfectly compliant ISO 26300 ODF, but falling far short of public expectations of high fidelity interop with OpenOffice ODF. Sound familiar? Everyone knew that it was only a matter of time before Microsoft was pressed into providing MSOffice ODF support. There was no doubt that they would face the exact same interop challenges as the many independent plug-in efforts. Hence the stepped up efforts by many at the OASIS ODF to "fix" ISO 26300! At the time of the List Enhancement Proposal, we had increasing evidence from the many pilot studies that ODF was impossible to implement in business and workgroup environments where the MSOffice productivity environment was the defining platform. ODF was not designed to be compatible with MSOffice or the binary documents so critical to business processes bound to this environment. OpenXML was designed exactly to be compatible with these environments. Unless ODF fixed it's compatibility/interoperability problems there was no way for the independent plug-ins to provide a reasonable ODF implementation alternative to OpenXML. And even if Microsoft did produce an MSOffice ODF compliant with ISO 26300, these productivity environments would remain entirely locked. The world expected ODF to be compatible, interoperable, Web ready, and fully capable of cracking open the iron grip Mic
1More

In Office SP2, Microsoft manages to reduce interoperability | TalkBack on ZDNet - 0 views

  •  
    ODF is important. So What Went Wrong? Response to Jeremy Allison: Having participated in a number of government pilot studies, I must say that you are right; government officials do care about ODF. They really want it to work. But they also had expectations that ODF simply wasn't designed for. What they expected ODF to be was an open technology based on highly-structured XML markup that was application, platform, and vendor-independent, backward compatible, universally interoperable, and importantly, Web ready. That is not ODF nor is it OOXML. In fact, the closest thing we have for meeting these expectations is an ajax-Webkit style HTML+ (HTML5, CSS4, SVG/Canvas, JS jQuery, etc.). ODF is highly structured, but it is not application-independent. .....
1More

Microsoft-led Forum Yields Tools for OOXML Interoperability - Business Center - PC World - 0 views

  •  
    Is there nothing that can cool the flames of this document war? Interesting coverage of the recent OOXML Interoperability event in London (Monday). Real stuff not talk. Since Florian, Jason and i are working on an OpenWeb ready HTML+ layer riding over OOXML there are some things mentioned that look very interesting. ..."An Opera browser plug-in for Open XML Document Viewer v1.0 was released at the meeting; the tool provides direct translation for Open XML documents (.DOCX) to HTML, enabling access to Open XML documents from any platform with a Web browser, including mobile devices. The document-viewing software already includes a plug-in for Firefox, Internet Explorer 7 and Internet Explorer 8...." ..."Microsoft and the other participants in Monday's forum also made available a beta of Apache POI 3.5, a Java API (application programming interface) to access information in the Open XML Format....."
3More

Microsoft offers Office 2010 file format 'ballot' to stop EU antitrust probe - 0 views

  • In a proposal submitted to the European Commission two weeks ago, Microsoft spelled out a range of promises related to Office, its desktop and server software, and other products to address antitrust concerns first expressed by officials in January 2008.
  • Beginning with the release of Office [2010], end users that purchase Microsoft's Primary PC Productivity Applications in the EEA [European Economic Area] in both the OEM and retail channel will be prompted in an unbiased way to select default file format (from options that include ODF) for those applications upon the first boot of any one of them," Microsoft said in its proposal [download Word document]
  •  
    Microsoft's proposed undertaking for resolving the ECIS complaint to the European Commission regarding its office productivity software can be downloaded from this linked web page. I've given it a quick skim. Didn't see anything in it for anyone but competing big vendors. E.g., no profiling of data formats for interop of less and more featureful implementations, no round-tripping provisions. Still, some major concessions offered.
1More

The collective comments of gary.edwards's as posted on CNET - 0 views

  •  
    Wow. i had no idea this existed until one of the attorney's working on the New York State XML format pilot study started asking questions based on this link. In particular he was interested in a further explanation for this particular clip:
1More

HyperOffice - Collaboration Software: Online Task, Document Management, Cloud Email , M... - 0 views

  •  
    Web - Browser based desktop productivity suite.  
1More

A New Patent Application from Apple Introduces us to a Breakthrough Platform Independen... - 0 views

  •  
    excerpt:  This could be Apple's new internet strategy that thrusts more of us into the next phase of what is now known as the Post-PC era. In my view, this breakthrough could be a game changer.   The Problem to Solve The recent proliferation of web browsers and computer networks has made it easy to display the same document on different computing platforms. However, inconsistencies in the way fonts are rendered across different computing platforms could cause the same document to be rendered differently for users of different computing platforms. More specifically, for a given font, the way in which metrics for various font features are interpreted, such as character height, width, leading and white space, can differ between computing platforms. These differences in interpretation could cause individual characters in a document to be rendered at different locations, which could ultimately cause the words in a document to be positioned differently between lines and pages on different computing platforms.   This inconsistent rendering could be a problem for people who are collaborating on a document. For example, if one collaborator points out an error on a specific line of a specific page, another collaborator viewing the same document on a different computing platform may have to first locate the error on a different line of a different page. Hence, what is needed is a technique for providing consistent rendering for documents across different computer systems and computing platforms. Apple's patent application describe a system that typesets and renders a document in a platform-independent manner. During operation, the system first obtains the document, wherein the document includes text content and associated style information including one or more fonts. The system also generates platform-independent font metrics for the one or more fonts, wherein the platform-independent font metrics include information that could be used to determine the positions of i
1More

Gray Matter : Office and SharePoint 2010 Highlights from SharePoint Conference - 0 views

  •  
    If there were any doubts left as to how far along Microsoft is in their efforts to create a proprietary version of the Web for Office Productivity and Business Systems, the recent SharePoint Conference should put these doubts to rest.   excerpt:  InfoPath 2010 and InfoPath Forms Services ....... Forms capability in Office and SharePoint is maturing rapidly. With the inclusion of BCS in SharePoint 2010 and Office 2010, InfoPath becomes even more powerful as a tool for aggregating, presenting and gathering information. Why? - People are now discovering how easy it is to bind BCS entities to a SharePoint list, and then present that list data to users in a rich InfoPath form. Because InfoPath does a great job of making complex data interaction simple for end users, it is becoming a critical component of LOB solutions managed in the SharePoint environment. Surfacing InfoPath solutions via the browser, InfoPath mobile forms, through Outlook, SharePoint Workspace or other interfaces makes the rich InfoPath experience portable and flexible. People on the floor certainly responded positively; InfoPath was a smashing success. Visit the InfoPath team blog to read about some of the solutions they were previewing. Below is an excerpt from the post:
1More

Free Online PDF to HTML5 Converter, convert pdf to html5 flip book | pubhtml5 - 1 views

  •  
    "PUB HTML5 automatically converts your legacy content to rich and interactive eBooks. Add interactivity, audios, videos, documents, HTML activities, assessments and more to provide a rich reading experience to your readers. PUB HTML5 enables you to convert your content only once and publish them to multiple platforms like iPad, Android and Windows 8 tablets, PC/Mac and industry standard formats like HTML5 and MOBI. For PUB HTML5, the operating steps of creating fabulous digital magazines are foolproof ones. We extol minimum efforts and maximum outputting effects. Just follow the right procedures of the software, and you can totally customize your own digital magazine on your IPAD. After you have converted your PDF files, with multiple Custom Setting buttons, you get the privilege to design your own digital magazines .You may chose the template you prefer; change the background image; insert rich media including audios, video, images; add links, etc. The whole process can be easily achieved within minutes. Converting your PDFs into HTML5 in order to create iPad magazines can be a simple and worthwhile experience following the right procedures. This video provides you with a step by step procedure on how to create iPad magazines from the very beginning. Even though the PDF is great for posting reading documents like manuals on a website, it can sometimes annoy and even deter your viewers. Public or shared computers may not have a PDF viewer installed or downloading a PDF might not agree with a user's browsing habits. In order to make material in a PDF more accessible to others, converting your PDF to HTML5 file may be an alternative to consider. You can convert PDF to HTML5 free by using the Export tool in PUB HTML5. This option lets you perform different types of on-the-fly PDF conversions. After you have personalized your digital creation by using PUB HTML5 on your PC, you may easily preview your digital work on your IPAD or any other electronic devices. You ma
1More

The End of ODF &amp; OpenXML - Hello ODEF! - 0 views

  •  
    Short slide deck of Barbara Held's February 28th, 2007 EU IDABC presentation. She introduces ODEF, the "Open Document Exchange Format" which is designed to replace both ODF and OpenOfficeXML. ComputerWorld recently ran a story about the end of ODF, as they covered the failure of six "legislative" initiatives designed to mandate ODF as the official file format. While the political treachery surrounding these initiatives is a story in and of itself, the larger story, the one that has world wide reverberations, wasn't mentioned. The larger ODF story is that ODF vendors are losing the political battles because they are unable to provide government CIO's with real world solutions. Here are three quotes from the California discussion that really say it all: "Interoperability isn't just a feature. It's the basic requirement for getting your XML file format and applications considered"..... "The challenge is that of migrating our existing documents and business processes to XML. The question is which XML? OpenDocument or OpenXML?" ....... "Under those conditions, is it even possible to implement OpenDocument?" ....... Bill Welty, CIO California Air Resource Board wondering if there was a way to support California legislative proposal AB-1668. This is hardly the first time the compatibility-interoperability issue has challenged ODf. Massachusetts spent a full year on a pilot study testing the top tier of ODF solutions: OpenOffice, StarOffice, Novell Office and IBM's WorkPlace (prototype). The results were a disaster for ODF. So much so that the 300 page pilot study report and accompanying comments wiki have never seen the light of day. In response to the disastrous pilot study, Massachusetts issued their now infamous RFi; a "request for information" about whether it's possible or not to write an ODF plugin for MSOffice applications. The OpenDocument Foundation responded to the RFi with our da Vinci plugin. The quick descriptio
« First ‹ Previous 61 - 80 of 131 Next › Last »
Showing 20 items per page