Adjust form behavior for DataServices

[jakubklimek]

Currently, the JSON-LD output and form behavior is not correct in the case of DataServices. Based on https://github.com/SEMICeu/DCAT-AP/issues/100 and https://github.com/w3c/dxwg/issues/1126, the usage in Czechia will be the following:

• When a user wants to create a catalog record for a Data service, it will ALWAYS be a part of Dataset registration, i.e. no stand-alone Data services.
• For each Data service, there will also be a Distribution.
• There will be no dcat:downloadURL, compression format, package format, file type nor media type for that distribution
• Distribution's dcat:accessURL will be equivalent to the Data service's dcat:endpointURL
• Distribution's dcterms:title will be equivalent to the Data service's dcterms:title, which is, however, mandatory
• The distribution will point to the data service using dcat:accessService
• Data service will point to the registered dataset using dcat:servesDataset
• When Data service is chosen, the rest of the entered "Downloadable file" properties will not be used

DCAT-AP Forms should implement these rules.

If something is not clear, ask.

[jakubklimek]

DCAT2, Datové sady, Datové služby a NKOD

[jakubklimek]

Pracovat na issues k DCAT-AP-Forms ohledně DCAT2