emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Timothy <orgmode@tec.tecosaur.net>
To: emacs-orgmode@gnu.org
Subject: On org-syntax and IANA MIME type registration
Date: Fri, 26 Jan 2024 11:30:41 +0800	[thread overview]
Message-ID: <87wmrw3gpy.fsf@tec.tecosaur.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]

Hi All,

With the recent mention of the text/org mime type, and registering it as an IANA
in-tree MIME type in particular, I’d like to draw attention to this part of
<https://www.rfc-editor.org/rfc/rfc6838.html#section-3.1>:

> When review is required, a change request may be denied if it renders entities
> that were valid under the previous definition invalid under the new definition.

While the org-syntax document is a work in progress to accurately describe the
current state of affairs, there are currently supported syntactic elements that
I think are broadly seen as “would be nice if we didn’t do that”. For example:
the special switch syntax in babel headers, and support for $-maths.

This does make me wonder if we should actually try to register a slightly
different org-syntax to “what org-mode parses”, without these elements that we
now think we’re better off without, but have org-mode still parse them.

My thinking is we don’t want to lock ourselves into a situation where we would
/like/ to deprecate certain syntax over the long term, but are unable to do so
without diverging from the IANA-registered specification, and can’t register the
change in syntax because of the paragraph I’ve quoted.

All the best,
Timothy

-- 
Timothy (‘tecosaur’/‘TEC’), Org mode contributor.
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/tec>.

next             reply	other threads:[~2024-01-26  3:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26  3:30 Timothy [this message]
2024-01-26 13:55 ` On org-syntax and IANA MIME type registration Ihor Radchenko

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=87wmrw3gpy.fsf@tec.tecosaur.net \
    --to=orgmode@tec.tecosaur.net \
    --cc=emacs-orgmode@gnu.org \
    /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

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).