Thanks Huabing. From: [email protected] [mailto:[email protected]] Sent: Wednesday, July 26, 2017 8:21 PM To: GUDISENA, VARUNESHWAR <[email protected]> Cc: [email protected] Subject: Re:[onap-discuss] API Format
Hi Varun, So far Swagger is recommended for API documentation. https://wiki.onap.org/display/DW/RESTful+API+Design+Specification+for+ONAP<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_RESTful-2BAPI-2BDesign-2BSpecification-2Bfor-2BONAP&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=S2qOaens2S1X5nqU95xJeA&m=fNvo6uRVREvmBSxOAzEBMDbvUZRuOFryCKBYemidIqM&s=C4_AccnO7O80RppE3Rc17R0lCB9hqffoEiWNUQdInfg&e=> BR, Huabing Original Mail Sender: <[email protected]<mailto:[email protected]>>; To: <[email protected]<mailto:[email protected]>>; Date: 2017/07/27 06:02 Subject: [onap-discuss] API Format Hi all, Since we have to document APIs for M2 Release Functionality Freeze Milestone, is there any defined format for the APIs. Is Swagger format fine? Thanks Varun Gudisena Sr. Software Engineer AT&T Services, Inc. 211 S Akard St, Dallas ,TX 75202 USA Ph: 617-834-4157
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
