A reference from an acceptance criterion to the named specification it elaborates: adiggs:PerformanceCriterion or diggs:DesignConformanceCriterion citing thediggs:RIColumnSpecification, diggs:RILTPSpecification or diggs:GroutSpecificationwhose requirements it states one of, or a diggs:CompositeAcceptanceCriterion doingthe same. This is not basedOnRef: a criterion is a component of the specification itelaborates, not a more specific version of it, and the per-propertymost-specific-wins resolution of basedOnRef has nothing to inherit between objectsthat share no properties. Composition is not specialization. At most one may begiven: a criterion belongs to one specification, and where it is also relevantelsewhere the consuming object cites both through its own repeatableprogramSpecificationRef. The target is the broad diggs:AbstractProgramSpecificationhead, so a criterion could technically cite another criterion or a composite; thatis not the intended use, since membership of a criterion in a composite is recordedby the composite's own criterionRef. Given by reference only.
The gml:identifier value of the referenced feature, as a fully qualifiedvalue. It gives an alternative to the gml:id in xlink:href for findingthe referenced feature, mainly to reference a feature by a globallyunique identifier and where naming conflicts occur with gml:id whenaccessing data in external files.
<element name="partOfSpecificationRef" type="diggs:FeatureReferenceType"><annotation><appinfo source="urn:x-gml:targetElement">diggs:AbstractProgramSpecification</appinfo><documentation>A reference from an acceptance criterion to the named specification it elaborates: a diggs:PerformanceCriterion or diggs:DesignConformanceCriterion citing the diggs:RIColumnSpecification, diggs:RILTPSpecification or diggs:GroutSpecification whose requirements it states one of, or a diggs:CompositeAcceptanceCriterion doing the same. This is not basedOnRef: a criterion is a component of the specification it elaborates, not a more specific version of it, and the per-property most-specific-wins resolution of basedOnRef has nothing to inherit between objects that share no properties. Composition is not specialization. At most one may be given: a criterion belongs to one specification, and where it is also relevant elsewhere the consuming object cites both through its own repeatable programSpecificationRef. The target is the broad diggs:AbstractProgramSpecification head, so a criterion could technically cite another criterion or a composite; that is not the intended use, since membership of a criterion in a composite is recorded by the composite's own criterionRef. Given by reference only.</documentation></annotation></element>
