Hydra W3C Community Group Telecon
Minutes for 2019-09-03
- Agenda
- https://www.w3.org/community/hydra/wiki/Conference_Calls#2019-09-03
- Topics
- Action Items
- Chair
- Karol Szczepański
- Scribe
- Karol Szczepański
- Present
- Sebastien Lambla, Tomasz Pluskiewicz, Karol Szczepański
- Audio Log
Karol Szczepański: Meeting: Hydra W3C Community Group Conference Call
Karol Szczepański is scribing.
Topic: Consider extending Hydra to handle non-RDF payloads
Tomasz Pluskiewicz: I had some discussions and the only thing that is needed is the first snipped after the proposed solutions
Tomasz Pluskiewicz: #199 replaces range of the hydra:expect with rangeIncludes
Karol Szczepański: will be there any harm in having both range and rangeIncludes?
Tomasz Pluskiewicz: whatever will be there, will be considered hydra:Class
Karol Szczepański: this is a breaking change
Karol Szczepański: I've suggested replacing a hydra:Class with hydra:Resource leaving range predicate
Tomasz Pluskiewicz: what about having both, range of hydra:Resource and rangeIncludes with more hints
Sebastien Lambla: I'm thinking about a generic browser console, when browsing, how will it work?
Tomasz Pluskiewicz: a completely generic browser is ultimately an excercise gowing towards utopia
Tomasz Pluskiewicz: generic client should support at least those of the rangeIncludes values provided in the spec
Sebastien Lambla: I may accept an event but that specific server will accept it in turtle format
Sebastien Lambla: I think content negotiation shoulld be a topic for another call/spec modifications
Sebastien Lambla: I think operation expectation and what can be actually sent may be somehow different
ACTION: Karol_Szczepanski will create a PR with range of the hydra:expect downgrade to hydra:Resource and introduce rangeIncludes with hydra:Class
Tomasz Pluskiewicz: we shall start thinking aobut an esxtension which will come with those features missing
Karol Szczepański: I'm worried that this will end up with a core vocabulary unusable and several extensions that won't fit to each other
ACTION: serialseb will provide raw use case scenarios of what may be needed regarding non-RDF payloads and content negotiation
TemplatedLink cannot formally have supportedOperation
Topic: Return to recently discussed PRs
ACTION: Karol_Szczepanski will take care of #197
Topic: Discuss PRs in Example API repository
Tomasz Pluskiewicz: I've sidestepped the issue as type entailing is quite complicated when you go deeper
Karol Szczepański: indeed; what Heracles.ts does not is a simple range/domain entailing and possibly I own't go any deeper