Skip to main content

Home/ Document Wars/ Group items tagged pdf

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

The real state of ODF Interoperability? There is none : Comments from the Northwest P... - 0 views

www.nwprogressive.org/...free-openofficeorg-writer.html

marbux odf ooxml interoperability

shared by Gary Edwards on 09 May 09 - No Cached
  • Gary Edwards on 09 May 09
     
    Marbux nails it again in the comments section of this obscure review. In particular, he sites Shah, Rajiv C. and Kesan, Jay P., Lost in Translation: Interoperability Issues for Open Standards - ODF and OOXML as Examples (September 2008), Link to paper on SSRN (compatibility fidelity comparisons of ODF implementations testing only a very small set of word processing features). "...Switching documents, I go through similar travails with the published ODF 1.1 specification, using both the PDF and ODT versions. Bottom line: I can't get either document into WordPerfect X3 or X4 using any rich text format. So I convert the document to plain text using Symphony and get my work done. That is the real state of ODF interoperability. There is no such thing. But that does not stop the vested interests from claiming that there is. E.g.:"
Gary Edwards

Official Google Blog: Pagination comes to Google Docs - 0 views

googleblog.blogspot.com/...tion-comes-to-google-docs.html

shared by Gary Edwards on 12 Apr 11 - No Cached
  • Gary Edwards on 12 Apr 11
     
    Although you need Chrome for the new Google Docs pagination feature, the key here is that gDocs now supports the CSS3 pagination module!   excerpt: Today, we're doing another first for web browsers by adding a classic word processing feature-pagination, the ability to see visual pages on your screen. We're also using pagination and some of Chrome's capabilities to improve how printing works in Google Docs. Native Printing: Pagination also changes what's possible with printing in modern browsers. We've worked closely with the Chrome team to implement a recent web standard, CSS3, so we can support a feature called native printing. Before, if you wanted to print your document we'd need to first convert it into a PDF, which you would then need to open and print yourself. With native printing, you can print directly from your browser and the printed document will always exactly match what you see on your screen.
Gary Edwards

Microsoft Office 365 vs. Google Apps: The ultimate guide | Applications - InfoWorld - 0 views

www.infoworld.com/...apps-the-ultimate-guide-246585

wordsdk Office-365 Cloud-Productivity-Platform

shared by Gary Edwards on 20 Aug 14 - No Cached
  • Gary Edwards on 20 Aug 14
     
    "Microsoft Office 365 and Google Apps have raised the bar for cloud productivity suites. Formerly pale shadows of available desktop programs, the two suites are now more than enough for many offices and businesses. But are they right for you? In this exhaustive review, InfoWorld covers multiple aspects of the cloud suites, starting with the many Office 365 SKUs and Google Apps for Business options and proceeding to: Setup Features Ease-of-use Administration Value InfoWorld examines all the details and fine points Microsoft and Google have to offer over the desktop suite -- and potential deal breakers for anyone considering the switch. If you've been thinking about breaking up with Microsoft Office on the desktop, this could be the time, but don't make any decisions before checking out InfoWorld's Microsoft Office 365 vs. Google Apps superguide. Download this PDF -- with InfoWorld's full and complete review, along with more expert advice -- for a handy rundown of both offerings and how they apply to your business. Office 365 and Google Apps have changed in the last couple of years. Find out if it's enough for your office to make the switch too. Download InfoWorld's Microsoft Office 365 vs. Google Apps superguide here."
Gary Edwards

Why Microsoft Azure could have the last laugh in the cloud wars | CITEworld - 0 views

www.citeworld.com/...t-laugh-in-the-cloud-wars.html

rdsdk Office-365 Cloud-Productivity-Platform

