Is there any way to validate the OPC UA schema (currently it is XML Nodeset and in future it might be JSON as well) while defining a new Companion Specification.
Basically, developer and tester will test the defined Mandatory parameters and respective rules as per specification and use CTT in relevant case, BUT is there any way, OPC UA schema can be validated using sample data similar to what we have in JSON Validator?
It is not clear what kind of validation you are expecting.
When the specification is being developed, authors are expected to use the NodeSetValidator to ensure their word document matches the NodeSet.
Once the specification has been published there are CTT test cases for some information models. Overtime it this will become more common.
Thanks Randy, I agree that CTT will be used for validation of the application which has implemented the specifications.
It was just to understand we something can be validated before implementation of the specification in the Nodeset Schema.
JSON Validator can verify the structure/type definition -- https://www.newtonsoft.com/jso.....hema.htm
So, I was just thinking can that be done to the schema defined for the specification to ensure it is valid before products implement it.
Maybe for OPC UA, CTT is the best way for verification and validation both.