Spec issue #10: Reference capability declaration with no referencedefinition.

[Gary P Cole <Gary.P.Cole@Sun.COM>]

10. What if reference capability declaration contains no reference 
definition?

In the spec's listTargets example, the listTargetsResponse contains two 
targets.
Within target2’s declaration of the Reference Capability for Person, the 
provider declares that a Person on target2 may own an account on 
target1. (That is, an instance of Person on target2 may use an "owns" 
type of reference to refer to an instance of Account on target1.)

<listTargetsResponse status=“success">
...
<target targetID=“target2”>
...
<capabilities>
...
<capability identifier=”urn:oasis:names:tc:SPML:2.0:reference”>
<appliesTo entityName=”Person”/>
<referenceDefinition typeOfReference=”owns”/>
<schemaEntity entityName=”Person”/>
<canReferTo entityName=”Account” targetID=“target1”/>
</referenceDefinition>
</capability>
</capabilities>
</target>
</listTargetsResponse>

Since the reference definition is *open content* of the <capability>,
nothing requires a declaration of the reference capability to contain a 
<referenceDefinition>.
This raises the question of what a declaration of the reference 
capability would mean
if no <referenceDefinition> were present.

In the listTargetsResponse example above, what would it mean if the 
provider omitted the <referenceDefinition>? Would this mean that an 
instance of Person on target2
may use *any* type of reference refer to an instance of any schema 
entity on any target?