Slashdot Mirror
Danish Study Recommends Open Standards for EU
PDAJames writes "The Danish government has wrapped up a two-year study of open source's potential for the public sector, and has some pretty interesting things to say. For one, it says that tie-ins to proprietary software effectively eliminate competition for government procurement and are inherently bad. For another, it recommends a public sector-led effort to adopt an XML-based standard document format, either that of OpenOffice or a new one developed by the EU. Will they push ahead with these plans or is it just more talk?"
Actually they are using a warped XML - not TRUE XML. Just like they did with Palladium - took over someone else's format and warped it.
Why don't the KDE developer stop working on KOffice and support OpenOffice instead?
We need more people working on OpenOffice. OpenOffice is the only product that has a chance against MS Office.
Maybe, in the light of the release of Windows RG edition they should rethink their position on proprietry software..
"You lied to me! There is a Swansea!"
Open standards are the best thing imaginable for the customer. The data that software manages is consistently orders of magnitude more valuable than the hardware/software that does the managing.
This wont open up things entirely, there are still patented feature sets, and purely proprietary technologies. It will at least let the best product win, not the company that got their first.
it says that tie-ins to proprietary software effectively eliminate competition for government procurement and are inherently bad.
Well, I might say that if one were considering government procurement only, they might be inherently bad. But there absolutely *is* good software out there that is proprietary that is good, and better than anything available open source. This is not to say I am not in favor of open source. Quite the contrary, I believe in an open source foundation, but companies should be allowed to bid on contracts for their proprietary products as long as those products are either based on open source, or support open source formats and alternatives.
Visit Jonesblog and say hello.
It's hard to imagine something smart to come from a country that sent a corvette, snow plows and other winter equipment and a submarine (that broke down before its first mission) to help in the war against Saddam.
We do not live in the 21st century. We live in the 20 second century.
I've been thinking about the XML document format problem, and I don't think there will ever be a "pure and beautiful implementation" that will ever be perfect.
As the capabilities of the document format grow, people gain the ability to embed images, arbitrary objects, graphs, etc. Much of this can be written in a self-describing style (ie: plain text XML nodes,) but there comes a point where the developers have to simply hack XML and embed some nasty CDATA kludge.
Just looking at the embedded image problem alone -- static SVG is a great, pure-XML image format. Unfortunately, it will never have the power to describe the full set of images that you could create in a binary format.
It all goes downhill from first post
For another, it recommends a public sector-led effort to adopt an XML-based standard document format, either that of OpenOffice or a new one developed by the EU. Will they push ahead with these plans or is it just more talk?
What's wrong with good old reliable existing formats?
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
I must say that I am a bit confused. Not long time ago our "beloved" government (I even voted for them) were in favor of software patents and the use of industry standard software (read Microsoft) ... Open Source has been discussed in the Danish parlament for some years, even before the current government (2 years old in a month). The former government promised to change all state-institutions to OSS, but still nothing has happened. SSLUG (Skane Sjaelland Linux User Group, biggest LUG in Denmark) have had some discussions on this topic without much succes ... but saying this, I am looking forward to a initiative from our very quiet IT-minister. The report is from the Board of Technology, that have many good and forgotten discussions.
(yes this can be compared with sex)
Better yet than XML... bundles!!!
.rtfd files on NeXT and Mac OS X. They're basically super-RTF files. They are actually a folder ending with .rtfd that the operating system presents to the user as a single file (for mere aesthetic and encapsulation reasons). They contain an RTF file and all the non-RTF resources (images, sounds, etc) that are embedded in the document as separate files in their own formats. I believe images are saved as TIFF by default.
:)
Go research
So why not combine open XML document formats and rtfd-style bundles! A complex document is really a folder full of files, but it appears to the user as a single file. This makes it easy to move around, esp from computer to computer, and presents a nice sensible metaphor to the user. It's also difficult to screw things up by messing with the components (but it is possible to get into the bundle if you need to). Inside these complex documents is an XML file that describes the components of the document. Then there are files that contain the components, in whatever (open) format you wish. RTF or OpenOffice or whatever for text, Ogg sounds, PNG or SVG images, CSV or more complex spreadsheet/table formats, all the fonts the document needs, etc.
One of the replies to the parent addressed the issue of pixel-exact rendering. That's easy - just use the same rendering engine everywhere! All Gecko browsers render exactly the same everywhere (assuming the same fonts are available). So just use a single homogenous rendering engine everywhere. (And include fonts in the document bundle).
I sure hope some brilliant application-software engineer reads this!
(Final note: Another, more risky option would be to provide an API for rendering modules written in some suitable language, which would then be included in the bundle. You want to render, say, Maya IFF images? Include the IFF renderer in the bundle. Of course great security precautions would need to be taken, and optimally the rendering modules would have access to nothing outside the document-world, and preferably only a buffer to draw into and layout above them would be managed by the program. This has been tried before, I think. But maybe its time has come?)
Save time now so you can waste it later
The Kingdom of Denmark is actually located both in Europe and North America (we gave up on Wineland aka New Foundland). It includes Denmark, The Faroe Islands and Greenland. The country and state Denmark is the "little hat" you see on top of Germany. And happy to tell this, we are still feared in east-England because of our past (even the CIA calls us raiders! :)
(yes this can be compared with sex)
nice...if the EU uses a public open format, their economic power will force MS to have filters for the format!!
I am the Alpha and the Omega-3
OpenOffice uses zip to combine several xml files (one for content, others for meta-info and editor advice) and any image files or similar embedded content in their native formats. IIRC, KOffice uses tar.bzip2 and Abiword uses tar.gz, but I don't have those in front of me at the moment.
Sig:Why copyright isn't a fundamental human right
Using an XML foundation doesn't assure openness of the file to other "interpreters", ie, other word processors. M$ may use XML as a basis for the layout of their docs, but they still fill it to the rim with closed, propriatory slop in an attempt to make it only renderable in Word. No good.
The desire for open + XML means that a document in this format would be fully transportable between wordprocessors. This is a good thing (tm), particularly in government. Anything else effectively gives ownership of all government documents to the company that supplied the closed, propriatory format. When that company goes under (ALL companies will die out at some point) it's file format dies with it.
Government documents belong to the PEOPLE for eternity, not to private companies. They must be accessible without artificial restriction (via propriatory, closed file format) no matter what happens to some vendor supplying the parent wordprocessor.
In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
However, the report recognised that establishing a existing alternative or a new format would be an uphill battle, given that Microsoft Office cannot read OpenOffice documents or other formats.
is real simple to correct. Start using OO format (via OO/SO) in government and M$ would be compelled by competition forces to support OO format...of be locked out of government. An OSS developer could also whip up an OO document "viewer" of small size so people could easily download this "plugin" and view OO government docs on their M$ systems (for those unwilling due to bandwidth constraints or obtuseness to simply install OO/SO).
It is wrong to essentially require people to spend lots of money for a specific, propriatory wordprocessor just so they can view government documents. It is another thing entirely for them to "have to" download and install a free-of-charge office suite to do the same (though a plugin would alleviate most unreasonable heartburn). Even if they didn't do either, the contents of the document are still fully available to them in a cluttered form if they simply unzip the OO document and look at the ascii contents. Can't do that with word docs.
In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
Open Standards are all about interoperability creating a level playing field where companies can compeat to produce the best readers and writers of the standards. Consumers and Govs are free to choose which suits them best. This is one of the reasons the web took off as html was essentially an open standard, even though there were no open source browsers about in the early days.
Open Source is a different beast. I don't think the the benifits for a company to open source its products are as clear. Yes there are advantages with transpanancy for govemental use. Yes its great for hobbyiest, probably great for products aimed at developers. But the economic model is dificult, the viral licencing can cause problems.
In general I'm much more passionatle about Open Standard than Open Source.
There are four sorts of people in the world: fools, lunatics, idiots and morons. - Umberto Eco, Foucaut's pendulum.