- From: Markus Lanthaler via GitHub <sysbot+gh@w3.org>
- Date: Sun, 18 Mar 2018 16:21:43 +0000
- To: public-hydra-logs@w3.org
I agree with everything Pavlik said. The design might still need a bit of work though (some of which may be out of scope for this PR like a more expressive description of what data an action/operation `expects`). I'd like to explore even more drastic changes to the client interface by raising the level of abstraction to something like this:
```javascript
client.usingApi("http://example.com/")
.findCollectionWith({
property: "http://www.w3.org/1999/02/22-rdf-syntax-ns#type",
object: "http://schema.org/Event"
})
.invoke('http://schema.org/CreateAction')
.whichExpects('http://schema.org/Event')
.withData(event)
.getResult();
```
We should keep an eye on the verbosity the split of operations into actions and operations entails.
---
Review status: all files reviewed at latest revision, 8 unresolved discussions.
---
*Comments from [Reviewable](https://beta.reviewable.io/reviews/hydracg/specifications/154#-:-L7tslA77zi0iLtBGK48:b-ifs2b4)*
<!-- Sent from Reviewable.io -->
--
GitHub Notification of comment by lanthaler
Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/154#issuecomment-374012295 using your GitHub account
Received on Sunday, 18 March 2018 16:21:47 UTC