- From: Myles, Stuart <SMyles@ap.org>
- Date: Tue, 6 Sep 2016 15:15:09 +0000
- To: Phil Archer <phila@w3.org>, "benedict.whittamsmith@thomsonreuters.com" <benedict.whittamsmith@thomsonreuters.com>, "public-poe-wg@w3.org" <public-poe-wg@w3.org>
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/ http://philarcher.org +44 (0)7887 767755 @philarcher1
Received on Tuesday, 6 September 2016 15:16:37 UTC