Changes between Version 116 and Version 117 of GAPI_AM_API_DRAFT
- Timestamp:
- 03/27/14 12:39:13 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GAPI_AM_API_DRAFT
v116 v117 295 295 * The value is a list of strings, of length at least one. It should generally be a list of length 1. Aggregates of aggregates may list multiple types. 296 296 * Legal characters: alphanumeric 297 * Values should be one of the defined GENI AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. (As of this proposal, one of `orca`, `foam`, `protogeni`, `sfa` . More GENI AM types may be added in the future.)297 * Values should be one of the defined GENI AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. (As of this proposal, one of `orca`, `foam`, `protogeni`, `sfa`, `dcn`. More GENI AM types may be added in the future.) 298 298 299 299 === Change Set N3: Use consistent types and prefixes === … … 312 312 * The value is a string. 313 313 * Legal characters: alphanumeric 314 * Values should be one of the defined GENI AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. (As of this proposal, one of `orca`, `foam`, `protogeni`, `sfa` . More GENI AM types may be added in the future.)314 * Values should be one of the defined GENI AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. (As of this proposal, one of `orca`, `foam`, `protogeni`, `sfa`, `dcn`. More GENI AM types may be added in the future.) 315 315 316 316 Aggregate specific options and return attributes should be named with a prefix denoting the aggregate type. It should be the same as the `am_type` and `geni_am_type` for this aggregate. Therefore, character restrictions are: 317 317 * The value is a string. 318 318 * Legal characters: alphanumeric 319 * Values should be one of the defined GENI AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. (As of this proposal, one of `orca`, `foam`, `protogeni`, `sfa` . More GENI AM types may be added in the future.)319 * Values should be one of the defined GENI AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. (As of this proposal, one of `orca`, `foam`, `protogeni`, `sfa`, `dcn`. More GENI AM types may be added in the future.) 320 320 321 321 For example: ProtoGENI includes an AM-specific status in the v2 API return from `SliverStatus` called `pg_status`. By this proposal, that attribute should be renamed `protogeni_status`. … … 359 359 Many values defined by this API appear to be limited to ASCII characters - both arguments and returns. We would like to support internationalization. Some values in this API (e.g. those defined as URLs) implicitly support unicode. Currently, a well behaved aggregate should be able to handle unicode values in at least some arguments. Similarly, a well behaved client should be able to handle unicode returns. 360 360 361 ''This change set was discussed and deferred at GEC19''. We do not yet have sufficient motivation, and the irare questions about this proposal.361 ''This change set was discussed and deferred at GEC19''. We do not yet have sufficient motivation, and there are questions about this proposal. 362 362 363 363 This change would clarify the support for internationalization in this API, and allow aggregates to specify unicode support. This change should not require any clients or aggregates to make changes. This change would specify: