Re: makesOffer should accept Service

Hi Martin — 

with regard to … 
> 
> 2. As for modeling services, schema:Product fits; it can be constrained by combining it with www.productontology.org types or other schema.org types without problems (in general; some Google infrastructure does not yet fully support multi-typed entities).
> 

… I don’t understand.  How would one use Product to model, say: the services of a product liability attorney who works on contingency: the SLA of an internet service provider offering to provide specific bandwidth rates, availabilities, etc. over a specific period of time;  a real estate broker specializing in distressed properties; or a hospital that specializes in orthopedic surgeries and that wants to cite certain procedures or success rates?  None of the Product properties seem to support these notions of performance, conditionality, rate, quality, technique, delivery time and method, etc.  And, conversely, many of the Product properties do not pertain.  It is possible, I suppose, to stuff of all of the salient differentiators into “description,” but the utility of Schema is undermined.  In any event, Product seems to be a tortured use of the word to describe what is being offered.

best,

Rob

Received on Thursday, 2 January 2014 12:56:16 UTC