I have created a proof of concept PubSub browser which has turned into a dynamix XHTML journal generator and which can give a good prespective of what Buku on XMPP would be.
https://git.xmpp-it.net/sch/Rivista
Rivista (journal in the Italian language) is able to read PubSub node items that are compliant with the Atom Syndication Format (RFC 4287);
It means, that namely XEP-0277 and XEP-0472 are supported, which further means that the uploaded data must be confined to the elements that RFC 4287 provides.
Of course, there is the "rel" attribute which allows own customizations, yet I focus on the commom elements.
buku provides id, url, metadata (i.e. title), tags, desc (i.e. description) and flags.
This is how I was thinking of populating Atom entries with buku data:
| buku |
atom |
| url |
link |
| metadata |
title |
| tags |
category |
| desc |
content |
I am not sure yet how to handle the id, if needed.
Please advise.
I have created a proof of concept PubSub browser which has turned into a dynamix XHTML journal generator and which can give a good prespective of what Buku on XMPP would be.
https://git.xmpp-it.net/sch/Rivista
Rivista (journal in the Italian language) is able to read PubSub node items that are compliant with the Atom Syndication Format (RFC 4287);
It means, that namely XEP-0277 and XEP-0472 are supported, which further means that the uploaded data must be confined to the elements that RFC 4287 provides.
Of course, there is the "rel" attribute which allows own customizations, yet I focus on the commom elements.
buku provides
id,url,metadata(i.e. title),tags,desc(i.e. description) andflags.This is how I was thinking of populating Atom entries with buku data:
I am not sure yet how to handle the
id, if needed.Please advise.