View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000581010000-011: Historical AccessSpecpublic2020-07-20 17:442024-06-04 15:35
ReporterJim Luth Assigned ToPaul Hunkar  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionreopened 
Target Version1.05.03 RC1Fixed in Version1.05.03 RC1 
Summary0005810: Missing relation of types to conformance units and profiles
Description

At the moment it is not possible to identify the relation of a type or of instances to a conformance unit and to profiles. This is a growing problem since the OPC UA namespace is constantly extended and there is no way for tooling to reduce the exposed types if only a subset of the OPC UA features is implemented.

OPC UA Part 6 defines a Category field for a Node in the UANodeset. The Category takes a String [ ]. There is currently no information defined that goes into this category. It can be used to provide a list of conformance units.

Each type table needs to add the conformance unit(s) it is related to to allow tooling to select the necessary types based on the profile selection.

The conformance unit goes into the Category of the UANodeset for processing in tooling.

Additional Information

As agreed in the OPC UA meeting on July 14, 2020, each type table must be extended with a list of conformance units that require the type.

Add rows with one column to the end of the table.
The first row contains the heading "Conformance Units" in bold.
The second and following rows contain the name of the conformance units the type is required for.
This is typically one conformance unit.

Example can be found in the following document:
OPC 10000-8 - UA Specification Part 8 - DataAccess Draft 1.05.06.ExtensionCategory2.docx
posted in:
https://opcfoundation.sharepoint.com/UA/Work/Forms/AllItems.aspx?RootFolder=%2FUA%2Fwork%2FMeetings%2F2020%2F2020%2D07%2D14%20Weekly%20Telecon&FolderCTID=0x012000FDF01D76A1A64246B261F99AF1ACA00A&View=%7B10076F95%2D9CBF%2D4395%2D8545%2D378F95701D6A%7D

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0005731 closedMatthias Damm 10000-014: PubSub Missing relation of types to conformance units and profiles 

Activities

Paul Hunkar

2023-01-03 17:12

developer   ~0018394

Added the ConformanceUnit to all of the required tables

Paul Hunkar

2023-01-03 17:31

developer   ~0018396

re-opened to add related mantis issue for missing CU

Paul Hunkar

2024-06-04 15:34

developer   ~0021261

was fixed a long time ago - nothing more to do

Jim Luth

2024-06-04 15:35

administrator   ~0021262

This was fixed and released in 1.05.03

Issue History

Date Modified Username Field Change
2020-07-20 17:44 Jim Luth New Issue
2020-07-20 17:44 Jim Luth Status new => assigned
2020-07-20 17:44 Jim Luth Assigned To => Matthias Damm
2020-07-20 17:44 Jim Luth Issue generated from: 0005731
2020-07-20 17:44 Jim Luth Relationship added related to 0005731
2020-07-20 17:45 Jim Luth Project 10000-014: PubSub => 10000-011: Historical Access
2020-07-20 17:45 Jim Luth Assigned To Matthias Damm => Rod Stein
2022-12-01 06:51 Paul Hunkar Assigned To Rod Stein => Paul Hunkar
2023-01-03 17:12 Paul Hunkar Status assigned => resolved
2023-01-03 17:12 Paul Hunkar Resolution open => fixed
2023-01-03 17:12 Paul Hunkar Fixed in Version => 1.05.03 RC1
2023-01-03 17:12 Paul Hunkar Note Added: 0018394
2023-01-03 17:31 Paul Hunkar Status resolved => feedback
2023-01-03 17:31 Paul Hunkar Resolution fixed => reopened
2023-01-03 17:31 Paul Hunkar Status feedback => assigned
2023-01-03 17:31 Paul Hunkar Note Added: 0018396
2023-04-25 15:53 Jim Luth Target Version => 1.05.03 RC1
2024-06-04 15:34 Paul Hunkar Status assigned => resolved
2024-06-04 15:34 Paul Hunkar Note Added: 0021261
2024-06-04 15:35 Jim Luth Status resolved => closed
2024-06-04 15:35 Jim Luth Note Added: 0021262