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

[Joe Hildebrand]

Another option in your Atom example is to use a more semantic- 
describing namespace rather than a syntactic-describing namespace.   
http://jabber.org/protocol/blog, http://jabber.org/protocol/releases,  
etc., all of which contain items in Atom format.

On Sep 12, 2006, at 2:31 PM, Peter Saint-Andre wrote:

> 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 ...
> </blog>
>
> <news xmlns='http://jabber.org/protocol/news'>
>   ... Atom content here ...
> </news>
>
> Etc.
>
> /me ponders
>
> Peter
>
> -- 
> Peter Saint-Andre
> Jabber Software Foundation
> http://www.jabber.org/people/stpeter.shtml
>