Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Thorsten Altenkirch <Thorsten....@nottingham.ac.uk>
To: Andrej Bauer <andrej...@andrej.com>,
	Homotopy Type Theory <homotopyt...@googlegroups.com>
Cc: Univalent Mathematics <univalent-...@googlegroups.com>
Subject: Re: [HoTT] A small observation on cumulativity and the failure of initiality
Date: Sun, 15 Oct 2017 10:42:41 +0000	[thread overview]
Message-ID: <D608F6EB.A2296%psztxa@exmail.nottingham.ac.uk> (raw)
In-Reply-To: <CAB0nkh1dApftkpR+KWJS445wxcab2zqt6o1FBgybjCrc-U0neA@mail.gmail.com>

On 14/10/2017, 10:37, "homotopyt...@googlegroups.com on behalf of
Andrej Bauer" <homotopyt...@googlegroups.com on behalf of
andrej...@andrej.com> wrote:

>> In our recent work on intrinsic
>> syntax of Type Theory we present a typed syntax that never refers to
>> preterms. In this framework theories with coercions cannot be expressed
>> and the syntax is the initial algebra of the corresponding notion of
>> algebras.
>
>This is quite cool, but I'd just like to point out that there are
>levels of abstraction, some of which cannot be ignored.
>
>At a very banal level, we need to know how to convert concrete syntax
>into abstract syntax.
>
>At a slightly less banal level, we have to admit that preterms
>(expressed as abstract syntax) are unavoidable. An important aspect of
>type theory revolves around making sure that the thing written down
>makes sense. The "thing written down" is a preterm (something that
>survived parsing but has yet to be type checked).

Indeed, but it isn't even preterms but strings we really see (or bits?).
The theorem that beta-reduction preserves matching brackets is  mixing
levels of abstraction in bad way. As we are happy to reason about terms as
trees knowing that we can parse strings into trees, we should think about
intrinsic terms (what Thomas calls "derivations") knowing that by type
checking and scope checking we can convert trees into derivations.
Assigning meaning to purely syntactic entities is a confusing levels of
abstractions in the same way as the matching brackets theorem.

>
>There is also the question of breaking the vicious circle: we express
>type theory inside type theory, but where did the original type theory
>come from? I think it is quite reasonable to take the possition that
>type theory is primitive, but it is also equally reasonable to take
>the position that one should analyse how type theory arises from a
>more concrete setup, for instance, there is some value in knowing that
>the syntactic models based on concrete syntax are initial for type
>theory.

The original type theory is in our mind and we may use english or any
other natural language to express it and then we want to be more precise
and use the type theory in our minds to explain the type theory we
implement, which then in turn can be implemented. No vicious circle.

Thorsten


>
>With kind regards,
>
>Andrej
>
>-- 
>You received this message because you are subscribed to the Google Groups
>"Homotopy Type Theory" group.
>To unsubscribe from this group and stop receiving emails from it, send an
>email to HomotopyTypeThe...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.





This message and any attachment are intended solely for the addressee
and may contain confidential information. If you have received this
message in error, please send it back to me, and immediately delete it. 

Please do not use, copy or disclose the information contained in this
message or in any attachment.  Any views or opinions expressed by the
author of this email do not necessarily reflect the views of the
University of Nottingham.

This message has been checked for viruses but the contents of an
attachment may still contain software viruses which could damage your
computer system, you are advised to perform your own checks. Email
communications with the University of Nottingham may be monitored as
permitted by UK legislation.


  parent reply	other threads:[~2017-10-15 10:42 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 18:43 Dimitris Tsementzis
2017-10-12 22:31 ` [HoTT] " Michael Shulman
2017-10-13  4:30   ` Dimitris Tsementzis
2017-10-13 15:41     ` Michael Shulman
2017-10-13 21:51       ` Dimitris Tsementzis
2017-10-13  0:09 ` Steve Awodey
2017-10-13  0:44   ` Alexander Altman
2017-10-13 15:50   ` Michael Shulman
2017-10-13 16:17     ` Steve Awodey
2017-10-13 16:23       ` Michael Shulman
2017-10-13 16:36         ` Matt Oliveri
2017-10-14 14:56         ` Gabriel Scherer
2017-10-15  7:45           ` Thomas Streicher
2017-10-15  8:37             ` Thierry Coquand
2017-10-15  9:26               ` Thomas Streicher
2017-10-16  5:30                 ` Andrew Polonsky
2017-10-15 10:12             ` Michael Shulman
2017-10-15 13:57               ` Thomas Streicher
2017-10-15 14:53                 ` Michael Shulman
2017-10-15 16:00                   ` Michael Shulman
2017-10-15 21:00                     ` Matt Oliveri
2017-10-16  5:09                       ` Michael Shulman
2017-10-16 12:30                         ` Neel Krishnaswami
2017-10-16 13:35                           ` Matt Oliveri
2017-10-16 15:00                           ` Michael Shulman
2017-10-16 16:34                             ` Matt Oliveri
2017-10-16 13:45                         ` Matt Oliveri
2017-10-16 15:05                           ` Michael Shulman
2017-10-16 16:20                             ` Matt Oliveri
2017-10-16 16:37                               ` Michael Shulman
2017-10-16 10:01                   ` Thomas Streicher
2017-10-15 20:06     ` Matt Oliveri
2017-10-13  8:03 ` Peter LeFanu Lumsdaine
2017-10-13  8:10   ` Thomas Streicher
2017-10-14  7:33     ` Thorsten Altenkirch
2017-10-14  9:37       ` Andrej Bauer
2017-10-14  9:52         ` Thomas Streicher
2017-10-14 10:51           ` SV: " Erik Palmgren
2017-10-15 23:42           ` Andrej Bauer
2017-10-15 10:42         ` Thorsten Altenkirch [this message]
2017-10-13 22:05   ` Dimitris Tsementzis
2017-10-13 14:12 ` Robin Adams
     [not found] <B14E498C-FA19-41D2-B196-42FAF85F8CD8@princeton.edu>
2017-10-14  9:55 ` [HoTT] " Alexander Altman
2017-10-16 10:21 Thorsten Altenkirch
2017-10-16 10:42 ` Andrew Polonsky
2017-10-16 14:12   ` Thorsten Altenkirch
2017-10-16 10:21 Thorsten Altenkirch

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

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

  git send-email \
    --in-reply-to=D608F6EB.A2296%psztxa@exmail.nottingham.ac.uk \
    --to="thorsten...."@nottingham.ac.uk \
    --cc="andrej..."@andrej.com \
    --cc="homotopyt..."@googlegroups.com \
    --cc="univalent-..."@googlegroups.com \
    /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.
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 NNTP newsgroup(s).