dc.contributor.author |
Bouras, A |
en |
dc.contributor.author |
Gouvas, P |
en |
dc.contributor.author |
Kourtesis, D |
en |
dc.contributor.author |
Mentzas, G |
en |
dc.date.accessioned |
2014-03-01T01:27:14Z |
|
dc.date.available |
2014-03-01T01:27:14Z |
|
dc.date.issued |
2007 |
en |
dc.identifier.issn |
15715736 |
en |
dc.identifier.uri |
https://dspace.lib.ntua.gr/xmlui/handle/123456789/18356 |
|
dc.subject |
Business To Business |
en |
dc.subject |
Enterprise Application Integration |
en |
dc.subject |
meta model |
en |
dc.subject |
Semantic Integration |
en |
dc.subject |
Service Discovery |
en |
dc.title |
Semantic integration of business applications across collaborative value networks |
en |
heal.type |
journalArticle |
en |
heal.identifier.primary |
10.1007/978-0-387-73798-0_58 |
en |
heal.identifier.secondary |
http://dx.doi.org/10.1007/978-0-387-73798-0_58 |
en |
heal.publicationDate |
2007 |
en |
heal.abstract |
If we try to increase the level of automation in Business-to-Business (B2B) Enterprise Application Integration (EAI) scenarios, we confront challenges related to the resolution of data heterogeneities, service discovery and process composition. In this paper, we propose the Enterprise Interoperability Ontology (ENIO) that provides a shared, common understanding of data, services and processes within B2B integration scenarios. ENIO consists of an Upper Enterprise Interoperability Ontology (Upper ENIO), which is based on the DOLCESUMO alignment, with extensions called facets that cover several dimensions of the EAI domain. Each facet contains a relative meta-model that utilizes widely adopted standards. Finally, we demonstrate the utilization of ENIO in a real-world B2B scenario across a franchisor-franchisees collaborative value network. © 2007 Springer Science+Business Media, LLC. |
en |
heal.journalName |
IFIP International Federation for Information Processing |
en |
dc.identifier.doi |
10.1007/978-0-387-73798-0_58 |
en |
dc.identifier.volume |
243 |
en |
dc.identifier.spage |
539 |
en |
dc.identifier.epage |
546 |
en |