Schema.org is a standardized method for explaining the data scheme for a variety of data types. Discover what information is available at schema.org and how to find a scheme for your data.
- There are two halves to the structured data problem. The first issue is that we need to clearly define the structure of our data. Once we know that, and we have that all standardized, then we can discuss how we will convey that standard via markup and programming. So let's address that first problem. How do we clearly define the structure of our data? Fortunately, there is one centralized solution for this, regardless of how we mark up the structure and that's through a website called schema.org. This is that particular website. You're welcome to open this up in your own browser and take a look at the website. Chances are, you might wind up going to the schemas link up here on the top. This will give you the option of browsing through a variety of types of works that are here on this website. So you can take a look at any of those, or of course you can go up to your search and you can type in a search parameter and find a thing in particular. Let's just jump right here to the recipe, which is a commonly used type of creative work. So this is a series of properties here that are specific to the recipe. They're right here at the top. And so you'll see here that a recipe has properties here that you would expect, like how long does it take to cook or how do you cook it or what kind of recipe is it and what are its ingredients? These are properties that really are specific to a recipe. While it's possible you won't have all of those properties in your recipe, they're available for your use. Now you might be thinking about other things that pertain to a recipe as well, that are not listed here at the very top of the schema. Things like, what is the name of this recipe or who created this recipe? That type of thing. Well, a recipe doesn't stand alone in the world. It inherits properties from other less defined properties, and that structure is described here in the breadcrumb. So as you see here, a recipe is derived from a work called how to, How to is derived from a creative work. And that is derived from a thing. Even though we're talking about a recipe, all of the properties that are associated with things, creative works, and how tos are available to us to use a recipe. So let's take a quick peek at the creative work to see what's listed there. So this is a listing of all of the properties that are here for a Creative Work and not all of these are going to apply to our recipe. For example, most recipes don't have an abstract. That is something that may apply to other types of creative works, but it probably doesn't apply to a recipe. It is, however, available to you if you wanted to have an abstract about your recipe. If you scroll down a little bit further though, you'll notice that author is one of the properties associated with a creative work and recipes certainly have authors. So that might be something that you'd want to leverage. Likewise, an award is something associated with a creative work that might also apply to a recipe. So these are things that you might want to have available to you if you were listing a recipe. So while you're choosing a schema to describe whatever it is you want to describe in the same type of way, you have the option of building on that generic item, like a creative work, and then layering on more properties specific to that type of item. All of these properties are available to you for describing that item. schema.org is a centralized method for describing just about anything. However, there are several ways to implement this scheme and we'll discuss that in the next video.
- Describing elements with schemas
- Embedding schemas in schemas
- Using the Structured Data Markup Helper
- Making up a document with microdata
- Making up a document with JSON-LD
- Testing your structured markup