expires property should apply to Product about schemaorg HOT 7 OPEN

Valid point. A few remarks, however:

1. We would need to adjust the text for schema:expires, as the current text may not fit:
   "Date the content expires and is no longer useful or available. For example a VideoObject or NewsArticle whose availability or relevance is time-limited, or a ClaimReview fact check whose publisher wants to indicate that it may no longer be relevant (or helpful to highlight) after some date."

The current property mixes the aspects of (1) availability with (2) end of relevance/usefulness/fitness for consumption.

expires for media seems to be mostly useful for deciding whether an object should be shown or no longer, whereas for products, it will mostly be used to predict shelf life or fitness for consumption. It can be a useful feature for product comparison, e.g. for long-lasting variants of food products.

2. If you want to use a date or datetime as the range, you can only use the property on IndividualProduct, because every bottle of milk will have an individual expiry date. So we would have to include Duration to the range. This would change the meaning and may require changing consuming applications, as a duration is relative to some (often unknown) point in time (e.g. date of production or purchase).

So I think it would be better to add a new property or two new properties, e.g. schema:expirationDate with a range of date or datetime (for "best before use", "use by" data of individual products, like food items or pharmaceuticals, and schema:shelfLife(we may need a better term) with a range of duration as a typical product characteristics.

A good reference is the NSF page on expiration dates.

from schemaorg.

That makes sense, a new property on IndividualProduct would make sense.

from schemaorg.

That makes sense, a new property on IndividualProduct would make sense.

I think the shelfLife property is more useful, because at least in public Web content, we rarely describe individual products or production batches (this may be different for B2B usages of the schema.org datamodel).

A bit more background is in the archived GoodRelations Wiki.

from schemaorg.

The period after opening would also be a candidate, it is very often present on cosmetic symbols, in a coded way: https://wiesmann.codiferes.net/wordpress/archives/29169

from schemaorg.

Maybe it is best to align with GS1 properties in here?
E.g. https://www.gs1.org/gs1-web-vocabulary

from schemaorg.

Yes, maybe what we need is to mention these at the right (product) level

from schemaorg.

This issue is being nudged due to inactivity.

from schemaorg.