Search

59 result(s) for TypeDefinitions

• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  level InstanceDeclarations , that are not directly visible in the table. The TypeDefinitions and DataTypes used in the InstanceDeclarations , and the ReferenceTypes are defined in their individual tables
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.7 Changes in AddressSpace over time
  possible and probable that the AddressSpace of a Server will change over time (i.e. TypeDefinitions can change; NodeIds can be modified, added or deleted). Server developers and administrators need
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.1 Node definitions
  level InstanceDeclarations , that are not directly visible in the table. The TypeDefinitions and DataTypes used in the InstanceDeclarations , and the ReferenceTypes are defined in their individual tables
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  7.3 Calibration Target Information Model overview
  which is provided by the calibration target category. The information model only provides the TypeDefinitions to manage calibration targets. It does not provide, how to organize several calibration targets
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-10101 – OPC UA for WoT Binding
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  4.2.3.2 Namespaces
  some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.2 Namespaces
  knowledge of some Nodes . OPC UA InformationModels generally define globally unique NodeIds for the TypeDefinitions defined by the InformationModel . QualifiedNames are non-localised names qualified with a Namespace . They ... Instances of a TypeDefinition are expected to have children with the same BrowseName s. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  4.3.4.2 Namespaces
  some Nodes. OPC UA information models generally define globally unique NodeIds for the TypeDefinitions defined by the information model. QualifiedNames are non-localized names qualified with a Namespace . They ... information models without conflict. The BrowseName is used to identify the children within a TypeDefinitions . Instances of a TypeDefinition are expected to have children with the same BrowseNames . TypeDefinitions
• OPC-30060 – OPC UA for Tobacco Machine Communication
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30140 – OPC UA for PROFINET
  4.2.3.2 Namespaces
  some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30141 – OPC UA for PROFIenergy
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different Information Model s without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that
• OPC-30142 – OPC UA for PROFINET Remote IO
  4.3.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  4.3.2 Namespaces
  some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30210-1 – OPC UA for Unattended Retail & Coffee Solutions - Part 1: Core Components
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30210-1 – OPC UA for Unattended Retail & Coffee Solutions - Part 1: Core Components
  6.3.4 Audit
  payment devices. X:MyMachineEngine, X:MyPaymentService, X:MyCoins and X:MyBills are all of TypeDefinitions generating Events of VendingBaseAuditEventType . At the bottom of Figure 18 some examples of Events
• OPC-30250 – OPC Unified Architecture for DEXPI
  5.2.3.2 Namespaces
  some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  4.2.3.2 Namespaces
  some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30450-1 – OPC UA for Digital Product Passport - Part 1: Information Model
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-34100 – OPC UA for Energy Consumption Management
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-34100 – OPC UA for Energy Consumption Management
  6.2.1 Base Concepts
  Overview EnergyMeasurementType and EnergyMeasurementValueType In Figure 9 , an example of the usage of those TypeDefinitions is given. The "X:SampleObject" contains two instances of EnergyMeasurementType , one measuring
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  4.2.3.2 Namespaces
  knowledge of some Nodes . OPC UA Information Models define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  4.2.3.2 Namespaces
  some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40200 – OPC UA for Weighing Technology
  4.2.3.2 Namespaces
  some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40210 – OPC UA for Geometric Measurement Systems
  5.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40301 – OPC UA for Flat Glass Processing
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40444 – OPC UA for Textile Testing Devices
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40450-1 – OPC UA for Joining Systems - Part 1: Base
  4.3.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management
  4.2.3.2 Namespaces
  some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40503-1 – OPC UA for Metal Forming - Part 1: General
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40504-1 – OPC UA for Cutting Tools - Part 1: Manufacturing
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40505 – OPC UA for Wireless Machine Tool Peripherals
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40530 – OPC UA for Laser Systems
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40540 – OPC UA for Additive Manufacturing
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40550-1 – OPC UA for Woodworking Machines - Part 1: Vertical Interface
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40560 – OPC UA for Mining - General
  4.3.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40570 – OPC UA for Wire Harness Manufacturing
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40600 – OPC UA for Weihenstephan Standards
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40700 – OPC UA for Surface Technology - General Types
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40701 – OPC UA for Surface Technology - Cleaning and Pretreatment
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40702 – OPC UA for Surface Technology - Organic Coating Technology - Material Supply Systems
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40718 – OPC UA for Surface Technology - Shot Blasting Machinery
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40719 – OPC UA for Plasma Surface Technology
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40740 – OPC UA for Process Air Extraction and Filtration Systems (PAEFS)
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction