New version EA - #73
Conversation
| - $ref: '#/components/parameters/acceptLanguage' | ||
| - $ref: '#/components/parameters/limit' | ||
| - $ref: '#/components/parameters/offset' | ||
| - $ref: '#/components/parameters/ogcBbox' |
There was a problem hiding this comment.
OGC should not be used.
There was a problem hiding this comment.
Why not? I've created both flavours: the REST (GET /personal-needs/) and the OGC style (GET /collections/personal-needs/items).
| - $ref: '#/components/parameters/ogcDatetime' | ||
| responses: | ||
| '200': | ||
| description: Success |
There was a problem hiding this comment.
chache control headers are needed
| content: | ||
| application/json: | ||
| schema: | ||
| $ref: '#/components/schemas/OgcItemCollection' |
There was a problem hiding this comment.
Why not? I've created both flavours: the REST (GET /personal-needs/) and the OGC style (GET /collections/personal-needs/items).
| content: | ||
| application/json: | ||
| schema: | ||
| $ref: '#/components/schemas/OgcItemCollection' |
There was a problem hiding this comment.
Why not? I've created both flavours: the REST (GET /personal-needs/) and the OGC style (GET /collections/personal-needs/items).
|
@Ulf9 "OTI - Search Offers Request.png": We should discuss if this is reflects the technical specification. E.g. the SEARCH OFFER POLICY contains now 'preferredContentLanguageCode'. The technical accepted header field is 'Content-Language'. I'd rather limit the number of possible synonims... Where it's possible, use the accepted standard wordings. |
|
@Ulf9 What do you mean with 'Search locked Offers Amendments Request' and 'Search offer Amends Request'? I'm getting lost in all the amend requests.... And they're still to be discussed in the next phase... |
3 participants
No description provided.