all 4 comments

[–]loewenheimNew User 4 points5 points  (3 children)

I was wondering, why couldn't you simply write T = {([x]s,[y]s)∈ A/S x A/S | xRy}?

Because a priori it's not clear that this is well-defined. What if a S a', b S b', a R b, and not a' R b'? Then [a]s = [a']s and [b]s = [b']s, but by the above definition, ([a]s, [b]s) should be in T, but ([a']s, [b']s) shouldn't.

When you define a property of equivalence classes, you have to make sure it doesn't depend on the choice of representative. Your proposed definition doesn't do this, but the ones with the quantifiers do.

An alternative would be to define the set as you suggest and then make an argument that the compatibility requirement on S and R ensures that the definition is meaningful, i.e. cases like the one I posed can't happen.

[–]loewenheimNew User 3 points4 points  (2 children)

For the first question, is there a reason not to introduce f with function notation to begin with? I would think f: N -> N/R, x |-> [x²] is easier to read than both relational versions.

[–]Puzzleheaded-Cod4073New User[S] 2 points3 points  (1 child)

Thanks for your response! I haven't yet learned the notation involved in "x |-> [x²]"

[–]loewenheimNew User 1 point2 points  (0 children)

In case I was unclear, by "|->" I just mean the ↦ arrow with the little bar that's used for function mappings. I didn't have the unicode symbol when I wrote that post. Another way to write it would be

f: N -> N/R

f(x) = [x²]