Re: [entity-resolution-comment] Public Comment

["Rob Lugt" <roblugt@elcel.com>]

I don't know about a recommended approach, but there are a number of things
you could try:-

1)  If you are sharing the catalog on a windows network, try using UNC paths
instead of drive mapping.  e.g.
<uri name="http://www.oasis-open.org/committees/docbook/";
   uri="file://<host>/<share>/file"/>

2)  Consider using relative URIs in your catalog.  If I remember rightly,
these should resolve relative to the catalog file in which they appear.
e.g.
<uri name="http://www.oasis-open.org/committees/docbook/";
   uri="docbook/"/>

3) Following on from your idea of putting file locations in another file,
such as mechanism already exists in XML, so you can use that.  e.g.

<!DOCTYPE catalog [
<!ENTITY % files SYSTEM "file-locations.ent">
%files;
]>
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
<uri name="http://www.oasis-open.org/committees/docbook/";
   uri="&PROJECT_INSTALL_LOCATION;/docbook/"/>
</catalog>

Best regards
Rob Lugt
ElCel Technology
http://www.elcel.com/

----- Original Message ----- 
From: <comment-form@oasis-open.org>
To: <entity-resolution-comment@lists.oasis-open.org>
Sent: Wednesday, October 22, 2003 11:27 PM
Subject: [entity-resolution-comment] Public Comment


> Comment from: csalter@ca.ibm.com
>
> What's the recommended approach for sharing xml catalogs that have
concrete file system locations in them?  For example, I have a catalog with
several entries like this...
>
> <uri name="http://www.oasis-open.org/committees/docbook/";
>           uri="file:///D:/projects/oasis/docbook/website/"/>
>
> Now I want to use this catalog on another machine where the 'project'
directory is installed on the 'E:' drive.  So I'm assuming one would need
some thing like this...
>
> <rewriteURI uriStartString="file:///D:/project/"
>             rewritePrefix="file:///E:/project/"/>
>
> It seems to me it would be nice to have some convention when specifying
file system URIs so that they can be easily 're-mapped' to actual drive
names (and to make it clear at a glance where these substitutions are
intended).   For example...
>
> <uri name="http://www.oasis-open.org/committees/docbook/";
>           uri="/PROJECT_INSTALL_LOCATION/oasis/docbook/website/"/>
>
> <rewriteURI uriStartString="/PROJECT_INSTALL_LOCATION"
>             rewritePrefix="file:///E:/project/"/>
>
> The next logical step would be to put move the rewrites containing the
'actual' file locations into a separate catalog file.  That way the 'main'
catalog could be shared in a team repository and wouldn't need to be edited.
Only the small catalog containing rewrites to 'actual' file locations would
ever need to be customized.
>
> Any comments/suggestions ?
>
> To unsubscribe from this list, send a post to
entity-resolution-comment-unsubscribe@lists.oasis-open.org, or visit
http://www.oasis-open.org/mlmanage/.
>
>