Changes between Version 38 and Version 39 of UniformClearinghouseAPIV2
- Timestamp:
- 02/20/14 10:57:09 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UniformClearinghouseAPIV2
v38 v39 902 902 || STRING || Generic UTF-8 string || || 903 903 || INTEGER || Generic integer argument || || 904 || DATETIME || Date time in RFC3339 format (http://tools.ietf.org/html/rfc3339) || '''Examples:''' 2013-06-15 02:39:08.25+0300 2013-06-15 02:39:08-05:00 '''Details:''' Timezone offset must be specified. Format: YYYY-MM-dd HH-mm-<seconds><timezone> where <seconds> may include decimal (to millisecond granularity) and <timezone> may be +HH:mm or -HH:mm||904 || DATETIME || String representing a date/time in RFC3339 format (http://tools.ietf.org/html/rfc3339). || '''Examples:''' 2013-06-15T02:39:08+03:00, 2013-06-15T02:39:08-05:00, 2014-02-23T11:00:05Z '''Details''': DATETIME values in the Federation API will be strings in RFC3339-compliant format. We recommend that implementers use parsers that fully implement this format. However, due to the flexibility in the spec and different interpretations chosen by different common parsers, we further recommend that such DATETIME values: 1) contain an uppercase T between the time and date portions, 2) contain a timezone suffix, either an uppercase Z (for UTC) or +/-HH:MM, and 3) do not contain fractional seconds.|| 905 905 || EMAIL || Well-formed email address compliant with RFC2822 http://tools.ietf.org/html/rfc2822#section-3.4.1 || '''Example:''' jbrown@geni.net || 906 906 || KEY || SSH or SSL public or private key (contents, not filename) || Key-specific format ||