W3C home > Mailing lists > Public > public-vocabs@w3.org > September 2014

Re: Schema.org proposal: New Actions and Actions contigent on an Offer

From: Jarno van Driel <jarnovandriel@gmail.com>
Date: Fri, 19 Sep 2014 00:24:57 +0200
Message-ID: <CADK2AU3Kvg2PvzJ6k8j81_YrDtEWgnCkLjAOzqoShJjWD6zSpQ@mail.gmail.com>
To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
Cc: Vicki Tardif Holland <vtardif@google.com>, "public-vocabs@w3.org" <public-vocabs@w3.org>
Sorry for spamming - I'm toying around with it in my head- how about an MTE?

{
"@context": "http://schema.org",
"@type": "WatchAction",
"target": "http://www.hulu.com/the­daily­show­with­jon­stewart",
"contingentOnOffer": {
"@type": [ "Offer", "False" ],
"availableAtOrFrom": {
"@type": "Country",
"name": "CHN"
}
}

2014-09-19 0:18 GMT+02:00 Jarno van Driel <jarnovandriel@gmail.com>:

> And maybe 'contingentOnOffer' can be renamed to something like
> 'dependsOnOffer'.
>
> As I'm not a native English speaker I had to look up what 'contingent on'
> first before I understood what it meant. So if you could 'dumb down' the
> term a bit I'd be much obliged.   :)
>
> 2014-09-19 0:10 GMT+02:00 Jarno van Driel <jarnovandriel@gmail.com>:
>
>> 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/the­daily­show­with­jon­stewart",
>> "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
>>>
>>>
>>>
>>
>
Received on Thursday, 18 September 2014 22:25:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:44 UTC