View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000441910000-006: MappingsApi Changepublic2018-10-09 16:222020-04-21 15:13
ReporterJim Luth Assigned ToRandy Armstrong  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Summary0004419: Generated 1.04 resources (21-Jun-2018 20:08) contains references to types not in the specification
Description

https://opcfoundation.org/UA/schemas/1.04/

At least NodeIds.cvs and Opc.Ua.NodeSet2.xml with timestamp (21-Jun-2018 20:08) contains (new, were not there when spec was released) reference to types that are not in the specification.

At least:
EUItemType,17497,VariableType
AnalogUnitItemType,17503,VariableType

Both are NOT in 1.04 spec, and the definition of both based on the NodeSet2 is identical to the already existing type AnalogItemType. (Copied to Additional Information part)

They should be removed.

Additionally the following cannot be found as well
GetEncryptingKeyMethodType,17531,Method
PubSubConnectionTypeAddWriterGroupMethodType,17561,Method
CreateCredentialMethodType,15248,Method
DescribesArgument,129,ReferenceType
DescribesInputArgument,130,ReferenceType
DescribesOptionalInputArgument,131,ReferenceType
DescribesOutputArgument,132,ReferenceType
KeyCredentialConfigurationFolderType,17496,ObjectType
CreateCredentialMethodType_OutputArguments,17495,Variable
DescribesArgument,129,ReferenceType
DescribesInputArgument,130,ReferenceType
DescribesOptionalInputArgument,131,ReferenceType
DescribesOutputArgument,132,ReferenceType

I omitted some of the nodes that are defined as part of those types.

Also it is possible that there are other errors as well, I only looked mostly at the diff to the previous 1.04 resource files (~3 months old).

Also it is possible that some of the changes are in a future errata that I'm not aware of (1.04.1 at the moment). Even on that possibility, I see no purpose of EUItemType and AnalogUnitItemType as they are in practice the same type as AnalogItemType.

If this relates to a future errata (for which the additions would be quite large I must say), it would be nice if this information would be mentioned e.g. in the file comments etc (if possible) to avoid future confusion.

Additional Information

EUItemType
<UAVariableType NodeId="i=17497" BrowseName="EUItemType" DataType="Number" ValueRank="-2">
<DisplayName>EUItemType</DisplayName>
<References>
<Reference ReferenceType="HasProperty">i=17500</Reference>
<Reference ReferenceType="HasProperty">i=17501</Reference>
<Reference ReferenceType="HasProperty">i=17502</Reference>
<Reference ReferenceType="HasSubtype" IsForward="false">i=2365</Reference>
</References>
</UAVariableType>
<UAVariable NodeId="i=17500" BrowseName="InstrumentRange" ParentNodeId="i=17497" DataType="i=884">
<DisplayName>InstrumentRange</DisplayName>
<References>
<Reference ReferenceType="HasTypeDefinition">i=68</Reference>
<Reference ReferenceType="HasModellingRule">i=80</Reference>
<Reference ReferenceType="HasProperty" IsForward="false">i=17497</Reference>
</References>
</UAVariable>
<UAVariable NodeId="i=17501" BrowseName="EURange" ParentNodeId="i=17497" DataType="i=884">
<DisplayName>EURange</DisplayName>
<References>
<Reference ReferenceType="HasTypeDefinition">i=68</Reference>
<Reference ReferenceType="HasModellingRule">i=80</Reference>
<Reference ReferenceType="HasProperty" IsForward="false">i=17497</Reference>
</References>
</UAVariable>
<UAVariable NodeId="i=17502" BrowseName="EngineeringUnits" ParentNodeId="i=17497" DataType="i=887">
<DisplayName>EngineeringUnits</DisplayName>
<References>
<Reference ReferenceType="HasTypeDefinition">i=68</Reference>
<Reference ReferenceType="HasModellingRule">i=80</Reference>
<Reference ReferenceType="HasProperty" IsForward="false">i=17497</Reference>
</References>
</UAVariable>

========================

AnalogUnitItemType

<UAVariableType NodeId="i=17503" BrowseName="AnalogUnitItemType" DataType="Number" ValueRank="-2">
<DisplayName>AnalogUnitItemType</DisplayName>
<References>
<Reference ReferenceType="HasProperty">i=17506</Reference>
<Reference ReferenceType="HasProperty">i=17509</Reference>
<Reference ReferenceType="HasProperty">i=17510</Reference>
<Reference ReferenceType="HasSubtype" IsForward="false">i=2365</Reference>
</References>
</UAVariableType>
<UAVariable NodeId="i=17506" BrowseName="InstrumentRange" ParentNodeId="i=17503" DataType="i=884">
<DisplayName>InstrumentRange</DisplayName>
<References>
<Reference ReferenceType="HasTypeDefinition">i=68</Reference>
<Reference ReferenceType="HasModellingRule">i=80</Reference>
<Reference ReferenceType="HasProperty" IsForward="false">i=17503</Reference>
</References>
</UAVariable>
<UAVariable NodeId="i=17509" BrowseName="EURange" ParentNodeId="i=17503" DataType="i=884">
<DisplayName>EURange</DisplayName>
<References>
<Reference ReferenceType="HasTypeDefinition">i=68</Reference>
<Reference ReferenceType="HasModellingRule">i=80</Reference>
<Reference ReferenceType="HasProperty" IsForward="false">i=17503</Reference>
</References>
</UAVariable>
<UAVariable NodeId="i=17510" BrowseName="EngineeringUnits" ParentNodeId="i=17503" DataType="i=887">
<DisplayName>EngineeringUnits</DisplayName>
<References>
<Reference ReferenceType="HasTypeDefinition">i=68</Reference>
<Reference ReferenceType="HasModellingRule">i=78</Reference>
<Reference ReferenceType="HasProperty" IsForward="false">i=17503</Reference>
</References>
</UAVariable>

