Browse Prior Art Database

Built-In Editing/Auditing of Input in Time Fields

IP.com Disclosure Number: IPCOM000099636D
Original Publication Date: 1990-Feb-01
Included in the Prior Art Database: 2005-Mar-15
Document File: 1 page(s) / 44K

Publishing Venue

IBM

Related People

Eisen, I: AUTHOR [+4]

Abstract

This article describes a facility for the built-in editing/auditing of time fields based on the cultural preference of the user. Any application which must support the input of user-given times will be able to function in a large number of countries and locations and support users that use different time zones and daylight savings rules and present the times for those rules in various forms and not have to worry about validation. All of the Editing and Auditing complexities are totally hidden from the application.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 78% of the total text.

Built-In Editing/Auditing of Input in Time Fields

       This article describes a facility for the built-in
editing/auditing of time fields based on the cultural preference of
the user. Any application which must support the input of user-given
times will be able to function in a large number of countries and
locations and support users that use different time zones and
daylight savings rules and present the times for those rules in
various forms and not have to worry about validation. All of the
Editing and Auditing complexities are totally hidden from the
application.

      A means to automatically validate a user input time to see that
the time is correct for the calendar chosen by the user is required.
For example, the time 13:59 am could be input by a user who prefers a
12-hour clock. This time is not valid in a 12-hour clock, so the user
should be notified of an error.  This concept can be extended to any
of the input fields and to the presentation of the time in any format
which the user has specified in any sequence (i.e., hour, minute,
second am/pm, time zone). The Editing/Auditing should be built into
the Time Control and take into account cultural preferences, such as
Calendar type (e.g., Gregorian, Islamic, Julian, etc.), Era
identifier (e.g., AD, Showa), start of year (e.g., January 1st, March
1st), weekstart, daystart, time zone, and daylight savings rule. The
user should be immediately notified of any errors found in the Time
field.

      The...