W3C home > Mailing lists > Public > www-html@w3.org > March 2007

RE: Control Text-file Embedding in HTML-docs

From: sunil vanmullem <sunil.vanmullem@btopenworld.com>
Date: Sat, 31 Mar 2007 15:35:33 +0100
To: <tina@greytower.net>
Cc: <www-html@w3.org>
Message-ID: <000001c773a1$d7042350$0200a8c0@xppropc11>

Yes its important to recognise the importance of backward compatibility 
and the accessibility legislation that gives certain communities the 
ability to litigate. Though this shouldn't be allowed to act as a hindrance 
to invention, innovation or the ability to progress.

It doesn't necessarily follow that the lowest common denominator should 
have the highest influence. i.e. the assertion about being back to square
one.

Standards implementation address problems of backward or upward
compatibility 
through standardisation processes (E.g. IEFT standardisation processes). 
These normally includes the following steps.

1) for the new standard to be initially released to the Browser Developers
along with a reference implementation and a certification process that tests
conformance. 
2) Once the certification process is complete or reached its milestone, the
Browser Developers release public patches or new products so that their
products are ready for the new standard while continuing to support existing
standards.
3) the new standard is released for general use
4) Applications are developed using the new standards.
5) end users have a seamless transition to the new standard.

If the end user chooses not to use certified browsers, that is their choice 
and at some point in time they would need to upgrade as applications evolve.



-----Original Message-----
From: www-html-request@w3.org [mailto:www-html-request@w3.org] On Behalf Of
Tina Holmboe
Sent: 31 March 2007 03:35
To: www-html@w3.org
Subject: Re: Control Text-file Embedding in HTML-docs

  Yes. And to make absolutely certain you also reach users with UAs or
  settings or physical realities which do /not/ support the above
  pulling in, ...  We are back to square one: build the /entire/ document on
the server,
  and send it to the client; ...
Received on Saturday, 31 March 2007 14:34:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:16:08 GMT