Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Matt Oliveri <atm...@gmail.com>
To: Homotopy Type Theory <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] A small observation on cumulativity and the failure of initiality
Date: Sun, 15 Oct 2017 14:00:10 -0700 (PDT)	[thread overview]
Message-ID: <37664950-3045-4570-af39-5f44bfc13a1b@googlegroups.com> (raw)
In-Reply-To: <CAOvivQw=Mx_cw-nTrR9ov042+uQ9wZHzP2ykJMJzqes7=NFShQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2940 bytes --]

In order to assign meanings to derivations, one would have to define 
derivations. Technically, to assign meanings to derivable terms, one would 
only need to define derivability. All information needed to pick the right 
meaning would then need to be included in the terms. This might explain the 
disagreement over whether unique typing is necessary. In the middle, you 
could assign meanings to derivable judgments...

Given the usual raw-terms-then-derivations approach, interpreting 
derivations is the most flexible. Gabirel Scherer brought up functor 
semantics of refinement type systems, which seems to be studying the 
general situation, with a category of derivation meanings and a category of 
term meanings, and a functor from the former to the latter.

With intrinsically typed syntax--what Thorsten is talking about--there is 
no separation between terms and derivations in the first place. This is a 
style of syntax for type systems where--as a design constraint--all 
"relevant" information is included in the terms.

Mike, I'm surprised that you favor interpreting derivations. For a 
categorical semantics, there is only one "level" of meaning. (Not two, like 
with a functor.) So I figured you would find it more elegant to stick to 
systems where the meaning can be assigned to derivable terms. Even when 
this sort of system is not directly amenable to implementation, it provides 
an interface to separate syntactic and semantic concerns.

On Sunday, October 15, 2017 at 12:00:36 PM UTC-4, Michael Shulman wrote:
>
> I mean, it seems to me kind of like the difference between proving a 
> type A is contractible by 
>
> Sigma(a:A) Pi(x:A) (x=a) 
>
> and by 
>
> A x Pi(x y:A) (x=y) 
>
> i.e. not much.  But maybe I am missing something? 
>
> On Sun, Oct 15, 2017 at 7:53 AM, Michael Shulman <shu...@sandiego.edu 
> <javascript:>> wrote: 
> > I'm not saying to do anything different mathematically, just to 
> > *think* about "using a partial interpretation function on prejudgments 
> > and showing that all derivable judgments get a meaning" as *being a 
> > way of* "assigning meanings to derivations and showing that distinct 
> > derivations of the same judgment get the same meaning". 
> > 
> > On Sun, Oct 15, 2017 at 6:57 AM, Thomas Streicher 
> > <str...@mathematik.tu-darmstadt.de <javascript:>> wrote: 
> >>> > When writing my thesis in the second half of the 80s I found this 
> too 
> >>> > difficult and instead used an a priori partial interpretation 
> >>> > function assigning meaning to prejudgements. It was then part of the 
> >>> > correctness theorem that all derivable judgements get assigned a 
> meaning. 
> >>> 
> >>> Couldn't one consider the latter to be a way of doing the former? 
> >> 
> >> In principle yes but it is very laborious. First of all you have to 
> >> formalize derivations and do a double induction on them which I don't 
> >> know how to to perform. 
> >> 
> >> Thomas
>

[-- Attachment #1.2: Type: text/html, Size: 3745 bytes --]

  reply	other threads:[~2017-10-15 21:00 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 [this message]
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
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=37664950-3045-4570-af39-5f44bfc13a1b@googlegroups.com \
    --to="atm..."@gmail.com \
    --cc="HomotopyT..."@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).