Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Vladimir Voevodsky <vlad...@ias.edu>
To: Paolo Capriotti <pa...@capriotti.io>
Cc: "Prof. Vladimir Voevodsky" <vlad...@ias.edu>,
	Benedikt Ahrens <benedik...@gmail.com>,
	Univalent Mathematics <univalent-...@googlegroups.com>,
	homotopytypetheory <homotopyt...@googlegroups.com>
Subject: Re: [UniMath] Re: [HoTT] about the HTS
Date: Fri, 24 Feb 2017 09:36:49 -0500	[thread overview]
Message-ID: <FAECD168-CDCC-4DC2-8968-3CEB59D26E71@ias.edu> (raw)
In-Reply-To: <87k28fek09.fsf@capriotti.io>

The slice category over P is equivalent to presheaves on the category of elements of P. What is your definition of the category of elements of $P$? Objects are pairs $(X:C,p:P(X))$, and morphisms from $(X,p)$ to $(X’,p’)$ are…?

> On Feb 24, 2017, at 9:33 AM, Paolo Capriotti <pa...@capriotti.io> wrote:
> 
>>> On Feb 23, 2017, at 1:52 PM, Benedikt Ahrens <benedik...@gmail.com> wrote:
>>> Section 1.4.8 "Equality" gives an informal account and points to several
>>> precise definitions.
>>> On page 43 two equality types are considered, one intensional one and
>>> one with reflection rule.
> 
> I haven't actually considered something like what Vladimir suggested, though.  In the systems that I described in my thesis, exact equality is defined for every type.
> 
> Vladimir Voevodsky writes:
>> BTW It is a little dangerous to define presheaves as functors C -> Sets^{op}. While it gives the correct objects, the morphisms between presheaves are not morphisms in the category of functors C -> Sets^{op} but in the opposite category.
> 
> Ah, right.  The reason why I defined presheaves this way is that you can just say that the slice category over a presheaf $P$ is presheaves over the category of elements of $P$, rather than copresheaves, so it's more uniform and certain proofs become a little bit nicer.  Of course, one could start with C^{op} and use copresheaves throughout, but then I think things would get quite confusing with the Yoneda embedding.
> 
> But thanks for pointing out this problem.  Somehow, it had never occured to me that natural transformations are going in the wrong direction with my definition.
> 
> Paolo
> 
> -- 
> You received this message because you are subscribed to the Google Groups "Univalent Mathematics" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to univalent-mathem...@googlegroups.com.
> To post to this group, send email to univalent-...@googlegroups.com.
> Visit this group at https://groups.google.com/group/univalent-mathematics.
> To view this discussion on the web visit https://groups.google.com/d/msgid/univalent-mathematics/87k28fek09.fsf%40capriotti.io.
> For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2017-02-24 14:36 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           ` Vladimir Voevodsky [this message]
2017-02-24 15:06             ` [UniMath] " 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
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=FAECD168-CDCC-4DC2-8968-3CEB59D26E71@ias.edu \
    --to="vlad..."@ias.edu \
    --cc="benedik..."@gmail.com \
    --cc="homotopyt..."@googlegroups.com \
    --cc="pa..."@capriotti.io \
    --cc="univalent-..."@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).