[Standards-JIG] RE: [jdev] Call for Experience: JEP-0030 (Service Discovery)

Chris Mullins cmullins at winfessor.com
Mon Mar 22 22:06:25 UTC 2004

PSA Wrote:
> 1. Who has implemented JEP-0030?

I have implemented Disco in both the SoapBox SDK and in the SoapBox
Server 2004. 

> 2. Have implementers experienced any problems with the protocol as
> defined in JEP-0030?

I encountered significant confusion as to the different between Items
and Info. Every developer I have had to help implement Disco has had a
similar confusion. It is unclear, as to the differences between these
two, and when one should be preferred over the other. The relationship
between them is also unclear. 

I am not convinced that section 5, "Publication of Available Items"
belongs as part of this JEP. It seems to be an extension, rather than
part of the core protocol. What is the use-case that is driving this? 

On the whole, the JEP is excellent. It is well defined and has a good
number of examples.

Chris Mullins

-----Original Message-----
From: Peter Saint-Andre [mailto:stpeter at jabber.org] 
Sent: Monday, March 22, 2004 1:35 PM
To: standards-jig at jabber.org
Cc: jdev at jabber.org
Subject: [jdev] Call for Experience: JEP-0030 (Service Discovery)

As JEP Editor, I hereby issue a Call for Experience on JEP-0030
(Service Discovery). As defined in JEP-0001, the Call for Experience is
the last chance to provide feedback on a JEP before it advances from
Draft to Final. To help the Jabber Council decide whether JEP-0030 is
ready to advance to a status of Final, the JSF would like to gather the 
following information:

1. Who has implemented JEP-0030? I am aware of several client, server,
and component implementations, including jabberd 1.4.3, jabberd 2.0,
Exodus, and mu-conference. Further examples would be helpful.

2. Have implementers experienced any problems with the protocol as
defined in JEP-0030? If so, please describe the problems and, if
possible, suggested solutions.

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

If you have any comments on this JEP, please provide them within the
next 2 weeks (i.e., by April 5), at which time the Call for Experience
will end. After the Call for Experience, this JEP will if necessary 
undergo one more revision, after which it will be presented to the 
Jabber Council for voting to a status of Final.

You may review the JEP here:


Please send all feedback to <standards-jig at jabber.org>.

Thank you.


Peter Saint-Andre
Jabber Software Foundation

jdev mailing list
jdev at jabber.org

More information about the Standards mailing list