W3C home > Mailing lists > Public > public-schemaorg@w3.org > March 2017

Re: Google Structured Data Testing Tool - improved support for multiple independent types

From: Robb Shecter <robb@weblaws.org>
Date: Thu, 02 Mar 2017 01:18:44 +0000
Message-ID: <CABQwFw9GFPXbfgej4DiBaxY16mv4nBNahp+9JWs5xucXqswyPA@mail.gmail.com>
To: public-schemaorg@w3.org
> In this case, is there some benefit to labeling something
>
> GovernmentOrganization instead of just Organization?
>
>
I'm think it's probably worse: there's a detriment to using
GovernmentOrganization because it may not be recognized, and so just
silently discarded.

I realized that I actually have a small successful test case, using
GovernmentOrganization as a property, not as the main type. My app
openhealthscores.com gets this search engine result for a page:

[image: Screen Shot 2017-03-01 at 5.09.04 PM.png]
I'm pretty sure that "New York City Department..." is sourced from this
schema.org/json-ld in the HTML source
<https://openhealthscores.com/us/ny/nyc/novecento/40392141>:

[image: Screen Shot 2017-03-01 at 5.10.20 PM.png]
So I conclude that although Google Search doesn't claim to support
GovernmentOrganization, they are using its data as if it's the super-class
Organization. This may be a case of Google being very permissive with the
code, just like they're permissive with malformed HTML. I.e., there's an
*author/name* attribute and so they're using it. The *@type* doesn't matter
so much for their purposes here.

Screen_Shot_2017-03-01_at_5.09.04_PM.png
(image/png attachment: Screen_Shot_2017-03-01_at_5.09.04_PM.png)

Screen_Shot_2017-03-01_at_5.10.20_PM.png
(image/png attachment: Screen_Shot_2017-03-01_at_5.10.20_PM.png)

Received on Thursday, 2 March 2017 01:28:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:12:34 UTC