Open jwise-mfg opened 5 months ago
I will ease the duplicate name check in the front end to check for duplicate only for the attributes associated within the particular type. Per the screenshot included, I have a base type with attribute "X". In my extended type, I can add a new attribute "X". I will however keep a check to not permit user to add a 2nd attribute also named "X" on this type (check for duplicate names within the attribute list of this type when trying to add).
As a Profile Designer user that wants to extend a base type, I want to change the properties of a member on that base type in my extension. For example, the base type has a member:
CurrentSpeed
with theIs Required
property asfalse
; in my extension, I wantCurrentSpeed
to haveIs Required
set totrue
.Per https://reference.opcfoundation.org/Core/Part3/v105/docs/6.3.3.3 the normative way to do this is for the Extension Profile to create a new member with the same name as the Base's member, and the new property value. Implementations must follow the definition in the most derived type.
However, Profile Designer has a uniqueness constraint (at least in the UI) on the BrowseName of a member preventing a user from implementing an over-riding extension. This is a defect, per the OPC UA specifcation, since the uniqueness constraint should be on the NodeId -- not the BrowseName. This prevents normative extension in Profile Designer and must be corrected.