search

CLARIAH / clariah-plus

This is the project planning repository for the CLARIAH-PLUS project. It groups all technical documents and discussions pertaining to CLARIAH-PLUS in a central place and should facilitate findability, transparency and project planning, for the project as a whole.
9 stars 6 forks source link

Document 'software metadata requirements' #40

Closed proycon closed 1 year ago

proycon commented 2 years ago

As part of the software & infrastructure requirements, we already formulated a clause stating the requirement to deliver software metadata. The actual metadata requirements, however, may need to be worked out in a separate document (because of length), and we can then refer to that from the software & infrastructure requirements.

This would be a main deliverable of this tool discovery track.

ddeboer commented 2 years ago

Practically, a codemeta.json must be supplied. The requirements should explain which CodeMeta properties are required. Depends on #32.

proycon commented 2 years ago

Assessment procedures for extra vocabulary things like TLR and SLR (#32) should be explicitly part of these requirements.

ddeboer commented 2 years ago

For inspiration, see also DARIAH assessment criteria, as suggested by @femmynine.

proycon commented 2 years ago

A lot of initial work on this has been done in https://github.com/CLARIAH/clariah-plus/pull/95 , what remains is mostly the write up of the extra vocabulary we prescribe, when those decisions have been taken.

proycon commented 1 year ago

The document on software metadata requirements is fairly complete now, though small things may still change if needed. Closing this issue.

proycon commented 1 year ago

It was decided in the Tech Committee today that we will finalize the software metadata requirements (and by extension the vocabulary discussion of #32) the upcoming techday (2022-10-27).