Before DDMS 4.0.1, a geospatialCoverage element contains a nested GeospatialExtent element. Because DDMS does not decorate this element with any special attributes, it is not implemented as a Java object. Starting in DDMS 4.0.1, the GeospatialExtent wrapper has been removed.
The introduction of TSPI deprecated the boundingBox and verticalExtent components in DDMS 5.0.
{@table.footer}{@table.header Nested Elements}{@child.info ddms:geographicIdentifier|0..1|11111}{@child.info ddms:boundingBox|0..1|11110}{@child.info ddms:boundingGeometry|0..1|11111}{@child.info ddms:postalAddress|0..1|11111}{@child.info ddms:verticalExtent|0..1|11110}{@table.footer}{@table.header Attributes}{@child.info ddms:precedence|0..1|00011}{@child.info ddms:order|0..1|00011}{@child.info ism:<securityAttributes>|0..*|01111}{@table.footer}{@table.header Validation Rules}{@ddms.rule The qualified name of this element must be correct.|Error|11111}{@ddms.rule This component must contain at least 1 child element.|Error|11111}{@ddms.rule Only 1 of each type of child element must be used.|Error|11111}{@ddms.rule If a ddms:geographicIdentifier is used and contains a ddms:facilityIdentifier, no other child elements must be used.|Error|11111}{@ddms.rule ddms:order must not be used before the DDMS version in which it was introduced.|Error|11111}{@ddms.rule ddms:precedence must not be used before the DDMS version in which it was introduced.|Error|11111}{@ddms.rule If set, ddms:precedence must be a valid token.|Error|11111}{@ddms.rule If ddms:precedence exists, this component must contain a ddms:geographicIdentifier with a ddms:countryCode.|Error|11111}{@ddms.rule Security attributes must not be used before the DDMS version in which they were introduced.|Error|11111}Does not validate the value of the order attribute (this is done at the Resource level).
{@table.footer} @author Brian Uri! @since 0.9.b | |