- From: Thad Guidry <thadguidry@gmail.com>
- Date: 2018年6月14日 07:46:03 -0500
- To: Martin Hepp <mfhepp@gmail.com>
- Cc: Anthony Moretti <anthony.moretti@gmail.com>, Dan Brickley <danbri@google.com>, Sebastian Samaruga <ssamarug@gmail.com>, Simon Cox <Simon.Cox@csiro.au>, Peter Patel-Schneider <pfpschneider@gmail.com>, Richard Wallis <richard.wallis@dataliberate.com>, Web Semantic <semantic-web@w3.org>, public-schemaorg@w3.org
- Message-ID: <CAChbWaOJr2c6uKjKhDtP-DR7OzFaJ0-Ckbet4oxM6NbxVgv7iA@mail.gmail.com>
Hi Martin ! "no, ProductModel is not an attribute, it is a class in its own right." Yes, that's what our current modeling simplifies to since it borrowed the top level from RDF. And that's where you have your opinion and others politely disagree and have their own opinion, that Model is an attribute or trait of the type Product. But that is fine ! We have dealt with it and things are published now. No worries! I was just referring to also having an Attribute or Trait as a Meta Type. Where Schema.org could have had it, but chose to simplify the hierarchy for various reasons. "Type" - a kind of thing - A class, also often called a 'Type'; equivalent to rdfs:Class. - "Attribute" or maybe "Trait" - Piece(s) of information that determine the properties of a Type. - A quality or feature of a Thing - "Property" - A property, used to indicate *<strikethrough>*attributes and*</strikethrough> *relationships of some Thing; equivalent to rdf:Property. I would have hung Properties off of an Attribute or Trait, and maybe I would have removed SubClasses. All the best man, still respect your valuable efforts ! -Thad
Received on Thursday, 14 June 2018 12:46:47 UTC