Le 05/09/2013 22:36, Alexander Gnauck a écrit :
I like this idea. I would do it in a similar way than groups in the
roster. This would allow multiple tags on each bookmark, and also
hierarchical with a separator in the tag name.
sample:
<storage xmlns='storage:bookmarks'>
<conference name='Council of Oberon'
autojoin='true'
jid='[email protected]
<mailto:[email protected]>'>
<nick>Puck</nick>
<tags>
<tag>A</tag>
<tag>B</tag>
<tag>A:B nested under A</tag>
</tags>
</conference>
</storage>
Alex
we can also define this in a separate extension and namespace.
--
Alexander Gnauck
http://www.ag-software.de
xmpp:[email protected] <mailto:xmpp%[email protected]>
On Wed, Sep 4, 2013 at 6:34 AM, Jaussoin Timothée <[email protected]
<mailto:[email protected]>> wrote:
Le 22/08/2013 09:23, Jaussoin Timothée a écrit :
Le 19/08/2013 11:24, Jaussoin Timothée a écrit :
Le 15/08/2013 22:09, Jaussoin Timothée a écrit :
Le 15/08/2013 19:47, Peter Saint-Andre a écrit :
On 8/15/13 2:26 AM, Jaussoin Timothée wrote:
I have implemented the Bookmarks XEP
(http://xmpp.org/extensions/xep-0048.html) in
Movim (http://movim.eu/)
to store the conferences, URL and subscribed
Pubsub feeds of the user.
Maybe it can be a great idea to add a
"category" tag with some "default"
categories like news, blog, nsfw... With this
kind of feature I'll be
able to tag more precisely the Pubsub items
and maybe add special
behaviours one some of them (like hide by
default the content of the
nsfw items or display in priority the news items).
In general, tagging is a good thing. :-)
Do you propose that we add a 'tag' attribute to
both the <url/> element
and the <conference/> element? Would it contain a
space-separated list
of tags?
Peter
Hi !
I've also added a specific element to bookmark the
pubsub nodes, this way :
<pubsub xmlns="http://jabber.org/protocol/pubsub";>
<items node="storage:bookmarks">
<item id="current">
<storage xmlns="storage:bookmarks">
<conference jid="[email protected]
<mailto:[email protected]>" autojoin="1"
name="Movim">
<nick>edhelas</nick>
</conference>
<subscription
xmlns="urn:xmpp:pubsub:subscription:0" subid=""
node="BouletCorp" server="pubsub.movim.eu
<http://pubsub.movim.eu>">
<title/>
</subscription>
<subscription
xmlns="urn:xmpp:pubsub:subscription:0" subid=""
node="CerealesMatin" server="pubsub.movim.eu
<http://pubsub.movim.eu>">
<title/>
</subscription>
<subscription
xmlns="urn:xmpp:pubsub:subscription:0" subid=""
node="Chez_Kek" server="pubsub.movim.eu
<http://pubsub.movim.eu>">
<title/>
</subscription>
<subscription
xmlns="urn:xmpp:pubsub:subscription:0" subid=""
node="JournalDuGeek" server="pubsub.movim.eu
<http://pubsub.movim.eu>">
<title/>
</subscription>
<subscription
xmlns="urn:xmpp:pubsub:subscription:0" subid=""
node="LinuxFr" server="pubsub.movim.eu
<http://pubsub.movim.eu>">
<title/>
</subscription>
</storage>
</item>
</items>
</pubsub>
We can maybe re-use the same tag system than for the
atom elements :
<conference jid="[email protected]
<mailto:[email protected]>" autojoin="1"
name="Movim">
<nick>edhelas</nick>
<category term="Movim"/>
<category term="XMPP"/>
<category term="Jabber"/>
</conference>
It's just an idea :)
Hi !
I also think that allow subscriptions tags in Bookmarks
can be a great thing. For the moment we don't have any way
to list all the subscribed nodes on the user account.
Using <tag/> can be great too ;)
Tim
Hi everyone !
I really need your feedback on this thing to update the XEP.
edhelas
Hi !
I've made my modifications on the XEP, if you have some feedbacks
don't hesitate.
I'm not very sure of this syntax for the Bookmark Pubsub
subscription element :
<subscription xmlns="urn:xmpp:pubsub:subscription:0"
name="My family party"
server="pubsub.shakespeare.lit" node="party">
<title>Party at the Capulets</title>
</subscription>
Maybe we can merge the title and the name elements (here 'title'
is the officiel Pubsub node title, and 'name' is a personnal one).
edhelas
Yeah maybe creating a more general namespace can be interresting, I'd
love to tag bookmarks and also pubsub nodes the same way I can tag atom
elements :)
Our project is nowaday handling hundrer of posts/user/day so I definitly
need to have something to "manage" all theses contents.
edhelas
