| Developed by | Giovanni Acampora |
|---|---|
| Type of format | Markup language |
| Extended from | XML |
| Standard | IEEE 1855-2016 |
Fuzzy Markup Language (FML) is a specific purpose markup language based on XML, used for describing the structure and behavior of a fuzzy system independently of the hardware architecture devoted to host and run it.
FML was designed and developed by Giovanni Acampora during his Ph.D. course in Computer Science, at University of Salerno, Italy, in 2004. The original idea inspired Giovanni Acampora to create FML was the necessity of creating a cooperative fuzzy-based framework aimed at automatically controlling a living environment characterized by a plethora of heterogeneous devices whose interactions were devoted to maximize the human comfort under energy saving constraints. This framework represented one of the first concrete examples of Ambient Intelligence. Beyond this pioneering application, the major advantage of using XML to describe a fuzzy system is hardware/software interoperability. Indeed, all that is needed to read an FML file is the appropriate schema for that file, and an FML parser. This markup approach makes it much easier to exchange fuzzy systems between software: for example, a machine learning application could extract fuzzy rules which could then be read directly into a fuzzy inference engine or uploaded into a fuzzy controller. Also, with technologies like XSLT, it is possible to compile the FML into the programming language of your choice, ready for embedding into whatever application you please. As stated by Mike Watts on his popular Computational Intelligence blog:[1]
"Although Acampora's motivation for developing FML seems to be to develop embedded fuzzy controllers for ambient intelligence applications, FML could be a real boon for developers of fuzzy rule extraction algorithms: from my own experience during my PhD, I know that having to design a file format and implement the appropriate parsers for rule extraction and fuzzy inference engines can be a real pain, taking as much time as implementing the rule extraction algorithm itself. I would much rather have used something like FML for my work."
A complete overview of FML and related applications can be found in the book titled On the power of Fuzzy Markup Language[2] edited by Giovanni Acampora, Chang-Shing Lee, Vincenzo Loia and Mei-Hui Wang, and published by Springer in the series Studies on Fuzziness and Soft Computing.
FML allows fuzzy systems to be coded through a collection of correlated semantic tags capable of modeling the different components of a classical fuzzy controller such as knowledge base, rule base, fuzzy variables and fuzzy rules. Therefore, the FML tags used to build a fuzzy controller represent the set of lexemes used to create fuzzy expressions. In order to design a well-formed XML-based language, an FML context-free grammar is defined by means of a XML schema which defines name, type and attributes characterized each XML element. However, since an FML program represents only a static view of a fuzzy logic controller, the so-called eXtensible Stylesheet Language Translator (XSLT) is provided to change this static view to a computable version. Indeed, XSLTs modules are able to convert the FML-based fuzzy controller in a general purpose computer language using an XSL file containing the translation description. At this level, the control is executable for the hardware. In short, FML is essentially composed by three layers:
FML syntax is composed of XML tags and attributes which describe the different components of a fuzzy logic controller listed below:
In detail, the opening tag of each FML program is <fuzzySystem> which represents the fuzzy controller under modeling. This tag has two attributes: name and ip. The first attribute permits to specify the name of fuzzy controller and ip is used to define the location of controller in a computer network. The fuzzy knowledge base is defined by means of the tag <KnowledgeBase> which maintains the set of fuzzy concepts used to model the fuzzy rule base. In order to define the fuzzy
concept related controlled system, <KnowledgeBase> tag uses a set of nested tags:
<FuzzyVariable> defines the fuzzy concept;<FuzzyTerm> defines a linguistic term describing the fuzzy concept;The attributes of <FuzzyVariable> tag are: name, scale, domainLeft, domainRight, type and, for only an output, accumulation, defuzzifier and defaultValue. The name attribute defines the name of fuzzy concept, for instance, temperature; scale is used to define the scale used to measure the fuzzy concept, for instance, Celsius degree; domainLeft and domainRight are used to model the universe of discourse of fuzzy concept, that is, the set of real values related to fuzzy concept, for instance [0°,40°] in the case of Celsius degree; the position of fuzzy concept into rule (consequent part or antecedent part) is defined by type attribute (input/output); accumulation attribute defines the method of accumulation that is a method that permits the combination of results of a variable of each rule in a final result; defuzzifier attribute defines the method used to execute the conversion from a fuzzy set, obtained after aggregation process, into a numerical value to give it in output to system; defaultValue attribute defines a real value used only when no rule has fired for the variable at issue.
As for tag <FuzzyTerm>, it uses two attributes: name used to identify the linguistic value associate with fuzzy concept and complement, a boolean attribute that defines, if it is true, it is necessary to consider the complement of membership function defined by given parameters. Fuzzy shape tags, used to complete the definition of fuzzy concept, are:
<TRIANGULARSHAPE><RIGHTLINEARSHAPE><LEFTLINEARSHAPE><PISHAPE><GAUSSIANSHAPE><RIGHTGAUSSIANSHAPE><LEFTGAUSSIANSHAPE><TRAPEZOIDSHAPE><SSHAPE><ZSHAPE><RECTANGULARSHAPE><SINGLETONSHAPE>Every shaping tag uses a set of attributes which defines the real outline of corresponding fuzzy set. The number of these attributes depends on the chosen fuzzy set shape.
In order to make an example, consider the Tipper Inference System described in Mathworks Matlab Fuzzy Logic Toolbox Tutorial. This Mamdani system is used to regulate the tipping in, for example, a restaurant. It has got two variables in input (food and service) and one in output (tip). FML code for modeling part of knowledge base of this fuzzy system containing variables food and tip is shown below.
<?xml version="1.0" encoding="UTF-8"?>
<fuzzySystem name="newSystem" ip="127.0.0.1">
<KnowledgeBase>
<FuzzyVariable name="food" domainleft="0.0" domainright="10.0" scale="" type="input">
<FuzzyTerm name="delicious" complement="false">
<LeftLinearShape Param1="5.5" Param2="10.0"/>
</FuzzyTerm>
<FuzzyTerm name="rancid" complement="false">
<TriangularShape Param1="0.0" Param2="2.0" Param3="5.5"/>
</FuzzyTerm>
</FuzzyVariable>
...........
<FuzzyVariable name="tip" domainleft="0.0" domainright="20.0" scale="Euro" defaultValue="0.0" defuzzifier="COG"
accumulation="MAX" type="output">
<FuzzyTerm name="average" complement="false">
<TriangularShape Param1="5.0" Param2="10.0" Param3="15.0"/>
</FuzzyTerm>
<FuzzyTerm name="cheap" complement="false">
<TriangularShape Param1="0.0" Param2="5.0" Param3="10.0"/>
</FuzzyTerm>
<FuzzyTerm name="generous" complement="false">
<TriangularShape Param1="10.0" Param2="15.0" Param3="20.0"/>
</FuzzyTerm>
</FuzzyVariable>
</KnowledgeBase>
............
</fuzzySystem>
A special tag that can furthermore be used to define a fuzzy shape is <UserShape>. This tag is used to customize fuzzy shape (custom shape). The custom shape modeling is performed via a set of <Point> tags that lists the extreme points of geometric area defining the custom fuzzy shape. Obviously, the attributes used in <Point> tag are x and y coordinates.
As for rule base component, FML allows to define a set of rule bases, each one of them describes a different behavior of system. The root of each rule base is modeled by <RuleBase> tag which defines a fuzzy rule set. The <RuleBase> tag uses five attributes: name, type, activationMethod, andMethod and orMethod. Obviously, the name attribute uniquely identifies the rule base. The type attribute permits to specify the kind of fuzzy controller (Mamdani or TSK) respect to the rule base at issue. The activationMethod attribute defines the method used to implication process; the andMethod and orMethod attribute define, respectively, the and and or algorithm to use by default. In order to define the single rule the <Rule> tag is used. The attributes used by the <Rule> tag are: name, connector, operator and weight. The name attribute permits to identify the rule; connector is used to define the logical operator used to connect the different clauses in antecedent part (and/or); operator defines the algorithm to use for chosen connector; weight defines the importance of rule during inference engine step. The definition of antecedent and consequent rule part is obtained by using <Antecedent> and <Consequent> tags. <Clause> tag is used to model the fuzzy clauses in antecedent and consequent part. This tag use the attribute modifier to describe a modification to term used in the clause. The possible values for this attribute are: above, below, extremely, intensify, more or less, norm, not, plus, slightly, somewhat, very, none. To complete the definition of fuzzy clause the nested <Variable> and <Term> tags have to be used. A sequence of <Rule> tags realizes a fuzzy rule base.
As example, consider a Mamdani rule composed by (food is rancid) OR (service is very poor) as antecedent and tip is cheap as consequent. The antecedent part is formed by two clauses: (food is rancid) and (service is poor). The first antecedent clause uses food as variable and rancid as fuzzy term, whereas, the second antecedent clause uses service as a variable, poor as fuzzy term and very as modifier; the consequent clause uses tip as a fuzzy variable and cheap as a fuzzy term. The complete rule is:
IF (food is rancid) OR (service is very poor) THEN (tip is cheap).
Let us see how FML defines a rule base with this rule.
<RuleBase name="Rulebase1" activationMethod="MIN" andMethod="MIN" orMethod="MAX" type="mamdani">
<Rule name="reg1" connector="or" operator="MAX" weight="1.0">
<Antecedent>
<Clause>
<Variable>food</Variable>
<Term>rancid</Term>
</Clause>
<Clause modifier="very">
<Variable>service</Variable>
<Term>poor</Term>
</Clause>
</Antecedent>
<Consequent>
<Clause>
<Variable>tip</Variable>
<Term>cheap</Term>
</Clause>
</Consequent>
</Rule>
............
</RuleBase>
Now, let us see a Takagi-Sugeno-Kang system that regulates the same issue. The most important difference with Mamdani system is the definition of a different output variable tip. The <TSKVariable> tag is used to define an output variable that can be used in a rule of a Tsk system. This tag has the same attributes of a Mamdani output variable except for the domainleft and domainright attribute because a variable of this kind (called tsk-variable) hasn't a universe of discourse. The nested <TSKTerm> tag represents a linear function and so it is completely different from <FuzzyTerm>. The <TSKValue> tag is used to define the coefficients of linear function. The following crunch of FML code shows the definition of output variable tip in a Tsk system.
<?xml version="1.0" encoding="UTF-8"?>
<fuzzySystem name="newSystem" ip="127.0.0.1">
<KnowledgeBase>
.......
<TSKVariable name="tip" scale="null" accumulation="MAX" defuzzifier="WA" type="output">
<TSKTerm name="average" order="0">
<TSKValue>1.6</TSKValue>
</TSKTerm>
<TSKTerm name="cheap" order="1">
<TSKValue>1.9</TSKValue>
<TSKValue>5.6</TSKValue>
<TSKValue>6.0</TSKValue>
</TSKTerm>
<TSKTerm name="generous" order="1">
<TSKValue>0.6</TSKValue>
<TSKValue>1.3</TSKValue>
<TSKValue>1.0</TSKValue>
</TSKTerm>
</TSKVariable>
<KnowledgeBase>
..........
</fuzzySystem >
The FML definition of rule base component in a Tsk system doesn't change a lot. The only different thing is that the <Clause> tag doesn't have the modifier attribute.
As example, consider a tsk rule composed by (food is rancid) OR (service is very poor) as antecedent and, as consequent, tip=1.9+5.6*food+6.0*service that can be written as tip is cheap in an implicitly way. So the rule can be written in this way:
IF (food is rancid) OR (service is very poor) THEN (tip is cheap).
Let us see how FML defines a rule base with this rule.
<RuleBase name="Rulebase1" activationMethod="MIN" andMethod="MIN" orMethod="MAX" type="tsk">
<Rule name="reg1" connector="or" operator="MAX" weight="1.0">
<Antecedent>
<Clause>
<Variable>food</Variable>
<Term>rancid</Term>
</Clause>
<Clause>
<Variable>service</Variable>
<Term>poor</Term>
</Clause>
</Antecedent>
<Consequent>
<Clause>
<Variable>tip</Variable>
<Term>cheap</Term>
</Clause>
</Consequent>
</Rule>
............
</RuleBase>
The FML tags used to build a fuzzy controller represent the set of lexemes used to create fuzzy expressions. However, in order to realize a well-formed XML-based language, an FML context-free grammar is necessary and described in the following. The FML context-free grammar is modeled by XML file in the form of a XML Schema Document (XSD) which expresses the set of rules to which a document must conform in order to be considered a valid FML document. Based on the previous definition, a portion of the FML XSD regarding the knowledge base definition is given below.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
........
<xs:complexType name="KnowledgeBaseType">
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="FuzzyVariable" type="FuzzyVariableType"/>
<xs:element name="TSKVariable" type="TSKVariableType"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
<xs:complexType name="FuzzyVariableType">
<xs:sequence>
<xs:element name="FuzzyTerm" type="FuzzyTermType" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="defuzzifier" default="COG">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="MM|COG|COA|WA|Custom"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="accumulation" default="MAX">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="MAX|SUM"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="scale" type="xs:string" />
<xs:attribute name="domainleft" type="xs:float" use="required"/>
<xs:attribute name="domainright" type="xs:float" use="required"/>
<xs:attribute name="defaultValue" type="xs:float" default="0"/>
<xs:attribute name="type" default="input">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="input|output"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
<xs:complexType name="FuzzyTermType">
<xs:choice>
<xs:element name="RightLinearShape" type="TwoParamType"/>
<xs:element name="LeftLinearShape" type="TwoParamType"/>
<xs:element name="PIShape" type="TwoParamType"/>
<xs:element name="TriangularShape" type="ThreeParamType"/>
<xs:element name="GaussianShape" type="TwoParamType"/>
<xs:element name="RightGaussianShape" type="TwoParamType"/>
<xs:element name="LeftGaussianShape" type="TwoParamType"/>
<xs:element name="TrapezoidShape" type="FourParamType"/>
<xs:element name="SingletonShape" type="OneParamType"/>
<xs:element name="RectangularShape" type="TwoParamType"/>
<xs:element name="ZShape" type="TwoParamType"/>
<xs:element name="SShape" type="TwoParamType"/>
<xs:element name="UserShape" type="UserShapeType"/>
</xs:choice>
<xs:complexType name="TwoParamType">
<xs:attribute name="Param1" type="xs:float" use="required"/>
<xs:attribute name="Param2" type="xs:float" use="required"/>
</xs:complexType>
<xs:complexType name="ThreeParamType">
<xs:attribute name="Param1" type="xs:float" use="required"/>
<xs:attribute name="Param2" type="xs:float" use="required"/>
<xs:attribute name="Param3" type="xs:float" use="required"/>
</xs:complexType>
<xs:complexType name="FourParamType">
<xs:attribute name="Param1" type="xs:float" use="required"/>
<xs:attribute name="Param2" type="xs:float" use="required"/>
<xs:attribute name="Param3" type="xs:float" use="required"/>
<xs:attribute name="Param4" type="xs:float" use="required"/>
</xs:complexType>
<xs:complexType name="UserShapeType">
<xs:sequence>
<xs:element name="Point" type="PointType" minOccurs="2" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="PointType">
<xs:attribute name="x" type="xs:float" use="required"/>
<xs:attribute name="y" type="xs:float" use="required"/>
</xs:complexType>
<xs:complexType name="RuleBaseType">
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="activationMethod" default="MIN">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="PROD|MIN"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="andMethod" default="MIN">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="PROD|MIN"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="orMethod" default="MAX">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="PROBOR|MAX"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="TSK|Tsk|tsk|Mamdani|mamdani"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
<xs:complexType name="MamdaniRuleBaseType">
<xs:complexContent>
<xs:extension base="RuleBaseType">
<xs:sequence>
<xs:element name="Rule" type="MamdaniFuzzyRuleType" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="AntecedentType">
<xs:sequence>
<xs:element name="Clause" type="ClauseType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="MamdaniConsequentType">
<xs:sequence>
<xs:element name="Clause" type="ClauseType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="ClauseType">
<xs:sequence>
<xs:element name="Variable">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:whiteSpace value="collapse"/>
<xs:pattern value="(([A-Z])|([a-z]))+([A-Z]|[a-z]|[0-9])*"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Term" type="xs:string">
</xs:element>
</xs:sequence>
<xs:attribute name="modifier" use="optional">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern
value="above|below|extremely|intensify|more_or_less|norm|not|plus|slightly|somewhat|very"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
..........
</xs:schema>
Since an FML program realizes only a static view of a fuzzy system, the so-called eXtensible Stylesheet Language Translator (XSLT) is provided to change this static view to a computable version. In particular, the XSLT technology is used convert a fuzzy controller description into a general-purpose computer language to be computed on several hardware platforms. Currently, a XSLT converting FML program in runnable Java code has been implemented. In this way, thanks to the transparency capabilities provided by Java virtual machines, it is possible to obtain a fuzzy controller modeled in high level way by means of FML and runnable on a plethora of hardware architectures through Java technologies. However, XSLT can be also used for converting FML programs in legacy languages related to a particular hardware or in other general purpose languages.