OMG Object Management Group (2003) XML Metadata Interchange (XMI), Specification, Version 2.0. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Terminology Extraction Techniques for Improving Traceability.. - Cerbah, Euzenat (2000) (Correct)
.... of covering the complete Troeps model (thus it is possible to destroy or rename classes as well as adding new attributes to existing classes) Moreover, it is relatively standard in the definition of formalized knowledge so that it will be easy to have XTerm generating other formats (e.g. XMI [13] or Ontolingua) which share the notion of classes and objects. More details about this approach of XML based knowledge modeling and exchange are given in [9] 4 Related Work Terminology acquisition is one of the most robust language processing technology [4, 11, 7] and previous works have ....
OMG. XML Metadata Interchange (XMI). Technical report, OMG, 1998.
Information Technology for European Advancement - Software Development Process (Correct)
....4.3 DESS OPSS technology 4.3.1 Implementation of the translator UML process models can be written by means of any of the several available CASE tools supporting UML. It is clearly convenient to build a unique translator which is able to process the output of any modelling tool. Luckily, XMI [14] is emerging as the standard language for the textual representation of UML models. We therefore decided to build a translator which takes XMI (version 1.1. files as input. The general organization of the translator is depicted in Figure 29. The translation process is carried out in two steps. ....
OMG, XML Metadata Interchange (XMI) Specification, Version 1.1, November 2000, ftp://ftp.omg.org/pub/docs/formal/00-11-02.pdf.
The Specifications Exchange Service of an RM-ODP Framework - Blanc Gervais Le (2000) (Correct)
....of metamodeling techniques provided by the MOF standard [3] We first have defined an RM ODP meta model according to the MOF architecture. Together with this standard are provided associated techniques such as IDL interfaces generation. Moreover, the MOF standard interworks with the XMI standard [4]. Thus, XML files structures can be derived from a meta model. We gained by using these facilities in order to address the aspects related to the encoding of a specification. Therefore, the Backbone supports two different ways to encode a specification, respectively as a set of objects obtained ....
....the structure defined by a meta model. Thus, thanks to these interfaces, a model can be represented by objects. Moreover, the MOF standard interworks with the OMG s XMI standard that defines rules for generating the structure of XML documents reflecting the structure defined by a meta model [4]. The structure of an XML document is a DTD (Document Type Definition) Thanks to a DTD, a model can be represented by an XML document. Building the Backbone consists of implementing these services provided to the users as a mould. Actually, three moulds are built to realize the various services ....
OMG, XML Metadata Interchange (XMI) v1.0, October 1998 www.omg.org ad/98-10-05
XML-based Method and Tool for Handling Variant Requirements.. - Jarzabek, Zhang (2001) (1 citation) (Correct)
....conducted initial experiments to apply frames in domain models . Recently, we designed a variant configuration language, called XVCL [17] which implements essential frame concepts in XML. In this paper, we describe how we applied XVCL to handle variants in UML domain models represented as XMI [13] documents . We chose XMI, as modeling tools such as Rational Rose adopt XMI standards as a common, exchangeable representation for software models. In this solution, an FVC is an XVCL interpreter implemented on top of JAXP [15] an open framework for parsing XML documents . The reader should ....
....textual use case diagram as we have done on use case description. After customizations, we convert the text back to diagrams. To illustrate this technique, we use an XMI (XML Metadata Interchange) tool Unisys Rose XMI to convert the UML diagrams to equivalent textual representation in XML. XMI [13] is a new OMG standard that combines UML and XML and enables the exchange of UML models over the Internet. XMI supports the round trip transformation of UML models from diagrams to an XML file without loss of information. Figure 7 shows an x frame for Create Task use case diagram depicted in ....
OMG, XML Metadata Interchange (XMI) 1.1 RTF, OMG Document ad/99-10-02, 25 October 1999
XML Support to Design for Testability - Deveaux, Denis, Keller (2000) (1 citation) (Correct)
....central role in the construction of software design team support, particularly if it is associated to a WebDAV 8 application. Data interchange This facet has been explored mainly by the UML (Uni ed Modeling Language) community which has proposed several data interchange formats such as XMI [OMG98] Microsoft s XIF [Mic99b] and UXF 9 . The standardization of interchange formats in software engineering (SE EDI) is certainly necessary but we contend that these interchange documents cannot contain all the information required for validation or process control, unless all participants use ....
OMG. Xml metadata interchange (xmi. ftp://ftp.omg.org/pub/docs/ad/98-10-05.pdf, October 1998. Document ad/98-10-05.
Round-Trip Engineering of Ontologies for Knowledge-Based Systems - Knublauch, Rose (2000) (Correct)
....OCL [34] The intention of this language is to facilitate the specification of model properties in a formal, yet comprehensible way. OCL expressions can also be used to express the constraints imposed by the multiplicities of relationships. UML diagrams can be stored and distributed in the XMI [22] format. The left half of figure 2 shows the reflection of an abstract ontology view in a UML class model. Concepts from the ontology are represented as UML classes. These classes can be extended by additional members, which are not part of the ontology view. For example, domain ontology ....
OMG. XML Metadata Interchange (XMI). http://www. omg.org/cgi-bin/doc?ad/98-10-05, 1998.
XML Conceptual Modeling using UML - Conrad, Scheffner, Freytag (2000) (7 citations) (Correct)
....a more abstract view on document structures according to database modeling, or software engineering respectively. By conceptually modeling DTDs with UML, the focal point of our approach is the schema level. Our approach should not be confused with the XML Metadata Interchange (XMI) format [7]. The XMI describes the exchange format for UML class diagrams in an XML style. This way, XMI enables the exchange of schema information for cooperative work. However, our interest focuses on the development of DTDs by means of modeling of UML class diagrams and their mapping into XML DTDs. 4 ....
OMG. XML Metadata Interchange (XMI). Technical report, OMG, Oct 1998.
Distributed Collaborations using Network Mobile Agents - Tripathi, Ahmed, Kakani.. (2000) (3 citations) (Correct)
....corresponds to a process level description, and the agent based middleware is the execution infrastructure. Our work is fundamentally different from Wfmc [18] which is concerned with process descriptions for interoperability of workflow systems, and OMG s XMI (XML Meta Data Interchange)[8] which mainly focuses on data exchange related issues. Several general purpose systems have been developed for building collaboration environments using library modules and interfaces [10] However, in these systems coordination policies still need to be programmed using procedural languages. ....
OMG . XML Meta Data Interchange. http://www.omg.org.
Implementing Distributed Workflow Systems from XML.. - Tripathi, Ahmed.. (Correct)
....specifications indicate how the dependencies between activities should be managed in a workflow. In workflow design, a process language allows one to define the activities [18] 1] A number of groups have proposed process definition meta models. These include OMG s XMI (XML Meta Data Interchange)[12], UML [15] and Wfmc [24] process definition meta language. Moreover, workflow specification languages [23, 2, 13] are studied based on state and activity charts. State and activity charts can be easily incorporated into our XML schema. In our approach, the XML based plan description corresponds ....
OMG . XML Meta Data Interchange. http://www.omg.org.
A cognitively informed approach to describing product lines in.. - Gurr, Stevens (Correct)
....extreme caution is needed; in practice, people use those features of UML which are supported by their tool. Current tools generally implement only a subset of UML; but this is changing rapidly as the standard matures. The new XML Metadata Interchange format (XMI) an OMG standard in progress[OMG98] for UML in XML (among other benefits) enables tool developers to update their tools with respect to the latest version of the UML standard with less effort than would previously have been required. However, even if many tools will soon support the whole language, this does not imply that they ....
OMG. Xml metadata interchange (XMI). ftp://ftp.omg.org/pub/docs/ad/98-10-05.pdf, October 1998.
An XML-Based Interchange Format for Event-Driven Process.. - Mendling, Nüttgens (2005) Self-citation (Management) (Correct)
No context found.
OMG Object Management Group (2003) XML Metadata Interchange (XMI), Specification, Version 2.0.
EPC Markup Language (EPML) - Mendling, Nüttgens (2005) Self-citation (Management) (Correct)
No context found.
OMG Object Management Group (2003) XML Metadata Interchange (XMI), Specification, Version 2.0.
Exchanging Business Process Models with GXL - Winter, Simon (2004) Self-citation (Www Technology) (Correct)
No context found.
XML Meta Data Interchange (XMI) Specification. http://www.omg.org/ technology/documents/formal/xmi.htm. November 2000.
A Simulation-Based Approach to Software Performance - Simonetta Balsamo Universit (2003) (Correct)
No context found.
O. M. G. (OMG). XML Metadata Interchange (XMI) specification, version 1.2, Jan. 2002.
Model-driven SoC Design Via Executable UML to SystemC - Kathy Dang Nguyen (Correct)
No context found.
OMG. XML Metadata Interchange (XMI), version 1.0. ftp://ftp.omg.org/pub/docs/ad/98-10-05.pdf, 2004.
A Comparison of XML Interchange Formats for Business.. - Mendling, Neumann.. (2004) (3 citations) (Correct)
No context found.
OMG, ed.: XML Metadata Interchange (XMI). Version 2.0. Object Management Group. May 2003.
Towards a Data Consistency Modeling and Testing.. - Nytun, Jensen, Oleshchuk (2003) (Correct)
No context found.
OMG Editor. XML Metadata Interchange (XMI) Specification v1.2. OMG Document. OMG, http://www.omg.org, January 2002.
A Model-Driven Approach to - Non-Functional Analysis Of (2003) (Correct)
No context found.
OMG document formal/02-01-01. XML Metadata Interchange (XMI), version 1.2, 2002.
Realizing UML Metamodel Transformations with AGG - Büttner, Gogolla (2004) (Correct)
No context found.
XML Metadata Interchange (XMI) Specification, v1.2. Technical report, Object Management Group, March 2002.
Handling Variant Requirements in Domain Modeling - Stan Jarzabek Wai (2001) (2 citations) (Correct)
No context found.
OMG, XML Metadata Interchange (XMI) 1.1 RTF, OMG Document ad/99-10-02, 25 October 1999
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC