View Issue Details

IDProjectCategoryView StatusLast Update
0009052NodeSets, XSDs and Generated CodeImplementation Bugpublic2023-12-04 20:00
ReporterThomas Merk Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.05.02 
Fixed in Version1.05.03 
Summary0009052: NodeSet does not match specification
Description

I found some differences between NodeSet2.xml and specification.
I tool the NodeSet2 xml from guthub using "latest" branch since I wnated to access 1.05.02

There are - at least - 4 node now located as property of "BaseEventType" (i=2041) which should be properties of "ConditionType":

  • "ConditionClassId" (i=31771)
  • "ConditionClassName" (i=31774)
  • "ConditionSubClassId" (i=31773)
  • "ConditionSubClassName" (31774)

There are also strange "HasModellingRule" references at properties of variable instances - e.g. "Id" (i=10021)
The mentioned "Id" is NOT a property of a type, but the property of a component of a type, here
"NonExclusiveLimitAlarmType" - "HighHighState" - "Id"

I assume that this is a bug as well since it would imply that the "Id" (mandatory for "TwoStateVariableType") shall be optional if used at "HighHighState".

I stopped investigation at that time since this NodeSet2.xml is not usable.
There may be other bugs in NodeSet2 as well.

TagsNo tags attached.
Commit Version1.05.03
Fix Due Date2023-11-14

Relationships

related to 0008039 closedJeff Harding 10000-005: Information Model Support ConditionClassId and ConditionSubClassId feature for BaseEventType 
related to 0006412 closedPaul Hunkar 10000-009: Alarms and Conditions Clarification needed for TwoStateVariableType TrueState and FalseState 

Activities

Randy Armstrong

2023-07-24 07:31

administrator   ~0019714

WRT ConditionClassId: the NodeSet is correct. The mantis issue 8039 covers the change is linked to this issue now.

WRT HasModellingRule on i=10021: The nodeSet looks correct. Can you clarify what the issue is?

Randy Armstrong

2023-11-14 16:53

administrator   ~0020359

Delete ConditionClassId property on BaseEventType, move Properties on ConditionType to BaseEventType instead assigning new NodeIds.

Nothing to do for the Id since it is correct.

Randy Armstrong

2023-11-16 02:49

administrator   ~0020364

The Properties in ConditionType must exist because they change the ModellingRule from Optional to Mandatory.

Randy Armstrong

2023-11-21 16:24

administrator   ~0020391

ConditionType is not fixed completely.

Randy Armstrong

2023-12-04 18:57

administrator   ~0020470

Optional nodes needed to be explicitly declared. Fixed and verified by Matthias.

Jim Luth

2023-12-04 20:00

administrator   ~0020484

Agreed to change in virtual F2F.

Issue History

Date Modified Username Field Change
2023-07-24 06:47 Thomas Merk New Issue
2023-07-24 07:08 Randy Armstrong Relationship added related to 0008039
2023-07-24 07:14 Randy Armstrong Relationship added related to 0006412
2023-07-24 07:31 Randy Armstrong Assigned To => Randy Armstrong
2023-07-24 07:31 Randy Armstrong Status new => feedback
2023-07-24 07:31 Randy Armstrong Note Added: 0019714
2023-11-14 16:53 Randy Armstrong Note Added: 0020359
2023-11-14 16:53 Randy Armstrong Status feedback => assigned
2023-11-14 16:53 Jim Luth Commit Version => 1.05.03
2023-11-14 16:53 Jim Luth Fix Due Date => 2023-11-15
2023-11-16 02:49 Randy Armstrong Status assigned => resolved
2023-11-16 02:49 Randy Armstrong Resolution open => no change required
2023-11-16 02:49 Randy Armstrong Note Added: 0020364
2023-11-21 16:24 Randy Armstrong Status resolved => assigned
2023-11-21 16:24 Randy Armstrong Note Added: 0020391
2023-12-04 18:57 Randy Armstrong Status assigned => resolved
2023-12-04 18:57 Randy Armstrong Note Added: 0020470
2023-12-04 18:57 Randy Armstrong Resolution no change required => fixed
2023-12-04 18:57 Randy Armstrong Fix Due Date 2023-11-15 => 2023-11-14
2023-12-04 20:00 Jim Luth Status resolved => closed
2023-12-04 20:00 Jim Luth Fixed in Version => 1.05.03
2023-12-04 20:00 Jim Luth Note Added: 0020484