From: henry@phare.normalesup.org
To: "David Yetter" <dyetter@ksu.edu>
Cc: "Categories list" <categories@mta.ca>
Subject: Re: Partial functors ..
Date: Wed, 18 Mar 2015 09:44:45 +0100 [thread overview]
Message-ID: <E1YYD6g-0006YP-Gy@mlist.mta.ca> (raw)
In-Reply-To: <E1YXue5-0006Gx-3h@mlist.mta.ca>
I don't this this works: if (g .g') is in the domain of the partial
functor and g is not, then g will be sent to 0 by the extension of the
partial functor, hence g.g' will also be sent to 0 which shouldn't be the
case because it is in the domain of the functor.
Also it is not entirely clear to me if the original question wanted
functor defined on a full subcategory or on an arbitrary sub-category. But
in both case, my opinion would be that the only reasonable notion is to
talk about "partial natural transformations" which are defined on a
subcategory included in the domain of definition of both functor (and
hence are natural transformation between ordinary functor).
Best wishes,
Simon Henry.
> The previous suggestion of considering functors to D + 1 was a false start
> for reasons Fred and Uwe pointed out, but it suggests a better approach:
> consider functors to the category D~ formed from D by freely adjoining a
> zero object. Arrows not in S now have somewhere to go (the zero arrow
> with the appropriate source and target).
>
> I think at the one-categorical level, taking Hom(C,D) to be the
> zero-preserving functors from C~ to D~, and letting C and D range over all
> small categories gives a category isomorphic to that of small categories
> with partial functors as arrows.
>
> Natural transformations between (zero-preserving) functors from C~ to D~
> would
> then give a reasonable notion of partial natural transformations. It
> certainly captures some, at least, of the natural transformations "more
> partial" than their source functor, since there will be a zero natural
> transformation between any two partial functors, corresponding to a
> "defined nowhere" partial natural transformation when zero-ness is
> interpreted as undefined as it was in the correspondence between
> zero-preserving functors from C~ to D~ and partial functors from C to D.
>
> I'm not sure how this fits with the restrictions Robin points out. It
> seems to allow more partial natural transformations than Robin's
> observation, since zero arrows can fill in whenever the image object under
> either the source or target functor is undefined, a partial natural
> transformation to be a natural transformation between the restrictions of
> the two partial functors to the intersections of their domain of
> definition (or a subcategory thereof).
>
> Best Thoughts,
> David Yetter
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next prev parent reply other threads:[~2015-03-18 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 23:12 Robin Cockett
2015-03-17 15:04 ` David Yetter
2015-03-17 19:08 ` Giorgio Mossa
2015-03-17 20:31 ` Robin Cockett
2015-03-17 21:05 ` Sergei Soloviev
2015-03-18 0:47 ` Ross Street
2015-03-18 21:36 ` Steve Lack
2015-03-18 8:44 ` henry [this message]
2015-03-18 7:03 Fred E.J. Linton
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=E1YYD6g-0006YP-Gy@mlist.mta.ca \
--to=henry@phare.normalesup.org \
--cc=categories@mta.ca \
--cc=dyetter@ksu.edu \
/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).