Abstract head of the substitution group for program specifications: the requirementsa program issues, such as tolerances, acceptance limits and performance criteria,each carrying the scope of features over which it applies. A realized featuredeclares which specifications govern it through diggs:programSpecificationRef, and adesign declares which it was prepared to satisfy through the same property. Not tobe confused with diggs:Specification. A program specification is a feature head: itsmembers are independently identified, referenceable features that state requirementsand, as program modules, carry scope and basedOnRef. diggs:Specification is acomponent object, a procedure that cites a published standard(standardReferenceNumber, standardTitle, standardVersion and so on) and states norequirement of its own. A program specification commonly cites a diggs:Specificationfor the test method by which conformance is measured; the two are complementary.
Database handle for the object. It is of XML type ID, so is constrained to beunique in the XML document within which it occurs. An external identifier for the object inthe form of a URI may be constructed using standard XML and XPointer methods. This is doneby concatenating the URI for the document, a fragment separator, and the value of the idattribute.
Source
<element abstract="true" name="AbstractProgramSpecification" type="diggs:AbstractProgramSpecificationType" substitutionGroup="diggs:AbstractProgramModule"><annotation><documentation>Abstract head of the substitution group for program specifications: the requirements a program issues, such as tolerances, acceptance limits and performance criteria, each carrying the scope of features over which it applies. A realized feature declares which specifications govern it through diggs:programSpecificationRef, and a design declares which it was prepared to satisfy through the same property. Not to be confused with diggs:Specification. A program specification is a feature head: its members are independently identified, referenceable features that state requirements and, as program modules, carry scope and basedOnRef. diggs:Specification is a component object, a procedure that cites a published standard (standardReferenceNumber, standardTitle, standardVersion and so on) and states no requirement of its own. A program specification commonly cites a diggs:Specification for the test method by which conformance is measured; the two are complementary.</documentation></annotation></element>