I agree with Corrinne. Option D is the way to go. Although, I have to say, the other options sound like they belong in a superhero technical service contract. 'Captain WSDL, assemble!'
Option D is definitely the winner. You can't just assume WSDL is the only way to define a service contract these days. There are so many options, gotta keep an open mind!
Hmm, I'm not so sure. I've seen components and HTTP methods used in service contracts too, depending on the technology. Maybe option D is the safest bet?
Cordie
3 days agoCorrinne
4 days agoSelma
7 days agoElfrieda
15 days agoAlyce
17 days agoJesus
19 days agoDesmond
22 days ago