My principal client, a healthcare organization, is working on leveraging Schema.org to develop a reusable, understandable, and API-first website. As the team works towards rearchitecting the website, we face the ongoing challenge of determining how our existing content model and relationships can be aligned with and migrated to a Schema.org-based content model.
Schema.org is a vocabulary that provides a standardized way of describing things on the web. It is used by search engines and other applications to understand the content of web pages.
Schema.org defines a vocabulary with 803 Types and 1465 Properties, which is a lot to take in. It can be easy to miss how your existing content types can be aligned with Schema.org. However, the Schema.org specification has been carefully thought out and developed with input from various organizations. For example, the Role type allows organizations to add additional specificity to any relationship. This is often used to define the role of members and employees within an Organization.
Despite my team's efforts, we occasionally need assistance aligning with Schema.org. This challenge led me to realize that instead of focusing on my organization's specific use case, I should look at how Schema.org can define an organization's content and information model. As a result, I created the Schema.org Blueprints Starter Kit: Organization module.
This starter kit leverages inverseOf relationships for member, employee, subOrganization, and department to arrange an organization's hierarchy and define individual roles within an organization using the Read More