Skip to content

Proposal - rebrandedTo to describe Organization merging / rebranding into another Organization #4356

@redphoenix2uk

Description

@redphoenix2uk

I am writing a big piece of structured data for a large organization who have acquired many organizations over the years, merging the old organisation names into the current company.

There isn't currently a way to accurately describe this.

I am currently using Organization (Company A) > subOrganization (Company B)
Company B then has a dissolutionDate specified
Company A's sameAs also contains Company B's sameAs

I therefore propose a new schema property called "rebrandedTo".

This would only accept the following types:

  • Organization (and all its subtypes)
  • LocalBusiness (and all its subtypes)

and be used on the following types:

  • Organization (and all its subtypes)
  • LocalBusiness (and all its subtypes)

This new property would be used to describe Organizations or LocalBusinesses which have been acquired by another business or merged into that business.

It would be even better if we could have a property such as "rebrandDate" to say the date when Company B was rebranded as Company A.

I imagine it would look something like this:
{ "@type": "Organization", "name": "Company A", "@id": "https://www.example.com/#organization", "alternateName": ["Company B"], "legalName": "Company A Inc.", "subOrganization": [ { "@type": "Organization", "name": "Company B", "legalName": "Company B, Inc.", "dissolutionDate": "2022-11-03", "rebrandedTo": { "@type": "Organization", "name": "Company A", "@id": "https://www.example.com/#organization", "rebrandDate": "2022-11-03" } }

If there is currently a better way of doing this that I've not found, please can you let me know. Thank you very much

Metadata

Metadata

Assignees

No one assigned

    Labels

    no-issue-activityDiscuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions