Skip to main content

Home/ OpenDocument/ Group items matching "Google" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

OpenDocuemnt Foundation dumps ODF, choses W3C CDF instead- Google News Collection - 0 views

  • ODF group abandons file format in favor of W3C alternativeComputerworld, MA - Oct 30, 2007October 30, 2007 (IDG News Service) -- A group that was set up to promote the Open Document Format for Office Applications (ODF) is abandoning its support ...
Paul Merrell

OpenDocument format gathers steam - CNET News.com - 0 views

  • IBM and Sun Microsystems convened a meeting in Armonk, N.Y., on Friday to discuss how to boost adoption of the standardized document format for office applications. The ODF Summit brought together representatives from a handful of industry groups and from at least 13 technology companies, including Oracle, Google and Novell.
  • The participants in last week's ODF Summit included Red Hat, Adobe, Computer Associates, Corel, Nokia, Intel and Linux e-mail company Scalix, in addition to Oracle, Novell and Google. The goal of the meeting, convened by Bob Sutor, IBM's vice president of standards and open source, and Simon Phipps, Sun's chief open-source officer, was to drive support for the standards "on a global level," Sutor said.
  • On the promotional side, IBM will draft a proposal to create an "OpenDocument Foundation" which would serve to market OpenDocument-based products.
  •  
    Martin LaMonica report of the 2005 ODF Summit Conference. Note IBM's plan to draft a proposal for the "OpenDocument Foundation."
Paul Merrell

Gray Matter : Compatibility Pack for Open XML passes 100 million downloads - 0 views

  •  
    Also includes stats in table form indicating that according to Google Search OOXML documents now outnumber ODF documents on the Web, for word processor documents, spreadsheet documents, and presentation documents.
Paul Merrell