shared by Gary Edwards on 20 Aug 14 - No Cached
  • Venture capitalist Brad Feld recently wrote an interesting post predicting the end of Amazon's dominance of the cloud computing market, and concluded, "it’s suddenly a good time to be Microsoft or Google in the cloud computing wars." I'd go one step farther. Using Feld's arguments, I'd say that Microsoft is in the driver's seat. More like this The dark side of the cloud price wars between Amazon, Google, and Microsoft The rise, fall, and rehabilitation of Internet Explorer Microsoft, Apple, and Google battle for the mobile enterprise Featured Resource Presented by Citrix Systems 10 essential elements for a secure enterprise mobility strategy Best practices for protecting sensitive business information while making people productive from Learn More First, the price war. Microsoft and Google are on approximately equal ground when it comes to cutting prices -- both have highly profitable core businesses that they can use to subsidize a price war in cloud infrastructure, even to the point of sustaining losses for a while to gain market share. Amazon does not. 
  • Second, the quality argument. Like Feld, we've also pointed out that there are niche cloud providers that do a better job than the big guys at providing infrastructure-as-a-service for specific verticals, but when you move all the way up the stack to full software-as-a-service applications, Microsoft has an edge among the big three with Office 365.
  • Google has been making inroads into smaller businesses with Google Apps for almost a decade now, Microsoft remains the standard in the biggest and most profitable business customers -- as this recent investigation from Dan Frommer at Quartz showed, only one company in the Fortune 50 uses Google Apps. (That company happens to be Google itself.) 
  • ...8 more annotations...
  • But then comes the fourth argument. Feld points out that once companies get to $200,000 per month of cloud-infrastructure spend, it's actually significantly cheaper to build their own data centers
  • The third argument, support, is mostly a wash. While Amazon's support may be terrible (I have no evidence of this, but I'm taking Feld's word for it), Microsoft and Google and their respective ecosystem partners do a decent job of supporting customers on their stacks.
  • It's unclear how the Google Cloud Platform helps that business. Are customers using Google's cloud somehow more likely to advertise with Google? I don't see it. Are Google advertising customers demanding to run other workloads on Google technology? I don't see it.
  • There's one more point favoring Microsoft. Google's core business is selling online advertising. That business makes up about 90% of Google's revenue, and it has enviably high operating margins -- around 30%, based on Google's 2011 financial report. (I picked 2011 because that was before Google bought Motorola Mobility, which changed the margin structure.)
  • Microsoft is the only one of the big three players with an on-premise offering -- Windows Server and the rest of the Microsoft infrastructure family. Maybe the exact break-even point will change as the cloud price wars continue, but Microsoft has the most pieces customers would need to move from all-cloud to a hybrid or on-premise solution. Or, for that matter, for existing on-premise customers to begin experimenting moving some workloads to the cloud.
  • Meanwhile, while Azure almost certainly offers lower margins than, say, on-premises Windows Servers, it's necessary -- customers are moving workloads to the cloud, and Microsoft needs a competitive offering there to keep them on the Microsoft stack so they continue to buy other Microsoft products. Plus, as I argued in point four, today's Azure customers could become tomorrow's on-premise Microsoft infrastructure customers.
  • In other words, Microsoft Azure and Google Cloud Engine both lower the profit margins of their parent companies. But Azure is clearly strategic while Cloud Engine, as far as I can tell, is not. Who's more likely to keep investing in and improving its cloud? 
  • right now, Microsoft's chances look pretty good to me. No wonder they put the cloud guy in charge of the company.
Gary Edwards

Online brochure maker by pub HTML5 is available online for everyone - WhaTech - 0 views

www.whatech.com/...-available-online-for-everyone

HTML5 HTML5-CSS3-JavaScript

shared by Gary Edwards on 28 Dec 15 - No Cached
  • Gary Edwards on 28 Dec 15
     
    "The press release introduces detailed capabilities of PUB HTML5's online brochure maker. The software is developed for people to prepare brochures online easily. PUB HTML5 is a leading publishing destination suitable for business owners, non-profit organizations as well as individuals. Whether you have a small scale business or a huge multinational company, you can certainly depend on PUB HTML5 for digital publishing. It is an open access HTML5 Digital Publishing Platform that allows you to convert PDF, MS Office and Open Office documents to HTML5 and jQuery based publications at no cost at all. These features make your flipbook even more attractive for the customers. Anna Lee, the chief designer of PUB HTML5 has announced a new online brochure maker (http://pubhtml5.com/digital-brochures-maker). It would make brochure designing simpler for the users. With the help of this software, you will be able to customize your catalogs, brochures and magazines online. More than six lakh users rely on PUB HTML5 for online publishing. The content published using the software program is compatible with all leading computers, laptops, tablets and mobile interfaces. Operating Systems like Android, iOS and Windows 8 also support this software quite well."
Gary Edwards

Microsoft pushes Trade Secrets Bill - 1 views

thestack.com/...trade-secrets-act-2015-support

Trade-secret-legislation Microsoft Patents Microsoft-Patent-Consortium

