From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Org-mode syntax as a tool-independent MIME type (was: Shower thought: submit an IETF RFC to register Org as a MIME type)
Date: Mon, 17 Oct 2022 22:46:50 +0200 [thread overview]
Message-ID: <2022-10-17T22-36-38@devnull.Karl-Voit.at> (raw)
In-Reply-To: 87sgbgg9r0.fsf@gmail.com
Hi,
* TEC <tecosaur@gmail.com> wrote:
>
> I'm still hoping for that discussion :P
>
> To the Org community, if you have thoughts on this - please share them
> :)
For reasons explained in my Orgdown-related articles[1] I would
propose to use this chance to introduce a different term for the
Org-mode lightweight markup language in contrast to the Org-mode
Elisp implementation in order to push the syntax in a tool-agnostic
way. We should not think only of GNU Emacs because there is a
rising number of tools that do support text files in Org-mode
syntax[2] which is also a huge advantage for users of GNU Emacs:
collaboration, public awareness of the syntax, more tool support,
...
I proposed the term Orgdown for the Org-mode syntax and also
proposed various levels in order to provide sub-sets of Org-mode
syntax[3] that are realistic to implement with finite effort. Using
those OD-levels to come up with a formal definition (EBNF?) might
play perfectly well with different parameters of the MIME type[4].
In my opinion, this would be a huge step forward for the whole
ecosystem that supports the same Org-mode syntax.
If we do not keep the MIME type independent from the GNU Emacs
Org-mode implementation, the overall use would be much smaller in
the long run.
Let's use that to establish a broad base for this great lightweight
markup language syntax!
[1]
https://karl-voit.at/2021/11/27/orgdown/
https://emacsconf.org/2021/talks/org-outside/
https://gitlab.com/publicvoit/orgdown
https://karl-voit.at/2021/12/02/Orgdown-feedback/
[2]
https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org
[3]
https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Orgdown-Levels.org
[4] https://gitlab.com/publicvoit/orgdown/-/issues/8
--
Personal Information Management > http://Karl-Voit.at/tags/pim/
Emacs-related > http://Karl-Voit.at/tags/emacs/
next prev parent reply other threads:[~2022-10-17 20:50 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 ` Karl Voit [this message]
2022-10-18 1:55 ` Org-mode syntax as a tool-independent MIME type (was: Shower thought: submit an IETF RFC to register Org as a MIME type) Timothy
2022-10-18 7:22 ` Org-mode syntax as a tool-independent MIME type Bastien
2022-10-18 8:13 ` Karl Voit
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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-17T22-36-38@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news2042@Karl-Voit.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).