is 'notAvailableAtOrFrom' really needed, wouldn't the following work as
well?
Not Available in China
{
"@context": "http://schema.org",
"@type": "WatchAction",
"target": "http://www.hulu.com/thedailyshowwithjonstewart",
"contingentOnOffer": {
"@type": "Offer",
"availability": "http://schema.org/False",
"availableAtOrFrom": {
"@type": "Country",
"name": "CHN"
}
}
2014-09-18 23:44 GMT+02:00 ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>:
> On 09/18/2014 10:43 PM, ☮ elf Pavlik ☮ wrote:
> > On 09/17/2014 11:21 PM, Vicki Tardif Holland wrote:
> >> And adding to Offer
> >> http://schema.org/notAvailableAtOrFrom
> > Whenever we change Offer I think we should check if it also makes sense
> > for Demand. Also looking at name of this property @|@ I would propose
> > considering some alternative solutions before committing to this one. I
> > have some suggestions but would prefer to share them in github PR (or
> Issue)
> I just suggested another pattern in:
> https://github.com/rvguha/schemaorg/issues/125#issuecomment-56107865
>
>
>