shared by Gary Edwards on 09 Dec 15 - No Cached
  • A spokesman for the Microsoft On The Issues website has expressed the company’s support for new legislation that would reform the legal framework for companies wishing to protect their trade secrets in a cloud-centric world where such information is frequently forced to reside on networks. In the post Microsoft’s Assistant General Counsel of IP Policy & Strategy Jule Sigall rallies behind business and academic concerns supporting the proposed Defend Trade Secrets Act 2015 (DTSA), which goes before the United States Senate Judiciary Committee today. Sigall, who is also Associate General Counsel for Copyright in Microsoft’s Legal & Corporate Affairs department, makes an ardent case for reform of the current legislation, as furnished by the Uniform Trade Secrets Act (UTSA). UTSA’s provisions are argued to be fractured, and rendered ineffective both by the inability of plaintiffs to pursue suits in federal courts (despite trade secret infractions being Federal by nature), and by the fact that not all states have adopted or instituted all the measures provided by the legislation. Additionally the limited provision for redress in international cases of trade secret theft are to be addressed.
  • Sigall presents the case of Microsoft’s Cortana AI as an example of why new legislation is necessary: ‘[Behind] Cortana sits a vast amount of technology developed or enhanced in-house by Microsoft – voice recognition; language translation; reactive and predictive algorithms that can synthesize context, location and data, and interface with the vast resources of the Bing search engine index; and a complex array of cloud servers to crunch and serve data in real time. This technology represents tens of thousands of hours of research, trial and error, and continued improvement as Cortana is adapted for new devices and new scenarios’
  • Sigall argues that better protection procedures for trade secrets, the only form of IP which currently lacks comprehensive cover in law, is essential for start-ups whose ideas, business plans and even customer lists may constitute the only marketable value of a company that is just in the stage of consolidating. ‘A trade secret is unique among forms of intellectual property in how it is legally protected. While it is a federal crime to steal a trade secret, a business that has its trade secrets stolen must rely on state law to pursue a civil remedy. Owners of copyrights, patents, and trademarks can go to federal court to protect their property and seek damages when their property has been infringed, but trade secret owners do not have access to such a federal remedy.’
  • ...7 more annotations...
  • Defend Trade Secrets Act 2015 contains [PDF] significant material from its doomed predecessor of 12 months ago, and one of its boldest initiatives is the extension of ex parte seizures, instituted in UTSA in a more limited form (particularly in the 1985 amendment to the Uniform Law Commission’s 1979 initial legislation). An ex parte seizure provides a kind of restraining order or injunction on disputed information, or even the dissemination of knowledge about whether the information is disputed, and places it under federal protection on the plaintiff’s behalf.
  • Microsoft had a hard time adjusting to the open source revolution, particularly in regard to the PC/Mac Office product which at one time represented the most successful and ubiquitous software in the world, and the many legal and semantic wrangles over the closed-source nature of Office formats such as Word led ultimately to a hybridised open source .docx format which is still argued to not be the OpenXML that was promised.
  • According to Sigall the state-by-state system currently in place was ‘simply not built with the digital world in mind’, and calls for ‘A uniform, national standard for protection’ which does not stop at state lines or even national borders.
  • In practical terms this seems likely to extend the circumstances under which information about leaks, hacks or thefts of information can be made the subject of gag orders for legal reasons, since it brings trade secrets into the same legal framework as other forms of intellectual property which enjoy more comprehensive coverage and recourse in law. The bill would also extend the purview of the 1996 Economic Espionage Act to take in a more rigorously conceived concept of ‘trade secrets’.
  • Even with the issues clear, the risk of disproportionate or over-reaching response in the event of the new bill passing successfully through congress in 2016 (it is unlikely to pass this year) is clear enough that the lack of network discussion about it is quite surprising. Essentially DTSA represents the same kind of proposed ‘judicial fast track’ – though in favour of corporations instead of governments – that has outraged so many commenters in the wake of the November 13th Paris attacks.
  • Silence in court Amongst its more quotidian clauses, the Defend Trade Secrets Act 2015 effectively offers corporate plaintiffs increased opportunity to federalise disputed private material in cases involving trade secrets, with all the penalties for infraction associated with that change of status – and far greater scope for sub judice orders likely to contain and conceal future breaches of information.
  • Eric Goldman of the Santa Clara University School of Law has just published a paper outlining the risks of extending ex parte seizures in the manner that DTSA 2015 proposes. Goldman writes that ‘the Seizure Provision does not solve many, if any, problems. In light of the remedies already available to trade secret owners in ex parte temporary restraining orders (TROs), the Seizure Provision purports to apply to only a narrow set of additional circumstances. In exchange for that modest benefit, the Seizure Provision creates the risk of anti-competitive seizures and seizures that cause substantial collateral damage to innocent third parties. To discourage such abuses, the Act imposes procedural safeguards and creates a cause of action for wrongful seizures. Unfortunately, those safeguards are miscalibrated to achieve the desired protections against abusive seizures.’
  • Paul Merrell on 09 Dec 15
     
    Lots of possible Constitutional issues lurking. The Constitution creates only two types of intellectual property, patents and copyrights. "(P)roperty interests . . . are not created by the Constitution. Rather, they are created and their dimensions are defined by existing rules or understandings that stem from an independent source such as state law." Ruckelshaus v. Monsanto Co., 467 US 986 (1984), https://goo.gl/ZljO1H (trade secrets case). The traditional source of rights in trade secrets have been state law. Thus there is a state's rights issue lurking in this legislation, a question whether the federal government is invading the States' police power, an "our federalism" question.