What is Boxcryptor | Easy to use encryption for cloud storage | boxcryptor.com - 1 views

  • Boxcryptor is an easy-to-use encryption software optimized for the cloud. It allows the secure use of cloud storage services without sacrificing comfort. Boxcryptor supports all major cloud storage providers (such as Dropbox, Google Drive, Microsoft OneDrive, SugarSync) and supports all the clouds that use the WebDAV standard (such as Cubby, Strato HiDrive, and ownCloud). With Boxcryptor your files go protected to your cloud provider and you can enjoy peace of mind knowing that your information cannot fall into the wrong hands. Here is how it works: Boxcryptor creates a virtual drive on your computer that allows you to encrypt your files locally before uploading them to your cloud or clouds of choice. It encrypts individual files - and does not create containers. Any file dropped into an encrypted folder within the Boxcryptor drive will get automatically encrypted before it is synced to the cloud. To protect your files, Boxcryptor uses the AES-256 and RSA encryption algorithms.
  •  
    Free for personal use. I haven't tried this yet, but the need for it has been near the top of my head since I first tried Dropbox and then realized how insecure it was. I tried a lot of sync services, but am now using Wuala, which features end-to-end encryption baked into the client software. But I also use MEGAsync for remote backup so I'[ll probably be trying this out with that service. I hope there's a way to sync the two programs.
Gary Edwards

Can a file be ODF and Open XML at the same time? (and HTML? and a Java servlet? and a PDF archive?) - O'Reilly XML Blog - 0 views

  • The recent bomb in the ODF world from Gary Edward’s claims that Sun successfully blocked the addition of features to ODF that would be needed for full interchange with Office are explosive not only because they demonstrate how ODF was (properly, in my view) developed to cope with the particular features of the participants, not really as a universal format, but also because the prop up Microsoft’s position that Open XML is required because it exposes particular features that ISO ODF is not capable of exposing. Both because ODF is still in progress and because sometimes the features are simply incompatible in the details.
  • Actually, ODF is about to get a new manifest along with the new metadata stuff. Because we base that on RDF, the manifest will also be RDF-based. It gives us the extensibility we want to provide (extension developers, for example, can add extra metadata they may need), without having to worry about breaking compatibility. The primary addition we've made is a mechanism to bind a stable URI to in-document content node ids and files. This is conceptually not all that different than what I see in OPC; it's just that the unique IDs are in fact URIs. Among other things, in the RDF context that allows further statements to be bound to those URIs. Bruce D'Arcus | July 29, 2007 01:02 PM
  •  
    What Bruce doesn't explain in this highlighted clip is that Sun decided to limit the "extra metadata" developer might need to just a handful of elements Sun and IBM needed to use in OpenOffice. The original OpenDocument Foundation metadata proposal was to open up the use of metadata to the extent that metadata could be used for all aspects of presentation (formatting AND layout!).
  •  
    This vendor specific - application specific limiting ended the last hope we had for ODF interoperability and backwards compatibility with the billions of "in-process" MSOffice documents known to be populating business processes the world over. In fact, the problem ODF adoption faces is primarily that of MSOffice bound business processes, reflected in these billions of workgroup-workflow documents.
  •  
    Proposal to have a standard packaging for combining application specific XML formats, Open HTML, and PDF. Great comments. This July 2007 article links to a January 2009 article: http://broadcast.oreilly.com/2009/01/packaging-formats-of-famous-ap.html
Gary Edwards

Is Sun Friend or Foe? - 0 views

  •  
    Published May 22, 2007, this comment was written in the aftermath of List Enhancement Proposal donnybrook at the ODF OASIS TC.

    It was at the height of our List Enhancement battle with Sun that OASIS stepped in their threat to boot the OpenDocument Foundation.  OASIS carried out that threat in May.  The lesson we learned is clear and unequivocal.  Opposition to Sun, in either the marketplace (da Vinci) or in the OASIS ODF TC, can be quite hazzardous to your health.

    Not that this comes as any surprise.  Nearly five years ago in 2002, when i first joined OASIS to work on OpenDocument, it was clear that OASIS was a big vendor consortia.  While OASIS does have an affordable "Lawn Jockey" program, Sun is clearly calling all the shots on the OASIS ODF TC.  This is why ODF is bound so tightly to the OpenOffice feature set.

    Still, we thought the "Lawn Jockey" loophole could be used to balance out the interests and control of the OASIS big vendors.  We were wrong.  And it took near five years for the obvious to finally sink.  Well, "sink in" thanks to the OASIS hammer and boot.

    ~ge~

Gary Edwards

Tim Anderson's ITWriting - Tech writing blog » Microsoft's Jean Paoli on the XML document debate - 0 views

  • What’s distinctive about the goals of OOXML? Primarily, to have full fidelity with pre-existing binary documents created in Microsoft Office. “What people want is to make sure that their billions of important documents can be saved in a format where they don’t lose any information. As a design goal, we said that those formats have to represent all the information that enables high-fidelity migration from the binary formats”, says Paoli. He mentions work with institutions including the British Library and the US Library of Congress, concerned to preserve the information in their electronic archive. I asked Paoli if such users could get equally good fidelity by converting their documents to ODF. “Absolutely not,” he says. “I am very clear on that. Those two formats are done for different reasons.” What can go wrong? Paoli gives as an example the myriad ways borders can be drawn round tables in Microsoft Office and all its legacy versions. “There are 100 ways to draw the lines around a table,” he says. “The Open XML format has them all, but ODF which has not been designed for backward compatibility, does not have them. It’s really the tip of the iceberg. So if someone translates a binary document with a table to ODF, you will lose the framing details. That is just a very small example.”
  • “Open Document Format and Office Open XML have very different goals”, says Paoli, responding to the claim that the world needs only one standard XML format for office documents. “Both of them are formats for documents … both are good.”
    • Gary Edwards
       
      The door should have been slammed shut on OOXML near five years ago when, on December 14th, 2006, at the very first OASIS ODF TC meeting, Stellent's Phil Boutros proposed that the charter include, "compatibility with existing file formats and interoperability with existing applications" as a priority objective.
  • Another benefit Paoli claims for OOXML is performance. “A lot of things are designed differently because we believe it will work faster. The spreadsheet format has been designed for very big spreadsheets because we know our users, especially in the finance industry, use very large spreadsheets.
    • Gary Edwards
       
      Wrong. The da Vinci plug-in prototype we demonstrated to Massachusetts on June 19th, 2006 proved that there is little or no difference in spreadsheet performance between a OOXML file, and an ODF file.

      In fact, ODF version of the extremely large test file beat the OOXML load by 12 seconds.

      Where the performance difference comes in is at the application level. MS Excel can load a OOXML version of a large spreadsheet faster than OpenOffice can load an ODF version of that same spreadsheet.

      If you eliminate the application differential, and load the OOXML file and the ODF version of that same spreadsheet into a plug-in enabled Excel, the performance differences are negligible.

      The reason for this is that the OOXML plug-in for Excel has a conversion overhead identical to the da Vinci plug-in for Excel. It has nothing to do with the file format, and everythign to do with the application.

      ~ge~
  • ...5 more annotations...
  • Paoli points to the conversion errors as evidence of how poorly ODF can represent legacy Office documents. My hunch is that this has more to do with the poor quality of the converter.
    • Gary Edwards
       
      Note that these OASIS ODF TC November 20th iX "interoperability enhancement" suggestions were submitted by Novell as part of their effort to perfect a OOXML plug-in for OpenOffice!!!!

      "Lists" were th first of these iX items to be submitted as formal proposal. And Sun fought that list proposal viciously for the next four months. The donnybrook resulted i a total breakdown of the ODF consensus process. But, it ensured that never again would anyone be stupid enough to challenge Sun's authority and control of the OASIS ODF TC.

      Sun made it clear that they would viciously oppose any other efforts to establish interoperability with existing Microsoft documents, applications, processes effort.

      Point taken.

      ~ge~
  • the idea that Sun is preparing a reference implementation of OOXML is laughable.
    • Gary Edwards
       
      Sorry Tim. It's true. Sun and Novell are working together to develop native OOXML file support in OpenOffice. You can find this clearly stated in the Gullfoss Planet OpenOffice blogs.

      The funny thing is that Sun will have to implement and support the November 20th iX enhancements submitted by Novell!! (Or, the interoperability frameworks also submitted by Novell in February of 2007). There is simply no other way for OpenOffice to implement OOXML with the needed fidelity.

      ~ge~
  • One of new scenarios enabled by the “custom xml parts” (again, if you read their blogs, you must have heard of this stuff) is the ability to bind xml sources and a control+layout so that it enables the equivalent of data queries (we’ve had in Excel for many years already), just with a source which is part of the package, contrary to the typical external data source connection. Well this stuff, besides the declaration (which includes, big surprise, GUIDs and stuff like that) requires the actual Office 2007 run-time to work. So whenever MS says this stuff is interoperable, they cannot mean you can take this stuff away in another application. Because you can’t. This binding is more or less the same than the embedding of VBA macros. It’s all application-specific, and only Microsoft’s own suite knows how to instantiate this stuff.
    • Gary Edwards
       
      Stephan whacks this one out of the park! Smart Documents will replace VBa scripts, macros and OLE functionality going forward. It's also the data binding - workflow and metadata model of the future. And it's all proprietary!

      It's the combination of OOXML plus the MSOffice- Vista Stack specific Smart Documents that will lock end users into the Vista Stack for years to come.

      Watch out Google!

      ~ge~
  • Has Microsoft published the .doc spec publicly? Then why should ODF worry about the past? It’s not ODF’s concern to worry about Microsoft’s past formats. (Understand that the .doc format alone changed six times in the last eight versions of Office!) That’s Microsoft’s legacy problem, not ODF’s.
    • Gary Edwards
       
      There really is no need to access the secret binary blueprints. The ACME 376 plug-in demonstration proves this conclusively. The only thing the ACME 376 demo lacks is that we didn't throw the switch on the magic key to release all VBa scripts, macros and OLE bindings to ACME. But that can be done if someone is serious about converting the whole shebang of documents, applications and processes.

      The real problem is that although ACME 376 proves we can hit the high fidelity required, it is impossible to effectively capture that fidelity in ODF without the iX interoperability enhancements. The world expects ODF interoperability. But as long as Sun opposes iX, we can't pipe from ACME 376 to ODF.

      ~ge~
  • I put it to Paoli that OOXML is hard to implement because of all its legacy support, some of which is currently not well documented. “I don’t believe that at all. It’s actually the opposite,” he says. He make the point that third parties like Corel, which have previously implemented support for binary formats like .doc and .xls, should find it easy to transition to OOXML. “We believe Open XML adoption by vendors like Corel will be very easy because they have already been doing 90% of the work, doing the binary formats. The features are already there.”
    • Gary Edwards
       
      WordPerfect does an excellent import of MSWord .doc documents. But there is no conversion! It's a read only rendering. Once you start editing the document in WP, all kinds of funny things happen, and the perfect fidelity melts away like the wicked witch of west in a bucket full of water.
  •  
    Tim Anderson interviews Microsoft's Jean Paoli about MOOXML and ODF.    Jean Paoli of course has the predictable set of answers.  But Tim anderson provides us with some interesting insights and comments of his own.  There is also a gem of a comment from Stephane Rodriquez, the reknown spreadsheet expert.

    The bottom line for Microsoft has not changed.  MOOXML exists because of the need for an XML file format compatible with the legacy of existing MSOffic ebinary documents.  He claims that ODF is not compatible, and offers the "page borders" issue as an example.

    Page borders?  What's that got to do with the ODF file format?   These are application specific, application bound proprietary graphics that can not be ported to any other application - like OpenOffice.  The reason has nothign whatsoever to do with ODF and everything to do with the fact that the page border library is bound to MSOffice and not available to other applications like OpenOffice. 

    So here is an application specific feature tha tJean Paoli claims can not be expressed in ODF, but can in MOOXML.  But when are running the da Vinci ODF plugin in MSWord, there is no problem whatsoever in capturing the page borders in ODF!!!!!!!!!!!!!!!!!!!!!!!!!!!  No problem!!!!!!!!!!

    The problem is opening up that same da Vinci MSWord document in OpenOffice.  That's where the page borders are dropped.  The issue is based entirely on the fact that OpenOffice is unable to render these MSWord specific graphics bound to an MSOffice only library.

    If however we take that same page border loaded da Vinci MSWord document, and send it half way across the world to another MSWord desktop running da Vinci, the da Vinci plugin easily loads the ODF document into MSWord where it is perfectly rendered, page borders and all!!!!!!!!

    Now i will admit that this is one very difficult issue to understand.  If not f
  •  
    Great interview. Tim can obviously run circles around poor Jean Paoli.
Gary Edwards

Microsoft: the cloud as feature - Rough Type - 0 views

  • In the short term and even medium term, it is very likely that mainstream business customers will be more comfortable viewing the cloud as an add-on to rather than a replacement for their traditional Office programs. The competitive battle, in other words, will be fought largely on Microsoft's turf, and on that turf a certain amount of messiness is both allowed and expected. "Google and other Office competitors will be breathing a sigh of relief this morning," writes Mike Arrington. If so, it's a sigh they may come to regret.
  •  
    Here we go.  The final piece to the MS Stack puzzle falls into place.  Nick Carr provides excellent commentary and analysis.  As usual.
Gary Edwards

Universal Interoperability Framework for OpenDocument - 0 views

  • SUMMARY: The OpenDocument Foundation proposes that the OASIS Office TC begin now to create an interoperability framework for inclusion in OpenDocument v. 1.2. This document, one of a series of planned proposals, proposes first steps towards a comprehensive interoperability framework and OpenDocument conformance requirements.  This proposal is designed to bring ODF v. 1.2 into compliance with current ISO Interoperability Requirements.
  •  
    The OpenDocument Foundation "Universal Interoperability Framework" Proposal has not been submitted to the OASIS ODF TC as of this bookmarking.  But this version is complete except for a closing summation.
Gary Edwards

The French AFNOR Proposal to Merge ODF and MS-OOXML - 0 views

  • Summary Statement:  Hey, this is an excellent plan!  We can fully support this effort, even though the ISO National Bodies still have to work their way through the treacherous big vendor consortia controlled channels of OASIS ODF and Ecma 376.  Bringing the big vendor applications to heel is not going to be easy.  Merging ODF and MS-OOXML however is a worthwhile effort - one that the conversion and translator plug-in communities have been working on for the past three years!  It can be done!  And all it takes is five generic elements added to the existing ODF 1.2 specification ........
Gary Edwards

Frankly Speaking: Microsoft's Cynicism - Flock - 0 views

  • In July, Jones was asked on his blog whether Microsoft would actually commit to conform to an officially standardized OOXML. His response: “It’s hard for Microsoft to commit to what comes out of Ecma [the European standards group that has already OK’d OOXML] in the coming years, because we don’t know what direction they will take the formats. We’ll of course stay active and propose changes based on where we want to go with Office 14. At the end of the day, though, the other Ecma members could decide to take the spec in a completely different direction. ... Since it’s not guaranteed, it would be hard for us to make any sort of official statement.”
    • Gary Edwards
       
      Then why is Microsoft dragging us through this standardization nonsense? Is this nothing more than thinly veiled assault on open standards in general?
  • To at least some people at Microsoft, this isn’t about meeting the needs of customers who want a stable, solid, vendor-neutral format for storing and managing documents. It’s just another skirmish with the open-source crowd and rivals like IBM, and all that matters is winning.
    • Gary Edwards
       
      The battle between OOXML and ODF is very much about two groups of big vendor alliances. Interestingly, both groups seek to limit ODF interoperability, but for different reasons.

      See: The Plot To Limit ODF Interop
  •  
    Good commentary from Frank Hayes of Computerworld concerning a very serious problem. Even if ISO somehow manages to approve MS-OOXML, Microsoft has reserved the right to implement whatever extension of Ecma-OOXML they feel like implementing. The whole purpose of this standardization exercise was to bring interoperability, document exchange and long term archive capability to digital information by separating the file formats from the traditions of application, platform and vendor dependence.

    If Microsoft is determined to produce a variation of OOXML that meets the needs of their proprietary application-platform stack, including proprietary bindings and dependencies, any illusions we might have about open standards and interoeprability will be shattered.  By 2008, Microsoft is expected to have over a billion MS-OOXML ready systems intertwined with their proprietary MS Stack of desktop, server, device and web applications. 

    How are we to interoperate/integrate non Microsoft applications and services into that MS Stack if the portable document/data/media transport is off limits?  If you thought the MS Desktop monopoly posed an impossible barrier, wait until the world gets a load of the MS Stack!

    Good article Frank.

    ~ge~

Gary Edwards

A Savage Journey … ODF at the OOXML BRM « A Frantic Opposition - 0 views

  • A Savage Journey … ‘Erupting from my vivid nightmares into the retro 80s faded luxury of a five-star hotel in Geneva, the pictures of the first victim reappeared on the wall.  The head of the Brazilian delegation-it’s only a matter of time now. My mind thrashes to disentangle the thrown spaghetti threads of blurred reasoning; who’s next, is it just the heads of delegation they are after, any NB member, P-members only? The fog lifts and it’s worse.  Who is behind this, them or us?  We outnumber them, but maybe their plan is more devious.  Must find Bonky Bob, he’ll know what to do.’ Enough levity for now.  The BRM has held few surprises, other than the rather galling situation where I was forced to publicly toe the INCITS line by the temporary head of delegation, a Microsoft employee, against my better judgement.
Gary Edwards

Linux Today - OOXML/ODF: Just One Battlefield in a Much Bigger War - 0 views

  • If the OOXML format in its current form cannot get made into a true ISO standard, it could lock Microsoft out of any future plays in what could be the biggest IT revolution to date. Here are the pieces of the puzzle that fit together for me:
  • "Amazon SimpleDB is a web service for running queries on structured data in real time."
  • "Structured data." And what's a good way to contain such data? In well-built structured data file format of course. Like, for instance, the Open Document Format (ODF). And who has a vested interest in ODF? IBM certainly does. And so does Sun. And these two companies, along with Google, Microsoft, and I'm sure many others, realize that if cloud computing does indeed take off, then it will be the file format that makes the whole thing work. Which is why Microsoft feels it must get their format standardized. Even with tactics that ironically have started to attract the attention of the EU again. How else can they get a piece of the cloud pie?
  •  
    excellent discussion of why the ISO standardization of OOXML is so importnat to Microsoft.
Gary Edwards

The Case for Harmonization (that IBM will vote against anyway) « A Frantic Opposition - 0 views

  • The Case for Harmonization (that IBM will vote against anyway) In my recent post, I discussed the case for harmonization, mainly due to trying to portray a more kindly, conciliatory face in the “standards krieg” that I was enjoying so much. I have been forced to take a different tack, in light of being hung out to dry by my more business-focused IBM comrades and the work that the enemy has done in sprucing up the spec. However, as my closest friends know, for me, there are no half-victories, so you can rest assured that I will not settle for this weak “harmonization” compromise. I set out my (and IBM’s) stall some time ago on this, and as those on the Open Document Foundation know, any attempt at harmonization shall be met with swift and final retribution.  They were ejected from the odf-coven just days after their impudence. I have baited my trap, inviting this “harmonization” in my lair (the OASIS ODF TC) where I can bog them down in a morass of incompetence, bickering and politicking, so no new standard is ever ratified.  I have already been practicing for this, as you can see, by the ODF 1.1 and 1.2 specs.
  •  
    This very funny satire builds on some harsh realities. The ODF chickens have come home to roost, and it isn't pretty. Very funny, yes. But not pretty for those who continue to believe that somehow ODF is a standard worthy of their support. The flip side of the coin is that using the same critieria of interoperability, OOXML is worthless. The sad truth is that both ODF and OOXML are applicaiton specific formats that will continue to defy and defeat all efforts at interoperability. Inparticular, it's the presentation layers of ODF and OOXML that remain bound to the layout engines and feature sets of their originating applications. Just as the presentation layers defy interoperability, they will also defeat harmonization. The only way to harmonize two application specific formats is to harmonize the originating applications. And Microsoft, Sun and IBM are not about to do that. The links in this satire are stunning!!! They shout loudly as to how Microsoft is going to respond to the ECIS anti trust allegations. So when you stop laughing, make certain you track down the links and read through the various OASIS ODF archive threads. IBM and Sun had their chance to fix ODF interoperability. Now it may be too late.
Gary Edwards

Microsoft's Open Source Strategy & The Yahoo bid to get back in the game - 0 views

  • On the morning of February 1st 2008, Microsoft announced an unsolicited bid of $44.6B hostile for Yahoo!, and by the end of the day, Microsoft had lost $20B in market capitalization. Where does this leave Microsoft's open source strategy and the analysis thereof? Yahoo! was a pioneering "internet company", one of the first to really create and capture value of a world newly web-enabled. And like many of these so-called internet companies (Google was another), Yahoo! built it infrastructure on open source technologies. Why? Better, faster, cheaper: Dave Filo and Jerry Yang were still poor college students back in the day, but smart. (As were Sergey Brin and Larry Page, but that's another story.)
  •  
    Michael Tiemann picks up where Mary Jo Foley left off. he takes her prescient arguments concerning Microsot's Open Source Strategey and xtends them to Microsot's bid for Yahoo! This is a must read!
