Ich said:
Synchronizing the frame clocks according to the Einstein convention, you define the directions orthogonal to the four velocity of the observer. Comparing the moving clock with a frame clock thus simply gives you the orthogonally projected length of B's unit time vector onto A's unit time vector.
I think you mean "parallel" here, not "orthogonal". Projections orthogonal to the observer's 4-velocity would give spatial vectors, not timelike vectors.
Ich said:
Comparing the moving clock with a frame clock thus simply gives you the orthogonally projected length of B's unit time vector onto A's unit time vector. That is, the dot product of their four velocities.
There are some complications here that affect how your interpretation generalizes.
First: the actual dot product involved is between the 4-velocity of a static observer at some finite radius and a moving observer at that same radius. (I think those are the ones you've been calling A and B.) The 4-velocity of a static observer at infinity, who is your "reference" observer, is spatially separated from A and B, and you can't take dot products between spatially separated vectors in curved spacetime.
However, since A happens to be static, there is a well-defined way to "convert" a dot product of B's 4-velocity with A's 4-velocity, to a sort of "effective dot product" of B's 4-velocity with the reference observer's 4-velocity: you just multiply by A's "redshift factor" relative to the reference observer. This is the product of the two invariants that you have been talking about.
But now let's ask a question: how does this computed "time dilation factor" for B compare to the actual redshift of light emitted by B and received by the reference observer? (We know they're the same for A, but A is static.) We'll idealize by imagining, not just a single reference observer, but a whole fleet of them, in a big sphere at infinity, so that no matter where B is in his orbit, he can always emit a flash of light radially outward and have it received by a reference observer. (We'll also ignore the fact that he has to aim the light at an angle to make sure it travels radially outward, because of aberration; he has a supercomputer that can calculate all that.)
Given all that, if B is in a circular orbit at a constant radius (the same radius as A), then I think the redshift of his light, when received by a reference observer, will be given by your "time dilation" factor--the product of A's "redshift factor" with B's time dilation relative to A. However, if B is in an elliptical orbit, so that he has nonzero radial velocity, I think this will
not be the case. The radial velocity leads to a Doppler shift that has to be included in the computation of the overall redshift.
(To see this in an extreme case, suppose that observer B is moving radially outward from A at exactly escape velocity--that is, he will eventually reach infinity and just be at rest there. If he emits light as he passes A, this light will have zero redshift when it reaches infinity--we know this because B's energy at infinity is equal to his rest mass, since he's moving at escape velocity, meaning he has zero "redshift factor". A would interpret this as the Doppler blueshift from his outward motion exactly cancelling the gravitational redshift from the change in altitude. But B's "time dilation" relative to A is still given by ##\sqrt{1 - v^2}##, so A still interprets B's clocks as "running slower" than his, even though an observer at infinity would say the opposite based on the respective redshifts of the light they emit.)