[standards-jig] LAST CALL: Service Discovery (JEP-0030)

Nick nick at devzero.homelinux.com
Wed Feb 26 01:50:20 UTC 2003

I still feel "node" has not been fully addressed and is still 
ambigious. Right before example number 5 there is a statement about 
"may be associated" thats not strong enough. It should read something 
like this: "The requesting entity SHOULD NOT assume anything about the 
'node' only that it is a unique string/attribute to address non 
addressable things. Node semantics are left up to the implementor so 
long as the requesting entity follows the previous"

I understand the example shows one semantic, but those could very well 
be md5 hashes or random characters assigned to those items.

It needs to be made very clear, the jep does not impose/imply/dictate a 
node semantic and that the requesting entity should never assume 
anything about the node semantic.


Nicholas Perez
Email: 	nick at devzero.homelinux.com
Jabber:	nick at devzero.homelinux.com
Home:	303.759.0574

On 2003.02.25 18:23 Peter Saint-Andre wrote:
> Peter Millard has updated JEP-0030 with some small changes. In
> accordance
> with my message from 2 weeks ago [1], I believe it is time to issue a
> second and hopefully final Last Call for this spec. This Last Call
> will
> end on March 7, after which the Council shall vote. So get your
> comments
> in while you can. :)
> http://www.jabber.org/jeps/jep-0030.html
> Peter
> [1]
> http://mailman.jabber.org/pipermail/standards-jig/2003-February/002643.html
> --
> Peter Saint-Andre
> Jabber Software Foundation
> http://www.jabber.org/people/stpeter.php
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> http://mailman.jabber.org/listinfo/standards-jig

More information about the Standards mailing list