View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004967NodeSets, XSDs and Generated CodeFeature Requestpublic2019-08-22 09:372021-11-17 18:24
ReporterWolfgang Mahnke Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version1.05.00 
Summary0004967: Relating NodeSetFile content to Profiles
Description

Remark: This topic has initial already been discussed at F2F meeting in Erlangen 2019

Example question that I would like to have answered in a formalized way is:
What ObjectTypes do I have to support in order to support the "A & C Base Condition Server Facet" Profile?

Overall goal: When I define a set of Profiles, I should know what parts of the NodeSet-File (Namespace 0) I need. I only need to put in the content into the server that is needed. As Namespace 0 is growing this becomes more of an issue. That concept should ideally also be applicable to companion specs, e.g. when they define several profiles.

As solution we talked about relating the NodeSet-File entries to the conformance units, either in the NodeSet-File or in the database or both. Randy was proposing the Category element in the NodeSet-File, and we talked about adding a database column and providing some query interface for the profile database.

Overall goal: When I define a set of Profiles, I should know what parts of the NodeSet-File (Namespace 0) I need. But that concept should ideally also be applicable to companion specs, e.g. when they define several profiles.

We talked about relating the NodeSet-File entries to the conformance units, either in the NodeSet-File or in the database or both. Randy was proposing the Category element in the NodeSet-File, and we talked about adding a database column and providing some query interface for the profile database.

Additional Information

By the way: This profile contains a conformance unit called “A & C ConditionClasses” with a test case described as:
“Check the ConditionClass type hierarchy is defined in the type system.” Expected Results: Definitions match specifications. Part 9 section 5.9.2 Figure 20, Table 55 (and derived types).”
That means that the expected result changes when we change Part 9 (e.g. adding Subtypes). It would get worse if we add a section, figure or table in the beginning, because the numbers would be broken.
With a relation to the NodeSet-File content this would be made explicit, but that would require the relation on the test cases.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Randy Armstrong

2020-09-11 10:56

administrator   ~0012779

Added list of ConformanceUnits to UANode.
This will have to match the ConformanceUnits appended to the definition in the Specification.

Randy Armstrong

2021-02-23 17:10

administrator   ~0013767

Need to automatically insert categories when validator runs.

Randy Armstrong

2021-03-02 13:07

administrator   ~0013871

Now add conformance units to category list.

Jim Luth

2021-03-02 18:57

administrator   ~0013913

Agreed to reopen in Virtual F2F. Will need code changes for the validator to understand some of the custom tables for CUs used in Parts 3 & 5.

Randy Armstrong

2021-11-16 22:44

administrator   ~0015332

Should have already been addressed.

Randy Armstrong

2021-11-17 18:20

administrator   ~0015342

Fixing mantis record.

Randy Armstrong

2021-11-17 18:23

administrator   ~0015343

Issue has been resolved with ConformanceUnits added to all Node tables in specifications.
Validator and specs have been updated.

Jim Luth

2021-11-17 18:24

administrator   ~0015344

Reviewed wit h Randy -- agreed it was already fixed in 1.05.00

Issue History

Date Modified Username Field Change
2019-08-22 09:37 Wolfgang Mahnke New Issue
2019-11-19 00:40 Randy Armstrong Assigned To => Randy Armstrong
2019-11-19 00:40 Randy Armstrong Status new => assigned
2020-09-11 10:56 Randy Armstrong Status assigned => resolved
2020-09-11 10:56 Randy Armstrong Resolution open => fixed
2020-09-11 10:56 Randy Armstrong Note Added: 0012779
2020-11-10 17:22 Jim Luth Target Version => 1.05
2021-02-23 17:10 Randy Armstrong Status resolved => assigned
2021-02-23 17:10 Randy Armstrong Note Added: 0013767
2021-03-02 13:07 Randy Armstrong Status assigned => resolved
2021-03-02 13:07 Randy Armstrong Note Added: 0013871
2021-03-02 18:57 Jim Luth Status resolved => feedback
2021-03-02 18:57 Jim Luth Resolution fixed => reopened
2021-03-02 18:57 Jim Luth Note Added: 0013913
2021-11-16 22:44 Randy Armstrong Status feedback => resolved
2021-11-16 22:44 Randy Armstrong Note Added: 0015332
2021-11-17 18:20 Randy Armstrong Status resolved => assigned
2021-11-17 18:20 Randy Armstrong Note Added: 0015342
2021-11-17 18:23 Randy Armstrong Status assigned => resolved
2021-11-17 18:23 Randy Armstrong Resolution reopened => fixed
2021-11-17 18:23 Randy Armstrong Fixed in Version => 1.05.00
2021-11-17 18:23 Randy Armstrong Note Added: 0015343
2021-11-17 18:24 Jim Luth Status resolved => closed
2021-11-17 18:24 Jim Luth Note Added: 0015344