emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode syntax as a tool-independent MIME type
Date: Tue, 18 Oct 2022 10:13:09 +0200	[thread overview]
Message-ID: <2022-10-18T10-05-24@devnull.Karl-Voit.at> (raw)
In-Reply-To: 87fsfl7g01.fsf@bzg.fr

Hi Bastien,

* Bastien <bzg@gnu.org> wrote:
> Hi Karl and Timothy,
> thank you Karl for reviving this important topic.
> I think our collective priority should be to work on
> https://orgmode.org/worg/dev/org-synxtax.html so that it reflects the
> current Org syntax.  Hopefully we can do this before Org 9.6.  As
> discussed with TEC, we can factor out suggestions from this document
> so that it is not a mix of facts and hypotheses.

A valid approach.

I think we do have two different approaches ongoing here. With OD1 I
tried to come up with a minimal set of Org-mode syntax elements that
are very easy to implement in non-Emacs tools in order to get an
easy intro to this universe. This is a bottom-up approach.

Defining the whole Org-mode syntax as you've suggested is a complete
definition of Orgdown (or OD∞ as of
) which is a top-down approach.

So far, I don´t see a conflict here. This may arise with OD2, OD3,
... definitions if they will ever exist.

> Then we can work on suggestions for evolutions of the current Org-mode
> syntax chunk by chunk, as a long-term goal for stabilizing changes for
> Org 10 (2023 ?)

Sounds great!

> What occurred to me while rereading this thread is that definining a
> syntax for a IETF RFC on an Org mimetype probably needs to be done not
> just by this Emacs Org-mode community, but by bringing together other
> "consumers" of .org files, from ecosystems outside of Emacs.
> Such a collective work could lead to define what subset of the Org
> syntax is useful as the corner-stone for .org files everywhere - which
> is what you rightfully brought up with "Orgdown".

I tried to collect projects on

> If successful, such a process could end up in defining the minimal and
> official "Org syntax" while allowing implementations (like the one for
> Emacs org-mode) to supercharge this syntax if deemed useful.

To me, this sound aligned with the idea of OD levels OD1 and OD∞.

> Perhaps TEC is right and we will end up having the minimal syntax
> being the one we currently use for Org-mode: we'll see.
> But we need volunteers: one to work on worg/dev/org-synxtax.org (I'm
> assuming TEC can lead the work here) and one to set up a discussion
> with people implementing Org in various places (you ?).

What kind of discussion is on your mind? At the moment, I tend to
think that the Org-mode community should provide directions by
developing a formal definition of the syntax and maybe later-on
define viable sub-sets (the OD levels?) so that tool developers
don't have to implement the whole large thing.

At this stage, I don't know what discussions you're trying to start
here. Can you elaborate?

> I suggest to take this sequentially and not tackle the second work
> before we're done with the first one.

I interpret this as "discussions with tool developers after working
on the formal Org definition". This would be my understanding and
also my thought.

get mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML into Org-mode:
       > get Memacs from https://github.com/novoid/Memacs <
Personal Information Management > http://Karl-Voit.at/tags/pim/
Emacs-related > http://Karl-Voit.at/tags/emacs/

  reply	other threads:[~2022-10-18  8:17 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 14:44 Shower thought: submit an IETF RFC to register Org as a MIME type TEC
2020-09-04 16:14 ` Gustav Wikström
2020-09-05  5:30 ` stardiviner
2020-09-05  5:50   ` Bastien
2020-09-05  5:53     ` TEC
2020-09-17  7:09       ` TEC
2020-09-17  7:18         ` hj-orgmode-1
2020-09-23  7:31           ` Bastien
2020-10-01  3:40             ` TEC
2020-10-01  5:21               ` Bastien
2020-10-01  5:48                 ` TEC
2020-10-01  6:46                   ` Bastien
2020-10-01 15:39               ` Wes Hardaker
2020-10-01 15:45                 ` TEC
2020-10-06 18:03                   ` Wes Hardaker
2020-10-06 19:03                     ` TEC
2020-10-06 20:39                       ` Palak Mathur
2020-10-24 12:09                     ` Bastien
2020-10-24 12:28                       ` Palak Mathur
2020-10-24 12:50                         ` Bastien
2020-10-24 13:09                           ` Leo Vivier
2020-10-24 13:38                             ` Bastien
2020-10-24 13:49                               ` Leo Vivier
2020-10-24 15:12                                 ` Bastien
2020-10-24 15:00                           ` Palak Mathur
2020-10-24 15:40                             ` Bastien
2020-10-24 15:57                               ` Palak Mathur
2020-10-14  9:52               ` Lennart C. Karssen
2020-10-14 14:22                 ` Nicolas Goaziou
2022-10-17 20:46         ` Org-mode syntax as a tool-independent MIME type (was: Shower thought: submit an IETF RFC to register Org as a MIME type) Karl Voit
2022-10-18  1:55           ` Timothy
2022-10-18  7:22             ` Org-mode syntax as a tool-independent MIME type Bastien
2022-10-18  8:13               ` Karl Voit [this message]
2022-10-21 11:44                 ` Ihor Radchenko
2022-10-18  8:05             ` Karl Voit
2022-10-21 11:41           ` Org-mode syntax as a tool-independent MIME type (was: Shower thought: submit an IETF RFC to register Org as a MIME type) Ihor Radchenko
2021-03-23  3:00 ` Shower thought: submit an IETF RFC to register Org as a MIME type Timothy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2022-10-18T10-05-24@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news2042@Karl-Voit.at \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).