OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: Catalog Requirements

Norm wrote:
| / Terry Allen <tallen@sonic.net> was heard to say:
| | Paul responded:
| | | Well, "rarely ambiguous" is still troubling, I would think.
| | 
| | I'm trying to find a concrete example of the trouble.
| I think Paul's example is perfectly concrete, but if you prefer:
| <?xml version="1.0"?>
| <!DOCTYPE book SYSTEM "http://www.oasis-open.org/docbook/xml/4.1.2/" [
| <!ENTITY % local.book.attrib 
| xmlns:xsi CDATA #IMPLIED
| xsi:schemaLocation CDATA #IMPLIED">
| ]>
| <book xmlns='http://www.oasis-open.org/docbook/schema/4.1.2/'
|       xmlns:xsi='http://www.w3.org/2000/10/XMLSchema-instance'
|       xsi:schemaLocation='http://www.oasis-open.org/docbook/schema/4.1.2/'>
| <?xml-stylesheet href="http://www.oasis-open.org/docbook/xml/4.1.2/"
| type="text/css"?>
| <chapter>...</chapter>
| </book>
| I've got at least three classes of identifiers here: a system
| identifier, a stylesheet identifer, and a schema location identifier.

They are, in order:


| I *could* have made them unambiguous at the URI level, but I am not
| required to do so. And there are organizations (e.g., the W3C) that
| deprecate using explicit URIs in favor of content negotiation.
| | | You want to be able to map the same string into different
| | | SOIs depending on the original string's context.
| | 
| | Why?  example, please.
| Because I want to get the DTD, the stylesheet, and the schema
| depending on the context.

Leaving aside my opinion of the W3C and the utility of content

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.

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.

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. 

best regards, Terry

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC