2010
DOI: 10.1007/978-3-642-16438-5_30
|View full text |Cite
|
Sign up to set email alerts
|

Ontology Learning for Cost-Effective Large-Scale Semantic Annotation of Web Service Interfaces

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0

Year Published

2010
2010
2015
2015

Publication Types

Select...
3
3

Relationship

4
2

Authors

Journals

citations
Cited by 14 publications
(14 citation statements)
references
References 9 publications
0
14
0
Order By: Relevance
“…In other words, when a given part/element name is assigned to an imprecise concept, then designated matching rules can not compensate this deficiency. In our work, accuracy of matching is mostly affected by performance of our ontology learning steps [6] which in turn, partially depends on the syntactic (e.g. spelling,…) and semantic (e.g.…”
Section: A Matching Resultsmentioning
confidence: 99%
See 3 more Smart Citations
“…In other words, when a given part/element name is assigned to an imprecise concept, then designated matching rules can not compensate this deficiency. In our work, accuracy of matching is mostly affected by performance of our ontology learning steps [6] which in turn, partially depends on the syntactic (e.g. spelling,…) and semantic (e.g.…”
Section: A Matching Resultsmentioning
confidence: 99%
“…For annotation of services in both datasets, we create two independent reference domain ontologies. While the first domain ontology is constructed manually by an ontology engineer, the second one is constructed automatically using our ontology learning mechanism [6]. We refer to the former and the latter respectively as the golden and the generated ontology.…”
Section: A Web Service Matching Evaluation Methodsmentioning
confidence: 99%
See 2 more Smart Citations
“…For newly introduced layers, we point out relevant sections in this paper while for some other layers references to our previous works are provided: A) Requirement Expansion Layer: It expands user requirement statement, specified in terms of available input and expected output parameters of services, with relevant concepts in order to increase service discovery efficiency. We obtain these terms and concepts from our pre-populated knowledge base which is built based on our ontology learning methodology [22]. The requirement expansion is performed according to the method proposed by Kungas and Dumas [11].…”
Section: Service Composition Architecturementioning
confidence: 99%