Search

Scope: Core (OPC-10000-*) All specs

63 result(s) for Namespace

OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.12 Roles

AccessRestrictions is application specific, but they can be assigned to all Nodes in a Namespace or to specific Nodes . Figure 6 - Role overview OPC UA defines a set of standard
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

3.3.2 Conventions for defining NodeClasses

name, which is mapped to the BrowseName having the NamespaceIndex 0, which represents the Namespace for OPC UA. The Use column (optional or mandatory) does not imply a specific ModellingRule
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.9 RolePermissions

information about how it manages Permissions . If a Server supports Permissions for a particular Namespace it shall add the DefaultRolePermissions Property to the NamespaceMetadata Object for that Namespace (see Figure ... particular Node in the Namespace needs to override the default values, the Server adds the RolePermissions Attribute to the Node. The DefaultRolePermissions Property and RolePermissions Attribute shall only be readable
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.11 AccessRestrictions

data type is defined in 8.56 . If a Server supports AccessRestrictions for a particular Namespace it adds the DefaultAccessRestrictions Property to the NamespaceMetadata Object for that Namespace (see Figure ... particular Node in the Namespace needs to override the default value the Server adds the AccessRestrictions Attribute to the Node. If a Server implements a vendor specific access restriction model
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.7.1 Method NodeClass

shall use a BrowseName equal to the name of the Argument it describes. The Namespace of the BrowseName shall be ignored by a Client when performing an equality check with
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.5.2 DataTypeRefinement Objects

Variable shall use a BrowseName equal to the name of the field. The Namespace of the BrowseName shall be ignored by a Client when performing an equality check with
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.29 AllowedSubtype

NamespaceIndex of the DataType NodeId unless it is defined in the same Namespace . It is not allowed to reference two Variables with the same BrowseName using the AllowedSubtype ReferenceType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.55 PermissionType

NodeClasses . AddNode 16 The Client is allowed to add Nodes to the Namespace . This Permission is only used in the DefaultRolePermissions and DefaultUserRolePermissions Properties of a NamespaceMetadata Object Reserved
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.58 AccessLevelExType

Value trigger changes to the ConfigurationVersion Property of the NamespaceMetadata Object for the Namespace of the Variable . When this Field is 0 the Value of the Variable may change ... ConfigurationVersion Property shall be provided along with the parent NamespaceMetadata Object for the Namespace of the Variable ). Table 41 defines the combinations of Constant and NonVolatile Fields and their
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.13 NamespaceMetadataType

NamespaceMetadataType This ObjectType defines the metadata for a namespace provided by the Server . It is formally defined in Table 22 . Instances of this Object allow Servers to provide more information ... like version information in addition to the namespace URI. Important information for aggregating Servers is provided by the StaticNodeIdTypes, StaticNumericNodeIdRange and StaticStringNodeIdPattern Properties . Table 22 - NamespaceMetadataType definition Attribute Value BrowseName
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.45 BitFieldDefinition

True if the range of bits is reserved for future use by the defining Namespace. StartingBitPosition UInt32 The bit position of the first bit used by this field. EndingBitPosition UInt32 ... shall only be defined by a Subtype of a BitFieldType defined in the same Namespace . Bits not defined or reserved in the BitFieldType may be used by a Subtype which
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.9 NodeId

NodeId are described the Table 16 . Table 16 - NodeId components Name Data Type Description Namespace UInt16 The index for a namespace URI. An index of 0 is used ... explicit format defined. Table 18 - Standard NodeId Binary DataEncoding Name Data Type Description Namespace UInt16 The NamespaceIndex . Identifier * The identifier which is encoded according to the following rules: NUMERIC UInt32
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.1 SafetyACSet Object

Server shall have a singleton Folder called SafetyACSet with a fixed NodeID in the Namespace of this document. Because all SafetyProviders and SafetyConsumers on this Server contain a hierarchical Reference
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.2 Safety ObjectType definitions

derived from ReferenceType HasProperty ) for Property References . As BrowseNames (i.e. name and Namespace ) are used to find Methods , the names of Objects and Properties shall be locally unique. The DataType
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

12.1 Namespace metadata

Namespace metadata Table 42 defines the Namespace metadata for this document. The Object is used to provide version information for the Namespace and an indication about static Nodes. Static Nodes
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

12.2 Handling of OPC UA namespaces

Table 43 - Namespaces used in a safety Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This Namespace shall have Namespace ... index 0. Mandatory Local server URI Namespace for Nodes defined in the local Server . This can include types and instances used in an AutoID Device represented by the Server . This
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

Annex A Safety Namespace and mappings (Normative)

