The first time we used 410 was to indicate that a historical forecast limits snapshot was no longer on the TROLIE server and may have been moved to the archive. In that case the use case was very clear, and the implementation burden wasn't high since nominating a historical forecast only relied on the clock, not keeping around knowledge of old opaque identifiers.
Since then we seemed to have lost the ability to nominate a historical forecast limits snapshot, and we've proliferated the use for 410 in some spurious cases (possibly copy/paste).
The first time we used 410 was to indicate that a historical forecast limits snapshot was no longer on the TROLIE server and may have been moved to the archive. In that case the use case was very clear, and the implementation burden wasn't high since nominating a historical forecast only relied on the clock, not keeping around knowledge of old opaque identifiers.
Since then we seemed to have lost the ability to nominate a historical forecast limits snapshot, and we've proliferated the use for 410 in some spurious cases (possibly copy/paste).