Lists Home |
Date Index |
Also because we are more often than not required to use
IE by company policy and by customer requirement
cited in an RFP.
The second part of the issue is the failure of both
developers and specification organizations to directly
address procurement processes and rules. Attempts to
do that from the top (say in xml.gov) will generally
fail for the same reasons that the specification organizations
Developers, as a general rule, don't make procurement decisions.
The success of heuristics such as the old "noone gets fired for
choosing IBM" is based on that. They put their trust in a
brand because the details of the technology are not sufficiently
understood and they shouldn't be required to understand them.
The recent articles at CNET etc. with quotations from XML
luminaries testify to the lack of teeth in standards and
the ascendancy of vendor open specifications. If so, then
we should quit looking to the specification organizations
and look to the successful vendors for running code and
coherent development frameworks. The market rules. If
so, then this technique
is standard. If not, then is the question
does the running code OR the dominant content type determine
From: Didier PH Martin [mailto:email@example.com]
yop! very true. In my daily practice I see a lot of intranets using IE
simply because it offers more then the others. For instance, the other
browsers still do not allow augmenting the default behavior. To be able to
separate the code from the declarative statements improve code re-use and
therefore reduces costs. Moreover, you can transform an XML document on the
client side into HTML and tag element to be "editable". Hence, only some
parts of the displayed document are editable. And on and on....
W3C seems like a parliament too far away from practical needs and caught
into political vested interests or simply jammed into ethereal dialogs.
This said, it seems that Mozilla came back to life and is now improving,
which is no longer the case for IE. If mozilla brings a good run time
environment for intranets apps, then things may change and we may have an
alternative option to XAML/IE/longhorn. Mozilla teams should listen more to
developers needs and less to W3C in order to succeed.