View Issue Details

IDProjectCategoryView StatusLast Update
000895010000-006: MappingsSpecpublic2023-10-10 16:54
ReporterThomas Merk Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.05.01 
Fixed in Version1.05.03 RC1 
Summary0008950: JSON Encoding of ExpandedNodeId - Namespace risky
Description

For Namespace (non-reversible) it is dedescribed:
"A NamespaceIndex of 1 is always encoded as a JSON number."

I assume the idea is that a server always reserves the namespace index 1 for its own (local) namespace, using its own namespace URI.
Is this really true, e.g. for "stand-alone" publishers not working as a server, i.e. without an own address space?

If the namespace index matches to e.g. "http://opcfoundation.org/UA/DI/" since the meta data contain only data types of namespace 0 and "DI" namespace, wouldnt it be better to encode also namespace 1 with its URI?
Or shall the meta data always contain an URI for the application (at position 1) - whether it is a server or not?

I would expect some clarification, both in

  • part 6 (JSON encoding of ExpandedNodeId )
  • part 5 (DataTypeSchemaHeader)
  • part 14 (DataSetMetaDataType)

Especially should be defined

  • what namespace URIS shall be in the array
  • the index in the array has to be incremetned by 1 to get the "real" namespace index (separate issue 8949)
TagsErrata Needed to Close
Commit Version
Fix Due Date2023-09-01

Activities

Randy Armstrong

2023-05-12 05:55

administrator   ~0019332

Removed all special rules for NamespaceIndex of 1. It was a mistake to assume the JSON encoding would only be used in the context of Session.

Randy Armstrong

2023-05-16 15:39

administrator   ~0019380

Need to delete in 1.04:
A NamespaceIndex of 1 is always encoded as a JSON number.

Jim Luth

2023-05-16 15:39

administrator   ~0019381

Reviewed 1.05.03 . Needs 1.04 Errata to close.

Randy Armstrong

2023-10-05 03:30

administrator   ~0020089

Added Errata to 1.04.13

Randy Armstrong

2023-10-05 03:44

administrator   ~0020090

Added Errata to 1.04.13

Jim Luth

2023-10-10 16:54

administrator   ~0020120

Agreed to Errata 1.04.13.

Issue History

Date Modified Username Field Change
2023-05-09 14:51 Thomas Merk New Issue
2023-05-12 05:55 Randy Armstrong Assigned To => Randy Armstrong
2023-05-12 05:55 Randy Armstrong Status new => resolved
2023-05-12 05:55 Randy Armstrong Resolution open => fixed
2023-05-12 05:55 Randy Armstrong Fixed in Version => 1.05.03 RC1
2023-05-12 05:55 Randy Armstrong Note Added: 0019332
2023-05-16 15:39 Randy Armstrong Note Added: 0019380
2023-05-16 15:39 Jim Luth Note Added: 0019381
2023-08-01 15:56 Jim Luth Fix Due Date => 2023-09-01
2023-08-01 16:50 Jim Luth Tag Attached: Errata Needed to Close
2023-10-05 03:30 Randy Armstrong Note Added: 0020089
2023-10-05 03:44 Randy Armstrong Note Added: 0020090
2023-10-10 16:54 Jim Luth Status resolved => closed
2023-10-10 16:54 Jim Luth Note Added: 0020120