From 67f575653e1114b39f45ca6188aad3d001a4a1bf Mon Sep 17 00:00:00 2001 From: CharlieG021163 Date: Thu, 15 Aug 2019 10:22:22 -0600 Subject: [PATCH] Update B2MML-TestSpecification.xsd ERDi, MESA: Fix typeOs. Issue raised: B2MML 7.0 beta has created a B2MML-TestSpecification.xsd schema and created the complex types of "TestResultType" and TestPropertyMeasurementType in the Common Schema. B2MML 7.0 still has the TestResult type as an attribute in each instance resource property per the old version of ISA-95 resource models and B2MML 6.0. This was a composite relationship which did not allow Test Result to be exchanged and queried as a 1st class object. In the new Operations Test Model in updated Part 2, Test Result is a 1st order object that is able to be exchanged/queried. The MESA Committee may reject changing their implementation. If so, ERDi should create an OperationsTest.xsd schema that has test specification type and test result type and allow 1st order transactions. I do not believe that the 1st order transaction were added to the updated part 5. But the updated part 2 as part of the collaboration with OAGi viewed Test Results as a 1st order object. --- Schema/B2MML-TestSpecification.xsd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Schema/B2MML-TestSpecification.xsd b/Schema/B2MML-TestSpecification.xsd index baa3ed3..ac5d236 100644 --- a/Schema/B2MML-TestSpecification.xsd +++ b/Schema/B2MML-TestSpecification.xsd @@ -172,7 +172,7 @@ of test specifications. minOccurs="0" maxOccurs="unbounded"/> - @@ -203,11 +203,11 @@ of test specifications. minOccurs="0" maxOccurs="unbounded"/> - - +