[Standards] adding body as RECOMMENDED field for PEP-protocols?

Mon Jun 18 02:35:21 CDT 2007

On Jun 14, 2007, at 8:45 PM, Mridul Muralidharan wrote:

> You are right, application payloads getting sent (as messages)  
> should, imo, not contain <body /> unless it expects to communicate  
> that to the user.
> In a lot of cases for pep typically, it would be consumed by the  
> client to appropriately add meta-data for the contact - it just  
> would not make sense to show the plain text info to user.
>
> That being said, we should not preclude addition of body, it might  
> make sense for usecases (maybe where pep is more used like pubsub  
> with infrequent updates ?)

A body inside the namespace for the particular PEP node is perfectly  
fine, if it makes sense for that namespace.  If a client doesn't know  
about that namespace, it's not going to add the +notify capability,  
nor subscribe to the node directly, so the notification should never  
come to a client that doesn't know how to process it; "process" here  
may mean just pull out the body element in the appropriate namespace  
and display it in some interesting way.

-- 
Joe Hildebrand