Olivier Mélois

> Just for my information is there an easy way to implement a custom protocol? Depends on the semantics of the protocol, and on your ability to reason in abstract....

@LiiMooTBM, so, our OpenAPI conversion was adapted from the constructs provided by directly by AWS. See [here](https://github.com/awslabs/smithy/blob/c8ce65a2bcc0264f3aeeb9db096564e0491a8786/smithy-openapi/src/main/java/software/amazon/smithy/openapi/fromsmithy/protocols/AbstractRestProtocol.java). I think it'd be best to adapt directly from there. I cannot remember...

wut, I wasn't aware `apply` was a possibility in the json syntax. You are correct in what needs to happen though. Mind PR-ing it in ?

We need a pre-processing step, that would inline the apply. We also need a pre-processing step that would inline the mixins. It's really doable, just a bit tedious.

Yes. But as isolated function `Model => Model` function that could be run in isolation.

> I don't know exactly whether the recommendation should be writing absolute paths in the smithy files That is a protocol-specific concern, and for the "simpleRestJson" protocol, the implicit rule...

> I think we should look at this some time soon Thanks for volunteering 😄

Yeah it's a different thing : this ticket has the server-side handling in in scope, the other one only has client-side with the added constraints of signing, URL setting, etc.

@daddykotex are we able to close this issue now ?

It's not even compilation that seems to hang, the following is sufficient to make it hang (on my machine anyway): ```scala //> using scala "2.13.10" //> using lib "com.disneystreaming.smithy4s::smithy4s-core:dev-SNAPSHOT" //>...