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>,
	 Thierry Coquand <Thierry...@cse.gu.se>,
	Vladimir Voevodsky <vlad...@ias.edu>,
	 Univalent Mathematics <univalent-...@googlegroups.com>
Subject: Re: [HoTT] about the HTS
Date: Thu, 23 Mar 2017 04:33:09 -0700	[thread overview]
Message-ID: <CAOvivQyxnG_qJkzNn1qgn5DdODG0ecU8KsSC5CurgW2nvxt0nQ@mail.gmail.com> (raw)
In-Reply-To: <4f4bcfe8-5d25-42f4-9bf2-ebf5748d629a@googlegroups.com>

Unless I misunderstand, that's not at all what cohesion is about.
Lawvere's cohesion is about relating discrete sets to space-like
objects (in the non-homotopical up-to-homeomorphism sense).  Higher
cohesion is about relating oo-groupoids to "topological oo-groupoids"
in an analogous way.

On Thu, Mar 23, 2017 at 4:22 AM, Matt Oliveri <atm...@gmail.com> wrote:
> Thanks.
>
> I agree that with the sSet option, with an equality reflection rule, it
> would be infeasible to check judgments without extra stuff from outside the
> type theory proper. But what's wrong with that? We add extra stuff anyway,
> like type classes, proof scripts, and implicit arguments. To me, it seems
> that the practical concern of checking the truth of judgments does not need
> to be solved by the design of the core type theory. Indeed, it seems like
> better separation of concerns *not* to solve it there.
>
> Anyway, my understanding of bSet, from what Thierry Coquand said, is that
> it'd be a more OTT-like version of sSet, which is more ETT-like. So instead
> of paths between bSets being reflectable to judgmental equalities, they
> would be "strict propositions" (sProp), whose elements are not only all
> (typally) equal, but they also have no computational content. So any
> "transport" across a strict equality reduces away, as long as it doesn't
> change the type. (It doesn't have to be (judgmentally equal to)
> reflexivity.)
>
> I figure the idea is that bSet should be able to do everything sSet can,
> just with extra computationally-irrelevant transports thrown in to appease a
> decidable type checker.
>
> I don't actually see how either of these universes would help define
> semi-simplicial types. I didn't realize that was the goal here. I thought we
> were just trying to make set-level math more convenient.
>
> -----------
>
> Though I haven't given it a serious thinking-about, I figured that stuff
> with cohesion would be a good way to make semi-simplicial types definable,
> without adding non-fibrant types.
> (https://homotopytypetheory.org/2015/09/25/realcohesion/) It sounded like
> cohesion gives you a set-level view of non-hsets, so I figured you should be
> able to use strict equality in the construction of non-hsets that way.
>
> I suppose strict sets and cohesion can be combined. A set-level view of
> things should yield only strict sets, not arbitrary hsets. (I guess that
> requires a whole hierarchy of strict set universes. But unlike HTS, they're
> all "included" in the univalent universes, not the other way around.)
>
> On Wednesday, March 22, 2017 at 5:01:16 PM UTC-4, v v wrote:
>>
>> 1. As Thierry pointed out previously, the problem with sSet is that if we
>> postulate that nat:sSet, then for any (small) type T, the function type T ->
>> nat is in sSet, e.g. nat -> nat is in sSet.
>>
>> Since it is possible to construct two elements of nat -> nat the equality
>> between which is an undecidable proposition, it implies that the
>> definitional equality in any sufficiently advanced type system with sSet and
>> nat:sSet is undecidable.
>>
>> That means that witnesses, in some language, of definitional equality need
>> to be carried around and therefore the design of a proof assistant where the
>> proof term is the proof is not possible in this system.
>>
>> 2. It is not so clear what would happen with only bSet and nat:bSet.
>>
>> Vladimir.
>>
>>
>>
>>
>>
>> On Mar 22, 2017, at 5:49 PM, Thierry Coquand <Thier...@cse.gu.se> wrote:
>>
>>
>> If my note was correct, it describes in the cubical set model two
>> univalent universes
>> (subpresheaf of the first universe)  that satisfy
>>
>>  (1)   if   A : sSet    and   p : Path A a b   then   a = b : A  and p is
>> the constant path a
>> (equality reflection rule)
>>
>>  (2)   if A : bSet and p and q of type Path A a b   then p = q : Path A a
>> b
>> (judgemental form of UIP)
>>
>>  Maybe (1) or (2) could be used instead of HTS (and we would remain in an
>> univalent
>> theory, where all types are fibrant)
>>
>>  For testing this, one question is:  can we define semi-simplicial types
>> in (1)? in (2)?
>>
>>  Best regards,
>>  Thierry
>>
>>
>>
>> On 20 Mar 2017, at 16:12, Matt Oliveri <atm...@gmail.com> wrote:
>>
>> So the answer was yes, right? Problem solved?
>>
>> On Thursday, February 23, 2017 at 9:47:57 AM UTC-5, v v wrote:
>>>
>>> Just a thought… Can we devise a version of the HTS where exact equality
>>> types are not available for the universes such that, even with the exact
>>> equality, HTS would remain a univalent theory.
>>>
>>> Maybe only some types should be equipped with the exact equality and this
>>> should be a special quality of types.
>>>
>>> Vladimir.
>>>
>>> PS If there are higher inductive types then the exact equality should not
>>> be available for them either.
>>
>>
>> --
>> 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.
>>
>>
>>
>> --
>> 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.
>
> --
> 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.

  reply	other threads:[~2017-03-23 11:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 14:47 Vladimir Voevodsky
2017-02-23 14:57 ` [HoTT] " Benedikt Ahrens
2017-02-23 18:08   ` Vladimir Voevodsky
2017-02-23 18:52     ` Benedikt Ahrens
2017-02-23 21:45       ` Vladimir Voevodsky
     [not found]         ` <87k28fek09.fsf@capriotti.io>
2017-02-24 14:36           ` [UniMath] " Vladimir Voevodsky
2017-02-24 15:06             ` Paolo Capriotti
2017-02-24 15:10               ` Vladimir Voevodsky
2017-03-10 13:35             ` HIT Thierry Coquand
2017-02-24 14:36         ` [HoTT] about the HTS Paolo Capriotti
2017-02-25 19:19 ` Thierry Coquand
2017-02-27 18:50   ` [UniMath] " Vladimir Voevodsky
2017-02-27 18:53     ` Vladimir Voevodsky
2017-02-27 18:58       ` Thierry Coquand
2017-02-28  2:17         ` Vladimir Voevodsky
2017-03-01 20:23           ` Thierry Coquand
2017-03-20 15:12 ` Matt Oliveri
2017-03-22 16:49   ` [HoTT] " Thierry Coquand
2017-03-22 21:01     ` Vladimir Voevodsky
2017-03-23 11:22       ` Matt Oliveri
2017-03-23 11:33         ` Michael Shulman [this message]
2017-03-23 12:16           ` Matt Oliveri

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=CAOvivQyxnG_qJkzNn1qgn5DdODG0ecU8KsSC5CurgW2nvxt0nQ@mail.gmail.com \
    --to="shu..."@sandiego.edu \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="Thierry..."@cse.gu.se \
    --cc="atm..."@gmail.com \
    --cc="univalent-..."@googlegroups.com \
    --cc="vlad..."@ias.edu \
    /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).