search

International-Data-Spaces-Association / InformationModel

The Information Model of the International Data Spaces implements the IDS reference architecture as an extensible, machine readable and technology independent data model.
Apache License 2.0
64 stars 38 forks source link

Remove non-used Classes and Properties #293

Closed sebbader closed 4 years ago

sebbader commented 4 years ago

Several classes, properties, taxonomies and instances in the current version have never been used, and no realistic use case is currently presented. I suggest to list such entities, and delete them from the model. This shall reduce the overall complexity of the model and help the users to find what is really relevant.

I have prepared suggestions in the branch feature/simplifications already.

sebbader commented 4 years ago

https://github.com/International-Data-Spaces-Association/InformationModel/tree/feature/simplifications

sebbader commented 4 years ago

Furthermore, I want to remove Operations from the model. It is not in the core focus of the IDS, and only provides minimal added value while at the same time presenting a huge set of classes and relations.

sebbader commented 4 years ago

And I want to get your opinion on our Licenses. This enumeration is, and always will be, incomplete. I strongly suggest using a third party vocabulary instead of trying our own model.

jlangkau commented 4 years ago

Furthermore, I want to remove Operations from the model. It is not in the core focus of the IDS, and only provides minimal added value while at the same time presenting a huge set of classes and relations.

A very good move!

jlangkau commented 4 years ago

Several classes, properties, taxonomies and instances in the current version have been never used, and no realistic use case is currently presented. I suggest to list such entities, and delete them from the model. This shall reduce the overall complexity of the model and help the users to find what is really relevant.

I have prepared suggestions in the branch feature/simplifications already.

This is a very good idea - but: are you shure, that know one (out in the field) is using some of those you want to eleminate?

HaydarAk commented 4 years ago

I agree with Sebastian. 👍 But removing Operations inevitably leads to a re-design of (interactive) endpoints, since interactive endpoints are mainly based of the operations as far as I knmow.

This is a very good idea - but: are you shure, that know one (out in the field) is using some of those you want to eleminate

Good question

And I want to get your opinion on our Licenses. This enumeration is, and always will be, incomplete. I strongly suggest using a third party vocabulary instead of trying our own model.

👍

I'd like to add the Activities to the list of things that we should remove.

clange commented 4 years ago

And I want to get your opinion on our Licenses. This enumeration is, and always will be, incomplete. I strongly suggest using a third party vocabulary instead of trying our own model.

I fully agree – could someone try to find one? I'm not so sure that there is such a thing. However, being incomplete should be OK, because the IDS infomodel already has a way of referring to "non-standard" licenses.

HaydarAk commented 4 years ago

model/contract/PricingModel.ttl model/contract/Payment.ttl

In my understanding, these classes are outdated and are now part of the usage policy. Remove them, @sebbader ? 🗑️

sebbader commented 4 years ago

90% sure that you are right, @HaydarAk. I think those were left overs from some business-related discussions, which we have never finished in any appropriate manner... But yes, the input from the IDSA Legal WG puts these ideas into the contracts.