- From: carmen <_@whats-your.name>
- Date: Sat, 7 Mar 2015 12:05:54 +0000
- To: public-hydra@w3.org
> If you take the time to read all of the prior threads on collections and paging looking at the threads of this year, #1 and #3 largest are about paging+collections: http://m.whats-your.name/address/org/w/w3/public-hydra/2015/?c=999&set=page will go do that, but LIMIT and OFFSET are definitely crucial maybe missed a memo about them being axed? will have to read these also: http://m.whats-your.name/address/org/w/w3/public-hydra/2015/?set=grep&q=offset right off am seeing offset=10. ugh.. ive no idea how big my collections are.. Datetimes, strings, URIs, Integers could all be offsets LIMIT is what, Bytes of representation-size? resources? triples? > a mash up of multiple resources from multiple endpoints and services > .. what your smart phone or tablet does day in day out using JSON based apis these apps are made by companies who have cherrypicked 3rd party API partners, then hardcoded support for them into their apps 99% of app/site-vendors want network-effects to occur within their sites, using their API Terms and at their whim to pull the plug or acquire any 3rd party API-consuming service/app that is getting too popular. it is HIGHLY unlikely that these companies are goign to prioritize LDP or Hydra to maximize unfettered reuse/remixing. they absolutely want their API/site to be a special-snowflake that we use their API-client libraries to access. most anyone here knows this and i'm sure you do as well, reiterating re : > one reason why an ill fitting standard to be like Hydra will be ignored Hydra could have a place for "Guerilla" description of APIs, coupled with related URI-template specs, hopefully Hydra will be able to describe what exists, rather than prescribe stuff most sites will never even use or hear about as for offsets, they might not always be in ?query-string http://blog.wordpress.com/page/2/ is in the URI..
Received on Saturday, 7 March 2015 12:02:50 UTC