View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000573110000-014: PubSubSpecpublic2020-06-16 20:312021-09-23 15:14
ReporterMatthias Damm Assigned ToMatthias Damm  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionfixed 
Summary0005731: 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 0005807 closedKarl Deiretsbacher 10000-008: Data Access Missing relation of types to conformance units and profiles 
related to 0005806 closedJeff Harding 10000-005: Information Model Missing relation of types to conformance units and profiles 
related to 0005808 closedPaul Hunkar 10000-009: Alarms and Conditions Missing relation of types to conformance units and profiles 
related to 0005809 closedKarl Deiretsbacher 10000-010: Programs Missing relation of types to conformance units and profiles 
related to 0005810 closedPaul Hunkar 10000-011: Historical Access Missing relation of types to conformance units and profiles 
related to 0005811 closedRandy Armstrong 10000-012: Discovery Missing relation of types to conformance units and profiles 
related to 0005812 closedRod Stein 10000-013: Aggregates Missing relation of types to conformance units and profiles 
related to 0005813 closedMax Walter 10000-015: Safety Missing relation of types to conformance units and profiles 
related to 0005814 closedWolfgang Mahnke 10000-016: State Machines Missing relation of types to conformance units and profiles 
related to 0005815 closedPaul Hunkar 10000-017: Alias Names Missing relation of types to conformance units and profiles 
related to 0005816 closedMatthias Damm 10000-018: Role-Based Security Missing relation of types to conformance units and profiles 
related to 0005817 closedJeff Harding 10000-019: Dictionary Reference Missing relation of types to conformance units and profiles 
related to 0005818 closedJeff Harding 10000-020: File Transfer Missing relation of types to conformance units and profiles 
related to 0006196 closedKarl Deiretsbacher 10000-100: Devices Missing relation of types to conformance units and profiles 
related to 0006982 closedWolfgang Mahnke 10000-022: Base Network Model Missing relation of types to conformance units and profiles 
related to 0007302 closedMatthias Damm 10000-007: Profiles Missing relation of types to conformance units and profiles 

Activities

Matthias Damm

2021-09-22 17:57

developer   ~0014926

Added in OPC 10000-14 - UA Specification Part 14 - PubSub 1.05.0 Draft36.docx
TBD - provide description for all CUs as clone to Part 7

PubSub Parameters Discovery
Core data structures already required for basic discovery

PubSub Parameters Discovery Extended
Core data structures for PubSub objects

PubSub Parameters PublishedDataSet
Configuration parameters used in a Publisher for PublishedDataSet

PubSub Parameters PublishedDataSet Custom
PubSub Parameters PublishedDataSet Events

PubSub Parameters SubscribedDataSet
PubSub Parameters SubscribedDataSet Mirror
PubSub Parameters SubscribedDataSet Standalone

PubSub Parameters Configuration
PubSub Parameters Configuration2

PubSub Parameters UADP
PubSub Parameters JSON
PubSub Parameters QoS
PubSub Parameters Datagram
PubSub Parameters Broker

PubSub Model SKS
PubSub Model SKS PushTarget

PubSub Model Base
Types needed for the basic information model

PubSub Model PublishedDataSet
PubSub Model PublishedDataSet Events

PubSub Model SubscribedDataSet
PubSub Model SubscribedDataSet Mirror
PubSub Model SubscribedDataSet Standalone

PubSub Model Diagnostics

PubSub Model Status Event
PubSub Model Diagnostics Events

PubSub Model UADP
PubSub Model JSON
PubSub Model Datagram
PubSub Model Broker

Jim Luth

2021-09-23 15:14

administrator   ~0014967

Agreed to changes in Virtual F2F.

Issue History

Date Modified Username Field Change
2020-06-16 20:31 Matthias Damm New Issue
2020-06-16 20:31 Matthias Damm Status new => assigned
2020-06-16 20:31 Matthias Damm Assigned To => Matthias Damm
2020-06-17 11:04 Matthias Damm Summary Missing relation of types to conformance units ans profiles => Missing relation of types to conformance units and profiles
2020-07-14 19:44 Matthias Damm Additional Information Updated
2020-07-20 17:38 Jim Luth Issue cloned: 0005806
2020-07-20 17:38 Jim Luth Relationship added related to 0005806
2020-07-20 17:40 Jim Luth Issue cloned: 0005807
2020-07-20 17:42 Jim Luth Relationship added related to 0005807
2020-07-20 17:42 Jim Luth Issue cloned: 0005808
2020-07-20 17:42 Jim Luth Relationship added related to 0005808
2020-07-20 17:43 Jim Luth Issue cloned: 0005809
2020-07-20 17:43 Jim Luth Relationship added related to 0005809
2020-07-20 17:44 Jim Luth Issue cloned: 0005810
2020-07-20 17:44 Jim Luth Relationship added related to 0005810
2020-07-20 17:46 Jim Luth Issue cloned: 0005811
2020-07-20 17:46 Jim Luth Relationship added related to 0005811
2020-07-20 17:52 Jim Luth Issue cloned: 0005812
2020-07-20 17:52 Jim Luth Relationship added related to 0005812
2020-07-20 17:59 Jim Luth Issue cloned: 0005813
2020-07-20 17:59 Jim Luth Relationship added related to 0005813
2020-07-20 18:01 Jim Luth Issue cloned: 0005814
2020-07-20 18:01 Jim Luth Relationship added related to 0005814
2020-07-20 18:02 Jim Luth Issue cloned: 0005815
2020-07-20 18:02 Jim Luth Relationship added related to 0005815
2020-07-20 18:03 Jim Luth Issue cloned: 0005816
2020-07-20 18:03 Jim Luth Relationship added related to 0005816
2020-07-20 18:04 Jim Luth Issue cloned: 0005817
2020-07-20 18:04 Jim Luth Relationship added related to 0005817
2020-07-20 18:05 Jim Luth Issue cloned: 0005818
2020-07-20 18:05 Jim Luth Relationship added related to 0005818
2020-10-30 09:30 Karl Deiretsbacher Issue cloned: 0006196
2020-10-30 09:30 Karl Deiretsbacher Relationship added related to 0006196
2021-06-03 19:25 Jim Luth Issue cloned: 0006982
2021-06-03 19:25 Jim Luth Relationship added related to 0006982
2021-09-22 17:57 Matthias Damm Status assigned => resolved
2021-09-22 17:57 Matthias Damm Resolution open => fixed
2021-09-22 17:57 Matthias Damm Note Added: 0014926
2021-09-23 15:01 Jim Luth Issue cloned: 0007302
2021-09-23 15:01 Jim Luth Relationship added related to 0007302
2021-09-23 15:14 Jim Luth Status resolved => closed
2021-09-23 15:14 Jim Luth Fixed in Version => 1.05
2021-09-23 15:14 Jim Luth Note Added: 0014967