categories - Category Theory list
 help / color / mirror / Atom feed
From: Krzysztof Worytkiewicz <krisw@bluewin.ch>
To: categories@mta.ca
Subject: Re: associated sheaf functor
Date: Wed, 17 Sep 2003 13:41:25 +0200	[thread overview]
Message-ID: <3F684865.4040808@bluewin.ch> (raw)
In-Reply-To: <Law10-F41jkO22ZhCl8000005f4@hotmail.com>


> I don't quite understand this question.
> I was interested since I am looking at the plus construction as part
> of my work at the moment.

Let P be a presheaf on the site (C,J) and consider the "classical" plus
construction

  P^+(c) = colim_{R \in J(c)}Match(R,P)

where Match(R,P) is the set of matching families for the cover R \in
J(c) and the colimit is taken over J(c) ordered by reverse inclusion
(cf. McLane & Moerdijk) . This is a nice filtered colimit so x \in
P^+(c) can be expressed as an equivalence class of matching families.

 Suppose now that J is given by a basis K. It is not immediately clear
(at least not for me) what happens in a variant of the above where
Match(R,P) is taken as the set of matching families for the K-cover R.
Indeed, the notion of "common refinement"  for K-covers is not as handy
as the one for J-covers for the task at hand since op-ordering K-covers
will not necessarily give a filtered category. The other obvious
candidate for a "category K(c)" where a factorisation witnessing a
refinement (of K-covers) is a morphism (in the opposite category) will
probably fail to be filtered as well, so I wondered if anybody allready
looked at such things.

I agree that a one-sentence prose might have been a bit messy...

Cheers

Krzysztof






       reply	other threads:[~2003-09-17 11:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Law10-F41jkO22ZhCl8000005f4@hotmail.com>
2003-09-17 11:41 ` Krzysztof Worytkiewicz [this message]
2003-09-16 17:12 Krzysztof Worytkiewicz

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=3F684865.4040808@bluewin.ch \
    --to=krisw@bluewin.ch \
    --cc=categories@mta.ca \
    /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).