Thad Guidry

@MatthiasWiesmann I didn't assume any of those. I simply stated that Schema.org provides a property to hold the values. How to format the values, attach additional metadata to the values,...

@MatthiasWiesmann Oops! So sorry, that should have been PropertyValue https://schema.org/PropertyValue . But the PropertyValueSpecification comes from Hydra and it's a way to specify a format (using it's valuePattern). If using...

I much prefer property/value pairs in JSON-LD, and how I usually handle it. I have always found property/value pairs (semantics, which allows easier information exchange) to be easier to parse...

@vberkel Its not ProductORModel ... its actually AProductModel So the heirarchy is fine the way it is. What needs to change is our current stupid confusing description. Which I never...

@jvandriel ProductModel = model (which could be a variant of another model) For clarity, scroll to the bottom and see the reversing properties http://schema.org/ProductModel In Good Relations and Schema.org... Products...

This is valuable. Agree with /ProductGroup name. Will /ProductGroup have properties for parent/sibling relationships like /ProductModel has with pre/succ ? Do we expand pre/succ to also expect a type of...

@danbri small quibble, but... could we get the description on https://webschemas.org/ProductGroup to also mention "features" perhaps like: > A ProductGroup represents a group of Products that vary only in certain...

@danbri There's a lot, depending on the ProductGroup and industrial manufacturer. I only gave this one example to illustrate a real world scenario with 2 ProductGroup levels (actually 3 if...

@alex-jansen "Packages" often do have a SKU (and in the USA, a single UPC label) and treated as a sellable item (fit for sale). A Package offered **can** be an...

@RichardWallis I've pinged David and Wendell from [ProgrammableWeb.com](http://www.programmableweb.com) to voice their opinions here as well. Hopefully they respond shortly.