refactor Activity.json

[zopalmer14]

Summary

Should resolve: #81

Documentation: Activity

Changes:

• remove the option for null values for label and add label to the required array

For Discussion

Does the above change make sense? If so, should it be extended across the other DCAT-US 3.0 classes? Is the change generalizable or a class-by-class determination?

Copied from issue:

I think this issue is just one example of a broader problem that I see with many of the classes. That being, many of them have no required/mandatory properties. As such, although I don't know why they would, a user/catalog owner could create instances of some of the DCAT-US 3.0 classes that are effectively "empty" and that provide no information to the viewer, but which would hypothetically pass validation.

[ParthVenkat]

note for later the " I don't know why they would" argument does not hold a ton of water to me. I truly believe CDOs and their staff will appreciate less opportunities for error unless there is a need for flexibility.

[zopalmer14]

Activity Usage in Schema

• DataService.wasUsedBy - may be used to specify a testing Activity over a Data Service, against a given Standard, producing as output a conformance degree
• Dataset.wasGeneratedBy - An activity that generated, or provides the business context for, the creation of the dataset

[zopalmer14]

Also, I should note that this needs to be run through Prettier before being merged