Schema documentation for component diggs:RIProgramBasis

The site-wide basis a rigid inclusion program's designs were prepared from: the governing standards, design method, arching model, safety format, working life and consequence class that make every other design value in the program interpretable. A design cites it through basisRef, parallel to how diggs:DesignRITreatedArea is cited through basedOnRef. It does not carry supportedStructureType, which is on diggs:DesignRILTPType: what a platform supports is not one fact for the whole program (a substation with nine differently loaded zones under one basis, say).

<diggs:RIProgramBasis 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:designWorkingLife howDetermined="" qualifier="" uom="">{0,1}</diggs:designWorkingLife>
  <diggs:consequenceClass codeSpace="">{0,1}</diggs:consequenceClass>
  <diggs:seismicHazard>{0,1}</diggs:seismicHazard>
  <diggs:basisParameter>{0,unbounded}</diggs:basisParameter>
  <diggs:groundModelRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,unbounded}</diggs:groundModelRef>
  <diggs:governingStandard xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:governingStandard>
  <diggs:analysisApproach>{0,1}</diggs:analysisApproach>
  <diggs:designMethod codeSpace="">{0,1}</diggs:designMethod>
  <diggs:archingModel codeSpace="">{0,1}</diggs:archingModel>
  <diggs:safetyFormat codeSpace="">{0,1}</diggs:safetyFormat>
  <diggs:exposureClassification codeSpace="">{0,unbounded}</diggs:exposureClassification>
  <diggs:factor>{0,unbounded}</diggs:factor>
</diggs:RIProgramBasis>

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 name="RIProgramBasis" type="diggs:RIProgramBasisType" substitutionGroup="diggs:AbstractProgramBasis"> <annotation> <documentation>The site-wide basis a rigid inclusion program's designs were prepared from: the governing standards, design method, arching model, safety format, working life and consequence class that make every other design value in the program interpretable. A design cites it through basisRef, parallel to how diggs:DesignRITreatedArea is cited through basedOnRef. It does not carry supportedStructureType, which is on diggs:DesignRILTPType: what a platform supports is not one fact for the whole program (a substation with nine differently loaded zones under one basis, say).</documentation> </annotation> </element>

Showing: