> 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.
