Government standards vehicle driven by "clueless fuckwittery"

| 2 Comments
| More
A senior member of a leading British tech standards body has launched an excoriating attack on Cabinet Office efforts to implement the central plank of its ICT Strategy.

The outburst has opened a crack into the secretive world of formal tech standards, suggesting it may be convulsed in a fit of pique not seen since Microsoft got its derided OOXML document format passed by standards bodies around the world in 2008.

Alex Brown, British Standards Institute committee member infamous for overseeing OOXML's approval, said in his personal blog how he had become exasperated with government efforts to bring ICT standards in line with its policy of easy interoperability of public computer systems.

Alex Brown.pngCabinet Office had given formal standards wonks a "kick in the teeth" with its attempt to create an approved set of government ICT standards, said Brown.

A public survey of favoured ICT standards opened by Cabinet Office in February was technically "ignorant", said the expert.

"Faced with such clueless fuckwittery it's tempting simply to ask: what's the point?" said Brown, who sits on IST/41, the BSI standards committee responsible for document formats.

Francis Cave, IST/41 chairman, refused to comment on Brown's outburst or the Cabinet Office consultation.

BSI standards bodies are so secret that members (who have typically invested a life's career in such work) face the threat of excommunication if they talk about proceedings.

The whole episode has nevertheless shown how the British Standards Institute has been thrust into a corner by the current trend for transparency and the Cabinet Office's apparent preference for crowd-sourcing standards from a church of people that may include the great unwashed.

The situation is said to have "gone toxic", with Brown's blue language drawing approval from at least some of his colleagues.

Garbage in, garbage out

The most offensive element of the Cabinet Office survey has been, it is said, its technical inferiority. It was stuffed with mistakes that - it is feared - may lead to useless survey results on which Cabinet Office will subsequently base its standards policy.

This has become a serious matter since the Cabinet Office ICT Strategy said it would "impose" standards across government.

This was a popular policy in a polity paralysed by proprietary technologies: the UK is setting an example, and Cabinet Office decisions on standards will have ramifications perhaps big enough even to change the landscape of the IT industry. Yet the Cabinet Office has raised questions about its technical authority with its first move.

Cabinet Office Standards Survey.pngMany of its mistakes are in the field of document standards in which Brown's IST/41 committee operates.

They include the repeated presentation of proprietary Microsoft document formats as options for formal government standards, despite government strategy being shaped by the icy grip proprietary formats have on the public purse.

The ICT strategy had already raised doubts about the Cabinet Office's commitment to open standards.

It had in February published a Public Procurement Policy Note declaring the public sector should use open standards.

Gerry Gavigan, who represents the Open Source Consortium on IST/41, pointed out that only a month later the ICT Strategy had downgraded the requirement to "common standards".

Conservative pragmatism has infected the coalition ICT Strategy with the belief that it would be impractical to impose open standards where industry already makes common use of de facto formats. The ICT Strategy nevertheless promised to make mandation of an open document format the first of its formal declarations.

ISO Protest Banner.pngReformation

This open / common dichotomy and the BSI's apparent ancillary part in it, point to the the bigger story behind Brown's blog.

That is the existential threat the Cabinet Office reforms may pose for the British Standards Institute itself, and the secretive, formal standard setting process that runs right up to the International Standards Organisation in Geneva.

"What's the point" of putting your heart and soul into a formal standards process when it can be undermined by an ill-thought-out public consultation, said Brown's blog.

Gavigan went further in another recent article, claiming the Cabinet Office's open consultation over standards "undermines the whole standards process which the government funds BSI to deliver".

The failure and, it was alleged at the time, susceptibility of that process to corruption may have been demonstrated by the OOXML affair.

The alleged corruption was never confirmed, to this correspondent's knowledge. But it has for more substantial reasons left the process with a stigmata that goes right to the heart of government policy.

The culture of transparency that has swept along in the wake of Sir Tim Berners Lee's open data initiative has in addition made the BSI look anachronistic.

The Cabinet Office's failure to involve the standards body in its own consultation and policy formation now make it look like the BSI's days are numbered. But the Cabinet Office's own lack of transparency can make anyone look that way.

The Cabinet Office was, as usual, unavailable for comment.

Both bodies are ripe for an equal dose of transparency and openness.

2 Comments

  • QUOTE

    This has become a serious matter since the Cabinet Office ICT Strategy said it would "impose" standards across government.

    UNQUOTE

    Perhaps the BSI shouldn't be too worried. The Cabinet Office can say what they like but they're in no position to impose anything on anyone.

    They tried to impose transformational government on Whitehall from end-2005 onwards. Whitehall's response was to ignore them.

    There was no public mention of clueless fuckwittery, of course. Instead, something much more chilling and effective -- ignoring the Cabinet Office made them look like a lot of funny old bagmen in the street, talking to themselves animatedly, but quite without influence.

  • For evidence of [alleged] ISO corruption, please see the Techrights indexes

    .

    http://techrights.org/ooxml-abuse-index/

    http://techrights.org/2008/05/24/ooxml-incidents-a-c/
    http://techrights.org/2008/05/25/ooxml-incidents-d-to-g/
    http://techrights.org/2008/05/26/ooxml-incidents-k-to-n/
    http://techrights.org/2008/05/26/ooxml-incidents-p-to-s/
    http://techrights.org/2008/05/26/ooxml-incidents-t-to-v/

    Thank you for noticing.

    Actual standards experts have shown that the OOXML specification was hoplessly inadequate. Despite being more than 6,000 pages it was both incomplete and self contradictory, often referencing the undocumented behavior of subversions of Microsoft's previous software. It only passed ISO because Microsoft corrupted the process and stuffed the vote as documented above.

    [Editor's note: there has been no prosecution against Microsoft for corrupting the OOXML standards process, as far as we know. Neither has the OOXML standard been discredited officially. The TechRights index does indeed look comprehensive at a glance, and quite astonishing. However, one item from this body of purported evidence we followed at random (the Swiss Cheese example) led ultimately, and appeared to rely for evidence in its entirety, on an anonymous posting on the NoOoxml campaign blog. The author of this here comment also operated anonymously.]

    Because people like Steve Pepper of Noway are still trying to correct national votes, it is too early to condemn ISO.

    Only a hypocrite can at once decry a defacto standard and recommend a phoney replacement which is technically identical in many parts. OOXML is impossible for anyone but Microsoft to implement but not even they have. It is amusing to watch someone with such low standards for documents resort to foul language but he does not have much else to stand on. I suppose that Mr. Brown is upset that anything but OOXML is being considered.

    Government and industry bodies should adopt the simpler but more complete ISO standard, ODF. Those who do can chose between a number of free and excellent implementations, at least one of which does a better job of importing legacy documents than Microsoft's own software.

  • Leave a comment

    Subscribe to blog feed

    Archives

    -- Advertisement --