[jdev] jabber.org not conforming to JEP standards

[Trejkaz]

On Mon, 8 Aug 2005 07:50, Tomasz Sterna wrote:
> 2005/8/7, Chris Chen <ckchris at idream.net>:
> > According to JEP-0078's jabber:iq:auth schema, there should only be 4
> > child elements to the query -- username, password, digest, and
> > resource, in that order.
>
> Please notice, that all JEP schemas are informative, not normative.
>
> JEP-0078 3.1 states that the only REQUIRED fields are username and the
> resource. Nothing in the JEP forbids adding more fields there. It would
> work against the eXtensibility of the protocol Enhancement.

I think it would be good if JEPs would explicitly note the places where things 
can be extended.  Otherwise, people have a hard time distinguishing the 
places where extensions are useful (e.g. inside jabber:iq:auth query) from 
the places where extensions are a problem (e.g. jabber:iq:roster item.)

The schemas would be the place to do this if only they were normative.  But 
since they're not, perhaps JEPs need to be checked so that they all name the 
places where extensions make sense, or alternatively, so that they forbid 
them where they don't make sense. :-/

TX


-- 
             Email: Trejkaz Xaoza <trejkaz at trypticon.org>
          Web site: http://trypticon.org/
         Jabber ID: trejkaz at jabber.zim.net.au
   GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F  A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20050808/a9c5b49e/attachment-0002.pgp>