Re: Request for a formal URN Namespace ID for "globus"

[Stuart Martin <[e-mail]>]

Hi Dale and all,

Are there any more reviews coming?  We (Globus) would like to start using these Globus URNs in an upcoming software release and would like to prevent a future change to them if possible.

Thanks,
Stu

> On Jan 11, 2016, at 4:03 PM, Stuart Martin <[e-mail]> wrote:
> 
> Hi Dale,
> 
> In the new “01” version (https://www.ietf.org/id/draft-martin-urn-globus-01.txt <https://www.ietf.org/id/draft-martin-urn-globus-01.txt>), I changed the following based on your input:
> 
> 1) Remove the space from “urn: “ to be “urn:"
> 2) "SUBNAMESPACE-SPECIFIC-STRING” to "subnamespace-specific-string
> 3)
>     a. <non-colon char> to <non-colon-char>
>     b. <non-colon trans> and <non-colon other> to be <non-colon-trans> and <non-colon-other>
> 
> Thanks for the feedback.  Let me know if any other changes are needed.
> 
> -Stu
> 
>> On Jan 11, 2016, at 2:19 PM, Dale R. Worley <[e-mail] <mailto:[e-mail]>> wrote:
>> 
>> I have some nits:
>> 
>>   2.4. Declaration of the Syntactic Structure
>> 
>>   <URN> ::= "urn: " "globus" ":" <NSS>
>> ------------------^
>> 
>> Remove this space.
>> 
>>   <NSS> ::= <SNID> | <SNID> ":" <SUBNAMESPACE-SPECIFIC-STRING>
>> 
>> You might want to change "SUBNAMESPACE-SPECIFIC-STRING" to
>> "subnamespace-specific-string" or "SNSS".
>> 
>>   <SNID> ::= 1*<non-colon chars>
>> 
>>   <SUBNAMESPACE-SPECIFIC-STRING> ::= 1*<URN chars>
>> 
>>   <non-colon chars> ::= <non-colon trans> | "%" <hex> <hex>
>> 
>>   <non-colon trans> ::= <upper> | <lower> | <number> | <non-colon
>>   other>
>> 
>>   <non-colon other> ::= "(" | ")" | "+" | "," | "-" | "." | "=" |
>>                         "@" | ";" | "$" | "_" | "!" | "*" | "'"
>> 
>> IMO, "<non-colon chars>" should be "<non-colon-chars>", etc.  (Though I
>> admit that RFC 2141 uses "<URN chars>".)
>> 
>> Dale
>