Gary Edwards

OOXML in Norway: The haywire process | Geir Isene : Straight talk on IT - 0 views

blogs.freecode.no/isene

interoperability iso odf officeopenxml ooxml opendocument

shared by Gary Edwards on 12 Dec 07 - Cached
  • I had read the essay by Jon Bosak (SUN Microsystems) on why SUN voted as it did in the US. He lays out a very different strategy. His view is that the battle is lost to completely reject OOXML as an ISO standard. ISO can only reject it with comments, and that is equivalent to giving Microsoft a todo-list on how to fix the draft so as to get it approved. Microsoft has sufficient manpower to easily tackle that. Most of us had missed what Mr. Bosak saw: OOXML promises interoperability with earlier closed binary formats (the Word Doc, older Excel file formats etc.). But it doesn’t deliver. How on earth could someone be able to convert old binary files to the new format without having the specification of the old formats and a mapping to OOXML. If you are to translate some text from Chinese to English, it doesn’t much help to only know English.
    • Gary Edwards
      Gary Edwards on 12 Dec 07
       
      A "Yes with comments" is a yes for the ISO approval of MS-OOMXL. If ISO approves MS-OOXML, it won't matter what Bosak's "comments" strategy is. Microsoft and the Vista Stack will be off to the races. The full disclosure of the MS binary document secret blueprint won't matter much at that point.
  • “Ah c’mon Bosak, you are chickening out, we must stop this dead in the track”
    • Gary Edwards
      Gary Edwards on 12 Dec 07
       
      There you go Geir!

      Sun and Bosak have held the door open for MS-OOXML since 2002, when Sun blocked an effort to write the ODF Charter to include as a priority, "compatibility with existing file formats". This of course would include the billions of legacy MS binary documents.

      The thing is that those who work in the conversion-translation field will tell you that it is currently impossible to pipe converted legacy binary documents and OOXMl docs for that matter into ODF. Just as Microsoft claims, ODF in it's current state is insufficient and unable to handle the rich feature set of the MSOffice developers platform.

      The problem could of course be easily fixed by the inclusion in ODF of five structural generics. In the past year, there have been no less than five iX "interoperability enhancement" proposals submitted to the OASIS ODF TC for discussion and consideration. As uber universal interop expert Florian Reuter points out in his blog, these iX proposals did not fare so well.

      What Florian doesn't point out is that it was Sun who opposed any and all efforts to improve compatibility with existing Microsoft binary and OOXML documents. Just as they have done for nearly five years now.

      Sort of puts the Sun-Bosak support for ISO approval of MS-OOXML in a different light. ~ge~
  • Gary Edwards on 12 Dec 07
     
    see the sticky notes on this one
Gary Edwards

The Microsoft Document Juggernaut: ECMA to Begin Drafting XPS as Alternative Standard t... - 0 views

www.betanews.com/...1183144526

davinci iso massachusetts microsoft odf officeopenxml ooxml opendocument xml

shared by Gary Edwards on 12 Dec 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 12 Dec 07
     
    More on Andy UpDegrove's "Game Over for open standards" comment.
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 kagle odf ooxml w3c

shared by Gary Edwards on 12 Dec 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 12 Dec 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 12 Dec 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

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

Harmonizing ODF and OOXML using NameSpaces | Tim Bray's Thought Experiment - 0 views

www.tbray.org/...Office-XML

bray florian-reuter namespaces odf ooxml opendocument openxml

