Newsgroups: sci.physics.research
From: b...@galaxy.ucr.edu (john baez)
Date: 1998/11/17
Subject: Re: Just Categories now
In article <72b3pd$...@gap.cco.caltech.edu>,
Toby Bartels <t...@ugcs.caltech.edu> wrote: Of course, part of the point of this puzzle is that the term >Given a functor U: C -> D, interpret U as a forgetful functor. "forgetful" is usually given no precise definition, so here we are seeking a precise definition. Usually people don't bother to define "forgetful functor" very precisely - like pornography, you're just supposed to know a forgetful functor when you see it. >Then C is D with extra *structure* if U is surjective on the objects I'm a little unhappy with this for two reasons: one nitpicky and one >and, given a pair of objects, injective on the morphisms between them [...] more serious. The nitpicky reason is that it's bad to care if a functor U: C -> D In general, the interesting properties of functors must be preserved However, the more serious reason I'm unhappy is that sometimes C-objects For example, consider the forgetful functor U: Vect -> Set where Vect Anyway, I think we should say that C-objects are D-objects with U: hom(x,y) -> hom(Ux,Uy) is injective. By the way, a functor with this property is called >[...] and C is D with extra *properties* if U is injective on the morphisms Hmm, again I'm unhappy for the same sort of nitpicky reason. Again, >(meaning injective on the objects and on the morphisms between a given pair); it's bad to care if U is injective on objects, because this property is not preserved by natural isomorphisms. I believe the politically correct substitute for this property is called "reflecting isomorphisms": we say a functor U: C -> D "reflects isomorphisms" if U(f) being an isomorphism in D implies that f is an isomorphism in C. In particular, nonisomorphic objects in C can't get sent to isomorphic objects in D by a functor that reflects isomorphisms. It seems that whenever C-objects are D-objects with extra properties, But I'd give a slightly different criterion for when C-objects are U: hom(x,y) -> hom(Ux,Uy) is 1-1 and onto. (If this map is always injective, we say it's Note that a fully faithful functor always reflects isomorphisms - Also note that the way I'm setting things up, "extra properties" >Otherwise, I guess C is just D with extra *stuff* Hmm, I wouldn't demand that. An example of "extra stuff" would >if, given a pair of objects, U is injective on the morphisms between them. be the functor U: Vect^2 -> Vect that takes a pair of vector spaces, or a pair of linear map, and discards the second one. In other words, I'd say a pair of vector spaces is a vector space "with extra stuff", namely another vector space. The functor U: Vect^2 -> Vect doesn't have the property you demand - i.e., it's not faithful. Now I forget if there is *any* property we should demand of U: C -> D >For example, the forgetful functor Groups -> Sets Let's check these examples: yes, U: Groups -> Sets is >shows that groups are sets with extra structure, >while the forgetful functor Abelian Groups -> Groups >shows that Abelian groups are groups with extra properties. faithful, while U: Abelian Groups -> Sets is fully faithful. >Or you can turn around and use the free functor Sets -> Groups Hmm, F: Sets -> Groups is faithful, but not full. Thus I'd >and say that sets are groups with extra properties >(to wit, the property of being free). say that a set can be viewed as a group with extra *structure*: namely, the property of being free together with the *structure* of a specific set of generators. The point is that not all homomorphisms between free groups come from functions between their set of generators. Fun stuff, eh? But I'm afraid it's drifting rather far afield You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| ||||||||||||||