OliverFendt

@jlovejoy The import is done roughly as follows The licenseIds are imported from https://spdx.org/licenses/licenses.json and the texts of the licenses are imported via the "detailsUrl" given in the licenses.json file...

I had a look at the new license request and have several comments. Given the text: > Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, # 2003,...

@jlovejoy to be honest I do not understand you comment about the copyright statements. If you look for example at the software package bash 5.1.16 there is: > Copyright (C)...

I had a look at the license text and have some small remarks 1. The line > Copyright 1989-1992, Bitstream Inc., Cambridge, MA. shall be exlcluded from the license text,...

I am in favor to add the license to the list

@LeChasseur good point. If there is no permission to modify the work and to distribute the work in modified form, this license is not conformant to the open source definition...

Hi regarding the "Component Analysis Service" in the Wednesday afternoon meeting there was the proposal to rename this to "Forensic Code Analysis Service". I personnally think that the proposed name...

A first step to realize this can be introducing a new class named ProductPolicy with associations to ProductInformation, Deliverable, License and probably to DigitalArtifact. The class shall have the members...

a solution to cope with this can be an associated class between License and Constraint named Assessment with member attribute status and possible values completed, inEvaluated, notEvaluated

Thank @mxmehl for pointing this out, I will check how to fix it and fix it