Open CharlieG021163 opened 5 years ago
Agree
Dennis has not accepted yet, but offered alternative Solution The relationship is a composite, so instead of adding an ID, I added the following element under the OperationsRecordTemplateType: <xsd:element name="RecordEntry' type="OperationsRecordEntryTemplateType" minOccurs="0" maxOccurs="unbounded"/>
Also found that the OperationsEvent/OperationsEventRecord was the wrong type. It was OperationsRecordEntryTemplateType, and should have been OperationsRecordTemplateType.
Resubmit to MESA as reply and fixes per Dennis's comments
I agree with the change.
issue is closed in MESA github, but I am moving this to 'Final Review' milestone as the changes are a small bit different to the proposal. Will review the fix applied by MESA once I have someone to assist me looking at and understanding the variance in the fix.
https://github.com/MESAInternational/B2MML-BatchML/issues/53
Add "OperationsRecordSpecificationID" and "OperationsRecordEntry" elements to "OperationsRecordTemplateType" in Common.xsd to align with updated 950002 Operations Record Model
Solution "OperationsRecordTemplateType"
ADD element name="OperationsRecordEntry" type="OperationsRecordEntryTemplateType" minOccurs="1" maxOccurs="unbounded"/> ADD element name="OperationsRecordSpecID"
Support Documents ISA-950002 JWG5 CDV01 version (2019 12) Clause 5.10.3 Operations record template, Table 120 – Operations record template relationship roles
Impacted Types B2MML- Common.xsd, complexType name="OperationsRecordTemplateType"