Lists Home |
Date Index |
There probably are wonks in DC who
believe this sort of thing. They tend to be
a trendy lot. But it won't work for reasons
most who have sat around the hotel rooms
for years are familiar with. The
civil servants sit down to wait out the
administration. Remember when we were all
told to migrate to ADA and the waivers started
raining down like holiday confetti?
The base reason is that by the time a
logistics group is through with their work,
it comes down to real parts and assemblies,
not the standards for them. The migration
to online procurements, online standards,
etc is well underway but not there yet.
Force feeding through the top won't change
the minds of the engineers. They will use
a W3C spec because it is usable.
From: Rick Jelliffe [mailto:email@example.com]
From: "Bullard, Claude L (Len)" <firstname.lastname@example.org>
> Sure as heck shreds the CIO proclamations for
> W3C-only tech. It's a CALS redux: the procurement
> officers sign the checks and that drives the
> emergence, not the standard or the imprimatur.
I wish that the XML.COM article on the CIO draft had actually
included some references to the document.
The article is pitched as if it means that non-W3C (presumably
excepting ISO, formally) specifications are being blocked, rather
than that W3C is being added to some favoured list.