Deliverables as drafted on 13 Dec 2017 + minutes from 08 March 2018 marked red In a nutshell Provide standards for the description of Input Request and Output Response, based on CCL / MMT. Provide basic principles for Webservice usage and implementation / design guideline. Make recommendations on best practices. Provide reference implementation of some pilot Webservices, based on the proposed standards. Also a manual describing the underlying business process. Make this publicly available. Create a marketing document, describing the intentions of this Workgroup. In detail Webservice candidates as pilot / demonstrator There is some reservation against the two candidates that were nominated in last meeting (Dec.2017), therefore now a 3rd candidate is added: 1st candidate: container master data” “Get Remark: As Peter points out, there exists a similar API from the BIC to be used for their BoxTech database. It's simple, REST-based, done with SWAGGER/OpenAPI and public: Since this Webservice serves a very similar purpose, it might be used as a role model for the future SMDG Webservice. SMDG should reconcile with the BIC regarding their existing Webservice ! As part of this, compliance of input/output data fields with CCL/MMT recommendations should be evaluated . 2nd candidate: VGM” “Send possibly too complex to be implemented as a reference because the receiver needs to apply multiple checks against his booking database. Also security issues seen. 3rd candidate new: Track and Trace Container discuss security aspect: can anyone request T&T data for any container? Or is he required to provide also the booking number? For each Webservice candidate: Define the input request and output response data elements. Decision: Format of description will be OpenAPI 2 (SWAGGER). Draft: Get container master data Input Request: - Container number Output Response: - Size Type
Deliverables as drafted on 13 Dec 2017 + minutes from 08 March 2018 marked red In a nutshell Provide standards for the description of Input Request and Output Response, based on CCL / MMT. Provide basic principles for Webservice usage and implementation / design guideline. Make recommendations on best practices. Provide reference implementation of some pilot Webservices, based on the proposed standards. Also a manual describing the underlying business process. Make this publicly available. Create a marketing document, describing the intentions of this Workgroup. In detail Webservice candidates as pilot / demonstrator There is some reservation against the two candidates that were nominated in last meeting (Dec.2017), therefore now a 3rd candidate is added: 1st candidate: “Get container master data” Remark: As Peter points out, there exists a similar API from the BIC to be used for their BoxTech database. It's simple, REST-based, done with SWAGGER/OpenAPI and public: Since this Webservice serves a very similar purpose, it might be used as a role model for the future SMDG Webservice. SMDG should reconcile with the BIC regarding their existing Webservice ! As part of this, compliance of input/output data fields with CCL/MMT recommendations should be evaluated . 2nd candidate: “Send VGM” possibly too complex to be implemented as a reference because the receiver needs to apply multiple checks against his booking database. Also security issues seen. 3rd candidate new: Track and Trace Container discuss security aspect: can anyone request T&T data for any container? Or is he required to provide also the booking number? For each Webservice candidate: Define the input request and output response data elements. Decision: Format of description will be OpenAPI 2 (SWAGGER). Draft: Get container master data Input Request: - Container number Output Response: - Size Type