- From: Clemens Portele via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Jan 2022 20:38:33 +0000
- To: public-sdwig@w3.org
> And what's the relationship between "Bespoke APIs" and "Convenience APIs"? A "bespoke API" is an API that largely ignores standardized API building blocks (using OGC API terminology). A "convenience API" is an API that is designed for a specific usage (convenient for clients supporting that use case). There is no strict relationship. Sometimes an API has to be "bespoke" to be "convenient", but for other uses an OGC Web API (not "bespoke") can also be "convenient". BP 12 basically says that you should look at the user needs in your API design. When we wrote BP 12 five years ago the point was that WFS etc are for most web uses/users not easy or convenient to use. In that sense the text implies that often convenience implies bespoke, but there has been some progress and the whole discussion needs a review. -- GitHub Notification of comment by cportele Please view or discuss this issue at https://github.com/w3c/sdw/pull/1332#issuecomment-1023619274 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 January 2022 20:38:34 UTC