Subscription services: datachange on localized text does not check preferred locale
Description
When a data change occurs on a LocalizedText value, the comparison is done for all the localized texts available and does not compare only the preferred locale for the subscription session It means that a data change notification will be triggered if any of the locales for the LocalizedText has been modified and even if the preferred locale of subscription session has no change (no change visible in new value notified).
Analysis
It is possible to interpret the comparison of values by getting the preferred locale for the LocalizedText before comparison. In this way we avoid to send a notification if there is no change for the preferred locale.