End users would like to have a standardized mechanisms which allows them to identify the published information without implementing other OPC UA mechanisms than PubSub. The information needed is the meaning of the data being sent, so not only the meta information but the semantical meaning.

Assuming a machine is publishing the process value of a temperature. Then they would like to identify based on a published message the relation in the information, so basically the path in the address space e.g.
Machine -> Components -> Sensor1 -> SignalSet -> Temperature
Machine -> Monitoring -> Temperature

After an initial discussion with Randy we think utilizing the properties in the meta message may be a good approach. With a standardized property which describes the types of the individual elements in the chain e.g.
MyMachineType -> MyComponentType -> MySensorType -> AnalogSignalType -> ProcessValueType
Together with the name of the value
TemperatureX001.Value