- From: Brian Tremblay <schema@btrem.com>
- Date: Wed, 1 Mar 2017 15:20:34 -0800
- To: Jacob Jett <jjett2@illinois.edu>, "schema.org Mailing List" <public-schemaorg@w3.org>
On 3/1/17 2:35 PM, Jacob Jett wrote: > > On Wed, Mar 1, 2017 at 4:15 PM, Brian Tremblay wrote: > >> That's the problem with being so far out front. schema.org is busy >> creating new vocabs without considering whether anyone is >> consuming those vocabs. >> >> In this case, is there some benefit to labeling something >> GovernmentOrganization instead of just Organization? I'd like to >> know what that benefit is. To take another example, is anyone or >> anything doing something meaningful (that is, something more than >> they do with LocalBusiness or Restaurant) with IceCreamShop? Or >> BarOrPub? How about CampingPitch or FireStation? > > Say you have five records of organizations in your database. The > fact that two are government organizations and two are businesses and > one is a church probably doesn't matter. At that scale a human can > identify the distinctions between these organization types without > needing any mediation. > > Now imagine that your database contains 5 million records of which > roughly 1 million are government organizations, 2 million are > businesses, 120k are churches, and the other 1.88 million are a > jumbled long tail of other organization types not covered by the > first three sub-types. This is a situation where having narrower > sub-classes definitely helps the end user zero in on the things they > are interested in. It only helps the end user has access to those sub-classes. In your imaginary database, one column has "org_type", populated with one of church, government, hospital, business, garage, cafe, bar, dog pound, zoo, preserve, foo, bar, baz, bat, foobar, bazbat, etc. What good is having that column if the user can not add a WHERE clause to a SELECT statement? -- Brian Tremblay
Received on Wednesday, 1 March 2017 23:21:38 UTC