Re: Additional Schema Needed for ItemAvailability

As there are often similar questions for adding new entries to enumerations in schema.org, I would like to stress two things:

1. Adding a new class, property, or enumerated value to schema.org does per se not promise any better understanding of your data by mainstream search engines. 

So if the goal is to see any kind of SEO benefit, simply extending schema.org is by and large useless. You would need to lobby for both its adoption by many sites AND for its consumption by major search engines.

2. If the goal is to be able to model your particular information for proprietary applications (think: start-up, mobile app, analytics), then you do not have to wait for schema.org to define a new element in the vocabulary.

Instead, you can simply define it locally, like so:

{
"@context": "https://schema.org",
"@type": "Product",
"description": "0.7 cubic feet countertop microwave. Has six preset cooking categories and convenience features like Add-A-Minute and Child Lock.",
"name": "Kenmore White 17\" Microwave",
"image": "kenmore-microwave-17in.jpg",
"offers": {
"@type": "Offer",
"availability": 
 {
 "@type": "schema:ItemAvailability",
 "rdfs:comment": "Indicates that the menu will be prepared while you are waiting.",
 "rdfs:label": "CookedToOrder"
 },
"price": "55.00",
"priceCurrency": "USD"
}
}

The block 

"availability": 
{
"@type": "schema:ItemAvailability",
"rdfs:comment": "Indicates that the menu will be prepared while you are waiting.",
"rdfs:label": "CookedToOrder"
},


defines a new instance of the proper ItemAvailability class, and the textual definition might be enough for consumers of the data to process it.

You could also define a globally unique ID for that value and link to an external definition, like so

    "availability": 
 {
 "@id": "https://myownschema.com/CookedToOrder",
 "@type": "ItemAvailability",
 "rdfs:comment": "Indicates that the menu will be prepared while you are waiting.",
 "rdfs:label": "CookedToOrder"
 },

and hence link to a globally unique identifier.

This is valid markup (but major consumers will likely not consider this part).

The same holds for site-specific additional classes and properties.

Best wishes
Martin

-----------------------------------
martin hepp https://www.heppnetz.de
mfhepp@gmail.com          





> On 25. Nov 2024, at 15:17, Mr. PC <dave@thinkmrpc.com> wrote:
> 
> Hello,
>  I am doing some work on a website for a manufacturer..
>  Some of the items that exist on the site for purchasing are items that get manufactured once an order is placed.   So…. it would be accurate to have a schema for item availability known as “Built to Order”.  The item has not been assembled yet, so “in stock”, “backorder”, “preorder” and “out of stock” are not accurate.
>  Please consider adding schema for ItemAvailability as “BuiltToOrder”.
>  Dave

Received on Tuesday, 26 November 2024 14:35:59 UTC