-
-
Notifications
You must be signed in to change notification settings - Fork 490
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
Category of open subsets of a topological space #31785
Comments
comment:1
Why do we need a category of open sets? Wouldn't it be better to represent the actual set of open subsets, i.e. the set-theoretic notion of topology? This is then an object of the category of topologies. As for the parent-element framework this would mean: the topology is the parent, and its elements are open subsets. |
comment:2
At least this would be helpful in view of #31703. |
comment:3
There are two possible ways to think about this. One is the category is the category of open subsets of |
comment:4
Okay, once again: why do we need this category? |
comment:5
When inclusions are maps, then the compatibility of restrictions of sections is the functorial property. |
comment:6
Now I see what you meant with functorial property. However, morphisms must be (well) defined between all objects in the category. But not all such morphisms can be inclusions. What are morphisms between 'non-compatible' subsets? |
comment:7
Or do we think of the Homset being empty in that case? |
comment:8
Ah, I suppose you see the open sets as posets again and you take the induced category, right? |
comment:9
But still, I don't see why we need this category. All we need then is the Homset between open subsets. I still favor implementing the topology as actual set, not as category. |
comment:10
Categories can be used a marker of properties of objects rather than having an explicit parameter (e.g., the finite-dimensional or finite versions of a category). It then later can be extended as a place to put common methods. Also, in case it isn't clear, it is okay to have the homset be empty. |
comment:11
Replying to @tscrim:
The only property we need is that of the homset. Isn't it a bit overkill to give it a whole category by itself? What does speak against a concrete implementation of the topology of a manifold, which comes in handy on many occasions, and then introducing a category of topologies? The homset between elements of the topology can then be established as induced by the poset structure of subsets. These homsets can still be implemented on the level of the category of topologies.
Yes, it is clear. But I just learned category theory and some things still confuse me at the first glimpse. |
comment:12
Example at hand:
I'd rather like to see open subsets as objects of the category of elements of a topology than giving it a bare category. |
comment:13
After a little chat with Travis, and a little thought myself, I think that Travis's latter proposal, i.e. seeing the category of open subsets as subcategory of subobjects of topological spaces, is indeed a good idea. The sheaf implementation is already on a good way and doesn't necessarily need a family structure (though it would be nice from a mathematical viewpoint imo). |
comment:14
Already made a proposal in #31703. This now relies on what happens here. Even though I still like the idea of the topology being realized as a set rather than a category more, I can live with that approach, too. |
Dependencies: #34461 |
We define the category of open subsets of a topological space.
CategoryWithParameters
A concrete implementation for open subsets of a topological manifold:
ManifoldSubsetFamily
instance that stores the equivalence class of named subsets that are known to be equalThis is preparation for #31703.
Depends on #34461
CC: @mjungmath @egourgoulhon @tscrim @tobiasdiez @mkoeppe
Component: categories
Issue created by migration from https://trac.sagemath.org/ticket/31785
The text was updated successfully, but these errors were encountered: