Search
48 result(s) for namespaceUri
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.2 URIsquery subcomponents and/or fragments. Below are recommended URI formats for different use cases. 1) NamespaceUri assigned by the creator of a InformationModel : tag:<authority-domain-name>,<yyyy
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.12 DiagnosticInforelated information. Table 132 - DiagnosticInfo Name Type Description DiagnosticInfo structure Vendor-specific diagnostic information. namespaceUri Int32 The symbolicId is defined within the context of a namespace. This namespace is represented ... Client in the stringTable parameter of the ResponseHeader parameter defined in 7.33 . The namespaceUri parameter contains the index into the stringTable for this string. -1 indicates that no string
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model6.3.13 NamespaceMetadataTypeBrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in 6.2 HasProperty Variable NamespaceUri String PropertyType Mandatory HasProperty Variable NamespaceVersion String PropertyType Mandatory HasProperty Variable NamespacePublicationDate DateTime PropertyType Mandatory ... NamespaceIndex of the QualifiedName and the namespace URI as name of the QualifiedName . The NamespaceUri Property contains the namespace represented by an instance of the MetaDataType. The NamespaceVersion Property provides
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Modelidentifies the Object on which the Method was called. The ExpandedNodeId shall use a namespaceUri , the serverIndex shall be set to 0 and the serverIndex shall be ignored. MethodId identifies ... method that was called. The ExpandedNodeId shall use a namespaceUri , the serverIndex shall be set to 0 and the serverIndex shall be ignored. The ServerUri in the parent class
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information ModelC.2.1 TypeDictionarythat are referenced by StructuredTypes defined in the dictionary. Each import element specifies the NamespaceUri of the TypeDictionary being imported. The TypeDictionary element shall declare an XML namespace prefix
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappingsopaqueid> = "b=" BASE64 NodeIds with a NamespaceIndex of 0 or a NamespaceUri of http://opcfoundation.org/UA/ shall only use the <identifier> form
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.2.2.10 ExpandedNodeIdExpandedNodeId An ExpandedNodeId extends the NodeId structure by allowing the NamespaceUri to be explicitly specified instead of using the NamespaceIndex . The NamespaceUri is optional. If it is specified, then ... encoded by first encoding a NodeId as described in 5.2.2.9 and then encoding NamespaceUri as a String . An instance of an ExpandedNodeId may still use the NamespaceIndex instead
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.2.2.12 DiagnosticInfoactually present in the encoded form. As described in OPC 10000-4 , the SymbolicId , NamespaceUri , LocalizedText and Locale fields are indexes in a string table which is returned ... Info 0x20 InnerStatusCode 0x40 InnerDiagnosticInfo SymbolicId Int32 A symbolic name for the status code. NamespaceUri Int32 A namespace that qualifies the symbolic id. Locale Int32 The locale used
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.4.2.10 NodeIdfirst abnormal state occurs when the encoder cannot map a NamespaceIndex to a NamespaceUri . In this case, the encoder shall encode the NamespaceIndex using the <namespace-index> form ... application. The second abnormal state occurs when the decoder cannot convert a NamespaceUri to a NamespaceIndex . If this occurs the decoder shall set the NamespaceIndex to 0, the IdType
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.4.2.11 ExpandedNodeIdIdentifier to the JSON string. When the ServerIndex is 0, decoders shall replace a NamespaceUri with a NamespaceIndex when a mapping exists or if a mapping can be created ... mapping exists or one cannot be created the NamespaceUri is stored in the NamespaceUri field of the ExpandedNodeId
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.4.2.13 DiagnosticInfodefault value is -1. It is not encoded if the value is -1. NamespaceUri Int32 A namespace that qualifies the symbolic id. The default value ... value is null. It is not encoded if the value is null. The SymbolicId , NamespaceUri , Locale and LocalizedText fields are encoded as JSON numbers which reference the StringTable contained
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.4.2.14 QualifiedNameencoding error. This can occur when the encoder cannot map a NamespaceIndex to a NamespaceUri . In this case, the encoder shall encode the NamespaceIndex using the <namespace-index ... application. A second abnormal state occurs when the decoder cannot convert a NamespaceUri to a NamespaceIndex . If this occurs the decoder shall set the NamespaceIndex to 0 and the Name
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsA.3 Numeric Node Idsexample, DataTypeEncoding Nodes have the form: <DataTypeName>_Encoding_<BrowseName> The NamespaceUri for all NodeIds defined is http://opcfoundation.org/UA/ The CSV released with this version
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsH.2 NodeIdNamespaceIndex is 0. For NonReversibleEncoding this field is the JSON string containing the NamespaceUri associated with the NamespaceIndex unless the NamespaceIndex is 0. If the NamespaceIndex is 0 the field
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsH.3 ExpandedNodeIdthis field. Namespace For ReversibleEncoding this field is a JSON string with the NamespaceUri if the NamespaceUri is specified. Otherwise, it is a JSON number with the NamespaceIndex. The field ... NamespaceIndex is 0. For NonReversibleEncoding this field is the JSON string containing the NamespaceUri or the NamespaceUri associated with the NamespaceIndex unless the NamespaceIndex
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsH.5 QualifiedNameNamespaceIndex is 0. For NonReversibleEncoding this field is the JSON string containing the NamespaceUri associated with the NamespaceIndex unless the NamespaceIndex is 0. If the NamespaceIndex is 0 the field
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access5.6.4.1 Generalunits used in all industries, the EUInformation structure includes a separate field (the namespaceUri ) to identify the system on which the exposed unit is based. The default OPC UA mapping
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Accessavailable here: https://reference.opcfoundation.org/files/UNECE_to_OPCUA.csv?u=http://opcfoundation.org/UA/ This mapping has been generated as follows: The namespaceUri shall be http:// www.opcfoundation.org/UA/units/un/cefact The Common Code (represented as an alphanumeric variable length
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Accessavailable here: https://reference.opcfoundation.org/files/IEC62720_to_OPCUA.csv?u=http://opcfoundation.org/UA/ This mapping has been generated as follows: The namespaceUri shall be http:// www.opcfoundation.org/UA/units/cdd/IEC62720 The Code is the data identifier of the IRDI
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global ServicesB.2 Numeric Node Idsaddition, this document defines Nodes which are only used by GlobalDiscoveryServers . The NamespaceUri for any GDS specific NodeIds is http://opcfoundation.org/UA/GDS / The CSV released with this version
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub9.1.9.3 SubscribedDataSetMirrorTypecreated in the Subscriber from the DataSetMetaData if they do not exist. The NamespaceUri of the created DataTypes shall match the namespace contained in the DataSetMetaData
-
OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security4.2.2 AddRole MethodRole to the RoleSet Object defined in 4.3 . The combination of the NamespaceUri and RoleName parameters are used to construct the BrowseName for the new Node . The BrowseName shall ... Roles are defined in OPC 10000-6 . Signature AddRole ( [in] String RoleName, [in] String NamespaceUri, [out] NodeId RoleNodeId ); Argument Description RoleName The name of the Role . NamespaceUri The NamespaceUri qualifies
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboardingaddition, this document defines Nodes which are only used by Registrars . The NamespaceUri for any Device Onboarding specific NodeIds is: http://opcfoundation.org/UA/Onboarding/ The CSV released with this version
-
OPC-10000-24 – OPC Unified Architecture - Part 24: SchedulerName for the ExceptionSchedule InstanceDeclaration within the ScheduleType declaration is: ScheduleType_ExceptionSchedule. The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/Scheduler/ The CSV released with this version
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.3.2 PortableNodeId providedconnecting to the Server , reading the NamespaceArray from the Server , and matching all NamespaceUri from the NamespaceArray to the URI's store in the PortableNodeId and storing the Index ... Connection to ensure it has not changed. Repeat for all Servers . When resolving NamespaceUri , if a Null or empty NamespaceUri is encountered, the Server shall assume that
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelconnecting to the Server , reading the NamespaceArray from the Server , and matching all NamespaceUri from the NamespaceArray to the URI's store in the PortableRelativePaths . PortableRelativePathElements and storing the Index ... process for resolving BrowsePaths shall be repeated. Repeat for all Servers . When resolving NamespaceUri , if a Null or empty NamespaceUri is encountered, the Server shall assume that
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelExpandedNodeIds and QualifiedNames that must be modified, so the NamespaceIndexes and ServerIndexes reference the NamespaceUri and ServerUri tables in the UANodeSet." When generating a UANodeSet XML file, the NamespaceArray
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelF.1.2.2 Namespacesdefined scope, all identifiers ( NodeId , QualifiedName ) use a NamespaceIndex instead of a NamespaceUri . The scope has a NamespaceArray with URIs where the NamespaceIndex is defined as an index into this ... NodeId and 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 OfflineEngineeringfollowing AttributeTypes used to compose the specialized mapping of NodeId described in A.3.7 : NamespaceUri - An AttributeType with a data type of xs:anyURI to hold a NamespaceUri of a NodeId
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringA.3.7.1 QualifiedName DataTypeQualifiedName DataType QualifiedName - The integer NamespaceIndex used in OPC UA is replaced by a NamespaceUri in AutomationML . In AutomationML , the full URI is always used, and there is never ... index. Wherever NamespaceUri is used, the AutomationML datatype is always xs:anyURI
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringA.3.7.5 PortableNodeId data typetype PortableNodeId - The identifier field of PortableNodeId has the same definition as NodeId. The NamespaceUri information of the PortableNodeId is already present in the identifier and, therefore, redundant
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringAttribute name Included in SystemUnitClasses or Instances Notes NodeId X If the NamespaceUri portion of the NodeId or the entire NodeId is not present, then the AML object contains ... Name portion of the BrowseName is inferred by the AML object Name. If the NamespaceUri sub-attribute of the BrowseName AML attribute is not present and the AML Object
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringA.9 Instance mappingInstanceHierarchy, care must be given to setting the URIs properly to reflect the correct NamespaceUri for both the BrowseName and the Node . In the InstanceHierarchy, an empty or missing NamespaceUri ... 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 OfflineEngineeringNamespaceIndexes : OPC UA FX AML does not use NamespaceIndexes . It always uses the NamespaceUri as a string; Bit order in OptionSets and Bitmasks : In OPC UA FX AML, OptionSet
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.2.1 NodeIdsNode have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is 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
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.2.2 BrowseNamesNodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A . For InstanceDeclarations
-
OPC-10000-100 – OPC Unified Architecture - Part 100: DevicesInformation Model is identified by the following URI: http://opcfoundation.org/UA/DI/ Documentation for the NamespaceUri can be found here . The NodeSet associated with this version of specification can be found ... latest version of the specification can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/DI/&i=2 The NamespaceUri for the package_metadata.json with structures and enumerations used for Software Package files is: http://opcfoundation.org/UA/DI/PackageMetadata/
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.2.1 NodeIdsNode have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is 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
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.2.2 BrowseNamesNodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 16.2 . For InstanceDeclarations of NodeClass
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.2.1 NodeIdsNode have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is 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
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.2.2 BrowseNamesNodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 8.2 . For InstanceDeclarations of NodeClass
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation3.3.2.1 NodeIdsNode have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is 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
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation3.3.2.2 BrowseNamesNodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A. For InstanceDeclarations
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.2.1 NodeIdsNode have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is 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
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.2.2 BrowseNamesNodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 10.2 . For InstanceDeclarations of NodeClass
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial LocationName for the Identifier InstanceDeclaration within the SpatialObjectType declaration is: SpatialObjectType_Identifier . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/RSL/ The CSV released with this version
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.2.1 NodeIdsNode have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is 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
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.2.2 BrowseNamesNodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 12.2 . For InstanceDeclarations of NodeClass