I haven't had time to look over the whole document yet, but I like
what I've seen so far. I have a few suggested changes :-).
First, I think the content body model is going to cause problems.
Here's how you're doing it now:
<export:contentsyntax
scheme="http://daringfireball.net/projects/markdown/";
label="Markdown"/>
<content type="text">I just wrote this *brilliant Java code*. Have a look!
public String getPaula() {
return paula;
}</content>
Can we change this to something like this:
<export:body type="http://daringfireball.net/projects/markdown/";
label="Markdown">I just wrote this *brilliant Java code*. Have a look!
public String getPaula() {
return paula;
}</export:content>
<content type="html">I just wrote this <em>brilliant Java
code</em>. Have a look!
public String getPaula() {
return paula;
}</content>
Basically, provide both the original format (for importers that
understand Markdown) and the processed format (for importers that
don't understand the original format).
Next, can you rename export:page to export:static or something
similar? I'd rather not be *too* Typo-specific :-).
Also, how does this represent things like:
- per-article trackback/comment open/closed?
- extended entries/excerpts/keywords
Scott
On 8/14/06, Alastair Rankine <[EMAIL PROTECTED]> wrote:
>
> Typographers,
>
> As promised, here is a proposal for the use of Atom as a blog export format:
>
> http://girtby.net/offerings/atomexport
>
> Note that there is nothing specific to Typo here (*), but I believe it
> should be implementable in Typo with minimal effort.
>
> Comments appreciated.
>
> (*) apart from shamelessly stealing the typosphere.org domain for the
> namespace, hopefully temporary.
> _______________________________________________
> Typo-list mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/typo-list
>
>
_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list
