Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Yuhao Huang <temp....@gmail.com>
To: Homotopy Type Theory <HomotopyT...@googlegroups.com>
Subject: Define transport as the primitive operation of cubicaltt and derive composition from it?
Date: Fri, 3 Nov 2017 17:27:36 -0700 (PDT)	[thread overview]
Message-ID: <bfe0fe93-9be3-434e-9547-4323115c665d@googlegroups.com> (raw)


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

I've been reading the cubical type theory paper and experimenting with 
cubicaltt. 

In cubicaltt, we have the composition operation as one of the primitive 
operations. Given a path p from A to B, the transport is defined by 

    trans A B p a : B = comp p a []

My question is, can we define a primitive operation "transport" and derive 
comp from it?

For example, the comp in the following definition (using cubicaltt's syntax)

compUp (A B : U) (P : Path U A B) (a a' : A) (b b' : B) (p : Path A a a') 
(q : PathP P a b) (q' : PathP P a' b') : Path B b b'
  = <i> comp P (p @ i) [(i = 0) -> q, (i = 1) -> q']

can be replaced by 

compUp2 (A B : U) (P : Path U A B) (a a' : A) (b b' : B) (p : Path A a a') 
(q : PathP P a b) (q' : PathP P a' b') : Path B b b'
  = transport (<i> (Path (P @ i) (q @ i) (q' @ i))) p

and similarly for other comps. 

The way I understand the composition operation is, it's a transport with 
given boundary condition. So why not start with transport and define 
composition later? If this is doable then hopefully equality judgements for 
transports are simpler than that of compositions.


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

             reply	other threads:[~2017-11-04  0:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04  0:27 Yuhao Huang [this message]
2017-11-05 15:09 ` Anders Mörtberg

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=bfe0fe93-9be3-434e-9547-4323115c665d@googlegroups.com \
    --to="temp...."@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).