[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: What is XHTML 2.0 for?

• To: Dare Obasanjo <dareo@m...>
• Subject: Re: What is XHTML 2.0 for?
• From: Paul Prescod <paul@p...>
• Date: Thu, 21 Nov 2002 13:17:36 -0800
• Cc: Mike Champion <mc@x...>, Xml-Dev <xml-dev@l...>
• In-reply-to: <B885BEDCB3664E4AB1C72F1D85CB29F8040EF7D6@R...>
• References: <B885BEDCB3664E4AB1C72F1D85CB29F8040EF7D6@R...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021016

Dare Obasanjo wrote:

> A browser-platform that understands [X]HTML/XForms/SVG/etc is not 
> exactly what I'd call a thin client. ;)  

I know you are joking but, I strongly agree! The terms thin/thick are 
not helpful anymore. There are a variety of orthogonal issues in 
client-deployment:

  1. Is the client "rich" or not, where rich means multimedia, vector 
graphics, client-side logic and GUI widgets.

  2. Is the client "standards-based" or not?

  3. Is the client URI-addressable or not?

  4. Is the client mostly declarative or mostly code?  Declarative 
clients tend to be XML-based with script for glue instead of 
code-centric (as in downloaded Java or .NET applets) with data fetched 
by the code on demand.

The existence of tools like Google and Yahoo depend upon 
standards-based, URI-addressable, declarative information publishing 
applications. The challenge is to create rich clients that preserve 
these virtues. Security is also a huge issue.

  Paul Prescod

• References:
  • RE: What is XHTML 2.0 for?
    • From: "Dare Obasanjo" <dareo@m...>

• Prev by Date: RE: RELAX NG Compact Syntax becomes an OASIS Committee Draft
• Next by Date: RE: What is XHTML 2.0 for?
• Previous by thread: RE: What is XHTML 2.0 for?
• Next by thread: RE: What is XHTML 2.0 for?
• Index(es):
  • Date
  • Thread