Scheduled For Release 2018-09-20
2 of 2 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
2 of 2 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
2 of 2 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
4 of 4 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
5 of 5 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
  • 0007591: [Spec] Transfersubscription text, how can a server check the support of the profiles of the new client? (Matthias Damm)
  • 0007930: [Spec] Parallel redundancy support for non-transparent and transparent server support (Jim Luth)
2 of 2 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
  • 0007591: [Spec] Transfersubscription text, how can a server check the support of the profiles of the new client? (Matthias Damm)
  • 0007930: [Spec] Parallel redundancy support for non-transparent and transparent server support (Jim Luth)
2 of 2 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
15 of 16 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
0 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
  • 0008039: [Spec] Support ConditionClassId and ConditionSubClassId feature for BaseEventType (Jeff Harding)
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
6 of 6 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
  • 0008435: [Spec] Datatype for CertificateErrorEventId within AuditOpenSecureChannelEventType should be ByteString instead of String (Randy Armstrong)
  • 0009018: [Spec] Need a way to express metadata for Key- Value pairs (Jeff Harding)
  • 0008516: [Spec] How can a tool find out which Namespace 0 NodeSet is newer / better? (Jeff Harding)
  • 0003105: [Spec] NonTransparent Hot+PM: Increase information about redundant servers (Jeff Harding)
  • 0008007: [Spec] Ambiguity in the definition of 3DOrientationType (Jeff Harding)
4 of 5 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
4 of 4 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
4 of 4 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
4 of 4 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
  • 0007393: [Spec] Is there a missing type XMLElement in Opc.Ua.Types.xsd? (Randy Armstrong)
  • 0007381: [Spec] Inconsistency between NodeSet (AllowSub'T'ypes) and Errata 1.04.10 + 1.05 RC1 (AllowSub't'ypes ) (Randy Armstrong)
2 of 2 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
  • 0007393: [Spec] Is there a missing type XMLElement in Opc.Ua.Types.xsd? (Randy Armstrong)
  • 0007381: [Spec] Inconsistency between NodeSet (AllowSub'T'ypes) and Errata 1.04.10 + 1.05 RC1 (AllowSub't'ypes ) (Randy Armstrong)
2 of 2 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
3 of 3 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
11 of 11 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
  • 0009615: [Spec] Clarification for 'SubjectName' and 'subject in Part 6, 'subject' in Part 12 and 'subject name' in Part 18 (Randy Armstrong)
  • 0009093: [Spec] Invalid reference to definition of ExpandedNodeId in OPC 10000-6 / Missing definition of ExpandedNodeId in OPC 10000-3 (Randy Armstrong)
  • 0009155: [Spec] Client ApplicationUri should not be required to configure reverse connect on server side (Randy Armstrong)
  • 0009154: [Spec] ApplicationUri for a client in reverse connect in server (Randy Armstrong)
  • 0009153: [Spec] New string NodeId encoding is a breaking change (Randy Armstrong)
4 of 5 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
2 of 4 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
0 of 1 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
3 of 4 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
3 of 4 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
2 of 2 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
9 of 10 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
0 of 3 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
2 of 2 issue(s) resolved View Issues
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
0 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
  • 0005810: [Spec] Missing relation of types to conformance units and profiles (Paul Hunkar)
  • 0008743: [Spec] Event Configuration for event received from an external server (Paul Hunkar)
  • 0002077: [Spec] OPC UA specification monitoring mode does not account for historical data changes (Paul Hunkar)
  • 0008742: [Spec] EventId and insertion of events (Paul Hunkar)
  • 0008644: [Spec] History of events - does not explain EventId requirements well enough (Paul Hunkar)
  • 0008453: [Spec] Timestamps related error handling needs clarification (Paul Hunkar)
  • 0008657: [Spec] Substring or indexes in an array cause a retrieval problem (Paul Hunkar)
  • 0007906: [Spec] Clarification of ReadDetails handling with ContinuationPoint (Paul Hunkar)
  • 0008522: [Spec] HistoricalDataConfigurationType defintion table ExceptiondevationFormat has wrong datatype (Paul Hunkar)
