ETPartners / b2mmlv7beta

b2mmlv7beta for review
2 stars 3 forks source link

Common.xsd: Change"InformationObjectID" to choice of "InformationObject" or "ExternalReferenceID" in "OperationsRecordEntryTemplateType" and ADD InformationObject.xsd to align with updated 950002, Operations Record Model #68

Open CharlieG021163 opened 5 years ago

CharlieG021163 commented 5 years ago

ERDi, MESA: To align with Updated 950002, Operations Record Model and Operations Event Model and with Updated 950004, Work Record Model, Background In the Operations Record Model, the Operations record entry template object has the "Corresponds to an entry in" dependency relationship to the Information object object with a 0..1 multiplicty. The Operations Record Model is an abstract model where its objects are used in the Operations Event Model (950002) and Work Record Model (950004). As defined in Clause 5.10.4 Operations record entry template, Table 122 – Operations record entry template relationships, the information object is either an embedded object or an external reference ID in an implementation. This choice is explicitly stated in the updated 950002.

The Common.xsd misrepresents the two choices for the InformationObject element as:

1. The current Common.xsd does not support a choice between "InformationObject" and "InformationObjectID" 2. In Clause 5.10.4 Operations record entry template, the Information Object and External Reference ID are the defined role names in Table 122, respectively, which are not the element names in Common.xsd. 3. The type used for both elements do not support the 0..1 multiplicity of the choice applied. 4. For "InformationObject", type="TextType" minOccurs="0"/> does not support an embedded first order object from 950002, 950004 or 3rd Party information objects. 5. For "InformationObjectID" type="IdentifierType"/> does support an external reference ID but is confusing since it does not use the defined role name, ExternalReferenceID. **Supporting Document** _ISA-950002 JWG5 CDV01 version (2019 12)_ Clause 5.10.1 Operations record model (abstract), Figure 17 – Operations record model (abstract ) Clause 5.10.4 Operations record entry template, Table 122 – Operations record entry template relationships Clause 5.11.11 Operations event record entry, Table 142 – Operations event record entry relationships _ISA-950004 JWG5 CDV01 version (2019 12)_ Clause 15.6 Work record entry, Table 110 – Work record entry relationships **Impacted Types and Solution** 1. ADD: New schema: InformationObject.xsd with xsd:complexType name="InformationObjectType" which has choice of one of all the ISA-95 objects or 3rd party object. xsd:complexType name="InformationObjectTypeType" for the InformationObjectType element in OperationsRecordEntryTemplateType in Common.xsd _Common.xsd_ 1. ADD: "InformationObject" type="TextType" minOccurs="0"/> TO: 2. CHANGE: element name="InformationObjectType" type="IdentifierType" TO: type="InformationObjectTypeType" _OperationsRecordSpecTemplateType_ CHANGE: element name="InformationObjectType" type="IdentifierType" TO: type="InformationObjectTypeType"
racheliurui commented 4 years ago

WIP -- removed myself from "assignee"

gerardmoloneyetpartners commented 4 years ago

Charlie is meeting with other experts to assist in designing the fix for this issue.

CharlieG021163 commented 4 years ago

@gerardmoloneyetpartners @terryrankine Need to discuss this issues proposed solution, I committed the solution to Common.xsd but did not run all ISA-95 1st order types in the choice.

CharlieG021163 commented 4 years ago

In Common.xsd, the previously added was deleted since it did not work as a reference schema for "OperationsRecordEntryTemplateType". It was replaced by ADDing the InformationObject.xsd as the reference.