Skip to content

On naming convention and file structure #809

Description

@iehality

There are multiple methods for naming things with more than two characteristics after their properties. A simple approach is to fix one characteristics to come first. However this yields at least two different naming methods. For instance,

  1.                                                          *
                                                             |
                      *--------------------------------------|----------------------------------*
                      |                                      |                                  |
                Propositional                           FirstOrder                         SecondOrder
                      |                                      |                                  |
            *---------|----------*                  *--------|--------*                *--------|--------*
            |                    |                  |                 |                |                 |
     Propositional.Int    Propositional.Cl    FirstOrder.Int    FirstOrder.Cl   SecondOrder.Int    SecondOrder.Cl
    

and

  1.                                                         *
                                                            |
                                 *--------------------------|----------------------------*
                                 |                                                       |
                                Int                                                      Cl
                                 |                                                       |
            *--------------------*-----------------*                  *------------------*-----------------*
            |                    |                 |                  |                  |                 |
     Int.Propositional    Int.FirstOrder    Int.SecondOrder    Cl.Propositional    Cl.FirstOrder   Cl.SecondOrder
    

Technically, the barriers between logics with different expressive powers Propositional / FirstOrder / SecondOrder seems large (because new syntactical structures (quantifiers, modalities, ...) must be introduced), while that between different logical philosophies Int / Cl appears small (to make intuitionistic into classical, one need only add LEM). Therefore, option 1 seems more appropriate.

However, mathematically, the distinction in logical philosophy seems more significant than the minor difference in expressive power. While many texts treat first-order logic as an extension of propositional logic, this is not the case with classical/intuitionistic. (Personally, I consider it a mistake to view classical logic and intuitionistic logic literally, as systems describing the same objects. Rather, as done by negative translation, intuitionistic logic should be regarded as a more detailed version of logic that embeds classical logic.) From this perspective, option 2 is preferable.

Currently, these are mixed up. Which one should be adopted?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions