optional arguments originate from. These seem equally possible:
1. client app developers automatically include them as optional form inputs for
all service requests (as per the spec)
2. they are included based on the server-side Service Definition
For example, we'd like to make the email field a mandatory argument for a
particular service request. According to the v2 spec, email is an optional
argument of the POST service request.
If (1), how to tell the client app developer that the email argument is
mandatory for this particular service request?
If BOTH (1) and (2), how to ensure that the client app developer will use the
email argument from the Service Definition instead (to prevent there being 2
email inputs on the form)?
If only (2), the solution is obvious, but then the optional arguments seem like
What is the proper way to make this a mandatory argument without introducing
potential ambiguity to the user?
Sr. Java Developer
City of Toronto