[typo] Atom exporting

Scott Laird scott at sigkill.org
Wed Aug 9 11:45:47 EDT 2006


The nice thing about XML specs like Atom is that you can trivially
extend them with namespaces.  The down side is that XML is a pain, and
namespaces are doubly painful.  At least they're easy to parse.


Scott

On 8/9/06, Alastair Rankine <arsptr at internode.on.net> wrote:
> I just read the APP spec and I couldn't see any discussion about raw
> vs cooked (as I like to call it) content.
>
> I think it is unlikely that they (APP spec writers) will add
> additional fields to the Atom entry document as alternative
> representations of the content, but hey that's just my guess.
>
> However it is pretty clear that APP builds upon Atom, and the
> additional functionality provided is not particularly relevant to the
> task of exporting blog content. For example the entries in a
> "collection" are retrieved as an Atom feed document, with only minor
> extensions: the paging extensions, which are largely irrelevant for
> our purposes, and the "publishing control" extensions, which look
> useful ("draft" status for entries).
>
> The point being that we probably don't need to wait for APP to be
> completed before starting work on blog exporting using Atom. Which is
> good, because I have almost finished a first draft proposal on this
> subject!
>
>
>
> On 09/08/2006, at 7:01 AM, Scott Laird wrote:
>
> > I don't remember seeing it when I read the spec last year, and Tim
> > Bray thought that filtering and formatting was a known problem when I
> > asked him a couple weeks ago.  It doesn't really make a difference in
> > this case, though-we're talking about serializing the whole blog to an
> > Atom-based XML file, which is kind of orthogonal to the Atom
> > Publishing Protocol.  I don't believe there's any standardized way to
> > handle comments and trackbacks via APP, so building a generic blog
> > sync tool via APP isn't really possible, either.
> >
> >
> > Scott
> >
> > On 8/8/06, Kevin Ballard <kevin at sb.org> wrote:
> >>
> >>
> >> I really should re-read it, but I'm pretty sure the Atom blog API
> >> stuff
> >> deals with getting the raw data out from the blog so you can edit
> >> it. And
> >> you can request more than just the last 10 or 15 posts or so - you
> >> can
> >> request chunks going back until the beginning.
> >>
> >> So I would hold of discussion on this until we can verify whether
> >> the Atom
> >> blog API does in fact do everything you want.
> >>
> >>
> >> On Aug 7, 2006, at 8:36 AM, Scott Laird wrote:
> >>
> >>
> >> 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.
> >>
> >> --
> >> Kevin Ballard
> >> http://kevin.sb.org
> >> kevin at sb.org
> >> http://www.tildesoft.com
> >> _______________________________________________
> >> Typo-list mailing list
> >> Typo-list at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/typo-list
> >>
> >>
> > _______________________________________________
> > Typo-list mailing list
> > Typo-list at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/typo-list
>
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>


More information about the Typo-list mailing list