Re: Escaping in URL templates

Hi Antonin,

Glad you asked.
I am quite new to the group, so please excuse me if I am talking nonsense.
In case you already have discussed this issue before.

It is in my opinion that one should avoid reworking other groups' specs.
Particularly if it is not the aim of the working group.
Having that in mind, it will be nice if the Reconcile API is built on top
of the OpenAPI (https://github.com/OAI/OpenAPI-Specification) specs.
Especially because it has broader acceptance and adoption (e.g. Daimler
Mobile data API).
In this particular case, the OpenAPI specifies the use of simple brackets
e.g. {variable} (
https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-templating
).

kind regards,
<emarx/>
http://emarx.org


On Fri, Apr 16, 2021 at 5:58 PM Antonin Delpeuch <antonin@delpeuch.eu>
wrote:

> Hi all,
>
> One area where we could make some progress is the URL templates exposed
> by the manifest:
> https://github.com/reconciliation-api/specs/issues/39
>
> Beyond the fact that the template variable is not consistent across the
> whole manifest, the escaping of the value it is replaced with remains to
> be specified. The problem is that both behaviours (escaping or not) can
> potentially be useful in some contexts.
>
> Any thoughts about how to specify this better?
>
> Best,
> Antonin
>
>