[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Handling of circular dependencies
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? ------------------------------------------------------------------ To unsubscribe from this elist send a message with the single word "unsubscribe" in the body to: entity-resolution-comment-request@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC