Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Examples of quality for services #252

Closed
riccardoAlbertoni opened this issue Jun 8, 2018 · 4 comments
Closed

Examples of quality for services #252

riccardoAlbertoni opened this issue Jun 8, 2018 · 4 comments
Assignees
Labels
dcat:Catalog dcat:DataService dcat dcat-primer Issues useful for dcat-primer due for closing Issue that is going to be closed if there are no objection within 6 days quality service
Milestone

Comments

@riccardoAlbertoni
Copy link
Contributor

We might want to include in the DCAT document examples of quality documentation related to services/catalogues. In particular, as suggested by Peter and other during a DCAT call (see https://www.w3.org/2018/06/07-dxwgdcat-minutes)

Given we are thinking of dataservices - we maybe need to think about these dimensions?
Platform stability (Average Availability; Mean time to failure; Mean time to repair; Mean time between failure; etc) Platform response (Response time; Throughput; Capacity; ) Scalability (static - add more kit; dynamic; predictive;) Latency Help Desk availability (none; 9-5; 24/7)

@riccardoAlbertoni
Copy link
Contributor Author

This issue has lost some of its importance considered the stage of DCAT development and that we have decided to reduce the number of examples. I think we might consider to close it...
@pwin: what do you think?

Shall we label this issue as "wontfix", or do we want to mark it with a new label, for example, "FoodForAPrimer"?

@agbeltran
Copy link
Member

I think it is good to tag it with dcat-primer and I've just created the label

@agbeltran agbeltran added the dcat-primer Issues useful for dcat-primer label Mar 5, 2019
@davebrowning davebrowning added the future-work issue deferred to the next standardization round label Sep 25, 2019
@andrea-perego andrea-perego added this to To do in DCAT revision via automation Sep 26, 2019
@andrea-perego andrea-perego added this to To do in DCAT Sprint: Data services via automation Nov 12, 2020
@andrea-perego andrea-perego removed this from To do in DCAT revision Nov 12, 2020
@andrea-perego
Copy link
Contributor

As no work is planned for a DCAT primer, I propose we close this issue.

@andrea-perego andrea-perego added the due for closing Issue that is going to be closed if there are no objection within 6 days label Mar 13, 2021
@andrea-perego
Copy link
Contributor

Noting no objections, I'm closing this issue.

DCAT Sprint: Data services automation moved this from To do to Done Mar 20, 2021
@andrea-perego andrea-perego removed the future-work issue deferred to the next standardization round label Mar 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dcat:Catalog dcat:DataService dcat dcat-primer Issues useful for dcat-primer due for closing Issue that is going to be closed if there are no objection within 6 days quality service
Projects
Development

No branches or pull requests

6 participants