Changes between Version 6 and Version 7 of GeniApiIdentifiers
- Timestamp:
- 07/13/12 11:14:01 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeniApiIdentifiers
v6 v7 3 3 = GENI API Identifiers = 4 4 5 GENI identifies objects (be it a researcher, resource, clearinghouse, or aggregate manager) with a [http://en.wikipedia.org/wiki/Uniform_Resource_Name Uniform Resource Name (URN)]. ''' The format of a GENI URN is: urn:publicid:IDN+<authority string>+<type>+<name>.''' The format is adapted from the [http://www.protogeni.net/trac/protogeni/wiki/URNs ProtoGENI URN format] and the [http://testglobalnoc.grnoc.iu.edu/gmoc/file-bin/urn-proposal3.pdf GMOC GENI URN proposal]. All sections of the URN are mandatory. Note that additional '+' characters are allowed in the <name> section. 5 GENI identifies objects (be it a researcher, resource, clearinghouse, or aggregate manager) with a [http://en.wikipedia.org/wiki/Uniform_Resource_Name Uniform Resource Name (URN)]. 6 7 ''' The format of a GENI URN is''': `urn:publicid:IDN+<authority string>+<type>+<name>` 8 9 The GENI URN format is adapted from the [http://www.protogeni.net/trac/protogeni/wiki/URNs ProtoGENI URN format] and the [http://testglobalnoc.grnoc.iu.edu/gmoc/file-bin/urn-proposal3.pdf GMOC GENI URN proposal]. All sections of the URN are mandatory. Note that additional '+' characters are allowed in the `<name>` section. 6 10 7 11 === Public Identifiers === … … 10 14 The public identifier section of a GENI URN must begin with "IDN ". When transcribed, this means that all GENI URNs begin with "urn:publicid:IDN+". 11 15 12 To transcribe a public ID to a URN use the following rules :16 To transcribe a public ID to a URN use the following rules, from RFC 3151: 13 17 14 18 || From || Transcribe to || … … 35 39 36 40 37 Formally, the URNformat follows the following naming convention (in perl regular expression syntax for the encoding string):41 Formally, the public ID format follows the following naming convention (in perl regular expression syntax for the encoding string): 38 42 `“IDN [toplevelauthority][\/\/sub-authority]* resource-type resource-name”` 39 43 40 This would lead to the following urnschema in the public id namespace (Using the transformation in [http://www.faqs.org/rfcs/rfc3151.html RFC 3151] :44 This would lead to the following URN schema in the public id namespace (Using the transformation in [http://www.faqs.org/rfcs/rfc3151.html RFC 3151] : 41 45 `“urn:publicid:IDN+toplevelauthority[:sub-authority]*\+resource-type\+resource-name”` 42 46 … … 79 83 80 84 === Type === 81 The <type> string has not yet been completely specified, but is used to identify the kind of resource being identified. Many APIs require use of URNs with particular types. Use the defined types below, unless they simply do not fit for you. In which case, please contact the GPOto inform them of your new type.85 The <type> string has not yet been completely specified, but is used to identify the kind of resource being identified. Many APIs require use of URNs with particular types. Use the defined types below, unless they simply do not fit for you. In which case, please [mailto:help@geni.net contact the GPO] to inform them of your new type. 82 86 83 87 `authority` … … 113 117 114 118 '''Sliver''': 115 - URN should be unique over time within an AM for record-keeping / operations purposes.119 - Sliver URN should be unique over time within an AM for record-keeping / operations purposes. 116 120 - Format: `urn:publicid:IDN+<AM name>+sliver+<sliver name>` 117 121 - Sliver names … … 122 126 - Usernames are case-insensitive internally, though they may be case-sensitive in display. 123 127 - EG !JohnSmth as a display name is johnsmth internally, and there cannot also be a user `JOHNSMTH`. 124 - Usernames should begin with a letter and be alphanumeric or underscores -no hyphen or '.': `('^[a-zA-Z][\w]\{1,8\}$')`.128 - Usernames should begin with a letter and be alphanumeric or underscores; no hyphen or '.': `('^[a-zA-Z][\w]\{1,8\}$')`. 125 129 - Usernames are limited to 8 characters. 126 130 - User URNs (which contain the authority name and the username) are required to be temporally and globally unique.