Hydra W3C Community Group Telecon Minutes for 2018-11-12

Thanks Karol for scribing. The minutes from this week's telecon are
now available at

   http://www.hydra-cg.com/minutes/2018-11-12/

The full text of the discussion is below, including a link to the audio
recording.


-------------------------------------------------------------------
Hydra W3C Community Group Telecon Minutes for 2018-11-12

Agenda:
  https://www.w3.org/community/hydra/wiki/Conference_Calls#2018-11-12
Topics:
  1. Presentation of Sandeep's & Vaibhav's GSoC work
  2. Talk about further plans with GSoC
  3. GSoC going forward
Chair:
  Markus Lanthaler
Scribe:
  Karol Szczepański
Present:
  Karol Szczepański, Sandeep Chauhan, Markus Lanthaler, Akshay 
  Dahiya, Tomasz Pluskiewicz, Chris Andrew, Lorenzo Moriondo
Audio:
  http://www.hydra-cg.org/minutes/2018-11-12/audio.mp3


Karol Szczepański is scribing.
Sandeep Chauhan: Hey all!

Topic: Presentation of Sandeep's & Vaibhav's GSoC work

Sandeep Chauhan: there are some slides regarding my presentation
Sandeep Chauhan: https://slides.com/sandeepsajan0/g/
design of a parser of Open API to Hydra
Open API seems to be more descriptive than Hydra
"on-screen live presentation is performed"
Markus Lanthaler: Am I the only one who doesn't hear anything 
  anymore?
Error: (IRC nickname not recognized)[20:17] <vaibhavchellani> 
  Multiple Parameters at different locations : Data can be received 
  at various locations in the form of parameters , for example 
  "header","body","path","query" . At times we may receive some 
  data from header and some from body in the same request . We get 
  only one key ie "expects" to represent the parameters . The two 
  questions here are   How to represent the location of input 
  data(parameter)?   How to represent multiple[CUT]
I've asked for a briefe list of features that were available in 
  the OpenAPI and were not in the Hydra or were difficult to 
  implement
ill share a more comprehensive list in a while
1. Representing endpoints like 'A/{id}/B/C'
Error: (IRC nickname not recognized)[20:26] <vaibhavchellani> 2. 
  Specifying location of input data for eg: request, body 
  ,path,query etc along with the actual expected request 
  type(hydraClass)
Error: (IRC nickname not recognized)[20:31] <vaibhavchellani> 3. 
  Supporting array in supported_prop : There are various instances 
  where we need to represent that the supported property (object in 
  supportedProperty ) is a list when we have the semantic reference 
  of an item of the list , the question here is "how can I 
  represent a property that is supposed to be a list where each 
  item follows a particular schema"
we also had some issues with creating unique identifiers on 
  server side for the agent to identify easily , right now we are 
  using uuid but the id should be verifiable on client side as well 
  as server side hence we were toying with the idea of checksum as 
  well.

Topic: Talk about further plans with GSoC

In order to attract more developers we should start with basics

Topic: GSoC going forward

Akshay Dahiya: http://35.224.198.158:5000/
Akshay Dahiya: The Simulation demo Gui
Akshay Dahiya: http://35.224.198.158:8080/api
Akshay Dahiya: http://35.224.198.158:8081/api
Akshay Dahiya: http://35.224.198.158:8082/api
Akshay Dahiya: http://35.224.198.158:8083/api
Akshay Dahiya: http://35.224.198.158:8084/api
Akshay Dahiya: Links to all the serves (drones and central 
  controller for the simulation)
Akshay Dahiya: P.S - Everything can be accessed from the Gui link

Received on Monday, 12 November 2018 20:18:26 UTC