Pull messages as transition triggers into edges of "contract negotiation state machine"

International-Data-Spaces-Association / ids-specification

The Dataspace Protocol is a set of specifications designed to facilitate interoperable data sharing between entities governed by usage control and based on Web technologies. These specifications define the schemas and protocols required for entities to publish data, negotiate Agreements, and access data in a data space

https://docs.internationaldataspaces.org/dataspace-protocol/

Apache License 2.0

33 stars 14 forks source link

Pull messages as transition triggers into edges of "contract negotiation state machine" #143

Closed SebastianOpriel closed 1 year ago

SebastianOpriel commented 1 year ago

Enhances and obeys comments of https://github.com/International-Data-Spaces-Association/ids-specification/pull/137

1st Iteration (a. without termination edges b. abbreviated msg + triggers in edges) 2nd Iteration (a. with termination edges b. msg + triggers in edges)

SebastianOpriel commented 1 year ago

ToDo

[ ] Adjustment of transfer state machine (blocked -> first discuss PR)

SebastianOpriel commented 1 year ago

I agree with you. What about 1b without all edges to TERMINATED?

jimmarino commented 1 year ago

I agree with you. What about 1b without all edges to TERMINATED?

Does 1.b. have the message types in it? It looks like it doesn't. It should have the message types.

SebastianOpriel commented 1 year ago

You are right. Here is the result: I think we have 2 valid options

Go with @juliapampus's approach, having all edges and all states in the diagram. Only thing is that messages in nodes might not comply with UML notation
Go with messages on edges + all edges to TERMINATED - with the downside that it is complicated to read, but correct

I would not suggest to go with the approach, now checked in, as it is IMO easier to read, but needs also the message in TERMINATED state, since the other edges were left out.