View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0007625Part 83: UAFX Offline EngineeringSpecpublic2022-01-20 15:502022-04-08 13:38
ReporterWolfgang Mahnke Assigned ToJim Luth  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.00.00 RC2 
Target Version1.00.00 ReleaseFixed in Version1.00.00 RC2 
Summary0007625: Various issues with Mapping NodeSet to AutomationML
Description

Annex A: The mapping of OPC UA DateTime and XML DateTime is not that straight forward, especially for a bidirectional mapping.

A 3.6 Statement on NodeIds is unclear. You cannot just define new NodeIds for well-defined nodes. How does this work, if you bring it back to OPC UA?

A4 BrowseName: Unclear how to decide which NamespaceIndex to use. "Depending on the context of the node". An ObjectType might have InstanceDeclarations using a different Namespace in the BrowseName than the one for the ObjectType.

Table A4: There are no additional common attributes for Objects and ObjectTypes. EventNotifier only for Objects (and Views), IsAbstract only for ObjectTypes. Why is this in one table?

NodeClass Variable Attribute Mapping is not defined.

Table A5: There is no NodeClass BaseVariableType, only VariableType. Historizing is not defined for VariableTypes.

A10: What about versioning, since the UA Spec is evolving over time and new things are added. Same for Annex B, C and D.

TagsNo tags attached.

Activities

Todd Snide

2022-03-18 14:02

developer   ~0016413

Last edited: 2022-03-21 13:00

Fifth and sixth paragraph are addressed in the Part 83 by changing the title of Table A.5.

Todd Snide

2022-03-18 14:23

developer   ~0016415

Last edited: 2022-03-21 13:00

Paragraph 7 has been handled in Mantis issue 7873.

Todd Snide

2022-03-21 12:37

developer   ~0016428

First and second paragraphs, there is no bidirectional mapping specified between UA and UA FX AML. DateTime mapping is defined in OPC Part 6.
As a practical matter specifications that define well known nodes define well known browse paths. It is from the well known browse that the AML object is found. The nodeIDs of the well known nodes are defined in the nodesets of the specification.

Todd Snide

2022-03-21 12:58

developer   ~0016429

Paragraph 3, if the instance declaration BrowseName requires a different namespace than that of the node, then the namespace URI attribute of the Browsename in AML would be filled in with the appropriate URI.

Todd Snide

2022-03-21 13:08

developer   ~0016430

Paragraph 4, in AML we do not model these separately in instances and types so we represent these as merged set. This leads to some nonsensical attributes, i.e IsAbstract on an instance.

Todd Snide

2022-03-21 13:09

developer   ~0016431

As per the included notes the various paragraphs of issues are resolved.

Emanuel Kolb

2022-04-08 13:38

manager   ~0016545

Review done in OE group

Issue History

Date Modified Username Field Change
2022-01-20 15:50 Wolfgang Mahnke New Issue
2022-01-21 14:55 Todd Snide Assigned To => Jim Luth
2022-01-21 14:55 Todd Snide Status new => assigned
2022-03-18 14:02 Todd Snide Note Added: 0016413
2022-03-18 14:23 Todd Snide Note Added: 0016415
2022-03-21 12:37 Todd Snide Note Added: 0016428
2022-03-21 12:58 Todd Snide Note Added: 0016429
2022-03-21 13:00 Todd Snide Note Edited: 0016413
2022-03-21 13:00 Todd Snide Note Edited: 0016415
2022-03-21 13:08 Todd Snide Note Added: 0016430
2022-03-21 13:09 Todd Snide Status assigned => resolved
2022-03-21 13:09 Todd Snide Resolution open => fixed
2022-03-21 13:09 Todd Snide Fixed in Version => 1.00.00 RC2
2022-03-21 13:09 Todd Snide Note Added: 0016431
2022-04-08 13:38 Emanuel Kolb Status resolved => closed
2022-04-08 13:38 Emanuel Kolb Note Added: 0016545