> Bastien <b...@altern.org> writes: >> In other words, we could then /apply/ org-mode >> on a document rather than transforming a document into an org >> document.
> What we may think about is a "Org readable exchange format (oref?)", > which would take the output of Nicolas' parser, export it in Org-mode > using some specific properties like "TAGS:" "TODO:" etc. I'm trying to get my head around what a 'readable exchange format' is. org-export.el already exports as an elisp list: M-: (setq my-org-buffer-as-elisp (org-element-parse-buffer)) RTE ... and it's pretty readable :-) So the basic idea is that you would export from an org file to an org file but one with a /different/ and maybe standardized format (highly standardized is the oref gist?). For example, anything that is content passes through as text and everything else (org guff) is put into a :PROPERTIES: :END: wrapper? > > > Maybe you can start working on a org-e-oref exporter, storying *all* > metadata into properties? ... Don't know where it will lead, but who > knows? A mission truly beyond my abilities, but how could I say no to such a meta org-mode process :-) Is the right place to start basically turning (org-element-parse-buffer) output back into an org buffer? Is this best thought of as another backend? I can't quite see why org-e-oref.el and not just org-e-org.el?
