Skip to main content

What's it Open *for*?

I was scrolling through an ElReg article linked from Lxer on ODF vs XMLRS (Microsoft’s answer to ODF), when I stumbled across a link to another blog (apparently since unlinked) which asked an important question:

What job does each do?

That could sound odd, since each purports to be an Open document standard, but it’s a very real question.

ODF was indeed written into OpenOffice as a literally Open document format (and their default), whereas XMLRS’ primary purpose is to support o single office suite by making it look more accessible.

The consequences will become more obvious with time, but we’re being asked to decide between them now (or soon). The ’blog mentions that they’re aimed at the same job — sorta — and makes the point that our decision should be based on what each format was designed for.

If we want to live in a MS-controlled (MS-owned) world, then XMLRC is appropriate, but otherwise ODF is the clear winner.

It’s a question which is too-seldom asked: “What is it for?’

My choice is obvious, how is yours?

Comments

Leon RJ Brooks said…
Uh, the XMLRC spec is about 2.5 times as large as ODF. Some of that will be due to incorporating ancient formatting barnacles (ie, more exceptions to consider), but most of it is not.

Popular posts from this blog

new life for an old (FTX) PSU, improved life for one human

the LEDs on this 5m strip happen to emit light centred on a red that does unexpectedly helpful things to (and surprisingly deeply within) a human routinely exposed to it. it has been soldered to a Molex connector, plugged into a TFX power supply from a (retired: the MoBo is cactus) Small Form Factor PC, the assorted PSU connectors (and loose end from the strip) have been taped over. the LED strip cost $10.24 including postage, the rest cost $0, the PSU is running at 12½% of capacity, consumes less power than a laptop plug-pack despite running a fan. trial runs begin today.

every-application-is-part-of-a-toolkit at work

I have a LibreOffice Impress slideshow that I wish to turn into a narrated video. 1. export the slideshow as PNG images (if that is partially broken — as at now — at higher resolutions, Export Directly as PDF then use ‘pdftoppm’ (from the poppler-utils package) to do the same). 2. write a small C program (63 lines including comments) to display those images one at a time, writing a config file entry for Imagination (default transition: ‘cross fade’) based on when the image-viewer application (‘display,’ from the GraphicsMagick suite) is closed on each one; run that, read each image aloud, then close each image in turn. 3. run ‘Imagination’ over the config file to produce a silent MP4 video with the correct timings. 4. run ‘Audacity’ to record speech while using ‘SMPlayer’ to display the silent video, then export that recording as a WAV file. 4a. optionally, use ‘TiMIDIty’ to convert a non-copyright-encumbered MIDI tune to WAV, then import that and blend it with the speech (as a quiet b...

boundaries

pushing the actual boundaries of the physical (not extremes, the boundaries themselves) can often remove barriers not otherwise perceived. one can then often resolve an issue itself, rather than merely stonewalling at the physical consequences of the issue.