Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Michael Shulman <shu...@sandiego.edu>
To: Matt Oliveri <atm...@gmail.com>
Cc: Homotopy Type Theory <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] A small observation on cumulativity and the failure of initiality
Date: Mon, 16 Oct 2017 09:37:59 -0700	[thread overview]
Message-ID: <CAOvivQw0fNvMdXk07wGayzXBTE3wr0p5Z-0Mj89arB+HXEMZHw@mail.gmail.com> (raw)
In-Reply-To: <feb647e4-c2c3-42ab-b8be-1e8bdae562ae@googlegroups.com>

I prefer my terminology (yes, I think inventing a new word "class" is so bad).
I don't actually reject "term", I use it to mean "derivation of a judgment
\Gamma \vdash A", and I use "type" to mean "derivation of a judgment
\Gamma \vdash type".  That matches the extrinsic usage pretty closely
in practice.
I only phrased it as "there are no terms" to contrast with your "there
are no derivations".

But let's not spam everyone else on this list any more with
discussions about terminology.

On Mon, Oct 16, 2017 at 9:20 AM, Matt Oliveri <atm...@gmail.com> wrote:
> I understand your argument as a good reason to consider intrinsic syntax as
> being more analogous to derivations than to preterms. But still, trying to
> consistently call all those things judgments and derivations, and having
> nothing syntactic called terms or types seems impractical. Like I said, one
> could have opinions about whether (the things I call) intrinsic terms are
> more like preterms or derivations, but my terminology recommendation is not
> dependent on that. The existing papers on intrinsic syntax always seem to
> call them terms, even when they point out that they're a lot like
> derivations.
>
> I realized my terminology proposal didn't include anything convenient for
> the metalanguage types of intrinsic syntax objects. Normally, "judgments"
> would be OK, since that's what they correspond to. But for now I want to
> distinguish them easily from the extrinsic judgments, which involve
> preterms. I'll call them "classes". They are strongly-typed versions of the
> things often called "syntactic classes" or "syntactic categories" in CS. (Of
> course, calling them "categories" here would be super confusing.)
>
> So now let's try out your opening sentence in my terminology:
> [I would rather characterize intrinsic style by saying there are no
> *preterms*: all you have are classes and terms.]
> That's not so bad, is it? I feel like what makes you want to reject the term
> "term" is that you want to emphasize that *preterms* are not involved at
> all.
>
> Anyway, now I think I know what you meant before, about interpreting
> derivations. But I think it wasn't clear, because it sounded like you were
> talking about the usual extrinsic derivations.
>
> On Monday, October 16, 2017 at 11:06:11 AM UTC-4, Michael Shulman wrote:
>>
>> I would rather characterize intrinsic style by saying there are no
>> *terms*: all you have are judgments and derivations.  Look at an
>> inductive-inductive encoding: its meta-language types are the
>> object-language judgments, and its meta-language terms are the
>> object-language derivations.  Some of the judgment forms may be put
>> together out of a context (another judgment) and a type in that
>> context (a third judgment), but not all of them (e.g. not the judgment
>> for "is a context"); and you can also call a derivation a "term", but
>> that could be misleading.  In particular, this perspective makes it
>> more clear that there is a bidirectional version of intrinsic style:
>> the two "directions" become simply two different judgment forms, and
>> the derivations are inductively generated by the bidirectional
>> "typing" rules.

  reply	other threads:[~2017-10-16 16:38 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 [this message]
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=CAOvivQw0fNvMdXk07wGayzXBTE3wr0p5Z-0Mj89arB+HXEMZHw@mail.gmail.com \
    --to="shu..."@sandiego.edu \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="atm..."@gmail.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).