An hour or so ago Sun Microsystems made good on an earlier pledge to issue further "non-assertion covenants" (NACs) in support of open standards. That's a good thing, and more vendors should do the same thing.
It's now been more than a week since Microsoft announced that its licensing discussions with Adobe had fallen apart after four months of negotiations. We don't know a great deal more now that Adobe has released a statement, but what we do know is bad for open standards.
Item: "Having the latest computer technology is great. But what e-government users from the public sector as well as citizens really want is software interoperability. Unfortunately IT managers still only pay lip service to such interoperability, concludes a European project assessing today's open-source movement."
Two years ago, a wireless standards war between the US and China escalated to the highest levels of government before a truce was reached, with then-Secretary of State Colin Powell personally intervening. The subject then was the WiFi wireless standard, and the challenger was a Chinese competitor with a security algorithm called WAPI. That truce, unfortunately, is now breaking down.
For a week now, the IT world has been scratching its collective head over the breakdown of PDF licensing negotiations between Microsoft and Adobe. What was there to breakdown over, if PDF is a standard?
In this third interview in a continuing series, I interview Sun's Erwin Tenhumberg, in order to compare StarOffice 2.0 with the other leading software productivity suites that support ODF (previous interviews have focused on KOffice and OpenOffice).
Recently, spokespersons for Microsoft's standards group have been promoting "design, collaboration and licensing" as alternatives, rather than supplements to, open standards. Maybe Adobe's been listening.
Two weeks ago, a Word Trojan with minimal impact was in the news, and now its StarOffice's turn, having taken a single "proof of concept" hit. So far, the "Stardust" virus seems to be bigger news.
Before there was Linux, before there was open source, there was (and still is) an operating system called Unix that was robust, stable and widely admired. It was also available under license to anyone that wanted to use it, and partly for that reason many variants grew up and lost interoperability - and the Unix wars began. The same thing could happen to Linux.
The Word Trojan virus is reported to have infected only two targets - but it received extensive coverage for a week. Given the limited facts to work with, journalists were left to deal mostly with "what ifs."
Three years ago, celebrated security expert Dan Geer lost his job at @stake when he co-authored a paper on the dangers that the Microsoft "monoculture" represented for end-users. He knew what he was talking about.
For the last couple of weeks I've been writing a number of blog entries focusing on poorly researched and deliberately misleading items in the news. One of those pieces is called "The Script Reloaded: Recognizing 'Them.'" Surprise - "They" have written another article.
The first draft of Open XML has been posted for public viewing - and it's bigger than ever.
There have been a number of stories published on-line in recent days that warrant both comment and qualification. That's both good news and bad news.
In this second in a series of interviews with the major open source and proprietary implementations of ODF, I learn from OpenOffice.org's Louis Suarez-Potts and John McNeesh how OO compares to the competition, wherein lie its strengths, and where it will head in the future.
It's not my goal at this blog to nominate myself as the official FUD Ombudsman for the contest between the ODF standard and Microsoft's Open XML (especially since the connotations of the name "Ombudsman" in this saga ain't what they used to be). But...
"Public Relations" is one of those funny phrases that has very little to do with what it really means. At sixty thousand feet, it's about influencing opinion, which (at that altitude) doesn't sound all that bad. But when it gets down into the bushes, it starts to become a bit less innocuous, and more unsavory.
This blog entry is a rarity for me: an exegesis on the deliberate disinformation of a single vendor. Of course, calling out falsehoods by some vendors is like shooting the same old fish in a barrel, but occasionally you have to haul out the firearm when they start landing in your soup.
Last week, the Massachusetts Information Technology Division (ITD) issued a Request for Information (RFI) on any plugins that might be under development to assist it in migrating from a MS Office environment to one based upon software that supports ODF. Perhaps Microsoft may be willing to lend a hand.
There are already multiple implementations of the OpenDocument Format (ODF) in the marketplace. Why do adopt a standard - and therefore by definition go head to head with their competitors?