feat: contract termination

[juliapampus]

What this PR changes/adds

Explains how to use DSP for contract termination.

Why it does that

Address community requests, such as #17.

Further notes

This PR raises requirements for the specification document:

• Add leftOperand for Agreement

Related discussion in Tractus-X project: eclipse-tractusx/tractusx-edc#1392 (comment)

Linked Issue(s)

--

Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

[arnoweiss]

thanks for the writeup, a couple of notes:

1. I'd suggest to stick closer to the problem. If the document is called "Contract Termination", considerations on other things associated with contracts/agreements (amendments etc) should be left out.
2. Let's consider how to link this work to the other best practices. When boiling it down, this document suggests a Policy Profile for contract termination, doesn't it?

[arnoweiss]

Same criticism as before. I don't think there's value in being this specific - especially in the later stages.

[juliapampus]

I've shortened this section. As this is a best practices document, I would be in favour of having some additional explaining information - especially as we know the most frequent discussion points. However, I agree that we should not make unnecessary assumptions or statements.

Is the Catena-X example okay?

[juliapampus]

thanks for the writeup, a couple of notes:

1. I'd suggest to stick closer to the problem. If the document is called "Contract Termination", considerations on other things associated with contracts/agreements (amendments etc) should be left out.
2. Let's consider how to link this work to the other best practices. When boiling it down, this document suggests a Policy Profile for contract termination, doesn't it?

Thanks for your comments! I have moved the text to the profile section.

[arnoweiss]

One example could be clarified a bit. Overall, this is a lean, viable best practice!