=========================

(The already existing AnalogItemType)

<UAVariableType NodeId="i=2368" BrowseName="AnalogItemType" DataType="Number" ValueRank="-2">
<DisplayName>AnalogItemType</DisplayName>
<References>
<Reference ReferenceType="HasProperty">i=2370</Reference>
<Reference ReferenceType="HasProperty">i=2369</Reference>
<Reference ReferenceType="HasProperty">i=2371</Reference>
<Reference ReferenceType="HasSubtype" IsForward="false">i=2365</Reference>
</References>
</UAVariableType>
<UAVariable NodeId="i=2370" BrowseName="InstrumentRange" ParentNodeId="i=2368" DataType="i=884">
<DisplayName>InstrumentRange</DisplayName>
<References>
<Reference ReferenceType="HasTypeDefinition">i=68</Reference>
<Reference ReferenceType="HasModellingRule">i=80</Reference>
<Reference ReferenceType="HasProperty" IsForward="false">i=2368</Reference>
</References>
</UAVariable>
<UAVariable NodeId="i=2369" BrowseName="EURange" ParentNodeId="i=2368" DataType="i=884">
<DisplayName>EURange</DisplayName>
<References>
<Reference ReferenceType="HasTypeDefinition">i=68</Reference>
<Reference ReferenceType="HasModellingRule">i=78</Reference>
<Reference ReferenceType="HasProperty" IsForward="false">i=2368</Reference>
</References>
</UAVariable>
<UAVariable NodeId="i=2371" BrowseName="EngineeringUnits" ParentNodeId="i=2368" DataType="i=887">
<DisplayName>EngineeringUnits</DisplayName>
<References>
<Reference ReferenceType="HasTypeDefinition">i=68</Reference>
<Reference ReferenceType="HasModellingRule">i=80</Reference>
<Reference ReferenceType="HasProperty" IsForward="false">i=2368</Reference>
</References>
</UAVariable>

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0004318 closedRandy Armstrong NodeSets, XSDs and Generated Code Generated 1.04 resources (21-Jun-2018 20:08) contains references to types not in the specification 

Activities

Randy Armstrong

2018-10-09 16:22

administrator   ~0009470

The 1.04 specification is updated with errata and amendments.

Please review the current amendments before assuming they are not defined.

Jim Luth

2018-10-09 16:22

administrator   ~0009471

Agreed to no-fix in telecon.

Jim Luth

2018-10-09 16:22

administrator   ~0009472

Need to move the stuff for the unreleased amendments from the 1.04 branch.

Randy Armstrong

2018-10-09 16:22

administrator   ~0009473

Added '1.05' Category to all new Nodes.
The master branch has these nodes and apps can filter them out.
v1.04 branch does not have these nodes.

Jim Luth

2018-10-09 16:22

administrator   ~0009474

Agreed to changes in Telecon.

Jim Luth

2018-10-09 16:26

administrator   ~0009475

Clone 4318 to Part 6 to update the schema.

Randy Armstrong

2019-03-03 03:38

administrator   ~0010001

Added ReleaseStatus to UANode to indicate when a Draft Node is added. Fixed in OPC UA Part 6 - Mappings Draft 1.05.05 Specification.docx.

Jim Luth

2019-03-08 15:29

administrator   ~0010032

Needs 1.04 Errata.

Randy Armstrong

2020-04-21 15:13

administrator   ~0011952

Closed on Apr 21st WG Call.

Issue History

Date Modified Username Field Change
2018-10-09 16:22 Jim Luth New Issue
2018-10-09 16:22 Jim Luth Status new => assigned
2018-10-09 16:22 Jim Luth Assigned To => Randy Armstrong
2018-10-09 16:22 Jim Luth Issue generated from: 0004318
2018-10-09 16:22 Jim Luth Relationship added related to 0004318
2018-10-09 16:26 Jim Luth Note Added: 0009475
2018-10-09 16:27 Jim Luth Project NodeSets, XSDs and Generated Code => 10000-006: Mappings
2018-10-09 16:27 Jim Luth Category Implementation Bug => Api Change
2019-03-03 03:38 Randy Armstrong Status assigned => resolved
2019-03-03 03:38 Randy Armstrong Resolution open => fixed
2019-03-03 03:38 Randy Armstrong Fixed in Version => 1.05
2019-03-03 03:38 Randy Armstrong Note Added: 0010001
2019-03-08 15:29 Jim Luth Note Added: 0010032
2020-04-21 15:13 Randy Armstrong Status resolved => closed
2020-04-21 15:13 Randy Armstrong Note Added: 0011952