…sion of which [ISO8601:1988] formed the basis of the Internet Date/Time Format [RFC3339]. However, this format allows timestamps to contain very little additional relevant information. Beyond that, any contextual information related to a given timestamp needs to be either handled…

…version of which ISO8601:1988 formed the basis of the Internet Date/Time Format RFC3339 However, this format allows timestamps to contain very little additional relevant information. Beyond that, any contextual information related to a given timestamp needs to be either handled s…

…version of which ISO8601:1988 formed the basis of the Internet Date/Time Format RFC3339 However, this format allows timestamps to contain very little additional relevant information. Beyond that, any contextual information related to a given timestamp needs to be either handled s…

…mats Aug 18th. Please edit! Aug 18 15:16:14 <Tantek> DanC, what do you think of RFC3339? Aug 18 15:17:14 <Tantek> ISO8601 subset Aug 18 15:17:19 <DanC> Date and Time on the Internet: Timestamps http://www.ietf.org/rfc/rfc3339.txt Aug 18 15:17:30 <DanC> Klyne is a good guy. I wond…

…he server will consider this order invalid, encoded in the format specified in [RFC3339]. This field is REQUIRED for objects with "pending" or "valid" in the status field. identifiers (required, array of object): An array of identifier objects that the order pertains to. type (re…

…e server will consider this order invalid, encoded in the format specified in [ RFC3339 ]. This field is REQUIRED for objects with "pending" or "valid" in the status field. identifiers (required, array of object): An array of identifier objects that the order pertains to. type (r…

… MST" RFC1123Z = "Mon, 02 Jan 2006 15:04:05 -0700" // RFC1123 with numeric zone RFC3339 = "2006-01-02T15:04:05Z07:00" RFC3339Nano = "2006-01-02T15:04:05.999999999Z07:00" Kitchen = "3:04PM" // Handy time stamps. Stamp = "Jan _2 15:04:05" StampMilli = "Jan _2 15:04:05.000" StampMic…

…hose field-body contains a date value use the "full-date" format specified in [ RFC3339 ]. For example: "2004-06-28" represents June 28, 2004, in the Gregorian calendar. The first record in the file contains the single field whose field- name is "File-Date" (see Figure 3). The fi…

… zero” and insert “shall be preceded by two zeros in accordance with 4.6” " The RFC3339 grammar never allowed just one zero ("0") preceding the fraction and has always been compliant with ISO 8601/Cor 1:1991. ----- Note from the RFC authors ----- There are interpretations of ISO …

…ording to the Internet profiles of [ISO.8601-1] and [ISO.8601-2] as defined in [RFC3339]. It is RECOMMENDED that the value of this field be less than a year into the future to avoid staleness. This field MUST always be present and MUST NOT appear more than once. Expires: 2021-12-…

… expressed using dateTime it MUST be interpreted as date-time as specified in [ RFC3339 ]. Specifically, the timezone offset is not optional. Editor's note : dateTime vs. date-time We should update the ontology to only use date-time and RFC3339 and not this odd combination of dat…

…gth. For the Creation Time keyword, the date format SHOULD be in the RFC 3339 [ rfc3339 ] date-time format or in the date format defined in section 5.2.14 of RFC 1123 [ rfc1123 ]. The RFC3339 date-time format is preferred. The actual format of this field is undefined. The iTXt ch…

…该 在 Activity Streams 2.0 文档中使用相对 IRI（及 URL）引用。 2.3 日期与时间 所有带有日期值与时间值的属性 必须 符合 [ RFC3339 ] 中的 “date-time” 产生式，唯一例外是秒数 可以 省略。 必须 使用大写字母 “T” 分隔日期与时间，在没有数字时区偏移的情况下， 必须 使用大写字母 “Z”。 日期与时间使用以下 [ ABNF ] 语法描述进行规定。“time-hour”、“time-minute”、“time-second”、“time-secfrac”、“time-offset” 与 “full…

…gth. For the Creation Time keyword, the date format SHOULD be in the RFC 3339 [ rfc3339 ] date-time format or in the date format defined in section 5.2.14 of RFC 1123 [ rfc1123 ]. The RFC3339 date-time format is preferred. The actual format of this field is undefined. The iTXt ch…

…value 0 is for date/time strings that follow the standard format described in [ RFC3339 ], as refined by Section 3.3 of [RFC4287] Tag value 1 is for numerical representation of seconds relative to 1970-01-01T00:00Z in UTC time. (For the non-negative values that the Portable Opera…