Search
10 result(s) for OptionalPlaceholder
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.4.4.4.4 OptionalPlaceholderOptionalPlaceholder For Object and Variable the intention of the ModellingRule OptionalPlaceholder is to expose the information that a complex TypeDefinition expects from instances of the TypeDefinition to add instances with ... where an instance Device A adds two DeviceParameters in the Folder. The ModellingRule OptionalPlaceholder adds no additional constraints on instances of the TypeDefinition . It just provides useful information when exposing
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.4.4.4.5 MandatoryPlaceholderObject and Variable the ModellingRule MandatoryPlaceholder has a similar intention as the ModellingRule OptionalPlaceholder . It exposes the information that a TypeDefinition expects of instances of the TypeDefinition to add instances
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model8.4.4 OptionalPlaceholderOptionalPlaceholder The ModellingRule OptionalPlaceholder is defined in OPC 10000-3 . Its representation in the AddressSpace , the " OptionalPlaceholder " Object, is formally defined in Table 116 . Table 116 - OptionalPlaceholder definition ... Attribute Value BrowseName OptionalPlaceholder References NodeClass BrowseName Comment HasTypeDefinition ObjectType ModellingRuleType Defined in 6.5 Conformance Units Base Info Base Types
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelBoolean 0:BaseDataVariableType O ConformanceUnits UAFX ConnectionManager Capabilities Base <Capability> - is an OptionalPlaceholder (defined in OPC 10000-3 ) to indicate that additional capabilities may be added by this ... shall include a Description, and they follow all of the rules associated with an OptionalPlaceholder. MaxConnectionConfigurationSets indicates the maximum number of ConnectionConfigurationSets that the ConnectionManager can support . MonitorsLocalConnectionEndpoints, when true
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.2.2 BrowseNamesdefined in Annex A . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.2.2 BrowseNamesdefined in 16.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.2.2 BrowseNamesdefined in 8.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation3.3.2.2 BrowseNamesdefined in Annex A. For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.2.2 BrowseNamesdefined in 10.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.2.2 BrowseNamesdefined in 12.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets