Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Vladimir Voevodsky <vlad...@ias.edu>
To: Paolo Capriotti <p.cap...@gmail.com>
Cc: "Prof. Vladimir Voevodsky" <vlad...@ias.edu>,
	Homotopy Type Theory <HomotopyT...@googlegroups.com>,
	benedik...@gmail.com, univalent-...@googlegroups.com
Subject: Re: [UniMath] Re: [HoTT] about the HTS
Date: Fri, 24 Feb 2017 10:10:12 -0500	[thread overview]
Message-ID: <BA7FCE30-297F-4450-8704-5C1CD4BCD8B5@ias.edu> (raw)
In-Reply-To: <ebf61361-d581-4a25-98cf-0e345e2e2035@googlegroups.com>

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

Our definition of the category of elements (cf. ElementsOp.v in UniMath/UniMath/Ktheory), and I think it is the standard one, is that morphisms are morphisms f:X -> X’ such that  p=P(f)(p’). Then all works as expected.


> On Feb 24, 2017, at 10:06 AM, Paolo Capriotti <p.cap...@gmail.com> wrote:
> 
> Vladimir Voevodsky writes:
> > 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…?
> 
> ...morphisms $f : C(X',X)$ such that $Pf(p) = p'$.
> 
> The slice category of the category of functors $A -> Set$ over a functor $F$ is equivalent to functors $el(F) -> Set$, right?  Now if you define presheaves as functors $C^{op} -> Set$, you get that presheaves on $C$ over a presheaf $P$ are equivalent to *functors* $el(P) -> Set$, not presheaves on $el(P)$.
> 
> That's why I was trying to be clever and use that unnatural definition of presheaves, but, as you pointed out, that doesn't work either, because the resulting category of presheaves is the opposite of what we want.
> 
> 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 <mailto:univalent-mathem...@googlegroups.com>.
> To post to this group, send email to univalent-...@googlegroups.com <mailto:univalent-...@googlegroups.com>.
> Visit this group at https://groups.google.com/group/univalent-mathematics <https://groups.google.com/group/univalent-mathematics>.
> To view this discussion on the web visit https://groups.google.com/d/msgid/univalent-mathematics/ebf61361-d581-4a25-98cf-0e345e2e2035%40googlegroups.com <https://groups.google.com/d/msgid/univalent-mathematics/ebf61361-d581-4a25-98cf-0e345e2e2035%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.


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

  reply	other threads:[~2017-02-24 15:10 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 [this message]
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=BA7FCE30-297F-4450-8704-5C1CD4BCD8B5@ias.edu \
    --to="vlad..."@ias.edu \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="benedik..."@gmail.com \
    --cc="p.cap..."@gmail.com \
    --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).