Slashdot Mirror


Trimarco Confirms Mass. ODF Support

Andy Updegrove writes "After Peter Quinn resigned, only two brief statements -- both from spokesman for Governor and presidential hopeful Mitt Romney -- were made to the press regarding whether Quinn's OpenDocument format policy would survive. Both were vague, and both spoke only of the "rules not changing", leaving ODF supporters worried that ODF would be swapped out for Microsoft's XML Reference Schema, even before its expected approval by Ecma. But today, in a private meeting with ITD General Counsel Linda Hamel, Secretary of Administration and Finance Thomas Trimarco assured her that Peter Quinn's departure "will result in no change to the Administration's position on the ODF standard." Trimarco is the public official that will supervise whoever Quinn's replacement will be until after the deadline for the new Massachusetts' policy is to become effective."

15 of 95 comments (clear)

  1. well that's good by alienpeach · · Score: 3, Insightful

    I personally go for open standards in government. I think it makes sense that government would try and stay away from proprietary things. But when you look at the rest of the American government, that is not what you see. Take the military for example: the government hires out everything to be made proprietarily (of course there aren't really that many open options either). Then with technology, us techies critisize the government for using what many others are using and for doing what they always do.

    But that's what democracy is for, for us to tell them their idiots and show them the right way to do things.

  2. Govt Is The Place It Should Start by oirtemed · · Score: 5, Insightful
    While I know that it is unreasonable to expect companies or even individuals to actively persue open formats, I feel that it should definitely be considered in the best interest of the people for governments at all levels to make such efforts. People comparing this situation to defense contracting or the use of other closed products are making bad analogies. This is not like hiring a private contractor or purchasing a commercial product. This is more like making codes and regulations that can only be followed with the use of a certain company's product. This would be like if the electrical code said that you could only use wire from a special company or that it had to be assembled in a certain way that only said company has the information and patent for. I'm lost as to what grounds anyone could argue for closed formats anyway - any takers please fire away. There is nothing preventing MS from implementing these formats in Office - this seems to be a case where there is only one logically right option and those that try to push the closed format option look ridiculously silly.

    Ummm..no..open formats are bad...because...ummm...just trust us...Office doesn't use them...and office is so popular so it must be ok!
    I mean, seriously, what is the logic?

    1. Re:Govt Is The Place It Should Start by mattwarden · · Score: 4, Interesting

      If governments start to use ODF, MS Office will certainly support the format (either natively or via importing and exporting). It will have to or it will lose revenue. However, I'm sure MS will do what it almost always does with open formats, which is fsck it up just enough to make its output incompatible just enough with other readers to keep those readers from being valid replacements for Word.

      Probably the easiest way to do this is to allow importing of an ODF document into native Word DOC format, and then exporting to ODF format. In this way, people will not be restricted to using only features which ODF supports while editing the file in Word. Then, when exporting, they will get a warning message about how features will be lost if they convert this file to ODF. All of a sudden their clip art is grayscale, their title is no longer in 3d and written on a curvature, meta information like comments and 'track changes' is lost or corrupt, etc.

      Just enough of a nuisance to keep the status quo and get the user to send their version of the document in Word DOC format.

    2. Re:Govt Is The Place It Should Start by JamesTRexx · · Score: 3, Insightful

      Most of the people who oppose changing from Word to OO.org, also complain when Word is upgraded to a new version. When we did a company wide upgrade, at first everyone was asking when they'd get the new version, after that they didn't know where to find certain features and complained that it wasn't the same like the old version.

      --
      home
    3. Re:Govt Is The Place It Should Start by judabuddhist · · Score: 4, Insightful

      When I heard RMS speak earlier this year he mentioned that a lawmaker's support for open standards and non-proprietary stuff in government makes a good litmus test of their integrity. It's an issue that's pretty straightfoward, since no reasonable government should be locked into proprietary formats and whatnot, but your average Joe couldn't care less, and isn't going to be basing any votes on the subject. There's so much money being thrown around by software companies, and so little political incentive to resist, that it's a wonder any polititian would be on the side of free software. This is why the whole Massachusetts thing is so important, since it's very much an exception to the rule and could raise public aweness even if it's not entirely successful.

    4. Re:Govt Is The Place It Should Start by Bert64 · · Score: 3, Interesting

      Well upgrading to the latest version of word will cost a lot more than upgrading to openoffice..
      There are about the same level of differences between old and new versions of word, as there are between word and openoffice so any training costs would be very similar..
      On the other hand, they don't need to pay for openoffice and can easily install it on as many machines as they have..
      Also, the latest version of word no longer runs on older versions of windows (NT4, 9x etc) whereas openoffice does, so upgrading word may also require upgrading windows, at more cost.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    5. Re:Govt Is The Place It Should Start by Alex+P+Keaton+in+da · · Score: 3, Insightful

      I deal with Word files from lots of different people; and hardly any of them know how to use the "tools" it offers; I'd say less than 5% ever use anything that's not on the formatting bar (which is virtually identical to the formatting bar on dozens of other word processors). And government workers aren't given a choice of which software to use anyway. Of course some do have specialised apps, these can be left alone and eventually converted (as they would have to be the next MS upgrade anyway).
      As a technical writer, I would agree wholeheartedly. Sometimes (often) when we design a document, clients request it in word, because if we use a different program (InDesign, Captivate, whatever) they don't have the software to make updates. I would much prefer InDesign for graphic heavy docs (Word doesn't handle vector graphics... I still can't believe that) People don't understand that word is not a publishing program!
      I use a ton of Field Codes and Styles in Word. I have, by request of a client, created a 200 page parts catalog in word that was one giant table...
      The worst experiences I have had were with Word docs designed with a ton of Field codes and styles, as when a third party updates them they ALWAYS get screwed up. That is why I prefer a program like Framemaker where I can set up a template, and have one person control the template and others only able to make content changes.
      The main problem with word (in my opinion) is that people use it for things it isn't, and wasn't ever intended for...

      --
      And All I Ask is a Tall Ship And a Star to Steer Her By
    6. Re:Govt Is The Place It Should Start by brw12 · · Score: 4, Interesting

      New York City agreed to a proprietary, closed design for their bus/subway card, "MetroCard." Only the company that designed the card knows the information storage format (although hackers have deciphered some of the unencrypted information, like some users' social security numbers!)

      The result? As the Village Voice revealed in several investigative pieces in 1997/8, The state (which administers the city's public transportation) is forced to pay an obscene $125,000 for each full-sized MetroCard vending machine they buy. They've lost millions of dollars (money which, for example, might have prevented the recent strike) just because they misunderstood the difference between "proprietary" and "secure."

  3. Re:No change on ODF by TubeSteak · · Score: 3, Interesting

    Not that this really relates to your comment, but OpenOffice.org doesn't have a grammar checker.

    I wrote a paper in OpenOffice once... then I took it to a computer with MS Office to run the grammar check. I think the lack has a serious effect on OO's functionality and as a consequence, its usefulness.

    AbiWord has one though.

    --
    [Fuck Beta]
    o0t!
  4. Re:No change on ODF by advocate_one · · Score: 3, Insightful
    Not that this really relates to your comment, but OpenOffice.org doesn't have a grammar checker.

    I wrote a paper in OpenOffice once... then I took it to a computer with MS Office to run the grammar check. I think the lack has a serious effect on OO's functionality and as a consequence, its usefulness.

    does a word processor really need a Grammar Checker? A grammar checker can't substitute for a proper grounding in your language. If you need a grammar checker, then perhaps you, yourself, are lacking somewhat.

    --
    Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
  5. Re:No change on ODF by mattwarden · · Score: 3, Insightful

    A grammar checker can't substitute for a proper grounding in your language. If you need a grammar checker, then perhaps you, yourself, are lacking somewhat.

    If you had RTFA, you would have realized that the topic of discussion is use of ODF by government employees.

    Seriously, though, there are certain things that aren't really grammar errors in the traditional sense. True grammar errors are difficult to make on accident, when the author truly does comprehend the language but simply slips up. However, other "grammar errors", like the misuse of 'there', 'their', and 'they're' are simple verbal errors that can happen just like a spelling error or typo.

    Others more in the gray area but just as easy to make are verb number agreement in comlpex sentences like one I wrote just a few minutes ago: "Meta information like comments and 'track changes' is lost or corrupt." I admit that I had to read it over again to make sure I had verb number agreeing with my subject, because it sounds almost like it should be plural rather than singular.

    Writing a 50-page report, these sort of things are easy to miss. If I have to pay attention to these minor grammar details, that will slow me down (however little) and annoy me. If I can use Office, already installed on my computer, with its grammar checker and not have to worry about these things, I might.

  6. Open Document, open meeting... by Max+Nugget · · Score: 3, Funny

    But today, in a private meeting with ITD General Counsel Linda Hamel, Secretary of Administration and Finance Thomas Trimarco assured her that Peter Quinn's departure "will result in no change to the Administration's position on the ODF standard."

    Well I'm sure Mr. Trimarco will be pleased to know that his private comments to Ms. Hamel remained private, leaving bloggers like Andy Updegrove with no choice but to resort to speculation as to the contents of said meeting, in absence of a direct quote from those inolved.

  7. What about 'em? by Anonymous Coward · · Score: 4, Insightful

    Macros are scripts: they manipulate data in ways the data processing application wasn't originally designed to. Macros run within the context of said program, because you, as consumer-user, are not permitted to know either the structure of the data in memory or self-similarly, the layout of the data in the output and input files. Macros are a direct result of you not being allowed to know the secret sauce of the memory structures or file format.

    Not so in the case of an Open Format. Both the input and output formats are fully known and so: one can write a program outside the context of the original data processing application in whatever language one chooses. There is zero need for macros when anyone with sufficient skills can write processes to evaluate input data and transform it to useful output data.

  8. Oh, don't be naive by btarval · · Score: 4, Insightful
    I'm sorry, but there's nothing good to see here. If Microsoft can get Peter Quinn to resign, what makes you think for a moment that "what makes sense" is going to happen? Do you really believe that what some State Official is saying right now is going to be what really happens?

    Mr. Quinn resigned because he had "become a lightning rod", and that was getting in the way of his work. Anyone who fills his shoes is going to be a similar lightning rod, and that is one thing successful bureaucrats don't like being. Far more likely is that the next person will attempt compromise in order to smooth things over. And that compromise will end up being far more (if not completely) Microsoft centric, unless people stand up and make their voices heard.

    This battle is far, far from over, despite what State Officials are now saying. It kind of reminds me of the claims made by Saddams' Minister of Information in the closing days of the Iraq invasion. Personally, I'll believe what I see when this battle has ended.

    And IMHO, the odds went way up that closed formats are going to end up ruling here. What was indeed needed was a lightning rod. A pity that Mr. Quinn found the presure to be too onerous.

    --
    The best way to predict the future is to create it. - Peter Drucker.
  9. They can't step back... by Pecisk · · Score: 3, Insightful

    Because there is too much information in the air, there is already said too much both from Microsoft ("well, we _could_ support OpenDocument, but...ohhhh, that's a nice clippy, isn't it?") and their lobbies in state institutions.

    If they would step back, that would be disasterous for Microsoft's future efforts to lobby to use Microsoft Office and their "open" format. See, if someone sees that Microsoft simply forces influence, politicians will get resitant. Not only because they afraid of their outlook in voter's eyes, but also they understand the whole issue - Microsoft is desperate and getting very personal when someone wants to take away their monopoly at least for abit. So they will start to see the whole issue then. And that is what Microsoft wants to avoid, I guess.

    So...yes. OpenDocument will be there and Microsoft will make export feature for goverments. And I don't think that they will embrace it or make specially with bugs or errors. They will try to fight it different way.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!