How should we handle links between assets (e.g. software dependencies)?

[jeff-zucker]

How should we handle links between assets (e.g. software dependencies)?

First we need to decide what relationships we want to support, then we can get into the details of which predicates and/or SKOS concepts we use to describe the relationships. And I'm starting with software Assets because that's a large part of what we deal with and can serve as a model for other types of Assets.

ADMS/DCAT terms dcat:theme and dcterms:type can be used to categorize software and dcterms:publisher can link software to its creator or vendor. ADMS uses wdrs:describedBy to link an Asset to its documentation. As discussed elsewhere, there are ways to handle links to things like code repositories.

But there are other aspects of software we want to cover. I propose the list below as a first pass at a list of the software relationships. For the moment, please focus on the concepts, not predicates. The permissable values (e.g. Browser/Terminal) would be stored in the SKOS ConceptScheme.

[Software]
  maintainer          [Person]
  contributor         [Person]
  usedBy              [Service]  # e.g :NSS usedBy :CommunityDotNet
  programmingLanguage [Programming language]
  platform            [Browser|Terminal|Agnostic]
  framework           [React|Vue|None|...]
  dependsOn           [Software]
  implements          [Protocol|Shape|ConceptScheme]
  handlesType         [a rdfs:Class]