Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Jasper Hugunin <jasperh@cs.washington.edu>
To: HomotopyTypeTheory@googlegroups.com
Subject: Re: [HoTT] Semantics of QIITs ?
Date: Mon, 20 May 2019 19:45:13 -0700	[thread overview]
Message-ID: <CAGTS-a9F-8ph2U4MoPFaoTHam0SCTg3YZWAEJAjyLrrbBd71sw@mail.gmail.com> (raw)
In-Reply-To: <64897263-717c-4596-9397-76f03b4e1c38@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 3378 bytes --]

Hello all,

To confirm what others have said about my construction:
As Andras and Jon noted, it remains open whether the construction can be
extended to reduce higher inductive-inductive types to higher inductive
types, but I am hopeful that it can, at least in a situation such as CTT
where the eliminator computes on path constructors.
As Matt noted, the general recursive-recursive eliminator is both essential
(for proving initiality, for example) and missing. This is the same
restriction as on the construction in extensional type theory (or using
UIP) given by Nordvall Forsberg. The main obstacle I see to getting the
general recursive-recursive eliminator is that the simple eliminator is not
strict, but only computes up to a path. I think I see a way to turn a
strict simple eliminator into a general eliminator, but this is still
conjectural.

To summarize my understanding of the original question, QIITs are an
obvious subset of HIITs, and we know how to handle many HITs primitively in
cubical type theory, but the extension to primitive HIITs in cubical type
theory has not been done, nor does my construction immediately allow
reducing HIITs to HITs (and even if extended lacks strictness and
generality of the eliminator).

Best regards,
- Jasper Hugunin

On Mon, May 20, 2019 at 5:28 PM Matt Oliveri <atmacen@gmail.com> wrote:

> I'm not completely satisfied with Hugunin's technique, because it
> justifies only the "simple" elimination principle, rather than the general,
> "recursive-recursive" elimination principle implemented in Agda. As far as
> I can tell, realistic use cases for inductive-inductive families also need
> the recursive-recursive elimination principle, where the types of the maps
> out of later families depend on the maps out of earlier families. (I'm not
> sure how much of the other research on IIFs stops short of handling
> recursion-recursion, but I think it should be taken seriously.)
>
> On Monday, May 20, 2019 at 7:26:12 PM UTC-4, Jon Sterling wrote:
>>
>> Echoing Andras, I recall that a new encoding due to Jasper Hugunin enable
>> us to interpret IITs without using UIP, and it is an open question to
>> determine whether Jasper's ideas can be extended to QIITs. I hope they can,
>> and someone should find out :)
>>
>> Best,
>> Jon
>>
> --
> 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/64897263-717c-4596-9397-76f03b4e1c38%40googlegroups.com
> <https://groups.google.com/d/msgid/HomotopyTypeTheory/64897263-717c-4596-9397-76f03b4e1c38%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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 HomotopyTypeTheory+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/HomotopyTypeTheory/CAGTS-a9F-8ph2U4MoPFaoTHam0SCTg3YZWAEJAjyLrrbBd71sw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 4514 bytes --]

  reply	other threads:[~2019-05-21  2:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 14:57 Bas Spitters
2019-05-16 15:39 ` Thorsten Altenkirch
2019-05-16 15:50   ` Bas Spitters
2019-05-16 16:15     ` András Kovács
2019-05-16 18:50       ` Bas Spitters
2019-05-20 16:16         ` Thorsten Altenkirch
2019-05-20 17:54           ` Bas Spitters
2019-05-20 18:35             ` Thorsten Altenkirch
2019-05-20 19:59               ` Jon Sterling
2019-05-20 21:04                 ` Bas Spitters
2019-05-20 22:17                   ` Thorsten Altenkirch
2019-05-20 23:26                     ` Jon Sterling
2019-05-21  0:28                       ` Matt Oliveri
2019-05-21  2:45                         ` Jasper Hugunin [this message]
2019-05-21  8:33                         ` Thorsten Altenkirch
2019-05-21 19:56                           ` Matt Oliveri
2019-05-21  8:39                       ` Thorsten Altenkirch
2019-05-21 11:47 ` [HoTT] " Andrew Swan
2019-05-21 12:14   ` Bas Spitters

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=CAGTS-a9F-8ph2U4MoPFaoTHam0SCTg3YZWAEJAjyLrrbBd71sw@mail.gmail.com \
    --to=jasperh@cs.washington.edu \
    --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).