Log In
02/22/2022
Offline
Hi all
I’m a little bit confuced about the usage of conformance units: according the definition https://reference.opcfoundatio…..105/docs/F the categroy tag is allowed also for all subtypes of UAInstance (UAObject, UAVariable, UAMethode, UAView) and not only for the subtypes of UAType (UAObjectType, UAVariableType, UADataType, UAReferenceType). Both of them are subtypes of UANode, which defines the category tag.
By using some conformance units (e.g. “ISA-95 Job Control Stop”) – this defines the availability of the Stop Method. So why are these conformance units not available in the NodeSet?
Some other conformance units are impossible to add inside a nodeset in a usefull way (e.g. overwrite optional to mandatory, some prosa text like min string-length = 64chars, predefined key-value pairs [string comparison]…)
Best regards
Patrick
05/30/2017
Offline
The tooling was updated so the word document is processed to find the CUs and add them to the NodeSet before release.
This requires that document authors follow specific conventions when creating the tables.
in this case it appears Stop Method
https://reference.opcfoundatio…..s/6.2.1.11
is missing the Conformance Units at the bottom of the table that you see here:
Moderators-Specifications
Moderators-Companion
Moderators-Implementation
Moderators-Certification
Moderators-COM
02/24/2014
Offline
It is important to remember that the release date of many of the companion specification is before the tooling updates to support CU at the bottom of table. The Base UA specification entered Mantis issue on those parts to track when those specification were updated to support the tooling. The same can be done for companion specification to trigger updates in the companion specifications.
It is also important to remember that the CU at the bottom of a table trigger the inclusion of that specific information model Node, there are many other ConformanceUnits that are not listed at the bottom of the table that govern optional items in the Node definition. They are not listed, since Facet will first require the base functionality that include all of the mandatory item, before listing optional ConformanceUnits. The Nodeset will not include the complete set of ConformanceUnits. It is also expected – especially when related to security that new ConformanceUnits and Facets will be defined without changes to a Nodeset.
Paul Hunkar - DSInteroperability
1 Guest(s)
Usage Policy