ETPartners / b2mmlv7beta

b2mmlv7beta for review
2 stars 3 forks source link

Change "OperationsEventRecord" type = "OperationsRecordEntryTemplateType in OperationsEvent.xsd to type = "OperationsRecordTemplateType" in complexType name = OperationsEventType #67

Open CharlieG021163 opened 5 years ago

CharlieG021163 commented 5 years ago

To align with Updated 95002, Operations Event Model Solution:
<xsd:complexType name = "OperationsEventType" name = "OperationsEventRecord"
CHANGE: type = "OperationsRecordEntryTemplateType" TO: "OperationsRecordTemplateType"

Supporting Document ISA-950002 JWG5 CDV01 version (2019 12) Clause 5.11.10 Operations event record, Table 140 – Operations event record relationship roles

Impacted types B2MML-OperationsEvent.xsd: OperationsEventRecordType

racheliurui commented 5 years ago
<xsd:complexType name="OperationsRecordEntryTemplateType">
        <xsd:sequence>
            <xsd:element name="ID"                      type="IdentifierType"/>
            <xsd:element name="Description"             type="DescriptionType"  minOccurs="0" maxOccurs="unbounded"/>
             <xsd:element name="InformationObject"      type="TextType"         minOccurs="0"/>
             <xsd:element name="InformationObjectID"    type="IdentifierType"   minOccurs="0"/>
             <xsd:element name="EffectiveTimestamp"     type="DateTimeType"     minOccurs="0"/>
             <xsd:element name="RecordTimestamp"        type="DateTimeType"     minOccurs="0"/>
             <xsd:element name="InformationObjectType"  type="IdentifierType"   minOccurs="0"/>
          <xsd:group ref="Extended:OperationsRecordEntryTemplate" minOccurs="0" maxOccurs="1"/>
        </xsd:sequence>
    </xsd:complexType>
    <!--     -->    
    <xsd:complexType name="OperationsRecordTemplateType">
        <xsd:sequence>
            <xsd:element name="ID"                      type="IdentifierType"/>
            <xsd:element name="Description"             type="DescriptionType"  minOccurs="0" maxOccurs="unbounded"/>
             <xsd:element name="Action"                 type="IdentifierType"   minOccurs="0" maxOccurs="unbounded"/>
             <xsd:element name="EffectiveTimestamp"     type="DateTimeType"     minOccurs="0"/>
             <xsd:element name="RecordTimestamp"        type="DateTimeType"     minOccurs="0"/>
           <xsd:group ref="Extended:OperationsRecordTemplate" minOccurs="0" maxOccurs="1"/>
        </xsd:sequence>
    </xsd:complexType>

The operations record template bundles operations record entry template objects by the type of action specifying the attribute, action, with defined values of created, changed, deleted and observed.

From above description, need to understand how they are bundled.

CharlieG021163 commented 5 years ago

The schema excerpt above is from master, not the current version from draft branch which has the correct relationship elements to bundle entries in records.

****
racheliurui commented 5 years ago

Agreed

Dennis-Brandl commented 4 years ago

I agree with the change.