[wp-hackers] Atom Export format

[Robin Adrianse]

I agree. If there was one XML-style import/export format, the world would be
a better place [not really, but still].

It lets users choose their blogging system, whereas some people I know stick
with MT because they don't want to go through all the "hassle" of importing
everything to a better platform, such as WordPress or Textpattern. No need
for "proprietary" formats, I deal with that enough with WMV and so on...

On 10/1/06, Alastair Rankine <arsptr at internode.on.net> wrote:
>
> On 29/09/2006, at 3:55 AM, Roland Haeder wrote:
>
> > Ah, I guess I missed the point here: Export format means that you
> > download the
> > output and upload it somewhere else?
>
> Exactly. The somewhere else would typically be the unspecified killer
> blogging engine of the future.
>
> Implementing this now benefits all blogging engines because it
> reduces the barrier to adoption. Users know they can trust their
> content to a system that supports a documented export format because
> they know they are not going to get locked in. I tried to explain
> this in the introduction to my document, which in case you've
> forgotten is at http://girtby.net/offerings/atomexport :)
>
> >> I think it's worth moving toward Atom, since it solves several
> >> issues with
> >> RSS (no namespace, lots of random extensions, no central place to
> >> discover
> >> extensions, horrible parenting, etc.).
> > So many good reasons to change over. :-) I don't know ATOM but I
> > believe in
> > your words that this is true.
>
> Yes although I should point out that you don't have to support Atom
> syndication in order to support my Atom export proposal.
>
> One of the advantages of using an Atom-based protocol is that there
> is the potential for code-sharing between syndication feed generation
> and content export. But there is no strict dependency.
>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>