[Standards-JIG] More pubsub questions

Peter Saint-Andre stpeter at jabber.org
Fri Feb 3 20:34:36 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matt Tucker wrote:
> Hello all,
> 
> First, the new pubsub draft is looking great. It's a lot clearer than
> the older versions. However, a few more questions about the spec:
> 
> 1) What error should we return when "Creating Nodes Associated with a
> Collection" and the provided nodeID of the parent node does not exist?
> Should we return an item-not-found error in this case?

Yes.

> 2) What error should we return if the specified parent node ID is a leaf
> node? Is a not_acceptable error correct?

Yes.

> 3) Should the pubsub#current_approver field be of type jid-multi since
> it can only contain JIDs?

Yes.

> 4) Field pubsub#title is present in "15.4.3 pubsub#node_config" and
> "15.4.4 pubsub#meta-data" forms. Is this correct?

Yes.

> 5) Some fields present in the pubsub#meta-data form can be automatically
> completed (e.g. pubsub#creator and pubsub#creation_date). However, other
> fields need to be manually configured. What is the proper way to set
> that information? IMHO, we could provide such information as part of the
> pubsub#node_config form. Maybe that's the reason why the field
> pubsub#title is present in both forms?

Ah yes, I meant to explain that more fully in the text somewhere. What
you describe is correct, I think.

I'll correct the JEP-in-progress to address these issues.

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD475bNF1RSzyt3NURAn/9AKCl/01rDeiOIfkcKhAmacY5K9ocVACg3v8O
38rkNDHaNB+B1kCe9iGzW8w=
=TNUS
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060203/a056dcb6/attachment.bin>


More information about the Standards mailing list