I think I would prefer an approach with a single object type, but clearer collections of properties based on the Network_Type value. Consider dividing up the property table and descriptions into sections that are common, and then appropriate to each network type.
Johnson Controls, Inc.
This is something I started thinking about during the San Antonio meeting, and the more I review Add. AI (and the NPO mods required for Add. AJ) the more I think what I'm proposing below is a little easier of an approach.
What does everyone think of splitting the one, huge NPO into several separate NPO based solely on network type? For example, in the new approach, there would be an MSTP NPO, a BACNET_IPV4 NPO, and so on.
Do you think this would make modifications easier? Do you think it makes the object easier to consume and implement? I look forward to hearing opinions on this.