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

How to model recursion with Services #3331

Open
sstiene opened this issue May 25, 2023 · 4 comments
Open

How to model recursion with Services #3331

sstiene opened this issue May 25, 2023 · 4 comments
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).

Comments

@sstiene
Copy link

sstiene commented May 25, 2023

Dear schema.org Team,
I would like to model a complex service system, where we have ~20 organisations that cooperate and offer services. The services can be used in combination and may build upon each other.

So the question is how to best model recursion in services:

Service A provided by organization X consists of Service B from organization X and Service C from organization Y.

Is this possible with the standard Service description (https://schema.org/Service) or do we have to derive an own Service class.

Kind Regards
Stefan

@danbri
Copy link
Contributor

danbri commented May 25, 2023 via email

@sstiene
Copy link
Author

sstiene commented May 25, 2023

The project is a european project where we build a network of AI and robotics test and experimentation facilities and the facilities provide services like testing, certification, ... for companies. The facilities cooperate and build synergistic services, so that a smaller service in Germany could be used as part of a bigger service in Italy for example. And at the moment I give JSON-LD a try to model this network (I am a beginner regarding JSON-LD).

I think the provider will not work.

It is more a new property of a service "consists_of" with an itemlist "Service" so that we are able to model that a certain Service is an umbrella service that consists of other subservices.
Best Regards
Stefan

@github-actions
Copy link

This issue is being nudged due to inactivity.

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Aug 24, 2023
@MatthiasWiesmann
Copy link
Contributor

So the proposal would be a subproject in https://schema.org/Project ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
Projects
None yet
Development

No branches or pull requests

3 participants