trackbot, start meeting

<scribe> Scribe: Karol_Szczepanski

Consider extending Hydra to handle non-RDF payloads

t_pluskiewicz: I had some discussions and the only thing that is needed is the first snipped after the proposed solutions

https://github.com/HydraCG/Specifications/issues/199

t_pluskiewicz: #199 replaces range of the hydra:expect with rangeIncludes

Karol_Szczepanski: will be there any harm in having both range and rangeIncludes?

t_pluskiewicz: whatever will be there, will be considered hydra:Class

Karol_Szczepanski: this is a breaking change
... I've suggested replacing a hydra:Class with hydra:Resource leaving range predicate

https://github.com/HydraCG/Specifications/issues/199#issuecomment-512552384

t_pluskiewicz: what about having both, range of hydra:Resource and rangeIncludes with more hints

serialseb: I'm thinking about a generic browser console, when browsing, how will it work?

t_pluskiewicz: a completely generic browser is ultimately an excercise gowing towards utopia
... generic client should support at least those of the rangeIncludes values provided in the spec

serialseb: I may accept an event but that specific server will accept it in turtle format
... I think content negitiation shoulld be a topic for another call/spec modifications
... I think operation expectation and what can be actually sent may be somehow different

<scribe> ACTION: Karol_Szczepanski will create a PR with range of the hydra:expect downgrade to hydra:Resource and introduce rangeIncludes with hydra:Class

t_pluskiewicz: we shall start thinking aobut an esxtension which will come with those features missing

Karol_Szczepanski: I'm worried that this will end up with a core vocabulary unusable and several extensions that won't fit to each other

<scribe> ACTION: serialseb will provide raw use case scenarios of what may be needed regarding non-RDF payloads and content negotiation

<t_pluskiewicz> TemplatedLink cannot formally have supportedOperation

<t_pluskiewicz> https://github.com/HydraCG/Specifications/issues/197

Return to recently discussed PRs

<scribe> ACTION: Karol_Szczepanski will take care of #197

Discuss PRs in Example API repository

<t_pluskiewicz> https://github.com/HydraCG/api-examples/pull/8

t_pluskiewicz: I've sidestepped the issue as type entailing is quite complicated when you go deeper

Karol_Szczepanski: indeed; what Heracles.ts does not is a simple range/domain entailing and possibly I own't go any deeper

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: t_pluskiewicz Karol_Szczepanski serialseb
Found Scribe: Karol_Szczepanski
Inferring ScribeNick: Karol_Szczepanski
Agenda: https://www.w3.org/community/hydra/wiki/Conference_Calls#2019-09-03

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: karol_szczepanski serialseb

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)