Open questions about metadata schemas

[vuillaut]

Hi.
There are some things I do not understand and would like to clarify.
Maybe this can be helpful to others as well.
Tagging @fdiblen and @dgarijo

• why is it qualityDimension in https://github.com/EVERSE-ResearchSoftware/schemas/tree/main/quality_indicators/dev and SoftwareQualityDimension in https://github.com/EVERSE-ResearchSoftware/schemas/blob/main/software/dev/context.jsonld ? Are we not referring to the same notion and same dimensions ?

• what's the difference between SoftwareQualityDimension and hasQualityDimension ?

• license is defined as "schema:license" - this should be URL - why do we have { "@id": "https://spdx.org/licenses/Apache-2.0.html", "@type": "@id"} in the example?

[dgarijo]

Thanks @vuillaut for asking these questions.
It seems like first and second point overlap. Here is the answer:

• qualityDimension is the property that links an indicator to the corresponding SoftwareQualityDimension.
• hasQualityDimension is the property linking a tool to the corresponding quality dimension. I think that maybe we should rename it "affectsQualityDimension" because a tool does not "have" a quality dimension, it "improves" it. What do you think? Both properties in both schemas refer to SoftwareQualityDimensions.
• SoftwareQualityDimension is the main concept to refer to a dimension. For example, https://w3id.org/everse/i/dimensions/functional_suitability is a SoftwareQualityDimension. Basically, it would be the equivalent to "Thomas" is a "Person"

For your second point, according to https://schema.org/license the value expected is a CreativeWork or a URL. The example uses a CreativeWork. But a URL is also valid. If you think it will make things easier, we can make it just URL, it will probably ease up things.

Based on this discussion, and if you agree, the following changes will be done:

• rename hasQualityDimension to affectsQualityDimension
• make schema:license range to URL only

[vuillaut]

Thank you Daniel for your answer!

1. Concerning affectsQualityDimension I think I disagree as some tools only measure software quality (is it really affecting in this case?), even though I agree hasQualityDimension might not be the best either.
   Since a. qualityDimension and hasQualityDimension refer both to SoftwareQualityDimension and b. hasQualityDimension is not so good and loosely defined, I'd probably use qualityDimension here as well. But maybe there is a reason for not using the same term?

2. No need to change it, I understand now and updating the readme would be enough. I'll take care of this.