AGATE 1.1

Description : A metamodel of AGATE (Atelier de Gestion de l Architecture des Systemes d Information). AGATE is a framework for Information systems architecture management. This framework was designed by the french DGA (D?l?gation G?n?rale pour l?Armement in english General delegation for the Armament). The currently version is 3.0.

Amble 1.1

date : 2005/05/30

Domain : Distributed programs, Objective Caml library

Description : This metamodel describes Amble which is a distributed programming language based on Objective Caml. Amble enables to specify a distributed program in terms of processes that run concurrently. These processes are designed as states machines that are connected to each other by means of networks. Each network specifies a set of channels. The source process of a channel is allowed to write to its target process. An Amble program is composed of a single .ml file that includes the definition of the different process types that are involved in the program, as well as a set of .topo files (one for each considered network) that specifies the topology of the defined networks.

Ant 0.3

date : 2005/07/06

Domain : Building tool

Description : A metamodel describing Ant: Apache Ant is a Java-based build tool. It is similar to make, without make s wrinkles. It is configured with a build file that is an XML document. The build files are generally platform independent. It is extended using Java classes not scripts or shell-based commands. It can take care of archiving, compilation, execution, documentation, deployment, and much more.

AnyLogic 1.0

date : 2008/01/29

Domain : Simulation

Description : This metamodel describes simulation models for AnyLogic, a tool which is a simulation engine that can run simulations in order to analyze systems and provides visual representation of the running simulation.

AsmL 1.0

ATOM 1.0

date : 2005/11/01

Domain :

Description : This metamodel describes ATOM. Atom is an XML-based document format for the syndication of web content such as weblogs and news headlines, and an HTTP-based protocol for editing weblogs based on the format.

Finite Automaton 1.0

date : 2006/07/18

Domain :

Description : This metamodel describes a finite automaton. An automaton is a finite state input/output device. An automaton that as an initial state, (initialState), a set of available states (stateSet), a set of transitions (transitionSet), an alphabet, an a set of final states (finalStateSet).

AWKPrograms 1.0

date : 2005/08/09

Domain : programming language

Description : This metamodel describes programs in AWK which is a Unix utility designed for processing text based data, either in files or data streams. The name AWK is derived from the surnames of its authors - Alfred V. Aho, Peter J. Weinberger, and Brian W. Kernighan.

BibTeXML 1.2

date : 2006/07/05

Domain : bibliography, XML

Description : This is a metamodel of BibTeXML which is an XML-based format for the BibTeX bibliographic tool system for use with LaTeX. A bibliography is modelized by a BibTeX File element. This element is composed of BibTeX Entries which are each associated with an id. All entries inherit, directly or indirectly, of the abstract BibTeX Entry element. The abstract classes Authored Entry, Dated Entry, Titled Entry and Book Titled Entry, as well as the Misc entry, directly inherit of BibTeX Entry. There are 13 possible entry types: PhD Thesis, Master Thesis, Article, Tech Report, Unpublished, Manual, In Proceedings, Proceedings, Booklet, In Collection, Book, In Book and Misc. Concrete BibTeX entries inherits from some of these abstract classes according to their set of mandatory fields.

BibTeX 1.1

date : 2005/05/17

Domain : bibliography, XML

Description : This is a partial metamodel of BibTeXML which is an XML-based format for the BibTeX bibliographic tool system for use with LaTeX. A bibliography is modelized by a BibTeX File element. This element is composed of BibTeX Entries which are each associated with an id. All entries inherit, directly or indirectly, of the abstract BibTeX Entry element. The abstract classes Authored Entry, Dated Entry, Titled Entry and Book Titled Entry, as well as the Misc entry, directly inherit of BibTeX Entry. There are 13 possible entry types: PhD Thesis, Master Thesis, Article, Tech Report, Unpublished, Manual, In Proceedings, Proceedings, Booklet, In Collection, Book, In Book and Misc. Concrete BibTeX entries inherits from some of these abstract classes according to their set of mandatory fields. This metamodel only deals with the mandatory fields of each BibTeX entries (for instance, author, year, title and journal for an article entry). But it has been designed in such a way that it should be easily extensible to handle optional fields (with minor modifications).

Book 1.1

date : 2005/03/18

Domain : Bibliography

Description : In the simple metamodel Book, the class Book contains an ordered set of Chapters. Each Book has a title and a set of chapters. Each Chapter has a title and a number of pages. This very simple metamodel is mainly used for illustrative purposes.

BPEL 1.0

date : 2006/09/15

Domain : business process

