Lau Cheuk Lung, Joni da Silva Fraga, Jean-Marie Farines et al. · 2003
This paper describes the design and implementation of a fault-tolerant CORBA naming service-CosNaming FT. Every CORBA object is accessed through its Interoperable Object Reference (IOR), which is registered with the CORBA name service. The name service therefore is a critical gateway to all objects in a distributed system; to avoid having a single point of failure, the name service should be made fault-tolerant. CosNamingFT uses the GroupPac package, a CORBA-compliant suite of protocols, to replicate the name server. GroupPac services are built from Common Object Services that function as building blocks to implement fault-tolerant applications. This paper aims to demonstrate the usefulness of some of these object services and to demonstrate the importance of open solutions issues in replicating distributed objects.
Cited by 10
Rubén Peredo Valderrama, Alejandro Canales Cruz, Iván Peredo Valderrama · 2011
The Software Factory described in this paper is an organizational structure specialized in the pro-duction of educational materials based on software components according to educational specifi-cations and externally-defined by the end-users requirements (Learners, Tutors, University, In-structional Designers, etc.). The Software Factory applies manufacturing techniques and princi-ples of Domain Engineering to software development, to mimic the benefits of traditional manu-facturing. The software components obtained are called Intelligent Reusable Learning- Compo-nents Object Oriented (IRLCOO), which are a special type of Sharable Content Object (SCO) according to the Sharable Content Object Reference Model (SCORM). These software compo-nents consume Web Services (WS) to produce reusable and interoperable learning content.
Cited by 0
Group C. Daboo · 2009
This document specifies a protocol that uses the iCalendar object specification to provide scheduling interoperability between different calendaring systems. This is done without reference to a specific transport protocol so as to allow multiple methods of communication between systems. Subsequent documents will define profiles of this protocol that use specific, interoperable methods of communication between systems. The iCalendar Transport-Independent Interoperability Protocol (iTIP) complements the iCalendar object specification by adding semantics for group scheduling methods commonly available in current calendaring systems. These scheduling methods permit two or more calendaring systems to perform transactions such as publishing, scheduling, rescheduling, responding to scheduling requests, negotiating changes, or canceling.
Cited by 0
Kimmo Raatikainen · International Journal on Wireless & Optical Communications · 2003
The Object Management Group has recently published the Wireless Access and Terminal Mobility in CORBA standard — Wireless CORBA for short. The specification enables mobility transparency of objects on a mobile terminal through a mobile Interoperable Object Reference (mobile IOR). A GIOP tunneling protocol is used to handle handoffs between access bridges even when the access technology changes. The current standard supports TCP, UDP, WAP WDP and Bluetooth L2CAP transports. The mobility management is based on principles of the current GSM network. The CORBA ORB is, however, only involved in handoffs between bridging domains, whereas mobility inside a bridging domain is handled by Mobile IP and/or link level mechanisms. The Wireless CORBA specification also provides the basic means to discover and resolve initial object references in the home and visited domains.
Cited by 24
Adrian Birka, Michael D. Ernst · ACM SIGPLAN Notices · 2004
This paper describes a type system that is capable of expressing and enforcing immutability constraints. The specific constraint expressed is that the abstract state of the object to which an immutable reference refers cannot be modified using that reference. The abstract state is (part of) the transitively reachable state: that is, the state of the object and all state reachable from it by following references. The type system permits explicitly excluding fields or objects from the abstract state of an object. For a statically type-safe language, the type system guarantees reference immutability. If the language is extended with immutability downcasts, then run-time checks enforce the reference immutability constraints. In order to better understand the usability and efficacy of the type system, we have implemented an extension to Java, called Javari, that includes all the features of our type system. Javari is interoperable with Java and existing JVMs. It can be viewed as a proposal for the semantics of the Java const keyword, though Javari's syntax uses readonly instead. This paper describes the design and implementation of Javari, including the type-checking rules for the language. This paper also discusses experience with 160,000 lines of Javari code. Javari was easy to use and provided a number of benefits, including detecting errors in well-tested code.
Cited by 11
Mohamed Taha Bennani · 2008
Abstract: The Object Management Group (OMG) extends standard CORBA specification to handle fault tolerance mechanisms. This extension led to the definition of a new standard: FT-CORBA, which introduces new concepts like IOGR (Interoperable Object Group Reference), and offers new programmable interfaces. The introduction of the IOGR limits the interactions with the legacy applications. Moreover, the definition of new interfaces forces developers to deal with the specification of the fault tolerant mechanisms, which could not be in their capabilities. The standard CORBA reflexive mechanisms may offer lightweight fault tolerance in a transparent way, portable and doesn’t alter the legacy applications. In this paper, we present the limits of these mechanisms, and how could we improve the fault tolerant features of the CORBA middleware using standard reflexive mechanisms like Portable Request Interceptors (PIs).
Cited by 0
Maryam Ahmadi, Shahla Foozonkhah, Arezoo Dehghani Mahmoodabadi · Eastern Mediterranean Health Journal · 2016
The present descriptive-comparative study was conducted to give an overview of the messaging standards that are necessary for interoperable electronic health records (EHRs). We designed a preliminary model after data collection and compared the messaging standards of Health Level Seven (HL7) and the International Organization for Standardization (ISO). The data were assessed with the Delphi technique. A comprehensive model for the messaging standards of EHRs in the Islamic Republic of Iran was presented in three pivots: structural characteristics (standard for all EHRs, XML-based and object-oriented messages, and dual model); model specifications (reference model, archetypes and classes of reference model), and general features (distinct ontology, mapping with other standards, and using reference archetypes for exchanging documents). In conclusion, we gave an overview of messaging standards for the interoperability of EHRs and experts selected ISO13606 as a suitable standard for the Islamic Republic of Iran.
Cited by 6Open access
A. Chitra, G. Sudha Sadasivam · Journal of Integrated Design and Process Science · 2003
The distributed object standards Component Object Model (COM) and Common Object Request Broker Architecture (CORBA) apply object technology to design and use software components. While COM forms a good front end for the Microsoft Systems, CORBA is well suited for middle tier and back end Unix servers. By integrating them, the user can get a combination of the best attributes of both the systems. Bridging software is needed to transparently couple components from both the systems. This paper discusses a static method of achieving COM/CORBA interworking using a generic IDL compiler. It maps the COM and CORBA IDLs onto an intermediate representation from which stubs and skeletons are generated. Further, threading is used to allow multiple COM clients to contact a single CORBA server using Internet Interoperable Protocol / Transmission Control Protocol (IIOP/TCP) as a communication medium. To improve the networking speed and to bring about multicasting, IIOP/UDP has also been tried as a communication medium. The Object Reference (OR) from the implementation repository (IMR) and the Object Identifier (OID) from the registry have also been cached to improve the speed of the name lookup mechanism.
Cited by 0
Njogu Njuguna, Adam E. Flanders, Charles E. Kahn · Radiographics · 2011
Computer-based learning, or "e-learning," plays an increasingly important role in healthcare education. Modular, standardized approaches to e-learning make learning content portable, reusable, and interoperable. The Shareable Content Object Reference Model (SCORM) is a standard for educational content that builds upon existing standards for e-learning. The "SCORM for Healthcare" model, which is designed to meet the particular needs of learning in health professions, is being developed to improve communication of educational needs, goals, and competencies among healthcare workers, educational providers, and certifying organizations. Radiologists can benefit from SCORM by becoming familiar with its features and the opportunities it affords to improve online learning.
Cited by 16
Bruce W. Herr, Josef Hardi, Ellen M. Quardokus et al. · Scientific Data · 2023
The Human Reference Atlas (HRA) is defined as a comprehensive, three-dimensional (3D) atlas of all the cells in the healthy human body. It is compiled by an international team of experts who develop standard terminologies that they link to 3D reference objects, describing anatomical structures. The third HRA release (v1.2) covers spatial reference data and ontology annotations for 26 organs. Experts access the HRA annotations via spreadsheets and view reference object models in 3D editing tools. This paper introduces the Common Coordinate Framework (CCF) Ontology v2.0.1 that interlinks specimen, biological structure, and spatial data, together with the CCF API that makes the HRA programmatically accessible and interoperable with Linked Open Data (LOD). We detail how real-world user needs and experimental data guide CCF Ontology design and implementation, present CCF Ontology classes and properties together with exemplary usage, and report on validation methods. The CCF Ontology graph database and API are used in the HuBMAP portal, HRA Organ Gallery, and other applications that support data queries across multiple, heterogeneous sources.
Cited by 16Open access
François Lévesque · 2007
Syntax Notation One ATM : Asynchronous Transfer Mode CMI : Common Management Information CMIP : Common Management Information Protocol CMIS : Common Management Information Services CMISE : Common Management Information Service Element CORBA : Common Object Request Broker Architecture COM : Component Object Model DCE : Distributed Computing Environment DCOM : Distributed ComponentObjectModel DHCP : Dynamic Host Con guration Protocol DII : Dynamic Invocation Interface DMI : Desktop Management Interface 149 DMTF : Desktop Management Task Force DSI : Dynamic Squeleton Interface EDF : Earliest Deadline First FIFO : First In First Out GDMO : Guidelines for the Description of Managed Objects GIOP : General Inter-ORB Protocol IANA : Internet Assigned Number Authority IDL : Interface De nition Language IETF : Internet Engineering Task Force IIOP : Internet Inter-ORB Protocol ILP : Integrated Layer Processing IOR : Interoperable Object Reference IP : Internet Protocol IrDA : Infra Red Dat Association ISO : International Standards Organization ITU : International Telecommunication Union JIDM : JointInter-Domain Management LDAP : Lightweight Directory Access Protocol MIB : Management Information Base MIDL : Microsoft IDL MFL : Maximum Laxity First MIF : Management Interface Format MMTF : Mobile Management Task Force MUF : Maximum Urgency First NTP : Network Time Protocol OMA : Object ManagementArchitecture OMG : Object Management Group 150 ORB : Object Request Broker ORPC : Object RPC OSI : Open Systems Interconnection POA : Portable Object Adapter RDP : Resource Discovery Protocol RFP : Request For Proposal RIOP : Real-time Inter-ORB Protocol RMI : Remote Method Invocation RMON : Remote Network Monitoring RMS : Rate Monotonic Sc...
Cited by 0
Abigail Ball · Radar (Oxford Brookes University)
SCORMSCORM stands for Shareable Content Object Reference Model and is a set of specifications for developing, packaging and delivering training content whenever and wherever they are needed.SCORM compliance makes sure that the resources are reusable, accessible, interoperable and durable.Examples of SCORM compliant software include Hot Potatoes, Camtasia, Adobe Captivate, Flash and Dreamweaver.Tutors sometimes create content in one of these packages and import them into a Moodle course for you to use.After the SCORM content is imported into Moodle, it is referred to as a SCORM package.SCORM packages display much like Moodle books with a table of contents and previous and next icons for navigation.They can be launched directly from Moodle without requiring any additional software to run them.
Cited by 0Open access
Seung Hee Kim, Yoo Kyung Boo, Yoon Kim · Journal of Korean Society of Medical Informatics · 2007
Objective: A reference terminology is essential to achieve semantic interoperability and enhance the quality of health care. Reference terminologies that have achieved common acceptance contain many concepts that clinicians would not want in healthcare, which preclude their practical use in documentation of patient information. To solve the problems, this document proposes a reference terminology model which contains concepts that physicians can use satisfactorily. Methods: We analyzed the structures of the UMLS and SNOMED CT. We also analyzed health care terms which had been collected by the Korea National Health Information Standard Committee. Based on the results of the analysis, we developed an object-oriented reference terminology model. And, we designed database schema with the model. Results: Eight components of the UMLS and six components of the SNOMED CT were analyzed. The collected terms had various properties and mapping vocabularies according to the characteristics of their respective domains. A reference terminology model was developed from a three-level view using UML. A database schema was developed using ERD. Conclusion: This study mainly focuses on reference terminology modeling. It is hoped that this reference terminology modeling helps the semantic interoperable exchange of clinical documents as the basis of common EMR. (Journal of Korean Society of Medical Informatics 13-2, 83-89, 2007)
Cited by 0
Michael J. O’Connor, Dennis L. Jones, James Gerding et al. · 2001
Abstract : Since the inception of HLA, there has been much discussion on how to create interoperable federates. Much of the early HLA work focused on creating new federations starting from scratch. In practice, this is rarely the case. Creating a federation is a labor- and money-intensive process. This paper discusses the approach used to create a new federation using existing federates with different FOMs. Our approach draws on the work performed by the Simulation Interoperability Standards Organization (SISO) Reference FOM Study Group and the SISO's ongoing Base Object Models Study Group. Under DTRA sponsorship, ITT and Litton/TASC created a new federation and resulting FOM using the Nuclear, Chemical, Biological, and Radiological Environment Server (NCBR) and Ocean, Atmosphere, and Space Environmental Services (OASES meteorological server). The NCBR and OASES use the SISO Real-time Platform Reference and DMSO's EnviroFed FOMs, respectively. The merged FOM allows the NCBR and OASES to maintain their current level of interoperability with other federates while adding the new capability.
Cited by 2
2010
This document specifies a protocol that uses the iCalendar object specification to provide scheduling interoperability between different calendaring systems. This is done without reference to a specific transport protocol so as to allow multiple methods of communication between systems. Subsequent documents will define profiles of this protocol that use specific, interoperable methods of communication between systems. The iCalendar Transport-Independent Interoperability Protocol (iTIP) complements the iCalendar object specification by adding semantics for group scheduling methods commonly available in current calendaring systems. These scheduling methods permit two or more calendaring systems to perform transactions such as publishing, scheduling, rescheduling, responding to scheduling requests, negotiating changes, or canceling. Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the
Cited by 0
Nikita Konshin, Marta G. Valverde, Danila Solodennikov et al. · Materials Today Bio · 2025
We present a large-scale, standardized image dataset and analysis pipeline designed to enable in silico discovery of cell-material interactions. This resource paper introduces an open, FAIR-aligned framework for acquiring, curating, and analyzing high-content imaging data of kidney podocytes cultured on 2176 micro-topographical surfaces using the TopoChip platform. Our workflow includes automated imaging, tilt correction, object segmentation, and multi-tiered quality control, resulting in over 5500 morphological features for >1.2 million cells. Structured metadata, standardized file architectures, and ontological annotations ensure that the dataset is fully interoperable and ready for reuse. To illustrate its versatility, we provide examples of how this resource supports machine learning model development, reproducible benchmarking, and hypothesis testing in cell biology and biomaterials science. This dataset and accompanying tools are designed as a foundational reference for the community, enabling scalable, quantitative, and reproducible exploration of how microenvironments shape cell behavior.
Cited by 1Open access
Philip W. L. Fong, C○philip W. L. Fong, Philip W. L. Fong · 2005
Confined types enforce a form of encapsulation stronger than what the standard Java type system offers. It is known that confined types effectively prevent accidental reference leaks that could lead to security breaches in object-oriented programs. Because existing formulations of confined types target the Java source language, they can only be enforced by the code producer at compile time. As such these formulations fail to qualify as practical languagebased protection mechanisms for the Java platform. This paper presents a capability-based formulation of confined types for JVM bytecode, and reports the first implementation to enforce confined types at link time, on the code consumer side. This novel formulation of confined types is backward compatible, modular, and interoperable with lazy dynamic linking. The paper also demonstrates how this bytecode-level formulation of confined types can be applied to facilitate a form of secure cooperation between mutually suspicious code units. 1
Cited by 0
Florian Thiery · Zenodo (CERN European Organization for Nuclear Research) · 2026
The Federated Knowledge Graph Ecosystem enables interoperable, distributed access to research knowledge by connecting RDF triplestores, community-curated knowledge bases, and shared semantic standards. However, many research outputs of high practical relevance—such as software, analytical workflows, images, or 3D data—remain difficult to integrate into such ecosystems, as they are typically distributed as binary artefacts outside the RDF world. FAIR Digital Objects (FDOs) address this gap by encapsulating digital artefacts together with metadata and identifiers in a machine-actionable form, but concrete, executable reference implementations remain scarce. This paper presents a minimal, standards-based method and software reference implementation that operationalises core FDO concepts using lightweight metadata packaging and semantic crosswalks. Starting from a self-contained ZIP archive containing binary content together with CITATION.cff and MD.cff metadata, the approach generates an RDF representation that exposes object structure, file-level distributions, and provenance information. The resulting RDF output can be ingested into triplestores and queried via SPARQL, enabling binary research artefacts to participate as first-class entities in Federated Knowledge Graph Ecosystems. The implementation is intentionally scoped as a pragmatic entry point, demonstrating how FAIR Digital Objects can be made actionable using existing standards and tooling.
Cited by 0Open access
Florian Thiery · Zenodo (CERN European Organization for Nuclear Research) · 2026
The Federated Knowledge Graph Ecosystem enables interoperable, distributed access to research knowledge by connecting RDF triplestores, community-curated knowledge bases, and shared semantic standards. However, many research outputs of high practical relevance—such as software, analytical workflows, images, or 3D data—remain difficult to integrate into such ecosystems, as they are typically distributed as binary artefacts outside the RDF world. FAIR Digital Objects (FDOs) address this gap by encapsulating digital artefacts together with metadata and identifiers in a machine-actionable form, but concrete, executable reference implementations remain scarce. This paper presents a minimal, standards-based method and software reference implementation that operationalises core FDO concepts using lightweight metadata packaging and semantic crosswalks. Starting from a self-contained ZIP archive containing binary content together with CITATION.cff and MD.cff metadata, the approach generates an RDF representation that exposes object structure, file-level distributions, and provenance information. The resulting RDF output can be ingested into triplestores and queried via SPARQL, enabling binary research artefacts to participate as first-class entities in Federated Knowledge Graph Ecosystems. The implementation is intentionally scoped as a pragmatic entry point, demonstrating how FAIR Digital Objects can be made actionable using existing standards and tooling.
Cited by 0Open access
Björn Möller, Alfredo Garro, Alberto Falcone et al. · NASA STI Repository (National Aeronautics and Space Administration) · 2016
Distributed and Real-Time Simulation plays a key-role in the Space domain being exploited for missions and systems analysis and engineering as well as for crew training and operational support. One of the most popular standards is the 1516-2010 IEEE Standard for Modeling and Simulation (M&S) High Level Architecture (HLA). HLA supports the implementation of distributed simulations (called Federations) in which a set of simulation entities (called Federates) can interact using a Run-Time Infrastructure (RTI). In a given Federation, a Federate can publish and/or subscribes objects and interactions on the RTI only in accordance with their structures as defined in a FOM (Federation Object Model). Currently, the Space domain is characterized by a set of incompatible FOMs that, although meet the specific needs of different organizations and projects, increases the long-term cost for interoperability. In this context, the availability of a reference FOM for the Space domain will enable the development of interoperable HLA-based simulators for related joint projects and collaborations among worldwide organizations involved in the Space domain (e.g. NASA, ESA, Roscosmos, and JAXA). The paper presents a first set of results achieved by a SISO standardization effort that aims at providing a Space Reference FOM for international collaboration on Space systems simulations.
Cited by 23Open access