[
Lists Home |
Date Index |
Thread Index
]
It has just occured to me that dedicating a catalog to a document type, and
putting it at a default URL (certainly hosted by the document type author)
is essentialy the same thing as associating a document with the URL of a
document listing various meta-data resources (like RDDL v2 could be)... The
terms change but they are just different words to describe the same system.
BTW, if you could concatenate the RDDL xlink:role and xlink:arcrole, and
still get a URI, it would be the URI that you would resolve in the catalog
described in my previous mail. Of course you can't because a concatenation
of two URI gives a URN, not a URI.
I'm not sure I'm pretty clear here... I still need to think about it and try
to get a precise description of the system.
Regards,
Nicolas
----- Original Message -----
From: "Nicolas Lehuen" <nicolas.lehuen@ubicco.com>
To: "Michael Brennan" <mpbrennan@earthlink.net>; "John Cowan"
<jcowan@reutershealth.com>
Cc: <xml-dev@lists.xml.org>
Sent: Saturday, January 19, 2002 12:09 AM
Subject: Re: TR: [xml-dev] RDDL (was RE: [xml-dev] Negotiate Out The Noise )
> 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 ?
>
> Regards,
> Nicolas
>
> ----- Original Message -----
> From: "Michael Brennan" <mpbrennan@earthlink.net>
> To: "John Cowan" <jcowan@reutershealth.com>
> Cc: <xml-dev@lists.xml.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>
> >
> >
>
>
>
> -----------------------------------------------------------------
> 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>
>
>
|
