The hasNext property structure and implementation should be modified

1. While defined in the OWL code, this property was never instantiated in our examples.
2. The property currently serves a dual purpose, connecting both different Requests and different Actions within a Request. When Request1 connects to Request2 via hasNext, while simultaneously Action1Request1 connects to Action2Request1, and Action1Request2 to Action2Request2, we encounter a complex layering of sequential relationships. This moves our model towards business process mapping territory, introducing additional complexity that needs to be addressed.

Possibility is to subcategorise the hasNext property in "hasNextrequest" and "hasNextaction"?

Community input needed.