Hydra W3C Community Group Telecon

Minutes for 2019-05-14

  1. API Examples
  2. Resolve pull request #185
  3. Discuss rdfs:range issue #192
  4. hydra:manages
Action Items
  1. Sebastien would share some API examples of his own
  2. Tomasz adds a proper statement in the spec on how to undestand manages block
Karol Szczepański
Karol Szczepański
Karol Szczepański, Tomasz Pluskiewicz, Sebastien Lambla
Audio Log
Karol Szczepański: Meeting: Hydra W3C Community Group Conference Call
Karol Szczepański is scribing.

Topic: API Examples

Karol Szczepański: there are no PRs pending
Tomasz Pluskiewicz: I wanted to keep track on the progress
Tomasz Pluskiewicz: wanted to propose implementing stuff on top of the API examples
Tomasz Pluskiewicz: finished stuff on the front end, generic app that I maintain
Tomasz Pluskiewicz: Sebastian, did you have a chance to take a peek on the examples?
Sebastien Lambla: I'm happy to review it
Sebastien Lambla: working on server implementation with .net server
Tomasz Pluskiewicz: did you have any thoughts on making api examples a repository useful for yourself
Tomasz Pluskiewicz: following a slack chat you'd be best source of feedback
Sebastien Lambla: we tried to follow the examples with the heracles client
Sebastien Lambla: there were examples with divergence, that were not compatible with collections, items
Sebastien Lambla: I'm happy going through the examples to understand whole topic
Tomasz Pluskiewicz: actions are relatively new
Karol Szczepański: actions didn't make it trough to the espec
Sebastien Lambla: we've got a live API that uses operations
Karol Szczepański: I'd love to help you with whatever needs you have related with hydra that your customer needs
Karol Szczepański: there is some .net implementation I've made some time ago
Tomasz Pluskiewicz: also I did create a nancy module for hydra
Tomasz Pluskiewicz: there are two clients in JS so we can discover possible ways of using it
Sebastien Lambla: some implementation workshop would come in handy
Sebastien Lambla: is it worht of keeping several examples in same repo or to have a separate one?
Karol Szczepański: we've agreed on having multiple API in one example repo
Sebastien Lambla: there are some broken things in hydra, but entrypoint, documentation and collections I have implemented
Sebastien Lambla: there are some purchase actions on some collections
ACTION: serialseb would share some API examples of his own
Tomasz Pluskiewicz: we shall create some issues to havae a backlog for future API examples

Topic: Resolve pull request #185

Karol Szczepański: I'd love to have it merged ASAP as this PR sits there for some time
Karol Szczepański: we agreed on not moving toward any more complicated header constructs, thus only xsd:string sits in the terms
Tomasz Pluskiewicz: I din't look at this one recently
Tomasz Pluskiewicz: but I agree xsd:string is fine now, there shouldn't be any problem with having more detailed values in future

Topic: Discuss rdfs:range issue #192

Sebastien Lambla: we're implementing rdfs:ranges on our side
Sebastien Lambla: it's a local vocabulary
Sebastien Lambla: we've redefined context to have the payload look like a pure JSON
Tomasz Pluskiewicz: maybe Karol's statement on having MAY in first point I proposed is not that bad
Tomasz Pluskiewicz: if taking into account Sebastiens approach
I barely here you Tomasz :(
Sebastien Lambla: we're dynamicaly compiling serializers, we're linking documents
Sebastien Lambla: this is for pure performance purposes
Sebastien Lambla: there is no JSON-LD in the backend - we cannot have it at the moment due to performance
Sebastien Lambla: whole communication is with pure JSON and context linked

Topic: hydra:manages

ACTION: tpluskiewicz adds a proper statement in the spec on how to undestand manages block