[Standards-JIG] JEP-0163: payload type vs. namespace

Peter Saint-Andre stpeter at jabber.org
Tue Sep 12 18:31:20 UTC 2006

Peter Saint-Andre wrote:
> I'm a bit uncomfortable with principle #3 of JEP-0163 (PEP), which
> states that there is one node per namespace. I think it's more accurate
> to say that there is one node per payload type. This matters because we
> could potentially use the same namespace for different payload types.
> For example, the Atom format could be used for blog updates, new
> releases, and who knows what else. But then it seems that perhaps we
> need a registry of payload types?

Well, another option (for PEP only, not generic pubsub) is to wrap the
payload format (as we often do for x:data), for example:

<blog xmlns='http://jabber.org/protocol/blogging'>
  ... Atom content here ...

<news xmlns='http://jabber.org/protocol/news'>
  ... Atom content here ...


/me ponders


Peter Saint-Andre
Jabber Software Foundation

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060912/6b1a6137/attachment.bin>

More information about the Standards mailing list