-
Notifications
You must be signed in to change notification settings - Fork 48
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
Introduce S209 Circle with two origins #1159
Conversation
Yeah, one of these days, hopefully not too far off, I should get going on injectively path connected. |
I'm energized to help, especially since I used arc connected incorrectly in this recent MSE post and have been anxious about whether or not it's a good idea to bump it to the front page to correct it. |
Ok, I'll make a plan for deployment in the next few days, will add it to the relevant issue. |
@david20000813 No worries, but I was leaving it open to see if @prabau requested any changes to the description (since we had a bit of a discussion about it in the Issue page), before I move onto the circle with countably infinitely many origins. |
@GeoffreySangston I'll take a look anyway a little later. |
@GeoffreySangston Ah, sorry. I was just browsing through the PR list and saw that this one was approved two days ago and still hasn’t been merged yet. I wasn’t aware of the discussion in the issue and there wasn’t any discussion here, so I thought it was simply that you haven’t had the time to see this being approved and perform the merge due to the holidays. My apologies for this. |
@GeoffreySangston I took a look. The first paragraph is a good description. The second paragraph was slightly confusing maybe, just after having read the first paragraph. Since the origin point For the third paragraph, after having discussed "open extension", "closed extension", and other types of "extension" in other discussions, I was at first wondering what kind of other extension the Alexandroff one was. Then I suddenly remembered it was another name for one-point compactification. Background: Thoughts? |
I strongly disagree for the reasons I've already stated. For many people "compactification" includes Hausdorff in its definition. The "the" in the name "the one-point compactification" refers to fact that there is only one compactification which extends a space by one point, only one Hausdorff compactification that is. We could settle for calling it "a one-point compactification" but then this is not precise for what exactly the relation between those spaces is, and as mentioned before, many people restrict the name "compactification" to mean "Hausdorff compactification". I disagree for making things general for the sake of generosity alone. Sure, pi-base includes spaces which are not even |
One constraint is the desire to follow the structure of the description of Line with two origins. The issue is I'm conflating an equivalence class with a representative. To do it properly I think I would have to add text to the first paragraph, but when I tried to do that just now it seemed strictly worse, so I've deleted that attempt and added the current small change.
I did not know Alexandroff extension is from Willard. (Solomon Leader actually uses it in a paper predating Willard for a construction which sounds similar, but applies to a different kind of object called a 'local proximity space'.) (I'm pretty agnostic as to whether or not we call this "Alexandroff extension", or "Alexandroff one-point compactification". Edit: "alexandroff extension" appears a few times, but not in particularly important sources for this question I think. "Alexandroff one-point compactification" is much more common, even when discussing non-Hausdorff spaces. I guess I'm undecided now. It comes down to deciding whether compactifications must be Hausdorff in pi-base. @StevenClontz do you have an opinion?) I was always under the impression that "one-point compactification" is just a name for the famous construction. This also appears to be frequently called "Alexandroff one-point compactification". E.g., Ronald Brown's book on Groupoids has an exercise about "Alexandroff 1-point compactifications" without apparently restricting to Hausdorff spaces. I don't doubt the claim that it's standard to restrict 'compactification' to include Hausdorff. I'm agnostic as to whether pi-base does or not, since it's simply a matter of adding in the adjective 'Hausdorff' to compactification. Some evidence for either view appears in Encyclopedia of General topology, which has articles with either convention:
|
@Moniker1998 You make a good point. There may indeed be many one-point compactifications of a space, that is compactifications obtained by adding one point to the original space. So it's not a good idea to talk about "the one-point compactification". Better use "Alexandroff one-point compactification", which does not have this ambiguity, and which also seems to be widely used. As for the term "compactification" in general, Engelking uses compact to mean compact Hausdorff, so for him any compactification should be Hausdorff, and only Hausdorff spaces to start with can even hope to have a compactification in this sense. Authors who only care about Hausdorff spaces will follow that without problem. But I agree with @GeoffreySangston and the sources cited that if we don't assume compact means compact Hausdorff, it makes sense to talk about compactification in general (i.e. compact spaces containing the original space as a dense subspace). And the Alexandroff one is a perfectly well defined special case of it. |
For the second paragraph, I still don't like the mod 2-pi business. I think one way that would satisfactorily indicate what is meant, coming right after the first paragraph, would be: ... exactly when (with quotes around origin, to make the reader pause for a second). Possibly also add quotes around it in the first paragraph? We may be overthinking this. |
I edited those in (please edit the second paragraph issue directly if it's still not up to snuff @prabau, if you don't mind). If @Moniker1998 still rejects the "Alexandroff one-point compactification" idea, then we may need another opinion. @StevenClontz? |
Let's move discussion of the term "compactification" to #1174. |
@prabau I was referring to my updates addressing your suggestions:
|
@GeoffreySangston Sure, but sorry I am lost. Did you mean that you edited in place another comment in this conversation? Link? Or some other PR or issue? |
@prabau Oh sorry about that. I meant with the PR as it stands right now. Except the commit I thought I submitted must not have gone through (or more likely I got distracted right when I finished it). Let me try again. Hmm. Well I see the issue. It says 'Unable to commit' when I commit. I must have clicked 'Commit & Push' and assumed it went through. Ah right. It's because this was already merged and closed. |
I'm just going to delete the branch and go with a new one to keep things simple. |
Part of #675
This space will be a good counterexample for distinguishing injectively path connected from arc connected, when that gets changed + added.
Just going to leave it to the currently added traits for this PR (unless any others are requested, also requesting the removal of any traits for now is fine too). The main thing for this PR is getting the right description mostly in order.