Slashdot Mirror


Unix Group Takes UK Standards Body To Court Over OOXML

superglaze writes "Halfway through the two-month window of opportunity during which OOXML's ISO standardization can be derailed by a formal objection from a national standards body, the UK Unix Users Group is trying to force the British Standards Institution to do just that. According to the Unix Users Group, the BSI used a flawed decision-making process when they chose to approve OOXML in the ISO vote. 'The UKUUG is also folding in many other complaints about Office Open XML (OOXML), such as unresolved patent issues and a lack of completion in the specification's documentation, and is calling for the High Court of Justice to force a judicial review of the BSI's decision.' This is not the first time a country's ISO vote has been challenged."

4 of 229 comments (clear)

  1. that reminds me of my first time... by Anonymous Coward · · Score: -1, Troll

    A few years ago, while browsing around the library downtown, I had to take a piss. As I entered the john, a big beautiful all-American football hero type, about twenty five, came out of one of the booths. I stood at the urinal looking at him out of the corner of my eye as he washed his hands. He didn't once look at me. He was "straight" and married -- and in any case I was sure I wouldn't have a chance with him.

    As soon as he left, I darted into the booth he'd vacated, hoping there might be a lingering smell of shit and even a seat still warm from his sturdy young ass. I found not only the smell but the shit itself. He'd forgotten to flush. And what a treasure he had left behind. Three or four beautiful specimens floated in the bowl. It apparently had been a fairly dry, constipated shit, for all were fat, stiff, and ruggedly textured. The real prize was a great feast of turd -- a nine inch gastrointestinal triumph as thick as a man's wrist. I knelt before the bowl, inhaling the rich brown fragrance and wondered if I should obey the impulse building up inside me. I'd always been a heavy rimmer and had lapped up more than one little clump of shit, but that had been just an inevitable part of eating ass and not an end in itself.

    Of course I'd had jerkoff fantasies of devouring great loads of it (what rimmer hasn't?), but I had never done it. Now, here I was, confronted with the most beautiful five-pound turd I'd ever feasted my eyes on, a sausage fit to star in any fantasy and one I knew to have been hatched from the asshole of the world's handsomest young stud.

    Why not? I plucked it from the bowl, holding it with both hands to keep it from breaking.

    I lifted it to my nose. It smelled like rich, ripe limburger (horrid, but thrilling), yet had the consistency of cheddar. What is cheese anyway but milk turning to shit without the benefit of a digestive tract? I gave it a lick and found that it tasted better then it smelled. I've found since then that shit nearly almost does. I hesitated no longer. I shoved the fucking thing as far into my mouth as I could get it and sucked on it like a big brown cock, beating my meat like a madman. I wanted to completely engulf it and bit off a large chunk, flooding my mouth with the intense, bittersweet flavor. To my delight I found that while the water in the bowl had chilled the outside of the turd, it was still warm inside. As I chewed I discovered that it was filled with hard little bits of something I soon identified as peanuts. He hadn't chewed them carefully and they'd passed through his body virtually unchanged. I ate it greedily, sending lump after peanutty lump sliding scratchily down my throat. My only regret was the donor of this feast wasn't there to wash it down with his piss. I soon reached a terrific climax. I caught my cum in the cupped palm of my hand and drank it down. Believe me, there is no more delightful combination of flavors than the hot sweetness of cum with the rich bitterness of shit. Afterwards I was sorry that I hadn't made it last longer. But then I realized that I still had a lot of fun in store for me. There was still a clutch of virile turds left in the bowl. I tenderly fished them out, rolled them into my hankercheif, and stashed them in my briefcase.

    In the week to come I found all kinds of ways to eat the shit without bolting it right down. Once eaten it's gone forever unless you want to filch it third hand out of your own asshole -- not an unreasonable recourse in moments of desperation or simple boredom.

    I stored the turds in the refrigerator when I was not using them but within a week they were all gone.

    The last one I held in my mouth without chewing, letting it slowly dissolve. I had liquid shit trickling down my throat for nearly four hours. I must have had six orgasms in the process. I often think of that lovely young guy dropping solid gold out of his sweet, pink asshole every day, never knowing what joy it could, and at least once did,bring to a grateful shiteater.

  2. Re:This molehill is gigantic! by BadAnalogyGuy · · Score: 0, Troll

    I thought the advantage of standards was to reduce divergence in systems. The more implementations of particular items, such as screws, conform to a standard, such as phillips head, the better it is for the people who use screws.

    You'd be incorrect. The advantage of a standard is that it provides a set of guidelines that define an implementation. If an implementation supports a certain standard (or standards), then it can be reasonably expected to work as specified.

    There is no reason to believe that only one specification may be supported in a product or (more generally) a market ecosystem. SGML still exists despite XML's rapid emergence. Even your beloved screw head has many different standards which are mixed and matched in products as necessary.

    The only valid point against OOXML is that it contains unclear and/or unimplementable aspects, thus denying others from the ability to create supporting implementations. However, if this is the case, and MS is unwilling to create OOXML implementations for non-MS/Apple platforms, how successful do you really expect the standard to be?

    In the end, government documents are write-only. The only thing that matters is the final output, so there's really no point in fighting over file formats since the documents will be archived in a completely non-RW format anyway (like PDF).

    The UKUUG taking legal action over the corruption in the vote doesn't make them look like whiners. It makes them look like learned elders who are about to take a stick to a bunch of delinquents.

    No, it looks like they are whining over a decision that didn't go their way.

    Protest against the standardization of OOXML doesn't appear technologically backwards when conducted in an appropriate forum and it portrays OOXML as the backwards step it truly is.

    No, it just says to onlookers that Microsoft's standard is so advanced that even the best and brightest of the computing world can't implement the difficult parts of it. Of course this is due to bad inclusions, but it doesn't make you come off any better by crying about it.

    This is about a format to be implemented by anyone who can read a specification

    Really? And you were expecting someone besides MS to implement OOXML? On top of that, you were expecting someone to buy an implementation of OOXML that was not developed by MS? Look at all these windmills, Don Quixote!

    A reasonable open standard already exists.

    Of course you mean PostScript, right?
  3. Re:Parent post is a troll. Mod it down by Anonymous Coward · · Score: -1, Troll

    I'm tired of people like you. Look buddy, we're crying not because "Microsoft bought a standard". We're crying because a half-baked specification got recognized as a standard

    An accurate statement would be that you are crying because someone told you to cry, since you clearly haven't investigated this yourself.

  4. Of course you haven't seen them, they're all 0/-1. by SEMW · · Score: 0, Troll

    Except, as has been pointed out here in the past by people who actually went through and read it, the OOXML "documented" standard is full of references to microsoft office internals, which _aren't_ documented in it. Except, as pointed out by people in comments on this article, those items have been flagged and fixed as per the comments raised on the initial draft. Would that be TFA, of this slashdot discussion? I can't find any references to flagging or fixing in TFA, and a vague reference to an ongoing slashdot debate is hardly authoritative. A quote or a link might be helpful.
    Personally, I haven't heard about any comments being addressed in the MSOOXML spec. The reason you haven't seen any of the relevent references in any Slashdot discussion is that they're invariably modded down to 0 or -1, because Slashdot modders don't like it when reality disagrees with their anti-Microsoft POV. E.g., here's a link to someone quoting from the documentation for autoSpaceLikeWord95. Since, as any Red-blodded True Slashdotter will tell you, autoSpaceLikeWord95 is undocumented, quoting from the documentation is liable to disturb Slashdotters' world-view; it's easier to just stick your fingers in your ears, moderate down, and pretend it didn't happen.
    --
    What's purple and commutes? An Abelian grape.