[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [provision] Containment Rules
I'm not sure what the UML would be, but couldn't containment rules be as simple as the following? <Target id='' > ... <ContainmentRules> <Type name='Organization'> <MayContainType name='OrganizationalUnit'/> </Type> <Type name='OrganizationalUnit'> <MayContainType name='OrganizationalUnit'/> </Type> </ContainmentRules> </Target> I'm sure there are more elegant ways to do this, but I think what we're trying to do is fairly straightforward. We could probably combine containment rules with capabilities if we wanted to do so: both are forms of target-specific "meta-data" for object types. Gary Darran Rolls wrote: >This is interesting. How would one express such a rule, could we use XACML? > > >It sounds like the target capabilities definition element is the key to SPML >2.0. We should try and draw out an rough object model here. If someone >wants to throw out a strawman (in words) I'll volunteer to draw the UML >model... > >-djr > > > >>-----Original Message----- >>From: Gary P Cole [mailto:Gary.P.Cole@Sun.COM] >>Sent: Thursday, May 13, 2004 5:27 AM >>To: PSTC >>Subject: [provision] 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 >> >> >>To unsubscribe from this mailing list (and be removed from >>the roster of the OASIS TC), go to >>http://www.oasis-open.org/apps/org/workgroup/provision/members >>/leave_workgroup.php. >> >> >> >> > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]