Skip to main content

Home/ Document Wars/ Group items tagged HTML

Rss Feed Group items tagged

Gary Edwards

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

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

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

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

Aptana Jaxer | Aptana - 0 views

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

Re: [office-comment] Public Comment - 0 views

  • Regarding section 1.5 itself: The Open Office TC decided to use the term MAY rather than MUST (or will) at the mentioned location, because it wanted to ensure that the OpenDocument specification can be used by as many implementations as possible. This means that the format should also be usable by applications that only support a very small subset of the specification, as long as the information that these applications store can be represented using the OpenDocument format. A requirement that all foreign elements and attributes must be preserved actually would mean that some applications may not use the format, although the format itself would be suitable. Therefor, we leave it up to the implementations, which elements and attributes of the specification they support, and whether they preserve foreign element and attributes. Some more information about this can be found in appendix D of the specification.
    • Gary Edwards
       
      This OASIS ODF discussion is about the Compliance - conformance clause of the ODF specification: Section 1.5. A developer has complained that use of MAY instead of MUST in the wording of the clause would enable conforming applications to destroy foreign elements and alien attribute markup at will. This of course would result in ZERO Interoeprability!!!!! The foreign elments and alien attributes were included for the purposes of improved ODF compatibility with the billions of MSOffice binary documents that would need to be converted to ODF. Sadly, the section 1.5 loop hole falls short of the compatibility goal, but that only begins to scratch the surface of the ODF problems. OpenOffice only supports foreign elements and alien attributes for text spans, and paragraphs!!!!!! All other such markup is unrecognized and therefore "destroyed" by OpenOffice. ZERO interop. No roundtripping with MSOffice desktops. Lossy conversion with jagged fidelity. Guaranteed.
Gary Edwards

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

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

Jonathan Schwartz: Today We Love the GPL! Live for the moment because it may not last - 0 views

  • It's driven competition into a market which historically had none - and it's created an opportunity for the world to standardize on an open, royalty and patent free file format for exchanging documents.
  •  
    Public posturing in overdrive.  Warp speed overdrive. 
Gary Edwards

PlexNex is Reaching New Audiences - 0 views

  •  
    Another great post from Sam. Maybe he'll soon be talking about what really happened in Massachusetts? Sam starts off his discussion with the plexnex traffic metrics. Soon enough though, he gets into OpenDocument, the Foundation's plugin, and events in
  •  
    Another great post from Sam. Maybe he'll soon be talking about what really happened in Massachusetts? Sam starts off his discussion with the plexnex traffic metrics. Soon enough though, he gets into OpenDocument, the Foundation's plugin, and events in
  •  
    Another great post from Sam. Maybe he'll soon be talking about what really happened in Massachusetts? Sam starts off his discussion with the plexnex traffic metrics. Soon enough though, he gets into OpenDocument, the Foundation's plugin, and events in
Gary Edwards

Infocon 4 - DOD bars use of HTML e-mail, Outlook Web Access - 0 views

  •  
    Wow, Outlook and Web OutLook eMail hit Infocon 4 and are banned by the DOD. The MS Exchange/ShrePoint Hub has been on a tear, with governments worldwide leading the way. And now this? Government mandates to use ODF on the desktop did not stop governmen
  •  
    Wow, Outlook and Web OutLook eMail hit Infocon 4 and are banned by the DOD. The MS Exchange/ShrePoint Hub has been on a tear, with governments worldwide leading the way. And now this? Government mandates to use ODF on the desktop did not stop governmen
  •  
    Wow, Outlook and Web OutLook eMail hit Infocon 4 and are banned by the DOD. The MS Exchange/ShrePoint Hub has been on a tear, with governments worldwide leading the way. And now this? Government mandates to use ODF on the desktop did not stop governmen
Gary Edwards

