• Sign In
 
  • MSDN Blogs
  • Microsoft Blog Images
  • More ...
Search
  • Advanced search options...
Tags
  • .NET
  • Altova
  • blogging
  • code samples
  • Codeplex
  • Custom XML
  • DII
  • DIS29500
  • ECMA-376
  • IBM
  • Java
  • Monarch
  • ODF
  • Office 2007
  • OpenXMLDeveloper.org
  • PHP
  • Redmond
  • SharePoint
  • System.IO.Packaging
  • TechEd
  • UOF
  • VSTO
  • Windows
  • WordprocessingML
  • workshops
Archives
Archives
  • January 2012 (1)
  • October 2011 (1)
  • July 2011 (2)
  • April 2011 (1)
  • March 2011 (3)
  • December 2010 (1)
  • August 2010 (1)
  • June 2010 (1)
  • May 2010 (1)
  • April 2010 (3)
  • March 2010 (1)
  • November 2009 (4)
  • October 2009 (1)
  • September 2009 (2)
  • July 2009 (2)
  • June 2009 (4)
  • May 2009 (5)
  • April 2009 (4)
  • March 2009 (4)
  • February 2009 (2)
  • January 2009 (4)
  • December 2008 (4)
  • November 2008 (3)
  • October 2008 (4)
  • September 2008 (3)
  • August 2008 (2)
  • July 2008 (5)
  • June 2008 (7)
  • May 2008 (5)
  • April 2008 (8)
  • March 2008 (14)
  • February 2008 (15)
  • January 2008 (13)
  • December 2007 (12)
  • November 2007 (5)
  • October 2007 (9)
  • September 2007 (6)
  • August 2007 (10)
  • July 2007 (9)
  • June 2007 (8)
  • May 2007 (12)
  • April 2007 (14)
  • March 2007 (12)
  • February 2007 (10)
  • January 2007 (17)
  • December 2006 (14)
  • November 2006 (10)
  • October 2006 (11)
  • September 2006 (12)
  • August 2006 (12)
  • July 2006 (12)
  • June 2006 (23)
  • May 2006 (14)
Common Tasks
  • Blog Home
  • Email Blog Author
  • About
  • RSS for comments
  • RSS for posts

document formats legislation in the US

Doug Mahugh - Office Interoperability
MSDN Blogs > Doug Mahugh > document formats legislation in the US

document formats legislation in the US

Rate This
Doug Mahugh
16 Oct 2007 4:06 PM
  • Comments 2

Shane Peterson, who has been following document formats legislation in the US for some time, has a new article on Public CIO entitled "What Domino Effect?" that takes a close look at how the situation has evolved in Massachussetts and Texas.

The article includes some quotes from my friend and colleague Stuart McKee on the value of choice:

"The reality is that many file formats exist to satisfy the incredible diversity of needs in software applications," he said, noting that some document formats present a fixed representation of information so that it can't ever be changed.

"Other formats are designed to maximize the ability to edit documents, and formats for spreadsheets or designing page layouts to suit the specific needs of software applications and systems.

"Since each of these features can be necessary given the goals of a specific project, locking in a single file format standard simply makes no sense," McKee said. "Choice among overlapping and even competing file format standards best enables governments to meet their needs, today and into the future, and ensures the efficient use of government resources and taxpayer monies."

Stuart discusses some related concepts in his column last week on "Translating Interoperability." As a former state CIO (Washington), his pragmatic perspective is very much in line with the thinking behind the Massachussetts ETRM (Enterprise Technology Reference Model), which stipulates a list of open-standard document formats for various types of applications including text, HTML, PDF, ODF, and Open XML.

  • 2 Comments
ETRM
Comments
  • MSDN Blog Postings » document formats legislation in the US
    16 Oct 2007 6:28 PM

    PingBack from http://msdnrss.thecoderblogs.com/2007/10/16/document-formats-legislation-in-the-us/

  • orcmid
    17 Oct 2007 3:41 PM

    The full article is rather interesting.  In one spot, it seems that the Massachusetts migration is competely off their timeline, but other evidence suggests that there is take-up of OpenOffice.org, so I think the comment about the Sun translator is simply garbled.

    It is also encouraging that no one seems to be in a hurry to dictate ODF considering the small matter of reality and the prospect for dramatic unintended consequences.

Page 1 of 1 (2 items)
  • © 2012 Microsoft Corporation.
  • Terms of Use
  • Trademarks
  • Privacy Statement
  • Report Abuse
  • 5.6.402.223