categories - Category Theory list
 help / color / mirror / Atom feed
From: Sebastiano Vigna <vigna@dsi.unimi.it>
To: categories@mta.ca
Subject: Re: Undirected graphs
Date: Thu, 09 Mar 2006 07:56:00 +0100	[thread overview]
Message-ID: <1141887360.12171.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20060308150720.9D5D07375B@chase.mathstat.dal.ca>

On Wed, 2006-03-08 at 11:07 -0400, Robert Pare wrote:

> by 1 and 2, or just 2.) Which is nice but what about loops?
> The involution might fix a loop or not. So wouldn't we be
> getting undirected graphs with two kinds of loops, whole loops
> and semiloops? What am I missing?

Yes, you'll get two kind of loops. This explains why in topological
graph theory books sometimes you'll find a remark like "we will count
loops once" or "we will count loops twice" (in the first case, sometimes
loops are depicted as segments going out of vertices with a dashed
ending). The problem is that the standard representation for undirected
graphs (subsets of unordered pairs) fails to distinguish between the two
kind of loops. The presheaf representation makes this distinction
clear.

In most cases you can forget about this problem, but when studying
covering the difference is huge: a loop fixed by the involution is
covered by an edge, whereas a pair of loops exchanged by the involution
are covered by a line. We discussed this issue at some length in our
paper "Fibrations of graphs" (Discrete Math., 2002).

Ciao,

						seba






  reply	other threads:[~2006-03-09  6:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 15:07 Robert Pare
2006-03-09  6:56 ` Sebastiano Vigna [this message]
2006-03-10 17:17   ` Vaughan Pratt
2006-03-12  4:10     ` Vaughan Pratt
2006-03-13  0:51       ` F W Lawvere
2006-03-09 14:05 ` F W Lawvere
2006-03-10  8:07 ` Marco Grandis
  -- strict thread matches above, loose matches on Subject: below --
2006-03-09 17:38 Chris Wensley
2006-03-02 18:16 Dr. Cyrus F Nourani

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=1141887360.12171.6.camel@localhost.localdomain \
    --to=vigna@dsi.unimi.it \
    --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).