XML.com: Introducing RDFa - 0 views

  •  
    The legendary XML blogger Bob DuCharme has written an excellent summary of RDFa including a how to explanation of XHTML with RDFa metadata. As some might know, the OASIS ODF Metadata Sub Committee is adopting a RDF/XML RDFa approach. Sun representatives
  •  
    The legendary XML blogger Bob DuCharme has written an excellent summary of RDFa including a how to explanation of XHTML with RDFa metadata. As some might know, the OASIS ODF Metadata Sub Committee is adopting a RDF/XML RDFa approach. Sun representatives
  •  
    The legendary XML blogger Bob DuCharme has written an excellent summary of RDFa including a how to explanation of XHTML with RDFa metadata. As some might know, the OASIS ODF Metadata Sub Committee is adopting a RDF/XML RDFa approach. Sun representatives
Gary Edwards

Keeping both sides honest - O\'Reilly XML Blog - 0 views

  • The former State Government CIO of Massachusetts (a state in USA) Louis Gutierrez has a worthwhile interview in Computerworld this week. What I like about the article in particular is that he seems clear that the role of govenment is not just to passively accept standards, but to pragmatically assess the suitability and impact and processes of each one. ISO makes “voluntary standards” not laws. Gutierrez says the obvious: that there is a marked difference in the feature set between ODF and OpenXML (”straightforward simplicity” versus “feature-rich but very idiosyncratic diversty”): he does not trivialize the difference in coverage or scope between the two.
  •  
    Finally, someone in Massachusetts is talking and it's the master, Louis Gutierrez.  Wiki Ricki has some nice comments about the ComputerWorld interview with Louis.  As have become his custom though, Rick once again carries the flag (or should i say water) for Microsoft.  Rick's expertise in XML used to be the draw for his column.  Now you have to parse through his comments, separating the nuggets of truth from the torren of bias.  Paid bias.  It's too bad.  Rick was one of the best. 
Gary Edwards

ODF Can Handle Anything MSOffice Throws At It - 0 views

  •  
    This commentary, based on Tim Bray's "Life is Complicated" blog and comment section, was published by Lxer.  Well worth the examination.
Gary Edwards

What is "Contradiction" of an ISO Standard? - O'Reilly XML Blog - 0 views

  •  
    Microsoft Wikipedia Shill Rick Jelliffe weighs in on the "contradiction" definition issue.  Rick is well known XML expert, and prior to his contracting out as a hired shill for Microsoft, was much respected.  Patrick Durusau, ODF editor and co chairman of the ISO/IEC JTSC1 committee that reviewed ODF and will be responsible for MS Ecma 376, requested the clarification.

    Rick J provides a nice framework for approachign the "contradiction definition" issue, but fails to provide an expert opinion on MS Ecma 376. 

    Anyone familiar with Rick's comments in the past will come away from this article much surprised.  He went all wobbly when it came time to make the call on MS Ecma 376.  This kind of wishy washy opinion is hardly what we've come to expect. 

    I guess the shill contract incuded much more than pasting up Wikipedia to make Microsoft look like an honest broker of information technologies. 

    ~ge~

  • ...2 more comments...
  •  
    Microsoft Wikipedia Shill Rick Jelliffe weighs in on the "contradiction" definition issue.  Rick is well known XML expert, and prior to his contracting out as a hired shill for Microsoft, was much respected.  Patrick Durusau, ODF editor and co chairman of the ISO/IEC JTSC1 committee that reviewed ODF and will be responsible for MS Ecma 376, requested the clarification.

    Rick J provides a nice framework for approachign the "contradiction definition" issue, but fails to provide an expert opinion on MS Ecma 376. 

    Anyone familiar with Rick's comments in the past will come away from this article much surprised.  He went all wobbly when it came time to make the call on MS Ecma 376.  This kind of wishy washy opinion is hardly what we've come to expect. 

    I guess the shill contract incuded much more than pasting up Wikipedia to make Microsoft look like an honest broker of information technologies. 

    ~ge~

  •  
    Microsoft Wikipedia Shill Rick Jelliffe weighs in on the "contradiction" definition issue. Rick is well known XML expert, and prior to his contracting out as a hired shill for Microsoft, was much respected. Patrick Durusau, ODF editor and co chairman of
  •  
    Microsoft Wikipedia Shill Rick Jelliffe weighs in on the "contradiction" definition issue. Rick is well known XML expert, and prior to his contracting out as a hired shill for Microsoft, was much respected. Patrick Durusau, ODF editor and co chairman of
  •  
    Microsoft Wikipedia Shill Rick Jelliffe weighs in on the "contradiction" definition issue. Rick is well known XML expert, and prior to his contracting out as a hired shill for Microsoft, was much respected. Patrick Durusau, ODF editor and co chairman of
