Collecting/Documenting Use-Cases and Requirements

We've done a lot of good work within the DPVCG in the past 4 years, with 
the DPV (and extensions) providing an extensive list of concepts. 
Unfortunately, we did not undertake an effort from the start to 
documenting how we have been discussing these and what were the 
use-cases and requirements that we derived them from.

To address this, and to ensure that going ahead we document this 
information (use-cases and requirements), we discussed in earlier 
meetings on how to best address this without creating a lot of work and 
(thanks to Jan) have some consensus on the structure of use-cases and 
examples to be provided.

My plan is to provide a web page, similar to the one in place for SHACL 
( that simply lists the use-cases and 
requirements. An example of this is below:

github issue:

I have gone further and stated that this information also be encoded in 
RDF form so that it can be linked alongside relevant concept e.g. 
dpv:Purpose showing what use-case or requirements are relevant for it. 
This would be completely automated, with relatively low amount of effort 
to develop it. This is expected to work alongside examples, i.e. 
creating and providing examples and linking them to relevant concepts in 
a similar manner (another mail coming soon on this).

Your feedback/suggestions on this are welcome.
Harshvardhan J. Pandit, Ph.D
Research Fellow
ADAPT Centre, Trinity College Dublin

Received on Friday, 10 June 2022 16:40:39 UTC