DDS12 — PIM and PSM contradicting wrt "get_sample_lost_status" operation

PIM and PSM are contradicting with respect to the "get_sample_lost_status" operation.

Summary:
According to the PIM in section 2.1.2.5.2(.12), the Subscriber class has got an operation called "get_sample_lost_status". According to the PSM in section 2.2.3, this operation is not part of the Subscriber, but of the DataReader.

Proposed Resolution::
Move the "get_sample_lost_status" operation in the PIM to the DataReader as well.
RTI: We propose ewmoving this from the Subscriber altoguether and moving it to the DataReader.

Proposed Revised Text::

In the Subscriber table in section 2.1.2.5.2 Subscriber Class
Remove the entry on the operation get_sample_lost_status()

In the DataReader table in section section 2.1.2.5.3 DataReader Class
Add the entry on the get_sample_lost_status() operation that was removed from the Subscriber class

Add section 2.1.2.5.3.24, previous 2.1.2.5.3.24 becomes 2.1.2.5.3.25:
2.1.2.5.3.24 get_sample_lost_status
This operation allows access to the SAMPLE_LOST_STATUS communication status. Communication statuses are described in Section 2.1.4.1, "Communication Status," on page 2-125.

Move the operation from the Subscriber to the DataReader