To avoid confusion between the name of the temporalCoverage element and the name of the specified time period, the latter is referred to as the "time period name".
If not "Not Applicable" or "Unknown", date formats must adhere to one of the DDMS-allowed date formats.
{@table.header History}Before DDMS 4.0.1, a temporalCoverage element contains a locally defined TimePeriod construct. This TimePeriod construct is a container for the name, start, and end values of a time period. It exists only inside of a ddms:temporalCoverage parent, so it is not implemented as a Java object. Starting in DDMS 4.0.1, the TimePeriod wrapper has been removed.
Starting in DDMS 4.1, the start and end dates may optionally be replaced by an approximableStart or approximableEnd date.
{@table.footer}{@table.header Nested Elements}{@child.info ddms:name|0..1|11111}{@child.info ddms:start|0..1|11111} {@child.info ddms:end|0..1|11111} {@child.info ddms:approximableStart|0..1|00011}{@child.info ddms:approximableEnd|0..1|00011} {@table.footer}{@table.header Attributes}{@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 If set, ddms:start must adhere to a valid date format.|Error|11111}{@ddms.rule If set, ddms:end must adhere to a valid date format.|Error|11111}{@ddms.rule Approximable dates must not be used before the DDMS version in which they were introduced.|Error|11111}{@ddms.rule Security attributes must not be used before the DDMS version in which they were introduced.|Error|11111}{@ddms.rule An empty ddms:name will be given a default value.|Warning|11111}{@ddms.rule Approximable dates may cause issues for DDMS 4.0.1 systems.|Warning|00010}{@table.footer} @author Brian Uri! @since 0.9.b | |