9 of 9 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
0 of 9 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
0 of 9 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
3 of 3 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
3 of 3 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
  • 0008064: [Spec] Need a detailed workflow description for Application Registration and Certificate Management (Matthias Damm)
  • 0008063: [Spec] Client behaviour for connections to GDS need clarification (Matthias Damm)
  • 0007459: [Spec] Add recommendation for naming convention of certificates when they use ECC (Randy Armstrong)
  • 0007446: [Spec] 7.5.37.6.3 StartSigningRequest - Remove reference to 1048 bits (Randy Armstrong)
4 of 4 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
7 of 7 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
  • 0009831: [Spec] Clarification needed for BaseConfigurationRecordDataType.Name
  • 0009830: [Spec] Inconsistency between figures for push order
  • 0009828: [Spec] Duplicate configuration of TransportProfileUri
  • 0009827: [Spec] ServerEndpointDataType UserTokenPolicies must be changed
  • 0009826: [Spec] Handling of ApplicationIdentity and certificate content changes
  • 0009825: [Spec] Invalid ConfigurationFileType Open mode option specified
  • 0009817: [Spec] AddCertificate Method has backward compatibility issue if isTrustedCertificate=FALSE
0 of 7 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
4 of 4 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
  • 0007424: [Spec] PubSub JSON encoding for DataSetMessage needs reversible encoding for DataValue (Matthias Damm)
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
  • 0007424: [Spec] PubSub JSON encoding for DataSetMessage needs reversible encoding for DataValue (Matthias Damm)
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
  • 0007036: [Spec] Timestamp and Status in keep-alive JSON DataSetMessage not clearly specified (Matthias Damm)
  • 0007871: [Spec] JSON DataSetMessage fields Timestamp and StatusCode need clarification. (Matthias Damm)
  • 0008053: [Spec] Information in PubSubConfiguration2DataType missing in PublishSubscribeType (Matthias Damm)
  • 0008055: [Spec] No capability for Security Key management (Matthias Damm)
  • 0005800: [Spec] For the MQTT PubSub encoding, specify a gzipped version of the body/payload for huge cost savings (Matthias Damm)
  • 0007919: [Spec] DatagramDataSetReaderTransportType has wrong base type (Matthias Damm)
  • 0008054: [Spec] CloseAndUpdate is missing error code for empty ConfigurationReferences array (Matthias Damm)
7 of 7 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
15 of 15 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
18 of 18 issue(s) resolved View Issues
Scheduled For Release 2021-10-19
  • 0009216: [Spec] JSON PubSubConnection definition: NetworkAddress should be excluded too. (Matthias Damm)
  • 0009217: [Spec] JSON DataSetMetaData definition should have a Timestamp (Matthias Damm)
  • 0009193: [Spec] StructureDefinition.DefaultEncodingId is not useful as described. (Matthias Damm)
  • 0008922: [Spec] Need JSON DataSetMessage option to include only minor meta data version (Matthias Damm)
  • 0008729: [Spec] How can UADP heartbeat messages be recognized? (Matthias Damm)
  • 0008474: [Spec] It is not clear what goes into DataTypeSchemaHeader fields of DataSetMetaDataType and/or UABinaryFileDataTupe (Matthias Damm)
  • 0008414: [Spec] DefaultDatagramPublisherId and related concepts need better explanation (Matthias Damm)
7 of 7 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
0 of 2 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
  • 0007418: [Spec] NodeSet: SafetyPDUsType has wrong double reference to subordinate components (Randy Armstrong)
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
  • 0007380: [Spec] Testing is impeded by missing possibility to distinguish between parameterized and currently active communication parameters (Max Walter)
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
  • 0009681: [Spec] Section about "Duration of Demand" misses explanations about timeout-based and bidirectional approaches. (Christian Eitner)
  • 0009680: [Spec] Requirement 5.6 "Ignore All-Zero SPDUs" Needs Detailing (Christian Eitner)
  • 0009621: [Spec] Normative changes in nodeset should be noted in the change log in the specification (Christian Eitner)
0 of 3 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2016-11-29
1 of 1 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
0 of 1 issue(s) resolved View Issues
Scheduled For Release 2012-02-09
0 of 1 issue(s) resolved View Issues
Scheduled For Release 2013-01-22
9 of 9 issue(s) resolved View Issues
Scheduled For Release 2015-07-09
4 of 4 issue(s) resolved View Issues
Scheduled For Release 2018-03-13
7 of 8 issue(s) resolved View Issues
Scheduled For Release 2018-09-20
7 of 8 issue(s) resolved View Issues
Scheduled For Release 2024-06-18
0 of 3 issue(s) resolved View Issues