Question: TranslateBrowsePathsToNodeIds behavior in corner cases

[okapies]

Type of issue

• Bug
• Enhancement
• Compliance
• Question
• Help wanted

Current Behavior

I want to know how TranslateBrowsePathsToNodeIds service works in the following request:

• BrowsePath(startingNode=<NodeId: /Objects>, relativePath=null)
• BrowsePath(startingNode=<NodeId: /Objects>, relativePath=<RelativePath: elements=[])
• BrowsePath(startingNode=<NodeId: /Objects>, relativePath=<RelativePath: elements=[<Element: targetName=null>])
• BrowsePath(startingNode=<NodeId: /Objects>, relativePath=<RelativePath: elements=[<Element: targetName="">])

I also wonder how "" (empty) and "/" as RelativePath text format should be treated in the client/server implementation.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

- OS:
- Environment:
- Runtime:
- Nuget Version:
- Component:
- Server:
- Client:

Anything else?

No response

[okapies]

The spec says:

The final element may have an empty targetName. In this situation all targets of the references identified by the referenceTypeId are the targets of the RelativePath.

In this sense, what is the "empty targetName"?

1. targetName = null
2. targetName = "" (empty string)
3. targetName = QualifiedName(name=null, namespaceIndex=[index])
4. targetName = QualifiedName(name="", namespaceIndex=[index])

In my experiment, the reference implementation does not recognize 4 (returns Bad_NoMatch).

[okapies]

If path string /[idx]: is given, RelativePathFormatter returns null only for ns=0 and otherwise QualifiedName(name="", namespaceIndex=[idx]). Which behavior is correct?

UA-.NETStandard/Stack/Opc.Ua.Core/Types/Utils/RelativePath.cs

Lines 844 to 850 in c7381cf

	if (namespaceIndex == 0)
	{
	return null;
	}
	}
	return new QualifiedName(buffer.ToString(), namespaceIndex);

[EthanChangAED]

migrating to discussion board.