Clarification about significance of local ID attribute for historical data in OAM context

[kgkishore]

TAPI RIA needs to clarify the significance of local ID attribute for historical data in OAM context

[kgkishore]

@nigel-r-davis , Here is a brief understanding from our discussion about significance of local ID attribute, correct as needed

In the TAPI information model, the significance of the local-id attribute for historical Performance Monitoring (PM) data lies in its role as the mandatory structural identifier for a local data object

Specifically, its significance is defined by the following:
Contextual Uniqueness: Historical PM data is recorded within the history-data object, which the TAPI standard strictly models as a local object
By definition, a local object must include a local-id to serve as an identifier that is unique within the context of its parent GlobalClass (such as the specific cep-pm-data, mep-pm-data, or mip-pm-data container that holds the history data) from which it is logically inseparable

Targeted API Retrieval: While users conceptually differentiate historical records by their timestamps (as every history-data instance includes a mandatory period-start-time and period-end-time), the local-id is required for programmatic access. When a TAPI client queries specific historical performance values via RESTCONF operations, the local-id acts as the precise structural key used in the API path to identify, differentiate, and retrieve that exact record from the parent's data list