Closed tomkxy closed 2 years ago
Good point. Should be easy to achieve and definitely a benefit.
Just saw that representation is a subclass of dcat:distribution. According to the DCAT spec title and description are formally already part of the ids:representation but according to my knowledge, they are not part of the generated Java classes.
I think the solution would be as easy as
ids:Representation rdfs:subClassOf ids:Described
Added the suggested changes (add title and description) to the ids:Representation
class in #483.
The IDS Information Model splits the dcat:Distribution into the ids:Representation and ids:Artifact. Therefore, it is not necessary to add title / description information to an artifact.
As part of the next major version, we might also consider to align with dcat --> merge ids:Artifact & Representation. But this is still open to discussion. Also related: #481
Dcat supports a title and description property on distribution level. Since I need to represent (map) from DCAT to IDS I was looking for those props on representation or artifact level.
It seems that IDS does not foresee a title and description field on artifacts and representation? If that is right, I would suggest to consider this, since mapping from DCAT seems to be common requirement, at least in MDP it is.