Editing Modeling language (section)

=== More specific types ===
In the field of [[computer science]] recently more specific types of modeling languages have emerged.

==== Algebraic ====
[[Algebraic modeling language|Algebraic Modeling Languages]] (AML) are high-level programming languages for describing and solving high complexity problems for large scale mathematical computation (i.e. large scale optimization type problems). One particular advantage of AMLs like [[AIMMS]], [[AMPL]], [[General Algebraic Modeling System|GAMS]], [[Gekko (optimization software)|Gekko]], [[FICO Xpress|Mosel]], [[OPL Development Studio|OPL]], [[MiniZinc]], and [[OptimJ]] is the similarity of its syntax to the mathematical notation of optimization problems. This allows for a very concise and readable definition of problems in the domain of optimization, which is supported by certain language elements like sets, indices, algebraic expressions, powerful sparse index and data handling variables, constraints with arbitrary names. The algebraic formulation of a model does not contain any hints how to process it.

==== Behavioral ====

Behavioral languages are designed to describe the observable behavior of complex systems consisting of components that
execute concurrently. These languages focus on the description of key concepts such as: concurrency, nondeterminism, synchronization, and communication. The semantic foundations of Behavioral languages are [[process calculus]] or [[process algebra]].

==== Discipline-specific ====
A [[Service-oriented modeling#Discipline-specific modeling|discipline-specific modeling (DspM)]] language is focused on deliverables affiliated with a specific software development life cycle stage. Therefore, such language offers a distinct vocabulary, syntax, and notation for each stage, such as discovery, analysis, design, architecture, contraction, etc. For example, for the analysis phase of a project, the modeler employs specific analysis notation to deliver an analysis proposition diagram. During the design phase, however, logical design notation is used to depict the relationship between software entities. In addition, the discipline-specific modeling language best practices does not preclude practitioners from combining the various notations in a single diagram.

==== Domain-specific ====
[[Domain-specific modeling]] (DSM) is a software engineering methodology for designing and developing systems, most often IT systems such as computer software. It involves the systematic use of a graphical [[domain-specific language]] (DSL) to represent the various facets of a system. DSM languages tend to support higher-level abstractions than General-purpose modeling languages, so they require less effort and fewer low-level details to specify a given system.

==== Framework-specific ====
A [[framework-specific modeling language]] (FSML) is a kind of domain-specific modeling language which is designed for an object-oriented application framework. FSMLs define framework-provided abstractions as FSML concepts and decompose the abstractions into features. The features represent implementation steps or choices.

A FSML concept can be configured by selecting features and providing values for features. Such a concept configuration represents how the concept should be implemented in the code. In other words, concept configuration describes how the framework should be completed in order to create the implementation of the concept.

==== Information and knowledge modeling ====
[[Linked data]] and [[ontology engineering]] require 'host languages' to represent [[Entity–relationship model|entities and the relations between them]], [[Constraint (mathematics)|constraints]] between the properties of entities and relations, and [[metadata]] [[attribute (computing)|attributes]]. [[JSON-LD]] and [[Resource Description Framework|RDF]] are two major (and semantically almost equivalent) languages in this context, primarily because they support [[Resource Description Framework#Statement reification and context|statement reification and contextualisation]] which are essential properties to support the [[higher-order logic]] needed to reason about models. [[Model transformation]] is a common example of such reasoning.

==== Object-oriented ====
[[Object modeling language]]s are modeling languages based on a standardized set of symbols and ways of arranging them to model (part of) an object oriented software design or system design.

Some organizations use them extensively in combination with a software development methodology to progress from initial specification to an implementation plan and to communicate that plan to an entire team of developers and stakeholders. Because a modeling language is visual and at a higher-level of abstraction than code, using models encourages the generation of a shared vision that may prevent problems of differing interpretation later in development. Often software modeling tools are used to construct these models, which may then be capable of automatic translation to code.

==== Virtual reality ====
[[VRML|Virtual Reality Modeling Language]] (VRML), before 1995 known as the Virtual Reality Markup Language is a standard file format for representing 3-dimensional (3D) interactive vector graphics, designed particularly with the World Wide Web in mind.

==== Others ====
* [[Architecture Description Language]]
* [[Face Modeling Language]]
* [[Generative Modelling Language]]
* [[Java Modeling Language]]
* [[Promela]]
* [[Rebeca Modeling Language]]
* [[Service Modeling Language]]
* [[Web Services Modeling Language]]
* [[X3D]]