An object that contains properites describing the characteristics of a batch of grout. This object optionally can reference a DesignGroutMix object defined within the GroutingProgram feature. A SPECIALIZATION OF diggs:DesignSample (DS1, 2026-09-27; previously a direct diggs:AbstractProgramDesign extension). A grout mix is a manufactured/produced sample: it inherits activityType (optional, but "aggregate" where stated - a grout mix is produced by blending constituents), plannedEquipment (a batching plant or mixer), and the generic plannedSampleWeight/Mass/Volume/Dimensions fields, none of which this type needs to restate. sampleScope, DesignSample's population/selection mechanism, is inherited but has no use here and is expected to stay absent - a manufactured sample has no source-feature or source-sample population to scope, per Dan's own framing of the design/build discussion this rebase came from - the type hierarchy makes that fall out naturally rather than needing a special case.
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 name="DesignGroutMix" substitutionGroup="diggs:DesignSample" type="diggs:DesignGroutMixType"><annotation><documentation>An object that contains properites describing the characteristics of a batch of grout. This object optionally can reference a DesignGroutMix object defined within the GroutingProgram feature. A SPECIALIZATION OF diggs:DesignSample (DS1, 2026-09-27; previously a direct diggs:AbstractProgramDesign extension). A grout mix is a manufactured/produced sample: it inherits activityType (optional, but "aggregate" where stated - a grout mix is produced by blending constituents), plannedEquipment (a batching plant or mixer), and the generic plannedSampleWeight/Mass/Volume/Dimensions fields, none of which this type needs to restate. sampleScope, DesignSample's population/selection mechanism, is inherited but has no use here and is expected to stay absent - a manufactured sample has no source-feature or source-sample population to scope, per Dan's own framing of the design/build discussion this rebase came from - the type hierarchy makes that fall out naturally rather than needing a special case.</documentation></annotation></element>