Gary Edwards

Yankees in the Court of King Arthur, with a Microsoft Agenda - 0 views

  •  
    ANSI/INCiTS has completed their review of Ecma 376, and is ready to cast their ISO/IEC Contradiction Review Phase Fast Track Ballot in favor of Ecma 376 being rammed through ISO. Guess who's carrying Microsoft's water?
  •  
    ANSI/INCiTS has completed their review of Ecma 376, and is ready to cast their ISO/IEC Contradiction Review Phase Fast Track Ballot in favor of Ecma 376 being rammed through ISO. Guess who's carrying Microsoft's water?
  •  
    ANSI/INCiTS has completed their review of Ecma 376, and is ready to cast their ISO/IEC Contradiction Review Phase Fast Track Ballot in favor of Ecma 376 being rammed through ISO. Guess who's carrying Microsoft's water?
Gary Edwards

BetaNews | ECIS Accuses Microsoft of Plotting HTML Hijack - 0 views

  • Nonetheless, from ECIS' perspective, the lone enemy is at the gate: "With XAML and OOXML," stated ECIS attorney Thomas Vinje, "Microsoft seeks to impose its own Windows-dependent standards and displace existing open cross-platform standards which have wide industry acceptance, permit open competition and promote competition-driven innovation. The end result will be the continued absence of any real consumer choice, years of waiting for Microsoft to improve - or even debug - its monopoly products, and of course high prices."
  •  
    There you go!  The Micrsoft plot to take over the Internet in a nutshell, with XAML and EOXML at the point of the spear.

    Funny how everyone knows what Micrsoft's intentions are, even having identified the tehcnoliges to be used, but still no one can stop them.  How did this recidivist reprobate get so outside the rule of law and beyond the reach of good men?

    EOXML (MS Ecma 376) must be stopped at ISO/IEC, if only to slow down this worldwide train wreck they plan for our beloved and open Internet.

Gary Edwards

fr0mat.net: PLUGIN: Default to ODF - 0 views

  • This permits individuals & organizations to configure their PCs to open, save and work primarily in the ISO OpenDocument Format.
  •  
    No, it does much more.  The default file setting feature is what will break the monopolists iron grip!
  • ...1 more comment...
  •  
    No, it does much more.  The default file setting feature is what will break the monopolists iron grip!
  •  
    No, it does much more.  The default file setting feature is what will break the monopolists iron grip!
  •  
    No, it does much more.  The default file setting feature is what will break the monopolists iron grip!
Gary Edwards

Microsoft Closer on \'Office Open\' Blessing - 0 views

  • Opponents to OOXML, which include IBM (Quote) and the Open Document Foundation, have argued that Microsoft's specifications are unwieldy and that the standard application is redundant with the Open Document Format (ODF), which already exists. Microsoft has countered that the OOXML format is valuable because it is closer to Office 2007 and is backwards-compatible with older versions of Office. "Although both ODF and Open XML are document formats, they are designed to address different needs in the marketplace," the company wrote in an open letter published earlier this month.
  •  
    Internet News is reporting that Ecma has submitted to the ISO/IEC JTC1 their repsonsess to the 20 "fast track" for Ecma 376 (OOXML) objections.  Nothing but blue skies and steady breeze at their back for our friends at Redmond, according to Ecma's rubber stamper in chief, Jan van den Beld.

    Once again there is that ever present drum beat from Microsoft that ODF can't handle MSOffice and legacy MSOffice features - including but not mentioned the conversion to XML of those infamous billions of binary documents:
    "Microsoft has countered that the OOXML format is valuable because it is closer to Office 2007 and is backwards-compatible with older versions of Office. "Although both ODF and Open XML are document formats, they are designed to address diffe
