Follow-up to discussion in #4657 with @MatthiasWiesmann.

Problem Definition

Current Schema.org properties (productionDate, purchaseDate) capture static timestamps but fail to describe the full lifecycle mandated by ESPR (manufacturing, repair, refurbishment, recycling).

We need a way to model discrete events in a product's life, each with its own location, performer, and certification data.

Proposal

Introduce a new type: ProductLifecycleEvent (subclass of schema:Event).

Key Properties:

• eventType: (Enum/String) "Manufacturing", "FirstPutOnMarket", "Repair", "Refurbishment", "Recycling"
• relatedProduct: Link to the specific IndividualProduct.
• actor: Who performed the event (Organization/Person).
• location: Where it happened.
• result: Outcome (e.g., "Repaired", "Scrapped").

Example Usage

{
"@type": "ProductLifecycleEvent",
"eventType": "Repair",
"startDate": "2026-05-12",
"actor": {
"@type": "Organization",
"name": "Authorized Repair Center Paris"
},
"location": {
"@type": "Place",
"address": "Paris, France"
},
"description": "Screen replacement with generic spare part."
}

text
undefined