Ryan Levering

That's a reasonable point of view to piggyback on the RDFa spec. There are two things that make this impractical: 1) Most data providers are using JSON-LD for these situations...

The structure I'm seeing in my head looks like: ``` { "@type": "SocialMediaPosting", "author": { "@type": "UserAccount", "url": "http://example.com/profiles/123" ... whatever fields are present in the content (also potentially a...

Yep. So it sort of has the same range on the actual real-life entity, just with an in-between account object.

First, please post this in the Google support forums since it's a Google specific issue. I swear they bubble up and we usually do something. Or ping me directly on...

> Can you point me to the appropriate Google support forum? I would post here: https://support.google.com/webmasters/community with a "Structured Data" tag. Generally someone will try to help you and in...

I don't think we were suggesting dropping the MedicalOrganization relationship (most of the predicates in Physician I think need to be inherited because Physician was more a business in schema.org...

That would probably solve the majority of the limitation currently, but isn't my preference: 1. sharedContent has more flexibility and can point to WebPage or audio objects or whatever CreativeWork...

I obviously am interested, though I really don't think full reconciliation is the right metaphor. That's a much harder problem to do correctly. What I personally am interested at the...

I'm pretty sure you are not including a schema.org @context in a JSON-LD block. Then the default (and correct) behavior is to use the current URL for type resolution.

I would log these issues to the Google help forums. We don't always notice things here and they eventually escalate there. But that was our mistake, we're fixing it today.