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

One ParentOrganization and 3 SubOrganization in same Address? #3014

Open
AngieRamIbiza opened this issue Dec 12, 2021 · 2 comments
Open

One ParentOrganization and 3 SubOrganization in same Address? #3014

AngieRamIbiza opened this issue Dec 12, 2021 · 2 comments
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).

Comments

@AngieRamIbiza
Copy link

I'm having an issue with my Local Bussiness. We offer 3 different services and now all of them will be in different web pages, domain etc. Plus the Parent organization, that makes 4 web pages, and in 2 languages makes 8 of them. How can I arrange the Schema situation? Can I use Parent/Sub as a solution? And what about the languages?

@RichardWallis
Copy link
Contributor

The clue to the way forward maybe in your wording "We offer 3 different services"

I suggest you look into individually describing those Services and link them via Offers to the organisation(s) offering them.

If you do have a hierarchy of organisations to describe, parentOrganization & subOrganization properties are designed for that purpose. Make sure you include an identifying URI (in JSON-LD the @id value) in those descriptions, especially if the organisations have their own web presence.

Language [of display] for a page is more a topic for html issues. However, description of a Service, can include via the availableChannel property a descriptions of ServiceChannel including availableLanguage. Also when describing an Organization, Service or whatever you have the option to provide multiple name & alternateName properties.

@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 Mar 19, 2022
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

2 participants