[Standards] Call for Experience: XEP-0066: Out of Band Data

Christian Schudt christian.schudt at gmx.de
Tue Feb 25 21:53:46 UTC 2020


see my answers below.

> Am 25.02.2020 um 16:52 schrieb Jonas Schäfer (XSF Editor) <jonas at wielicki.name>:
> The XEP Editor would like to Call for Experience with XEP-0066 before
> presenting it to the Council for advancing it to Final status.
> During the Call for Experience, please answer the following questions:
> 1. What software has XEP-0066 implemented? Please note that the
> protocol must be implemented in at least two separate codebases (at
> least one of which must be free or open-source software) in order to
> advance from Draft to Final.

I’ve implemented in xmpp.rocks aka Babbler (Java XMPP library).

> 2. Have developers experienced any problems with the protocol as
> defined in XEP-0066? If so, please describe the problems and, if
> possible, suggested solutions.

Unfortunately I never really integrated it with SI File Transfer as written. Instead I’ve treated Example 1 as File Transfer Offer like in Example 8 and mapped the URL’s 'Content-Length' header to the „size“ attribute, the <url> element to the „name“ attribute and the OOB <desc> element to the SI <desc> element, hiding everything behind a generic interface.

That kind of works and now that XEP-0096 is deprecated I am even more wondering if this integration should be part of the specification.

> 3. Is the text of XEP-0066 clear and unambiguous? Are more examples
> needed? Is the conformance language (MAY/SHOULD/MUST) appropriate?
> Have developers found the text confusing at all? Please describe any
> suggestions you have for improving the text.

Although the specification is eventually relatively clear to work with URIs, it often mixes the terms „URL“ and „URI“, which even misled me to introduce a bug (software worked with URL only, not with URI):

It is confusing that the XML element is named „url“, but in fact it can contain URIs.

I suggest to be more clear in the text and only use „URI“, since the XML element name should not change.

Kind regards,

More information about the Standards mailing list