- From: Thad Guidry <thadguidry@gmail.com>
- Date: Tue, 10 Jul 2018 20:48:02 -0500
- To: Joe Duarte <songofapollo@gmail.com>
- Cc: "schema.org Mailing List" <public-schemaorg@w3.org>
Received on Wednesday, 11 July 2018 01:48:39 UTC
Joe, The Type Names are a guide...not really anything other than a semantic placeholder. The Type Descriptions are a guide...not really anything other than a semantic placeholder's definition. I.E. We could have a Type called "FirePitsForPeopleToCookMarshmellowsAndHotDogs" with a definition of "a spot, of fire, to do whatever you want. Some folks just watch it, others might pitch a tent nearby it, still others might never light the thing, and hence its just a pit, nay....just a spot". It doesn't matter. But as you can see, it sorta does matter. We want Types and Properties labels and definitions to not get lost in translation. And... Developers still get it wrong sometimes on proper usage of them, no matter what labels we use or how we define it, or what languages we use. And... That's OK. (Mostly) :-) Let's move on Joe. -Thad
Received on Wednesday, 11 July 2018 01:48:39 UTC