The following github issues were discussed, the resulting discussions and solutions are listed below:

#463 To link GoodsItem and Item
GoodsItem and Item could be linked via their Ids epo-ful:GoodsItem epo-ful:hasTraceID and epo-cat:Item has epo:hasSerialID.

Definition for epo-ful:hasTraceID:
The identifier used for tracking the goods item

Additional information:
An example is the EPC number used in RFID.

WG approval 21/09/2023

The origin of the ticket was that Veit had investigated information about the GoodsItem and was wandering why there is no link between the Item and GoodsItem.

Peter questioned whether you can know the packaging in the Catalogue because it does not exist at the time of the catalogue

It is decided to have epo-cat:Item epo-cat:foreseesPackage epo-ful:Package.
As a consequence the epo-ful:Package epo-ful:containsGoodsItem epo-ful:GoodsItem needs to be less restrictive and the cardinality is changed to 0..* rather than 1..* as the eCatalogue will not use the GoodsItem.
The Quantity is on the epo-fulAbstractContainer so it can also be used by the Catalogue.
It was decided that it was more appropriate to put the association of the Package to the Catalogue Line rather than the Item. The model created:

#426 Validity periods for Catalogues and Catalogue Items
Validity period for the Catalogue Item exists, however it is missing for the Catalogue. It existed in v3.1.0 but somehow it has been lost, it was reintegrated in the meeting.
The definition in v4.0.0 for hasValidityPeriod (it is used for different domains and ranges) is an improvement on that used in v3.1.0, therefore the definition already in v4.0.0 is kept:

epo:hasValidityPeriod: the relation indicating until when a given instance of a concept is applicable. WG approval 30/05/2023

The epo-cat:hasCatalogueLineValidity has no definition the following is agreed:
The relation indicating until when a Catalogue Line instance is applicable.

WG approval: 21/09/2023

#453 This ticket provides the basic model for the Catalogue Response. Veit gave a quick overview and the Package was created in the conceptual model.

The outcome of the discussion was the following model:

This will be reviewed and rediscussed at a later date.

The model created in the last meeting (12/09/2023) was discussed.

There seems to be no link between epo-ful:DespatchLine and the epo-cat:Item. It is shown that it exists as the epo-ful:DespatchLine is a specialisation of epo-cat:Line

The following diagram shows how a document can be associated to the DespatchLine.

It was agreed that Peter would provide a list of the business terms used in the eFulfilment use cases so that the mappings to the ontology could be inserted and then checked together at a later date.
Veit will provide a similar file for eCatalogue for information as the mappings have already been done.