Overthink rule to later binding definition

[JakobVogelsang]

At the moment, a later binding type reference is one that has the internal address set. The attribute intAddre in element ExtRef is NOT null. In the same way, message binding, data binding are references that do not have this attribute.

We see not problems with this definition with documentation type SCD files. See for example ABB SSC600. The ICT here works with message binding subscription, but at the end it also adds the link to the internal function (add the intAddr attribute). When you want to read such a file all of a sudden, the message binding editor will not show any subscriptions.

It is not easy to find a solution that fits all here, but I feel the one we implemented right now can be improved.

[Sander3003]

As discussed, please add the options how to go about this with their pro's and con's. Main issue in my words: Their is no way to determin how a SCL file was created with bindings (Later binding directly or starting with message binding; both contain IntAddre eventually once finished).

• Add explanation between the 3 differences types of plug-ins; https://wiki.lfenergy.org/display/SHP/IEC+61580
• Make a solution proposal

[michelguerin]

@JakobVogelsang is this still relevant to you ? Should we close this issue ?