Understanding the extended Markdown some outliners use

[scripting]

I understand that some outliners use an extended form of Markdown to save their outlines.

I'm interested in knowing exactly what this format is, because -- if it's easy to support as an export and import format in Drummer, then I want to do it. But first we have to understand what it is.

A good first step would be to do this:

1. Find an outliner that supports OPML import, whose native file format is Markdown.

2. Import our states.opml example into this app.

3. Save/export it as Markdown.

4. Post it here as a comment.

Why use states.opml? Because we know what's "content" and what's structure in the example. When I get an example where the text is about the format it's an example of, it gets confusing quickly. I know "Montana" and "Chicago" aren't part of the file structure. See how that works?

Everyone but silo-builders wins if our products interop.

[sabre23t]

Imported states.opml into Logseq.com v0.3.7 It's converted into states.opml.md attached. states.opml.md

Edit: I just tried re-downloading the above states.opml.md. It did download ok. It's a 815 byte file. Cut&paste as source here.

[scripting]

OK -- I've reviewed @sabre23t upload.

1. First, thanks! 👍

2. Noted that the only head-level attribute that is preserved is <title>. There are quite a few others.

3. I will come up with a better test, where the individual headlines have attributes. Coming in a minute. I will update the post at the top of the thread.

[scripting]

Here's the next test, the OPML source behind the opml.org home page.

http://opml.org/?format=opml

This is a better test because every headline has a created attribute. Let's see what they do with those.

[sabre23t]

2. Noted that the only head-level attribute that is preserved is