View Issue Details

IDProjectCategoryView StatusLast Update
000434910000-007: ProfilesSpecpublic2020-09-22 16:12
ReporterPaul Hunkar Assigned ToPaul Hunkar  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Summary0004349: Historical Access Data Max Nodes Read Continuation Point
Description

The historical Access data Max nodes read continuation point conformance unit is incorrect. It states that the number of continuation point must equal the number of point allowed in a call, but the specification clearly states that this is not the case

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0006030 assignedAlexander Allmendinger Compliance Test Tool (CTT) Unified Architecture Historical Access Data Max Nodes Read Continuation Point 

Activities

Paul Hunkar

2018-07-31 18:27

developer   ~0009241

from additional review we think this conformance unit should just be deleted. the continuation points are checked in Base Info server capabilities as well as the max nodes

Jim Luth

2018-08-14 15:59

administrator   ~0009311

Rod needs to check if anything needs to be changed in Part 11.

Jim Luth

2018-08-14 16:00

administrator   ~0009312

Agreed to remove this conformance unit.

Paul Hunkar

2018-08-17 13:45

developer   ~0009320

There is also an identical conformance unit that is associated with events "Historical Access Event Max Events Read Continuation Point"

this also should be removed

Karl Deiretsbacher

2020-09-17 17:37

developer   ~0012925

Discussed in UA virtual F2F on 2020-09-17. Fixed v1.03 and v1.04 as follows:
The CUs "Historical Access Data Max Nodes Read Continuation Point" and "Historical Access Event Max Events Read Continuation Point" have been removed from the Facets and subsequently deleted.

Jim Luth

2020-09-22 16:12

administrator   ~0012974

Agreed to removal in telecon.

Issue History

Date Modified Username Field Change
2018-07-31 18:03 Paul Hunkar New Issue
2018-07-31 18:27 Paul Hunkar Note Added: 0009241
2018-08-14 15:59 Jim Luth Assigned To => Paul Hunkar
2018-08-14 15:59 Jim Luth Status new => assigned
2018-08-14 15:59 Jim Luth Note Added: 0009311
2018-08-14 16:00 Jim Luth Note Added: 0009312
2018-08-17 13:45 Paul Hunkar Note Added: 0009320
2020-09-17 14:13 Jim Luth Issue cloned: 0006030
2020-09-17 14:13 Jim Luth Relationship added related to 0006030
2020-09-17 17:37 Karl Deiretsbacher Status assigned => resolved
2020-09-17 17:37 Karl Deiretsbacher Resolution open => fixed
2020-09-17 17:37 Karl Deiretsbacher Note Added: 0012925
2020-09-22 16:12 Jim Luth Status resolved => closed
2020-09-22 16:12 Jim Luth Fixed in Version => 1.04
2020-09-22 16:12 Jim Luth Note Added: 0012974