Intoduce usage agreement (issue #505) #567
Conversation
Raphael-Gazzotti
added
request
| "shortName" | ||
| ], | ||
| "properties": { | ||
| "contactInformation": { |
There was a problem hiding this comment.
@apdavison would you agree that this should be rather renamed to "mainContact" and offer a single string (format: email?) entry? (ContactInformation is currently handled privately only but that info should be public similar to supportChannel)
Co-authored-by: Lyuba Zehl <lyuba.zehl@ebrains.eu>
| "_linkedTypes": [ | ||
| "core:Copyright", | ||
| "core:License", | ||
| "core:UsageAgreement" | ||
| ] | ||
| }, |
There was a problem hiding this comment.
copyright should ideally not be linked but embedded, maybe there should be another schema defined that is linked here (and links to license/usage agreement but embeds copyright) or copyright has to remain a separate property
The big issue (with both) is that the properties have to become optional because a copyright could be the only necessary one, but may not be the important one for other cases.
@apdavison, @olinux and @lzehl: Any suggestions? We should probably discuss this in one of the developer meetings.
3 participants
Address issue #505
Correct the errors of #559
legalPerson category will need to be updated in a future PR.
the controlledTerms ModificationRights will need to be added first (openMetadataInitiative/openMINDS_controlledTerms#512).