Proceedings of the 8th International Conference on New Technologies in Distributed Systems - NOTERE '08 2008
DOI: 10.1145/1416729.1416780
|View full text |Cite
|
Sign up to set email alerts
|

Development of semantic web services

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2010
2010
2021
2021

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 17 publications
(5 citation statements)
references
References 7 publications
0
5
0
Order By: Relevance
“…The SWS was described using the UML and formatted profiles based on the ontology definition metamodel (ODM) in Lautenbacher and Bauer 21 to match the WSMO, OWL-S, WSDL-S, and SWSF. Due to the UML static structure, UML modeling capabilities were expanded in Bensaber et al 22 through stereotypes, custom data types, and extension values to model various structures in the OWL-S. However, in this approach, logical expressions, preconditions/postconditions, and effects were greatly distorted from UML to OWL-S.…”
Section: Related Workmentioning
confidence: 99%
“…The SWS was described using the UML and formatted profiles based on the ontology definition metamodel (ODM) in Lautenbacher and Bauer 21 to match the WSMO, OWL-S, WSDL-S, and SWSF. Due to the UML static structure, UML modeling capabilities were expanded in Bensaber et al 22 through stereotypes, custom data types, and extension values to model various structures in the OWL-S. However, in this approach, logical expressions, preconditions/postconditions, and effects were greatly distorted from UML to OWL-S.…”
Section: Related Workmentioning
confidence: 99%
“…The authors characterize the behaviour of WS operations through an activity diagram [12]. They import Web Service Description Language (WSDL) descriptions to UML and then obtain OWL-S from UML; this benefits service developers, who otherwise have to write a lot of low level code.…”
Section: Software Process Framework For Swasmentioning
confidence: 99%
“…The main advantages of the MDA approach are portability, interoperability, reusability and technology independence, acting on the architectural concepts of separation between specification and implementation of the software [3]. Thus, software engineers have no longer need to worry about programming language or runtime platform.…”
Section: Figure 2: Mda's Pim and Psmmentioning
confidence: 99%