[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Resource discovery directory [was: XML Catalog proposal]
- From: Jonathan Borden <firstname.lastname@example.org>
- To: Paul Grosso <email@example.com>, XML-Dev Mailing list <firstname.lastname@example.org>
- Date: Tue, 02 Jan 2001 13:28:43 -0500
Paul Grosso wrote:
> As Dan Vint's message points out, calling this a catalog can
> lead to confusion. The OASIS Entity Management catalog ,
> John Cowan's XML-ization of it called XML Catalog , and
> the current OASIS Entity Resolution Technical Committee (ERTC)
> work  on standardizing an XML ER catalog (xmlcat) are all
> talking about a mechanism to map external identifier information
> (e.g., public ids, system ids, and namespace names) to URIs.
> What the current discussion is about is defining the format
> of a resource discovery "directory". (See also Tim Bray's paper
> of Sept 1999 .) I would strongly suggest we avoid the word
> "catalog" in the current discussion.
I have no particular attachement to the term "catalog". Would either
"XML Namespace Resource Directory" (XNRD)
"XML Resource Directory" (XRD) be preferable?
The following has the best acronym:
"XML Namespace URI Resource Directory" (XNURD).
Open for discussion.
> I'd also suggest we avoid mixing ER catalogs with resource
> discovery (RD) directories.
After further consideration and offline discussion I agree that it is
best not to mix these together.
>These things are at different
> levels and should not be mixed. Mapping external ids is
> something that happens in the middle of an XML parsing
> process by an entity resolver (a module called by the
> XML parser itself), whereas using a RD directory to find
> a stylesheet or a metadata or relevant external code is
> something that happens "above" the level of the parser.
My thinking was that one might create an entity resolver which resolves
external entities in a namespace dependent fashion (note, doing such is not
dependent on any particular or direct support for entities in the namespace
directory document). By this mechanism, as new namespace URIs are
encountered *during the parse phase* the namespace directory would be
resolved and parsed into a map. As elements are parsed, the map associated
with the element's namespace URI could be used in the entity resolution
Again, this mechanism which I bring up for discussion purposes, could
just as easily be supported by using a namespace resource pointing to a
<p class="resource">The OASIS Open Catalog format catalog for
this namespace is: <code>...</code> ...</p>
> I do think there is a potentially useful synergy between
> the ER catalog and the RD directory
Yes. We can explore these synergies.
The Open Healthcare Group