Re: [apps-discuss] APPSDIR review of draft-gregorio-uritemplate-07

["Murray S. Kucherawy" <[e-mail]>]

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of Mark Nottingham
> Sent: Wednesday, December 07, 2011 1:08 AM
> To: Jiankang YAO
> Cc: [e-mail]; IETF Apps Discuss
> Subject: Re: [apps-discuss] APPSDIR review of draft-gregorio-uritemplate-07
> 
> > 1) In section 1.5.  Notational Conventions
> >
> > There is a repetition of definition of ALPHA, DIGIT, HEXDIG,......
> >
> > There is a discussion in IETF: we should not give the repetition of
> > definition of ABNF syntax if we can refer it to other documents. The
> > reason is that repetition may bring the errors or misunderstanding.
> >
> > Suggestion: for example, we just say "ALPHA, DIGIT are imported from
> > RFC5234" instead of repeating
> > "ALPHA          =  %x41-5A / %x61-7A   ; A-Z / a-z"
> 
> Is this a discussion that's already taken place?

I agree that re-stating definitions that are better replaced by references to them is the wiser move.

> > Discussion issues:
> > 1)No IANA actions are required by this document.
> >
> > comments or suggestions:I suggest something in the document to be
> > added to IANA, for example,the operators in section 2 and 3 of this
> > document.
> > If we register these operators in IANA, it will help the future use
> > of these operators/characters.

I don't think this is necessary.  The point of registries is to make something extensible without having to modify its defining document, such as adding header fields to email or MIME types, etc.  In this case, declaring a character as an operator that's not already an operator can alter the semantics of existing templates based on the initial RFC.  So if the set of operators is to change, I suggest that a new RFC would be required, obsoleting previous ones.

-MSK