Replies: 2 comments
-
|
Referring to some doubts, let me stress that the semantic diff is far above the XML syntax. It only means that we can read an XML file and validate it against a selected schema (here UANodeSet). Using different XML documents we can express the same OPC UA Information Model. On the other hand, an XML document is just a text, so using the text diff we can distinguish numerous unimportant in the context of the document meaning differences. Let me give you an example. If the NamespaceIndex in the BrowseName (QulifiedName) is 0 we can omit it, and the meaning of the BrowseName is the same, finally it doesn't have any impact on the Information Model - the document meaning is the same. Concluding. Semantic diff means that we are comparing the meaning of the documents, but not only the text used to express the meaning. |
Beta Was this translation helpful? Give feedback.
-
|
I have added a discussion at https://d.strumenta.community/t/opc-ua-dsl-semantic-diff/1224?u=mpostol. Consider joining - just fill the form at https://strumenta.community. |
Beta Was this translation helpful? Give feedback.
-
Do we need UANodeSet semantic diff?
Executive summary
UANodeSetis a domain-specific language implemented using the XML standard. The syntax of theUANodeSetdocuments is defined in the OPC 10000-6: OPC Unified Architecture; 2017, Release 1.04.The schema document is available at http://opcfoundation.org/UA/2011/03/UANodeSet.xsd
The description is covered by the document
Problem
The problem is reported in OPCFoundation/UA-ModelCompiler#75 and the discussion is to be continued here.
Generally speaking, talking about the tracking of the modification we have the following possibilities:
feature that was not widely used,non-critical differences, etc.Following that my questions are:
Beta Was this translation helpful? Give feedback.
All reactions