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: An interoperability problem?


/ John Cowan <jcowan@reutershealth.com> was heard to say:
| Norman Walsh wrote:
| 
| > Now, the greedy processor is going to retrieve these stylesheets:
| > 
| >   http://example.com/a.xsl
| >   file:///stylesheets/bPrime.xsl
| > 
| > But the lazy processor is going to retrieve:
| > 
| >   file:///stylesheets/aPrime.xsl
| >   file:///stylesheets/bPrime.xsl
| > 
| > I don't see any way out of this interoperability problem: I don't
| > think we can say either of these processors is "wrong" in some way [...].
| 
| No, what is wrong is the document.  If you make reference to something
| catalog-relevant before declaring your catalog, you cannot expect
| consistent results.

I suppose this is one possible answer. But I don't find it very
satisfying.

| Or did you mean to say that Greedy will fetch example.com/a.xsl and
| example.com/b.xsl?

Nope.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM   | There is no such thing as an absolute
XML Standards Engineer | certainty, but there is assurance sufficient
Technology Dev. Group  | for the purposes of human life.--John Stuart
Sun Microsystems, Inc. | Mill


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


Powered by eList eXpress LLC