Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Licenses exclusive or license puts out of character limitations on data package #214
The data package descriptor file allows (even if it isn't explicitly named in the specification) any additional properties except in one case:
This means a data package can have additional properties EXCEPT
This is obviously very hard to enforce in a schema where you cannot really define what you don't want, but you can get around it with code, but that's not as reusable and transferable as a schema.
I think this exclusive or for
Of the two I would vote for
It is possible to define licenses on a resource level which is way more practical because then it is clear to what piece of work the license applies. This is actually not the case now because the resource level only supports
That way we could have only a single license for the data package itself which can be inherited by resources that do not define a license) but could overwrite the data package license on the resource level if applicable.
So basically I propose we drop