Hypermedia and path variable

Hi everyone,

I’m facing an issue an i don’t know if there is a solution yet.

Is it possible to pass an absolute URI from a links object as a variable for a path ?

Example :

links:
  pathLink:
    operationId: whatever
      parameters:
        pathUri: '$response.body#_links/whatever/href'

And then having as a path :

paths:
  '{pathUri}':
    get:
    operationId: whatever
      parameters:
        - name: pathUri
          in: path
          required: true
          schema:
            type: string

According to the specification, paths must be relative but in that specific case could it be acceptable ?

Thanks for your answers.

[darrelmiller]

@handrews That leading slash in paths makes me sad every time I see it.

@boubasse I don’t think removing the slash is feasible in a non-breaking way. So, I think we are stuck with it until at least 4.0

However, there is another more radical thing that might be doable in a point release. We possibly could introduce a new top level concept called ‘resources’. The resources node would use a complete URI Template to identify the resource. This would enable describing resources that can only be discovered via links and also enable supporting operations that are differentiated by query parameter.

resources:
  '{uriTemplate}':
    get:
      operationId: whatever
      parameters:
        - name: pathUri
          in: path
          required: true
          schema:
            type: string

This would be a big change and I don’t know what the appetite for this kind of change is in the community.

[handrews]

hit post too soon…

My point was to see if there’s still interest in the resources idea or if anything else has come up in the meantime.