84 | | * “OBJECT” provides the object to which the field belongs (if not the default authority object, i.e. SLICE for Slice Authority, MEMBER for Member Authority, Service for Registry) |
85 | | * “TYPE” may be one of “URN”, “UID”, “STRING”, “DATETIME”, “EMAIL”, “KEY”,“BOOLEAN”, “CREDENTIAL”, “CERTIFICATE”. [NB. This set of types subject to change. See Appendix for more information on these data types.] |
86 | | * “CREATE” attributes may be specified as “REQUIRED”, “ALLOWED” or “NOT ALLOWED” (default = “NOT ALLOWED”). These indicate whether the given supplementary field is required, allowed or prohibited in create calls. |
87 | | * "MATCH" attributes may be specified as TRUE or FALSE (default = TRUE). These indicate whether a given field may be specified in an match option of a lookup call. |
88 | | * “UPDATE” attributes may be specified as TRUE or FALSE (default = FALSE). These indicate whether the given field may be specified in an update call. |
89 | | * “PROTECT” attributes may be labeled as “PUBLIC”, “PRIVATE” or “IDENTIFYING”. These are for the Member Authority Only to differentiate between public, identifying and private data fields on members. |
| 83 | * “OBJECT” provides the object to which the field belongs (if not the default authority object, i.e. SLICE for Slice Authority, MEMBER for Member Authority, Service for Registry). This field is mandatory for any field listed. |
| 84 | * “TYPE” may be one of “URN”, “UID”, “STRING”, “DATETIME”, “EMAIL”, “KEY”,“BOOLEAN”, “CREDENTIAL”, “CERTIFICATE”. [NB. This set of types subject to change. See Appendix for more information on these data types.] This field is mandatory for any field listed. |
| 85 | * “CREATE” attributes may be specified as “REQUIRED”, “ALLOWED” or “NOT ALLOWED” (default = “NOT ALLOWED”). These indicate whether the given supplementary field is required, allowed or prohibited in create calls. This attribute is optional for listed fields. |
| 86 | * "MATCH" attributes may be specified as booleans TRUE or FALSE (default = TRUE). These indicate whether a given field may be specified in an match option of a lookup call. This attribute is optional for listed fields. |
| 87 | * “UPDATE” attributes may be specified as booleans TRUE or FALSE (default = FALSE). These indicate whether the given field may be specified in an update call. This attribute is optional for listed fields. |
| 88 | * “PROTECT” attributes may be labeled as “PUBLIC”, “PRIVATE” or “IDENTIFYING”. These are for the Member Authority Only to differentiate between public, identifying and private data fields on members. The default, if not provided, is "PUBLIC", and thus this attribute is optional. |
| 89 | |
| 90 | The FIELDS element of the get_version is optional for all services, as it only contains supplementary fields (which may not exist for a given service). |
447 | | || ''' Service ''' || ''' Description ''' || ''' Required ''' || |
448 | | || SLICE || Managing generation, renewal of slice credentials and slice lookup services || YES || |
449 | | || SLICE_MEMBER ||Defining and managing roles of members with respect to slices || NO || |
450 | | || SLIVER_INFO || Providing information about what Aggregates have reported having slivers for a given slice. Non-authoritative/advisory || NO || |
451 | | || PROJECT || Defining projects (groupings of slices) and project lookup services || NO || |
452 | | || PROJECT_MEMBER || Defining and managing roles of members with respect to projects || NO || |
| 450 | || ''' Service ''' || ''' Description ''' || ''' Required ''' || ''' Object ''' || |
| 451 | || SLICE || Managing generation, renewal of slice credentials and slice lookup services || YES || SLICE || |
| 452 | || SLICE_MEMBER ||Defining and managing roles of members with respect to slices || NO || || |
| 453 | || SLIVER_INFO || Providing information about what Aggregates have reported having slivers for a given slice. Non-authoritative/advisory || NO || SLIVER_INFO || |
| 454 | || PROJECT || Defining projects (groupings of slices) and project lookup services || NO || PROJECT || |
| 455 | || PROJECT_MEMBER || Defining and managing roles of members with respect to projects || NO || || |