Schema documentation for component diggs:AbstractAcceptanceCriterion

Abstract head of the substitution group for acceptance criteria. A criterion states one testable requirement: what is measured, how the measurements are reduced to one value, the comparison applied and the limit compared against. As a program specification it also carries the scope of the features it governs and may specialize a more general criterion through basedOnRef. Its members differ in what is measured: diggs:PerformanceCriterion measures a physical property of the completed work, and diggs:DesignConformanceCriterion measures a geometric or constructional property against its design intent. Each names its subject through the parameterName of limit; use the DIGGS dictionary properties.xml for a performance criterion and designProperty.xml for a design conformance criterion. A specification that imposes several requirements on one property, such as a mean and a minimum, is stated as several criteria that share a scope. diggs:CompositeAcceptanceCriterion states the requirement that a logical combination of other criteria holds; it is a program specification but does not substitute this head, because it has no operator or limit of its own.

<diggs:AbstractAcceptanceCriterion gml:id="" xmlns:diggs="http://diggsml.org/schemas/3" xmlns:gml="http://www.opengis.net/gml/3.2">
  <gml:description xlink:href="" nilReason="">{0,1}</gml:description>
  <gml:identifier codeSpace="">{0,1}</gml:identifier>
  <gml:name codeSpace="">{0,unbounded}</gml:name>
  <diggs:internalIdentifier codeSpace="">{0,1}</diggs:internalIdentifier>
  <diggs:status codeSpace="">{0,1}</diggs:status>
  <diggs:implementationStatus codeSpace="">{0,1}</diggs:implementationStatus>
  <diggs:associatedFile xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:associatedFile>
  <diggs:role>{0,unbounded}</diggs:role>
  <diggs:remark>{0,unbounded}</diggs:remark>
  <diggs:basedOnRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:basedOnRef>
  <diggs:basisRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:basisRef>
  <diggs:appliesToZone xlink:href="" nilReason="" owns="false">{0,1}</diggs:appliesToZone>
  <diggs:appliesToFeatureType codeSpace="">{0,1}</diggs:appliesToFeatureType>
  <diggs:statistic>{0,1}</diggs:statistic>
  <diggs:percentileValue>{0,1}</diggs:percentileValue>
  <diggs:statisticScope>{0,1}</diggs:statisticScope>
  <diggs:operator>{1,1}</diggs:operator>
  <diggs:limit>{1,1}</diggs:limit>
  <diggs:basis codeSpace="">{0,1}</diggs:basis>
  <diggs:baseLength howDetermined="" qualifier="" uom="">{0,1}</diggs:baseLength>
  <diggs:evidenceCondition>{0,unbounded}</diggs:evidenceCondition>
  <diggs:sourceSpecRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:sourceSpecRef>
  <diggs:partOfSpecificationRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:partOfSpecificationRef>
</diggs:AbstractAcceptanceCriterion>

Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods. This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.

<element abstract="true" name="AbstractAcceptanceCriterion" type="diggs:AbstractAcceptanceCriterionType" substitutionGroup="diggs:AbstractProgramSpecification"> <annotation> <documentation>Abstract head of the substitution group for acceptance criteria. A criterion states one testable requirement: what is measured, how the measurements are reduced to one value, the comparison applied and the limit compared against. As a program specification it also carries the scope of the features it governs and may specialize a more general criterion through basedOnRef. Its members differ in what is measured: diggs:PerformanceCriterion measures a physical property of the completed work, and diggs:DesignConformanceCriterion measures a geometric or constructional property against its design intent. Each names its subject through the parameterName of limit; use the DIGGS dictionary properties.xml for a performance criterion and designProperty.xml for a design conformance criterion. A specification that imposes several requirements on one property, such as a mean and a minimum, is stated as several criteria that share a scope. diggs:CompositeAcceptanceCriterion states the requirement that a logical combination of other criteria holds; it is a program specification but does not substitute this head, because it has no operator or limit of its own.</documentation> </annotation> </element>

Showing: