- From: Simon Steyskal <simon.steyskal@wu.ac.at>
- Date: Wed, 07 Sep 2016 08:24:31 +0200
- To: Phil Archer <phila@w3.org>
- Cc: benedict.whittamsmith@thomsonreuters.com, SMyles@ap.org, public-poe-wg@w3.org
Hi! AFAIK, one can constrain the number of times a certain action can be exercised, e.g.: odrl:permission [ .... odrl:action odrl:execute ; odrl:constraint [ a odrl:Constraint ; odrl:status 2 ; odrl:count 10 ; odrl:operator odrl:lteq ] ] . which means that permission to perform odrl:execute is granted as long as the property value of odrl:status is <= the one of odrl:count. However, it is currently not possible (correct me if im wrong) to narrow the scope of that constraint further, i.e. expressing that "performing odrl:execute is limited to at most 10 times within 10 minutes". simon --- DDipl.-Ing. Simon Steyskal Institute for Information Business, WU Vienna www: http://www.steyskal.info/ twitter: @simonsteys Am 2016-09-06 17:48, schrieb Phil Archer: > Will do. > > On 06/09/2016 16:22, benedict.whittamsmith@thomsonreuters.com wrote: >> Thank you Stuart! >> >> Phil - I think you should add two use cases: a prohibition on >> web-scraping; and rate-limiting for APIs. Both are common use cases. >> >> Ben >> >>> -----Original Message----- >>> From: Myles, Stuart [mailto:SMyles@ap.org] >>> Sent: 06 September 2016 16:15 >>> To: Phil Archer; Whittam Smith, Benedict (TR Technology & Ops); >>> public- >>> poe-wg@w3.org >>> Subject: RE: One by one, but not in bulk >>> >>> I think you'd need to figure out how you could express this "not in >>> bulk" requirement in terms that a machine could understand. >>> >>> >>> >>> For example, you might be able to express this as a restriction on >>> how >>> frequently the API could be called. Or by imposing a limit to the >>> number of times it could be called within a given timeframe. (Both of >>> these are typical "rate limiting" strategies for APIs). >>> >>> >>> >>> Regards, >>> >>> >>> >>> Stuart >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -----Original Message----- >>> >>> From: Phil Archer [mailto:phila@w3.org] >>> >>> Sent: Tuesday, September 06, 2016 9:21 AM >>> >>> To: benedict.whittamsmith@thomsonreuters.com; public-poe-wg@w3.org >>> >>> Subject: Re: One by one, but not in bulk >>> >>> >>> >>> >>> >>> >>> >>> On 06/09/2016 14:18, benedict.whittamsmith@thomsonreuters.com wrote: >>> >>>> Hi Phil, >>> >>>> >>> >>>> I think a odrl:Prohibition on screen-scraping would likely be a very >>> common requirement. I'm not sure if screen-scraping would come under >>> odrl:extract - but perhaps we can provide some guidance here. >>> >>>> >>> >>>> As to downloading one-by-one rather than by collection: does the API >>> provide two methods, one of which is prohibited? Seems a bit odd to >>> me >>> at first glance. >>> >>> >>> >>> No, what I mean is you're not allowed to hit the API repeatedly and >>> thereby collect the full dataset, not that there's a big red button >>> marked "do not push!" >>> >>> >>> >>> Phil >>> >>> >>> >>> >>> >>>> >>> >>>> Ben >>> >>>> >>> >>>>> -----Original Message----- >>> >>>>> From: Phil Archer [mailto:phila@w3.org] >>> >>>>> Sent: 06 September 2016 14:05 >>> >>>>> To: POE WG >>> >>>>> Subject: One by one, but not in bulk >>> >>>>> >>> >>>>> I had a quick look through the use cases but can't immediately >>> >>>>> identify one that covers one that just came up at a Big Data Europe >>> >>>>> meeting; so can I check whether this is new or already covered or >>> >>>>> doable in ODRL please? >>> >>>>> >>> >>>>> You can use our API to access one item at a time, but you may not >>> >>>>> download the full set as bulk (including by screen-scraping). >>> >>>>> >>> >>>>> Is this new? (it's definitely a real case). >>> >>>>> >>> >>>>> Thanks >>> >>>>> >>> >>>>> Phil. >>> >>>>> >>> >>>>> -- >>> >>>>> >>> >>>>> >>> >>>>> Phil Archer >>> >>>>> W3C Data Activity Lead >>> >>>>> http://www.w3.org/2013/data/ >>> >>>>> >>> >>>>> https://urldefense.proofpoint.com/v2/url?u=http- >>> >>>>> 3A__philarcher.org&d=CwICaQ&c=4ZIZThykDLcoWk- >>> >>>>> >>> GVjSLm9hvvvzvGv0FLoWSRuCSs5Q&r=GQ6xvz2BG1vCgiGGeLHdL1qJLbLUqYG6W19eFB >>> >>>>> lz >>> >>>>> >>> nzDGH3wjzyriGVJemENTKsgx&m=xUrZnBS5gfbR7wgzYE1s_Jm8ESkCE2psO4sSVTRBD9 >>> >>>>> k& s=XiuIAfz3FkSsJjzaa77Q5pkUQ0LgYEmqWKhX6kKO1YA&e= >>> >>>>> +44 (0)7887 767755 >>> >>>>> @philarcher1 >>> >>>> >>> >>> >>> >>> -- >>> >>> >>> >>> >>> >>> Phil Archer >>> >>> W3C Data Activity Lead >>> >>> http://www.w3.org/2013/data/ >>> >>> >>> >>> https://urldefense.proofpoint.com/v2/url?u=http- >>> 3A__philarcher.org&d=CwIGaQ&c=4ZIZThykDLcoWk- >>> GVjSLm9hvvvzvGv0FLoWSRuCSs5Q&r=GQ6xvz2BG1vCgiGGeLHdL1qJLbLUqYG6W19eFBlz >>> nzDGH3wjzyriGVJemENTKsgx&m=8YZef1IuWePBgyxkRbNVeZo6JsWxwwPr7X0iFFLSz3A& >>> s=2Y5OlnJT-0UkRkxLnVLti6ugm0kqzwbiP-_uvIX2jTM&e= >>> >>> +44 (0)7887 767755 >>> >>> @philarcher1 >>> >>> >>
Received on Wednesday, 7 September 2016 06:27:32 UTC