[Standards-JIG] JEP for storing annotations

Stefan Strigler steve at zeank.in-berlin.de
Fri Oct 1 09:28:53 UTC 2004


Am Fr, den 01.10.2004 schrieb Trejkaz Xaoza um 11:12:
> On Fri, 1 Oct 2004 01:34, Rottenberg, Hal wrote:
> > I don't see any glaring technical issues not already mentioned.  I would
> > like to second the author in saying that there is no reason to constrain
> > this to contacts.  I would certainly see the benefit in perhaps
> > annotating a unique or complex transport (Jogger for example?) by adding
> > usage notes or a link to its homepage.
> 
> That's an interesting idea.  I agree that this can apply to all roster items 
> (the only reason to detach it from the roster itself would just be that your 
> client doesn't always want to pull down the annotations.)

The JEP itself doesn't restrict usage on roster items. Perhaps I should
point this out more clearly.

> But you know what would also be good... being able to send these annotations 
> from user to user, the same way roster items are traded.  Then you could do 
> things like sending another user more information about how to use a 
> transport, which could be handy for support type roles as well.

That sounds like sending it as a message ...

> Another thought... we're really talking about a metadata overlay here, where 
> information from the user overlays the information from the actual entity.  
> Whatever we do here might be good to plan for being more than simple strings.

I'd like to call it more a supplement then an overlay. Could you show an
example for a use case you're thinking about?

-Steve





More information about the Standards mailing list