ResourceLocationType Child Relationship

[gerardmoloneyetpartners]

Currently, the B2MML-Common.xsd defines the ResourceLocationType as per below.

As there are certain objects (OperationalLocation, Equipment, PhysicalAsset) with the 'is made up of' relationship, I would like to see this updated to support this part of the ISA95 data models and suggest the update as a new line inserted at line 1642 as per below.
I believe this would then support the ability to have these objects nested and reported appropriately.

[gerardmoloneyetpartners]

Hi @Dennis-Brandl, you were a bit quick for me to get this bug documented before the recent update.
Can we please get this also put into the V7.0.1 also.
I'd really like to have this ready for our next project implementation so that the following will allow nested locations
OpMaterialActualType for the StorageLocation
OpEquipmentActualType for the OperationalLocation
OpPhysicalAssetActualType for the PhysicalLocation

[Dennis-Brandl]

I will put this in on Friday and create the pull request. The change looks correct to me, and consistent with the ISA/IEC/ISO specification, so we can merge into V7.01 right away. Dennis Dennis Brandl 208 Townsend Ct, Suite 200 Cary, NC 27518-8319, USA +1-919-656-2205 (Mobile) +1-832-201-0554 (Fax) <http://www.brlconsulting.com/> www.brlconsulting.com ***@***.***> ***@***.*** From: gerardmoloneyetpartners ***@***.***> Sent: Tuesday, March 7, 2023 9:59 PM To: MESAInternational/B2MML-BatchML ***@***.***> Cc: Dennis Brandl ***@***.***>; Mention ***@***.***> Subject: Re: [MESAInternational/B2MML-BatchML] ResourceLocationType Child Relationship (Issue #82) Hi @Dennis-Brandl <https://github.com/Dennis-Brandl> , you were a bit quick for me to get this bug documented before the recent update. Can we please get this also put into the V7.0.1 also. I'd really like to have this ready for our next project implementation so that the following will allow nested locations OpMaterialActualType for the StorageLocation OpEquipmentActualType for the OperationalLocation OpPhysicalAssetActualType for the PhysicalLocation — Reply to this email directly, view it on GitHub <#82 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEBIXAXGLVHRBXE6MS2BGFTW27YXHANCNFSM6AAAAAAVSH63FA> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AEBIXAVTDZQMFBPC76753DLW27YXHA5CNFSM6AAAAAAVSH63FCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSW7IYY4.gif> Message ID: ***@***.*** ***@***.***> >