View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000581110000-012: DiscoverySpecpublic2020-07-20 17:462022-06-22 14:58
ReporterJim Luth Assigned ToRandy Armstrong  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version1.05.02 RC1 
Summary0005811: 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

Randy Armstrong

2020-09-13 09:58

administrator   ~0012789

Added conformance units.

Randy Armstrong

2020-09-14 17:30

administrator   ~0012804

Only add Server Side CUs.

Use the right server side CU for push:
Push Model for Global Certificate and TrustList Management
Push Model for KeyCredential Service

Randy Armstrong

2020-09-16 02:48

administrator   ~0012847

Fixed CUs so only CUs associated with a Server are listed.

Jim Luth

2022-06-22 14:58

administrator   ~0016994

Agreed to changes edited in Munich F2F.

Issue History

Date Modified Username Field Change
2020-07-20 17:46 Jim Luth New Issue
2020-07-20 17:46 Jim Luth Status new => assigned
2020-07-20 17:46 Jim Luth Assigned To => Randy Armstrong
2020-07-20 17:46 Jim Luth Issue generated from: 0005731
2020-07-20 17:46 Jim Luth Relationship added related to 0005731
2020-07-20 17:46 Jim Luth Project 10000-014: PubSub => 10000-012: Discovery
2020-09-13 09:58 Randy Armstrong Status assigned => resolved
2020-09-13 09:58 Randy Armstrong Resolution open => fixed
2020-09-13 09:58 Randy Armstrong Note Added: 0012789
2020-09-14 17:30 Randy Armstrong Status resolved => assigned
2020-09-14 17:30 Randy Armstrong Note Added: 0012804
2020-09-16 02:48 Randy Armstrong Status assigned => resolved
2020-09-16 02:48 Randy Armstrong Note Added: 0012847
2022-06-22 14:58 Jim Luth Status resolved => closed
2022-06-22 14:58 Jim Luth Fixed in Version => 1.05.02 RC1
2022-06-22 14:58 Jim Luth Note Added: 0016994