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

 


Help: OASIS Mailing Lists Help | MarkMail Help

provision message

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


Subject: Containment Rules


We've said that the core create operation supports containment 
(hierarchies).  Every object is bound beneath a parent--the default 
parent is the target.  Are there rules about what types of objects a 
particular type of object can contain? 

For example, suppose that an OU can contain another OU (but not an ORG). 
Does the target declare this somehow, or must the requestor "program by 
exception"?  I think that we'd prefer to declare these rules so that the 
requestor can (understand them and thereby) avoid exception.

Perhaps each target could also expose its containment rules?  In much 
the same way that each target exposes its capabilities (i.e. the set of 
interfaces each object type supports), the target could expose the set 
of types each object type may contain.

Gary



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