Changes between Version 3 and Version 4 of GAPI_AM_API_DRAFT/SpeaksFor

Timestamp:

04/30/13 12:23:15 (12 years ago)

Author:

Aaron Helsinger

Comment:

--

GAPI_AM_API_DRAFT/SpeaksFor

@@ -33 +33 @@
   - Tool names are case-insensitive internally, though they may be case-sensitive in display.
    - EG `JohnSmth` as a display name is `johnsmth` internally, and there cannot also be a user `JOHNSMTH`.
-  - Tool names should begin with a letter and be alphanumeric or underscore, hyphen, or period: (`'^[a-zA-Z][a-ZA-Z0-9\-_\.]\{0,31\}$'`).
+  - Tool names should begin with a letter and be alphanumeric or underscore, hyphen, or period: (`'^[a-zA-Z][a-ZA-Z0-9\-_\.]{0,31}$'`).
   - Tool names are limited to 32 characters.
   - Tool URNs (which contain the authority name and the tool instance name) are required to be temporally and globally unique.
 
-'''[FIXME: Must tool names be in the same namespace as user names? That is, do any AMs use the name part of the client URN in some way that cross both tools and users? Can we loosen these restrictions? That is, are some of these only because the user turns into a unix login name or something?]'''
+'''[FIXME: 32 characters? Right character restrictions?]'''
 
  - The tool email address should be a way to contact the administrators of the tool instance - the organization or individual who applied for the certificate and who stands behind its integrity.