Hello all:
I am wondering what is the procedure for getting clarification with regarding ambiguities within the API PDF spec versus the CTK spec?
For example, with Document Management API v17.0.0 the PDF spec describes that:
description,
type, and
attachment are the mandatory attributes required to create a resource, however within the CTK, the two tests cases are contradictory of each other. "TC_DocMng_E2 - Invalid Request - Missing mandatory parameter" and "TC_DocMng_N4 - Create Document"
Similarly, with the Payment Methods API v17.0.0 we are seeing the RESTful resources
/balanceTopup being tested, however, we see no mention of this particular endpoint within the PDF specs. Also, we see that account is an attribute given in the CTK, but there are no mentions of the account attribute in the PDF specification.
My assumption is that each individual API release is self-contained, such that, I am not required to read earlier versions of the API spec to fully understand the spec or having to cross-reference other API spec documents.
------------------------------
Bill Li
TELUS
------------------------------