Text 13962, 104 rader
Skriven 2026-03-10 10:14:47 av Matthew Asham (1:153/150)
Ärende: Re: MARKUP Registry
===========================
On March 2 2026, Matthew Asham wrote:

 >> 3. THE MARKUP KLUDGE
 >> --------------------
 RS>>  >
 >> 3.1 Syntax
 RS>>  >
 >> The MARKUP kludge line has the following syntax:
 RS>>  >
 >>     ^AMARKUP: <format> <version>
 RS>>  >
 >> where ^A represents the ASCII SOH character (0x01), <format> is a
 >> registered or otherwise well-known markup format identifier, and
 >> <version> is a format version string meaningful within that format.
 RS>>  >
 >> Examples:
 RS>>  >
 >>     ^AMARKUP: Markdown 1.0
 >>     ^AMARKUP: BBCode 1.0
 >>     ^AMARKUP: Gemtext 1.0

It occured to me that a REGISTRY is not defined for the markup codes.  There is
an
examples section but examples are not really a registry.

I have added a new section "MARKUP FORMAT REGISTRY" as section 8.


8. MARKUP FORMAT REGISTRY
-------------------------

This section defines the initial set of registered format identifiers
for use with the MARKUP kludge. Additional identifiers MAY be used by
mutual agreement between implementations; authors of new identifiers
are ENCOURAGED to document them and submit them for inclusion here.

Format identifiers are matched case-insensitively per section 3.3.
The canonical capitalisation shown below SHOULD be used when emitting
the kludge.

8.1 Registered Identifiers

  Identifier    Version   Description
  ----------    -------   -----------
  Markdown      1.0       CommonMark-compatible Markdown. Implementations
                          SHOULD follow the CommonMark specification [5].
                          See section 5 for guidance on dialect disclosure.

  BBCode        1.0       Tag-based markup originating in bulletin board
                          systems, using [tag] and [/tag] delimiters.
                          Implementations SHOULD document which tag set
                          is supported, as no single normative BBCode
                          specification exists.

  Gemtext       1.0       Line-oriented markup used by the Gemini protocol.
                          Each line begins with an optional prefix character
                          that determines its type (link, heading, list
                          item, preformatted block, quote, or plain text).
                          Implementations SHOULD follow the Gemini
                          specification for line-type parsing.

  StyleCodes    1.0       Character-sequence-based inline formatting
                          originating in GoldEd and compatible FidoNet
                          editors. Also known as "Rich Text" (SemPoint),
                          "Structured Text" (Mozilla/Thunderbird), and
                          "markup" (Synchronet). The identifier StyleCodes
                          is RECOMMENDED over these alternatives; see
                          section 5.

8.2 Reserved Identifiers

  The following identifiers are reserved and MUST NOT be used as
  format identifiers in the MARKUP kludge, to avoid collision with
  existing terminology:

    RTF      (conflicts with Microsoft Rich Text Format)
    RST      (conflicts with reStructuredText)
    HTML     (conflicts with HyperText Markup Language; active content
              rendering is explicitly discouraged by section 6)

8.3 Registration Process

  At this time no formal registration authority exists. Authors wishing
  to use a new identifier SHOULD:

    1. Choose a stable, unambiguous token not already in use.
    2. Publish a definition of the format and the meaning of any
       version strings used.
    3. Submit the identifier and definition to the FidoNet community
       for inclusion in this registry.



Rather than re-post the entire proposal I've updated the "live" version here: 
https://github.com/awehttam/binkterm-php/issues/161

Matthew

~ awehttam @1:153/150 @gmail.com | www.lovelybits.org

... Press any key to continue or any other key to quit

--- BinktermPHP v1.8.6
 * Origin: Claude's BBS - https://claudes.lovelybits.org (1:153/150)