Gary Edwards

Microsoft's OOXML: The No vote | Computerworld - 0 views

  • The Cyberspace Law and Policy Centre at the University of New South Wales recently hosted a symposium to discuss issues surrounding the proposed Microsoft OOXML document format standard. In attendance at a technical session were representatives from Microsoft, IBM, Google, the Open Source Industry Australia, Standards Australia, the National Archives of Australia, and the International Organisation for Standardisation.
Gary Edwards

Microsoft bids big for Yahoo - $44.6 Billion |Techworld.com - 0 views

  • Microsoft has offered to buy the search engine company Yahoo for $44.6 billion (£22.4 bn) in cash and shares. The offer is 62 percent above Yahoo's closing share price on Thursday
  •  
    I hope the anti trust police are awake.
Gary Edwards

garyedwards's Discussions at ZDNet.co.uk Community - 0 views

  • garyedwards's Discussions Breaking the Web Talkback: Google: OOXML 'insufficient and unnecessary'
Gary Edwards

Plan B: The NO ViSTA Mandates, and the failure of ISO/IEC - 0 views

  • Plan B: The "NO ViSTA" Mandates:  the failure of Anti Trust Laws and International Trade Agreements to Stop The Great Monopolist, Microsoft A series of surprising government mandate announcements rolled out in the immediate aftermath of the ISO/IEC decision to fast track Ecma 376 otherwise known as Microsoft Office Open XML (MOOX).  The three articles commented on here are all from Information Week, who has done yeoman work concerning the OpenDocument - MOOX controversy that has so upset Microsoft.  Now the mighty monopolist can taste victory, with fast track approval of MOOX certain, and ISO/IEC in the bag.  Incredibly the company that escaped a Court ordered death sentence by purchasing what amounts to a presidential pardon.  They even avoided the stink of their own lobbyist and henchman Jack Abramoff, and his motley crew of Ralph Reed and Grover Nyquist operatives.  Now they are well on their way towards purchasing an International Standard.  So much for Plan A.  Time for Plan B, the "NO ViSTA" mandate.
  •  
    Okay.  I've combined my three comments into a single page.  Sadly Diigo does not offer spell checking.  My apologies to all.  Hoepfully this will be a better read.
‹ Previous 21 - 40 of 54 Next ›
Showing 20 items per page