Skip to content

Commit

Permalink
Update B2MML-TestSpecification.xsd
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
CharlieG021163 authored Aug 15, 2019
1 parent ea787f6 commit 67f5756
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions Schema/B2MML-TestSpecification.xsd
Original file line number Diff line number Diff line change
Expand Up @@ -172,7 +172,7 @@ of test specifications.
minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="Value" type="ValueType"
minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="TestSpecificationPropertychild" type="TestSpecificationPropertyType"
<xsd:element name="TestSpecificationPropertyChild" type="TestSpecificationPropertyType"

This comment has been minimized.

Copy link
@CharlieG021163

CharlieG021163 Aug 15, 2019

Author Collaborator

ERDI, MESA: complexType name = "TestSpecificationPropertyType", CHANGE element name = "TestSpecificationPropertychild" to "TestSpecificationPropertyChild" to fix typeO.

This comment has been minimized.

Copy link
@racheliurui

racheliurui Aug 26, 2019

Collaborator

#12

minOccurs="0" maxOccurs="unbounded"/>
<xsd:group ref="Extended:TestSpecificationProperty" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
Expand Down Expand Up @@ -203,11 +203,11 @@ of test specifications.
minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="TestableObjectPropertyID" type="IdentifierType"
minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="TestSpecificationCriteriaID" type="IdentifierType"
<xsd:element name="TestSpecificationCriteriaID" type="IdentifierType"
minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="WorkDefinitionID" type="IdentifierType"
minOccurs="0" maxOccurs="unbounded"/>
<xsd:group ref="Extended:TestSpecificationEvaluatedProperty" minOccurs="0" maxOccurs="1"/>
<xsd:group ref="Extended:EvaluatedProperty" minOccurs="0" maxOccurs="1"/>

This comment has been minimized.

Copy link
@CharlieG021163

CharlieG021163 Aug 15, 2019

Author Collaborator

ERDI, MESA: complexType name = "EvaluatedPropertyType", CHANGE 'Extended = TestSpecificationEvaluatedProperty" to "EvaluatedPropertyType" to align with updated Part 2 OperationsTest Model's Test Specification object's relationship attributes.

This comment has been minimized.

Copy link
@racheliurui

racheliurui Aug 26, 2019

Collaborator

#25

</xsd:sequence>
</xsd:complexType>

Expand Down

0 comments on commit 67f5756

Please sign in to comment.