Re: Issues with HYDRA

Dear Vaibhav,

Glad to see another comrade working on OAS and hydra conversion.

Which version of the OAS spec are you working on?

I have started working on spec 3.0, doing keyword mapping right now. Let me
know if you are open to collaborate on this.

As for your specific question, follow Karol's instructions on
iritemplating. It covers more base than OAS.

As for headers, my plan was to introduce a custom name now and change it to
hydra spec whenever it's ready.

Regards,
Yaswanth

On Fri 13 Jul, 2018 12:53 pm Vaibhav Chellani, <vaibhavchellani223@gmail.com>
wrote:

> Hi ,
>
> I am Vaibhav Chellani working on a parser to convert Open Api
> Documentation to Api Documentation for hydrus as my Gsoc Project with
> hydrus . While developing I came across some situations where I could not
> think of a way in which I could represent the api structure written using
> Open Api Specification in HYDRA Documentation , I hope you can help me in
> the problems discussed below :
>
>    - *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 vocab's in key “expects” along with
>       the corresponding location of data ?
>    - *Templating*  : How do I represent endpoints like ‘A/{id}/B/C’?
>
>
> How do you think we can solve the above issues ?
>
>
>
> Best ,
> Vaibhav Chellani
>