View Issue Details

IDProjectCategoryView StatusLast Update
000358810000-004: ServicesSpecpublic2016-12-15 22:43
ReporterBjarneBostrom Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionfixed 
Summary0003588: Clarify should AddNodes Service create complete structure of nodes of given TypeDefinition
Description

Spec 1.03 Part 4, AddNodes Service.

The specification should be clarified what happens when the service is called with one AddNodesItem that should create e.g. a Variable/Object node with the given TypeDefinition which has sub-nodes in the type. Is the result

  1. A single node is added to the address space OR
  2. A complete structure of the node with only Mandatory instance declarations instantiated under the new Variable/Object

Based on the current wording the 1 would make more sense as spec says "List of Nodes to add" for the nodesToAdd list parameter. However from a practical point, if an instance of a type exist in the address space, it should have all it's Mandatory components. However if the result is the option 2., it becomes hard to instantiate the Optional components of the type.

One option is that clients shall provide all nodes of instance, and the server could maybe reject the call if not all mandatory nodes are not in the call. However then as the new top-level Variable/Object node does not exist yet, the clients could use the not yet existing/requestedNewNodeId of the top-level node as parentNodeId of the subcomponenets. It would be a bit complicated in the server side, but this way the client could define all the optional nodes it needs in the call.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Matthias Damm

2016-12-13 19:42

developer   ~0007516

Added following text to AddNodes description:
When a Server creates an instance of a TypeDefinitionNode it shall create the same hierarchy of Nodes beneath the new Object or Variable depending on the ModellingRule of each InstanceDeclaration. All Nodes with a ModellingRule of Mandatory shall be created. The creation of Nodes with other ModelingRules is Server specific.

Made changes in document version OPC UA Part 4 - Services 1.04 Specification Draft 02.docx

Jim Luth

2016-12-15 22:43

administrator   ~0007589

Agreed to changes in meeting.

Issue History

Date Modified Username Field Change
2016-11-07 12:06 BjarneBostrom New Issue
2016-11-22 17:05 Jim Luth Assigned To => Matthias Damm
2016-11-22 17:05 Jim Luth Status new => assigned
2016-12-13 19:42 Matthias Damm Note Added: 0007516
2016-12-13 19:42 Matthias Damm Status assigned => resolved
2016-12-13 19:42 Matthias Damm Resolution open => fixed
2016-12-15 22:43 Jim Luth Note Added: 0007589
2016-12-15 22:43 Jim Luth Status resolved => closed
2016-12-15 22:43 Jim Luth Fixed in Version => 1.04