View Issue Details

IDProjectCategoryView StatusLast Update
000722410000-006: MappingsSpecpublic2021-09-14 16:10
ReporterSendMatt Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0007224: Possible inconsistent definition of JSON Object Definition for a 'NodeId' <-> 'ExpandedNodeId' at 'Id'
Description

Please see https://reference.opcfoundation.org/Core/docs/Part6/5.4.2/

chapter 5.4.2.10 NodeId --> Table 23 – JSON Object Definition for a NodeId:
"...
Id The Identifier.
The value of the [!!!] id field [!!!] specifies the encoding of this field.
..."

chapter 5.4.2.11 ExpandedNodeId --> Table 24 – JSON Object Definition for an ExpandedNodeId:
"...
Id The Identifier.
The value of the [!!!] ‘t’ field [!!!] specifies the encoding of this field.
..."

I am not common to "JSON" but somehow it looks like an inconsistent definiton (marked above with "[!!!]") of "id" field;
I would assume that also at '5.4.2.10 NodeId' the definition " ‘t’ field" [JSON data type syntax ?? ] instead of "id field" is correct.
Please check if my assumption is correct or not. Thanks.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Randy Armstrong

2021-09-14 04:35

administrator   ~0014838

Typos fixed in text, Now says
The value of the IdType field specifies the encoding of this field.
in DRAFT 5.

Jim Luth

2021-09-14 16:10

administrator   ~0014853

Agreed to changes in 1.05.1 Draft 5.

Issue History

Date Modified Username Field Change
2021-09-13 10:36 SendMatt New Issue
2021-09-14 04:35 Randy Armstrong Assigned To => Randy Armstrong
2021-09-14 04:35 Randy Armstrong Status new => resolved
2021-09-14 04:35 Randy Armstrong Resolution open => fixed
2021-09-14 04:35 Randy Armstrong Note Added: 0014838
2021-09-14 16:10 Jim Luth Status resolved => closed
2021-09-14 16:10 Jim Luth Fixed in Version => 1.05
2021-09-14 16:10 Jim Luth Note Added: 0014853