Changes between Version 74 and Version 75 of GAPI_AM_API_DRAFT

Timestamp:

09/24/12 16:28:42 (12 years ago)

Author:

Aaron Helsinger

Comment:

--

GAPI_AM_API_DRAFT

@@ -137 +137 @@
   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.
 
-This change would allow an aggregate to explicitly specify that arguments and returns should be treated as unicode. By default, aggregates are expected to use the ASCII only regular expressions that the rest of this API specification uses, and to limit returns to ASCII characters where possible. This change would add an optional return from `GetVersion` that allows an aggregate to specify that all returns must be handled as unicode. Specifically, this change adds `geni_unicode_compliant` to the return from `GetVersion`. 
+This change would allow an aggregate to explicitly specify that arguments may be unicode, and returns may be unicode if the content demands it. By default, aggregates are expected to use the ASCII only regular expressions that the rest of this API specification uses, and to limit returns to ASCII characters where possible. This change would add an optional return from `GetVersion` that allows an aggregate to specify that unicode arguments are acceptable (ASCII strings must still be accepted), and that all returns may be unicode. When the aggregate specifies this option, it shall still attempt to support ASCII inputs to allow clients to operate only in ASCII where possible. Specifically, this change adds `geni_unicode_compliant` to the return from `GetVersion`. 
  - This field is optional.
  - Default is `false`. All strings specified in this API are to be treated as ASCII unless otherwise specified, (e.g. the format explicitly references a standard that supports unicode). This includes both arguments and returns.
- - When `true`, all strings specified in this API are to be treated as unicode. In particular, regular expressions that limit to ASCII characters shall be interpreted to include the unicode equivalents.
+ - When `true`, all strings specified in this API may be unicode. In particular, regular expressions that limit to ASCII characters shall be interpreted to include the unicode equivalents. The aggregate will still accept ASCII input. Returns will remain ASCII where the API defines ASCII constants or content allows it.
 
 == Older Proposals ==