shared by Gary Edwards on 07 Mar 08 - Cached
  • First, what if Microsoft really is doing the right thing? Second, how can we avoid having two incompatible file formats? [Update: There’s been a lot of reaction to this piece, and I addressed some of those points here.]
  • On the technology side, the two formats are really more alike than they are different. But, there are differences: O12X’s design center, Microsoft has said repeatedly, is capturing the exact semantics of the billions of existing Microsoft Office documents. ODF’s design center is general-purpose reusability, and leveraging existing standards like SVG and MathML and so on.
    • Gary Edwards
      Gary Edwards on 07 Mar 08
       
      OOXML, or to put it more accurately "O12X" as Tim suggests, is designed to capture the exact semantics of MSOffice 12. In fact, OOXML is an XML encoding of the MSOffice 12 in-memory-binary-representation dump. When it comes to representing older versions of MSOffice documents, OOXML must use legacy compatibility settings" to capture the semantics. And it's not an exacting science to say the least. The thing is, OpenOffice ODF uses the same technique resulting in application specific ODF documents with over 150 un docuemnted, unspecified "compatibility settings". After years of requests from the OASIS ODF Technical Committee to document these application specific settings, Sun has yet to provide any kind of response. And this kills ODF interoperability. Especially concerning KOffice. There is also the issue of OASIS ODF high-jacked namespaces. When ODF applications reference a namespace, the actual URL is high-jacked with http://oasis-open.org/???? replacing the proper namespace of http://W3C.org/???? This high-jacking impacts the oDF reuse of important W3C technologies such as XForms, SVG, MathML, and SMiL. So where's the problem you ask? Well, when a developer imports or tries to process an OpenOffice ODF document, they rely on say the W3C XForms specification for their understanding. OpenOffice however seriously constrains the implementation of XForms, SVG, MathML, RDFa and RDF/XML. This should be reflected in the new namespace. However, if you follow the high-jacked URL, you'll find that there is nothing there. There is no specification describing how OpenOffice implements XForms in ODF! This breaks developer libraries, breaks ODF interoperability between ODF applications, and, offends the W3C to no end. So i think it might be fair to say that at this point, neither ODF or OOXML have come close to fulfilling their design objectives.
  • The capabilities of ODF and O12X are essentially identical for all this basic stuff. So why in the flaming hell does the world need two incompatible formats to express it? The answer, obviously, is, “it doesn’t”.
    • Gary Edwards
      Gary Edwards on 07 Mar 08
       
      Exactly!! Except for one thing that Tim misses: the presentation layers of both ODF and OOXML are application specific. It is also the application specific nature of OpenOffice ODF presnetation layer that prevents interoperability with KOffice ODF! There is near zero interop between OpenOffice and KOffice, and KOffice has been a contributing member of the OASIS ODF TC for FIVE YEARS! It's the presentation layer Tim. ODF and OOXML are application specific formats because their presentation layers are woefully applicaiton specific and entirely reflective of each applications layout engine and feature set implementation model. I often imagine what ODF would be like if back in 2001, Sun had chosen to implement CSS as the OpenOffice presentation layer instead of the quirky but innovative, and 100% application specific automatic-styles presentation layer we now see in ODF. Unlike ODF's "automatic-styles", CSS is a totally application independent presentation model prized exactly for it's universal interoperability!
  • ...1 more annotation...
  • The ideal outcome would be a common shared office-XML dialect for the basics—and it should be ODF (or a subset), since that’s been designed and debugged—then another extended vocabulary to support Microsoft features , whether they’re cool new whizzy features or mouldy old legacy features (XML Namespaces are designed to support exactly this kind of thing). That way, if you stayed with the basic stuff you’d never need to worry about software lock-in; the difference between portable and proprietary would be crystal-clear. And, for the basic stuff that everybody uses, there’d be only one set of tags. This outcome is technically feasible. Who could possibly be against it?
    • Gary Edwards
      Gary Edwards on 07 Mar 08
       
      Bingo! ODF and OOXML should strip off the application specific complexities and seek a neutral generic XML representation of basic document structures common to ALL documents. Then, use the XML NameSpace mechanism to extend (with proper descriptions) the generic to include the volumes of application specific features that now fill each format. One thing i disagree with Tim about. And that's that the interop of ODF and OOXML is hopelessly broken. The OpenDocument Foundation tried for over a year to close the compatibility gap between ODF and MSOffice binary - xml documents. The OASIS ODF TC would have none of it. IBM and Sun are set on a harsh course of highly disruptive and costly rip-out-and-replace of MSOffice based on government mandates for ODF. There is no offer of compromise to be had. On the Microsoft side, even if they did want to compromise (a big IF), there is that problem of over 550 million MSOffice workgroup-workflow desktops to contend with. The thing is, the only way to harmonize, merge, convert or translate between two application specific formats is to actually harmonize the applications themselves. While the generic subset is a worthy goal, the process would be fraught with real world concerns that the existing application workflows are not disrupted. My proposal? Demand that ODF and OOXML application vendors provide format options for PDF, and the W3C's family of formats: (X)HTML5, (X)HTML - CSS, and CDF (XHTML-CSS-XForms-SVG-SMil-MathML). That will do it. We might never see the quality of interoperability we had hoped for in a desktop application to application scenario. But we can and should fully expect high quality interop at the higher level of the Web. You can convert an application specific format to a generic like CDF. By setting up conversion channels to the same CDF profile within MSOffice, OpenOffice, KOffice, Symphony, and Google Docs, we can achieve the universal interoperabil
