Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: "Jon Sterling" <jon@jonmsterling.com>
To: "'Martin Escardo' via Homotopy Type Theory"
	<HomotopyTypeTheory@googlegroups.com>
Subject: Re: [HoTT] Re: A question about the problem with regularity in CCHM cubical type theory
Date: Sun, 15 Sep 2019 21:04:10 -0400	[thread overview]
Message-ID: <80a2be3b-afaa-4106-9c69-0df6567ec709@www.fastmail.com> (raw)
In-Reply-To: <16b3b92f-069b-468c-94f8-f3859e152338@googlegroups.com>

Hi Andrew,

Does "all monomorphisms are cofibrations" imply that identity and path types coincide? or only the other way around?

Thanks,
Jon


On Sun, Sep 15, 2019, at 7:55 AM, Andrew Swan wrote:
> You might have already seen this, but I have a paper on some related 
> issues at https://arxiv.org/abs/1808.00920 . In that paper I didn't 
> look at the original version of regularity, but a more recent version 
> ("all monomorphisms are cofibrations") that fits better with the 
> general framework of Orton and Pitts. In that case it is definitely 
> equality of objects that causes problems.
> 
> Best,
> Andrew
> 
> On Friday, 13 September 2019 08:10:42 UTC+2, Jasper Hugunin wrote:
> > Hello all,
> > 
> > I've been trying to understand better why composition for the universe does not satisfy regularity.
> > Since comp^i [ phi |-> E ] A is defined as (roughly) Glue [ phi |-> equiv^i E ] A, I would expect regularity to follow from two parts:
> > 1. That Glue [ phi |-> equivRefl A ] A reduces to A (a sort of regularity condition for the Glue type constructor itself)
> > 2. That equiv^i (refl A) reduces to equivRefl A
> > I'm curious as to which (or both) of these parts was the issue, or if regularity for the universe was supposed to follow from a different argument.
> > 
> > Context:
> > I've been studying and using CCHM cubical type theory recently, and often finding myself wishing that J computed strictly.
> > If I understand correctly, early implementations of ctt did have strict J for Path types, and this was justified by a "regularity" condition on the composition operation, but as discussed in this thread on the HoTT mailing list <https://groups.google.com/d/msg/homotopytypetheory/oXQe5u_Mmtk/3HEDk5g5uq4J>, the definition of composition for the universe was found to not satisfy regularity.
> > I don't remember seeing the regularity condition defined anywhere, but my understanding is that it requires that composition in a degenerate line of types, with the system of constraints giving the sides of the box also degenerate in that direction, reduces to just the bottom of the box. This seems to be closed under the usual type formers, plus Glue, but not the universe with computation defined as in the CCHM paper <http://www.cse.chalmers.se/~coquand/cubicaltt.pdf> (for trivial reasons and non-trivial reasons; it gets stuck at the start with Glue [ phi |-> equiv^i refl ] A not reducing to anything).
> > 
> > Best regards,
> > - Jasper Hugunin
> 
>  -- 
>  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 HomotopyTypeTheory+unsubscribe@googlegroups.com.
>  To view this discussion on the web visit 
> https://groups.google.com/d/msgid/HomotopyTypeTheory/16b3b92f-069b-468c-94f8-f3859e152338%40googlegroups.com <https://groups.google.com/d/msgid/HomotopyTypeTheory/16b3b92f-069b-468c-94f8-f3859e152338%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
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 HomotopyTypeTheory+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/HomotopyTypeTheory/80a2be3b-afaa-4106-9c69-0df6567ec709%40www.fastmail.com.

  parent reply	other threads:[~2019-09-16  1:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13  6:10 [HoTT] " Jasper Hugunin
2019-09-15  5:57 ` [HoTT] " Jasper Hugunin
     [not found]   ` <CAMWCppk4PWzfZ1HKNLMdAZ=RBC-ARxtJXR8okvwO3raea5gC8Q@mail.gmail.com>
     [not found]     ` <CAGTS-a-SvWWF+br6sKxGj6ufVY=4m830FH9BDg06QJR1vbNFsw@mail.gmail.com>
2019-09-16  2:18       ` Fwd: " Jasper Hugunin
2019-09-16 16:18         ` [HoTT] " Licata, Dan
2019-09-16 17:09           ` Jasper Hugunin
2019-09-16 19:01             ` Licata, Dan
2019-09-16 20:17               ` Jasper Hugunin
2019-09-18 12:16                 ` Anders Mortberg
2019-09-18 12:52                   ` Thierry Coquand
2019-09-15 11:55 ` [HoTT] " Andrew Swan
2019-09-15 22:38   ` Jasper Hugunin
2019-09-16  1:04   ` Jon Sterling [this message]
     [not found]     ` <A605E6EE-0101-4390-B50D-A6AEB36FDCC2@icloud.com>
2019-09-16  1:44       ` Jon Sterling

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=80a2be3b-afaa-4106-9c69-0df6567ec709@www.fastmail.com \
    --to=jon@jonmsterling.com \
    --cc=HomotopyTypeTheory@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).