See comments inline.
> > > > Sorry for not being clear and thanks for your time. I
> > want to know the
> > > > meaning of *token. Appendix defines what is token, which itself
> > > > containts multiple characters since it is 1*(.......).So, how does
> > > > *token make sense?
> > > >
> > > > If *token is correct, what would be the separator between two
> > > > consequetive tokens? If there is no separator, what is the
> > > > use of *token
> > > > because the definition of the token would suffice.
> > > >
> > >
> > > 1* of the token definition means there is
> > > at least one.
> > >
> > > The display-name definition *token basically
> > > just cancels the "at least one" part of the
> > > token definition.
> >
> >
> > Isn't it so that *token is 0 or more tokens separated with
> > LWS. This would
> > make Foo Bar a legal display-name.
>
> The definition of the *rule does not indicate
> that the elements are separated by LWS.
But what about the last sentences from "C summary of Augmented BNF" in
bis03:
"The grammar described by this specification is word-based. Except where
noted otherwise, linear white
space (LWS) can be included between any two adjacent words (token or
quoted-string), and between
adjacent tokens and separators, without changing the interpretation of a
field. At least one delimiter (LWS
and/or separators) MUST exist between any two tokens (for the definition of
"token" below), since they
would otherwise be interpreted as a single token. Note that URLs do NOT
contain LWS."
Doesn't this imply that there MUSTbe at least 1 delimeter between the tokens
that arise from the expression *token.
Whouldn't this make Foo Bar a legal display-name?
Christian Jansson
www.hotsip.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
