Model modeling interoperability

As stated on the OMG (Object Management) website (http //www.omg. org/), a lack of data standards results in data conversions, loss of information, lack of interoperability, etc. Current standards du jour are XML (Extensible Markup Language) [17], LSID (Life Sciences Identifiers), and now the RDF (Resource Description Framework) from the W3C (World Wide Web Consortium), which is extensible though hard to implement. Substantial work on OO (Object Oriented) modeling of life science data types takes place at the OMG s LSR (Life Sciences Research) group—this is discussed below. 

The model developer who wants to couple the models (1) has to include coupler-specific interfaces in the models, and (2) has to provide the model and coupling meta-data according to standards of the coupling software. Both tasks can be time consuming, and the gain of interoperability has to be balanced against the costs of the implementation. 

Model interfaces include many aspects of the interoperability of NWP/MM and ACTM models. Modular coding is advocated in order to ease implementation of different algorithms/routines serving the same purpose. Ensuring common standards for data exchange are also important. 

Irototyping is building an initial physical, functioning model of your innovation. As such, it helps you verify the design of the super-system—say, a bicycle—as well as the interoperability of the subsystems—the drive train, gears, brakes, tires, and so on. A prototype also tests the robustness of your design and its sensitivity to uncontrollable factors. Additionally, prototyping helps you verify that the required resources and processes are available to support full-scale production or delivery of your innovation. 

Expanding Process Modelling Capability through Software Interoperability Standards Application, Extension and Maintenance of CAPE OPEN standards... 

CAPE OPEN standards have been developed to the state of maturity where standards are finding application in industrial and academic applications. The need for further standards has been identified as well as sustaining existing standards. To be successful standards also need to be maintained and supported. Developments in applying, extending and maintaining software interoperability standards to expand Process Modelling Capability will be presented. 

Because there are different aspects to interoperability standards and because there has been standardization interest in this area for over a decade, the result is a plethora of APIs, data formats, and standards bodies targeted at a number of technologies, including C, Java, CORBA, XML, and SOAP. The more recent interest in modeling and standardizing business-to-business processes has made the situation even more confusing, with considerable debate around the overlap between workflow and business processes and whether the pre-existing workflow standards are even appropriate for peer-to-peer business processes [WS6]. 

True interoperability will not be just a simple sharing of data and models. There must be a rigorous standardization to prevent misapplication of modeling results. Models and simulations at different scales must be correctly integrated. New scaling laws and rules will be required to translate model prediction at the nanoscale to the micro-, the meso- (or middle scale), and ultimately the macroscale. Numerical algorithms must be carefully documented to assure that issues of time steps, grids, and boundary conditions are appropriately applied for uses with other models and simulations experiments and projects. 

The archive is important because it provides context for work—not merely a way of getting at a particular known piece of work. Libraries provide that context by bringing together the patchwork of various pubUshers and models, and then deal with the frustrations of trying to piece it all together. Libraries work toward a grand vision of a richer and more interoperable context. Gold said. 

While IP ownership is an essential driver of innovation, technological advances are often dependent on shared knowledge, standards, and collaborative innovation. The IP framework must enable both. We must protect truly new, novel, and useful inventions. And we need to recognize that open standards can accelerate the interoperability and expansion of the global infrastructure. Because collaborative innovation is relatively new, the stmcture and processes to accommodate ownership, openness, and access are evolving, and new creative models are emerging. 

Towards an Integrated SOA-based Architecture for Interoperable and Responsive Manufacturing Systems Using the ISA-95 Object Model... 

The rest of this paper is organized as follows. Section 2 presents our approach to Verilog-VHDL interoperability around a Hierarchical Finite State Machine semantic model. Section 3 defines a common interpretation in that model for a RTL subset of Verilog and VHDL, the emphasis being on the illustration of the approach taken rather than on a complete formal derivation, which would exceed the space of this paper. Section 4 presents an implementation of a translator from SMP to Blif-mv, the intermediate formats for the semantic model in the Prevail and VIS systems, enabling formal verification of VHDL-Verilog equivalence in the VIS environment... 

SYNCHRONOUS DESIGNS INTEROPERABILITY THROUGH THE HFSM MODEL... 

---