-
Notifications
You must be signed in to change notification settings - Fork 838
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
eligibleRegion and ineligbleRegion have different associated types #213
Labels
guidelines docs examples
Work on our supporting materials rather than on schema definitions
schema.org vocab
General top level tag for issues on the vocabulary
Milestone
Comments
I think we should do this. |
agreed |
+1 |
mfhepp
added a commit
to mfhepp/schemaorg
that referenced
this issue
Mar 24, 2015
Closed
I just submitted a pull request that fixes this: |
36 tasks
that looks good to me |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
guidelines docs examples
Work on our supporting materials rather than on schema definitions
schema.org vocab
General top level tag for issues on the vocabulary
http://schema.org/eligibleRegion
http://schema.org/ineligibleRegion
eligibleRegion is applicable on more types, but fails to allow Place.
ineligibleRegion is applicable on fewer types (not Demand or DeliveryChargeSpecification), and anticipates Place but not GeoShape, Text.
There is no obvious reason for these properties to vary.
Exact proposal:
(We might also consider their relationship to Action types while we're at it - spawn separate issue?)
The text was updated successfully, but these errors were encountered: