Replication Data for: Evaluation of OPC UA Companion Specification Models

Attributes.csv Column headers: NodeId,Attribute,Value,Value (Secondary) Set evaluated: all Nodes Included if Attribute Value explicitly set; AccessLevel included if different values used in NodeSet File Categories.csv Column headers: Category,BrowseNames,NodeIds Set evaluated: all hierarcy root Nodes Included if category tag set Children.csv Column headers: BrowseName,Number of Children,Size of Subtree,Breadth of Subtree,Depth of Subtree,NS Aggregation Score Set evaluated: all hierarcy root Nodes Included if Node spans a hierarchy with References derived from “Aggregates” DIT.csv Column headers: NodeClass,Name,NodeId,tDIT,rDIT Set evaluated: all Type Nodes Included: always DataTypeAggregation.csv Column headers: BrowseName,Number of Aggregated DataTypes,Size of Subtree Set evaluated: all DataType Nodes of type Structure Included: always Includes.csv Column headers: Kind of inclusion, BrowseName, NodeId, foreign Namespace Set evaluated: all Nodes Included if inclusion found InstOutOfTypes.csv Column headers: NodeId,NodeClass,BrowseName,NSRoot Set evaluated: Objects, Variables and Methods that are not InstanceDeclarations Included if recursively evaluated “highest” Parent is Object, Method, Variable, View Instances.csv Column headers: Type BrowseName,Total Instance Occurrences,Prototypes, Final Set evaluated: all Nodes (to find Reference Uses and TypeDefinitions) Included: all Type nodes

Method

Arguments.csv Column headers: Parent,

Method

Name,NodeId,Inputs,Outputs,ModellingRule Set evaluated: all

Methods

Included if BrowseName of Method in Namespace NOC.csv Column headers: BrowseName,Namespace,NodeId,NOC Set evaluated: all Type Nodes and their parent Nodes Included if Node has Children/Subtypes (Inheritance) NodeCounts.csv Column headers: NodeClass, Node Count Set evaluated: all Nodes Included: always Manual_Evaluations Notes of manual analysis in the Companion Specifications as found via reference.opcfoundation.org/ AccessLevel.md Spec - Name of the Specification AccessLevel mentioned - manual analysis: is AccessLevel included in the Type Definition Tables?

AccessLevel in NodeSet - result from automated analysis: are there different AccessLevel Values mentioned in the XML? If “not in file” is mentioned: manual analysis with search for String “AccessLevel” in XML CUs.md Spec - Name of the Specification No. of CUs in XML - result from automated analysis No. of CUs in Text - manual Analysis of section with title “Conformance Units” or “Profiles and Conformance Units” No. of CUs per Type in XML (Min/Max/Mean) - result from automated analysis No. of CUs per Type in Text (Min/Max/Mean) - result from manual analysis using CUs mentioned at the type definition tables [not used in publication] No. of types per CU in XML (Min/Max/Mean) - result from automated analysis Description.md Spec - Name of the Specification Number of Nodes with Description - result from automated analysis Number of Nodes total - result from automated analysis Description in Document?

(at all) - Manual analysis in Node Attribute Tables and Component Descriptions EventNotifier.md Spec - Name of the Specification Number of EventNotifier - result from automated analysis relevant to instance? - manual interpretation based on CS document InstancesOutOfTypes.md Spec - Name of the Specification Number of [NodeClass] IOOT - result from automated analysis Remarks - Notes on what the Instances likely are, manual analysis based on Result-CSV-Files and NodeSet XML, in case of entry points also CS document

Method

ModellingRules.md Notes on the Methods with ModelingRule Mantatory Placeholder and None, based on XML and CS document Scripts Python scripts used to create the figures in the paper and most of the evaluations.