Gary Edwards

Study: Open Document Format made gains in '07 | InfoWorld | News | 2008-01-04 | By Chri... - 0 views

www.infoworld.com/...-Format-gained-momentum_1.html

alliance cdf ibm mandates oasis odf ooxml opendocument

shared by Gary Edwards on 11 Jan 08 - Cached
  • "It's one thing to recognize ODF as a matter of policy in an enterprise architecture framework and another to mandate its use," he added. "Proprietary formats in the public sphere are going out of style and becoming unacceptable globally."
    • Gary Edwards
      Gary Edwards on 11 Jan 08
       
      That's right! Which is why announcing a preference for HTML, XHTML, PDF and ODF is meaningless. A mandate for ODF RATHER THAN OOXML is the only way ODF can succeed as an open standard.
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

NYS Open Records Discussion Must Recognize Technical Requirements - 0 views

www.ibiblio.org/...nys-open-records-policy.html

ajax cdf odf ooxml pdf webkit

shared by Gary Edwards on 15 Oct 08 - Cached
  • Gary Edwards on 15 Oct 08
     
    While the workgroup failed to decide between "choice" (Microsoft's mantra) and "openness" (the ODF mantra), predictably punting this question to a new Electronic Records Committee, it did issue a number of interesting findings, the most important of which reads as follows: In the office suite format debate, there currently is no compelling solution for the State's openness needs. The State needs open standards and formats. Simultaneously, the State needs electronic records to be preserved in their original formats whenever possible. Many Request for Public Comments commenters, particularly in response to the e-discovery questions, stated preserving a record in the same format as it was created results in a more faithful record and diminishes the possibility of expensive e-discovery disputes. This is important to ensure future generations of New Yorkers can access the permanently valuable electronic records being created today. Moreover, State Archives emphasizes creating records in open formats makes it easier to preserve their essential characteristics and demonstrates they are authentic (i.e., they were created in the course of State government business and have not been altered without proper authorization). I imagine that the workgroup must have found some level of solace in arriving at the one conclusion that all the experts seem to agree on: that electronic documents should be published using the same format in which they are created. If this principle held true for state documents, it would reduce the job of the new Electronic Records Committee to deciding between three alternatives: (1) require all state agencies to create and publish their documents in OOXML, (2) require all state agencies to create and publish their documents in ODF, or (3) allow each agency to decide which of these formats, OOXML or ODF, they will use in creating and publishing their documents. Unfortunately, this central assumption is incorrect, and adopting it as a basi
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

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

www.princexml.com

cagle cdf css w3c xhtml

shared by Gary Edwards on 12 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

EICTA White Paper on Standardisation and Interoperability - 0 views

74.125.155.132/search

interoperability

shared by Gary Edwards on 03 Aug 09 - Cached
  • Gary Edwards on 03 Aug 09
     
    Standardisation is one of the key facilitators for interoperability of networks, services and equipment. Interoperability in this sense has gained increasing attention and demand inthe market-place. Thus, in response to market-driven needs interoperability is becomingan important requirement in standards projects.This white paper examines the standards development process as well as the actors involved and proposes a set of recommendations in standards development that will help to address interoperability challenges that may occur and can be observed instandardisation. At the same time it provides an agreed industry position on key aspects for standards development. Observing these recommendations - as is done by a lot of actors in standardisation already, including formally established standards setting bodies - may help to increase the level of interoperability in standardisation. This white paper aims at strengthening the awareness to observe interoperability issues at an early stage and make those issues an important consideration as part of the standards-setting process. EICTA's recommendations for the standards development process:
‹ Previous 21 - 40 of 42 Next ›
Showing 20▼ items per page