Showing:

Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Used by
Element xmcda:function / constant
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_integer XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_real XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_interval XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_rational XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_label XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_boolean XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_NA XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_fuzzyNumber XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_valuedLabel XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_integer XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_real XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_rational XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_NA XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue
Type xmcda:numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
 
<constant id="" mcdaConcept="" name="">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</constant>
Attributes
QName Type Use Annotation
id xs:string optional 
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional 
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional 
The name attribute contains the human readable name of the object or concept.
Source
 
<xs:element name="constant" type="xmcda:numericValue"/>
Element xmcda:function / affine
Namespace No namespace
Annotations
 
Affine function. Requires a slope and an intercept.
Diagram
Diagram XMCDA-3_1_1_xsd_Complex_Type_xmcda_function.tmp#function_function_affine_slope XMCDA-3_1_1_xsd_Complex_Type_xmcda_function.tmp#function_function_affine_intercept
Properties
content complex
Model
Children intercept, slope
Instance
 
<affine>
  <slope id="" mcdaConcept="" name="">{1,1}</slope>
  <intercept id="" mcdaConcept="" name="">{1,1}</intercept>
</affine>
Source
 
<xs:element name="affine">
  <xs:annotation>
    <xs:documentation>Affine function. Requires a slope and an intercept.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="slope" type="xmcda:numericValue"/>
      <xs:element name="intercept" type="xmcda:numericValue"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element xmcda:function / affine / slope
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_integer XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_real XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_interval XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_rational XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_label XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_boolean XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_NA XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_fuzzyNumber XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_valuedLabel XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_integer XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_real XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_rational XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_NA XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue
Type xmcda:numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
 
<slope id="" mcdaConcept="" name="">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</slope>
Attributes
QName Type Use Annotation
id xs:string optional 
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional 
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional 
The name attribute contains the human readable name of the object or concept.
Source
 
<xs:element name="slope" type="xmcda:numericValue"/>
Element xmcda:function / affine / intercept
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_integer XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_real XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_interval XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_rational XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_label XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_boolean XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_NA XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_fuzzyNumber XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_valuedLabel XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_integer XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_real XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_rational XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue_NA XMCDA-3_1_1_xsd_Complex_Type_xmcda_numericValue.tmp#numericValue
Type xmcda:numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
 
<intercept id="" mcdaConcept="" name="">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</intercept>
Attributes
QName Type Use Annotation
id xs:string optional 
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional 
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional 
The name attribute contains the human readable name of the object or concept.
Source
 
<xs:element name="intercept" type="xmcda:numericValue"/>
Element xmcda:function / piecewiseLinear
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Complex_Type_xmcda_piecewiseLinear.tmp#piecewiseLinear_segment XMCDA-3_1_1_xsd_Complex_Type_xmcda_piecewiseLinear.tmp#piecewiseLinear
Type xmcda:piecewiseLinear
Properties
content complex
Model
Children segment
Instance
 
<piecewiseLinear>
  <segment>{1,unbounded}</segment>
</piecewiseLinear>
Source
 
<xs:element name="piecewiseLinear" type="xmcda:piecewiseLinear"/>
Element xmcda:function / discrete
Namespace No namespace
Annotations
 
A discrete function defined by a sequence of points.
Diagram
Diagram XMCDA-3_1_1_xsd_Complex_Type_xmcda_function.tmp#function_function_discrete_point
Properties
content complex
Model
Children point
Instance
 
<discrete>
  <point>{1,unbounded}</point>
</discrete>
Source
 
<xs:element name="discrete">
  <xs:annotation>
    <xs:documentation>A discrete function defined by a sequence of points.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="point" type="xmcda:point" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element xmcda:function / discrete / point
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Complex_Type_xmcda_point.tmp#point_abscissa XMCDA-3_1_1_xsd_Complex_Type_xmcda_point.tmp#point_ordinate XMCDA-3_1_1_xsd_Complex_Type_xmcda_point.tmp#point
Type xmcda:point
Properties
content complex
maxOccurs unbounded
Model
Children abscissa, ordinate
Instance
 
<point>
  <abscissa id="" mcdaConcept="" name="">{1,1}</abscissa>
  <ordinate id="" mcdaConcept="" name="">{1,1}</ordinate>
</point>
Source
 
<xs:element name="point" type="xmcda:point" maxOccurs="unbounded"/>
Complex Type xmcda:function
Namespace http://www.decision-deck.org/2019/XMCDA-3.1.1
Annotations
 
A general function which can be of one of the following four types: either a constant, an affine function (defined by a slope and an intercept), a piecewise linear function (defined by a sequence of segments), or a set of points.
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_function.tmp#function_constant XMCDA-3_1_1_xsd_Complex_Type_xmcda_function.tmp#function_affine XMCDA-3_1_1_xsd_Complex_Type_xmcda_function.tmp#function_piecewiseLinear XMCDA-3_1_1_xsd_Complex_Type_xmcda_function.tmp#function_discrete
Used by
Model
Children affine, constant, discrete, piecewiseLinear
Attributes
QName Type Use Annotation
id xs:string optional 
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional 
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional 
The name attribute contains the human readable name of the object or concept.
Source
 
<xs:complexType name="function">
  <xs:annotation>
    <xs:documentation>A general function which can be of one of the following four types: either a constant, an affine function (defined by a slope and an intercept), a piecewise linear function (defined by a sequence of segments), or a set of points.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="constant" type="xmcda:numericValue"/>
    <xs:element name="affine">
      <xs:annotation>
        <xs:documentation>Affine function. Requires a slope and an intercept.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="slope" type="xmcda:numericValue"/>
          <xs:element name="intercept" type="xmcda:numericValue"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="piecewiseLinear" type="xmcda:piecewiseLinear"/>
    <xs:element name="discrete">
      <xs:annotation>
        <xs:documentation>A discrete function defined by a sequence of points.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="point" type="xmcda:point" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:choice>
  <xs:attributeGroup ref="xmcda:defaultAttributes"/>
</xs:complexType>