A. Why SAWSDL?
For describing web services semantically three are different approaches are available namely WSML, OWL-S, USDL, WSDL-S. Among this all selection of SAWSDL  can be justified as follows. • Ontology Independence: As SAWSDL:modelReference does not need any specific ontology to add annotation.
- Standard Adaption: As compared to other techniques SAWSDL is just adding attributes to existing description method. It makes SAWSDL to be used only by extending existing tools for WSDL.
- Expressiveness: SAWSDL:modelRefrence can be used to add behavioral contracts like pre and post conditions as other techniques also do, but instead of different elements for each expression, SAWSDL describes all by one attribute only. It makes SAWSDL more simplified.
B. Why Cross Domain Ontology?
Web services are specifically designed to integrate resources from heterogeneous resources. Making domain specific ontology makes the discovery and composition restricted between know resources only. Also Design of domain specific Ontology need extra efforts while Cross Domain Ontology  can be taken as collection of different contributors.
C. Why Automation in annotation?
Web services are growing in millions of numbers and this growth is increasing. Creating manual annotation of this many web services may remain erroneous and tedious process. So it is required to develop some automated approach. Also Web Service discovery and composition process also needs to be deployed on the automated semantic annotation process.
Experiments here in this paper show that it is possible to create semantic web service description without much modification in existing standards like WSDL. As well as automating service annotation process makes it common in all descriptions. Though correction and accuracy rate of this approach is only satisfactory for the experimentation, automation and generalization creates basic platform for the dynamic discovery and automatic composition of the web services. Automation in this web service composition reduces human effort and errors. But this approach has limitation in creating liftingSchemaMapping and loweringSchemaMapping. As this both are provided in SAWSDL  but they need help of mediator services for converting from semantic type to syntactic type and vice versa. This automation of liftigSchemaMapping and loweringSchemaMapping as future work to be designed in to the data type mediators.