-
Notifications
You must be signed in to change notification settings - Fork 82
Anodyne maps #1361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anodyne maps #1361
Conversation
How are the changes to descent related to anodyne maps? I can't see from just reading the changes on GitHub where you need those. |
I've continued work in this branch after the initial work on anodyne maps concluded, since subsequent work depends on this and it tends to take a long while for my work to be reviewed. I'm hoping to formalize Mather's second cube theorem. By the way, how do you feel about renaming "descent data of pushouts" to "reduced descent data of pushouts"? So we can name the thing with an additional family |
If someone is willing to review my work on anodyne maps then I'm happy to move the changes to descent data of pushouts to a different branch |
The changes to |
I've preemptively moved the new changes to a different branch |
I don't see a reason to. The current development uses this definition, and the cube theorems talk about cartesian transformations. |
The proposed definition seems more useful to me, and mirrors the signature of the underlying diagram. For instance, I'm currently working on formalizing the flattening lemma for (expanded) descent data of pushouts, since that's the formulation I need for Mather's cube theorem. |
An alternative is to call the type with two equivalences "equifibered spans", precisely because they mirror the shape of a span. For sequential colimits the two notions agree, and the SvDR paper uses "equifibered sequences", so |
Ah, yep, that works, thanks! |
@VojtechStep Hi again. I read a little up on the origin of the terminology, and being "equifibered" is a property of a natural transformation/display/dependent structure, not the structure itself. I.e., a span can't be "equifibered", but a dependent or displayed span can be, i.e., a span can only be equifibered relative to some other span. In particular, every span is equifibered over itself. This seems to be inconsistent with how you've implemented the terminology in the library. What's the justification for the current terminology usage? |
If you want a noun for such a structure, one might speak of an equifibration over a span, or equifibration of spans. |
I was suggesting that if you have a span See that |
What you have formalized is an "equifibered dependent sequential diagram", which is different from an equifibered sequential diagram over a sequential diagram, i.e., a morphism of sequential diagram |
Sorry, let me elaborate a little. I think the disambiguation/elaboration matters, as the term "equifibered" is not that common, at least, I had not heard of it before, and it sounds similar to other unrelated concepts like "equivariance" and "isofibration". By omitting key terms like "dependent" or "displayed", or "over", the meaning and usage of the term was not clear to me, and I suspect it might not be to others either. |
There's precedent for calling dependent structures "fibered"/"over" and their instantiation at a point Unless you envision formalizing fibers of general morphisms of sequential diagrams and spans, I would strongly prefer to keep the current naming scheme. And even if you do, I'm inclined to believe that they would be less useful/convenient to work with, since by talking about fibers you raise the dimension of identifications you need to care about — I experimented recently with sections of unstraightened fibered sequential diagrams, and it was very painful. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Defines anodyne maps and weakly anodyne maps and establishes some basic closure properties.