You're reading the public-facing archive of the Category Theory Zulip server.
To join the server you need an invite. Anybody can get an invite by contacting Matteo Capucci at name dot surname at gmail dot com.
For all things related to this archive refer to the same person.
I learned a little about the principle of equivalence recently, and in that context I was thinking about the definition of a path. I'm hoping to understand better, through this example, when picking a specific object among isomorphic objects is fine, and when we'd prefer to not make such a choice.
We might define "a path in " to be a continuous function , where has the usual subspace topology and is some topological space. Accepting this definition, the following sentence is a true statement about : "A continuous function from to is a path in ".
Now, let be some topological space that is isomorphic (homeomorphic) to in , with . Using the definition above, the following sentence about is false: "A continuous function from to is a path in ".
So, we have , but the truth values of and are not equal or even isomorphic in some appropriate partially ordered set of truth values. Does this violate the principle of equivalence?
Motivated by this, I am wondering if it would be more in the spirit of the principle of equivalence to define "a path in " like this: a path in is a continuous function , where is some topological space isomorphic to the unit interval . Is this an approach that people sometimes take?
Any thoughts on these specific questions, or more generally on the topic of selecting a specific object when isomorphic alternatives exist, would be most welcome.
David Egolf said:
So, we have , but the truth values of and are not equal or even isomorphic in some appropriate partially ordered set of truth values. Does this violate the principle of equivalence?
Yes. More objectively - since "principles" are not the same as mathematical facts, and it's often nice to state facts - we can say that you have defined a map from the class of topological spaces to the set of truth values, but this does not extend to a functor from the category of topological spaces to the poset of truth values, since it maps isomorphic topological spaces to nonisomorphic topological spaces.
There are various ways to "fix" this. But the most popular, in math and especially computer science, is simply to avoid talking about this sort of map . What do you plan to do with it, anyway?
Does anyone ever want to say "If is a space such that a map from to any space is a path in , then..."?
I never need, or even desire, to say such things.
After all, this is a long-winded way of saying "If , then..."
So in fact I think we should focus on the statement , or for that matter any statement of equality between objects.
In category-influenced mathematics we avoid such statements when they are used as a [[propositional equality]]. Note this is different from a [[definitional equality]]. For example it's fine to we say
Let ...
when we want a short name for something.
David Egolf said:
Motivated by this, I am wondering if it would be more in the spirit of the principle of equivalence to define "a path in " like this: a path in is a continuous function , where is some topological space isomorphic to the unit interval . Is this an approach that people sometimes take?
This is an interesting idea, but I think if you try using it for something you'll see it's not very useful.
Suppose I have such a path in : that is, a continuous function from some unknown space that is isomorphic to the unit interval to . What can I do with it? Not much!
It's like saying "You have $1,000,000 in some mailbox, somewhere in the universe". Try spending it.
It depends on what you mean by “is” and . There are a bunch of angles to tackle this question.
For instance, in HoTT, there simply is not any that is isomorphic to but is not equal to , since equality and homeomorphism coincide for topological spaces.
Additionally, if you take “is” to mean in HoTT, the proposition “A continuous function from to is a path in ” is true for all spaces homeomorphic to as well. But I generally think that you want definitions to be something stricter than propositional equality (pardon the Type Theory jargon) ...
Neglecting HoTT for a moment, what do we care about in the choice of ? I think you would agree that we don't care about the specific numbers: would work just as well, too. But I think being _merely_ isomorphic is too weak: we do want to be able to work with the endpoints, to say that a path starts at a known point and ends at a known point. If you don't know what the isomorphism is, you cannot say which point is the start and which the end, so I might suggest a tweak to your second definition that makes it remember the end points at least.
You can make my last point more formal by talking about path induction and stuff in HoTT, but I don't want to type out the details at the moment. It's the difference between (which is provably equal to ) and (which is not, due to the propositional truncation of the equality).
If you want “is” to mean a definitional equality, my first comment would be that it's customary to write the thing you are defining on the left: “A path in is a continuous function from to ”.
From that point of view, it is true that if you define path that way, then other equalities fail to hold definitionally, like “A path in is a continuous function from to ” fails to hold, since is not definitionally equal to .
But that is at the meta-theoretic level: within the logic you are working in, you cannot observe a “lack of definitional equality”. It just doesn't make sense to ask that. (Such as for the reason that we know that definitional equality is an under-approximation of equality in the theory.) This is the difference between “judgment” and “proposition”, where that distinction makes sense. Propositions can be negated, judgments cannot (except at a meta-theoretic level).
John Baez said:
David Egolf said:
Motivated by this, I am wondering if it would be more in the spirit of the principle of equivalence to define "a path in " like this: a path in is a continuous function , where is some topological space isomorphic to the unit interval . Is this an approach that people sometimes take?
This is an interesting idea, but I think if you try using it for something you'll see it's not very useful.
Suppose I have such a path in : that is, a continuous function from some unknown space that is isomorphic to the unit interval to . What can I do with it? Not much!
It's like saying "You have $1,000,000 in some mailbox, somewhere in the universe". Try spending it.
Maybe I didn't say it right, but I think what I wanted to say was this: To specify a path in according to my proposed definition, you must specify a space and a continuous function , where is isomorphic to . One way to specify could be by providing an isomorphism to it from . (But the idea is that you don't have to pick , you can pick a different from as long as it is isomorphic to ).
Hmmm. This is tricky to think about. I suppose we talk about an arbitrary path without actually specifying . Maybe I shouldn't be asking for specification of the , but only require a specification of ? I don't feel like I have a clear way of thinking about this kind of thing yet.
Verity Scheel also brings up the good point that we want to be able to talk about the "endpoints" of . I'd have to think about ways to manage that. If we require a specified isomorphism from to , that could provide a way to talk about endpoints, for example.
And thank-you both for sharing the concepts of "propositional equality" and "definitional" equality". Those seem like interesting and important concepts to absorb!
I also wonder if it could be interesting to define a path in as an isomorphism class of continuous maps to , such that the isomorphism class contains a continuous map from to . (Drawing inspiration from the definition of subobject). Although I'm not sure how to evaluate if this is "better" than the above proposed definition.
I think if you don't have the isomorphism specified between and your specified, you can still work with some topological notions like path-connected (where the specific path and even the choice of endpoints does not matter), but not other uses of paths.
Also, I'm pretty sure that in set-theoretic foundations, if you specify both your space and the isomorphism between and you get way too much data in there. Why would your usage of the path care about the particular topological space the path uses? (HoTT solves this, via path induction, but maybe you don't want to commit to that as a foundation, and I'm not sure how it could be handled in set theory exactly.)
Verity Scheel said:
Also, I'm pretty sure that in set-theoretic foundations, if you specify both your space and the isomorphism between and you get way too much data in there. Why would your usage of the path care about the particular topological space the path uses? (HoTT solves this, via path induction, but maybe you don't want to commit to that as a foundation, and I'm not sure how it could be handled in set theory exactly.)
I'm trying to understand what you are saying. Is the idea that we could pick , or pick , and - as long as both are given with a specified isomorphism to - we should be able to work with the resulting path just as well? If that is so, it does seem undesirable to have this additional data of specifying a specific as our choice of space the path is mapping from.
If we instead define a path in to be an isomorphism class of continuous functions to - so we specify one continuous function from each isomorphic to - maybe we can avoid singling out a particular in this way.
Regarding homotopy type theory, it always intrigues me whenever it comes up, but it sounds like a lot of work to learn!
Yeah, I guess the right kind of quotient could work, but you need to be more careful about how you state it.
And at the end of the day, your isomorphism class is going to have a canonical representative, namely the standard definition of paths.
Returning to this:
Fix a topological space . Consider the set of triples where is a topological space, is a specified homeomorphism between and , and is a continuous function from to .
If you want to recover something that is equivalent to the usual definition of path you can do this: Define an equivalence relation on this set by iff . This is quite literally saying that the only thing that matters is the view of these paths via the usual definition .
You can have finer or coarser equivalence relations as well.
That makes sense! I think that condition implies that and both induce the same continuous function from to . So, it sounds reasonable to me to intuitively view them as essentially describing the same path.
It's interesting to note how this situation is different from the definition of a subobject in terms of equivalence classes. I hadn't fully appreciated that for each we don't just have a morphism from to ; we have a morphism from to together with a specified isomorphism from to , and that makes things a bit different. Thanks for helping to clarify that!
One nice thing about allowing different isomorphs of is that you can sometimes get stricter behavior. For instance, a Moore path in is a continuous map for some real number . Then if and are Moore paths with , we define their concatenation by if and if . This concatenation operation is then strictly associative and unital, with units being 0-length constant paths .
Mike Shulman said:
This concatenation operation is then strictly associative and unital, with units being 0-length constant paths .
Hang on, isn't isomorphic to ! So a Moore path is a smidge more general than the definition @David Egolf suggested.
Hah, yes, that's true. But you still get a strictly associative composition if you leave that one out.
You may also be interested in https://mathoverflow.net/q/92206/49.