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:

• Add: http://schema.org/ineligibleRegion domainIncludes Demand, DeliveryChargeSpecification.
• Add: http://schema.org/ineligibleRegion rangeIncludes GeoShape, Text
• Add: http://schema.org/eligibleRegion rangeIncludes Place

(We might also consider their relationship to Action types while we're at it - spawn separate issue?)