Re: Catalog Requirements

/ Terry Allen <> was heard to say:
| They are, in order:
| 
| http://www.oasis-open.org/docbook/xml/4.1.2/
| http://www.oasis-open.org/docbook/xml/4.1.2/
| http://www.oasis-open.org/docbook/schema/4.1.2/

Oh, barf, I meant them all to be the same.

| In the case above you have two different URLs:  the SYSTEM
| identifier that you are using for both the DTD and the style sheet,
| and the URL for the schema location.  So we can discard the latter
| for purposes of this discussion.

No, I meant it to be the same.

| And yes, you could have used different URLs for the DTD and the
| style sheet.  I think that that's the only way in which you'll ever 
| be able to count on that instance being processed the same way
| by various tools.

Tools that understand xmlcat will work just fine with

<system id="http://www.oasis-open.org/docbook/xml/4.1.2/" soi="docbook.dtd"/>
<stylesheet id="http://www.oasis-open.org/docbook/xml/4.1.2/" soi="docbook.css"/>
<schemaloc id="http://www.oasis-open.org/docbook/xml/4.1.2/" soi="docbook.xsd"/>

| And do you have software that actually will fetch the DTD or the style
| sheet from the same directory depending on the XML function of its
| identifier?  Maybe I'm missing something, but this seems a contrived
| example that doesn't solve any real problem. 

No, I don't, but if I had a catalog that let me get the right answer,
I might.

Terry, are you really suggesting that this boils down to

  <uri target="first uri" destination="second uri"/>

and that's all we should provide?

I think that's just awful. It means I must use unique "first uri"
across all applications all the time forever or I'm going to get
hosed.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <> | We are thinking beings, and we cannot
http://nwalsh.com/            | exclude the intellect from
                              | participating in any of our
                              | functions.--William James