Hi Peter and Kevin,

In the spirit of illustrating a generic solution that would suit this
specific question-and-answer pattern, I offer a simple example:

- Peter creates a node called "philosophy" where he publishes all
philosophical questions he has.
- Some friends subscribe to it.
- Kevin publishes an answer to whatever node better identifies the subject
(free tagging) AND the following metadata to the "commented" node:

<iq type='set' from='[EMAIL PROTECTED]' to='pubsub.kismith.co.uk' id='answer'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<publish node='commented'>
<item>
<commented>
<original jid='[EMAIL PROTECTED]' id='368866411b877c30064a5f62b917cffe'/>
<comment jid='[EMAIL PROTECTED]' id='ae890ac52d0df67ed7cfdf51b644e901'/>
</commented>
</item>
</publish>
</pubsub>
</iq>


This metadata associates Kevin's answer with Peter's question. Some other
special metadata/nodes are presented here:

http://iss.im/node/55

I need to work more on these, but as you can see, it's a generic
non-obtrusive solution built on top of PEP that suits well this
question-and-answer pattern.

Best regards,
Nick

P.S.: Peter, I'm still working on the ISS XEP. I'll keep you informed about
my progress.

P.S.2: Kevin, your expertise would be greatly appreciated, since it builds
up from your PEP work.


On Jan 30, 2008 2:16 PM, Peter Saint-Andre <[EMAIL PROTECTED]> wrote:

> Kevin Smith wrote:
>
> >> Perhaps I confused things by calling it "bleg". Qian called it
> "Q-and-A"
> >> before I changed the name to be more edgy.
> >
> > Well, my inclination is that if you're interested enough to answer,
> > you're probably interested enough to see how it 'turns out', and so
> > would want to see the notifications yourself. The spec as it is
> > probably only really covers the Q, and doesn't do much about the A :)
>
> Ah, I see. One way to handle that would be to make everyone (in your
> roster) a publisher at your bleg node. Another would be to publish the
> replies you receive.
>
> Peter
>
> --
> Peter Saint-Andre
> https://stpeter.im/
>
>

Reply via email to