15 Feb
2026
15 Feb
'26
12:54 a.m.
Greetings.
XEP-0277 is meant to deliver RFC 4287 (Atom format) over XMPP.
However, as with Atom Activity Stream, only elements "atom:entry" are
delivered.
So, elements "atom:subtitle" and "atom:logo" of element
"atom:feed" are
neglected.
Could we utilize element "pubsub:items" to store that missing data of
element "atom:feed"?
<items node='urn:xmpp:microblog:0'
title='The Journal of Romeo'
subtitle='Of the affairs of the Capulet and Montague families.'
logo='http://montague.lit/logo.svg'>
Regards,
Schimon
15 Feb
15 Feb
3:40 a.m.
Hi,
No, you can't add random attributes like this in any XMPP protocol element and expect
it to work.
For storing feed meta data on nodes, there are two options:
1. Having a special item to hold it. See section 5 of XEP-0277.
2. Add meta data on the pubsub node's configuration. Some fields already exist to
cover information from the feed level meta data. If there's no direct match, you can
use Clark Notation to namespace custom fields (see XEP-0068).
I also want to call out a special mention of a deferred XEP to store XML in a form field,
which references the exact use case: XEP-0315.
--
ralphm
On 15 February 2026 08:54:36 CET, Schimon Jehudah <sch(a)fedora.email> wrote:
Greetings.
XEP-0277 is meant to deliver RFC 4287 (Atom format) over XMPP.
However, as with Atom Activity Stream, only elements "atom:entry" are
delivered.
So, elements "atom:subtitle" and "atom:logo" of element
"atom:feed" are
neglected.
Could we utilize element "pubsub:items" to store that missing data of
element "atom:feed"?
<items node='urn:xmpp:microblog:0'
title='The Journal of Romeo'
subtitle='Of the affairs of the Capulet and Montague families.'
logo='http://montague.lit/logo.svg'>
Regards,
Schimon
_______________________________________________
Standards mailing list -- standards(a)xmpp.org
To unsubscribe send an email to standards-leave(a)xmpp.org
9:42 a.m.
Thank you for this explanation.
Much appreciated!
Schimon
On Sun, 15 Feb 2026 11:40:14 +0100
Ralph Meijer <ralphm(a)ik.nu> wrote:
Hi,
No, you can't add random attributes like this in any XMPP protocol
element and expect it to work.
For storing feed meta data on nodes, there are two options:
1. Having a special item to hold it. See section 5 of XEP-0277.
2. Add meta data on the pubsub node's configuration. Some fields
already exist to cover information from the feed level meta data. If
there's no direct match, you can use Clark Notation to namespace
custom fields (see XEP-0068).
I also want to call out a special mention of a deferred XEP to store
XML in a form field, which references the exact use case: XEP-0315.
2
days inactive
2
days old
2 comments
2 participants
participants (2)
-
Ralph Meijer -
Schimon Jehudah