Martin Hepp

Thanks a lot! Yes, I will be using a filter for the time being! Btw, the defaults files route is very powerful; I am developing a huge library of output...

You do not even need to attach a schema:Offer to a product entity that cannot/cannot yet be ordered. An order, in the original GoodRelations sense is the promise to transfer...

I think there is a rationale in here: 1. LocalBusiness has **two parent classes:** [`schema:Organization`](https://schema.org/Organization) and [`schema:Place`](https://schema.org/Place). This has historic reasons stemming [from the original GoodRelations model](http://wiki.goodrelations-vocabulary.org/Documentation/Conceptual_model): In most business...

I see the pragmatic benefit of this, as some entities might want to express that they "in general accept credit cards" or similar. And as for data markup at Web...

+1 for adding URL to the range of schema:telephone so that tel: URIs are explicitly supported

> I guess this is not a priority for anyone, but if we are ever changing the telephone field in schema.org markups, we should also create space for the type...

Valid point. A few remarks, however: 1. We would need to adjust the text for [`schema:expires`](https://schema.org/expires), as the current text may not fit: *"Date the content expires and is no...

> 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...

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

I think the core of this problem is that any HTTP(S) access to "iot.schema.org" should not return an HTTP 200 status, but instead a 301 permanent redirect to https://schema.org. Then,...