DDMS 4.1: New abstract base class, AbstractApproximableDate, and concrete implementations.

Description

(Imported from Google Code)
This class represents the base type which allows an approximate date.

Class: buri.ddmsence.ddms.AbstractApproximableDate

Constraints:

  • Can have an optional "description" element (0-to-1, xs:string)

  • Can have an optional "approximableDate" element (0-to-1, CombinedDateType with optional "approximation" attribute)

  • Can have an optional "searchableDate" element (0-to-1) containing a "start" and "end" CombinedDateType

  • "approximation" attribute can hold values from the enumeration [1st qtr, 2nd qtr, 3rd qtr, 4th qtr, circa, early, mid, late]

Implementers:
buri.ddmsence.ddms.resource.Dates
buri.ddmsence.ddms.summary.TemporalCoverage

Activity

Show:

Brian Uri August 29, 2012 at 12:35 AM

Complete in Rev 762.

The class ended up being a final class (ApproximableDate) rather than an abstract. In DDMS, every implementation of this type is a locally-defined element, so there was no need to have an abstract class underneath.

Brian Uri August 27, 2012 at 4:17 PM

<xs:complexType name="ApproximableDateType">
<xs:all>
<xs:element name="description" type="xs:string" minOccurs="0" />
<xs:element name="approximableDate" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="CombinedDateType">
<xs:attribute name="approximation" type="DateApproximationEnumerationType" />
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="searchableDate" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="start" type="CombinedDateType" />
<xs:element name="end" type="CombinedDateType" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:all>
</xs:complexType>

Fixed

Assignee

Reporter

Fix versions

Priority

Created June 12, 2012 at 12:46 PM
Updated April 5, 2015 at 2:25 PM
Resolved April 5, 2015 at 2:25 PM