Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Model
Properties
Source
Used by
Element xmcda:threshold / 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:threshold / affine
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Complex_Type_xmcda_threshold.tmp#threshold_threshold_affine_type XMCDA-3_1_1_xsd_Complex_Type_xmcda_threshold.tmp#threshold_threshold_affine_slope XMCDA-3_1_1_xsd_Complex_Type_xmcda_threshold.tmp#threshold_threshold_affine_intercept
Properties
content complex
Model
Children intercept, slope, type
Instance
 
<affine>
  <type>{0,1}</type>
  <slope id="" mcdaConcept="" name="">{1,1}</slope>
  <intercept id="" mcdaConcept="" name="">{1,1}</intercept>
</affine>
Source
 
<xs:element name="affine">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="type" minOccurs="0" maxOccurs="1">
        <xs:simpleType>
          <xs:annotation>
            <xs:documentation>The type of the affine threshold : either direct when the evaluation of the best of the 2 alternatives is taken into account in the affine formula, or inverse when the evaluation of the worst alternative is considered in the formula. If not present, it is assumed that the type is direct.</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
            <xs:enumeration value="direct"/>
            <xs:enumeration value="inverse"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="slope" type="xmcda:numericValue" minOccurs="1" maxOccurs="1"/>
      <xs:element name="intercept" type="xmcda:numericValue" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element xmcda:threshold / affine / type
Namespace No namespace
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
enumeration direct
enumeration inverse
Source
 
<xs:element name="type" minOccurs="0" maxOccurs="1">
  <xs:simpleType>
    <xs:annotation>
      <xs:documentation>The type of the affine threshold : either direct when the evaluation of the best of the 2 alternatives is taken into account in the affine formula, or inverse when the evaluation of the worst alternative is considered in the formula. If not present, it is assumed that the type is direct.</xs:documentation>
    </xs:annotation>
    <xs:restriction base="xs:string">
      <xs:enumeration value="direct"/>
      <xs:enumeration value="inverse"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element xmcda:threshold / 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
minOccurs 1
maxOccurs 1
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" minOccurs="1" maxOccurs="1"/>
Element xmcda:threshold / 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
minOccurs 1
maxOccurs 1
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" minOccurs="1" maxOccurs="1"/>
Complex Type xmcda:threshold
Namespace http://www.decision-deck.org/2019/XMCDA-3.1.1
Annotations
 
Discrimination threshold (used to represent preferences on criteria).
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_threshold.tmp#threshold_constant XMCDA-3_1_1_xsd_Complex_Type_xmcda_threshold.tmp#threshold_affine
Used by
Model
Children affine, 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:complexType name="threshold">
  <xs:annotation>
    <xs:documentation>Discrimination threshold (used to represent preferences on criteria).</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="constant" type="xmcda:numericValue"/>
    <xs:element name="affine">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="type" minOccurs="0" maxOccurs="1">
            <xs:simpleType>
              <xs:annotation>
                <xs:documentation>The type of the affine threshold : either direct when the evaluation of the best of the 2 alternatives is taken into account in the affine formula, or inverse when the evaluation of the worst alternative is considered in the formula. If not present, it is assumed that the type is direct.</xs:documentation>
              </xs:annotation>
              <xs:restriction base="xs:string">
                <xs:enumeration value="direct"/>
                <xs:enumeration value="inverse"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
          <xs:element name="slope" type="xmcda:numericValue" minOccurs="1" maxOccurs="1"/>
          <xs:element name="intercept" type="xmcda:numericValue" minOccurs="1" maxOccurs="1"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:choice>
  <xs:attributeGroup ref="xmcda:defaultAttributes"/>
</xs:complexType>