W3C home > Mailing lists > Public > public-cdf@w3.org > March 2006

Re: CDR Framework: Last Call Comments

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 13 Mar 2006 15:08:06 +0100
To: Steve K Speicher <sspeiche@us.ibm.com>
Cc: public-cdf@w3.org
Message-ID: <hkta12dbp0d8i88gt1nh1v5m1cdl08ifei@hive.bjoern.hoehrmann.de>

* Steve K Speicher wrote:
>In the case of our WICD profiles: mobile and full, full is a super-set
>of mobile.  If full content were provided to a mobile profile only
>capable device, then the mobile device would rely on user agent
>conformance for handling unknown content.  Given that this fallback
>behaviour would be XHTML fallback behaviour - "If a user agent
>encounters an element it does not recognize, it must process the
>element's content"[1] - we expect that much (though admitedly, not
>all) full XHTML 1.0 content will be usable (though not perfectly
>rendered, of course) by a typical end user.
>
> [1] http://www.w3.org/TR/xhtml1/#uaconf

http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410 seems to
have clearer text, "If a user agent encounters an element it does not
recognize, it must continue to process the children of that element.
If the content is text, the text must be presented to the user." While
this text is not entirely clear to me, it seems that in case of e.g.

  <style>
    ...
  </style>

or

  <script ...>
    ...
  </script>

the style sheet or script "must be presented to the user". It is not
clear to me how this would result in usable results. My homepage would
be entirely unusable, for example.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Monday, 13 March 2006 14:09:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:21 UTC