Showing:

Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Element diggs:RigidInclusionProgram
Namespace http://diggsml.org/schemas/3
Annotations
 
A program of rigid inclusion ground improvement work: the designs the program
issues, the specifications it must satisfy, and the bases those were prepared from.
It has three generic slots (design, specification, basis) rather than one per kind
of design or specification, because the kind of object is carried by its own type
and substitution group. Document order is strictly all design elements, then all
specification elements, then all basis elements, not interleaved. This is an XSD
sequence constraint, not a logical one: a design's programSpecificationRef may point
at a specification declared later in the document, but every design element must
precede every specification element, and every specification element every basis
element, whichever cites which. An instance grouped by narrative instead, such as a
DesignMeasurement next to its own criterion, fails validation.
Diagram
Diagramgml3_2Profile_diggs_xsd_Attribute_gml_id.tmp#idgml3_2Profile_diggs_xsd_Element_gml_description.tmp#descriptiongml3_2Profile_diggs_xsd_Element_gml_descriptionReference.tmp#descriptionReferencegml3_2Profile_diggs_xsd_Element_gml_identifier.tmp#identifiergml3_2Profile_diggs_xsd_Element_gml_name.tmp#namegml3_2Profile_diggs_xsd_Element_Group_gml_StandardObjectProperties.tmp#StandardObjectPropertiesgml3_2Profile_diggs_xsd_Complex_Type_gml_AbstractGMLType.tmp#AbstractGMLTypegml3_2Profile_diggs_xsd_Complex_Type_gml_AbstractFeatureType.tmp#AbstractFeatureTypegml3_2Profile_diggs_xsd_Attribute_gml_id.tmp#idgml3_2Profile_diggs_xsd_Element_gml_description.tmp#descriptiongml3_2Profile_diggs_xsd_Element_gml_identifier.tmp#identifierAbstractTypes_xsd_Complex_Type_diggs_AbstractFeatureBaseType.tmp#AbstractFeatureBaseTypegml3_2Profile_diggs_xsd_Element_gml_name.tmp#nameCommon_xsd_Element_diggs_internalIdentifier.tmp#internalIdentifierCommon_xsd_Element_diggs_status.tmp#statusCommon_xsd_Element_diggs_implementationStatus.tmp#implementationStatusAbstractTypes_xsd_Complex_Type_diggs_AbstractFeatureType.tmp#http___diggsml.org_schemas_3_AbstractFeatureType_associatedFileAbstractTypes_xsd_Complex_Type_diggs_AbstractFeatureType.tmp#http___diggsml.org_schemas_3_AbstractFeatureType_roleAbstractTypes_xsd_Complex_Type_diggs_AbstractFeatureType.tmp#http___diggsml.org_schemas_3_AbstractFeatureType_remarkAbstractTypes_xsd_Complex_Type_diggs_AbstractFeatureType.tmp#http___diggsml.org_schemas_3_AbstractFeatureTypeCommon_xsd_Element_diggs_projectRef.tmp#projectRefAbstractTypes_xsd_Complex_Type_diggs_AbstractProgramType.tmp#AbstractProgramTypeRigidInclusions_xsd_Complex_Type_diggs_RigidInclusionProgramType.tmp#RigidInclusionProgramType_designRigidInclusions_xsd_Complex_Type_diggs_RigidInclusionProgramType.tmp#RigidInclusionProgramType_specificationRigidInclusions_xsd_Complex_Type_diggs_RigidInclusionProgramType.tmp#RigidInclusionProgramType_basisRigidInclusions_xsd_Complex_Type_diggs_RigidInclusionProgramType.tmp#RigidInclusionProgramTypeAbstractTypes_xsd_Element_diggs_AbstractProgram.tmp#AbstractProgram
Type diggs:RigidInclusionProgramType
Type hierarchy
Properties
content complex
Substitution Group Affiliation
Model
Children diggs:associatedFile, diggs:basis, diggs:design, diggs:implementationStatus, diggs:internalIdentifier, diggs:projectRef, diggs:remark, diggs:role, diggs:specification, diggs:status, gml:description, gml:identifier, gml:name
Instance
 
<diggs:RigidInclusionProgram 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:projectRef xlink:href="" identifierRef="" nilReason="" owns="false">{1,unbounded}</diggs:projectRef>
  <diggs:design>{0,unbounded}</diggs:design>
  <diggs:specification>{0,unbounded}</diggs:specification>
  <diggs:basis>{0,unbounded}</diggs:basis>
</diggs:RigidInclusionProgram>
Attributes
QName Type Use Annotation
gml:id ID required 
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.
Source
 
<element name="RigidInclusionProgram" type="diggs:RigidInclusionProgramType" substitutionGroup="diggs:AbstractProgram">
  <annotation>
    <documentation>A program of rigid inclusion ground improvement work: the designs the program issues, the specifications it must satisfy, and the bases those were prepared from. It has three generic slots (design, specification, basis) rather than one per kind of design or specification, because the kind of object is carried by its own type and substitution group. Document order is strictly all design elements, then all specification elements, then all basis elements, not interleaved. This is an XSD sequence constraint, not a logical one: a design's programSpecificationRef may point at a specification declared later in the document, but every design element must precede every specification element, and every specification element every basis element, whichever cites which. An instance grouped by narrative instead, such as a DesignMeasurement next to its own criterion, fails validation.</documentation>
  </annotation>
</element>
XML Schema documentation generated by ® XML Editor.