| ### Showing:
Diagrams
Source
Used by

Simple Type CombinedDateType

Namespace | http://metadata.dod.mil/mdr/ns/DDMS/3.0/
Diagram |
Type | union of(xs:dateTime, xs:date, xs:gYearMonth, xs:gYear)
Used by |
Attributes | DatesType/@created, DatesType/@infoCutOff, DatesType/@posted, DatesType/@validTil, irm:Dates/@irm:dateApproved, irm:Dates/@irm:dateReceived, irm:ProcessingInfo/@irm:dateProcessed
Source |
    <xs:simpleType name="CombinedDateType">
      <xs:annotation>
        <xs:appinfo>
          <mdr:definition>The type used to support the range of date representations.</mdr:definition>
          <mdr:comment>Recommended practice is that date be specified in one of the following formats: YYYYYYYY-MM YYYY-MM-DD YYYY-MM-DDThh:mmTZD YYYY-MM-DDThh:mm.ssTZD YYYY-MM-DDThh:mm:ss.sTZD Where:YYYY 0000 through current year MM 01 through 12 (month) DD 01 through 31 (day) hh 00 through 24 (hour) mm 00 through 59 (minute) ss 00 through 60 (second) .s .0 through 999 (fractional second) This profile suggests two ways of handling time zone offsets: 1. Times are expressed in UTC (Coordinated Universal Time), with a special UTC designator ("Z"). 2. Times are expressed in local time, together with a time zone offset in hours and minutes. A time zone offset of "+hh:mm" indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes ahead of UTC. A time zone offset of "-hh:mm" indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes behind UTC.</mdr:comment>
        </xs:appinfo>
      </xs:annotation>
      <xs:union memberTypes="xs:dateTime xs:date xs:gYearMonth xs:gYear"/>
    </xs:simpleType>
Schema location | DDMS-Globals.xsd