eCatalogue meeting

Date: 20/01/2022
Participants: Cecile Guasch, Veit Jahns, Natalie Muric
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre

Discuss issue #284

The type of change can be send from the provider to the receiver

We should implement this in the ontology

We can mention that there was a type of change and give the replica of the change

We need a change type code (from Veit)

Should we provide a text field where to mention what was changed

We need a description of what the catalogue action items are.

ecmGZMKGrwXwKtpTvAkOZ0G2pQ5d8ScGd71gYa4IMfbOh5zj8QkP++UgWulT4u4UPYsq0wn4KhsW4DyzDbWmYRYXuTPPTSlYaiSwngqiAw1VOWmlymkgkEolEIpH+PzlDlhMxXyifRFdS0Wv6H09bL690Ek1QAAAAAElFTkSuQmCC

Action Code should be renamed into Change Type Code.

We can not directly interpret their wording being syntactically correct.

The action code is intended to know what and how has been changed.

We want to give the possibility that if the system wants to do the update one by one to do so.

Is it just for informing of what was changed? YES.

So it’s NOT about what should be changed.

So these are not actions, they are information.

ID of the Catalogue and of the Item stays the same. We might assume that the URI stays the same.

Discuss GH 315

We provide epo:hasRegisteredAddress instead of hasLegalLocation.

Closing the ticket.

Discuss GH 316

The model provides a relationship between ContactPoint and Address:

x9UT1Z1hyvXLgAAAABJRU5ErkJggg==

Closing the ticket.