Gary Edwards

Vista and Office 2007 spin tales from the Underground | Channel Register - 0 views

  • Firstly it is a back end to what most people would traditionally think of as "Microsoft Office", i.e. the suite of desktop tools (Word, PowerPoint, Excel and so on). In this respect, it acts as a hub for collaboration, document storage/sharing, search and a range of other functions. However, SharePoint can also be used independently of the Office desktop components as a very respectable and capable portal environment for serving up either native .Net or composite applications to users through a browser.
  •  
    Excellent article about Vista and MSOffice "System" 2007 as development platforms.  The author provides one of the better explanations of how MSOffice 2007 and SharePoint "Hub" are connected and joined at the hip.  Hey, i invented tha tterm "Hub"!  Or so i thought.  I guess some things are just obvious.

    My use of the term "Hub" to describe an XML turnstile where backend information meges with portal interfaces, email, messaging, and document storage/collaboration goes back to the 2003 "Sales and Inventory" management system prototype we built for Comcast.  Desktops connect to the hub through XML documents, XForms and Jabber XMPP data binding, and browsers.  Great stuff - the way SOA should be done!

Gary Edwards

Open Stack: Game Time for OpenDocument - 0 views

  • IMHO, it all comes down to one question: > *... Is ODF able to handle everything EOOXML was designed for? Is there something you can do in EOOXML that can't be done with ODF? > Microsoft insists that the reason they developed EOOXML is that ODF is inadequate and unable to handle the advanced features of MSOffice, and, most importantly, the billions of binary legacy documents produced by the many versions of MSOffice still in production. > The answer to this question is that ODF can handle everything MSOffice can throw at it. > There are two ways of proving this. >
  •  
    The primary difference between ODF and MOOXML is that ODF was designed to be a universal file format.  MOOXML was designed to be an XML file format for MSOffice, the Win32 API, and the Vista Information Processing Chain API (.NET 3.0). 

    ODF is application and platform independent.  MOOXML is application and platform specific.  It's bound to the Windows - Vista platform. 

    Microsoft's Brian Jones recently got caugh tup in a argument with the heavily armed WMD ODF expert and combatant Sam Hiser (WMD=Words of Massive Destruction).  In their exchange, Brian got confused over this very important distinction between ODF and MOOXML.  ODF allows specific applications to place their configurations and requirements in a settings file that is separate from the content, presentation and metadata containers.  MOOXML on the other hand makes no distinction whatsoever between application specific (MSOffice only) configuration, settings, processsing instructions and systemm dependencies and the rest of the file format contents.  Application settings are bound to content, presentation, and schema containers.  So bound that Brian is seemingly unaware of what ODF has achieved.  Sam caught him by surprise, as did many others posting comments:

    Brian Jones on MOOXML support for older versions of MSOffice:  Coments by Sam the WMD Man are below.


Gary Edwards

PlexNex: HUMOR: Interoperability, Choice and Open XML - 0 views

  • reflects the functionality in those products.
  • It is important to recognize that ODF and Open XML were created with very different design goals and that they are only two of many document format standards in use today, each of which has characteristics that are attractive to different users in different scenarios
  •  
    Sam really nailsit with this satirical commentary on the spliny whiny letter Microsoft wrote begging the world to reconsider the proprietary application and platform bound Microsoft Office Open XML file format as an international standard for office productivity suites.
« First ‹ Previous 181 - 200 of 244 Next › Last »
Showing 20 items per page