Lists Home |
Date Index |
OK, so this could be the best world : a combination of local catalogs with
fallback remote catalogs, possibly with a HTTP cache in between ?
Let's suppose for now that we'll use catalogs. Now, for any given document,
we have a PI that points to a default catalog and a DOCTYPE with a public
and a system ID. Now I want to get a schema in RELAX NG for the document so
that I can validate it, and, say, the Java Archive that contains an
implementation of java.lang.Applet (which after all is as a nice Java plugin
API for browsers) that can display the document ?
Suppose the document is an X3D document linked from an XHTML file, then the
browser could validate it and automatically download a renderer Applet then
feed him with the document. Nice, isn't it ?
My question is : should all those resources (schemas, plugins, etc.) be
resolved directly in the catalog (in which case we have to find a way to sum
up the purpose, nature etc. of resources in their URIs), or thanks to a
RDF/RDDL/whatever document which can handle more complex resolving semantics
than the catalog (in which case we have to define the URI of this document,
and of course the model of the document itself, back to the workbench) ?
Would the catalog resolving capabilities suffice, if associated to a clever
URI format that can encompass purpose and nature of resource ?
----- Original Message -----
From: "Michael Brennan" <email@example.com>
To: "John Cowan" <firstname.lastname@example.org>
Sent: Friday, January 18, 2002 11:21 PM
Subject: Re: TR: [xml-dev] RDDL (was RE: [xml-dev] Negotiate Out The Noise )
> John Cowan wrote:
> > Nicolas Lehuen wrote:
> > > Are those catalog DNS like ?
> > They could be, though there is currently nothing analogous to the DNS
> > root servers. Catalogs can be local or remote, and local catalogs
> > can delegate to remote ones, since catalogs are referred to by
> > URIs.
> And an XML instance can contain a PI that points to a default catalog
> that the application can fall back to resolve URIs. The referenced
> catalog is appended to the end of the chain of catalogs to search.
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>