View Issue Details

IDProjectCategoryView StatusLast Update
000284210000-003: Address SpaceSpecpublic2014-11-03 17:34
ReporterNathan PocockAssigned ToWolfgang Mahnke  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version1.03Fixed in Version1.03 
Summary0002842: 5.2.4 BrowseName: Case Sensitivity of BrowseName is Required?
Description

CMPWG 9/4/2014:

The very last sentence in section 5.2.4 says:

"The string-part of the BrowseName is case sensitive."

Elsewhere in the spec case-sensitivity is described for NodeId, but not for BrowseName. Does this sentence mean that ALL Servers must reject TranslateBrowsePath... requests when case does not match even if the server is not case-sensitive?

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2014-09-30 16:59

administrator   ~0005509

Should we clarify the spec to treat case sensitivity for BrowsePath the same as we do for NodeIds in Mantis 1406?

"Defined that string-part of BrowseName shall be case sensitive and the string-part of a NodeId shall be assumed to be case sensitive but servers can make aliases supporting case-insensitive string-parts of NodeIds."

Wolfgang Mahnke

2014-10-15 18:26

developer   ~0005541

My assumption is this is only relevant for TranslateBrowsePath... and I would suggest that we would add text there stating that this service might return nodes that cannot be found by browse.
1.) We have no concept of aliases in BrowseNames
2.) In FDI we have non-browsable nodes and they would need to be accessible with this service. You could argue at the moment this is not allowed by OPC UA spec (I never thought about that before).

Wolfgang Mahnke

2014-11-03 17:33

developer   ~0005590

Added Text to BrowseName:
That is, Clients shall consider them case sensitive. Servers are allowed to handle BrowseNames passed in Service requests as case insensitive. Examples are the TranslateBrowsePathsToNodeIds Service or Event filter.

Jim Luth

2014-11-03 17:34

administrator   ~0005591

Agreed to clarification edited in the ua call.

Issue History

Date Modified Username Field Change
2014-09-04 16:55 Nathan Pocock New Issue
2014-09-30 16:59 Jim Luth Note Added: 0005509
2014-09-30 16:59 Jim Luth Assigned To => Wolfgang Mahnke
2014-09-30 16:59 Jim Luth Status new => assigned
2014-10-15 18:26 Wolfgang Mahnke Note Added: 0005541
2014-11-03 15:53 Jim Luth Target Version => 1.03
2014-11-03 17:33 Wolfgang Mahnke Note Added: 0005590
2014-11-03 17:33 Wolfgang Mahnke Status assigned => resolved
2014-11-03 17:33 Wolfgang Mahnke Resolution open => fixed
2014-11-03 17:34 Jim Luth Note Added: 0005591
2014-11-03 17:34 Jim Luth Status resolved => closed
2014-11-03 17:34 Jim Luth Fixed in Version => 1.03