| ### Showing:
Annotations
Diagrams
Source
Used by

Simple Type irm:CombinedDateType

Namespace | urn:us:gov:ic:irm
Annotations | ? The type used to support the range of date representations. Recommended practice is that date be specified in one of the following formats: YYYY YYYY-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) TZD = time zone designator (Z or +hh:mm or -hh:mm) 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.
Diagram |
Type | union of(xsd:dateTime, irm:DateHourMinType , xsd:date, xsd:gYearMonth, xsd:gYear)
Used by |
Elements | AnalyticType/eventEntity/endDate , AnalyticType/eventEntity/startDate , AnalyticType/financialTransactionEntity/date , AnalyticType/travelEntity/arrivalDateTime , AnalyticType/travelEntity/departureDateTime , DeviceImageType/dateImaged , FirmwareType/actualDateAndTime , FirmwareType/biosDateAndTime , ImageDetailsType/dateTimeOriginal , RelationshipType/endDate , RelationshipType/startDate , TranslationDetailsType/dateRequired , TranslationDetailsType/requestDate , TranslationDetailsType/translationDate , entityCommonElements/creationDate , entityCommonElements/lastModifiedDate , file/dateAccessed , file/dateAndTimeOfLastModification , file/dateCreated , file/dateModified , file/entryDate , irm:ApproximableDateType/irm:approximableDate , irm:ApproximableDateType/irm:searchableDate/irm:end , irm:ApproximableDateType/irm:searchableDate/irm:start
Attributes | irm:DatesType/@irm:approvedOn , irm:DatesType/@irm:created , irm:DatesType/@irm:infoCutOff , irm:DatesType/@irm:posted , irm:DatesType/@irm:receivedOn , irm:DatesType/@irm:validTil , irm:ProcessingInfoType/@irm:dateProcessed
Source |
    <xsd:simpleType name="CombinedDateType">
      <xsd:annotation>
        <xsd:documentation>&#x2028;
          <p xmlns="http://www.w3.org/1999/xhtml" ism:ownerProducer="USA" ism:classification="U">The type used to support the range of date representations. Recommended practice is that date be specified in one of the following formats: YYYY YYYY-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) TZD = time zone designator (Z or +hh:mm or -hh:mm) 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.</p>
        </xsd:documentation>
      </xsd:annotation>
      <xsd:union memberTypes="xsd:dateTime irm:DateHourMinType xsd:date xsd:gYearMonth xsd:gYear"/>
    </xsd:simpleType>
Schema location | IC-IRM.xsd Copy and paste this link to your file browser, clicking the link MAY open in the browser. Opening in an XML aware editor is best.

## This document has been approved for Public Release by the Office of the Director of National Intelligence. See Distribution Notice for details. Click Here