#65 XML - Publish and Subscribe telegram identification

[Gari]

Identify one port defined in the XML as Source (Publish) or Sink (Subscribe) is ambiguous. There is not any tag defined to identify this, and the understanding of the data inside the telegram block (source, destination tags...) is not defined in each case too.

So, it should be necessary to define some mechanism to distinguish both type of telegrams.

[Armin-Hagen Weiss]

Each telegram will be defined only once in a tool. The application decides to do a subscribe and/or a publish. Up to now there is no automatic subscription/publishing supported. An additional telegram attribute "type" would be needed only in this case. If we want to support such a feature we should define first the functionality and the requirements.
Up to now in a higher layer the subscribe/publish can be done by using only the ComId. All other parameters are fixed in the XML configuration.

[Bernd Löhr]

Returned comment from TRDP seminar:
To be able to configure a device via XML configuration there should be at least an optional attribute for telegrams, whether they are sink or source for that specific device.
-> Eventually a separate sink/source tag with list of comIDs?

[Bernd Löhr]

The tag will be added to the xsd definition as attribute to the telegram definition (type = source|sink|sourcesink)
The structures from the XML header file will be extended.

[Bernd Löhr]

xsd and header definitions added

[Bernd Löhr]

ToDo: XML example should use the new attribute...