The workflow does depict asynchronous processing, i.e. events might be validated during async processing.
imho only Capture-FileSize-Limit: 413 Payload Too Large, is suitable as a valid condition for preliminary exit from POST /capture service.
Description of asynchronous capture process is missing completely
Location header flow and how it has to be used to call GET /capture/{captureID} for retrieving capture details from Capture Jobs Interface shall be addded.
RESTful binding shall support both EPCISDocument and EPCISQueryDocument
sboeckelmann
commented
1 year ago
Capture Interface workflow (Figure 12-3)
The workflow does depict asynchronous processing, i.e. events might be validated during async processing. imho only Capture-FileSize-Limit: 413 Payload Too Large, is suitable as a valid condition for preliminary exit from POST /capture service.
Description of asynchronous capture process is missing completely
Location header flow and how it has to be used to call GET /capture/{captureID} for retrieving capture details from Capture Jobs Interface shall be addded.
RESTful binding shall support both EPCISDocument and EPCISQueryDocument
see https://github.com/gs1/EPCIS/blob/master/REST%20Bindings/openapi.yaml line 121