Application module: Date time ISO/TS 10303-1010:2014-02(E)
© ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
    3.1 Terms and definitions
    3.2 Abbreviated terms

4 Information requirements
   4.1 ARM type definitions
   4.2 ARM entity definitions
5 Module interpreted model
   5.1 Mapping specification
   5.2 MIM EXPRESS short listing

A MIM short names
B Information object registration
C ARM EXPRESS-G   EXPRESS-G
D MIM EXPRESS-G   EXPRESS-G
E Computer interpretable listings
F Application module implementation and usage guide
G Change history
Bibliography
Index

Annex F
(informative)

Application module implementation and usage guide

This clause describes usages of this module.

The MIM entity calendar_date provides the capability to represent a date in the Gregorian Calendar.

EXAMPLE 1   The date of February 10, 1999 can be represented as follows:

#1=CALENDAR_DATE(1999,10,2);

The MIM entity date_and_time provides the capability to represent a date in the Gregorian Calendar and a point in time in that day.

EXAMPLE 2   The following instances represent the date of February 10, 1999 with a time of 11:10 PM in the Japanese time zone:

#1=DATE_AND_TIME(#2,#3);
#2=CALENDAR_DATE(1999,10,2);
#3=LOCAL_TIME(23,10,$,#4);
#4=COORDINATED_UNIVERSAL_TIME_OFFSET(9,$,.AHEAD.);

EXAMPLE 3   The following instances represent the date of February 10, 1999 with a time of 11:10 PM in Newfoundland, Canada:

#1=DATE_AND_TIME(#2,#3);
#2=CALENDAR_DATE(1999,10,2);
#3=LOCAL_TIME(23,10,$,#4);
#4=COORDINATED_UNIVERSAL_TIME_OFFSET(3,30,.BEHIND.);

Pre-processor Recommendations: All pre-processors should use noon in the originating time zone as a default for local_time when time information is unavailable.



© ISO 2014 — All rights reserved