Extend result reasons on actions

[bmeesters]

Type of request

• [x] I'd like to add something to the OTM 5 spec
• [ ] I'd like to change something in the OTM 5 spec

Is your feature request related to a problem? The current actions contain a result that has a status and a reason. This result can be used to indicate how the action was completed (succeeded, failed, partially succeeded) and if something went wrong why it went wrong. The current possible reasons are damage and receiverAbsent. These reasons are not complete enough for most use cases.

Describe the solution you'd like Extend the reason list with:

• incomplete: the list of goods was delivered 'partially successfully', it was not complete to what was originally planned/agreed upon.
• deliveredElsewhere: the goods were delivered, but not upon the agreed upon location. This could mean a different dock, or maybe at the neighbours (depending on the use case).
• locationUnreachable: The driver was not able to reach the location were the goods were to be dropped. E.g. because some gate was closed, road was under maintenance, etc.
• rejected: the receiver rejected the goods (for whatever reason). The remark can be used to specify the exact reason. only to be used if any of the other reasons is not more applicable.

I expect that these reasons are widely applicable for different type of logistic operations and fairly complete, at least looking at it from a higher level (why the location is unreachable does not need to be a status code).

Describe alternatives you've considered Currently we need to fallback to the remark, which is a free text string.

Additional context Add any other context or screenshots about the feature request here.

[bmeesters]

After some discussion I would like to add the option deliverPerInstructions to indicate the difference between something that was physically handed over to the receiving party, or the receiver was absent, but left instructions that could be successfully followed.