New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
itemOffered and offers do not match in range vs. domain: CreativeWork#637
Comments
We should encourage the use of multiple types. Otherwise, we will need to expand the domain for many properties related to Product. |
+1 for MTEs (note: Google's Search Console reports MTEs successfully, it's only their Structured Data Testing Tool that can't handle them yet) |
Another +1 for MTEs On 9 Jul 2015, at 15:49, jvandriel <notifications@github.commailto:notifications@github.com> wrote: +1 for MTEs |
By the way, why does schema.org/CreativeWork have the I feel the proper way to express this would be by using an MTE as well: |
Bumping this, as the general case of 'offers' and 'itemOffered' being near-but-not-quite inverses hasn't gone away. See also https://plus.google.com/+Evgeniy-Orlov/posts/fYFQEAv4jPL for a recent report. Are there any reasons to not want to align all the associated types and declare these properties to simply be inverses of each other? They do appear at first reading to just mean the same thing in either direction. |
I keep bumping into this. My 2019 proposal is that we copy over the ugly list of types, for backwards compatibility, and declare these formal inverses. The definitions should also mention that while a few kinds of offerable thing are listed, others are possible and can be expressed with multiple typing (i.e. Product and its subtypes). |
Ok I have made them fully inverse of each other. This meant that 'offers' also needed to acquire mention of being used with Demand. |
This issue is being tagged as Stale due to inactivity. |
http://schema.org/offers includes CreativeWork as its domain, while http://schema.org/itemOffered does only include Product in its range..
So currently, you have to use Book -> offers -> Offer for books; Offer -> itemOffered -> Book does not work as of now.
Note: It is not clear to me whether we should simply include CreativeWork in the range of itemOffered. Using multi-typed entities properly would be a cleaner approach
Works:
Does not work:
The text was updated successfully, but these errors were encountered: