Changes between Version 72 and Version 73 of GAPI_AM_API_DRAFT


Ignore:
Timestamp:
09/20/12 12:53:15 (7 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GAPI_AM_API_DRAFT

    v72 v73  
    115115Various fields in the AM API specification are defined only as strings, without explicit limits on legal characters. This makes it awkward to pass these values to and from scripts. In particular, many fields should only be alphanumeric, plus some limited number of separator characters.
    116116
    117 Note that in general, where this API says 'alphanumeric' or explicitly identifies `a-zA-Z`, we would ''like'' to expand this to non-ASCII letters, to support internationalization - making these into unicode strings. Therefore, aggregates are encouraged to support non-ASCII letters as input. However, this change set does not require that aggregates support non-ASCII inputs, and aggregates should not require clients to accept non-ASCII results where the API does not explicitly require it.
     117Note that in general, where this API says 'alphanumeric' or explicitly identifies `a-zA-Z`, we would ''like'' to expand this to non-ASCII letters, to support internationalization - making these into unicode strings. Therefore, aggregates are encouraged to support non-ASCII letters as input. Clients are encouraged to support non-ASCII returns from aggregates. However, this change set does not require that either aggregates or clients support non-ASCII strings, and aggregates should not require clients to accept non-ASCII results where the API does not explicitly require it.
    118118
    119119This change set proposes constraining several options/return values that are currently defined only as 'string'.