Description : This metamodel was semi-automatically derived from the BPEL metamodel used by the Eclipse BPEL project (http://www.eclipse.org/bpel/), which uses the XSD (from http://www.eclipse.org/xsd/), and WSDL (from http://www.eclipse.org/webtools/) metamodels. Elements from XSD and WSDL are therefore included in the KM3 version. Moreover, some Ecore artefacts remain (see ecore package).

Bugzilla 1.1

date : 2005/07/07

Domain : Software bug tracking

Description : This metamodel describes the structure used by Bugzilla to import/export bugs in XML format. Bugzilla is a free Defect Tracking System or Bug-Tracking System which allows individual or groups of developers to keep track of outstanding bugs in their product effectively.

C 1.0

date : 2005/08/08

Domain : Programming language

Description : This metamodel describes C which is a standardized imperative computer programming language developed in the early 1970s by Ken Thompson and Dennis Ritchie for use on the UNIX operating system. It has since spread to many other operating systems, and is one of the most widely used programming languages. C is prized for its efficiency, and is the most popular programming language for writing system software, though it is also used for writing applications. It is also commonly used in computer science education, despite not being designed for novices. This simplified metamodel describes a subset of the C language.

CDE 1.0

date : 2005/08/10

Domain : Component modeling

Description : This metamodel describes a subset of the Component Description Model (CDE) which is a set of generic component-related UML extensions describing run-time (executable) components and their specifications. It is part of the Open Information Model (OIM) supplied with the Microsoft Repository. OIM is no more available since Microsoft stopped supporting it.

Class 1.1

date : 2005/03/18

Domain : Object-oriented programming

Description : This metamodel describes simple class schema models (OOP). It consists of classes having a name which they inherit from the abstract class NamedElt. The principal class is the class Class, which contains a set of attributes of the type Attribute and has the super references pointing to superclasses for modelling inheritance trees. The class DataType models primitive data types. Class and DataType inherit from Classifier which serves to declare the type of Attributes. Attributes can be multivalued.

CML 1.0

date : 2005/06/22

Domain : Chemical, XML

Description : This metamodel describes CML (Chemical Markup Language). It is based on the 1.0 DTD of CML. CML deliberately does not cover all chemistry but concentrates on molecules (discrete entities representatable by a formula and usually a connection table). It supports a hierarchy for compound molecules (clathrates, macromolecules, etc.). It also supports reactions, and macromolcular strucures/sequences (though it can interoperate with other macromolecular XML languages as they are developed). It has no specific support for physicochemical concepts, but can support labelled numeric datatypes of several sorts which can cover a wide range of requirements. It allows quantities and properties to be specifically attached to molecules, atoms or bonds.

COBOL 1.0

date : 2005/08/08

Domain : Programming language

Description : This metamodel describes COBOL (Common Business Oriented Language) which is a programming languages still used in business programming . It has been developed for building business, finance, and administrative systems for companies and governments in 1959 by a group of computer professionals called the Conference on Data Systems Languages (CODASYL).

CORBAComponent 1.0

Description : This metamodel describes a subset of CORBA (Common Object Request Broker Architecture) which is a standard for software componentry. The CORBA standard is created and controlled by the Object Management Group (OMG). It defines APIs, communication protocol, and object/service information models to enable heterogeneous applications written in various languages running on various platforms to interoperate. CORBA therefore provides platform and location transparency for sharing well-defined objects across a distributed computing platform.

CPL 1.0

date : 2006/01/18

Domain :

Description : This metamodel describes CPL (Call Processing Language). It is a standard scripting language for the SIP protocol. It offers a limited set of language constructs. CPL is supposed to be simple enough so that it is safe to execute untrusted scripts on public servers.

C++ 1.0

date : 2005/08/05

Domain : Programming language

Description : This metamodel simply describes C++ which is a general-purpose computer programming language. This is a statically typed language supporting procedural programming, data abstraction, object-oriented programming, and generic programming. During the 1990s, C++ became one of the most popular commercial programming languages. The C++ programming language standard was ratified in 1998 as ISO/IEC 14882:1998, the current version of which is the 2003 version, ISO/IEC 14882:2003.

CPR 1.0

date : 2005/08/10

Domain : Ontology

Description : This metamodel describes a subset of the Core Plan Representation (CPR) which is an effort to construct a general plan ontology. It has been developed to support the common plan representation of military planning, workflow and simulation. CPR is a DARPA project that mainly focuses on planning (specifying an action list in order to deal with a set of objectives) as well as on foreseeing (specifying moments at which activities will be realized and resource quantities will be used).

C# 1.0

date : 2005/08/08

Domain : Programming language, object-oriented programming

Description : This metamodel simply describes C# which is a simple, modern, object-oriented, and type-safe programming language that has its roots in the C family of languages. It has been developped by Microsoft. This simplified metamodel corresponds to a small subset of the language.

CSM 1.0

date : 2006/07/28

Domain :

Description : This metamodel describes CSM, that is a metamodel developed from the Real-Time and Distributed Systems Group at Carleton University to integrate performance annotations into software models.

CWMCore 1.0

date : 2005/08/10

Domain : Data Warehousing, MOF

Description : This metamodel describes a subset of the core of the Common WareHouse Metamodel (CWM) which is a specification that describes metadata interchange among data warehousing, business intelligence, knowledge management and portal technologies.

CWMRelationalData 1.0

date : 2005/08/10

Domain : Data Warehousing, MOF

Description : This metamodel describes a subset of the relational data part of the Common WareHouse Metamodel (CWM) which is a specification that describes metadata interchange among data warehousing, business intelligence, knowledge management and portal technologies.

System Definition Model DeploymentReport 0.1

date : 2005/07/05

Domain : DSI, SDM Deployment Report Metamodel, XML

Description : This metamodel corresponds to the Deployment Report metamodel of the Microsoft SDM (System Definition Model). It is derived from the XML Schema DeploymentReport.xsd which is the metamodel for describing the error messages that may occur during the deployment s simulation on a model (that conforms to the SDM metamodel) designed in Visual Studio 2005 Beta2.

DiagramInterchange 1.0

date : 2005/08/11

Domain : UML, Diagrams

Description : This metamodel describes a subset of Diagram Interchange which is an extension of the UML meta-model and is currently based on UML 2.0. The existing mechanism of XMI[UML] for exchanging models includes only the logical information but not the graphical presentation information. The diagram interchange extension allows graphical information to be included for diagrams used in UML models.

DocBook 1.1

date : 2005/05/17

Domain : Document composition, XML

Description : This metamodel describes a limited subset of DocBook, an XML-based format for document composition. Within this metamodel, a DocBook document is associated with a DocBook element. Such an element is composed of several Books that, in their turn, are composed of several Articles. An Article is composed of Sections that are ordered. A Section is composed of Paragraphs that are also ordered within each section. Both Article and Section inherit from the TitledElement abstract class.

DoDAF-SV4 0.1

date : 2006/06/26

Domain : Architecture Description, SoS (System of System)

Description : A Metamodel of DoDAF (Department of Defense Architecture Framework). This metamodel describes DoDAF SV4 (Structural View) Systems Functionalities Description. This part of DoDAF is used to represent system functional hierarchies and system functions.

DoDAF-SV5 0.1

date : 2006/06/26

Domain : Architecture Description, SoS (System of System)

Description : A Metamodel of DoDAF (Department of Defense Architecture Framework). This metamodel is a model for DoDAF SV5 (Structural View) Operational Activity to Systems Function Traceability Matrix. This DoDAF part is in correlation with OV5 and SV4 parts with the aim to provide a traceability matrix. This matrix has two axes. The first one represents the capabilities and operation activities from an OV5 model. The second one represents systems and their system functions. Each matrix elements represents the level of the relationship between Operational Activities and System Functions. They are three level: red means functionality planned but no developed, yellow means partial functionality provided or full but system has not been yet fielded, and green means full functionality provided and system has been fielded.

DSL 1.1

date : 2005/06/14

Domain : MDE

Description : This metamodel represents domain models (or metamodels in MDA) used by Microsoft DSL Tools (May 2005 CTP release for Visual Studio 2005 Beta 2). With DSL Tools you can create your own designer for a visual domain specific language that is represent by a domain model. The tools generate the code of a graphical editor for the language you defined in a domain model.

DSLModel 1

date : 2005/07/05

Domain : MDE, DSL models

Description : This metamodel represents DSL models used by Visual Studio DSL Tools to represent models for a domain model. Those models are stored in an xml file. This metamodel captures informations about the logic domain but not about the graphical representation.

DTD 1.0

date : 2005/06/20

Domain : XML

Description : This metamodel describes external DTD (Document Type Definition). The purpose of a DTD is to define the legal building blocks of an XML document. It defines the document structure with a list of legal elements. A DTD can be declared inline in your XML document, or as an external reference.

DXF 1.1

date : 2005/02/01

Domain : DataBase

Description : This metamodel describes geometrical data in DXF (Drawing eXchange Format) which is the native vector file format of Autodesk s AutoCAD CAD application. This simplified DXF metamodel has an aggregation hierarchy. It consists of one DXF element that contains a number of Meshes (a 3D object based on a set of contiguous lines) which in turn consist of a number of Points (two consecutive points represent a line). Meshes and Points have names. Points have three coordinates, namely x, y and z.

EAI 0.1

date : 2005/08/03

Domain : Programming paradigms

Description : This metamodel describes the structure of EAI (Enterprise Application Integration). The goal of EAI is the interoperability and the organization of the information flow between heterogeneous applications. An EAI project consists in setting up an architecture in which different applications communicate with one another. This has to do with developing connections (e.g. middleware) enabling the applications to interface, using different communication protocols. Nevertheless, EAI spans beyond interoperability between applications: it allows to define a workflow between applications and constitute therefore an alternative to the ERP with a more modular approach. It provides a metadata interchange standard for information about accessing application interfaces. The goal is to simplify application integration by standardizing application metadata for invoking and translating application information. The FCM composition model unifies the composition and coordination needs for factual or other styles. This model is at a higher abstraction level than the one of the flows of the messages, sources, targets, adapters and other operators.

ebXML 0.1

date : 2005/08/03

Domain : XML

Description : ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet. Using ebXML, companies now have a standard method to exchange business messages, conduct trading relationships, communicate data in common terms and define and register business processes. ebXML was started in 1999 as an initiative of OASIS and the United Nations/ECE agency CEFACT. The original project envisioned and delivered five layers of substantive data specification, including XML standards for: Business processes , Core data components, Collaboration protocol agreements, Messaging, Registries and repositories.

EclipsePlugIn 0.1

date : 2005/08/04

Domain : IDE

Description : This metamodel describes the structure of Eclipse plug-in. The Eclipse Platform is designed for building integrated development environments (IDE) that can be used to create applications as diverse as Web sites, embedded Java programs, C++ programs, and Enterprise JavaBeans. Although the Eclipse Platform has a lot of built-in functionality, most of that functionality is very generic. It takes additional tools to extend the Platform to work with new content types, to do new things with existing content types, and to focus the generic functionality on something specific. The Eclipse Platform is built on a mechanism for discovering, integrating, and running modules called plug-ins. A tool provider writes a tool as a separate plug-in that operates on files in the workspace and surfaces its tool-specific UI in the workbench. When the Platform is launched, the user is presented with an integrated development environment (IDE) composed of the set of available plug-ins. The quality of the user experience depends significantly on how well the tools integrate with the Platform and how well the various tools work with each other.

EQN 1.0

date : 2006/07/24

Domain :

Description : This metamodel describes EQN (Extended Queueing Network). It is an extension of QN (as LQN). EQN has been introduced in order to represent several interesting features of real systems, such as synchronization and concurrency constraints, finite capacity queues, memory and population constraints and simultaneous resource possession.

EXPRESS 0.1

date : 2007/09/28

Domain : Information Modeling Language

Description : This EXPRESS metamodel was created from the EXPRESS UML model RFC (http://www.omg.org/cgi-bin/doc?mantis/2007-09-02). The EXPRESS information modeling language is widely used in the scope of the ISO 10303 Standard for Exchange of Product Data (STEP).

Family 1.1

date : 2005/06/13

Domain : Family

Description : This basic metamodel allows to represent families. A family, which has a name, is composed of several persons identified by their firstname. Each person (member of a family) has a closest friend which is also a person. It can have several email addresses.

FeatureDiagrams 1.0

date : 2005/08/10

Domain : GME, domain-specific modeling

Description : This metamodel describes feature diagrams which are a part of the GME (Generic Modeling Environment). The Generic Modeling Environment is a configurable toolkit for creating domain-specific modeling and program synthesis environments. The configuration is accomplished through metamodels specifying the modeling paradigm (modeling language) of the application domain. The modeling paradigm contains all the syntactic, semantic, and presentation information regarding the domain; which concepts will be used to construct models, what relationships may exist among those concepts, how the concepts may be organized and viewed by the modeler, and rules governing the construction of models. The modeling paradigm defines the family of models that can be created using the resultant modeling environment. The metamodeling language is based on the UML class diagram notation and OCL constraints.

Generic Outline 0.1

date : 2005/02/01

Domain : IDE

Description : This metamodel describes a generic outline. In Eclipse, editors often have corresponding content outliners that provide a structured view of the editor contents and assist the user in navigating through the content of the editor.

GeoTrans 1.1

date : 2005/02/01

Domain : DataBase

Description : This metamodel describes basic geometrical operations (rotate, move, explode) that can be executed in sequence or parallel. The GeoTrans metamodel has an aggregation hierarchy. GeoTransfo can be put in a tree structure through subGeoTransfos and superGeoTransfos. GeoTransfo may have Params (parameters). GeoTransfo represents a geometrical operation. The actual operation is determined from its name attribute. Freeze means that the output of the operation has to be captured. A Param has a name, a Double value param and a back reference to the operation it belongs to.

GRAFCET 1.0

date : 2005/06/29

Domain : GRAFCET

Description : This basic metamodel describes GRAFCET. Grafcet is a french discrete system modeling notation close to Petri nets. The GRAFCET represents graphically the operation of an automatism by: Steps with associated action, transitions between steps, Directed connections between the steps and the transitions.

PetriNet 0.1

date : 2007/11/19

Domain :

Description : This metamodel is presented by Guido Wachsmut in the paper Metamodel Adaptation and Model Co-adaption. The metamodel captures a Petri net. A Petri net is composed of several places and transitions. Each transition has at least one input and one output place.

PetriNet 1.0

date : 2007/11/19

Domain :

Description : This metamodel is presented by Guido Wachsmut in the paper Metamodel Adaptation and Model Co-adaption. The metamodel captures a Petri net. A Petri net is composed of several places and transitions (at least one place and one transition). Each transition has at least one input place and one output place.

PetriNet 2.0

date : 2007/11/19

Domain :

Description : This metamodel is presented by Guido Wachsmut in the paper Metamodel Adaptation and Model Co-adaption. The metamodel captures a Petri net. A Petri net is composed of several places and transitions (at least one place and one transition). Each transition has at least one input place and one output place. Arcs between places and transitions are explicit.

PetriNet 3.0

date : 2007/11/19

Domain :

Description : This metamodel is presented by Guido Wachsmut in the paper Metamodel Adaptation and Model Co-adaption. The metamodel captures a Petri net. A Petri net is composed of several places and transitions (at least one place and one transition). Each transition has at least one input place and one output place. Arcs between places and transitions are explicit. PTArc and TPArc are respectively representing place-to-transition arcs and transition-to-place ones.

PetriNet 4.0

date : 2007/11/19

Domain :

Description : This metamodel is presented by Guido Wachsmut in the paper Metamodel Adaptation and Model Co-adaption. The metamodel captures a Petri net. A Petri net is composed of several places and transitions (at least one place and one transition). Each transition has at least one input place and one output place. Arcs between places and transitions are explicit. PTArc and TPArc are respectively representing place-to-transition arcs and transition-to-place ones. Arcs are annotated with weight.

PetriNet 5.0

date : 2007/11/19

Domain :

Description : This metamodel is presented by Guido Wachsmut in the paper Metamodel Adaptation and Model Co-adaption. The metamodel captures a Petri net. A Petri net is composed of several places and transitions (at least one place and one transition). Each transition has at least one input place and one output place. Arcs between places and transitions are explicit. PTArc and TPArc are respectively representing place-to-transition arcs and transition-to-place ones. Arcs are annotated with weight. In order to model dynamic aspects, places need to be marked with tokens.

HAL 1

date : 2006/05/12

Domain : Bibliography

Description : This is HAL import metamodel. This metamodel is used to import bibliography into HAL (Hyper Article en Ligne). HAL is a tool for direct scientific communication between researchers. Documents deposited in HAL are not subjected to any peer evaluation; but they should, however, be of sufficient quality to rate submission for publication in a specialized scientific journal. They should be uploaded either by one of the co-authors with the permission of the others or by an authorized person (e.g. librarian) who takes responsibility.The free access to these documents is intended to provide the widest possible diffusion of research work, but the intellectual property remains that of the authors. The users should conform to the usual standards of good academic usage, in the same way as in paper publications: respect of original work, citation of previous work, no plagiarism, etc.

HTML 1.0

date : 2005/04/15

Domain : HTML

Description : This basic metamodel describes HyperText Markup Language. HTML is the lingua franca for publishing hypertext on the World Wide Web. It is a non-proprietary format based upon SGML, and can be created and processed by a wide range of tools, from simple plain text editors - you type it in from scratch- to sophisticated WYSIWYG authoring tools. HTML uses tags such as <h1> and </h1> to structure text into headings, paragraphs, lists, hypertext links etc.

Integration of OCL Expressions in UML

date : 2006/07/10

Domain : UML

Description : This metamodel describes the Integration of OCL Expressions into the UML Core and Data Types Packages

See : This metamodel has been extracted from information available on this book:
Article A Metamodel for OCL
by Mark Richters and Martin Gogolla
Page 160, Section 3, Fig. 3 Integration of OCL Expressions into the UML Core and Data Types Packages
Lecture Notes in Computer Science 1723
Robert France, Bernhard Rumpe (Eds.)
The Unified Modeling Language UML 99: Beyond the standard

J2SE5 1.0

date : 2007/10/03

Domain : Object-oriented programming, Java

Description : This metamodel describes all the structural concepts of Java 5 source code (from packages up to method invocations and comments) and links between code elements (method invocations, variables usage, class inheritance, ...). The aim of this metamodel is to provide support in reverse-engineering Java applications or migrating existing applications to Java.

JAVA 1.1

date : 2005/03/18

Domain : Object-oriented programming, Java

Description : This simplified metamodel of Java consists principally of JavaElements which all have a name. A JavaClass has Methods and Fields and belongs to a Package. Methods, Fields and JavaClasses are subclasses of Modifiers and therefore indicate whether they are public, static or final. JavaClasses and Methods declare with the isAbstract attribute whether they are abstract or not. PrimitiveTypes and JavaClasses are Types. A Method has a Type as return Type and parameters of certain Types. A Field has also a Type.

JAVA3 0.1

date : 2005/08/11

Domain : Object-oriented programming, Java

Description : This basic metamodel describes JAVA. The Java language is an object-oriented programming language created by James Gosling and other engineers at Sun Microsystems. It was developed in 1991, as part of the Green Project, and officially announced on May 23 1995, at SunWorld; being released in November. Gosling and friends initially designed Java, which was called Oak at first (in honor of a tree outside Gosling s office), to replace C++ (although the feature set better resembles that of Objective C). The Java specifications are community-maintained through the Sun-managed Java Community Process. Sun holds a trademark on the Java name. The Java software plays three crucial roles or identities in the field of software: as a programming language, as middleware, as a platform. A crucial component of Java is the Java Virtual Machine (JVM). The availability of the JVM on almost all types of device, chips and software package enables Java to function both as middleware and a computing platform. The JVM enables Java to be platform independent since the JVM on each device/chip interprets the standard Java bytecode. This means you can develop code on your PC and expect it to run on Java-enabled phones as well as on mainframes equipped with Java without any adjustments. Hence the expression Write once, run anywhere. This also represents a huge amount of savings for software developers as code can be developed locally and cheaply.

JavaAbstractSyntax 1.0

date : 2006/10/24

Domain : Object-oriented programming, Java

Description : This metamodel describes a full abstract syntax tree (AST) of the code (statements, expressions, annotations and Javadoc) taken from a Java compilation unit (typically a Class). It is based upon the Eclipse JDT API specification.

JavaSource 1.1

date : 2005/04/12

Domain : Object-oriented programming, Java

Description : This basic metamodel represent Java source code. Java sources are modelized by a JavaSource element. This element is composed of ClassDeclarations. Each ClassDeclaration is composed of MethodDefinitions. Both ClassDeclaration and MethodDefinition inherit from the abstract NamedElement class (which provides a name). A MethodDefinition is composed of MethodInvocations (a call to a method). Each MethodInvocation is, in its turn, associated with a one and only MethodDeclaration (the called method).

KDM 1.0

Description : This metamodel describes the whole Knowledge Discovery Meta-Model (KDM), KDM being the first part of the work of the OMG Architecture-Driven Modernization (ADM) Task Force. KDM specifies the core concepts required for understanding existing software in preparation for its modernization and provides infrastructure to support more detailed definitions of Knowledge Discovery.

KDMSimplified 1.0

Description : This metamodel describes the main concepts of the Core and Kdm packages of the Knowledge Discovery Meta-Model (KDM) by the OMG Architecture-Driven Modernization (ADM) Task Force. KDM specifies the core concepts required for understanding existing software in preparation for its modernization and provides infrastructure to support more detailed definitions of Knowledge Discovery. This metamodel defines the basic abstractions of KDM and so was designed to be extended.

Klaper 1.0

date : 2006/07/19

Domain :

Description : This metamodel describes KLAPER ((Kernel LAnguage for PErformance and Reliability analysis). It is a kernel language whose aim is to capture the relevant information for the analysis of non-functional attributes of component-based systems, with a focus on performance and reliability attributes, abstracting away unnecessary details.

KM3 1.1

date : 2004/11/01

Domain : KM3 language

Description : KM3, the Kernel MetaMetaModel, provides a textual concrete syntax that eases the coding of metamodels. Its syntax is simple, straight forward and has some similarities with the Java notation. KM3 resembles Ecore terminology and has the notion of package, class, attribute, reference and primitive datatype.

LaTeX 1.0

date : 2005/06/17

Domain : Documentation

Description : This basic metamodel describes the structure of LaTeX document. This metamodel is based on Tayeb Lemlouma LaTeX DTD created on June 2001. LaTeX is a high-quality typesetting system, with features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

Make 0.3

date : 2005/07/06

Domain : Build tool

Description : A metamodel describing the build tool Make: Make is a UNIX utility intended to automate and optimize the construction of programs. It can help develop programs when they consist of many components or source files. A descriptor file, namely makefile, describes the relationship among source files and provides commands for updating each file. Make invokes makefile to automatically rebuild a program whenever one of the source files is modified. It only recompiles the files that were affected by changes, thus saving compiling time. This helps reduce the likelihood of human errors when making entries from the command line. Apart from compilation, make is an effective tool for program installation and system configuration changes.

Maven (maven.xml) 0.3

date : 2005/07/06

Domain : build tool

Description : A metamodel describing the file maven.xml of the build tool Maven: Apache Maven is a project management and build tool that is becoming more common in organisations. It continues on from where Ant left off and provides for modularisation of functionality into plugins, the use of a central repository for storing dependent JAR s, as well as many other convenience functionality. This file defines maven.xml, project specific properties.

Maven (project.xml) 0.3

date : 2005/07/06

Domain : build tool

Description : A metamodel describing the file project.xml of the build tool Maven: Apache Maven is a project management and build tool that is becoming more common in organisations. It continues on from where Ant left off and provides for modularisation of functionality into plugins, the use of a central repository for storing dependent JAR s, as well as many other convenience functionality. This file represents project.xml, it contains the basic project configuration for maven (project name, developers, urls, dependencies, etc).

Mining Mart 1.0

date : 2006/07/21

Domain : Mining Mart

Description : This metamodel describes Mining Mart. Mining Mart follows a typical metadata-driven software architecture,[...]. The Mining Mart MetaModel(M4) can be logically divided into two main parts, one managing information with regard to data modelling and the other one regarding case.

Monitor Program 1.1

date : 2005/05/09

Domain : programming

Description : This metamodel describes programs containing Hoare s monitors definitions. A Program inherits both from Structure and ProcContainerElement. A Progam can contain VariableDeclarations (as a Structure), Procedures (as a ProcContainerElement), and Monitors. A Monitor is also a Structure and a ProcContainerElement, and can therefore contain VariableDeclarations and Procedures. Besides Statements and Parameters, a Procedure, as a Structure, can also contain VariableDeclarations. Each VariableDeclaration is associated with a one and only Type. It may also contain an initial value that is represented by an Expression (see below). Parameters inherit from VariableDeclaration. They are characterized by a direction attribute (in or out). A Procedure contains a sequence of Statements. An AssignmentStat contains a target VariableExp and a value Expression. A WhileStat contains a condition Expression and several doStats Statements. A ConditionalStat contains a condition Expression, several thenStats Statements and, optionally, elseStats Statements. Finally, an ExpressionStat simply contains an Expression. Expression is an abstract entity from which the following elements inherit: IntegerExp and BooleanExp (which inherit from the abstract LiteralExp entity), VariableExp which is associated with a VariableDeclaration, PropertyCallExp (abstract) which is characterized by its source element (of type Expression). There exist three types of PropertyCallExp: the AttributeCallExp, the OperatorCallExp and the ProcedureCallExp. An OperatorCallExp contains a right element (of type Expression). A ProcedureCallExp can contain argument Expressions.

SpreadsheetMLBasicDef 1.2

date : 2005/07/01

Domain : Microsoft Office Excel, XML

Description : This metamodel describes a basic subset of SpreadsheetML, an XML dialect developed by Microsoft to represent the information in an Excel spreadsheet. This metamodel takes back in details the concepts expressed in the simplified SpreadsheetML metamodel and adds the notion of Office document Properties.

SpreadsheetMLPrintingSetup 1.2

date : 2005/07/01

Domain : Microsoft Office Excel, XML

Description : This metamodel describes a subset of SpreadsheetML, an XML dialect developed by Microsoft to represent the information in an Excel spreadsheet. This metamodel takes back in details the concepts expressed in the SpreadsheetML metamodel who manages worksheet options, and adds the management of page setup and print options (Excel worksheet options).

SpreadsheetMLSimplified 1.2

date : 2005/07/01

Domain : Microsoft Office Excel, XML

Description : This metamodel describes a simplified subset of SpreadsheetML, an XML dialect developed by Microsoft to represent the information in an Excel spreadsheet. The root element for an XML spreadsheet is the Workbook element. A Workbook element can contain multiple Worksheet elements. A Worksheet element can contain a Table element. It holds the row elements that define a spreadsheet. A row holds the cell elements that make it up. A Cell element holds the data. In addition, Column elements (children of the Table element) can be used to define the attributes of columns in the spreadsheet.

SpreadsheetMLStyles 1.2

date : 2005/07/01

Domain : Microsoft Office Excel, XML

Description : This metamodel describes a quite complete subset of SpreadsheetML, an XML dialect developed by Microsoft to represent the information in an Excel spreadsheet. This metamodel takes back in details the concepts expressed in the SpreadsheetML metamodel who manages printing setup, and adds the management of default or user-defined styles and named ranges.

SpreadsheetMLWorkbookProp 1.1

date : 2005/06/29

Domain : Microsoft Office Excel, XML

Description : This metamodel describes a subset of SpreadsheetML, an XML dialect developed by Microsoft to represent the information in an Excel spreadsheet. This metamodel takes back in details the concepts expressed in the basic SpreadsheetML metamodel and adds the notion of Excel Workbook specific properties.

SpreadsheetMLWorksheetOpt 1.2

date : 2005/07/01

Domain : Microsoft Office Excel, XML

Description : This metamodel describes a subset of SpreadsheetML, an XML dialect developed by Microsoft to represent the information in an Excel spreadsheet. This metamodel takes back in details the concepts expressed in the SpreadsheetML metamodel who manages workbook properties, and adds the management of the main Excel worksheet options.

WordprocessingMLBasicDef 1.2

date : 2005/07/01

Domain : Microsoft Office Word, XML

Description : This metamodel describes a basic subset of WordprocessingML, an XML dialect developed by Microsoft to represent the information in an Word document. This metamodel takes back in details the concepts expressed in the simplified WordprocessingML metamodel and adds the notion of Office document properties.

WordprocessingMLSimplified 1.2

date : 2005/07/01

Domain : Microsoft Office Word, XML

Description : This metamodel describes a simplified subset of WordprocessingML, an XML dialect developed by Microsoft to represent the information in an Word document. This format is an alternative file format to the well-known .doc binary format and saves all of the same information that is saved in the Word binary format. This metamodel only manages raw textual data in very simple word documents (advanced properties of Word are not developed in this metamodel...).

WordprocessingMLStyles 1.2

date : 2005/07/01

Domain : Microsoft Office Word, XML

Description : This metamodel describes a subset of WordprocessingML, an XML dialect developed by Microsoft to represent the information in an Word document. This metamodel takes back in details the concepts expressed in the WordprocessingML metamodel who manages table elements, and adds the partial management of fonts and styles for a Word document.

WordprocessingMLTableElts 1.2

date : 2005/07/01

Domain : Microsoft Office Word, XML

Description : This metamodel describes a subset of WordprocessingML, an XML dialect developed by Microsoft to represent the information in an Word document. This metamodel takes back in details the concepts expressed in the basic WordprocessingML metamodel and adds the management of table elements that can be contained in a Word document.

MSProject 1.1

date : 2005/04/13

Domain : Microsoft, Project Management

Description : This metamodel describes projects defined in conformance to a limited subset of the MSProject metamodel. Within this metamodel, a project is associated with a MSProject element. Such an element contains Task, identified by a unique UID attribute, which can have predecessors among other defined Tasks.

MSProject2 0.1

date : 2005/08/04

Domain : Microsoft, Project Management

Description : This metamodel is a simplified metamodel of Microsoft Project. Microsoft Project (or MSP) is project management software developed and sold by Microsoft. It is designed to assist project managers in developing plans, assigning resources to tasks, tracking progress, managing budgets and analyzing workloads. Microsoft Project creates critical path schedules, schedules can be resource leveled. The chain is visualized in a gantt chart. Resource definitions (people, equipment and materials) can be shared between projects using a shared resource pool. Each resource can have its own calendar which defines what days and shifts a resource can work. Resource rates are used to calculate resource assignment costs which are rolled up and summarized the resource level. Each resource can be assigned to multiple tasks in multiple plans and each task can be assigned multiple resources. Microsoft Project schedules task work based on the resource availability as defined in the resource calendars. All resources can be defined in a enterprise resource pool. Microsoft Project creates budgets based on assignment work and resource rates. As resources are assigned to tasks and assignment work estimated, Microsoft Project calculates the cost equals the work times the rate. This rolls up to the task level, then to any summary tasks and finally to the project level.

DatadiagramMLBasicDef 1.2

date : 2005/07/01

Domain : Microsoft Visio, XML

Description : This metamodel describes a basic subset of DatadiagramML, an XML dialect developed by Microsoft to represent Visio documents data elements and attributes and their containment relationships. This metamodel takes back in details the concepts expressed in the simplified DatadiagramML metamodel and adds the management of the main document properties and settings.

DatadiagramMLSimplified 1.2

date : 2005/07/01

Domain : Microsoft Visio, XML

Description : This metamodel describes a simplified subset of DatadiagramML, an XML dialect developed by Microsoft to represent Visio documents data elements and attributes and their containment relationships. A DatadiagramML file, like a Visio drawing (VSD) file, contains document-level containers and hierarchical containers of other containers. Most elements that define the data in the DatadiagramML file are named with the same or similar names to the cells in the Shape or the properties exposed in the Visio object model. This metamodel only manages geometrical forms and raw textual data (without text formatting).

DatadiagramMLTextFormat 1.2

date : 2005/07/01

Domain : Microsoft Visio, XML

Description : This metamodel describes a subset of DatadiagramML, an XML dialect developed by Microsoft to represent Visio documents data elements and attributes and their containment relationships. This metamodel takes back in details the concepts expressed in the basic DatadiagramML metamodel and adds the management of textual data formatting for a Visio document.

DatadiagramMLXForm 1.2

date : 2005/07/01

Domain : Microsoft Visio, XML

Description : This metamodel describes a subset of DatadiagramML, an XML dialect developed by Microsoft to represent Visio documents data elements and attributes and their containment relationships. This metamodel takes back in details the concepts expressed in the DatadiagramML metamodel who manages text formatting, and adds the management of XForms and Visio document settings.

MTRANS 0.1

date : 2005/08/10

Domain : Model transformation

Description : This metamodel describes MTRANS. The MTRANS project aims to supply a general framework for expressing model transformations. In order to be as general as possible, it is based on a meta-modeling approach (a meta-model is used to define the semantics of each model). The MTRANS framework is supplying a language and an environment to write models transformations. The language is composed by a fixed instruction set (conditional, loop, etc.) plus a part depending on the particular meta-models used. MTRANS was a precursor to QVT languages.

News 0.1

OCCAM 0.1

date : 2006/07/25

Domain :

Description : This metamodel describes OCCAM. OCCAM is a parallel processing language designed by a team at INMOS in conjunction with the design of the transputer processor, and based on T. Hoare s ideas of CSP.

OCL Expressions

date : 2006/07/10

Domain : OCL

Description : This metamodel describes OCL Expressions

See : This metamodel has been extracted from information available in the following article:
Article A Metamodel for OCL
by Mark Richters and Martin Gogolla
Page 161, Section 5, Fig. 7 Metamodel for OCL Expressions
Lecture Notes in Computer Science 1723
Robert France, Bernhard Rumpe (Eds.)
The Unified Modeling Language UML 99: Beyond the standard

OCL Operations

date : 2006/07/10

Domain : OCL

Description : This metamodel describes OCL Operations

See : This metamodel has been extracted from information available in the following article:
Article A Metamodel for OCL
by Mark Richters and Martin Gogolla
Page 161, Section 5, Fig. 9 Metamodel for OCL Operations
Lecture Notes in Computer Science 1723
Robert France, Bernhard Rumpe (Eds.)
The Unified Modeling Language UML 99: Beyond the standard

OCL Types

date : 2006/07/10

Domain : OCL

Description : This metamodel describes OCL Types

See : This metamodel has been extracted from information available in the following article:
Article A Metamodel for OCL
by Mark Richters and Martin Gogolla
Page 161, Section 3, Fig. 4 Metamodel for OCL Types
Lecture Notes in Computer Science 1723
Robert France, Bernhard Rumpe (Eds.)
The Unified Modeling Language UML 99: Beyond the standard

OCL Values

date : 2006/07/10

Domain : OCL

Description : This metamodel describes OCL Values

See : This metamodel has been extracted from information available in the following article:
Article A Metamodel for OCL
by Mark Richters and Martin Gogolla
Page 160, Section 6, Fig. 11 Metamodel for Values
Lecture Notes in Computer Science 1723
Robert France, Bernhard Rumpe (Eds.)
The Unified Modeling Language UML 99: Beyond the standard

ODP Computational Viewpoint 0.1

date : 2005/12/01

Domain :

Description : The Reference Model of Open Distributed Processing (RM-ODP) provides a general framework for the standardization of open distributed processing. RM-ODP defines five generic and complementary viewpoints on the system and its environment: enterprise, information, computational, engineering and technology. They divide the system design according to several areas of concerns, each one focusing on a specific aspect of the system, and allow different stakeholders to observe the system from different perspectives. In particular, the ODP computational viewpoint describes the functionality of the system and its environment in terms of computational objects that interact at interfaces. The Computational Viewpoint Metamodel defines the ODP Computational Language, and conforms to ITU-T Rec. X.906 | ISO/IEC Committee Draft 19793 (Use of UML for ODP systems specifications) a standard that defines how to use UML to represent the ODP viewpoint languages and concepts.

ODP Enterprise Viewpoint 0.1

date : 2006/01/01

Domain :

Description : The Reference Model of Open Distributed Processing (RM-ODP) provides a general framework for the standardization of open distributed processing. RM-ODP defines five generic and complementary viewpoints on the system and its environment: enterprise, information, computational, engineering and technology. They divide the system design according to several areas of concerns, each one focusing on a specific aspect of the system, and allow different stakeholders to observe the system from different perspectives. In particular, the ODP enterprise viewpoint is concerned with the purpose, scope and policies governing the activities of the ODP system within the organization of which it is a part. The Enterprise Viewpoint Metamodel defines the ODP Enterprise Language, and conforms to ITU-T Rec. X.906 | ISO/IEC Committee Draft 19793 (Use of UML for ODP systems specifications) a standard that defines how to use UML to represent the ODP viewpoint languages and concepts.

ODP Information Viewpoint 0.1

date : 2005/12/01

Domain :

Description : The Reference Model of Open Distributed Processing (RM-ODP) provides a general framework for the standardization of open distributed processing. RM-ODP defines five generic and complementary viewpoints on the system and its environment: enterprise, information, computational, engineering and technology. They divide the system design according to several areas of concerns, each one focusing on a specific aspect of the system, and allow different stakeholders to observe the system from different perspectives. In particular, the ODP information viewpoint allows the description of the information required and handled by an ODP system. The Information Viewpoint Metamodel defines the ODP Information Language, and conforms to ITU-T Rec. X.906 | ISO/IEC Committee Draft 19793 (Use of UML for ODP systems specifications) a standard that defines how to use UML to represent the ODP viewpoint languages and concepts.

ODP Engineering Viewpoint 0.1

date : 2005/12/01

Domain :

Description : The Reference Model of Open Distributed Processing (RM-ODP) provides a general framework for the standardization of open distributed processing. RM-ODP defines five generic and complementary viewpoints on the system and its environment: enterprise, information, computational, engineering and technology. They divide the system design according to several areas of concerns, each one focusing on a specific aspect of the system, and allow different stakeholders to observe the system from different perspectives. In particular, the ODP engineering viewpoint is concerned with the architecture required to support the distribution of the system and its constituent components. The Engineering Viewpoint Metamodel defines the ODP Engineering Language, and conforms to ITU-T Rec. X.906 | ISO/IEC Committee Draft 19793 (Use of UML for ODP systems specifications) a standard that defines how to use UML to represent the ODP viewpoint languages and concepts.

ODP Technology Viewpoint 0.1

date : 2006/01/01

Domain :

Description : The Reference Model of Open Distributed Processing (RM-ODP) provides a general framework for the standardization of open distributed processing. RM-ODP defines five generic and complementary viewpoints on the system and its environment: enterprise, information, computational, engineering and technology. They divide the system design according to several areas of concerns, each one focusing on a specific aspect of the system, and allow different stakeholders to observe the system from different perspectives. In particular, the ODP technology viewpoint allows the description of the choice of technology applied in the implementation of an ODP system. The Technology Viewpoint Metamodel defines the ODP Technology Language, and conforms to ITU-T Rec. X.906 | ISO/IEC Committee Draft 19793 (Use of UML for ODP systems specifications) a standard that defines how to use UML to represent the ODP viewpoint languages and concepts.

OpenQVT 0.1

date : 2005/08/09

Domain : QVT

Description : This metamodel describes the structure of OpenQVT. The QVT Structure layer introduces common OO structuring concepts that can be easily shared by existing or new QVT languages and QVT frameworks. Such a common foundation is important to model explicitly the inter-operability between distinct tools possibly implementing a variety of formalisms and paradigms. This layer only exposes structuring concepts any excludes any behavioral concern. Note that this level does not need to be standardized since the common Core of the infrastructure library shared by MOF and UML 2.0 already represents it. The next upper level is the QVT Languages and Frameworks. Any language or any framework, which is compliant with the structuring concepts defined in the previous layer, is positioned here. The TRL language (a renaming of MTRANS), proposed for specifying precise mappings in the OMG specifications, is an example. However, other approaches may be used. A transformation program may be written using a programming language such as Java or Python and use various structural patterns packaged in a transformation framework. The highest abstract layer is QVT interoperability, which introduces a component view of transformations, allowing them to be integrated or combined within transformation assembly lines.

Parameters 0.1

date : 2006/03/03

Domain : Model Transformation Design Pattern, Parameter

Description : This simple metamodel describes the notion of parameter and list of parameters. Models conform to the Parameter metamodel are often associated to a model transformation as defined in the design pattern Parameter.

Pascal 0.1

date : 2005/08/10

Domain : Programming Language

Description : This metamodel describes the Pascal programming language, which was originally developed by Niklaus Wirth, a member of the International Federation of Information Processing (IFIP) Working Group 2.1. Professor Niklaus Wirth developed Pascal to provide features that were lacking in other languages of the time. His principle objectives for Pascal were for the language to be efficient to implement and run, allow for the development of well structured and well organized programs, and to serve as a vehicle for the teaching of the important concepts of computer programming. Pascal, which was named after the mathematician Blaise Pascal, is a direct descendent from ALGOL 60, which Wirth helped develop. Pascal also draws programming components from ALGOL 68 and ALGOL-W. The original published definition for the Pascal language appeared in 1971 with latter revisions published in 1973. It was designed to teach programming techniques and topics to college students and was the language of choice to do so from the late sixties to the late heighties. Significant Language Features: Built in Data Types- Pascal contains it is own built in data types of Integer, Real, Character, and Boolean. User defined Data Types - Has the ability to define scalar types as well as sub-ranges of those data types. Provides a defined set of Data Structures- These data structures include Arrays, Records, Files and Sets. Has a strong data typing element - Pascal compliers can diagnose an incompatible assignment of one type to a variable to another type. Supports Structured Programming - This is accomplished through the use of subprograms called procedures and functions. Simplicity and Expressivity - Because the language is simple and expressive in nature it allows for effective teaching of computer programming techniques. The Prime area of application that Pascal entails is the learning environment. This language was not really developed to be used for anything other than teaching students the basics of programming, after all it was originally developed for this purpose. In the early seventies to the early nineties Pascal was the language of choice for most major colleges and universities for teaching college level programming techniques.

PathExp 1.0

date : 2005/07/18

Domain : Path Expression

Description : The PathExp metamodel describes the structure of the graphical representation of the path expression. The PathExp metamodel describes the different model elements that compose the graphical representation associated with path expressions, as well as the way they can be linked to each other. A PathExp is composed of States and Transitions. Each Transition has a State as source and a State as target. Each State can have several incoming and outgoing Transitions. Both Transition and PathExp inherits from the abstract Element entity, for which a name attribute is defined.

Perceptory 1.0

date : 2006/07/24

Domain :

Description : This metamodel describes Perceptory. Perceptory is a CASE tool that comprises a UML based conceptual schema building tool for geospatial conceptual models and an object dictionary database.

PetriNet 1.0

date : 2005/07/18

Domain : Petri Net, PNML

Description : The PetriNet metamodel describes the different model elements that compose a Petri net model, as well as the way they can be linked to each other. A PetriNet model is composed of Transitions, Places and Arcs. The PetriNet entity, as well as the Transition and the Place ones, inherits from the abstract Element entity that defines a name attribute. An Arc is an abstract entity which is associated with a weight attribute. Each Arc is either of the TransToPlaceArc or PlaceToTransArc kind. A TransToPlaceArc connects a Transition to a Place, whereas a PlaceToTransArc connects a Place to a Transition. A Place can have several outgoing PlaceToTransArcs and several incoming TransToPlaceArcs. Similarly, a Transition can have several incoming PlaceToTransArcs and several outgoing TransToPlaceArcs. Each TransToPlaceArc has a source Transition and a target Place. In the same way, each PlaceToTransArc has a source Place and a target Transition.

PetriNet_extended 1.0

date : 2005/08/11

Domain : Petri net

Description : This basic metamodel describes Petri Net. It consists of places, transitions and directed arcs that connect them, so arcs run between places and transitions, not between places and places or transitions and transitions. There is two sorts of arcs : the ones which connect places with transitions, and the other start at a transition and end at a place. Places can contain tokens; the current state of the modeled system (the marking) is given by the number (and type if the tokens are distinguishable) of tokens in each place. Transitions are active components. They model activities which can occur (the transition fires), thus changing the state of the system (the marking of the Petri net). Transitions are only allowed to fire if they are enabled, which means that all the preconditions for the activity must be fulfilled (there are enough tokens available in the input places). When the transition fires, it removes tokens from its input places and adds some at all of its output places. The number of tokens removed / added depends on the cardinality of each arc (weight). The interactive firing of transitions in subsequent markings is called token game.

PIF 0.1

date : 2005/08/04

Domain : Interchange Format

Description : This metamodel describes the structure of PIF (Process Interchange Format). The goal of the PIF Project is to develop an interchange format to help automatically exchange process descriptions among a wide variety of business process modeling and support systems such as workflow software, flow charting tools, process simulation systems, and process repositories. Instead of having to write ad hoc translators for each pair of such systems, each system will only need to have a single translator for converting process descriptions in that system into and out of the common PIF format. Then any system will be able to automatically exchange basic process descriptions with any other system. The PIF project aims to support sharing process descriptions such a way that that they can be automatically translated back and forth between PIF and other process representations with as little loss of meaning as possible. If translation cannot be done fully automatically, the human efforts needed to assist the translation should be minimized. If a translator cannot translate part of a PIF process description to its target format, it will: Translate as much of the description as possible (and not, for example, simply issue an error message and give up); Represent any untranslatable parts so that the translator can add them back to the process description when it is translated back into PIF.

PL/1 0.1

date : 2005/08/11

Domain : programming language

Description : This basic metamodel describes PL/1. PL/1 (Programming Language One) was developed as an IBM product in the mid sixties, and was originally named NPL (New Programming Language). Until the time this new language was developed, all previous languages had focused on one particular area of application, such as science, artificial intelligence, or business. PL/I was not designed to be used in the same way. It was the first large scale attempt to design a language that could be used in a variety of application areas. Significant Language Features: PL/1 is completely free form and has no reserved keywords; It precisely defines it is data types without regard for any hardware; PL/1 is a block-oriented language, consisting of packages, begin blocks, and statements. This type of structure allows the programmer to produce highly-modular applications; PL/1 contains control structures. For example, SELECT...WHEN...OTHERWISE allow logical operations, and DO statements allow units to be executed unconditionally one time, forever, or while a condition is true or until a condition becomes true; PL/1 supports arrays, structures, unions, arrays of structures or unions, structures or unions of arrays, and combinations thereof; PL/1 provides four different storage classes: AUTOMATIC, STATIC, CONTROLLED, and BASED.

PNML_basic 1.0

date : 2005/06/15

Domain : Petri net, XML

Description : This metamodel describes basic PNML (Petri Net Markup Language). PNML is a concept for defining the overall structure of a Petri net file. There are many different types of Petri nets. Thus, there is a generic concept for adjusting net type specific features via a specific Petri Net Type Definition (PNTD). For implementing a specific PNTD, PNML is enlarged by type specific labels at certain net objects. A label assigns further meaning (besides the Petri net semantics) to a net or its objects. Typically, a label represents a name of a node, the initial marking of a place, the guard of a transition, or the inscription of an arc. The legal labels and the legal combination of labels are defined within a PNTD. This meta-model is based on ptNetb.pntd defined by Michael Weber on June 2003. It is implements the Petri net type for Place/Transition nets and it is based on the definition for basic PNML.

PNML Modular 1.0

date : 2005/06/16

Domain : Petri net, XML

Description : This metamodel describes modular PNML (Petri Net Markup Language). PNML is a concept for defining the overall structure of a Petri net file. There are many different types of Petri nets. Thus, there is a generic concept for adjusting net type specific features via a specific Petri Net Type Definition (PNTD). For implementing a specific PNTD, PNML is enlarged by type specific labels at certain net objects. A label assigns further meaning (besides the Petri net semantics) to a net or its objects. Typically, a label represents a name of a node, the initial marking of a place, the guard of a transition, or the inscription of an arc. The legal labels and the legal combination of labels are defined within a PNTD. This metamodel is based on ptNetb.pntd defined by Michael Weber on June 2003. It is implements the Petri net type for Place/Transition nets and it is based on the definition for modular PNML.

PNML Simplified 1.1

date : 2005/06/15

Domain : Petri net, XML

Description : The Petri Net Markup Language (PNML) is a proposal of an XML-based interchange format for Petri nets. Originally, the PNML was intended to serve as a file format for the Java version of the Petri Net Kernel. PNML is a concept for defining the overall structure of a Petri net file. This metamodel describes simplified PNML (Petri Net Markup Language). PNML is a concept for defining the overall structure of a Petri net file. There are many different types of Petri nets. Thus, there is a generic concept for adjusting net type specific features via a specific Petri Net Type Definition (PNTD). For implementing a specific PNTD, PNML is enlarged by type specific labels at certain net objects. A label assigns further meaning (besides the Petri net semantics) to a net or its objects. Typically, a label represents a name of a node, the initial marking of a place, the guard of a transition, or the inscription of an arc. The legal labels and the legal combination of labels are defined within a PNTD. This meta-model is based on ptNetb.pntd defined by Michael Weber on June 2003. It is implements the Petri net type for Place/Transition nets and it is based on the definition for simplified PNML.

PNML_structured 1.0

date : 2005/06/16

Domain : Petri net, XML

Description : This metamodel describes structured PNML (Petri Net Markup Language). PNML is a concept for defining the overall structure of a Petri net file. There are many different types of Petri nets. Thus, there is a generic concept for adjusting net type specific features via a specific Petri Net Type Definition (PNTD). For implementing a specific PNTD, PNML is enlarged by type specific labels at certain net objects. A label assigns further meaning (besides the Petri net semantics) to a net or its objects. Typically, a label represents a name of a node, the initial marking of a place, the guard of a transition, or the inscription of an arc. The legal labels and the legal combination of labels are defined within a PNTD. This meta-model is based on ptNetb.pntd defined by Michael Weber on June 2003. It is implements the Petri net type for Place/Transition nets and it is based on the definition for structured PNML.

Problem 1.0

Program 0.1

date : 2007/03/07

Domain : programming

Description : This metamodel describes programs. A Program inherits both from Structure and ProcContainerElement. A Progam can contain VariableDeclarations (as a Structure), Procedures (as a ProcContainerElement), and Monitors. A Monitor is also a Structure and a ProcContainerElement, and can therefore contain VariableDeclarations and Procedures. Besides Statements and Parameters, a Procedure, as a Structure, can also contain VariableDeclarations. Each VariableDeclaration is associated with a one and only Type. It may also contain an initial value that is represented by an Expression (see below). Parameters inherit from VariableDeclaration. They are characterized by a direction attribute (in or out). A Procedure contains a sequence of Statements. An AssignmentStat contains a target VariableExp and a value Expression. A WhileStat contains a condition Expression and several doStats Statements. A ConditionalStat contains a condition Expression, several thenStats Statements and, optionally, elseStats Statements. Finally, an ExpressionStat simply contains an Expression. Expression is an abstract entity from which the following elements inherit: IntegerExp and BooleanExp (which inherit from the abstract LiteralExp entity), VariableExp which is associated with a VariableDeclaration, PropertyCallExp (abstract) which is characterized by its source element (of type Expression). There exist three types of PropertyCallExp: the AttributeCallExp, the OperatorCallExp and the ProcedureCallExp. An OperatorCallExp contains a right element (of type Expression). A ProcedureCallExp can contain argument Expressions.

ProMarte a UML profile for MARTE 0.1

Description : A metamodel of MARTE. It comes from the ProMARTE specifaction a UML profile for MARTE dating from 14th November 2005. MARTE is the acronym for Modeling and Analysis of Real-Time and Embedded systems.

PtolemyII 1.0

date : 2005/08/03

Domain : Java, modeling, design

Description : This metamodel describes a substet of the Ptolemy II Java packages set which supports heterogeneous, concurrent modeling and design. It belongs to the Ptolemy project whose aim is to study modeling, simulation, and design of concurrent, real-time, embedded systems by focusing on assembly of concurrent components.

QVT 1.0

date : 2007/06/03

Domain : MDE/Model Transformation, QVT

Description : This KM3 version of the QVT (MOF™ Query / Views / Transformations) metamodel was created from the files available on the OMG website (http://www.omg.org/cgi-bin/doc?ad/2005-09-01), and was hand-modified to be compatible with the output of the SmartQVT front-end.

SimpleUML 0.2

R2ML 4.0

date : 2006/12/15

Domain : R2ML (REWERSE I1 Rule Markup Language) language metamodel

Description : R2ML language metamodel represents abstract syntax for R2ML XML based concrete syntax. R2ML is a general Web rule markup language for representing different types of rules. It consists of overlapping metamodels for the following types of rules: integrity, derivation, reaction, production, and transformation rules.

Relational 1.1

date : 2005/03/18

Domain : DataBase

Description : This metamodel describes simple relational database models. It consists of classes having a name which they inherit from the abstract class Named. The principal class Table contains a set of Columns and has a reference to its keys. The class Column has the references owner and keyOf pointing to the Table it belongs to and of which it is part of the key (in case it is a key). Furthermore, Column has a reference to Type.

Repository 1.0

date : 2006/07/25

Domain :

Description : This metamodel describes Repository. The repository metamodel includes only elements that contribute to the structure and semantics of the system under development. Classes in the repository model are, e.g., SUBSYSTEM, CLASS, FEATURE etc.

Reqtify 0.1

date : 2005/07/21

Domain : traceability tool

Description : Reqtify Metamodel: TNI-Valiosys requirements traceability tool. Most projects often start with a systems and requirements engineering phase during which the system specification is defined, and the system requirements are captured and formalized. Reqtify takes as inputs the formalized requirements produced from this phase, and monitors their implementation throughout the rest of the lifecycle of project. Reqtify effectively manages requirements traceability and impact analysis across the entire lifecycle of the project, enabling quality development in both hardware and software projects.

RSS-2.0 2.0

date : 2005/11/01

Domain : XML

Description : This metamodel describes RSS. RSS is a Web content syndication format. Its name is an acronym for Really Simple Syndication. RSS is a dialect of XML. All RSS files must conform to the XML 1.0 specification, as published on the World Wide Web Consortium (W3C) website.

SCADE 1.0

date : 2006/07/11

Domain : SCADE

Description : This metamodel is not the official version supported by the SCADE suite. SCADE is a commercial product from the Esterel Technologies Company. It stands for Safety Critical Application Development Environment. ESTEREL Technologie has provided the sources necessary to implement in KM3 the SCADE metamodel.

Sharengo 1.0

date : 2007/02/27

Domain :

Description : This metamodel is a very simple SharenGo metamodel. SharenGo is a group aiming to organize, explain and work on principles of sharing between differents companies in the context of IT but oriented on the core business (not IT related) of all participants.

SPEM 0.1

date : 2005/08/10

Domain : Software Process

Description : This metamodel describes SPEM (Software Process Engineering Metamodel) which is is a meta-model for defining processes and their components. A tool based on SPEM would be a tool for process authoring and customizing. The actual enactment of processes - that is, planning and executing a project using a process described with SPEM, is not in the scope of this model. In the chapters so far, SPEM has been directly defined as a meta-model. SPEM can be used by directly instantiating this stand-alone meta-model. But SPEM is also defined as a UML Profile. SPEM is dedicated to software processes modeling. Many features of the UML provide the necessary basis for modeling processes, and many other UML features provide useful additional modeling capacities. Being a UML profile, SPEM both defines modeling capacities dedicated to the software process domain, and gains the benefit of the expressiveness of UML. For example, Use Case modeling, which is sometimes used for modeling processes, is not defined as a specific SPEM facility, but can be inherited from UML. Alignment with various process modeling languages is another advantage of using UML Profiles. The SPEM profile uses extensively the UML Activity Diagram model to give more detail to the work decomposition that is represented in the stand-alone meta-model by the WorkDefinition::subWork association. It is expected that the various kinds of process modeling techniques (Business Process Modeling, Workflow, etc.) will be aligned with UML at some time. SPEM will naturally benefit from this convergence, and from any other convergence and improvements that will occur with UML.

SPL 1.0

date : 2006/01/18

Domain :

Description : This metamodel describes SPL (Session Processing Language). The goal of SPL is to ease the development of telephony services. SPL relies on a Service Logic Execution Environment for SIP (SIP-SLEE). SPL guaranties critical properties by introducing domain-specific concepts and semantic restrictions.

Statecharts 1.0

date : 2005/08/03

Domain : UML

Description : This metamodel describes Statecharts which consist of three primary items: States: distinguishable conditions of existence that persist for a significant period of time, Transitions: means by which objects change states in respond to events and Actions: atomic behaviors, simple statements such as a++ or invocation of operations defined within the context object or other objects (they are executed behaviors at various points in a state machine, such as when an event triggers a transition, when a state is entered, or when a state is exited).

SWRC 1

date : 2006/07/18

Domain : Bibliography

Description : This metamodel describes SWRC ontology. The SWRC (Semantic Web for Research Communities) is an ontology for modeling entities of research communities such as persons, organisations, publications (bibliographic metadata) and their relationships. It is used in numerous applications and projects including the AIFB portal, Bibster and the SemIPort project. More details about the modeling of the SWRC ontology can be found in: York Sure, Stephan Bloehdorn, Peter Haase, Jens Hartmann, Daniel Oberle. The SWRC Ontology - Semantic Web for Research Communities. In Proceedings of the 12th Portuguese Conference on Artificial Intelligence (EPIA 2005). Springer, Covilha, Portugal, December 2005.

SysML (OMG System Modeling Language) 1.0

Description : A metamodel of SysML in km3. SysML is an acronym for Systems Modeling Language. It is an OMG standard to design systems and it became an UML profile. The currently version of specifications is dating from the 3rd May 2006.

Table 1.1

date : 2005/04/12

Domain : Spreadsheet

Description : This is a very basic abstract Table metamodel, which may be easily mapped to existing table representations (XHTML, ExcelML etc). Within this metamodel, a Table is associated with a Table element. Such an element is composed of several Rows that, in their turn, are composed of several Cells.

TextualPathExp 1.0

date : 2005/07/18

Domain : Path Expression

Description : The TextualPathExp metamodel describes the structure of a path expression in its textual form. A TextualPathExp contains a Path, which, in its turn, can contain from one to several Transitions. A Transition can be defined as a multiple or a single Transition. It is an abstract entity that can be either a PrimitiveTransition or an AlternativeTransition. A PrimitiveTransition is characterized by its name. An AlternativeTransition contains a number of alternative Paths.

UDDI 0.1

date : 2005/08/04

Domain : Interchange Format

Description : This metamodel is a fragment of UDDI metamodel. The Universal Description, Discovery and Integration (UDDI) protocol is one of the major building blocks required for successful Web services. UDDI creates a standard interoperable platform that enables companies and applications to quickly, easily, and dynamically find and use Web services over the Internet. UDDI also allows operational registries to be maintained for different purposes in different contexts. UDDI is a cross-industry effort driven by major platform and software providers, as well as marketplace operators and e-business leaders within the OASIS standards consortium.

UEML 1.0

date : 2006/07/18

Domain : UEML

Description : UEML (Unified Enterprise Modelling Language) is a Themantic Network Project (IST–2001–34229) financed by European Union (EU). The aim of UEML is to create working group that will involve in the 6th Frame Program to develop core UEML.

UML2 1.0

date : 2006/05/21

Domain : UML, EMF

Description : This metamodel has been extracted from the project UML2 (http://www.eclipse.org/uml2/). UML2 is an EMF-based implementation of the UML(TM) 2.x metamodel for the Eclipse platform. The objectives of this project are to provide a useable implementation of the metamodel to support the development of modeling tools, a common XMI schema to facilitate interchange of semantic models, test cases as a means of validating the specification, and validation rules as a means of defining and enforcing levels of compliance.

UMLDI Activity Graphs 0.1

date : 2006/02/21

Domain : UML

Description : This is a simplified metamodel of UML Activity Graphs diagram according to the UML Diagram Interchange standard. The source metamodel of UML is well described by the OMG. It has been voluntarily simplified to be used more easily.

UMLDI Collaborations 0.1

date : 2006/02/21

Domain : UML

Description : This is a simplified metamodel of UML Collaborations diagram according to the UML Diagram Interchange standard. The source metamodel of UML is well described by the OMG. It has been voluntarily simplified to be used more easily.

UMLDI ModelManagement 0.1

date : 2006/02/21

Domain : UML

Description : This is a simplified metamodel of UML Model Management diagram according to the UML Diagram Interchange standard. The source metamodel of UML is well described by the OMG. It has been voluntarily simplified to be used more easily.

UMLDI State Machine 0.1

date : 2006/02/21

Domain : UML

Description : This is a simplified metamodel of UML State Machines diagram according to the UML Diagram Interchange standard. The source metamodel of UML is well described by the OMG. It has been voluntarily simplified to be used more easily.

UMLDI Use Cases 0.1

date : 2006/02/21

Domain : UML

Description : This is a simplified metamodel of UML Use Cases diagram according to the UML Diagram Interchange standard. The source metamodel of UML is well described by the OMG. It has been voluntarily simplified to be used more easily.

UMLDI 1.1

date : 2005/03/18

Domain : UML

Description : This is a simplified UML metamodel according to the UML Diagram Interchange standard. The source metamodel of UML is well described by the OMG. It has been voluntarily simplified to be used more easily.

UML For Object Oriented Class Modeling 1.0

date : 2005/08/09

Domain : UML, MOF, Object-Oriented modeling

Description : This metamodel describes a subset of UML, third generation modeling and specification language. The UML represents a compilation of best engineering practices which have proven to be successful in modeling large, complex systems, especially at the architectural level. This metamodel exclusively focuses on object-oriented class modeling.

Unified Ontology Language 1.0

date : 2005/08/10

Domain : Ontology

Description : This metamodel describes Unified Ontology Language. An ontology is an explicit specification of a conceptualization. Formally, an ontology is the statement of a logical theory. We use common ontologies to describe ontological commitments for a set of agents so that they can communicate about a domain of discourse without necessarily operating on a globally shared theory. We say that an agent commits to an ontology if its observable actions are consistent with the definitions in the ontology. The Knowledge Level is a level of description of the knowledge of an agent that is independent of the symbol-level representation used internally by the agent. Knowledge is attributed to agents by observing their actions; an agent knows something if it acts as if it had the information and is acting rationally to achieve its goals. The actions of agents (including knowledge base servers and knowledge-based systems) can be seen through a tell and ask functional interface, where a client interacts with an agent by making logical assertions (tell), and posing queries (ask). Pragmatically, a common ontology defines the vocabulary with which queries and assertions are exchanged among agents. Ontological commitments are agreements to use the shared vocabulary in a coherent and consistent manner. The agents sharing a vocabulary need not share a knowledge base; each knows things the other does not, and an agent that commits to an ontology is not required to answer all queries that can be formulated in the shared vocabulary.

USECASE2 1.0

date : 2006/07/19

Domain :

Description : This KM3 file shows the requirements metamodel, which is an extension to the use case concept of UML. It relates a use case with interacting roles, scenarios that detail the use case, conditions for the use case, goals for the use case, and the requirements represented by the use case.

WfMC 0.1

date : 2005/08/09

Domain : Workflow Process

Description : This metamodel is inspired by the structure of WfMC (Workflow Management Coalition) process. A variety of different tools may be used to analyze, model, describe and document a business process. The workflow process definition interface defines a common interchange format, which supports the transfer of workflow process definitions between separate products. The interface also defines a formal separation between the development and run-time environments, enabling a process definition, generated by one modeling tool, to be used as input to a number of different workflow run-time products. A workflow process definition, generated by a build-time tool, is capable of interpretation in different workflow runtime products. Process definitions transferred between these products or stored in a separate repository are accessible via that common interchange format. To provide a common method to access and describe workflow definitions, a workflow process definition meta-data model has been established. This meta-data model identifies commonly used entities within a process definition. A variety of attributes describe the characteristics of this limited set of entities. Based on this model, vendor specific tools can transfer models via a common exchange format.

WorkDefinitions 0.1

date : 2005/08/10

Domain : Software Process

Description : This metamodel, inspired by the SPEM initiative, describes work definitions. A work definition is an abstract entity. It is a model element (stemming from the ModelElement package) that describes a work unity (that can be composed of other work definitions). It specifies the operations to apply on work products in a well-defined role context that will have to realize it. A work definition always comes together with constraints: Goals and Preconditions. Those constraints are defined as Boolean expressions over Work Products states related with the Work Definition. They indicate beginning and ending conditions for the execution of the Work Definition.

WSDL 0.1

date : 2005/08/11

Domain : Web Services

Description : This basic metamodel describes a part of WSDL. WSDL (Web Services Description Language) is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate. WSDL service definitions provide documentation for distributed systems and serve as a recipe for automating the details involved in applications communication. A WSDL document defines services as collections of network endpoints, or ports. In WSDL, the abstract definition of endpoints and messages is separated from their concrete network deployment or data format bindings.This allows the reuse of abstract definitions: messages, which are abstract descriptions of the data being exchanged, and port types which are abstract collections of operations. The concrete protocol and data format specifications for a particular port type constitutes a reusable binding. A port is defined by associating a network address with a reusable binding, and a collection of ports define a service. Hence, a WSDL document uses the following elements in the definition of network services: Types- a container for data type definitions using some type system (such as XSD). Message- an abstract, typed definition of the data being communicated. Operation- an abstract description of an action supported by the service. Port Type- an abstract set of operations supported by one or more endpoints. Binding- a concrete protocol and data format specification for a particular port type. Port- a single endpoint defined as a combination of a binding and a network address. Service- a collection of related endpoints.

XHTML 1.0

date : 2005/06/23

Domain : HTML, XML

Description : This metamodel partially describes the Extensible HyperText Markup Language version 1.0 strict (XHTML). It is based on the W3C DTD named xhtml1-strict.dtd. This specification defines the Second Edition of XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4. These semantics provide the foundation for future extensibility of XHTML. Compatibility with existing HTML user agents is possible by following a small set of guidelines.

XML 1.1

date : 2005/06/13

Domain : XML

Description : This metamodel defines a subset of the Extensible Markup Language (XML). It describes an XML document with one root node. Node is an abstract class having two direct children, namely ElementNode and AttributeNode. ElementNode represents the tags, for example a tag named xml: <xml></xml>. ElementNodes can be composed of many Nodes. AttributeNode represents attributes, which can be found in a tag, for example the attr attribute: <xml attr=value of attr/>. ElementNode has two sub classes, namely RootNode and TextNode. RootNode is the root element. The TextNode is a particular node, which does not look like a tag; it is only a string of characters.

XPDL 0.1

date : 2006/02/21

Domain : XML, Business Process

Description : XML Process Definition Language (XPDL) is a format standardized by the WfMC to interchange Business Process definitions between different workflow products like modeling tools and workflow engines.

XQuery 1.1

date : 2005/06/13

Domain : XML

Description : This metamodel describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources. It contains also parts of the XML metamodel (Node, ElementNode, AttributeNode and TextNode). An XQueryProgram is composed of ExecutableExpressions which can be FLWOR expressions, function calls (FunctionCall) and function declarations (FunctionDeclaration). The main class is FLWOR, it represents FLWOR expressions which are composed of For, Let, Where, Order by and Return statements. For is composed of an XPath expression representing the value stored by the variable defined by the var attribute. Let is also composed of an XPath expression representing the value stored by the variable defined by the var attribute. Where is composed of a boolean XPath expression used to do a selection on the variables of the For statements. OrderBy is composed of an XPath expression defining how to order the output. Return is composed of Expressions representing the output data. Expression is the superclass of ExecutableExpressions, (XML-) Nodes and ReturnXPath expressions. The Node class and its sub classes are the same as those of the XML metamodel. There are two different XPath classes. In the ReturnXPath class the corresponding String expression (value) has to be put between braces, in the XPath class the expression is without braces.

XSchema 1.0

date : 2005/07/06

Domain : XML

Description : This basic metamodel describes XSchema. DTDs have limited expressiveness and it is necessary to experiment with new ideas in schema design. These ideas include a syntax that is more like that of XML document content, certain kinds of extensibility and a cleaner separation between parsing and verifying. XSchema is an experimental schema language designed to provide a starting point for these experiments.

XSLT 1.1

date : 2005/06/13

Domain : XML

Description : This metamodel describes XSLT which is a language for transforming XML documents into other XML documents. It is an extension of the XML metamodel. The main class is called XSLTNode and inherits from ElementNode. The XSLTNode class has sub classes representing XSLT elements, namely xsl:apply-templates, xsl:template, xsl:if, xsl:value-of. For reasons of simplification, several features such as xsl:for-each, xsl:choose, xsl:sort, xsl:copy-of elements have been ignored; this is why these are neither in the metamodel nor in the transformation code.

Measure 2.0

date : 2007/06/05

Domain : measurement data, metrics

Description : This metamodel is a representation of measurement data.

See : The measurement data are stored in sets of measures (MeasureSet). Each MeasureSet stores the data collected from one model element. The name and type of the model element are stored respectively in elementName and elementType of the MeasureSet. The reference subsets allow a hierarchy between the MeasureSets (the same as from the model measured). A measure (Measure) corresponds to a metric (Metric) (with a name and a description [desc]). The different metrics are also categorised (a category has a name and a description [desc]). The value of a measure can be an integer, a double or a percentage value (respectively IntegerMeasure, DoubleMeasure and PercentageMeasure).