My last message was stupid. Please ignore. :)
What I was _trying_ to get at was this:
There Exists a Function which Relates en => de.
Ie. When you write down /en/de/ you are suggesting that in order to go
to de, you have to go through en. That is, you start at 'en' (the
original document) and end up at 'de' (the translated document). This
is true.
In the case of Lat/Long, there is no function which relates the two like
this. A Lat,Long pair stands by itself and doesn't have a function in
itself which relates the two. It's just a dot on a map. You can just
as easily get to the same point on the map by referencing the
coordinates in Lat,Long format as Long,Lat format. By convention, we
typically use Lat,Long, but that's not to stop the correct
interpretation either way.
The point is, writing .../jobs/en,de doesn't portray the relational
aspect of en and de to _me_.
It's obviously possible that it can portray that relational information
to someone else. Possibly formal Mathematicians, etc. Instead, what
en,de says to me is that their pair go together just like a point on a
map. There is more to their relationship than that, that's why I like
the slashes for this case.
Later,
Adam
Adam Taft wrote:
Erik Hetzner wrote:
That is a hierarchy, so it should use slashes. Longitude,latitude is
not a hierarchy but a tuple, and they suggest for this commas.
So:
Longitude,Latitude == Latitude,Longitude ??
I'm legitimately asking. It does in real life, right? Same with things
like x,y coordinates, etc.
If so, then I agree, commas make sense. However, if it's the case that
Long,Lat != Lat,Long, then I say there is an implied hierarchy.
In this thread's case: en,de != de,en
This is why /en/de/ makes sense.
Adam
