Clarify XXXCall's StopPointRef

[leonardehrenfried]

Hello there, this is my first PR to this repo so be gentle. :)

I hit a problem with Estimated/RecordedCall's StopPointRef value in an Italian feed. It took a bit of back and forth to figure out what exactly it refers to but we got an agreement in the end: https://public.3.basecamp.com/p/TcEEP5WrNZJPBxrJU9GAjint

I would like to document what I learned so others can benefit from it.

Unfortunately I have no clue if I put the information into the correct place and whether the formatting is correct.

Therefore I request a rigorous review.

@ue71603 @Aurige

[skinkie]

Don't think basecamp links or profile implementations should be placed in here, hence it requires some rephrasing.

[leonardehrenfried]

cc @rcavaliere

The base branch was changed.

[leonardehrenfried]

Sorry, I seem to be unable to teach my editor to use the correct indentation and I also seem to have stripped emtpy line endings.

Is there an automatic formatting tool available?

[TuThoThai]

Needs to be reworked since the phrasing does not fit the group. Explanation: QUAYs must be referenced using QuayRef. Also, there is a bigger conversation about making clearer the StopPointRef

[leonardehrenfried]

Thanks for the review. I see that you assigned other people.

Presumably they will provide the precise documentation to use. Is this correct?

[TuThoThai]

@leonardehrenfried
Yes, it is correct. As it is a group effort, we will try to find some wording to propose and advance this PR together. 😄

[ue71603]

I disagree. We spent years makeing it very clear that this always is a SCHEDULED STOP POINT. No acceptance ever from me

[TuThoThai]

@ue71603, the group agreed that this PR will be reworked entirely with:

• clarification that a SCHEDULED STOP POINT is expected
• but also, in some cases, allow for QUAY and STOP PLACES

However, the new PR is very long to make as it needs to be carefully crafted for each SIRI Service, so I am keeping this one open as reminder to myself

[ue71603]

@TuThoThai I don't think this is the work group to redefine Transmodel. So, no.