[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Catalog circularity
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. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC