categories - Category Theory list
 help / color / mirror / Atom feed
From: Christian Sattler <sattler.christian@gmail.com>
To: Thomas Streicher <streicher@mathematik.tu-darmstadt.de>
Cc: Jon Sterling <jon@jonmsterling.com>,
	Richard Garner <richard.garner@mq.edu.au>,
	 David Roberts <droberts.65537@gmail.com>,
	categories@mq.edu.au
Subject: Re: Fibrewise opposite fibration
Date: Thu, 1 Feb 2024 12:26:16 +0100	[thread overview]
Message-ID: <CALCpNBr-_UVJFifs5Pe5Vcys1qBXOydRD9uRhVU2phU-HNYV0A@mail.gmail.com> (raw)
In-Reply-To: <Zbt7UxPYa9DSxx2x@mathematik.tu-darmstadt.de>

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

I think there is a problem with this analogy. A basis for a vector space is actual (higher) data, but a cleavage for a fibration is property-like data.

Morphisms of fibrations that weakly preserve the cleavage are just morphisms of fibrations.

Morphisms of vector spaces that preserve a chosen basis are very different from just morphisms of vector spaces.

On Thu, 1 Feb 2024, 12:07 Thomas Streicher, <streicher@mathematik.tu-darmstadt.de<mailto:streicher@mathematik.tu-darmstadt.de>> wrote:
Dear Jon,

for constructing the opposite of a fibration you do not need at all
that the chosen cleavage is split. It is easy to see that fixing the
cartesian arrow also fixes the vertical arrow.

If everybody is happy with this solution I am fine. It is in the same spirit
as chosen pullbacks or chosen finite limits.
The reason for my reluctance is that nobody would consider as a
natural notion a vector space with a chosen basis.
The virtue of strong choice is that then such additional structure can be
pulled out of the hat at demand.


Thomas


You're receiving this message because you're a member of the Categories mailing list group from Macquarie University. To take part in this conversation, reply all to this message.

View group files<https://outlook.office365.com/owa/categories@mq.edu.au/groupsubscription.ashx?source=EscalatedMessage&action=files&GuestId=4eb9b40c-9b3a-48a5-9781-836e5a171e8b>   |   Leave group<https://outlook.office365.com/owa/categories@mq.edu.au/groupsubscription.ashx?source=EscalatedMessage&action=leave&GuestId=4eb9b40c-9b3a-48a5-9781-836e5a171e8b>   |   Learn more about Microsoft 365 Groups<https://aka.ms/o365g>


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

  parent reply	other threads:[~2024-02-01 20:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28  0:51 David Roberts
2024-01-28 11:54 ` Jon Sterling
2024-01-28 20:03   ` Thomas Streicher
2024-01-30  6:42     ` David Roberts
2024-01-31  0:35       ` Richard Garner
2024-01-31 19:31         ` Christian Sattler
2024-01-31 23:41           ` streicher
2024-02-01  4:48             ` Martin Bidlingmaier
2024-02-01  9:43             ` Jon Sterling
2024-02-01 11:06               ` Thomas Streicher
2024-02-01 11:18                 ` Jon Sterling
2024-02-01 11:46                   ` Thomas Streicher
     [not found]                     ` <ZbuFZoT9b9K8o7zi@mathematik.tu-darmstadt.de>
2024-02-02 10:11                       ` Thomas Streicher
2024-02-01 11:26                 ` Christian Sattler [this message]
2024-02-09  0:02 ` Dusko Pavlovic
2024-02-09  1:48   ` Michael Barr, Prof.
2024-02-09 19:55     ` Dusko Pavlovic
2024-02-10  6:28       ` David Roberts
2024-02-10  8:42         ` Jon Sterling
2024-02-09 11:25   ` Fibrewise opposite fibration + computers Sergei Soloviev
2024-02-09 20:25     ` Dusko Pavlovic
2024-02-12 13:20   ` Fibrewise opposite fibration Nath Rao
2024-02-13  8:16     ` Jon Sterling
2024-02-13 10:04       ` Thomas Streicher
2024-02-13 10:56         ` Jon Sterling
2024-02-13 11:38           ` Thomas Streicher
2024-02-13 11:53             ` Jon Sterling
2024-02-13 12:18               ` Thomas Streicher
2024-02-13 16:35                 ` Thomas Streicher
2024-02-23  1:50                   ` Dusko Pavlovic
2024-02-23  1:52                     ` Dusko Pavlovic
2024-02-23  1:42     ` Dusko Pavlovic
2024-02-26  7:31       ` Dusko Pavlovic

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=CALCpNBr-_UVJFifs5Pe5Vcys1qBXOydRD9uRhVU2phU-HNYV0A@mail.gmail.com \
    --to=sattler.christian@gmail.com \
    --cc=categories@mq.edu.au \
    --cc=droberts.65537@gmail.com \
    --cc=jon@jonmsterling.com \
    --cc=richard.garner@mq.edu.au \
    --cc=streicher@mathematik.tu-darmstadt.de \
    /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).