On Mon Mar 16 12:09:46 2009, Dirk Meyer wrote:
> Section 3, Example 5: That's not EBNF, could you change it to the
> correct syntax, so there is no room for interpretation?
It is not? OK, I will fix it. It should have been EBNF :)
No, it should be ABNF, and (to me) it looks like it. It's slightly
wrong, the chunk-size in the examples is given as decimal, which is
sensible, but it's hex in the ABNF. (Actually HEX, which is
presumably meant to be HEXDIG from RFC 5234)
I would still change the syntax, though, so that last-chunk includes
the data, and so that no leading zeros are used except for the zero
case.
This gives two productions changed, plus one added, and a couple of
missing ones:
stream = *(chunk | last-chunk)
chunk = chunk-size id CRLF chunk-data CRLF
digit-nonzero = %x31-39 ; "1"-"9"
chunk-size = digit-nonzero *DIGIT
id = Name
last-chunk = "0" id CRLF CRLF
;; Conforms to chunk
;; Remainder are INFORMATIVE ABNF renditions of W3C's REC-xml11 TR.
Name = NameStartChar *NameChar
NameChar = NameStartChar / "-" / "." / DIGIT / %xB7 / %x0300-036F /
%x203F-2040
NameStartChar = ":" / ALPHA / "_" / %xC0-D6 / %xD8-F6 / %xF8-2FF /
%x370-37D /
%x37F-1FFF / %x200C-200D / %x2070-218F
/ %x2C00-2FEF /
%x3001-D7FF / %xF900-FDCF / %xFDF0-FFFD
/ %x10000-EFFFF
> On a higher level, I think that's a great idea :) Could be hell
for
> some client implementations, though, due to the asynchronicity
(you
> have to buffer the parts of the stanza you already know, and
collect
> the rest before passing it to the upper layers).
Yes, maybe restrict the usage to a stanza and not allow it inside a
stanza by default. So a client MAY send any return from any XEP out
of
band, but only the whole result. If out of band is allowed
somewehere
deep inside a stanza it SHOULD be added to the XEP defining that
namespace.
I think for BoB usage, then references are okay, since that's already
expected.
Dave
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
