W3C home > Mailing lists > Public > www-tag@w3.org > February 2005

RE: Significant W3C Confusion over Namespace Meaning and Policy

From: Rice, Ed (HP.com) <ed.rice@hp.com>
Date: Tue, 22 Feb 2005 09:22:55 -0800
Message-ID: <7D6953BFA3975C44BD80BA89292FD60E01678177@cacexc08.americas.cpqcorp.net>
To: "Bullard, Claude L (Len)" <len.bullard@intergraph.com>, "Chris Lilley" <chris@w3.org>, "Pawson, David" <David.Pawson@rnib.org.uk>
Cc: "Jonathan Borden" <jonathan@openhealth.org>, <www-tag@w3.org>

I think it depends on how dynamic the information is.  If you expect the
catalog to change rapidly, caching the content can cause more problems
than it solves.


-----Original Message-----
From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf
Of Bullard, Claude L (Len)
Sent: Tuesday, February 22, 2005 8:33 AM
To: 'Chris Lilley'; 'Pawson, David'
Cc: 'Jonathan Borden'; 'www-tag@w3.org'
Subject: RE: Significant W3C Confusion over Namespace Meaning and Policy

On the other hand, it should evolve down to a 
semi-stable set of stable DTDs or schemas that 
can be replicated.  Relying on an always connected 
system is dicey.  That is a recurring pattern of 
network design:  what to localize/replicate and 
what to centralize/connect to.  

Where do catalogs thrive?  It seems to be a best 
practice question worth thinking about.


From: www-tag-request@w3.org [mailto:www-tag-request@w3.org]On Behalf Of
Chris Lilley

The focus should probably be on getting application developers to use
catalogs, so that users don't have to know about them and see no
difference when online or offline.

PD>   I would hate XML and its applications to become a tool
PD> for connected users only.

Agreed. Really annoying to be editing a doc on a plane, and it times out
for a couple of minutes and then says the xhtml dtd is not available :)
Received on Tuesday, 22 February 2005 17:22:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:45 UTC