[typo] Atom exporting
scott at sigkill.org
Mon Aug 7 11:36:05 EDT 2006
I'd love to see an Atom-based blog export/import standard. Does
anyone know any of the WP guys?
It seems to me that the rational thing to do would be to have a "pure"
Atom feed, including HTML for each entry, and then add an 'export'
namespace and use tags like '<export:description>' to include the
original markup, as well as other fields that don't map into standard
Atom (comments open, trackbacks, etc). I'm not sure if static
content, comments, and trackbacks would be better as more entries with
a special type flag or as their own tag.
I suspect that we could get a few prominent non-Typo XML people
involved in this pretty quickly, if we can sit down and produce a
first draft of the standard.
On 8/7/06, Alastair Rankine <arsptr at internode.on.net> wrote:
> On 06/08/2006, at 4:24 PM, Kevin Ballard wrote:
> > Actually, we have atom exporting already (I assume by exporting you
> > mean
> > a feed).
> Actually, I meant more than just a feed.
> I don't know about anyone else, but I find it a lot easier to put my
> data somewhere that I know I will be able to get it out again. This
> applies especially for web applications hosted by third-parties,
> where export facilities are a must before I'll even look at it, but I
> believe it is generally a good practice. The ability to export is
> something that is missing from Typo. You can get your data out again,
> but it's in the database schema du jour.
> Hence the motivation for an export facility for Typo. This is an
> escape hatch, if you will, for migration to an unspecified future
> blogging platform.
> At present there is no common interchange format for blog content.
> The closest we get is Atom, and I'm not even sure whether that is
> entirely suitable for representing all of the interesting content of
> a blog. Anyway I think it's worth having a crack at it.
> Unlike the current Atom feed, the Atom export facility would:
> a) include a complete archive, that is all of the articles, pages,
> comments, trackbacks, etc in the blog
> b) use the 'raw' formatting (eg markdown) instead of HTML
> c) probably ignore attachments (unless someone has a better idea?)
> On Scott's blog I mentioned the possibility that this could be
> expanded to fill the role of a backup/restore format, and he was
> fairly sure he wanted these to be completely separate. Which seems
> Typo-list mailing list
> Typo-list at rubyforge.org
More information about the Typo-list