- From: Thad Guidry <thadguidry@gmail.com>
- Date: Mon, 12 Sep 2016 21:19:21 -0500
- To: Eric Franzon <eric.franzon@gmail.com>
- Cc: W3C Vocabularies <public-vocabs@w3.org>
- Message-ID: <CAChbWaPS1CvD4cHfVBcUm5xrHVJbKMC4ximWay6FWawNRtFDSg@mail.gmail.com>
Hi Eric, In the past, I've voted to stick 'about' right onto schema.org/Thing :) any Thing can be about anyThing :) But that was deemed overkill. I like killing things I guess. :) In general, and a few folks swayed my mind into conciseness, having 'about' available on Types where it makes common sense for that Type in the wild is usually a best practice. So if you have more than just Event that you feel 'about' or 'aboutness' is a common occurrence that your seeing, then let's expand into those domains as well. A few that I see with my quick 1 minute eyes : http://schema.org/TelevisionChannel - home improvement, gardening, etc - HGTV http://schema.org/JobPosting - industry=gaming, skills=machine learning, about=Biological Systems http://schema.org/ReservationPackage - I recall folks in Travel industry wanting 'about' to help sell their tour packages in niche markets like 'ecology', 'space', etc. http://schema.org/Organization and http://schema.org/NGO and probably any sub Organization types we have like GovernmentOrganization - In Freebase we had a really cool 'aboutness' property called 'scope' or something, forgot what it was actually called, to note what an organization is involved in, not just its naics code or industry. Like PETA would have a scope of 'animal rights'. and so many more I forgotten about. Thad +ThadGuidry <https://www.google.com/+ThadGuidry>
Received on Tuesday, 13 September 2016 02:19:55 UTC