Changes between Version 35 and Version 36 of UniformClearinghouseAPIV2


Ignore:
Timestamp:
01/28/14 14:21:13 (6 years ago)
Author:
mbrinn@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UniformClearinghouseAPIV2

    v35 v36  
    898898
    899899|| ''' Type ''' || ''' Description ''' || ''' Format ''' ||
    900 || URN || Standard GENI identifier, guaranteed to be unique across all GENI services and authorities at a given time, but may be reused by obsolete/expired objects (e.g. slices) || '''Example:''' urn:publicid:IDN+mych+user+abrown ''' Details: ''' urn:publicid:IDN+AUTHORITY+TYPE+NAME where AUTHORITY is the unique fully qualified identifier of the authority creating the URN (e.g. ch.geni.net), TYPE is the type of entity (e.g. slice, user, tool, project) and name is the unique name of the entity (e.g. slice_name, user_name, tool_name, project_name) ||
    901 || UID || Unique identifier within the scope of a single authority, not guaranteed to be unique across authorities || '''Example:''' 8e405a75-3ff7-4288-bfa5-111552fa53ce '''Details:''' Varies by implementation but the python UUID4 standard is a good example. ||
     900|| URN || Standard GENI identifier, guaranteed to be unique across all GENI services and authorities at a given time, but may be reused by obsolete/expired objects (e.g. slices) || '''Example:''' urn:publicid:IDN+mych+user+abrown ''' Details: ''' urn:publicid:IDN+AUTHORITY+TYPE+NAME where AUTHORITY is the unique fully qualified identifier of the authority creating the URN (e.g. ch.geni.net), TYPE is the type of entity (e.g. slice, user, tool, project) and name is the unique name of the entity (e.g. slice_name, user_name, tool_name, project_name). See  http://groups.geni.net/geni/wiki/GeniApiIdentifiers  for data type definitions. ||
     901|| UID || Unique identifier within the scope of a single authority, not guaranteed to be unique across authorities || '''Example:''' 8e405a75-3ff7-4288-bfa5-111552fa53ce '''Details:''' Varies by implementation but the python UUID4 standard is a good example.  See RFC4122 standard http://www.ietf.org/rfc/rfc4122.txt ||
    902902|| STRING || Generic UTF-8 string ||  ||
    903903|| INTEGER || Generic integer argument || ||
    904904|| DATETIME || Date time in RFC3339 format || '''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 ||
    905 || EMAIL || Well-formed email address || '''Example:''' jbrown@geni.net ||
     905|| EMAIL || Well-formed email address compliant with RFC2822 http://tools.ietf.org/html/rfc2822#section-3.4.1 || '''Example:''' jbrown@geni.net ||
    906906|| KEY || SSH or SSL public or private key (contents, not filename) || Key-specific format ||
    907 || BOOLEAN || XMLRPC boolean || '''Example:''' True ||
    908 || CREDENTIALS || List of dictionaries, one per credential, tagged with credential type and version (as indicated in the GENI AM API specification) || '''Details:''' Credentials = [ { geni_type: <string, case insensitive>, geni_version: <string containing an integer>, geni_value : <credential as string>, <others> } ] ||
    909 || CERTIFICATE || X509 certificate (contents, not filename) || Standard X509 PEM certificate format. A chain of such certificates may be concatenated. ||
     907|| BOOLEAN || XMLRPC encoded boolean || '''Example:''' True ||
     908|| CREDENTIALS || List of dictionaries, one per credential, tagged with credential type and version (as indicated in the GENI AM API specification) || '''Details:''' Credentials = [ { geni_type: <string, case insensitive>, geni_version: <string containing an integer>, geni_value : <credential as string>, <others> } ]. See http://groups.geni.net/geni/wiki/GAPI_AM_API_V3/CommonConcepts#credentials or http://groups.geni.net/geni/wiki/GeniApiCertificates for credential format and semantic specification. ||
     909|| CERTIFICATE || X509 v3 certificate (contents, not filename) || Standard X509 v3 PEM certificate format. A chain of such certificates may be concatenated.  See  http://en.wikipedia.org/wiki/X.509 and http://groups.geni.net/geni/wiki/GeniApiCertificates for more details ||
    910910
    911911As noted above, this list is subject to change as the API develops over time.