From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ilya Shlyakhter <ilya_shl@alum.mit.edu>
Subject: Re: suggestion: "native" orgmode XML export (and import?)
Date: Sun, 9 Aug 2009 16:14:39 +0200
Message-ID: <4b11f87e0908090714u4df77408y851ed46551697e5b@mail.gmail.com>
References: <4b11f87e0908060754o7601aeb1uf9b8cebf44c29a24@mail.gmail.com>
	<1f38ae890908061457m7350ecfdw566e7ce9adc6f06e@mail.gmail.com>
	<1f38ae890908061458kc3d71fci7f944ae03c2400e@mail.gmail.com>
	<4b11f87e0908062305ue685293m633213469c47d0e8@mail.gmail.com>
	<1f38ae890908070213x1fabc9e3o75db945d9f86b2fa@mail.gmail.com>
	<4b11f87e0908070246rc21ec59k99b0f6ddaac84be3@mail.gmail.com>
	<87fxc2g8kn.fsf@bzg.ath.cx>
	<4b11f87e0908081325h6d3ec469id91fcdb739f5a201@mail.gmail.com>
	<28c656e20908090619r3ee89747we76b6d540b68cf95@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ma9AZ-0005y1-Da
	for emacs-orgmode@gnu.org; Sun, 09 Aug 2009 10:14:43 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ma9AX-0005xp-0L
	for emacs-orgmode@gnu.org; Sun, 09 Aug 2009 10:14:42 -0400
Received: from [199.232.76.173] (port=40720 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ma9AW-0005xm-QI
	for emacs-orgmode@gnu.org; Sun, 09 Aug 2009 10:14:40 -0400
Received: from ey-out-1920.google.com ([74.125.78.150]:10028)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <ilya239@gmail.com>) id 1Ma9AW-0000tM-BI
	for emacs-orgmode@gnu.org; Sun, 09 Aug 2009 10:14:40 -0400
Received: by ey-out-1920.google.com with SMTP id 5so824169eyb.24
	for <emacs-orgmode@gnu.org>; Sun, 09 Aug 2009 07:14:39 -0700 (PDT)
In-Reply-To: <28c656e20908090619r3ee89747we76b6d540b68cf95@mail.gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: B Smith-Mannschott <bsmith.occs@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>

> Out of curiosity, how would you want to handle textual content? Pass
> it through unchanged with org's wiki-like markup in tact, or somehow
> xml-ified?:
>
> *foo* --> *foo*
> *foo* --> <strong>foo</strong>

Probably the latter, since converting XMLified content to wiki markup
(or any other form) is easy and does not require manual parsing, while
the other direction is harder.
But for a first version, just leaving the markup as text would be fine too.

What would help a lot is, if XML content could be imported as a subtree.
Then you could have "python plugins" that take a subtree (or an entire orgf=
ile)
converted to XML, process it into updated XML, and then that updated
XML gets imported
back into org and replaces the original subtree.   This would make it
easy for users
to implement something like http://tinyurl.com/nskzs8 , and probably
other custom
functions.

On Sun, Aug 9, 2009 at 3:19 PM, B Smith-Mannschott<bsmith.occs@gmail.com> w=
rote:
> On Sat, Aug 8, 2009 at 22:25, Ilya Shlyakhter<ilya_shl@alum.mit.edu> wrot=
e:
>>> In the meantime, it would be useful to describe what kind of XML output
>>> do you want, because "XML" does not really describe anything per se.
>>
>> I'm looking for XML output that would closely mirror the logical
>> structure of the org file, and that would contain all the information
>> in the orgfile (since it's easy to ignore the parts you don't need
>> during XML processing). =A0So, something like
>>
>> <orgfile>
>> =A0 <entry>
>> =A0 =A0 =A0<headline>Tasks</headline>
>> =A0 =A0 =A0<body>Here are the tasks I need to do</body>
>> =A0 =A0 =A0<children>
>> =A0 =A0 =A0 =A0 =A0<entry>
>> =A0 =A0 =A0 =A0 =A0 =A0 <headline>Buy bread</headline>
>> =A0 =A0 =A0 =A0 =A0 =A0 <todo-status>DONE</todo-status>
>> =A0 =A0 =A0 =A0 =A0 =A0 <tags><tag>food</tag><tag>errands</tag></tags>
>> =A0 =A0 =A0 =A0 =A0 =A0 <properties>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <property><name>Importance</name><value>=
1</value></property>
>>
>> <property><name>Deadline</name><value><date><day>07</day><month>08</mont=
h><year>09</year></date></value></property>
>> =A0 =A0 =A0 =A0 =A0 =A0 </properties>
>> =A0 =A0 =A0 =A0 =A0 </entry>
>> =A0 =A0 =A0 =A0</children>
>> =A0 =A0 =A0</entry>
>> =A0 </orgfile>
>>
>> The details of the XML schema can of course change. =A0 But it should
>> let you process org file data without having to parse any elements of
>> the org file (ideally, even dates) -- it would all be parsed by
>> orgmode's native parsing code and put into XML elements.
>>
>> If there are questions about how to represent specific org elements in
>> XML I can try to write a more detailed spec.
>>
>
> Out of curiosity, how would you want to handle textual content? Pass
> it through unchanged with org's wiki-like markup in tact, or somehow
> xml-ified?:
>
> *foo* --> *foo*
> *foo* --> <strong>foo</strong>
>
> // Ben
>