interoperation
Martin H. Weik · 2000
Cited by 1
Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 1,920 papers for “Interoperation”
Martin H. Weik · 2000
Cited by 1
George Hatzisymeon, Nikos Houssos, Dimitris Andreadis et al. · 2008
Cited by 0
2007
Cited by 0
Johannes Sametinger · 2007
A variety of component types can be reused. Yet different composition techniques and different forms of interoperation of components make reuse difficult or impossible in many situations. We briefly introduce components and component composition. Then we describe forms of interoperation. We propose a classification by introducing an interoperation matrix where we consider control and data aspects of interoperation and distinguish among sixteen different forms of interoperation. Keywords: software components, software composition, software interoperation, component taxonomy, software reuse Workshop Goals: discussion/definition of component/composition/interoperation Working Groups: component certification tools, frameworks and processes; domain engineering tools 1 Background The author's main research interests include software engineering, software maintenance, software documentation, object-oriented programming, component-oriented programming, and software reuse. Results in the a...
Cited by 0
2006
Cited by 0
Jan Frederic Jannink · 2000
Cited by 0
Lv Y(吕勇), Yu HB(于海斌), Wang TR(王天然) et al. · SIA OpenIR (Chinese Academy of Sciences) · 2004
This paper discusses several interoperation technologies in fieldbus systems. Based on studying of several popular fieldbus standards, analyzed the key technologies of interoperation between homogeneous protocols: standardized application layer logic structure and device description. In order to fit different fieldbus interoperation demand between heterogeneous protocols, two types of gateways are classified: protocol-conversion-type gateway and bridge-type gateway. Their principles, characteristics, application areas and development steps are analyzed as well. With the introduction of OPC technologies, elaborates the methods to realize interoperation between multi-protocols. The limitations are also analyzed in detail and some solutions are also provided to overcome their limitations.
Cited by 0
Xiaolei Qian, Louiqa Raschid · 1995
We develop an efficient algorithm for the query interoperation among existing heterogeneous object-oriented and relational databases. Our algorithm utilizes a canonical deductive database as a uniform representation of object schema and data. High-order object queries are transformed to the canonical deductive database in which they are partially evaluated and optimized, before being translated to relational queries. Our algorithm can be incorporated into object-oriented interfaces to relational databases or object-oriented federated databases to support object queries to heterogeneous relational databases.
Cited by 0
Frank‐Walter Jaekel, Yves Ducq · 2012
The following topics were discussed to approach the topic Enterprise Interoperation Management (EIM): The overview presentation “Industry Needs and Potentials of EIM” is focused on a strategic perspective of how enterprise interoperability effects an organization with a specific viewpoint on production and how enterprise interoperability management can help. The presentation “EIM from a Research Perspective” describes an operational perspective of Enterprise interoperability between organizations and how the interoperability aspects should be managed from a research perspective as well as from analyzed industrial needs. The paper “Business Intelligence and Enterprise Interoperability: Literature Review” is a literature review that illustrates the interoperability requirements as well as a wide range of islands of interoperability in organizations. Finally, the presentation “Enterprise Interoperability Management and Standardization” shows an overview of standards in the area of interoperability as well as the current approaches regarding enterprise interoperability frameworks. Controlled Vocabulary Terms business communication; interoperability
Cited by 0
Apress eBooks · 2007
In this chapter, you will look at everything you need to make F# interoperate well with other languages, not just within the .NET Framework but also using unmanaged code from F# and using F# from unmanaged code.
Cited by 0
Wernher Behrendt, N. J. Fiddian, William A. Gray et al. · Lecture notes in computer science · 1998
Cited by 0
Soma Bandyopadhyay, P. Balamuralidhar, Arpan Pal · Journal of ICT Standardization · 2013
River Publishers - In the few years since our launch, River Publishers has managed to establish an excellent reputation amongst academics and professionals world-wide as a provider of high quality Scientific, Technical, Medical content! We are a global publisher of print and electronic products and we welcome all persons with publishing ideas which focus on scientific topics.
Cited by 28Open access
Robert Pickering, Kit Eason · Apress eBooks · 2016
In this chapter, you will look at everything you need to make F interoperate well with other languages, not just within the .NET Framework but also using unmanaged code from F# and using F# from unmanaged code.
Cited by 0
Yi Zhao, Xia Wang, Wolfgang A. Halang · IGI Global eBooks · 2009
With the increasing interest in Semantic Web-based applications, researchers have started to build tools enabling organisations to share information. An important aspect in maintaining the Semantic Web is, however, to preserve security during semantic interoperation of different entities. Security and privacy are indispensable to the success of Semantic Web services. Hence, this chapter aims to investigate the currently used security methods in semantic interoperation, including the security methods employing Semantic Web representation languages such as XML, RDF and ontologies, and their application methods in semantic interoperation such as secure access control and secure knowledge management. How to manage privacy, trust and reputation at the same time during semantic interoperation will also be discussed in this chapter. Finally, some directions for our further research will be presented.
Cited by 0
Gio Wiederhold · 1994
In this paper we address the problem of interoperation at a semantic level. We assume that emerging standards will solve most of the syntactic infrastructure problems that exist today. However, interoperation has to deal with sources from differing domains, and their semantic differences. We present mediation as the principal means to resolve problems of semantic interoperation. Since the number of domains is large we cannot foresee a global solution to that problem, and hence will have to deal with domain interaction incrementally, and bring domains together as and when needed. To formalize the processing in mediation we will need formal models of the source domains, of the articulation points, and of the customer needs. We expect to capture these models using tools developed in the ARPA knowledge-sharing projects. The basis for these models are domain ontologies. We propose a knowledge-based algebra to manage the interoperation of information from different domains. Several research ...
Cited by 0
Peter D. Karp · Journal of Computational Biology · 1995
To realize the full potential of biological databases (DBs) requires more than the interactive, hypertext flavor of database interoperation that is now so popular in the bioinformatics community. Interoperation based on declarative queries to multiple network-accessible databases will support analyses and investigations that are orders of magnitude faster and more powerful than what can be accomplished through interactive navigation. I present a vision of the capabilities that a query-based interoperation infrastructure should provide, and identify assumptions underlying, and requirements of, this vision. I then propose an architecture for query-based interoperation that includes a number of novel components of an information infrastructure for molecular biology. These components include a knowledge base that describes relationships among the conceptualizations used in different biological databases, a module that can determine the DBs that are relevant to a particular query, a module that can translate a query and its results from one conceptualization to another, a collection of DB drivers that provide uniform physical access to different database management systems, a suite of translators that can interconvert among different database schema languages, and a database that describes the network location and access methods for biological databases. A number of the components are translators that bridge the heterogeneities that exist between biological DBs at several different levels, including the conceptual level, the data model, the query language, and data formats.
Cited by 107
Haitham S. Al-Sinani, Chris J. Mitchell · Royal Holloway Digital Repository (University of London) · 2011
Whilst the growing number of identity management systems have the potential to reduce the threat of identity attacks, major deployment problems remain because of the lack of interoperability between such systems. In this paper we propose a simple, novel scheme to provide interoperability between two of the most widely discussed identity systems, namely CardSpace and Shibboleth. In this scheme, CardSpace users are able to obtain an assertion token from a Shibboleth-enabled identity provider that can be processed by a CardSpace-enabled relying party. We specify the operation of the scheme and also describe an implementation of a proof-of-concept prototype. Additionally, security and operational analyses are provided.
Cited by 2
Xiaolei Qian, Li Gong, R. A. Riemenschneider · 1995
Cited by 6
Haitham S. Al-Sinani, Chris J. Mitchell · 2011
Cited by 11
Altmann, Udo · German Medical Science (German Research Foundation) · 2009
Einleitung: Tumordokumentation in klinischen Krebsregistern ist interdisziplinär, sektor- und einrichtungsübergreifend und umfaßt den gesamten Krankheitsverlauf. Ein klinisches Arbeitsplatzsystem im Rahmen eines Krankenhausinformationssystems oder eines Arztpraxissystems kann grundsätzlich[for full text, please go to the a.m. URL]
Cited by 0Open access