[CODEMETA] Questions on the list of codemeta tags that we prepared with Roberto

[laurab1]

Hi,
in the list of codemeta tags that swe prepared with Roberto, we found this two fields:

Identifiants externes de type SHA1 SWH, DOI, etc... ; [identifier] ;
...
Depot de code; [codeRepository] ;

codeRepository should be an URL to related resources. Carlo and I wonder whether this URL identifies the site that contains the code identified by the first tag or not necessarily.

[laurab1]

Another question about this field:

Référence interne ; [referencePublication] ;

why "interne"? A published article wouldn't do?

[laurab1]

Finally, we compared the CMM codemeta and the new codemeta of July 1st. In CMM we found the following entries which could be interesting:

"codeSampleType":"full (compile ready) solution",
"image":"is there an appropriate image ?",
"targetProduct": {
"@type": "SoftwareApplication",
"applicationCategory":"System",
"applicationSubCategory":"Memory Management",
"downloadUrl":"is there quella originaria ?",
}

What do you think of adding them to the new one?

[moranegg]

About the first question:

codeRepository should be an URL to related resources. Carlo and I wonder whether this URL identifies the site that contains the code identified by the first tag or not necessarily.

codeRepository is a typed url where we know the field will hold the location of the development of the code.
Here is the description of the field:
Link to the repository where the un-compiled, human readable code and related code is located (SVN, GitHub, CodePlex, institutional GitLab instance, etc.).
identifier can be a url as well, its purpose is to identify the artifact and can be a DOI, SWH-ID, HAL-ID, ASCL-ID.. or other.

second question:

why "interne"? A published article wouldn't do?
The list is taken directly from the work with HAL, référence interne is the property linking between artifacts in the HAL archive, for example, the publication connected or describing the software.
We had to find a way to translate it to CodeMeta.

third question:
The entries you found are taken from SoftwareApplication in schema.org, if you find it useful for the use case, feel free to use them. In my opinion these properties are more adapted to the software executables than the software source code.