<p>I think we need to clearly distinguish between network protocols and communication specifications. In both the Internet domain and the Computers domain, several things are marked as protocol that have no business being protocols. As mentioned above HTTP is a specification for communication between two agents. The protocol used could be TCP, IP, UDP or some other such entity. Even SOAP for that matter is a specification which identifies the format of the message that is to be transported and states nothing about the actual transport engine itself.<br><br>
Another issue deals with the discussion <a href="">here</a> because several pieces of software that have their own communication specification are also typed as protocols, which IMO is incorrect. We need a different type for the same. </p>