Grouper Developers Forum

[Tom Barton <>]

Gary presented an initial draft of how to represent composite groups in 
the XML import/export schema, as follows:

<list field='members' groupType='base'>
   <composite>
     <groupRef id='d2823e8a-303f-4703-8b13-cd669586e76e'
             name='qsuob:fionas'
      displayName='QS University of Bristol:fionas'/>
    <compositeType>union</compositeType>
     <groupRef id='d2427186-3260-4651-a44e-acdca7f6c29f'
             name='qsuob:keiths'
      displayName='QS University of Bristol:keiths'/>
   </composite>
</list>

I raised a concern that this format relies on the order of presentation 
of the two groupRef elements when the compositeType is "complement". I 
think this should be schematically declared so that any XML-faithful 
parser that deployers use should have a chance to get it right.

So here's an alternative:

<list field='members' groupType='base'>
  <composite type="complement"/>
    <groupRef operand="1"
      id='d2823e8a-303f-4703-8b13-cd669586e76e'
      name='qsuob:fionas'
      displayName='QS University of Bristol:fionas'/>
    <groupRef operand="2"
      id='d2427186-3260-4651-a44e-acdca7f6c29f'
      name='qsuob:keiths'
      displayName='QS University of Bristol:keiths'/>
   </composite>
</list>

The "operand" attribute is only required for the "complement" composite 
type. By convention the composite this indicates is

  <group with operand=1> <composite type> <group with operand=2>

Tom