From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id 4LAGLHsulF/YDAAA0tVLHw (envelope-from ) for ; Sat, 24 Oct 2020 13:39:07 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id FLDyJ3sulF85GgAA1q6Kng (envelope-from ) for ; Sat, 24 Oct 2020 13:39:07 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id F00DD9401DD for ; Sat, 24 Oct 2020 13:39:06 +0000 (UTC) Received: from localhost ([::1]:36900 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kWJlB-00007Z-P8 for larch@yhetil.org; Sat, 24 Oct 2020 09:39:05 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:57166) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kWJkR-00007D-W9 for emacs-orgmode@gnu.org; Sat, 24 Oct 2020 09:38:20 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:46605) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kWJkL-0007By-8G; Sat, 24 Oct 2020 09:38:13 -0400 Received: from [2a01:e35:2fe1:f780:5497:18cd:5079:cbdf] (port=43304 helo=guerry) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.82) (envelope-from ) id 1kWJkK-0001wR-RO; Sat, 24 Oct 2020 09:38:13 -0400 Received: by guerry (Postfix, from userid 1000) id 532841A60E1D; Sat, 24 Oct 2020 15:38:11 +0200 (CEST) From: Bastien To: Leo Vivier Subject: Re: Shower thought: submit an IETF RFC to register Org as a MIME type Organization: GNU References: <87y2jvkeql.fsf@gnu.org> <87ft63hjoh.fsf@bzg.fr> <87zh4bixe4.fsf@hidden> Date: Sat, 24 Oct 2020 15:38:11 +0200 In-Reply-To: <87zh4bixe4.fsf@hidden> (Leo Vivier's message of "Sat, 24 Oct 2020 15:09:07 +0200") Message-ID: <87d0177ni4.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: hj-orgmode-1@hj.proberto.com, Palak Mathur , emacs-orgmode@gnu.org, mail@nicolasgoaziou.fr, Wes Hardaker , TEC Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.51 X-TUID: qjOYE/AyYj9C Hi Leo, Leo Vivier writes: > Bastien writes: > >> As the first paragraph says:=20 >> >> "This document describes and comments Org syntax as it is currently >> read by its parser (Org Elements)" >> >> while we need a description of Org's syntax from the point of view of=20 >> (1) a human writer and (2) any possible Org parser. > > I agree that (1) and (2) should be two different documents.=20=20 Sorry, perhaps I was not clear: (1) and (2) do not need to be separate documents. I think both can be described in a single document, my main point was that the current org-syntax.org is from none of these points of view. > (2) would > be especially interesting since there are quite a few projects afoot to > parse Org documents outside of Emacs: > - go-org (Go) > https://github.com/niklasfasching/go-org > - orgize (Rust) > https://docs.rs/orgize/0.8.4/orgize/ > > They are in various stages of advancement, but a design document would > go a long way in federating those efforts. > >> I don't know how difficult it is, but I suspect it is quite a lot of >> work. > > I assume that it would be, yes. However, as someone with a vested > interest in developing an efficient external parser for Org documents, > I=E2=80=99d love to contribute. I=E2=80=99ve been playing around lately = with ox.el to > write an exporter to Jupyter (more on that soon), and since it makes > extensive use of org-element.el, I=E2=80=99d have a modicum of knowledge = upon > which I could initiate the effort. Great, thanks for volunteering. I think this is something you should perhaps do with a long time Org user, ping-pong'ing with commits, not alone. Nicolas, what's your take on this? Would it be okay for you if we rename worg/dev/org-syntax.org to something like worg/dev/org-elements-syntax.org or would that be confusing? Would you have any advice on how to tackle worg/org-syntax.org in a generic and useful way? --=20 Bastien