Difference between revisions of "Date"

From BDI Data
Jump to: navigation, search
property / associated Property: Unformatted Value / qualifier
 +
Usage Notes: A text version (alphabetic mixed case and integer) of the date at which the unit identification event took place. This element is meant for use when the date is imprecise, ambiguous or not in a form that satisfies the standard structured date format. It can also be used when it is important to record the verbatim representation of the date or when dates to be recorded are not completely legible. (English)
property / associated Property: Unformatted Value / qualifier
 +
Usage Notes: For example the day and month may be decipherable but not the year; the use of this field will allow recording of partially interpreted information.This field can be used to record generalised date ranges and irresolvable ambiguity such as different day/month order conventions (e.g. US/Europe) or to allow for multiple dates and periods. (English)
property / associated Property: Unformatted Value / qualifier
 +
example (localized): January 21st, 1900 (English)
property / associated Property: Unformatted Value / qualifier
 +
example (localized): Autumn 1805 (English)
property / associated Property: Unformatted Value / qualifier
 +
example (localized): 17.05.192? (last digit indistinguishable, could be 5, 9 or 2) (English)
property / associated Property: Unformatted Value / qualifier
-
Usage Notes: A text version (alphabetic mixed case and integer) of the date at which the unit identification event took place. This element is meant for use when the date is imprecise, ambiguous or not in a form that satisfies the standard structured date format. It can also be used when it is important to record the verbatim representation of the date or when dates to be recorded are not completely legible. (British English)
 
property / associated Property: Unformatted Value / qualifier
-
Usage Notes: For example the day and month may be decipherable but not the year; the use of this field will allow recording of partially interpreted information.This field can be used to record generalised date ranges and irresolvable ambiguity such as different day/month order conventions (e.g. US/Europe) or to allow for multiple dates and periods. (British English)
 
property / associated Property: Unformatted Value / qualifier
-
example (localized): January 21st, 1900 (British English)
 
property / associated Property: Unformatted Value / qualifier
-
example (localized): Autumn 1805 (British English)
 
property / associated Property: Unformatted Value / qualifier
-
example (localized): 17.05.192? (last digit indistinguishable, could be 5, 9 or 2) (British English)
 

Revision as of 11:12, 23 October 2018

A class to describe dates, times and time spans in the Gregorian calendar.
In more languages
Configure
Language Label Description Also known as
English
Date
A class to describe dates, times and time spans in the Gregorian calendar.

    Statements

    0 references
    Date
    0 references
    0 references
    Verbatim Date
    A text version (alphabetic mixed case and integer) of the date at which the unit identification event took place. This element is meant for use when the date is imprecise, ambiguous or not in a form that satisfies the standard structured date format. It can also be used when it is important to record the verbatim representation of the date or when dates to be recorded are not completely legible. (English)
    For example the day and month may be decipherable but not the year; the use of this field will allow recording of partially interpreted information.This field can be used to record generalised date ranges and irresolvable ambiguity such as different day/month order conventions (e.g. US/Europe) or to allow for multiple dates and periods. (English)
    January 21st, 1900 (English)
    Autumn 1805 (English)
    17.05.192? (last digit indistinguishable, could be 5, 9 or 2) (English)
    0 references
    0 references
    0 references
    0 references
    0 references