California Joins Open Document Bandwagon
Andy Updegrove writes "A legislator in California has decided that it's time for California to get on the open formats bandwagon. If all of the bills filed in the last few weeks pass, California, Texas, and Minnesota will all require, in near-identical language, that 'all documents, including, but not limited to, text, spreadsheets, and presentations, produced by any state agency shall be created, exchanged, and preserved in an open extensible markup language-based, XML-based file format.' What type of formats will qualify? Again, the language is very uniform (the following is from the California statute): 'When deciding how to implement this section, the department in its evaluation of open, XML-based file formats shall consider all of the following features: (1) Interoperable among diverse internal and external platforms and applications; (2) Fully published and available royalty-free; (3) Implemented by multiple vendors; (4) Controlled by an open industry organization with a well-defined inclusive process for evolution of the standard.'"
Minnesota also is considering open documents.
Just called my CA Assembly rep to ask them to support the bill. Look yours up here.
It may not be perfect, but is a move in the right direction.
SB 446
So far, each bill has been filed and referred to the appropriate committee. However, the legislative session just started in January and things don't usually start happening until after the filing deadline on 2007-03-09.
I believe the IFC (Industry Foundation Classes) format, intended for cross-app CAD communication, is XML-based, and major CAD developers are supporting or working on support for it.
Death to DWG/DXF.
Ooh, a sarcasm detector. Oh, that's a real useful invention.
Which is why the bill doesn't just specify XML. FTFA,
...the department in its evaluation of open, XML-based file formats shall consider all of the following features:From a greybeard
... That should be easy (because of XML). Help me."?
XML Problem Checklist:
- Ensure the library functions are flexible enough for the application, and do not consume too many resources. This can be an issue for smaller systems, and may be an issue for larger ones as well.
- Ensure that the XML implementation is usable on a security basis. Should not have buffer overruns - parsing problems etc.
- Ensure that the XML works with ANOTHER XML implementation. Adds testing (its not just "someone elses problem").
- Application data structures are influenced by XML (eg. XML does not represent bitfields/bitsets directly). Mappings must be reasonable.
- XML should be 'vetted so that the format doesn't look like it was laid out by 'noobs. Stuff like the Microsoft specification for XML WORD shouldn't be generated.
- Because the only reason that XML formats are being used is for interoperability, a separate set of interoperability documents must be maintained. At some point, someone will ask the question "You use XML, I want to stick the data into
Just another "Cubible(sic) Joe" 2 17 3061
All video formats are now illegal. (or is there now an XML video abomination?)
All audio formats are now illegal.
Probably all image formats are now illegal.
Whee.... this'll be entertaining.