Annex A Safety Namespace and mappings (Normative) This Annex A defines the numeric identifiers for the numeric NodeIds defined in the Namespace of this document. The identifiers are specified
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

6.2 AliasNameType ObjectType Definition

least one AliasFor Reference (or subtype of). A Client shall always ignore the namespace associated with an AliasName for comparison with other AliasNames . AliasName can be defined in Namespace ... local Server ) or in some vendor defined namespace. See OPC 10000-3 for additional details on Namespaces. The AliasName Object's BrowseName shall not be modified once it is defined
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.7 CustomMetaDataProperties Property

containing the Values the semantic Properties belong to are qualified with the OPC UA Namespace . This allows the encoder to omit the NamespaceIndex when serializing the QualifiedName inside the KeyValuePair
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.5 ConnectionManager error reporting

connecting to a Server , resolving Node Information by AliasName lookup, TranslateBrowsePathToNodeId , or even for Namespace lookup issues. The ConnectionManager also report errors from interactions with an SKS (local or remote
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.6 Loading / Saving ConnectionConfigurationSets

listed at the top of the generated file. But in this case, not all Namespace entries might be defined in the ConnectionManager Server . So, exporting a UANodeset XML from ... exist in the Server's NamespaceArray ), or it could result in an incorrect Namespace being referenced. The simplest solution is to ensure that the ConnectionManager Server include all Namespaces
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.2 Namespaces

scope of those identifiers is defined by the related ServerAddressConfDataType structure, containing a Namespace array. The NamespaceIndex of a node identifier is used as an index into the Namespace array ... RelativePath contained in the DataTypes to their portable versions using the NamespaceUri from the Namespace array when it loads the ConnectionConfigurationSet from the data structure
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

7.7 OpcAmlMetaModel and OPC UA FX AML Libraries

contain the AML type libraries (SystemUnitClass, InterfaceClassLibrary, RoleClassLibrary, AttributeTypeLibrary) of exactly one OPC UA Namespace . For OPC UA FX AML Libraries, the following rules apply: The new types ... SystemUnitClass library and <ModelUri> is the OPC UA Namespace of the corresponding OPC UA NodeSet file. In an OPC UA FX AML Library, the Namespace URI, the version
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.2.1 OpcAmlMetaModel libraries Overview

libraries to imply semantics that do not correspond to a Node in some UA Namespace and hence do not belong in the other generated AML libraries that are each based ... single UA Namespace
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.2.3 ATL_OpcAmlMetaModel library

from the OPC UA metamodel and hence have no corresponding Node in the UA Namespace . The following enumeration-based attributes are provided: AttributeId, BuiltInType, and ModellingRuleType. Additionally, the ATL_OpcAmlMetaModel
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.2.4 SUC_OpcAmlMetaModel library

instantiated. Since there is no Node that represents the Method NodeClass in a UA Namespace (because it is built-in to the UA meta-model), the SUC UaMethodNodeClass is defined
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.1 DataType mapping overview

A.3.1 DataType mapping overview For every OPC UA Namespace , an AML Attribute Type Library exists that defines a corresponding AML AttributeType for each OPC UA DataType . The name ... Library is composed of the string "ATL_" followed by the OPC UA Namespace name. Each AML AttributeType has a NodeId Attribute, which matches the NodeId
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.2 Built-in Types

defined as an AML AttributeType in the AttributeType Library for the base OPC UA Namespace . Table A.2 - Mapping simple built-in Datatypes UA DataType XML Schema type used
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.4 Arrays

DataTypes are represented as XML lists. The AML AttributeType Library of an OPC UA Namespace defines a number of lists for arrays of UA DataTypes , of which a subset
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.4 NodeClass mapping

then the AML object contains an AML attribute UaNodeNamespaceUri that represents the OPC UA Namespace of the corresponding OPC UA Node . If the NodeId and UaNodeNamespaceUri are empty ... present, then the presumed value is either the OPC UA Namespace referenced by the AML library containing the AML object or the default OPC UA Server Namespace (depending
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.9 Instance mapping

BrowseName ) or UaNodeNamespaceUri shall imply the default NamespaceUri of the OPC UA Server (i.e. Namespace index 1). In all other cases, the URI attributes shall contain valid URIs that reflect
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

B.1.1 UA library overview

types defined in the base OPC UA Specifications (i.e., those defined in Namespace 0, " http://opcfoundation.org/UA/" ). AML libraries for all other OPC UA Information Models can be created ... Specifications. The AutomationML libraries that mirror the types defined in the OPC UA Namespace http://opcfoundation.org/UA/ are provided in a single digitally signed AML Container here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/FX/Data/&v=1.00.03&i=2
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

C.1.1 DI Library Overview

Library Overview The AutomationML libraries that mirror the types defined in the OPC UA Namespace http://opcfoundation.org/UA/DI/ are provided in a single digitally signed AML Container https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/FX/Data/&v=1.00.03&i=2
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

D.1.1 OPC UA FX Library Overview

AutomationML libraries that mirror the types and instances defined in the OPC UA Namespace s http://opcfoundation.org/UA/FX/* are provided in the following digitally signed AML Containers https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/FX/Data/&v=1.00.03&i=2
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

E.1.1 UA Safety Library Overview

Library Overview The AutomationML libraries that mirror the types defined in the OPC UA Namespace http://opcfoundation.org/UA/Safety/ are provided in a single digitally signed AML Container https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/FX/Data/&v=1.00.03&i=2
OPC-30020 – MDIS OPC UA Companion Specification

4.3.4.2 Namespaces

services defined for OPC UA use the NamespaceIndex to specify the Namespace for qualified values. There are two types of values in OPC UA that are qualified with Namespaces : NodeIds ... TypeDefinitions defined by the InformationModel . QualifiedNames are non-localised names qualified with a Namespace . They are used for the BrowseNames of Nodes and allow the same names to be used
OPC-30020 – MDIS OPC UA Companion Specification

10.4 UANodeSet Development

UANodeSet Development In OPC UA an AddressSpace is separated into Namespaces , where each Namespace defines the owner of the address space contained in it. The MDIS Namespace shall ... owned by MDIS. Any implementation (custom types / instances) shall be in a separate Namespace from the MDIS Namespace . Any custom types or subtypes of the standard MDIS Types, as defined
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

4.3.4.2 Namespaces

services defined for OPC UA use the NamespaceIndex to specify the Namespace for qualified values. There are two types of values in OPC UA that are qualified with Namespaces : NodeIds ... TypeDefinitions defined by the information model. QualifiedNames are non-localized names qualified with a Namespace . They are used for the BrowseNames of Nodes and allow the same names
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

6.1 General

This model generates standard types. All PackML types will be defined in their own Namespace and will begin with "PackML" A key point is a standard ObjectType representation
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture

8.1 General

NodeIds for random objects in a POWERLINK Object Dictionary . For this generic access the Namespace ' http://opcfoundation.org/UA/POWERLINK/UA/DirectAccess/' is used
OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases

4.1 Introduction to Cloud Library

part of an AddressSpace of a real OPC UA server). To identify a stored NameSpace in the Cloud Library, a globally unique identifier such as the NamespaceUri (as defined
OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases

5 Use cases

cases For each of the use cases, the OPC UA NameSpace needs to be known up front, before a connection to the physical machine (containing an OPC UA server ... possible. Therefore, the NameSpace for the machine needs to be available on the Internet on a global scale
OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases

5.1 Configure the application behind the OPC UA Client which consumes the data from the machine

machine or factory. The Cloud Library enables the machine builder to upload the NameSpace after final commissioning before the machine is shipped and installed in the factory. During this timeframe
OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases

5.3 Retrofit OPC UA to existing machines

would like to build my PLC program so that it fulfills a published NameSpace for a heat treatment process. I might search for "heat treatment
OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases

5.4 Downloading a NameSpace from the Cloud Library into a "blank" UA Server Instance

Downloading a NameSpace from the Cloud Library into a "blank" UA Server Instance Abby works as an OT engineer at a steel welder machine manufacturer ... metadata via one of the REST APIs. Within minutes, she finds the specific NameSpace that she wants to use in her "blank" OPC UA server built into
OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases

5.5 Engineering support from existing NameSpaces

AddressSpace of the whole production line. Jeff will certainly also upload the resulting NameSpace to the Cloud Library , so that his customer can prepare the corresponding OPC UA Client
OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases

11.1 Sovereignty

Sovereignty To create a workable marketplace, NameSpace owners' IP rights must be protected when they make their NameSpaces available via the Cloud Library . NameSpace sovereignty is a fundamental aspect ... Cloud Library as such, NameSpace Owners will remain in control of their NameSpaces . Examples of such control factors include who has access to each NameSpace and on what terms
OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases

13.3 Content Owner Insights

persona) shall have access to basic metadata which helps to understand how popular their NameSpace is. This can be a great source of customer data that can flow into product ... management decisions regarding the assets being described by the uploaded NameSpace from a particular source
OPC-30400-2 – OPC UA for Cloud Library - Part 2: API Definition

4.2.5 Method Upload

stored or updated. Response Body Schema string Comments Upload cannot overwrite a matching NameSpace from another organization. The Namespace can be uniquely identified by its NamespaceUri and its PublicationDate
OPC-30400-2 – OPC UA for Cloud Library - Part 2: API Definition

5 Cloud Library Data Model for REST & GraphQL Interface

REST & GraphQL Interface The following diagram describes the class hierarchy of the NameSpace query for the GraphQL interface. It is also used for uploading and downloading NameSpaces
OPC-30400-2 – OPC UA for Cloud Library - Part 2: API Definition

5.2 Category

Category The Category describes a collection of NameSpace s, for example all companion specifications released by the VDMA. Each NameSpace is assigned to one Category . Table 2 - Category Definition Property
OPC-30400-2 – OPC UA for Cloud Library - Part 2: API Definition

5.3 License

Apache License 2.0. See https://tldrlegal.com/license/apache-license-2.0-(apache-2.0) Custom Custom license provided by the NameSpace contributor, see the provided information under the given LicenseUrl
OPC-30400-2 – OPC UA for Cloud Library - Part 2: API Definition

5.4 NodeSet2

NodeSet2 The NodeSet2 holds the OPC UA NodeSet for the related NameSpace . Access to this entity should only be provided to users allowed to download the NodeSet file. Table ... Definition Property Description Type Required NodeSetXML XML providing the OPC UA NodeSet for related NameSpace String Mandatory PublicationDate Date and time the NodeSet was published DateTime Mandatory (retrieved from nodeset
OPC-30400-2 – OPC UA for Cloud Library - Part 2: API Definition

5.5 NameSpace

NameSpace The NameSpace contains meta data describing the NodeSet2 to provide relevant and searchable information. The NameSpace must contain a NodeSet2 . Table 5 - NameSpace Definition Property Description Type Required Title ... Title of the NameSpace String Mandatory Version Version of the NameSpace String Mandatory License License for the usage of this NameSpace License Mandatory Contributor Contributing organization Organization Mandatory Description Description
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

3.4.1.1 Node definitions

DataType shall be used. Note that if a symbolic name of a different Namespace is used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of different NodeClasses cannot
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

3.4.1.2 Additional References

needs to refer to a Type or well-known instance, uniquely identified within a Namespace by the BrowseName . References can be made to any other Node
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

3.4.2.1 NodeIds

vendor specific and depends on the position of the NamespaceUri in the server Namespace table. Note that this document not only defines concrete Nodes , but also requires for some Nodes ... running on the Server . The NodeIds of those Nodes are Server specific, including the Namespace . However, the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

3.4.2.2 BrowseNames

BrowseName is not defined by this document, a Namespace index prefix is added to the BrowseName (e.g., prefix '0' leading to '0:EngineeringUnits' or prefix '2' leading to '2:DeviceRevision
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

4.2.3.2 Namespaces

this possible by eliminating naming and ID conflicts between information from different sources. Each Namespace in OPC UA has a globally unique string called a NamespaceUri which identifies a naming ... changed. The Services defined for OPC UA use the NamespaceIndex to specify the Namespace for qualified values. There are two types of structured values in OPC UA that are qualified
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

10.1 Namespace metadata

Namespace metadata Table 145 defines the Namespace metadata for this document. The Object is used to provide version information for the Namespace and an indication of the static Nodes . Static ... IsNamespaceSubset Property is set to False, as the UANodeSet XML file contains the complete Namespace . Servers only exposing a subset of the Namespace should change this value to True
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

10.2 Handling of OPC UA Namespaces

define a standard Property . Servers may often choose to use the same Namespace for the NodeId and the BrowseName . However, if they want to provide a standard Property , its BrowseName ... shall have the Namespace of the standard's body even though the Namespace of the NodeId reflects something else, such as the EngineeringUnits Property . All NodeIds of Nodes not defined
OPC-40200 – OPC UA for Weighing Technology

13.1 Namespace Metadata

Namespace Metadata Table 185 defines the namespace metadata for this specification. The Object namespace metadata is used to provide version information for the namespace and an indication about static Nodes ... provided as Object of the type NamespaceMetadataType . This Object is a component of the Namespace Object that is part of the Server Object . The NamespaceMetadataType ObjectType and its Properties
OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems

6.7 Adding new Components

left panel shows the introduction of the new compressor type TurboCompressorType in a separate Namespace . The middle panel shows the introduction of a completely new Component type in a separate ... Namespace . The right panel shows the use of the CASComponentType as TypeDefinition for a new Component in a separate namespace. For each approach, the corresponding new enumeration is shown below