Re: Catalog circularity

[dcpleland@ftnetwork.com]

I think that it should just throw a warning, and stop the loop, and carry on processing.

Regards,
David Leland
************************************************************
ndw@nwalsh.com wrote on 5/23/01 5:06:28 PM
************************************************************
From the comments list:

  How should a catalog processor behave if it encounters a circular
  dependency, e.g. firstcatalog.cat contains a <delegatePublic>
  pointing to secondcatalog.cat which in turn contains a <nextCatalog>
  pointing back to firstcatalog.cat?  Should it simply ignore the
  reference, or should it report an error?

Comments?

I think that we have to make this an error that must be detected.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM   | I don't make predictions. I never have and I
XML Standards Engineer | never will.--Tony Blair
Technology Dev. Group  | 
Sun Microsystems, Inc. | 

------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: entity-resolution-request@lists.oasis-open.org


___________________________________________________________________________________________________
Get your free e-mail account with *unlimited* storage at  http://www.ftnetwork.com

Visit the web site of the Financial Times at  http://www.ft.com