Proposed use of Software Description Ontology (in relation to, or in replacement of PROV-O ?)

Software Description Ontology : https://knowledgecaptureanddiscovery.github.io/SoftwareDescriptionOntology/release/1.8.0/index-en.html

The proposed used of PROV-O was to capture the following : "A request entity has been derived from the analysis of the english linguistic variant of the legislation (optionally by using a software agent in a certain version)"

The idea being that, even if Requests are linked (only to) temporal version of a legislation (and not to a linguistic variant), it would still be possible to indicate which was the linguistic variant that was analyzed to find/extract/describe the Request.

The emphasis of the proposal was on the derivation link between the linguistic variant and the request, not on the description of the software agent itself.

Consequently, I think the use of the suggested software ontology is complementary to the suggested use of PROV-O, if there is indeed a desire to describe in more detail the software itself that was used (?). I note also that this ontology is compatible with PROV, with one of its class being a subclassOf PROV activity

One interesting information on the software agent is its version, so that it is possible to track which version of the software produces which request, and, if a bug is found in the software, we know which request should be regenerated. Software ontology does provide classes and properties for this (Software Version + hasVersionId).

For further analysis,what would be the use-cases for using this software description ontology ?