Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Model
Properties
Source
Used by
Main schema XMCDA-4.0.0.xsd
Annotations
XMCDA v4.0.0 Schema - Copyright (c) Decision Deck Consortium, 2020-2021
by Sébastien BIGARET and Patrick MEYER (IMT Atlantique)
Based on the previous works:
- XMCDA 3.x (2013-2019) by Sébastien BIGARET and Patrick MEYER (IMT Atlantique)
- XMCDA 2.x (2009-2012) by Raymond BISDORFF (University of Luxembourg), Patrick MEYER (Telecom Bretagne), Thomas Veneziano (University of Luxembourg), who formalised the collective work of the Decision Deck Consortium.
Properties
attribute form default unqualified
element form default qualified
Element xmcda
Annotations
Root of the XMCDA tree.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#xmcda_alternatives XMCDA-4_0_0_xsd.tmp#xmcda_alternativesSets XMCDA-4_0_0_xsd.tmp#xmcda_criteria XMCDA-4_0_0_xsd.tmp#xmcda_criteriaSets XMCDA-4_0_0_xsd.tmp#xmcda_performanceTable XMCDA-4_0_0_xsd.tmp#xmcda_categories XMCDA-4_0_0_xsd.tmp#xmcda_categoriesSets XMCDA-4_0_0_xsd.tmp#xmcda_alternativesAssignments XMCDA-4_0_0_xsd.tmp#xmcda_alternativesCriteriaValues XMCDA-4_0_0_xsd.tmp#xmcda_alternativesLinearConstraints XMCDA-4_0_0_xsd.tmp#xmcda_alternativesMatrix XMCDA-4_0_0_xsd.tmp#xmcda_alternativesValues XMCDA-4_0_0_xsd.tmp#xmcda_alternativesSetsLinearConstraints XMCDA-4_0_0_xsd.tmp#xmcda_alternativesSetsMatrix XMCDA-4_0_0_xsd.tmp#xmcda_alternativesSetsValues XMCDA-4_0_0_xsd.tmp#xmcda_criteriaFunctions XMCDA-4_0_0_xsd.tmp#xmcda_criteriaHierarchy XMCDA-4_0_0_xsd.tmp#xmcda_criteriaLinearConstraints XMCDA-4_0_0_xsd.tmp#xmcda_criteriaMatrix XMCDA-4_0_0_xsd.tmp#xmcda_criteriaScales XMCDA-4_0_0_xsd.tmp#xmcda_criteriaThresholds XMCDA-4_0_0_xsd.tmp#xmcda_criteriaValues XMCDA-4_0_0_xsd.tmp#xmcda_criteriaSetsHierarchy XMCDA-4_0_0_xsd.tmp#xmcda_criteriaSetsLinearConstraints XMCDA-4_0_0_xsd.tmp#xmcda_criteriaSetsMatrix XMCDA-4_0_0_xsd.tmp#xmcda_criteriaSetsValues XMCDA-4_0_0_xsd.tmp#xmcda_categoriesLinearConstraints XMCDA-4_0_0_xsd.tmp#xmcda_categoriesMatrix XMCDA-4_0_0_xsd.tmp#xmcda_categoriesProfiles XMCDA-4_0_0_xsd.tmp#xmcda_categoriesValues XMCDA-4_0_0_xsd.tmp#xmcda_categoriesSetsLinearConstraints XMCDA-4_0_0_xsd.tmp#xmcda_categoriesSetsMatrix XMCDA-4_0_0_xsd.tmp#xmcda_categoriesSetsValues XMCDA-4_0_0_xsd.tmp#xmcda_programParameters XMCDA-4_0_0_xsd.tmp#xmcda_programExecutionResult
Properties
content complex
Model
Children alternatives, alternativesAssignments, alternativesCriteriaValues, alternativesLinearConstraints, alternativesMatrix, alternativesSets, alternativesSetsLinearConstraints, alternativesSetsMatrix, alternativesSetsValues, alternativesValues, categories, categoriesLinearConstraints, categoriesMatrix, categoriesProfiles, categoriesSets, categoriesSetsLinearConstraints, categoriesSetsMatrix, categoriesSetsValues, categoriesValues, criteria, criteriaFunctions, criteriaHierarchy, criteriaLinearConstraints, criteriaMatrix, criteriaScales, criteriaSets, criteriaSetsHierarchy, criteriaSetsLinearConstraints, criteriaSetsMatrix, criteriaSetsValues, criteriaThresholds, criteriaValues, performanceTable, programExecutionResult, programParameters
Instance
<xmcda xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternatives id="" mcdaConcept="" name="">{0,1}</alternatives>
  <alternativesSets id="" mcdaConcept="" name="">{0,1}</alternativesSets>
  <criteria id="" mcdaConcept="" name="">{0,1}</criteria>
  <criteriaSets id="" mcdaConcept="" name="">{0,1}</criteriaSets>
  <performanceTable id="" mcdaConcept="" name="">{0,unbounded}</performanceTable>
  <categories id="" mcdaConcept="" name="">{0,1}</categories>
  <categoriesSets id="" mcdaConcept="" name="">{0,1}</categoriesSets>
  <alternativesAssignments id="" mcdaConcept="" name="">{0,unbounded}</alternativesAssignments>
  <alternativesCriteriaValues id="" mcdaConcept="" name="">{0,unbounded}</alternativesCriteriaValues>
  <alternativesLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</alternativesLinearConstraints>
  <alternativesMatrix id="" mcdaConcept="" name="">{0,unbounded}</alternativesMatrix>
  <alternativesValues id="" mcdaConcept="" name="">{0,unbounded}</alternativesValues>
  <alternativesSetsLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</alternativesSetsLinearConstraints>
  <alternativesSetsMatrix id="" mcdaConcept="" name="">{0,unbounded}</alternativesSetsMatrix>
  <alternativesSetsValues id="" mcdaConcept="" name="">{0,unbounded}</alternativesSetsValues>
  <criteriaFunctions id="" mcdaConcept="" name="">{0,unbounded}</criteriaFunctions>
  <criteriaHierarchy id="" mcdaConcept="" name="">{0,unbounded}</criteriaHierarchy>
  <criteriaLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</criteriaLinearConstraints>
  <criteriaMatrix id="" mcdaConcept="" name="">{0,unbounded}</criteriaMatrix>
  <criteriaScales id="" mcdaConcept="" name="">{0,unbounded}</criteriaScales>
  <criteriaThresholds id="" mcdaConcept="" name="">{0,unbounded}</criteriaThresholds>
  <criteriaValues id="" mcdaConcept="" name="">{0,unbounded}</criteriaValues>
  <criteriaSetsHierarchy id="" mcdaConcept="" name="">{0,unbounded}</criteriaSetsHierarchy>
  <criteriaSetsLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</criteriaSetsLinearConstraints>
  <criteriaSetsMatrix id="" mcdaConcept="" name="">{0,unbounded}</criteriaSetsMatrix>
  <criteriaSetsValues id="" mcdaConcept="" name="">{0,unbounded}</criteriaSetsValues>
  <categoriesLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</categoriesLinearConstraints>
  <categoriesMatrix id="" mcdaConcept="" name="">{0,unbounded}</categoriesMatrix>
  <categoriesProfiles id="" mcdaConcept="" name="">{0,unbounded}</categoriesProfiles>
  <categoriesValues id="" mcdaConcept="" name="">{0,unbounded}</categoriesValues>
  <categoriesSetsLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</categoriesSetsLinearConstraints>
  <categoriesSetsMatrix id="" mcdaConcept="" name="">{0,unbounded}</categoriesSetsMatrix>
  <categoriesSetsValues id="" mcdaConcept="" name="">{0,unbounded}</categoriesSetsValues>
  <programParameters id="" mcdaConcept="" name="">{0,unbounded}</programParameters>
  <programExecutionResult id="" mcdaConcept="" name="">{0,unbounded}</programExecutionResult>
</xmcda>
Source
<xs:element name="xmcda">
  <xs:annotation>
    <xs:documentation>Root of the XMCDA tree.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <!-- Alternatives and alternatives sets -->
      <xs:element name="alternatives" type="alternatives" minOccurs="0" maxOccurs="1"/>
      <xs:element name="alternativesSets" type="alternativesSets" minOccurs="0" maxOccurs="1"/>
      <!-- Criteria and criteria sets -->
      <xs:element name="criteria" type="criteria" minOccurs="0" maxOccurs="1"/>
      <xs:element name="criteriaSets" type="criteriaSets" minOccurs="0" maxOccurs="1"/>
      <!-- Performance tables -->
      <xs:element name="performanceTable" type="performanceTable" minOccurs="0" maxOccurs="unbounded"/>
      <!-- Categories and categories sets -->
      <xs:element name="categories" type="categories" minOccurs="0" maxOccurs="1"/>
      <xs:element name="categoriesSets" type="categoriesSets" minOccurs="0" maxOccurs="1"/>
      <!-- Data linked to alternatives -->
      <xs:element name="alternativesAssignments" minOccurs="0" maxOccurs="unbounded" type="alternativesAssignments"/>
      <xs:element name="alternativesCriteriaValues" minOccurs="0" maxOccurs="unbounded" type="alternativesCriteriaValues"/>
      <xs:element name="alternativesLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="alternativesLinearConstraints"/>
      <xs:element name="alternativesMatrix" minOccurs="0" maxOccurs="unbounded" type="alternativesMatrix"/>
      <xs:element name="alternativesValues" minOccurs="0" maxOccurs="unbounded" type="alternativesValues"/>
      <!-- Data linked to alternatives sets -->
      <xs:element name="alternativesSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="alternativesSetsLinearConstraints"/>
      <xs:element name="alternativesSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="alternativesSetsMatrix"/>
      <xs:element name="alternativesSetsValues" minOccurs="0" maxOccurs="unbounded" type="alternativesSetsValues"/>
      <!-- Data linked to criteria -->
      <xs:element name="criteriaFunctions" type="criteriaFunctions" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="criteriaHierarchy" minOccurs="0" maxOccurs="unbounded" type="criteriaHierarchy"/>
      <xs:element name="criteriaLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="criteriaLinearConstraints"/>
      <xs:element name="criteriaMatrix" minOccurs="0" maxOccurs="unbounded" type="criteriaMatrix"/>
      <xs:element name="criteriaScales" type="criteriaScales" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="criteriaThresholds" type="criteriaThresholds" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="criteriaValues" minOccurs="0" maxOccurs="unbounded" type="criteriaValues"/>
      <!-- Data linked to criteria sets -->
      <xs:element name="criteriaSetsHierarchy" minOccurs="0" maxOccurs="unbounded" type="criteriaSetsHierarchy"/>
      <xs:element name="criteriaSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="criteriaSetsLinearConstraints"/>
      <xs:element name="criteriaSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="criteriaSetsMatrix"/>
      <xs:element name="criteriaSetsValues" minOccurs="0" maxOccurs="unbounded" type="criteriaSetsValues"/>
      <!-- Data linked to categories -->
      <xs:element name="categoriesLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="categoriesLinearConstraints"/>
      <xs:element name="categoriesMatrix" minOccurs="0" maxOccurs="unbounded" type="categoriesMatrix"/>
      <xs:element name="categoriesProfiles" minOccurs="0" maxOccurs="unbounded" type="categoriesProfiles"/>
      <xs:element name="categoriesValues" minOccurs="0" maxOccurs="unbounded" type="categoriesValues"/>
      <!-- Data linked to categories sets -->
      <xs:element name="categoriesSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="categoriesSetsLinearConstraints"/>
      <xs:element name="categoriesSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="categoriesSetsMatrix"/>
      <xs:element name="categoriesSetsValues" minOccurs="0" maxOccurs="unbounded" type="categoriesSetsValues"/>
      <!-- Data linked to algorithms -->
      <xs:element name="programParameters" type="programParameters" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="programExecutionResult" type="programExecutionResult" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element xmcda / alternatives
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternatives_description XMCDA-4_0_0_xsd.tmp#alternatives_alternative XMCDA-4_0_0_xsd.tmp#alternatives
Type alternatives
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children alternative, description
Instance
<alternatives id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <alternative id="" mcdaConcept="" name="">{1,unbounded}</alternative>
</alternatives>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternatives" type="alternatives" minOccurs="0" maxOccurs="1"/>
Element alternatives / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element description / author
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
<xs:element name="author" minOccurs="0" maxOccurs="unbounded" type="xs:string"/>
Element description / comment
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xs:element name="comment" minOccurs="0" maxOccurs="1" type="xs:string"/>
Element description / keyword
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
<xs:element name="keyword" minOccurs="0" maxOccurs="unbounded" type="xs:string"/>
Element description / bibliography
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#bibliography_description XMCDA-4_0_0_xsd.tmp#bibliography_bibEntry XMCDA-4_0_0_xsd.tmp#bibliography
Type bibliography
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children bibEntry, description
Instance
<bibliography id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <bibEntry>{0,unbounded}</bibEntry>
</bibliography>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="bibliography" minOccurs="0" maxOccurs="1" type="bibliography"/>
Element bibliography / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element description / creationDate
Diagram
Diagram
Type xs:dateTime
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xs:element name="creationDate" minOccurs="0" maxOccurs="1" type="xs:dateTime"/>
Element description / lastModificationDate
Diagram
Diagram
Type xs:dateTime
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xs:element name="lastModificationDate" minOccurs="0" maxOccurs="1" type="xs:dateTime"/>
Element bibliography / bibEntry
Annotations
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
<xs:element name="bibEntry" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation/>
  </xs:annotation>
</xs:element>
Element alternatives / alternative
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#alternative_description XMCDA-4_0_0_xsd.tmp#alternative_type XMCDA-4_0_0_xsd.tmp#alternative_active XMCDA-4_0_0_xsd.tmp#alternative
Type alternative
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children active, description, type
Instance
<alternative id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <type>{0,1}</type>
  <active>{0,1}</active>
</alternative>
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="alternative" type="alternative" minOccurs="1" maxOccurs="unbounded"/>
Element alternative / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element alternative / type
Annotations
Type Indicates whether an alternative is real or fictive. By default, if the tag is not present, an alternative is considered as real. Fictive alternatives are those which might not exist in reality, but can be used for some preference elicitation means.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
maxOccurs 1
default real
Facets
enumeration real
enumeration fictive
Source
<xs:element name="type" minOccurs="0" maxOccurs="1" default="real">
  <xs:annotation>
    <xs:documentation>Type Indicates whether an alternative is real or fictive. By default, if the tag is not present, an alternative is considered as real. Fictive alternatives are those which might not exist in reality, but can be used for some preference elicitation means.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="real"/>
      <xs:enumeration value="fictive"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element alternative / active
Annotations
Active indicates whether an alternative is active or not in the calculations. By default, if the tag is not present, an alternative is considered as active (true).
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
maxOccurs 1
default true
Source
<xs:element name="active" type="xs:boolean" minOccurs="0" maxOccurs="1" default="true">
  <xs:annotation>
    <xs:documentation>Active indicates whether an alternative is active or not in the calculations. By default, if the tag is not present, an alternative is considered as active (true).</xs:documentation>
  </xs:annotation>
</xs:element>
Element xmcda / alternativesSets
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSets_description XMCDA-4_0_0_xsd.tmp#alternativesSets_alternativesSet XMCDA-4_0_0_xsd.tmp#alternativesSets
Type alternativesSets
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children alternativesSet, description
Instance
<alternativesSets id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <alternativesSet id="" mcdaConcept="" name="">{0,unbounded}</alternativesSet>
</alternativesSets>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesSets" type="alternativesSets" minOccurs="0" maxOccurs="1"/>
Element alternativesSets / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesSets / alternativesSet
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#alternativesSet_description XMCDA-4_0_0_xsd.tmp#alternativesSet_element XMCDA-4_0_0_xsd.tmp#alternativesSet
Type alternativesSet
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, element
Instance
<alternativesSet id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <element>{0,unbounded}</element>
</alternativesSet>
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="alternativesSet" type="alternativesSet" minOccurs="0" maxOccurs="unbounded"/>
Element alternativesSet / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesSet / element
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativesSet_alternativesSet_element_alternativeID XMCDA-4_0_0_xsd.tmp#alternativesSet_alternativesSet_element_values
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativeID, values
Instance
<element xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <values>{0,1}</values>
</element>
Source
<xs:element name="element" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="alternativeID" type="xs:string"/>
      <xs:element name="values" minOccurs="0" maxOccurs="1" type="values"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element alternativesSet / element / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativeID" type="xs:string"/>
Element alternativesSet / element / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" minOccurs="0" maxOccurs="1" type="values"/>
Element values / value
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value
Type value
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
<value id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <interval>{1,1}</interval>
  <rational>{1,1}</rational>
  <label>{1,1}</label>
  <boolean>{1,1}</boolean>
  <NA>{1,1}</NA>
  <fuzzyNumber id="" mcdaConcept="" name="">{1,1}</fuzzyNumber>
  <valuedLabel>{1,1}</valuedLabel>
</value>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="value" type="value" minOccurs="1" maxOccurs="unbounded"/>
Element value / integer
Diagram
Diagram
Type xs:int
Properties
content simple
Source
<xs:element name="integer" type="xs:int"/>
Element value / real
Diagram
Diagram
Type xs:double
Properties
content simple
Source
<xs:element name="real" type="xs:double"/>
Element value / interval
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#interval_lowerBound XMCDA-4_0_0_xsd.tmp#interval_upperBound XMCDA-4_0_0_xsd.tmp#interval
Type interval
Properties
content complex
Model
Children lowerBound, upperBound
Instance
<interval xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <lowerBound id="" mcdaConcept="" name="" open="false">{1,1}</lowerBound>
  <upperBound id="" mcdaConcept="" name="" open="false">{0,1}</upperBound>
  <upperBound id="" mcdaConcept="" name="" open="false">{1,1}</upperBound>
</interval>
Source
<xs:element name="interval" type="interval"/>
Element interval / lowerBound
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#intervalBound_open XMCDA-4_0_0_xsd.tmp#intervalBound
Type intervalBound
Type hierarchy
Properties
content complex
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
<lowerBound id="" mcdaConcept="" name="" open="false" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <interval>{1,1}</interval>
  <rational>{1,1}</rational>
  <label>{1,1}</label>
  <boolean>{1,1}</boolean>
  <NA>{1,1}</NA>
  <fuzzyNumber id="" mcdaConcept="" name="">{1,1}</fuzzyNumber>
  <valuedLabel>{1,1}</valuedLabel>
</lowerBound>
Attributes
QName Type Default Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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.
open xs:boolean false optional
If false (the default), the value is included within the interval, otherwise it is not.
Source
<xs:element name="lowerBound" type="intervalBound"/>
Element value / rational
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#rational_numerator XMCDA-4_0_0_xsd.tmp#rational_denominator XMCDA-4_0_0_xsd.tmp#rational
Type rational
Properties
content complex
Model
Children denominator, numerator
Instance
<rational xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <numerator>{1,1}</numerator>
  <denominator>{1,1}</denominator>
</rational>
Source
<xs:element name="rational" type="rational"/>
Element rational / numerator
Diagram
Diagram
Type xs:int
Properties
content simple
Source
<xs:element name="numerator" type="xs:int"/>
Element rational / denominator
Diagram
Diagram
Type xs:int
Properties
content simple
Source
<xs:element name="denominator" type="xs:int"/>
Element value / label
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="label" type="xs:string"/>
Element value / boolean
Diagram
Diagram
Type xs:boolean
Properties
content simple
Source
<xs:element name="boolean" type="xs:boolean"/>
Element value / NA
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#NA
Type NA
Properties
content complex
Source
<xs:element name="NA" type="NA"/>
Element value / fuzzyNumber
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#function_constant XMCDA-4_0_0_xsd.tmp#function_affine XMCDA-4_0_0_xsd.tmp#function_piecewiseLinear XMCDA-4_0_0_xsd.tmp#function_discrete XMCDA-4_0_0_xsd.tmp#function XMCDA-4_0_0_xsd.tmp#membershipFunction_piecewiseLinear XMCDA-4_0_0_xsd.tmp#membershipFunction
Type membershipFunction
Type hierarchy
Properties
content complex
Model
Children piecewiseLinear
Instance
<fuzzyNumber id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <piecewiseLinear>{1,1}</piecewiseLinear>
</fuzzyNumber>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="fuzzyNumber" type="membershipFunction"/>
Element function / constant
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<constant id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <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 and reference the underlying piece of data.
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="numericValue"/>
Element value / valuedLabel
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#valuedLabel_label XMCDA-4_0_0_xsd.tmp#valuedLabel_value XMCDA-4_0_0_xsd.tmp#valuedLabel
Type valuedLabel
Properties
content complex
Model
Children label, value
Instance
<valuedLabel xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <label>{1,1}</label>
  <value id="" mcdaConcept="" name="">{1,1}</value>
</valuedLabel>
Source
<xs:element name="valuedLabel" type="valuedLabel"/>
Element valuedLabel / label
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="label" type="xs:string"/>
Element valuedLabel / value
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value
Type value
Properties
content complex
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
<value id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <interval>{1,1}</interval>
  <rational>{1,1}</rational>
  <label>{1,1}</label>
  <boolean>{1,1}</boolean>
  <NA>{1,1}</NA>
  <fuzzyNumber id="" mcdaConcept="" name="">{1,1}</fuzzyNumber>
  <valuedLabel>{1,1}</valuedLabel>
</value>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="value" type="value"/>
Element numericValue / integer
Diagram
Diagram
Type xs:int
Properties
content simple
Source
<xs:element name="integer" type="xs:int"/>
Element numericValue / real
Diagram
Diagram
Type xs:double
Properties
content simple
Source
<xs:element name="real" type="xs:double"/>
Element numericValue / rational
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#rational_numerator XMCDA-4_0_0_xsd.tmp#rational_denominator XMCDA-4_0_0_xsd.tmp#rational
Type rational
Properties
content complex
Model
Children denominator, numerator
Instance
<rational xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <numerator>{1,1}</numerator>
  <denominator>{1,1}</denominator>
</rational>
Source
<xs:element name="rational" type="rational"/>
Element numericValue / NA
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#NA
Type NA
Properties
content complex
Source
<xs:element name="NA" type="NA"/>
Element function / affine
Annotations
Affine function. Requires a slope and an intercept.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#function_function_affine_slope XMCDA-4_0_0_xsd.tmp#function_function_affine_intercept
Properties
content complex
Model
Children intercept, slope
Instance
<affine xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <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="numericValue"/>
      <xs:element name="intercept" type="numericValue"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element function / affine / slope
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<slope id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <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 and reference the underlying piece of data.
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="numericValue"/>
Element function / affine / intercept
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<intercept id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <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 and reference the underlying piece of data.
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="numericValue"/>
Element function / piecewiseLinear
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#piecewiseLinear_segment XMCDA-4_0_0_xsd.tmp#piecewiseLinear
Type piecewiseLinear
Properties
content complex
Model
Children segment
Instance
<piecewiseLinear xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <segment>{0,unbounded}</segment>
</piecewiseLinear>
Source
<xs:element name="piecewiseLinear" type="piecewiseLinear"/>
Element piecewiseLinear / segment
Annotations
Segment, defined by two points: one for the head, one for the tail. An attribute ("open") in the head and the tail allows to specify if the point is included in the segment or not.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#piecewiseLinear_piecewiseLinear_segment_head XMCDA-4_0_0_xsd.tmp#piecewiseLinear_piecewiseLinear_segment_tail
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children head, tail
Instance
<segment xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <head open="false">{1,1}</head>
  <tail open="false">{1,1}</tail>
</segment>
Source
<xs:element name="segment" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Segment, defined by two points: one for the head, one for the tail. An attribute ("open") in the head and the tail allows to specify if the point is included in the segment or not.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="head" type="nillableEndPoint">
        <xs:annotation>
          <xs:documentation>Head point of a segment. All heads except the first one can be nil (no content): in that case, it is equal to the previous segment's tail.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="tail" type="endPoint">
        <xs:annotation>
          <xs:documentation>Tail point of a segment..</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element piecewiseLinear / segment / head
Annotations
Head point of a segment. All heads except the first one can be nil (no content): in that case, it is equal to the previous segment's tail.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#nillableEndPoint_open XMCDA-4_0_0_xsd.tmp#nillableEndPoint_abscissa XMCDA-4_0_0_xsd.tmp#nillableEndPoint_ordinate XMCDA-4_0_0_xsd.tmp#nillableEndPoint
Type nillableEndPoint
Properties
content complex
Model
Children abscissa, ordinate
Instance
<head open="false" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <abscissa id="" mcdaConcept="" name="">{1,1}</abscissa>
  <ordinate id="" mcdaConcept="" name="">{1,1}</ordinate>
</head>
Attributes
QName Type Default Use Annotation
open xs:boolean false optional
If false (the default), the end point is included in the segment, otherwise it is not part of the segment.
Source
<xs:element name="head" type="nillableEndPoint">
  <xs:annotation>
    <xs:documentation>Head point of a segment. All heads except the first one can be nil (no content): in that case, it is equal to the previous segment's tail.</xs:documentation>
  </xs:annotation>
</xs:element>
Element nillableEndPoint / abscissa
Annotations
The abscissa of a point.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value
Type value
Properties
content complex
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
<abscissa id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <interval>{1,1}</interval>
  <rational>{1,1}</rational>
  <label>{1,1}</label>
  <boolean>{1,1}</boolean>
  <NA>{1,1}</NA>
  <fuzzyNumber id="" mcdaConcept="" name="">{1,1}</fuzzyNumber>
  <valuedLabel>{1,1}</valuedLabel>
</abscissa>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="abscissa" type="value">
  <xs:annotation>
    <xs:documentation>The abscissa of a point.</xs:documentation>
  </xs:annotation>
</xs:element>
Element nillableEndPoint / ordinate
Annotations
The ordinate of a point.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value
Type value
Properties
content complex
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
<ordinate id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <interval>{1,1}</interval>
  <rational>{1,1}</rational>
  <label>{1,1}</label>
  <boolean>{1,1}</boolean>
  <NA>{1,1}</NA>
  <fuzzyNumber id="" mcdaConcept="" name="">{1,1}</fuzzyNumber>
  <valuedLabel>{1,1}</valuedLabel>
</ordinate>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="ordinate" type="value">
  <xs:annotation>
    <xs:documentation>The ordinate of a point.</xs:documentation>
  </xs:annotation>
</xs:element>
Element piecewiseLinear / segment / tail
Annotations
Tail point of a segment..
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#point_abscissa XMCDA-4_0_0_xsd.tmp#point_ordinate XMCDA-4_0_0_xsd.tmp#point XMCDA-4_0_0_xsd.tmp#endPoint_open XMCDA-4_0_0_xsd.tmp#endPoint
Type endPoint
Type hierarchy
Properties
content complex
Model
Children abscissa, ordinate
Instance
<tail open="false" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <abscissa id="" mcdaConcept="" name="">{1,1}</abscissa>
  <ordinate id="" mcdaConcept="" name="">{1,1}</ordinate>
</tail>
Attributes
QName Type Default Use Annotation
open xs:boolean false optional
If false (the default), the end point is included in the segment, otherwise it is not part of the segment.
Source
<xs:element name="tail" type="endPoint">
  <xs:annotation>
    <xs:documentation>Tail point of a segment..</xs:documentation>
  </xs:annotation>
</xs:element>
Element point / abscissa
Annotations
The abscissa of a point.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value
Type value
Properties
content complex
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
<abscissa id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <interval>{1,1}</interval>
  <rational>{1,1}</rational>
  <label>{1,1}</label>
  <boolean>{1,1}</boolean>
  <NA>{1,1}</NA>
  <fuzzyNumber id="" mcdaConcept="" name="">{1,1}</fuzzyNumber>
  <valuedLabel>{1,1}</valuedLabel>
</abscissa>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="abscissa" type="value">
  <xs:annotation>
    <xs:documentation>The abscissa of a point.</xs:documentation>
  </xs:annotation>
</xs:element>
Element point / ordinate
Annotations
The ordinate of a point.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value
Type value
Properties
content complex
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
<ordinate id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <interval>{1,1}</interval>
  <rational>{1,1}</rational>
  <label>{1,1}</label>
  <boolean>{1,1}</boolean>
  <NA>{1,1}</NA>
  <fuzzyNumber id="" mcdaConcept="" name="">{1,1}</fuzzyNumber>
  <valuedLabel>{1,1}</valuedLabel>
</ordinate>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="ordinate" type="value">
  <xs:annotation>
    <xs:documentation>The ordinate of a point.</xs:documentation>
  </xs:annotation>
</xs:element>
Element function / discrete
Annotations
A discrete function defined by a sequence of points.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#function_function_discrete_point
Properties
content complex
Model
Children point
Instance
<discrete xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <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="point" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element function / discrete / point
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#point_abscissa XMCDA-4_0_0_xsd.tmp#point_ordinate XMCDA-4_0_0_xsd.tmp#point
Type point
Properties
content complex
maxOccurs unbounded
Model
Children abscissa, ordinate
Instance
<point xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <abscissa id="" mcdaConcept="" name="">{1,1}</abscissa>
  <ordinate id="" mcdaConcept="" name="">{1,1}</ordinate>
</point>
Source
<xs:element name="point" type="point" maxOccurs="unbounded"/>
Element membershipFunction / piecewiseLinear
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#piecewiseLinear_segment XMCDA-4_0_0_xsd.tmp#piecewiseLinear
Type piecewiseLinear
Properties
content complex
Model
Children segment
Instance
<piecewiseLinear xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <segment>{0,unbounded}</segment>
</piecewiseLinear>
Source
<xs:element name="piecewiseLinear" type="piecewiseLinear"/>
Element interval / upperBound
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#intervalBound_open XMCDA-4_0_0_xsd.tmp#intervalBound
Type intervalBound
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
<upperBound id="" mcdaConcept="" name="" open="false" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <interval>{1,1}</interval>
  <rational>{1,1}</rational>
  <label>{1,1}</label>
  <boolean>{1,1}</boolean>
  <NA>{1,1}</NA>
  <fuzzyNumber id="" mcdaConcept="" name="">{1,1}</fuzzyNumber>
  <valuedLabel>{1,1}</valuedLabel>
</upperBound>
Attributes
QName Type Default Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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.
open xs:boolean false optional
If false (the default), the value is included within the interval, otherwise it is not.
Source
<xs:element name="upperBound" type="intervalBound" minOccurs="0"/>
Element xmcda / criteria
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteria_description XMCDA-4_0_0_xsd.tmp#criteria_criterion XMCDA-4_0_0_xsd.tmp#criteria
Type criteria
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children criterion, description
Instance
<criteria id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterion id="" mcdaConcept="" name="">{1,unbounded}</criterion>
</criteria>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteria" type="criteria" minOccurs="0" maxOccurs="1"/>
Element criteria / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" minOccurs="0" type="description"/>
Element criteria / criterion
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#criterion_description XMCDA-4_0_0_xsd.tmp#criterion_active XMCDA-4_0_0_xsd.tmp#criterion
Type criterion
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children active, description
Instance
<criterion id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <active>{0,1}</active>
</criterion>
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="criterion" minOccurs="1" maxOccurs="unbounded" type="criterion"/>
Element criterion / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criterion / active
Annotations
Indicates whether a criterion is active or not in the calculations. By default, if the tag is not present, the criterion is considered to be active (true).
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default true
Source
<xs:element name="active" type="xs:boolean" minOccurs="0" default="true">
  <xs:annotation>
    <xs:documentation>Indicates whether a criterion is active or not in the calculations. By default, if the tag is not present, the criterion is considered to be active (true).</xs:documentation>
  </xs:annotation>
</xs:element>
Element xmcda / criteriaSets
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSets_description XMCDA-4_0_0_xsd.tmp#criteriaSets_criteriaSet XMCDA-4_0_0_xsd.tmp#criteriaSets
Type criteriaSets
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children criteriaSet, description
Instance
<criteriaSets id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criteriaSet id="" mcdaConcept="" name="">{1,unbounded}</criteriaSet>
</criteriaSets>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSets" type="criteriaSets" minOccurs="0" maxOccurs="1"/>
Element criteriaSets / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaSets / criteriaSet
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#criteriaSet_description XMCDA-4_0_0_xsd.tmp#criteriaSet_element XMCDA-4_0_0_xsd.tmp#criteriaSet
Type criteriaSet
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children description, element
Instance
<criteriaSet id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <element>{0,unbounded}</element>
</criteriaSet>
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="criteriaSet" type="criteriaSet" minOccurs="1" maxOccurs="unbounded"/>
Element criteriaSet / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaSet / element
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaSet_criteriaSet_element_criterionID XMCDA-4_0_0_xsd.tmp#criteriaSet_criteriaSet_element_values
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criterionID, values
Instance
<element xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <criterionID>{1,1}</criterionID>
  <values>{0,1}</values>
</element>
Source
<xs:element name="element" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="criterionID" type="xs:string"/>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criteriaSet / element / criterionID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criterionID" type="xs:string"/>
Element criteriaSet / element / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / performanceTable
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#performanceTable_description XMCDA-4_0_0_xsd.tmp#performanceTable_alternativePerformances XMCDA-4_0_0_xsd.tmp#performanceTable
Type performanceTable
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativePerformances, description
Instance
<performanceTable id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <alternativePerformances>{0,unbounded}</alternativePerformances>
</performanceTable>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="performanceTable" type="performanceTable" minOccurs="0" maxOccurs="unbounded"/>
Element performanceTable / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" minOccurs="0" type="description"/>
Element performanceTable / alternativePerformances
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativeOnCriteriaPerformances_alternativeID XMCDA-4_0_0_xsd.tmp#alternativeOnCriteriaPerformances_performance XMCDA-4_0_0_xsd.tmp#alternativeOnCriteriaPerformances
Type alternativeOnCriteriaPerformances
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativeID, performance
Instance
<alternativePerformances xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <performance>{1,unbounded}</performance>
</alternativePerformances>
Source
<xs:element name="alternativePerformances" minOccurs="0" maxOccurs="unbounded" type="alternativeOnCriteriaPerformances"/>
Element alternativeOnCriteriaPerformances / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 1
maxOccurs 1
Source
<xs:element name="alternativeID" minOccurs="1" maxOccurs="1" type="xs:string"/>
Element alternativeOnCriteriaPerformances / performance
Annotations
Evaluation of an alternative on a criterion. If the evaluation is not available, put NA.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativeOnCriteriaPerformances_alternativeOnCriteriaPerformances_performance_description XMCDA-4_0_0_xsd.tmp#alternativeOnCriteriaPerformances_alternativeOnCriteriaPerformances_performance_criterionID XMCDA-4_0_0_xsd.tmp#alternativeOnCriteriaPerformances_alternativeOnCriteriaPerformances_performance_values
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children criterionID, description, values
Instance
<performance xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterionID>{1,1}</criterionID>
  <values>{1,1}</values>
</performance>
Source
<xs:element name="performance" minOccurs="1" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Evaluation of an alternative on a criterion. If the evaluation is not available, put NA.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="description" minOccurs="0" type="description"/>
      <xs:element name="criterionID" minOccurs="1" maxOccurs="1" type="xs:string"/>
      <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element alternativeOnCriteriaPerformances / performance / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" minOccurs="0" type="description"/>
Element alternativeOnCriteriaPerformances / performance / criterionID
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 1
maxOccurs 1
Source
<xs:element name="criterionID" minOccurs="1" maxOccurs="1" type="xs:string"/>
Element alternativeOnCriteriaPerformances / performance / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / categories
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categories_description XMCDA-4_0_0_xsd.tmp#categories_category XMCDA-4_0_0_xsd.tmp#categories
Type categories
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children category, description
Instance
<categories id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <category id="" mcdaConcept="" name="">{1,unbounded}</category>
</categories>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categories" type="categories" minOccurs="0" maxOccurs="1"/>
Element categories / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categories / category
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#category_description XMCDA-4_0_0_xsd.tmp#category_active XMCDA-4_0_0_xsd.tmp#category
Type category
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children active, description
Instance
<category id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <active>{0,1}</active>
</category>
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="category" type="category" minOccurs="1" maxOccurs="unbounded"/>
Element category / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element category / active
Annotations
Indicates whether a category is active or not in the calculations. By default, if the tag is not present, the category is considered to be active (true).
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default true
Source
<xs:element name="active" type="xs:boolean" minOccurs="0" default="true">
  <xs:annotation>
    <xs:documentation>Indicates whether a category is active or not in the calculations. By default, if the tag is not present, the category is considered to be active (true).</xs:documentation>
  </xs:annotation>
</xs:element>
Element xmcda / categoriesSets
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSets_description XMCDA-4_0_0_xsd.tmp#categoriesSets_categoriesSet XMCDA-4_0_0_xsd.tmp#categoriesSets
Type categoriesSets
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children categoriesSet, description
Instance
<categoriesSets id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <categoriesSet id="" mcdaConcept="" name="">{0,unbounded}</categoriesSet>
</categoriesSets>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesSets" type="categoriesSets" minOccurs="0" maxOccurs="1"/>
Element categoriesSets / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesSets / categoriesSet
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#categoriesSet_description XMCDA-4_0_0_xsd.tmp#categoriesSet_element XMCDA-4_0_0_xsd.tmp#categoriesSet
Type categoriesSet
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, element
Instance
<categoriesSet id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <element>{0,unbounded}</element>
</categoriesSet>
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="categoriesSet" type="categoriesSet" minOccurs="0" maxOccurs="unbounded"/>
Element categoriesSet / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesSet / element
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesSet_categoriesSet_element_categoryID XMCDA-4_0_0_xsd.tmp#categoriesSet_categoriesSet_element_values
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children categoryID, values
Instance
<element xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <categoryID>{1,1}</categoryID>
  <values>{0,1}</values>
</element>
Source
<xs:element name="element" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="categoryID" type="xs:string"/>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element categoriesSet / element / categoryID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoryID" type="xs:string"/>
Element categoriesSet / element / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / alternativesAssignments
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesAssignments_description XMCDA-4_0_0_xsd.tmp#alternativesAssignments_alternativeAssignment XMCDA-4_0_0_xsd.tmp#alternativesAssignments
Type alternativesAssignments
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativeAssignment, description
Instance
<alternativesAssignments id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <alternativeAssignment id="" mcdaConcept="" name="">{1,unbounded}</alternativeAssignment>
</alternativesAssignments>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesAssignments" minOccurs="0" maxOccurs="unbounded" type="alternativesAssignments"/>
Element alternativesAssignments / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesAssignments / alternativeAssignment
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativeAssignment_description XMCDA-4_0_0_xsd.tmp#alternativeAssignment_alternativeID XMCDA-4_0_0_xsd.tmp#alternativeAssignment_categoryID XMCDA-4_0_0_xsd.tmp#alternativeAssignment_categoriesSetID XMCDA-4_0_0_xsd.tmp#alternativeAssignment_categoriesInterval XMCDA-4_0_0_xsd.tmp#alternativeAssignment_values XMCDA-4_0_0_xsd.tmp#alternativeAssignment
Type alternativeAssignment
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children alternativeID, categoriesInterval, categoriesSetID, categoryID, description, values
Instance
<alternativeAssignment id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <alternativeID>{1,1}</alternativeID>
  <categoryID>{1,1}</categoryID>
  <categoriesSetID>{1,1}</categoriesSetID>
  <categoriesInterval id="" mcdaConcept="" name="">{1,1}</categoriesInterval>
  <values>{0,1}</values>
</alternativeAssignment>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativeAssignment" type="alternativeAssignment" minOccurs="1" maxOccurs="unbounded"/>
Element alternativeAssignment / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativeAssignment / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativeID" type="xs:string"/>
Element alternativeAssignment / categoryID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoryID" type="xs:string"/>
Element alternativeAssignment / categoriesSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoriesSetID" type="xs:string"/>
Element alternativeAssignment / categoriesInterval
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesInterval_description XMCDA-4_0_0_xsd.tmp#categoriesInterval_lowerBound XMCDA-4_0_0_xsd.tmp#categoriesInterval_upperBound XMCDA-4_0_0_xsd.tmp#categoriesInterval
Type categoriesInterval
Properties
content complex
Model
Children description, lowerBound, upperBound
Instance
<categoriesInterval id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <lowerBound>{1,1}</lowerBound>
  <upperBound>{0,1}</upperBound>
  <upperBound>{1,1}</upperBound>
</categoriesInterval>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesInterval" type="categoriesInterval"/>
Element categoriesInterval / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesInterval / lowerBound
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesIntervalBound_categoryID XMCDA-4_0_0_xsd.tmp#categoriesIntervalBound
Type categoriesIntervalBound
Properties
content complex
Model
Children categoryID
Instance
<lowerBound xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <categoryID>{1,1}</categoryID>
</lowerBound>
Source
<xs:element name="lowerBound" type="categoriesIntervalBound"/>
Element categoriesIntervalBound / categoryID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoryID" type="xs:string"/>
Element categoriesInterval / upperBound
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesIntervalBound_categoryID XMCDA-4_0_0_xsd.tmp#categoriesIntervalBound
Type categoriesIntervalBound
Properties
content complex
minOccurs 0
Model
Children categoryID
Instance
<upperBound xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <categoryID>{1,1}</categoryID>
</upperBound>
Source
<xs:element name="upperBound" type="categoriesIntervalBound" minOccurs="0"/>
Element alternativeAssignment / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / alternativesCriteriaValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesCriteriaValues_description XMCDA-4_0_0_xsd.tmp#alternativesCriteriaValues_alternativeCriteriaValues XMCDA-4_0_0_xsd.tmp#alternativesCriteriaValues
Type alternativesCriteriaValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativeCriteriaValues, description
Instance
<alternativesCriteriaValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <alternativeCriteriaValues>{1,unbounded}</alternativeCriteriaValues>
</alternativesCriteriaValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesCriteriaValues" minOccurs="0" maxOccurs="unbounded" type="alternativesCriteriaValues"/>
Element alternativesCriteriaValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesCriteriaValues / alternativeCriteriaValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativeCriteriaValues_alternativeID XMCDA-4_0_0_xsd.tmp#alternativeCriteriaValues_criteriaValues XMCDA-4_0_0_xsd.tmp#alternativeCriteriaValues
Type alternativeCriteriaValues
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children alternativeID, criteriaValues
Instance
<alternativeCriteriaValues xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <criteriaValues id="" mcdaConcept="" name="">{1,1}</criteriaValues>
</alternativeCriteriaValues>
Source
<xs:element name="alternativeCriteriaValues" type="alternativeCriteriaValues" minOccurs="1" maxOccurs="unbounded"/>
Element alternativeCriteriaValues / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 1
Source
<xs:element name="alternativeID" minOccurs="1" type="xs:string"/>
Element alternativeCriteriaValues / criteriaValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaValues_description XMCDA-4_0_0_xsd.tmp#criteriaValues_criterionValues XMCDA-4_0_0_xsd.tmp#criteriaValues
Type criteriaValues
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children criterionValues, description
Instance
<criteriaValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterionValues id="" mcdaConcept="" name="">{1,unbounded}</criterionValues>
</criteriaValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaValues" type="criteriaValues" minOccurs="1" maxOccurs="1"/>
Element criteriaValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaValues / criterionValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criterionValues_description XMCDA-4_0_0_xsd.tmp#criterionValues_criterionID XMCDA-4_0_0_xsd.tmp#criterionValues_values XMCDA-4_0_0_xsd.tmp#criterionValues
Type criterionValues
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children criterionID, description, values
Instance
<criterionValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterionID>{1,1}</criterionID>
  <values>{1,1}</values>
</criterionValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criterionValues" type="criterionValues" minOccurs="1" maxOccurs="unbounded"/>
Element criterionValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criterionValues / criterionID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criterionID" type="xs:string"/>
Element criterionValues / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / alternativesLinearConstraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_description XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_constraints XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints
Type alternativesLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<alternativesLinearConstraints id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <variables>{0,1}</variables>
  <constraints>{1,1}</constraints>
</alternativesLinearConstraints>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="alternativesLinearConstraints"/>
Element alternativesLinearConstraints / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesLinearConstraints / variables
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#variables_variable XMCDA-4_0_0_xsd.tmp#variables
Type variables
Properties
content complex
minOccurs 0
Model
Children variable
Instance
<variables xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <variable id="" mcdaConcept="" name="">{1,unbounded}</variable>
</variables>
Source
<xs:element name="variables" type="variables" minOccurs="0"/>
Element variables / variable
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#variable_description XMCDA-4_0_0_xsd.tmp#variable
Type variable
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children description
Instance
<variable id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
</variable>
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="variable" type="variable" minOccurs="1" maxOccurs="unbounded"/>
Element variable / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element alternativesLinearConstraints / constraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint
Properties
content complex
Model
Children constraint
Instance
<constraints xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <constraint id="" mcdaConcept="" name="">{1,unbounded}</constraint>
</constraints>
Source
<xs:element name="constraints">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:annotation>
            <xs:documentation>A linear constraint related to alternatives. It is composed of a sum of elements, each element being composed of an alternative or a variable and a coefficient. The rhs allows to specify the value of the right hand side. The values linked to each constraint can represent a credibility of this constraint in the eyes of a decision maker, for example.</xs:documentation>
          </xs:annotation>
          <xs:sequence>
            <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
            <xs:element name="elements" minOccurs="0" maxOccurs="1">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:choice>
                          <xs:element name="alternativeID" type="xs:string"/>
                          <xs:element name="variableID" type="xs:string"/>
                        </xs:choice>
                        <xs:element name="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
                      </xs:sequence>
                      <xs:attributeGroup ref="defaultAttributes"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name="operator" minOccurs="1">
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="geq"/>
                  <xs:enumeration value="eq"/>
                  <xs:enumeration value="leq"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="rhs" type="numericValue"/>
            <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element alternativesLinearConstraints / constraints / constraint
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_description XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_elements XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_operator XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_rhs XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_values
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children description, elements, operator, rhs, values
Instance
<constraint id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <elements>{0,1}</elements>
  <operator>{1,1}</operator>
  <rhs id="" mcdaConcept="" name="">{1,1}</rhs>
  <values>{0,1}</values>
</constraint>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="constraint" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A linear constraint related to alternatives. It is composed of a sum of elements, each element being composed of an alternative or a variable and a coefficient. The rhs allows to specify the value of the right hand side. The values linked to each constraint can represent a credibility of this constraint in the eyes of a decision maker, for example.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
      <xs:element name="elements" minOccurs="0" maxOccurs="1">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:choice>
                    <xs:element name="alternativeID" type="xs:string"/>
                    <xs:element name="variableID" type="xs:string"/>
                  </xs:choice>
                  <xs:element name="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
                </xs:sequence>
                <xs:attributeGroup ref="defaultAttributes"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="operator" minOccurs="1">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="geq"/>
            <xs:enumeration value="eq"/>
            <xs:enumeration value="leq"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="rhs" type="numericValue"/>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element alternativesLinearConstraints / constraints / constraint / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element alternativesLinearConstraints / constraints / constraint / elements
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_elements_element
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children element
Instance
<elements xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <element id="" mcdaConcept="" name="">{1,unbounded}</element>
</elements>
Source
<xs:element name="elements" minOccurs="0" maxOccurs="1">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:choice>
              <xs:element name="alternativeID" type="xs:string"/>
              <xs:element name="variableID" type="xs:string"/>
            </xs:choice>
            <xs:element name="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element alternativesLinearConstraints / constraints / constraint / elements / element
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_elements_alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_elements_element_alternativeID XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_elements_alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_elements_element_variableID XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_elements_alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_alternativesLinearConstraints_alternativesLinearConstraints_constraints_alternativesLinearConstraints_alternativesLinearConstraints_constraints_constraint_elements_element_coefficient
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children alternativeID, coefficient, variableID
Instance
<element id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <variableID>{1,1}</variableID>
  <coefficient id="" mcdaConcept="" name="">{1,1}</coefficient>
</element>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="element" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:choice>
        <xs:element name="alternativeID" type="xs:string"/>
        <xs:element name="variableID" type="xs:string"/>
      </xs:choice>
      <xs:element name="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element alternativesLinearConstraints / constraints / constraint / elements / element / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativeID" type="xs:string"/>
Element alternativesLinearConstraints / constraints / constraint / elements / element / variableID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="variableID" type="xs:string"/>
Element alternativesLinearConstraints / constraints / constraint / elements / element / coefficient
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children NA, integer, rational, real
Instance
<coefficient id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</coefficient>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
Element alternativesLinearConstraints / constraints / constraint / operator
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 1
Facets
enumeration geq
enumeration eq
enumeration leq
Source
<xs:element name="operator" minOccurs="1">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="geq"/>
      <xs:enumeration value="eq"/>
      <xs:enumeration value="leq"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element alternativesLinearConstraints / constraints / constraint / rhs
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<rhs id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</rhs>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="rhs" type="numericValue"/>
Element alternativesLinearConstraints / constraints / constraint / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / alternativesMatrix
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesMatrix_description XMCDA-4_0_0_xsd.tmp#alternativesMatrix_row XMCDA-4_0_0_xsd.tmp#alternativesMatrix
Type alternativesMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row
Instance
<alternativesMatrix id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <row>{1,unbounded}</row>
</alternativesMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesMatrix" minOccurs="0" maxOccurs="unbounded" type="alternativesMatrix"/>
Element alternativesMatrix / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesMatrix / row
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativesMatrix_alternativesMatrix_row_alternativeID XMCDA-4_0_0_xsd.tmp#alternativesMatrix_alternativesMatrix_row_column
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children alternativeID, column
Instance
<row xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <column>{1,unbounded}</column>
</row>
Source
<xs:element name="row" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>Row of a matrix.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="alternativeID" type="xs:string"/>
      <xs:element name="column" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="alternativeID" type="xs:string"/>
            <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element alternativesMatrix / row / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativeID" type="xs:string"/>
Element alternativesMatrix / row / column
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativesMatrix_alternativesMatrix_row_alternativesMatrix_alternativesMatrix_row_column_alternativeID XMCDA-4_0_0_xsd.tmp#alternativesMatrix_alternativesMatrix_row_alternativesMatrix_alternativesMatrix_row_column_values
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children alternativeID, values
Instance
<column xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <values>{0,1}</values>
</column>
Source
<xs:element name="column" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="alternativeID" type="xs:string"/>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element alternativesMatrix / row / column / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativeID" type="xs:string"/>
Element alternativesMatrix / row / column / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / alternativesValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesValues_description XMCDA-4_0_0_xsd.tmp#alternativesValues_alternativeValues XMCDA-4_0_0_xsd.tmp#alternativesValues
Type alternativesValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativeValues, description
Instance
<alternativesValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <alternativeValues id="" mcdaConcept="" name="">{1,unbounded}</alternativeValues>
</alternativesValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesValues" minOccurs="0" maxOccurs="unbounded" type="alternativesValues"/>
Element alternativesValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesValues / alternativeValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativeValues_description XMCDA-4_0_0_xsd.tmp#alternativeValues_alternativeID XMCDA-4_0_0_xsd.tmp#alternativeValues_values XMCDA-4_0_0_xsd.tmp#alternativeValues
Type alternativeValues
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children alternativeID, description, values
Instance
<alternativeValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <alternativeID>{1,1}</alternativeID>
  <values>{1,1}</values>
</alternativeValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativeValues" type="alternativeValues" minOccurs="1" maxOccurs="unbounded"/>
Element alternativeValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativeValues / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativeID" type="xs:string"/>
Element alternativeValues / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / alternativesSetsLinearConstraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_description XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_constraints XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints
Type alternativesSetsLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<alternativesSetsLinearConstraints id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <variables>{0,1}</variables>
  <constraints>{1,1}</constraints>
</alternativesSetsLinearConstraints>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="alternativesSetsLinearConstraints"/>
Element alternativesSetsLinearConstraints / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesSetsLinearConstraints / variables
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#variables_variable XMCDA-4_0_0_xsd.tmp#variables
Type variables
Properties
content complex
minOccurs 0
Model
Children variable
Instance
<variables xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <variable id="" mcdaConcept="" name="">{1,unbounded}</variable>
</variables>
Source
<xs:element name="variables" type="variables" minOccurs="0"/>
Element alternativesSetsLinearConstraints / constraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint
Properties
content complex
Model
Children constraint
Instance
<constraints xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <constraint id="" mcdaConcept="" name="">{1,unbounded}</constraint>
</constraints>
Source
<xs:element name="constraints">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:annotation>
            <xs:documentation>A linear constraint related to sets of alternatives. It is composed of a sum of elements, each element being composed of a set of alternatives or a variable and a coefficient. The rhs allows to specify the value of the right hand side. The values linked to each constraint can represent a credibility of this constraint in the eyes of a decision maker, for example.</xs:documentation>
          </xs:annotation>
          <xs:sequence>
            <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
            <xs:element name="elements" minOccurs="0" maxOccurs="1">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:choice>
                          <xs:element name="alternativesSetID" type="xs:string"/>
                          <xs:element name="variableID" type="xs:string"/>
                        </xs:choice>
                        <xs:element name="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
                      </xs:sequence>
                      <xs:attributeGroup ref="defaultAttributes"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name="operator" minOccurs="1">
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="geq"/>
                  <xs:enumeration value="eq"/>
                  <xs:enumeration value="leq"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="rhs" type="numericValue"/>
            <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element alternativesSetsLinearConstraints / constraints / constraint
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_description XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_elements XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_operator XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_rhs XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_values
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children description, elements, operator, rhs, values
Instance
<constraint id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <elements>{0,1}</elements>
  <operator>{1,1}</operator>
  <rhs id="" mcdaConcept="" name="">{1,1}</rhs>
  <values>{0,1}</values>
</constraint>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="constraint" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A linear constraint related to sets of alternatives. It is composed of a sum of elements, each element being composed of a set of alternatives or a variable and a coefficient. The rhs allows to specify the value of the right hand side. The values linked to each constraint can represent a credibility of this constraint in the eyes of a decision maker, for example.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
      <xs:element name="elements" minOccurs="0" maxOccurs="1">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:choice>
                    <xs:element name="alternativesSetID" type="xs:string"/>
                    <xs:element name="variableID" type="xs:string"/>
                  </xs:choice>
                  <xs:element name="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
                </xs:sequence>
                <xs:attributeGroup ref="defaultAttributes"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="operator" minOccurs="1">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="geq"/>
            <xs:enumeration value="eq"/>
            <xs:enumeration value="leq"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="rhs" type="numericValue"/>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element alternativesSetsLinearConstraints / constraints / constraint / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element alternativesSetsLinearConstraints / constraints / constraint / elements
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_elements_element
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children element
Instance
<elements xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <element id="" mcdaConcept="" name="">{1,unbounded}</element>
</elements>
Source
<xs:element name="elements" minOccurs="0" maxOccurs="1">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:choice>
              <xs:element name="alternativesSetID" type="xs:string"/>
              <xs:element name="variableID" type="xs:string"/>
            </xs:choice>
            <xs:element name="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element alternativesSetsLinearConstraints / constraints / constraint / elements / element
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_elements_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_elements_element_alternativesSetID XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_elements_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_elements_element_variableID XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_elements_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_alternativesSetsLinearConstraints_alternativesSetsLinearConstraints_constraints_constraint_elements_element_coefficient
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children alternativesSetID, coefficient, variableID
Instance
<element id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativesSetID>{1,1}</alternativesSetID>
  <variableID>{1,1}</variableID>
  <coefficient id="" mcdaConcept="" name="">{1,1}</coefficient>
</element>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="element" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:choice>
        <xs:element name="alternativesSetID" type="xs:string"/>
        <xs:element name="variableID" type="xs:string"/>
      </xs:choice>
      <xs:element name="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element alternativesSetsLinearConstraints / constraints / constraint / elements / element / alternativesSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativesSetID" type="xs:string"/>
Element alternativesSetsLinearConstraints / constraints / constraint / elements / element / variableID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="variableID" type="xs:string"/>
Element alternativesSetsLinearConstraints / constraints / constraint / elements / element / coefficient
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children NA, integer, rational, real
Instance
<coefficient id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</coefficient>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
Element alternativesSetsLinearConstraints / constraints / constraint / operator
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 1
Facets
enumeration geq
enumeration eq
enumeration leq
Source
<xs:element name="operator" minOccurs="1">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="geq"/>
      <xs:enumeration value="eq"/>
      <xs:enumeration value="leq"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element alternativesSetsLinearConstraints / constraints / constraint / rhs
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<rhs id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</rhs>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="rhs" type="numericValue"/>
Element alternativesSetsLinearConstraints / constraints / constraint / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / alternativesSetsMatrix
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix_description XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix_row XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix
Type alternativesSetsMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row
Instance
<alternativesSetsMatrix id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <row>{1,unbounded}</row>
</alternativesSetsMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="alternativesSetsMatrix"/>
Element alternativesSetsMatrix / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesSetsMatrix / row
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix_alternativesSetsMatrix_row_alternativeID XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix_alternativesSetsMatrix_row_alternativesSetID XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix_alternativesSetsMatrix_row_column
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children alternativeID, alternativesSetID, column
Instance
<row xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <alternativesSetID>{1,1}</alternativesSetID>
  <column>{1,unbounded}</column>
</row>
Source
<xs:element name="row" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>Row of a matrix.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:choice>
        <xs:element name="alternativeID" type="xs:string"/>
        <xs:element name="alternativesSetID" type="xs:string"/>
      </xs:choice>
      <xs:element name="column" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:choice>
              <xs:element name="alternativeID" type="xs:string"/>
              <xs:element name="alternativesSetID" type="xs:string"/>
            </xs:choice>
            <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element alternativesSetsMatrix / row / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativeID" type="xs:string"/>
Element alternativesSetsMatrix / row / alternativesSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativesSetID" type="xs:string"/>
Element alternativesSetsMatrix / row / column
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix_alternativesSetsMatrix_row_alternativesSetsMatrix_alternativesSetsMatrix_row_column_alternativeID XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix_alternativesSetsMatrix_row_alternativesSetsMatrix_alternativesSetsMatrix_row_column_alternativesSetID XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix_alternativesSetsMatrix_row_alternativesSetsMatrix_alternativesSetsMatrix_row_column_values
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children alternativeID, alternativesSetID, values
Instance
<column xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <alternativesSetID>{1,1}</alternativesSetID>
  <values>{0,1}</values>
</column>
Source
<xs:element name="column" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:choice>
        <xs:element name="alternativeID" type="xs:string"/>
        <xs:element name="alternativesSetID" type="xs:string"/>
      </xs:choice>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element alternativesSetsMatrix / row / column / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativeID" type="xs:string"/>
Element alternativesSetsMatrix / row / column / alternativesSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativesSetID" type="xs:string"/>
Element alternativesSetsMatrix / row / column / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / alternativesSetsValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSetsValues_description XMCDA-4_0_0_xsd.tmp#alternativesSetsValues_alternativesSetValues XMCDA-4_0_0_xsd.tmp#alternativesSetsValues
Type alternativesSetsValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativesSetValues, description
Instance
<alternativesSetsValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <alternativesSetValues id="" mcdaConcept="" name="">{1,unbounded}</alternativesSetValues>
</alternativesSetsValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesSetsValues" minOccurs="0" maxOccurs="unbounded" type="alternativesSetsValues"/>
Element alternativesSetsValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesSetsValues / alternativesSetValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSetValues_description XMCDA-4_0_0_xsd.tmp#alternativesSetValues_alternativesSetID XMCDA-4_0_0_xsd.tmp#alternativesSetValues_values XMCDA-4_0_0_xsd.tmp#alternativesSetValues
Type alternativesSetValues
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children alternativesSetID, description, values
Instance
<alternativesSetValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <alternativesSetID>{1,1}</alternativesSetID>
  <values>{1,1}</values>
</alternativesSetValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesSetValues" type="alternativesSetValues" minOccurs="1" maxOccurs="unbounded"/>
Element alternativesSetValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element alternativesSetValues / alternativesSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativesSetID" type="xs:string"/>
Element alternativesSetValues / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / criteriaFunctions
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaFunctions_description XMCDA-4_0_0_xsd.tmp#criteriaFunctions_criterionFunctions XMCDA-4_0_0_xsd.tmp#criteriaFunctions
Type criteriaFunctions
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criterionFunctions, description
Instance
<criteriaFunctions id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterionFunctions id="" mcdaConcept="" name="">{1,unbounded}</criterionFunctions>
</criteriaFunctions>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaFunctions" type="criteriaFunctions" minOccurs="0" maxOccurs="unbounded"/>
Element criteriaFunctions / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element criteriaFunctions / criterionFunctions
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criterionFunctions_description XMCDA-4_0_0_xsd.tmp#criterionFunctions_criterionID XMCDA-4_0_0_xsd.tmp#criterionFunctions_functions XMCDA-4_0_0_xsd.tmp#criterionFunctions
Type criterionFunctions
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children criterionID, description, functions
Instance
<criterionFunctions id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterionID>{1,1}</criterionID>
  <functions>{1,1}</functions>
</criterionFunctions>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criterionFunctions" type="criterionFunctions" minOccurs="1" maxOccurs="unbounded"/>
Element criterionFunctions / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element criterionFunctions / criterionID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criterionID" type="xs:string"/>
Element criterionFunctions / functions
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criterionFunctions_criterionFunctions_functions_function
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children function
Instance
<functions xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <function id="" mcdaConcept="" name="">{1,unbounded}</function>
</functions>
Source
<xs:element name="functions" minOccurs="1" maxOccurs="1">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="function" type="function" minOccurs="1" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criterionFunctions / functions / function
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#function_constant XMCDA-4_0_0_xsd.tmp#function_affine XMCDA-4_0_0_xsd.tmp#function_piecewiseLinear XMCDA-4_0_0_xsd.tmp#function_discrete XMCDA-4_0_0_xsd.tmp#function
Type function
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children affine, constant, discrete, piecewiseLinear
Instance
<function id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <constant id="" mcdaConcept="" name="">{1,1}</constant>
  <affine>{1,1}</affine>
  <piecewiseLinear>{1,1}</piecewiseLinear>
  <discrete>{1,1}</discrete>
</function>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="function" type="function" minOccurs="1" maxOccurs="unbounded"/>
Element xmcda / criteriaHierarchy
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaHierarchy_description XMCDA-4_0_0_xsd.tmp#criteriaHierarchy_nodes XMCDA-4_0_0_xsd.tmp#criteriaHierarchy
Type criteriaHierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, nodes
Instance
<criteriaHierarchy id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <nodes>{1,unbounded}</nodes>
</criteriaHierarchy>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaHierarchy" minOccurs="0" maxOccurs="unbounded" type="criteriaHierarchy"/>
Element criteriaHierarchy / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaHierarchy / nodes
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaHierarchyNodes_node XMCDA-4_0_0_xsd.tmp#criteriaHierarchyNodes
Type criteriaHierarchyNodes
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children node
Instance
<nodes xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <node>{1,unbounded}</node>
</nodes>
Source
<xs:element name="nodes" type="criteriaHierarchyNodes" minOccurs="1" maxOccurs="unbounded"/>
Element criteriaHierarchyNodes / node
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criterionHierarchyNode_criterionID XMCDA-4_0_0_xsd.tmp#criterionHierarchyNode_nodes XMCDA-4_0_0_xsd.tmp#criterionHierarchyNode
Type criterionHierarchyNode
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children criterionID, nodes
Instance
<node xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <criterionID>{1,1}</criterionID>
  <nodes>{0,unbounded}</nodes>
</node>
Source
<xs:element name="node" type="criterionHierarchyNode" minOccurs="1" maxOccurs="unbounded"/>
Element criterionHierarchyNode / criterionID
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 1
maxOccurs 1
Source
<xs:element name="criterionID" type="xs:string" minOccurs="1" maxOccurs="1"/>
Element criterionHierarchyNode / nodes
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaHierarchyNodes_node XMCDA-4_0_0_xsd.tmp#criteriaHierarchyNodes
Type criteriaHierarchyNodes
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children node
Instance
<nodes xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <node>{1,unbounded}</node>
</nodes>
Source
<xs:element name="nodes" type="criteriaHierarchyNodes" minOccurs="0" maxOccurs="unbounded"/>
Element xmcda / criteriaLinearConstraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_description XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_constraints XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints
Type criteriaLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<criteriaLinearConstraints id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <variables>{0,1}</variables>
  <constraints>{1,1}</constraints>
</criteriaLinearConstraints>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="criteriaLinearConstraints"/>
Element criteriaLinearConstraints / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaLinearConstraints / variables
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#variables_variable XMCDA-4_0_0_xsd.tmp#variables
Type variables
Properties
content complex
minOccurs 0
Model
Children variable
Instance
<variables xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <variable id="" mcdaConcept="" name="">{1,unbounded}</variable>
</variables>
Source
<xs:element name="variables" type="variables" minOccurs="0"/>
Element criteriaLinearConstraints / constraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint
Properties
content complex
Model
Children constraint
Instance
<constraints xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <constraint id="" mcdaConcept="" name="">{1,unbounded}</constraint>
</constraints>
Source
<xs:element name="constraints">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:annotation>
            <xs:documentation>A linear constraint related to criteria. It is constructed from a sum of elements, each element being composed of a reference to a criterion or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
          </xs:annotation>
          <xs:sequence>
            <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
            <xs:element name="elements" minOccurs="0" maxOccurs="1">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:choice>
                          <xs:element name="criterionID" type="xs:string"/>
                          <xs:element name="variableID" type="xs:string"/>
                        </xs:choice>
                        <xs:element name="coefficient" type="numericValue"/>
                      </xs:sequence>
                      <xs:attributeGroup ref="defaultAttributes"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name="operator" minOccurs="1">
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="geq"/>
                  <xs:enumeration value="eq"/>
                  <xs:enumeration value="leq"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="rhs" type="numericValue"/>
            <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criteriaLinearConstraints / constraints / constraint
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_description XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_elements XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_operator XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_rhs XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_values
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children description, elements, operator, rhs, values
Instance
<constraint id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <elements>{0,1}</elements>
  <operator>{1,1}</operator>
  <rhs id="" mcdaConcept="" name="">{1,1}</rhs>
  <values>{0,1}</values>
</constraint>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="constraint" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A linear constraint related to criteria. It is constructed from a sum of elements, each element being composed of a reference to a criterion or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
      <xs:element name="elements" minOccurs="0" maxOccurs="1">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:choice>
                    <xs:element name="criterionID" type="xs:string"/>
                    <xs:element name="variableID" type="xs:string"/>
                  </xs:choice>
                  <xs:element name="coefficient" type="numericValue"/>
                </xs:sequence>
                <xs:attributeGroup ref="defaultAttributes"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="operator" minOccurs="1">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="geq"/>
            <xs:enumeration value="eq"/>
            <xs:enumeration value="leq"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="rhs" type="numericValue"/>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element criteriaLinearConstraints / constraints / constraint / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element criteriaLinearConstraints / constraints / constraint / elements
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_elements_element
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children element
Instance
<elements xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <element id="" mcdaConcept="" name="">{1,unbounded}</element>
</elements>
Source
<xs:element name="elements" minOccurs="0" maxOccurs="1">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:choice>
              <xs:element name="criterionID" type="xs:string"/>
              <xs:element name="variableID" type="xs:string"/>
            </xs:choice>
            <xs:element name="coefficient" type="numericValue"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criteriaLinearConstraints / constraints / constraint / elements / element
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_elements_criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_elements_element_criterionID XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_elements_criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_elements_element_variableID XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_elements_criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_criteriaLinearConstraints_criteriaLinearConstraints_constraints_criteriaLinearConstraints_criteriaLinearConstraints_constraints_constraint_elements_element_coefficient
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children coefficient, criterionID, variableID
Instance
<element id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <criterionID>{1,1}</criterionID>
  <variableID>{1,1}</variableID>
  <coefficient id="" mcdaConcept="" name="">{1,1}</coefficient>
</element>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="element" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:choice>
        <xs:element name="criterionID" type="xs:string"/>
        <xs:element name="variableID" type="xs:string"/>
      </xs:choice>
      <xs:element name="coefficient" type="numericValue"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element criteriaLinearConstraints / constraints / constraint / elements / element / criterionID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criterionID" type="xs:string"/>
Element criteriaLinearConstraints / constraints / constraint / elements / element / variableID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="variableID" type="xs:string"/>
Element criteriaLinearConstraints / constraints / constraint / elements / element / coefficient
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<coefficient id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</coefficient>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="coefficient" type="numericValue"/>
Element criteriaLinearConstraints / constraints / constraint / operator
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 1
Facets
enumeration geq
enumeration eq
enumeration leq
Source
<xs:element name="operator" minOccurs="1">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="geq"/>
      <xs:enumeration value="eq"/>
      <xs:enumeration value="leq"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element criteriaLinearConstraints / constraints / constraint / rhs
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<rhs id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</rhs>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="rhs" type="numericValue"/>
Element criteriaLinearConstraints / constraints / constraint / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / criteriaMatrix
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaMatrix_description XMCDA-4_0_0_xsd.tmp#criteriaMatrix_row XMCDA-4_0_0_xsd.tmp#criteriaMatrix
Type criteriaMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row
Instance
<criteriaMatrix id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <row>{1,unbounded}</row>
</criteriaMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaMatrix" minOccurs="0" maxOccurs="unbounded" type="criteriaMatrix"/>
Element criteriaMatrix / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaMatrix / row
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaMatrix_criteriaMatrix_row_criterionID XMCDA-4_0_0_xsd.tmp#criteriaMatrix_criteriaMatrix_row_column
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children column, criterionID
Instance
<row xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <criterionID>{1,1}</criterionID>
  <column>{1,unbounded}</column>
</row>
Source
<xs:element name="row" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A row of the matrix.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:choice>
        <xs:element name="criterionID" type="xs:string"/>
      </xs:choice>
      <xs:element name="column" maxOccurs="unbounded">
        <xs:complexType>
          <xs:annotation>
            <xs:documentation>A column of the matrix.</xs:documentation>
          </xs:annotation>
          <xs:sequence>
            <xs:element name="criterionID" type="xs:string"/>
            <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criteriaMatrix / row / criterionID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criterionID" type="xs:string"/>
Element criteriaMatrix / row / column
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaMatrix_criteriaMatrix_row_criteriaMatrix_criteriaMatrix_row_column_criterionID XMCDA-4_0_0_xsd.tmp#criteriaMatrix_criteriaMatrix_row_criteriaMatrix_criteriaMatrix_row_column_values
Properties
content complex
maxOccurs unbounded
Model
Children criterionID, values
Instance
<column xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <criterionID>{1,1}</criterionID>
  <values>{1,1}</values>
</column>
Source
<xs:element name="column" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A column of the matrix.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="criterionID" type="xs:string"/>
      <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criteriaMatrix / row / column / criterionID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criterionID" type="xs:string"/>
Element criteriaMatrix / row / column / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / criteriaScales
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaScales_description XMCDA-4_0_0_xsd.tmp#criteriaScales_criterionScales XMCDA-4_0_0_xsd.tmp#criteriaScales
Type criteriaScales
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criterionScales, description
Instance
<criteriaScales id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterionScales id="" mcdaConcept="" name="">{1,unbounded}</criterionScales>
</criteriaScales>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaScales" type="criteriaScales" minOccurs="0" maxOccurs="unbounded"/>
Element criteriaScales / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaScales / criterionScales
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criterionScales_description XMCDA-4_0_0_xsd.tmp#criterionScales_criterionID XMCDA-4_0_0_xsd.tmp#criterionScales_scales XMCDA-4_0_0_xsd.tmp#criterionScales
Type criterionScales
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children criterionID, description, scales
Instance
<criterionScales id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterionID>{1,1}</criterionID>
  <scales>{1,1}</scales>
</criterionScales>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criterionScales" type="criterionScales" minOccurs="1" maxOccurs="unbounded"/>
Element criterionScales / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element criterionScales / criterionID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criterionID" type="xs:string"/>
Element criterionScales / scales
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criterionScales_criterionScales_scales_description XMCDA-4_0_0_xsd.tmp#criterionScales_criterionScales_scales_scale XMCDA-4_0_0_xsd.tmp#criterionScales_criterionScales_scales_scaleID
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children description, scale, scaleID
Instance
<scales xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <scale id="" mcdaConcept="" name="">{1,1}</scale>
  <scaleID>{1,1}</scaleID>
</scales>
Source
<xs:element name="scales" minOccurs="1" maxOccurs="1">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>One or more scales related to a criterion.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="description" type="description" minOccurs="0"/>
      <xs:sequence>
        <xs:choice minOccurs="1" maxOccurs="unbounded">
          <xs:element name="scale" type="scale"/>
          <xs:element name="scaleID" type="xs:string">
            <xs:annotation>
              <xs:documentation>A reference to a scale defined anywhere in the parent criteriaScales.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:choice>
      </xs:sequence>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criterionScales / scales / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criterionScales / scales / scale
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#scale_nominal XMCDA-4_0_0_xsd.tmp#scale_qualitative XMCDA-4_0_0_xsd.tmp#scale_quantitative XMCDA-4_0_0_xsd.tmp#scale
Type scale
Properties
content complex
Model
Children nominal, qualitative, quantitative
Instance
<scale id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <nominal>{1,1}</nominal>
  <qualitative>{1,1}</qualitative>
  <quantitative>{1,1}</quantitative>
</scale>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="scale" type="scale"/>
Element scale / nominal
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#nominal_labels XMCDA-4_0_0_xsd.tmp#nominal
Type nominal
Properties
content complex
Model
Children labels
Instance
<nominal xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <labels>{1,1}</labels>
</nominal>
Source
<xs:element name="nominal" type="nominal"/>
Element nominal / labels
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#nominal_nominal_labels_label
Properties
content complex
Model
Children label
Instance
<labels xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <label>{1,unbounded}</label>
</labels>
Source
<xs:element name="labels">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>The set of labels used by a nominal scale.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="label" type="xs:string" minOccurs="1" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element nominal / labels / label
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 1
maxOccurs unbounded
Source
<xs:element name="label" type="xs:string" minOccurs="1" maxOccurs="unbounded"/>
Element scale / qualitative
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#qualitative_preferenceDirection XMCDA-4_0_0_xsd.tmp#qualitative_valuedLabels XMCDA-4_0_0_xsd.tmp#qualitative
Type qualitative
Properties
content complex
Model
Children preferenceDirection, valuedLabels
Instance
<qualitative xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <preferenceDirection>{0,1}</preferenceDirection>
  <valuedLabels>{1,1}</valuedLabels>
</qualitative>
Source
<xs:element name="qualitative" type="qualitative"/>
Element qualitative / preferenceDirection
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#preferenceDirection
Type preferenceDirection
Properties
content simple
minOccurs 0
Facets
enumeration min
enumeration max
Source
<xs:element name="preferenceDirection" type="preferenceDirection" minOccurs="0"/>
Element qualitative / valuedLabels
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#qualitative_qualitative_valuedLabels_valuedLabel
Properties
content complex
Model
Children valuedLabel
Instance
<valuedLabels xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <valuedLabel>{1,unbounded}</valuedLabel>
</valuedLabels>
Source
<xs:element name="valuedLabels">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>Sequence of valued labels. Could either be labels to which are associated ranks, or fuzzy labels.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="valuedLabel" type="valuedLabel" minOccurs="1" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element qualitative / valuedLabels / valuedLabel
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#valuedLabel_label XMCDA-4_0_0_xsd.tmp#valuedLabel_value XMCDA-4_0_0_xsd.tmp#valuedLabel
Type valuedLabel
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children label, value
Instance
<valuedLabel xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <label>{1,1}</label>
  <value id="" mcdaConcept="" name="">{1,1}</value>
</valuedLabel>
Source
<xs:element name="valuedLabel" type="valuedLabel" minOccurs="1" maxOccurs="unbounded"/>
Element scale / quantitative
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#quantitative_preferenceDirection XMCDA-4_0_0_xsd.tmp#quantitative_minimum XMCDA-4_0_0_xsd.tmp#quantitative_maximum XMCDA-4_0_0_xsd.tmp#quantitative
Type quantitative
Properties
content complex
Model
Children maximum, minimum, preferenceDirection
Instance
<quantitative xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <preferenceDirection>{0,1}</preferenceDirection>
  <minimum id="" mcdaConcept="" name="">{0,1}</minimum>
  <maximum id="" mcdaConcept="" name="">{0,1}</maximum>
</quantitative>
Source
<xs:element name="quantitative" type="quantitative"/>
Element quantitative / preferenceDirection
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#preferenceDirection
Type preferenceDirection
Properties
content simple
minOccurs 0
Facets
enumeration min
enumeration max
Source
<xs:element name="preferenceDirection" type="preferenceDirection" minOccurs="0"/>
Element quantitative / minimum
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children NA, integer, rational, real
Instance
<minimum id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</minimum>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="minimum" type="numericValue" minOccurs="0"/>
Element quantitative / maximum
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children NA, integer, rational, real
Instance
<maximum id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</maximum>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="maximum" type="numericValue" minOccurs="0"/>
Element criterionScales / scales / scaleID
Annotations
A reference to a scale defined anywhere in the parent criteriaScales.
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="scaleID" type="xs:string">
  <xs:annotation>
    <xs:documentation>A reference to a scale defined anywhere in the parent criteriaScales.</xs:documentation>
  </xs:annotation>
</xs:element>
Element xmcda / criteriaThresholds
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaThresholds_description XMCDA-4_0_0_xsd.tmp#criteriaThresholds_criterionThresholds XMCDA-4_0_0_xsd.tmp#criteriaThresholds
Type criteriaThresholds
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criterionThresholds, description
Instance
<criteriaThresholds id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterionThresholds id="" mcdaConcept="" name="">{1,unbounded}</criterionThresholds>
</criteriaThresholds>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaThresholds" type="criteriaThresholds" minOccurs="0" maxOccurs="unbounded"/>
Element criteriaThresholds / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaThresholds / criterionThresholds
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criterionThresholds_description XMCDA-4_0_0_xsd.tmp#criterionThresholds_criterionID XMCDA-4_0_0_xsd.tmp#criterionThresholds_thresholds XMCDA-4_0_0_xsd.tmp#criterionThresholds
Type criterionThresholds
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children criterionID, description, thresholds
Instance
<criterionThresholds id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterionID>{1,1}</criterionID>
  <thresholds>{1,1}</thresholds>
</criterionThresholds>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criterionThresholds" type="criterionThresholds" minOccurs="1" maxOccurs="unbounded"/>
Element criterionThresholds / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element criterionThresholds / criterionID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criterionID" type="xs:string"/>
Element criterionThresholds / thresholds
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criterionThresholds_criterionThresholds_thresholds_description XMCDA-4_0_0_xsd.tmp#criterionThresholds_criterionThresholds_thresholds_threshold
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children description, threshold
Instance
<thresholds xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <threshold id="" mcdaConcept="" name="">{1,unbounded}</threshold>
</thresholds>
Source
<xs:element name="thresholds" minOccurs="1" maxOccurs="1">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>One or more discrimination thresholds related to a criterion.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="description" type="description" minOccurs="0"/>
      <xs:element name="threshold" type="threshold" minOccurs="1" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criterionThresholds / thresholds / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criterionThresholds / thresholds / threshold
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#threshold_constant XMCDA-4_0_0_xsd.tmp#threshold_affine XMCDA-4_0_0_xsd.tmp#threshold
Type threshold
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children affine, constant
Instance
<threshold id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <constant id="" mcdaConcept="" name="">{1,1}</constant>
  <affine>{1,1}</affine>
</threshold>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="threshold" type="threshold" minOccurs="1" maxOccurs="unbounded"/>
Element threshold / constant
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<constant id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <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 and reference the underlying piece of data.
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="numericValue"/>
Element threshold / affine
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#threshold_threshold_affine_type XMCDA-4_0_0_xsd.tmp#threshold_threshold_affine_slope XMCDA-4_0_0_xsd.tmp#threshold_threshold_affine_intercept
Properties
content complex
Model
Children intercept, slope, type
Instance
<affine xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <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="numericValue" minOccurs="1" maxOccurs="1"/>
      <xs:element name="intercept" type="numericValue" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element threshold / affine / type
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 threshold / affine / slope
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children NA, integer, rational, real
Instance
<slope id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <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 and reference the underlying piece of data.
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="numericValue" minOccurs="1" maxOccurs="1"/>
Element threshold / affine / intercept
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children NA, integer, rational, real
Instance
<intercept id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <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 and reference the underlying piece of data.
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="numericValue" minOccurs="1" maxOccurs="1"/>
Element xmcda / criteriaValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaValues_description XMCDA-4_0_0_xsd.tmp#criteriaValues_criterionValues XMCDA-4_0_0_xsd.tmp#criteriaValues
Type criteriaValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criterionValues, description
Instance
<criteriaValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criterionValues id="" mcdaConcept="" name="">{1,unbounded}</criterionValues>
</criteriaValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaValues" minOccurs="0" maxOccurs="unbounded" type="criteriaValues"/>
Element xmcda / criteriaSetsHierarchy
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetsHierarchy_description XMCDA-4_0_0_xsd.tmp#criteriaSetsHierarchy_nodes XMCDA-4_0_0_xsd.tmp#criteriaSetsHierarchy
Type criteriaSetsHierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, nodes
Instance
<criteriaSetsHierarchy id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <nodes>{1,unbounded}</nodes>
</criteriaSetsHierarchy>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSetsHierarchy" minOccurs="0" maxOccurs="unbounded" type="criteriaSetsHierarchy"/>
Element criteriaSetsHierarchy / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaSetsHierarchy / nodes
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaSetsHierarchyNodes_node XMCDA-4_0_0_xsd.tmp#criteriaSetsHierarchyNodes
Type criteriaSetsHierarchyNodes
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children node
Instance
<nodes xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <node>{1,unbounded}</node>
</nodes>
Source
<xs:element name="nodes" type="criteriaSetsHierarchyNodes" minOccurs="1" maxOccurs="unbounded"/>
Element criteriaSetsHierarchyNodes / node
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaSetHierarchyNode_criteriaSetID XMCDA-4_0_0_xsd.tmp#criteriaSetHierarchyNode_nodes XMCDA-4_0_0_xsd.tmp#criteriaSetHierarchyNode
Type criteriaSetHierarchyNode
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children criteriaSetID, nodes
Instance
<node xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <criteriaSetID>{1,1}</criteriaSetID>
  <nodes>{0,unbounded}</nodes>
</node>
Source
<xs:element name="node" type="criteriaSetHierarchyNode" minOccurs="1" maxOccurs="unbounded"/>
Element criteriaSetHierarchyNode / criteriaSetID
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 1
maxOccurs 1
Source
<xs:element name="criteriaSetID" type="xs:string" minOccurs="1" maxOccurs="1"/>
Element criteriaSetHierarchyNode / nodes
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaSetsHierarchyNodes_node XMCDA-4_0_0_xsd.tmp#criteriaSetsHierarchyNodes
Type criteriaSetsHierarchyNodes
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children node
Instance
<nodes xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <node>{1,unbounded}</node>
</nodes>
Source
<xs:element name="nodes" type="criteriaSetsHierarchyNodes" minOccurs="0" maxOccurs="unbounded"/>
Element xmcda / criteriaSetsLinearConstraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_description XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_constraints XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints
Type criteriaSetsLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<criteriaSetsLinearConstraints id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <variables>{0,1}</variables>
  <constraints>{1,1}</constraints>
</criteriaSetsLinearConstraints>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="criteriaSetsLinearConstraints"/>
Element criteriaSetsLinearConstraints / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaSetsLinearConstraints / variables
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#variables_variable XMCDA-4_0_0_xsd.tmp#variables
Type variables
Properties
content complex
minOccurs 0
Model
Children variable
Instance
<variables xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <variable id="" mcdaConcept="" name="">{1,unbounded}</variable>
</variables>
Source
<xs:element name="variables" type="variables" minOccurs="0"/>
Element criteriaSetsLinearConstraints / constraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint
Properties
content complex
Model
Children constraint
Instance
<constraints xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <constraint id="" mcdaConcept="" name="">{1,unbounded}</constraint>
</constraints>
Source
<xs:element name="constraints">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:annotation>
            <xs:documentation>A linear constraint related to criteria. It is constructed from a sum of elements, each element being composed of a reference to a set of criteria or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
          </xs:annotation>
          <xs:sequence>
            <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
            <xs:element name="elements" minOccurs="0" maxOccurs="1">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:choice>
                          <xs:element name="criteriaSetID" type="xs:string"/>
                          <xs:element name="variableID" type="xs:string"/>
                        </xs:choice>
                        <xs:element name="coefficient" type="numericValue"/>
                      </xs:sequence>
                      <xs:attributeGroup ref="defaultAttributes"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name="operator" minOccurs="1">
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="geq"/>
                  <xs:enumeration value="eq"/>
                  <xs:enumeration value="leq"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="rhs" type="numericValue"/>
            <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criteriaSetsLinearConstraints / constraints / constraint
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_description XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_elements XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_operator XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_rhs XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_values
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children description, elements, operator, rhs, values
Instance
<constraint id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <elements>{0,1}</elements>
  <operator>{1,1}</operator>
  <rhs id="" mcdaConcept="" name="">{1,1}</rhs>
  <values>{0,1}</values>
</constraint>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="constraint" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A linear constraint related to criteria. It is constructed from a sum of elements, each element being composed of a reference to a set of criteria or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
      <xs:element name="elements" minOccurs="0" maxOccurs="1">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:choice>
                    <xs:element name="criteriaSetID" type="xs:string"/>
                    <xs:element name="variableID" type="xs:string"/>
                  </xs:choice>
                  <xs:element name="coefficient" type="numericValue"/>
                </xs:sequence>
                <xs:attributeGroup ref="defaultAttributes"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="operator" minOccurs="1">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="geq"/>
            <xs:enumeration value="eq"/>
            <xs:enumeration value="leq"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="rhs" type="numericValue"/>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element criteriaSetsLinearConstraints / constraints / constraint / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element criteriaSetsLinearConstraints / constraints / constraint / elements
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_elements_element
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children element
Instance
<elements xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <element id="" mcdaConcept="" name="">{1,unbounded}</element>
</elements>
Source
<xs:element name="elements" minOccurs="0" maxOccurs="1">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:choice>
              <xs:element name="criteriaSetID" type="xs:string"/>
              <xs:element name="variableID" type="xs:string"/>
            </xs:choice>
            <xs:element name="coefficient" type="numericValue"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criteriaSetsLinearConstraints / constraints / constraint / elements / element
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_elements_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_elements_element_criteriaSetID XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_elements_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_elements_element_variableID XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_elements_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_criteriaSetsLinearConstraints_criteriaSetsLinearConstraints_constraints_constraint_elements_element_coefficient
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children coefficient, criteriaSetID, variableID
Instance
<element id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <criteriaSetID>{1,1}</criteriaSetID>
  <variableID>{1,1}</variableID>
  <coefficient id="" mcdaConcept="" name="">{1,1}</coefficient>
</element>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="element" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:choice>
        <xs:element name="criteriaSetID" type="xs:string"/>
        <xs:element name="variableID" type="xs:string"/>
      </xs:choice>
      <xs:element name="coefficient" type="numericValue"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element criteriaSetsLinearConstraints / constraints / constraint / elements / element / criteriaSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criteriaSetID" type="xs:string"/>
Element criteriaSetsLinearConstraints / constraints / constraint / elements / element / variableID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="variableID" type="xs:string"/>
Element criteriaSetsLinearConstraints / constraints / constraint / elements / element / coefficient
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<coefficient id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</coefficient>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="coefficient" type="numericValue"/>
Element criteriaSetsLinearConstraints / constraints / constraint / operator
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 1
Facets
enumeration geq
enumeration eq
enumeration leq
Source
<xs:element name="operator" minOccurs="1">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="geq"/>
      <xs:enumeration value="eq"/>
      <xs:enumeration value="leq"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element criteriaSetsLinearConstraints / constraints / constraint / rhs
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<rhs id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</rhs>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="rhs" type="numericValue"/>
Element criteriaSetsLinearConstraints / constraints / constraint / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / criteriaSetsMatrix
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetsMatrix_description XMCDA-4_0_0_xsd.tmp#criteriaSetsMatrix_row XMCDA-4_0_0_xsd.tmp#criteriaSetsMatrix
Type criteriaSetsMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row
Instance
<criteriaSetsMatrix id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <row>{1,unbounded}</row>
</criteriaSetsMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="criteriaSetsMatrix"/>
Element criteriaSetsMatrix / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaSetsMatrix / row
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaSetsMatrix_criteriaSetsMatrix_row_criteriaSetID XMCDA-4_0_0_xsd.tmp#criteriaSetsMatrix_criteriaSetsMatrix_row_column
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children column, criteriaSetID
Instance
<row xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <criteriaSetID>{1,1}</criteriaSetID>
  <column>{1,unbounded}</column>
</row>
Source
<xs:element name="row" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A row of the matrix.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="criteriaSetID" type="xs:string"/>
      <xs:element name="column" maxOccurs="unbounded">
        <xs:complexType>
          <xs:annotation>
            <xs:documentation>A column of the matrix.</xs:documentation>
          </xs:annotation>
          <xs:sequence>
            <xs:element name="criteriaSetID" type="xs:string"/>
            <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criteriaSetsMatrix / row / criteriaSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criteriaSetID" type="xs:string"/>
Element criteriaSetsMatrix / row / column
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaSetsMatrix_criteriaSetsMatrix_row_criteriaSetsMatrix_criteriaSetsMatrix_row_column_criteriaSetID XMCDA-4_0_0_xsd.tmp#criteriaSetsMatrix_criteriaSetsMatrix_row_criteriaSetsMatrix_criteriaSetsMatrix_row_column_values
Properties
content complex
maxOccurs unbounded
Model
Children criteriaSetID, values
Instance
<column xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <criteriaSetID>{1,1}</criteriaSetID>
  <values>{1,1}</values>
</column>
Source
<xs:element name="column" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A column of the matrix.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="criteriaSetID" type="xs:string"/>
      <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element criteriaSetsMatrix / row / column / criteriaSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criteriaSetID" type="xs:string"/>
Element criteriaSetsMatrix / row / column / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / criteriaSetsValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetsValues_description XMCDA-4_0_0_xsd.tmp#criteriaSetsValues_criteriaSetValues XMCDA-4_0_0_xsd.tmp#criteriaSetsValues
Type criteriaSetsValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criteriaSetValues, description
Instance
<criteriaSetsValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criteriaSetValues id="" mcdaConcept="" name="">{1,unbounded}</criteriaSetValues>
</criteriaSetsValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSetsValues" minOccurs="0" maxOccurs="unbounded" type="criteriaSetsValues"/>
Element criteriaSetsValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaSetsValues / criteriaSetValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetValues_description XMCDA-4_0_0_xsd.tmp#criteriaSetValues_criteriaSetID XMCDA-4_0_0_xsd.tmp#criteriaSetValues_values XMCDA-4_0_0_xsd.tmp#criteriaSetValues
Type criteriaSetValues
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children criteriaSetID, description, values
Instance
<criteriaSetValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <criteriaSetID>{1,1}</criteriaSetID>
  <values>{1,1}</values>
</criteriaSetValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSetValues" type="criteriaSetValues" minOccurs="1" maxOccurs="unbounded"/>
Element criteriaSetValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element criteriaSetValues / criteriaSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="criteriaSetID" type="xs:string"/>
Element criteriaSetValues / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / categoriesLinearConstraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_description XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_constraints XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints
Type categoriesLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<categoriesLinearConstraints id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <variables>{0,1}</variables>
  <constraints>{1,1}</constraints>
</categoriesLinearConstraints>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="categoriesLinearConstraints"/>
Element categoriesLinearConstraints / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesLinearConstraints / variables
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#variables_variable XMCDA-4_0_0_xsd.tmp#variables
Type variables
Properties
content complex
minOccurs 0
Model
Children variable
Instance
<variables xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <variable id="" mcdaConcept="" name="">{1,unbounded}</variable>
</variables>
Source
<xs:element name="variables" type="variables" minOccurs="0"/>
Element categoriesLinearConstraints / constraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint
Properties
content complex
Model
Children constraint
Instance
<constraints xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <constraint id="" mcdaConcept="" name="">{1,unbounded}</constraint>
</constraints>
Source
<xs:element name="constraints">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:annotation>
            <xs:documentation>A linear constraint related to categories. It is constructed from a sum of elements, each element being composed of a reference to a category or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
          </xs:annotation>
          <xs:sequence>
            <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
            <xs:element name="elements" minOccurs="0" maxOccurs="1">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:choice>
                          <xs:element name="categoryID" type="xs:string"/>
                          <xs:element name="variableID" type="xs:string"/>
                        </xs:choice>
                        <xs:element name="coefficient" type="numericValue"/>
                      </xs:sequence>
                      <xs:attributeGroup ref="defaultAttributes"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name="operator" minOccurs="1">
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="geq"/>
                  <xs:enumeration value="eq"/>
                  <xs:enumeration value="leq"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="rhs" type="numericValue"/>
            <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element categoriesLinearConstraints / constraints / constraint
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_description XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_elements XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_operator XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_rhs XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_values
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children description, elements, operator, rhs, values
Instance
<constraint id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <elements>{0,1}</elements>
  <operator>{1,1}</operator>
  <rhs id="" mcdaConcept="" name="">{1,1}</rhs>
  <values>{0,1}</values>
</constraint>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="constraint" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A linear constraint related to categories. It is constructed from a sum of elements, each element being composed of a reference to a category or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
      <xs:element name="elements" minOccurs="0" maxOccurs="1">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:choice>
                    <xs:element name="categoryID" type="xs:string"/>
                    <xs:element name="variableID" type="xs:string"/>
                  </xs:choice>
                  <xs:element name="coefficient" type="numericValue"/>
                </xs:sequence>
                <xs:attributeGroup ref="defaultAttributes"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="operator" minOccurs="1">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="geq"/>
            <xs:enumeration value="eq"/>
            <xs:enumeration value="leq"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="rhs" type="numericValue"/>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element categoriesLinearConstraints / constraints / constraint / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element categoriesLinearConstraints / constraints / constraint / elements
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_elements_element
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children element
Instance
<elements xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <element id="" mcdaConcept="" name="">{1,unbounded}</element>
</elements>
Source
<xs:element name="elements" minOccurs="0" maxOccurs="1">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:choice>
              <xs:element name="categoryID" type="xs:string"/>
              <xs:element name="variableID" type="xs:string"/>
            </xs:choice>
            <xs:element name="coefficient" type="numericValue"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element categoriesLinearConstraints / constraints / constraint / elements / element
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_elements_categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_elements_element_categoryID XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_elements_categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_elements_element_variableID XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_elements_categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_categoriesLinearConstraints_categoriesLinearConstraints_constraints_categoriesLinearConstraints_categoriesLinearConstraints_constraints_constraint_elements_element_coefficient
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children categoryID, coefficient, variableID
Instance
<element id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <categoryID>{1,1}</categoryID>
  <variableID>{1,1}</variableID>
  <coefficient id="" mcdaConcept="" name="">{1,1}</coefficient>
</element>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="element" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:choice>
        <xs:element name="categoryID" type="xs:string"/>
        <xs:element name="variableID" type="xs:string"/>
      </xs:choice>
      <xs:element name="coefficient" type="numericValue"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element categoriesLinearConstraints / constraints / constraint / elements / element / categoryID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoryID" type="xs:string"/>
Element categoriesLinearConstraints / constraints / constraint / elements / element / variableID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="variableID" type="xs:string"/>
Element categoriesLinearConstraints / constraints / constraint / elements / element / coefficient
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<coefficient id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</coefficient>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="coefficient" type="numericValue"/>
Element categoriesLinearConstraints / constraints / constraint / operator
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 1
Facets
enumeration geq
enumeration eq
enumeration leq
Source
<xs:element name="operator" minOccurs="1">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="geq"/>
      <xs:enumeration value="eq"/>
      <xs:enumeration value="leq"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element categoriesLinearConstraints / constraints / constraint / rhs
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<rhs id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</rhs>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="rhs" type="numericValue"/>
Element categoriesLinearConstraints / constraints / constraint / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / categoriesMatrix
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesMatrix_description XMCDA-4_0_0_xsd.tmp#categoriesMatrix_row XMCDA-4_0_0_xsd.tmp#categoriesMatrix
Type categoriesMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row
Instance
<categoriesMatrix id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <row>{1,unbounded}</row>
</categoriesMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesMatrix" minOccurs="0" maxOccurs="unbounded" type="categoriesMatrix"/>
Element categoriesMatrix / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesMatrix / row
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesMatrix_categoriesMatrix_row_categoryID XMCDA-4_0_0_xsd.tmp#categoriesMatrix_categoriesMatrix_row_column
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children categoryID, column
Instance
<row xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <categoryID>{1,1}</categoryID>
  <column>{1,unbounded}</column>
</row>
Source
<xs:element name="row" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A row of a matrix.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="categoryID" type="xs:string"/>
      <xs:element name="column" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="categoryID" type="xs:string"/>
            <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element categoriesMatrix / row / categoryID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoryID" type="xs:string"/>
Element categoriesMatrix / row / column
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesMatrix_categoriesMatrix_row_categoriesMatrix_categoriesMatrix_row_column_categoryID XMCDA-4_0_0_xsd.tmp#categoriesMatrix_categoriesMatrix_row_categoriesMatrix_categoriesMatrix_row_column_values
Properties
content complex
maxOccurs unbounded
Model
Children categoryID, values
Instance
<column xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <categoryID>{1,1}</categoryID>
  <values>{1,1}</values>
</column>
Source
<xs:element name="column" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="categoryID" type="xs:string"/>
      <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element categoriesMatrix / row / column / categoryID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoryID" type="xs:string"/>
Element categoriesMatrix / row / column / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / categoriesProfiles
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesProfiles_description XMCDA-4_0_0_xsd.tmp#categoriesProfiles_categoryProfile XMCDA-4_0_0_xsd.tmp#categoriesProfiles
Type categoriesProfiles
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children categoryProfile, description
Instance
<categoriesProfiles id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <categoryProfile id="" mcdaConcept="" name="">{0,unbounded}</categoryProfile>
</categoriesProfiles>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesProfiles" minOccurs="0" maxOccurs="unbounded" type="categoriesProfiles"/>
Element categoriesProfiles / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesProfiles / categoryProfile
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoryProfile_description XMCDA-4_0_0_xsd.tmp#categoryProfile_categoryID XMCDA-4_0_0_xsd.tmp#categoryProfile_central XMCDA-4_0_0_xsd.tmp#categoryProfile_bounding XMCDA-4_0_0_xsd.tmp#categoryProfile
Type categoryProfile
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children bounding, categoryID, central, description
Instance
<categoryProfile id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <categoryID>{1,1}</categoryID>
  <central>{1,1}</central>
  <bounding>{1,1}</bounding>
</categoryProfile>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoryProfile" minOccurs="0" maxOccurs="unbounded" type="categoryProfile"/>
Element categoryProfile / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoryProfile / categoryID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoryID" type="xs:string"/>
Element categoryProfile / central
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoryProfile_categoryProfile_central_alternativeID XMCDA-4_0_0_xsd.tmp#categoryProfile_categoryProfile_central_values
Properties
content complex
Model
Children alternativeID, values
Instance
<central xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <values>{0,unbounded}</values>
</central>
Source
<xs:element name="central">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="alternativeID" type="xs:string"/>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element categoryProfile / central / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativeID" type="xs:string"/>
Element categoryProfile / central / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="unbounded"/>
Element categoryProfile / bounding
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoryProfile_categoryProfile_bounding_lowerBound XMCDA-4_0_0_xsd.tmp#categoryProfile_categoryProfile_bounding_upperBound
Properties
content complex
Model
Children lowerBound, upperBound
Instance
<bounding xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <lowerBound>{1,1}</lowerBound>
  <upperBound>{0,1}</upperBound>
  <upperBound>{1,1}</upperBound>
</bounding>
Source
<xs:element name="bounding">
  <xs:complexType>
    <!-- At least one among (lowerBound, upperBound), or both -->
    <xs:choice>
      <xs:sequence>
        <xs:element name="lowerBound" type="categoryProfileBound"/>
        <xs:element name="upperBound" type="categoryProfileBound" minOccurs="0"/>
      </xs:sequence>
      <xs:element name="upperBound" type="categoryProfileBound"/>
    </xs:choice>
  </xs:complexType>
</xs:element>
Element categoryProfile / bounding / lowerBound
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoryProfileBound_alternativeID XMCDA-4_0_0_xsd.tmp#categoryProfileBound_values XMCDA-4_0_0_xsd.tmp#categoryProfileBound
Type categoryProfileBound
Properties
content complex
Model
Children alternativeID, values
Instance
<lowerBound xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <values>{0,1}</values>
</lowerBound>
Source
<xs:element name="lowerBound" type="categoryProfileBound"/>
Element categoryProfileBound / alternativeID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="alternativeID" type="xs:string"/>
Element categoryProfileBound / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element categoryProfile / bounding / upperBound
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoryProfileBound_alternativeID XMCDA-4_0_0_xsd.tmp#categoryProfileBound_values XMCDA-4_0_0_xsd.tmp#categoryProfileBound
Type categoryProfileBound
Properties
content complex
minOccurs 0
Model
Children alternativeID, values
Instance
<upperBound xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <alternativeID>{1,1}</alternativeID>
  <values>{0,1}</values>
</upperBound>
Source
<xs:element name="upperBound" type="categoryProfileBound" minOccurs="0"/>
Element xmcda / categoriesValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesValues_description XMCDA-4_0_0_xsd.tmp#categoriesValues_categoryValues XMCDA-4_0_0_xsd.tmp#categoriesValues
Type categoriesValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children categoryValues, description
Instance
<categoriesValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <categoryValues id="" mcdaConcept="" name="">{1,unbounded}</categoryValues>
</categoriesValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesValues" minOccurs="0" maxOccurs="unbounded" type="categoriesValues"/>
Element categoriesValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesValues / categoryValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoryValues_description XMCDA-4_0_0_xsd.tmp#categoryValues_categoryID XMCDA-4_0_0_xsd.tmp#categoryValues_values XMCDA-4_0_0_xsd.tmp#categoryValues
Type categoryValues
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children categoryID, description, values
Instance
<categoryValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <categoryID>{1,1}</categoryID>
  <values>{1,1}</values>
</categoryValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoryValues" type="categoryValues" minOccurs="1" maxOccurs="unbounded"/>
Element categoryValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoryValues / categoryID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoryID" type="xs:string"/>
Element categoryValues / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / categoriesSetsLinearConstraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_description XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_constraints XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints
Type categoriesSetsLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<categoriesSetsLinearConstraints id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <variables>{0,1}</variables>
  <constraints>{1,1}</constraints>
</categoriesSetsLinearConstraints>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="categoriesSetsLinearConstraints"/>
Element categoriesSetsLinearConstraints / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesSetsLinearConstraints / variables
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#variables_variable XMCDA-4_0_0_xsd.tmp#variables
Type variables
Properties
content complex
minOccurs 0
Model
Children variable
Instance
<variables xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <variable id="" mcdaConcept="" name="">{1,unbounded}</variable>
</variables>
Source
<xs:element name="variables" type="variables" minOccurs="0"/>
Element categoriesSetsLinearConstraints / constraints
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint
Properties
content complex
Model
Children constraint
Instance
<constraints xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <constraint id="" mcdaConcept="" name="">{1,unbounded}</constraint>
</constraints>
Source
<xs:element name="constraints">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:annotation>
            <xs:documentation>A linear constraint related to sets of categories. It is constructed from a sum of elements, each element being composed of a reference to a category set or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
          </xs:annotation>
          <xs:sequence>
            <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
            <xs:element name="elements" minOccurs="0" maxOccurs="1">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:choice>
                          <xs:element name="categoriesSetID" type="xs:string"/>
                          <xs:element name="variableID" type="xs:string"/>
                        </xs:choice>
                        <xs:element name="coefficient" type="numericValue"/>
                      </xs:sequence>
                      <xs:attributeGroup ref="defaultAttributes"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name="operator" minOccurs="1">
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="geq"/>
                  <xs:enumeration value="eq"/>
                  <xs:enumeration value="leq"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="rhs" type="numericValue"/>
            <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element categoriesSetsLinearConstraints / constraints / constraint
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_description XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_elements XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_operator XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_rhs XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_values
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children description, elements, operator, rhs, values
Instance
<constraint id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <elements>{0,1}</elements>
  <operator>{1,1}</operator>
  <rhs id="" mcdaConcept="" name="">{1,1}</rhs>
  <values>{0,1}</values>
</constraint>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="constraint" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A linear constraint related to sets of categories. It is constructed from a sum of elements, each element being composed of a reference to a category set or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
      <xs:element name="elements" minOccurs="0" maxOccurs="1">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:choice>
                    <xs:element name="categoriesSetID" type="xs:string"/>
                    <xs:element name="variableID" type="xs:string"/>
                  </xs:choice>
                  <xs:element name="coefficient" type="numericValue"/>
                </xs:sequence>
                <xs:attributeGroup ref="defaultAttributes"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="operator" minOccurs="1">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="geq"/>
            <xs:enumeration value="eq"/>
            <xs:enumeration value="leq"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="rhs" type="numericValue"/>
      <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element categoriesSetsLinearConstraints / constraints / constraint / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element categoriesSetsLinearConstraints / constraints / constraint / elements
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_elements_element
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children element
Instance
<elements xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <element id="" mcdaConcept="" name="">{1,unbounded}</element>
</elements>
Source
<xs:element name="elements" minOccurs="0" maxOccurs="1">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:choice>
              <xs:element name="categoriesSetID" type="xs:string"/>
              <xs:element name="variableID" type="xs:string"/>
            </xs:choice>
            <xs:element name="coefficient" type="numericValue"/>
          </xs:sequence>
          <xs:attributeGroup ref="defaultAttributes"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element categoriesSetsLinearConstraints / constraints / constraint / elements / element
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_elements_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_elements_element_categoriesSetID XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_elements_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_elements_element_variableID XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_elements_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_categoriesSetsLinearConstraints_categoriesSetsLinearConstraints_constraints_constraint_elements_element_coefficient
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children categoriesSetID, coefficient, variableID
Instance
<element id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <categoriesSetID>{1,1}</categoriesSetID>
  <variableID>{1,1}</variableID>
  <coefficient id="" mcdaConcept="" name="">{1,1}</coefficient>
</element>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="element" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:choice>
        <xs:element name="categoriesSetID" type="xs:string"/>
        <xs:element name="variableID" type="xs:string"/>
      </xs:choice>
      <xs:element name="coefficient" type="numericValue"/>
    </xs:sequence>
    <xs:attributeGroup ref="defaultAttributes"/>
  </xs:complexType>
</xs:element>
Element categoriesSetsLinearConstraints / constraints / constraint / elements / element / categoriesSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoriesSetID" type="xs:string"/>
Element categoriesSetsLinearConstraints / constraints / constraint / elements / element / variableID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="variableID" type="xs:string"/>
Element categoriesSetsLinearConstraints / constraints / constraint / elements / element / coefficient
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<coefficient id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</coefficient>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="coefficient" type="numericValue"/>
Element categoriesSetsLinearConstraints / constraints / constraint / operator
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 1
Facets
enumeration geq
enumeration eq
enumeration leq
Source
<xs:element name="operator" minOccurs="1">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="geq"/>
      <xs:enumeration value="eq"/>
      <xs:enumeration value="leq"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element categoriesSetsLinearConstraints / constraints / constraint / rhs
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA XMCDA-4_0_0_xsd.tmp#numericValue
Type numericValue
Type hierarchy
Properties
content complex
Model
Children NA, integer, rational, real
Instance
<rhs id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</rhs>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="rhs" type="numericValue"/>
Element categoriesSetsLinearConstraints / constraints / constraint / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
Element xmcda / categoriesSetsMatrix
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSetsMatrix_description XMCDA-4_0_0_xsd.tmp#categoriesSetsMatrix_row XMCDA-4_0_0_xsd.tmp#categoriesSetsMatrix
Type categoriesSetsMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row
Instance
<categoriesSetsMatrix id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <row>{1,unbounded}</row>
</categoriesSetsMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="categoriesSetsMatrix"/>
Element categoriesSetsMatrix / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesSetsMatrix / row
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesSetsMatrix_categoriesSetsMatrix_row_categoriesSetID XMCDA-4_0_0_xsd.tmp#categoriesSetsMatrix_categoriesSetsMatrix_row_column
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children categoriesSetID, column
Instance
<row xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <categoriesSetID>{1,1}</categoriesSetID>
  <column>{1,unbounded}</column>
</row>
Source
<xs:element name="row" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A row of a matrix.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="categoriesSetID" type="xs:string"/>
      <xs:element name="column" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="categoriesSetID" type="xs:string"/>
            <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element categoriesSetsMatrix / row / categoriesSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoriesSetID" type="xs:string"/>
Element categoriesSetsMatrix / row / column
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesSetsMatrix_categoriesSetsMatrix_row_categoriesSetsMatrix_categoriesSetsMatrix_row_column_categoriesSetID XMCDA-4_0_0_xsd.tmp#categoriesSetsMatrix_categoriesSetsMatrix_row_categoriesSetsMatrix_categoriesSetsMatrix_row_column_values
Properties
content complex
maxOccurs unbounded
Model
Children categoriesSetID, values
Instance
<column xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <categoriesSetID>{1,1}</categoriesSetID>
  <values>{1,1}</values>
</column>
Source
<xs:element name="column" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="categoriesSetID" type="xs:string"/>
      <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element categoriesSetsMatrix / row / column / categoriesSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoriesSetID" type="xs:string"/>
Element categoriesSetsMatrix / row / column / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / categoriesSetsValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSetsValues_description XMCDA-4_0_0_xsd.tmp#categoriesSetsValues_categoriesSetValues XMCDA-4_0_0_xsd.tmp#categoriesSetsValues
Type categoriesSetsValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children categoriesSetValues, description
Instance
<categoriesSetsValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <categoriesSetValues id="" mcdaConcept="" name="">{1,unbounded}</categoriesSetValues>
</categoriesSetsValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesSetsValues" minOccurs="0" maxOccurs="unbounded" type="categoriesSetsValues"/>
Element categoriesSetsValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesSetsValues / categoriesSetValues
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSetValues_description XMCDA-4_0_0_xsd.tmp#categoriesSetValues_categoriesSetID XMCDA-4_0_0_xsd.tmp#categoriesSetValues_values XMCDA-4_0_0_xsd.tmp#categoriesSetValues
Type categoriesSetValues
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children categoriesSetID, description, values
Instance
<categoriesSetValues id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <categoriesSetID>{1,1}</categoriesSetID>
  <values>{1,1}</values>
</categoriesSetValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesSetValues" type="categoriesSetValues" minOccurs="1" maxOccurs="unbounded"/>
Element categoriesSetValues / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element categoriesSetValues / categoriesSetID
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="categoriesSetID" type="xs:string"/>
Element categoriesSetValues / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
Element xmcda / programParameters
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#programParameters_description XMCDA-4_0_0_xsd.tmp#programParameters_programParameter XMCDA-4_0_0_xsd.tmp#programParameters
Type programParameters
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, programParameter
Instance
<programParameters id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <programParameter id="" mcdaConcept="" name="">{1,unbounded}</programParameter>
</programParameters>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="programParameters" type="programParameters" minOccurs="0" maxOccurs="unbounded"/>
Element programParameters / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element programParameters / programParameter
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#programParameter_description XMCDA-4_0_0_xsd.tmp#programParameter_values XMCDA-4_0_0_xsd.tmp#programParameter
Type programParameter
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children description, values
Instance
<programParameter id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <values>{1,1}</values>
</programParameter>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="programParameter" type="programParameter" minOccurs="1" maxOccurs="unbounded"/>
Element programParameter / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
Element programParameter / values
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value XMCDA-4_0_0_xsd.tmp#values
Type values
Properties
content complex
Model
Children value
Instance
<values xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <value id="" mcdaConcept="" name="">{1,unbounded}</value>
</values>
Source
<xs:element name="values" type="values"/>
Element xmcda / programExecutionResult
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#programExecutionResult_description XMCDA-4_0_0_xsd.tmp#programExecutionResult_status XMCDA-4_0_0_xsd.tmp#programExecutionResult_messages XMCDA-4_0_0_xsd.tmp#programExecutionResult
Type programExecutionResult
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, messages, status
Instance
<programExecutionResult id="" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <status>{0,1}</status>
  <messages>{0,1}</messages>
</programExecutionResult>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="programExecutionResult" type="programExecutionResult" minOccurs="0" maxOccurs="unbounded"/>
Element programExecutionResult / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element programExecutionResult / status
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#executionStatus
Type executionStatus
Properties
content simple
minOccurs 0
Facets
enumeration ok
enumeration warning
enumeration error
enumeration terminated
Source
<xs:element name="status" type="executionStatus" minOccurs="0"/>
Element programExecutionResult / messages
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#programExecutionResult_programExecutionResult_messages_message
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children message
Instance
<messages xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <message id="" level="info" mcdaConcept="" name="">{0,unbounded}</message>
</messages>
Source
<xs:element name="messages" minOccurs="0" maxOccurs="1">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="message" type="message" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element programExecutionResult / messages / message
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#message_level XMCDA-4_0_0_xsd.tmp#message_description XMCDA-4_0_0_xsd.tmp#message_text XMCDA-4_0_0_xsd.tmp#message
Type message
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, text
Instance
<message id="" level="info" mcdaConcept="" name="" xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <description>{0,1}</description>
  <text>{1,1}</text>
</message>
Attributes
QName Type Default Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
level messageLevel info optional
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="message" type="message" minOccurs="0" maxOccurs="unbounded"/>
Element message / description
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate XMCDA-4_0_0_xsd.tmp#description
Type description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
<description xmlns="http://www.decision-deck.org/2021/XMCDA-4.0.0">
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
<xs:element name="description" type="description" minOccurs="0"/>
Element message / text
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="text" type="xs:string"/>
Complex Type alternatives
Annotations
The set of alternatives.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternatives_description XMCDA-4_0_0_xsd.tmp#alternatives_alternative
Used by
Model
Children alternative, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternatives">
  <xs:annotation>
    <xs:documentation>The set of alternatives.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
    <xs:element name="alternative" type="alternative" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type description
Annotations
Description of most of the tags. The names of the elements suggest their standard use.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#description_author XMCDA-4_0_0_xsd.tmp#description_comment XMCDA-4_0_0_xsd.tmp#description_keyword XMCDA-4_0_0_xsd.tmp#description_bibliography XMCDA-4_0_0_xsd.tmp#description_creationDate XMCDA-4_0_0_xsd.tmp#description_lastModificationDate
Used by
Elements alternative/description, alternativeAssignment/description, alternativeOnCriteriaPerformances/performance/description, alternativeValues/description, alternatives/description, alternativesAssignments/description, alternativesCriteriaValues/description, alternativesLinearConstraints/constraints/constraint/description, alternativesLinearConstraints/description, alternativesMatrix/description, alternativesSet/description, alternativesSetValues/description, alternativesSets/description, alternativesSetsLinearConstraints/constraints/constraint/description, alternativesSetsLinearConstraints/description, alternativesSetsMatrix/description, alternativesSetsValues/description, alternativesValues/description, bibliography/description, categories/description, categoriesInterval/description, categoriesLinearConstraints/constraints/constraint/description, categoriesLinearConstraints/description, categoriesMatrix/description, categoriesProfiles/description, categoriesSet/description, categoriesSetValues/description, categoriesSets/description, categoriesSetsLinearConstraints/constraints/constraint/description, categoriesSetsLinearConstraints/description, categoriesSetsMatrix/description, categoriesSetsValues/description, categoriesValues/description, category/description, categoryProfile/description, categoryValues/description, criteria/description, criteriaFunctions/description, criteriaHierarchy/description, criteriaLinearConstraints/constraints/constraint/description, criteriaLinearConstraints/description, criteriaMatrix/description, criteriaScales/description, criteriaSet/description, criteriaSetValues/description, criteriaSets/description, criteriaSetsHierarchy/description, criteriaSetsLinearConstraints/constraints/constraint/description, criteriaSetsLinearConstraints/description, criteriaSetsMatrix/description, criteriaSetsValues/description, criteriaThresholds/description, criteriaValues/description, criterion/description, criterionFunctions/description, criterionScales/description, criterionScales/scales/description, criterionThresholds/description, criterionThresholds/thresholds/description, criterionValues/description, message/description, performanceTable/description, programExecutionResult/description, programParameter/description, programParameters/description, variable/description
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Source
<xs:complexType name="description">
  <xs:annotation>
    <xs:documentation>Description of most of the tags. The names of the elements suggest their standard use.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="author" minOccurs="0" maxOccurs="unbounded" type="xs:string"/>
    <xs:element name="comment" minOccurs="0" maxOccurs="1" type="xs:string"/>
    <xs:element name="keyword" minOccurs="0" maxOccurs="unbounded" type="xs:string"/>
    <xs:element name="bibliography" minOccurs="0" maxOccurs="1" type="bibliography"/>
    <xs:element name="creationDate" minOccurs="0" maxOccurs="1" type="xs:dateTime"/>
    <xs:element name="lastModificationDate" minOccurs="0" maxOccurs="1" type="xs:dateTime"/>
  </xs:sequence>
</xs:complexType>
Complex Type bibliography
Annotations
Bibliographical entries
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#bibliography_description XMCDA-4_0_0_xsd.tmp#bibliography_bibEntry
Used by
Model
Children bibEntry, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="bibliography">
  <xs:annotation>
    <xs:documentation>Bibliographical entries</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
    <xs:element name="bibEntry" type="xs:string" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation/>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternative
Annotations
Definition of an alternative. The id attribute is mandatory.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#alternative_description XMCDA-4_0_0_xsd.tmp#alternative_type XMCDA-4_0_0_xsd.tmp#alternative_active
Used by
Model
Children active, description, type
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="alternative">
  <xs:annotation>
    <xs:documentation>Definition of an alternative. The id attribute is mandatory.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
    <xs:element name="type" minOccurs="0" maxOccurs="1" default="real">
      <xs:annotation>
        <xs:documentation>Type Indicates whether an alternative is real or fictive. By default, if the tag is not present, an alternative is considered as real. Fictive alternatives are those which might not exist in reality, but can be used for some preference elicitation means.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="real"/>
          <xs:enumeration value="fictive"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="active" type="xs:boolean" minOccurs="0" maxOccurs="1" default="true">
      <xs:annotation>
        <xs:documentation>Active indicates whether an alternative is active or not in the calculations. By default, if the tag is not present, an alternative is considered as active (true).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributesIDRequired"/>
</xs:complexType>
Complex Type alternativesSets
Annotations
Definition of sets of alternatives.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSets_description XMCDA-4_0_0_xsd.tmp#alternativesSets_alternativesSet
Used by
Model
Children alternativesSet, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesSets">
  <xs:annotation>
    <xs:documentation>Definition of sets of alternatives.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="alternativesSet" type="alternativesSet" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativesSet
Annotations
Definition of a set of alternatives. Each element can be valued (to represent valued or ordered sets).
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#alternativesSet_description XMCDA-4_0_0_xsd.tmp#alternativesSet_element
Used by
Model
Children description, element
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="alternativesSet">
  <xs:annotation>
    <xs:documentation>Definition of a set of alternatives. Each element can be valued (to represent valued or ordered sets).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="element" minOccurs="0" maxOccurs="unbounded">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="alternativeID" type="xs:string"/>
          <xs:element name="values" minOccurs="0" maxOccurs="1" type="values"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributesIDRequired"/>
</xs:complexType>
Complex Type values
Annotations
Sequence of values.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#values_value
Used by
Model
Children value
Source
<xs:complexType name="values">
  <xs:annotation>
    <xs:documentation>Sequence of values.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="value" type="value" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
Complex Type value
Annotations
General value type.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel
Used by
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="value">
  <xs:annotation>
    <xs:documentation>General value type.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice>
      <xs:element name="integer" type="xs:int"/>
      <xs:element name="real" type="xs:double"/>
      <xs:element name="interval" type="interval"/>
      <xs:element name="rational" type="rational"/>
      <xs:element name="label" type="xs:string"/>
      <xs:element name="boolean" type="xs:boolean"/>
      <xs:element name="NA" type="NA"/>
      <xs:element name="fuzzyNumber" type="membershipFunction"/>
      <xs:element name="valuedLabel" type="valuedLabel"/>
    </xs:choice>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type interval
Annotations
An interval consists in a lower bound and an upper bound, both of which are values. Neither the lower bound not the upper bound are mandatory, which allows to define unbounded intervals.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#interval_lowerBound XMCDA-4_0_0_xsd.tmp#interval_upperBound
Used by
Element value/interval
Model
Children lowerBound, upperBound
Source
<xs:complexType name="interval">
  <xs:annotation>
    <xs:documentation>An interval consists in a lower bound and an upper bound, both of which are values. Neither the lower bound not the upper bound are mandatory, which allows to define unbounded intervals.</xs:documentation>
  </xs:annotation>
  <!-- At least one among (lowerBound, upperBound), or both -->
  <xs:choice>
    <xs:sequence>
      <xs:element name="lowerBound" type="intervalBound"/>
      <xs:element name="upperBound" type="intervalBound" minOccurs="0"/>
    </xs:sequence>
    <xs:element name="upperBound" type="intervalBound"/>
  </xs:choice>
</xs:complexType>
Complex Type intervalBound
Annotations
Bound of an interval.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#intervalBound_open
Type extension of value
Type hierarchy
Used by
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Attributes
QName Type Default Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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.
open xs:boolean false optional
If false (the default), the value is included within the interval, otherwise it is not.
Source
<xs:complexType name="intervalBound">
  <xs:annotation>
    <xs:documentation>Bound of an interval.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="value">
      <xs:attribute name="open" type="xs:boolean" default="false">
        <xs:annotation>
          <xs:documentation>If false (the default), the value is included within the interval, otherwise it is not.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type rational
Annotations
Rational number described by the numerator and the denominator, which are both integers.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#rational_numerator XMCDA-4_0_0_xsd.tmp#rational_denominator
Used by
Model
Children denominator, numerator
Source
<xs:complexType name="rational">
  <xs:annotation>
    <xs:documentation>Rational number described by the numerator and the denominator, which are both integers.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="numerator" type="xs:int"/>
    <xs:element name="denominator" type="xs:int"/>
  </xs:sequence>
</xs:complexType>
Complex Type NA
Diagram
Diagram
Used by
Source
<xs:complexType name="NA">
  <xs:complexContent>
    <xs:restriction base="xs:anyType"/>
  </xs:complexContent>
</xs:complexType>
Complex Type membershipFunction
Annotations
Restriction of the "function" type to functions compatible with fuzzy numbers.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#function_constant XMCDA-4_0_0_xsd.tmp#function_affine XMCDA-4_0_0_xsd.tmp#function_piecewiseLinear XMCDA-4_0_0_xsd.tmp#function_discrete XMCDA-4_0_0_xsd.tmp#function XMCDA-4_0_0_xsd.tmp#membershipFunction_piecewiseLinear
Type restriction of function
Type hierarchy
Used by
Model
Children piecewiseLinear
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="membershipFunction">
  <xs:annotation>
    <xs:documentation>Restriction of the "function" type to functions compatible with fuzzy numbers.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:restriction base="function">
      <xs:choice>
        <xs:element name="piecewiseLinear" type="piecewiseLinear"/>
      </xs:choice>
    </xs:restriction>
  </xs:complexContent>
</xs:complexType>
Complex Type function
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-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#function_constant XMCDA-4_0_0_xsd.tmp#function_affine XMCDA-4_0_0_xsd.tmp#function_piecewiseLinear XMCDA-4_0_0_xsd.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 and reference the underlying piece of data.
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="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="numericValue"/>
          <xs:element name="intercept" type="numericValue"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="piecewiseLinear" type="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="point" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:choice>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type numericValue
Annotations
Restriction of the "value" type to simple values of type: integer, real, rational and NA.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#value_integer XMCDA-4_0_0_xsd.tmp#value_real XMCDA-4_0_0_xsd.tmp#value_interval XMCDA-4_0_0_xsd.tmp#value_rational XMCDA-4_0_0_xsd.tmp#value_label XMCDA-4_0_0_xsd.tmp#value_boolean XMCDA-4_0_0_xsd.tmp#value_NA XMCDA-4_0_0_xsd.tmp#value_fuzzyNumber XMCDA-4_0_0_xsd.tmp#value_valuedLabel XMCDA-4_0_0_xsd.tmp#value XMCDA-4_0_0_xsd.tmp#numericValue_integer XMCDA-4_0_0_xsd.tmp#numericValue_real XMCDA-4_0_0_xsd.tmp#numericValue_rational XMCDA-4_0_0_xsd.tmp#numericValue_NA
Type restriction of value
Type hierarchy
Used by
Model
Children NA, integer, rational, real
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="numericValue">
  <xs:annotation>
    <xs:documentation>Restriction of the "value" type to simple values of type: integer, real, rational and NA.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:restriction base="value">
      <xs:sequence>
        <xs:choice>
          <xs:element name="integer" type="xs:int"/>
          <xs:element name="real" type="xs:double"/>
          <xs:element name="rational" type="rational"/>
          <xs:element name="NA" type="NA"/>
        </xs:choice>
      </xs:sequence>
    </xs:restriction>
  </xs:complexContent>
</xs:complexType>
Complex Type valuedLabel
Annotations
Label to which is associated a value. Can be used to represent ranks of ordinal labels, or fuzzy labels for example.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#valuedLabel_label XMCDA-4_0_0_xsd.tmp#valuedLabel_value
Used by
Model
Children label, value
Source
<xs:complexType name="valuedLabel">
  <xs:annotation>
    <xs:documentation>Label to which is associated a value. Can be used to represent ranks of ordinal labels, or fuzzy labels for example.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="label" type="xs:string"/>
    <xs:element name="value" type="value"/>
  </xs:sequence>
</xs:complexType>
Complex Type piecewiseLinear
Annotations
Piecewise linear function defined by a sequence of segments.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#piecewiseLinear_segment
Used by
Model
Children segment
Source
<xs:complexType name="piecewiseLinear">
  <xs:annotation>
    <xs:documentation>Piecewise linear function defined by a sequence of segments.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="segment" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Segment, defined by two points: one for the head, one for the tail. An attribute ("open") in the head and the tail allows to specify if the point is included in the segment or not.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="head" type="nillableEndPoint">
            <xs:annotation>
              <xs:documentation>Head point of a segment. All heads except the first one can be nil (no content): in that case, it is equal to the previous segment's tail.</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="tail" type="endPoint">
            <xs:annotation>
              <xs:documentation>Tail point of a segment..</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type nillableEndPoint
Annotations
An end point for segments which may have no coordinates. The meaning of an end point with no coordinates is defined by its parent.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#nillableEndPoint_open XMCDA-4_0_0_xsd.tmp#nillableEndPoint_abscissa XMCDA-4_0_0_xsd.tmp#nillableEndPoint_ordinate
Used by
Model
Children abscissa, ordinate
Attributes
QName Type Default Use Annotation
open xs:boolean false optional
If false (the default), the end point is included in the segment, otherwise it is not part of the segment.
Source
<xs:complexType name="nillableEndPoint">
  <xs:annotation>
    <xs:documentation>An end point for segments which may have no coordinates. The meaning of an end point with no coordinates is defined by its parent.</xs:documentation>
  </xs:annotation>
  <xs:sequence minOccurs="0">
    <xs:element name="abscissa" type="value">
      <xs:annotation>
        <xs:documentation>The abscissa of a point.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="ordinate" type="value">
      <xs:annotation>
        <xs:documentation>The ordinate of a point.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="open" type="xs:boolean" default="false">
    <xs:annotation>
      <xs:documentation>If false (the default), the end point is included in the segment, otherwise it is not part of the segment.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
Complex Type endPoint
Annotations
An end point for segments.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#point_abscissa XMCDA-4_0_0_xsd.tmp#point_ordinate XMCDA-4_0_0_xsd.tmp#point XMCDA-4_0_0_xsd.tmp#endPoint_open
Type extension of point
Type hierarchy
Used by
Model
Children abscissa, ordinate
Attributes
QName Type Default Use Annotation
open xs:boolean false optional
If false (the default), the end point is included in the segment, otherwise it is not part of the segment.
Source
<xs:complexType name="endPoint">
  <xs:annotation>
    <xs:documentation>An end point for segments.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="point">
      <xs:attribute name="open" type="xs:boolean" default="false">
        <xs:annotation>
          <xs:documentation>If false (the default), the end point is included in the segment, otherwise it is not part of the segment.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type point
Annotations
Point defined by an abscissa and an ordinate.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#point_abscissa XMCDA-4_0_0_xsd.tmp#point_ordinate
Used by
Complex Type endPoint
Element function/discrete/point
Model
Children abscissa, ordinate
Source
<xs:complexType name="point">
  <xs:annotation>
    <xs:documentation>Point defined by an abscissa and an ordinate.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="abscissa" type="value">
      <xs:annotation>
        <xs:documentation>The abscissa of a point.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="ordinate" type="value">
      <xs:annotation>
        <xs:documentation>The ordinate of a point.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type criteria
Annotations
Definition of criteria.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteria_description XMCDA-4_0_0_xsd.tmp#criteria_criterion
Used by
Element xmcda/criteria
Model
Children criterion, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteria">
  <xs:annotation>
    <xs:documentation>Definition of criteria.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" minOccurs="0" type="description"/>
    <xs:element name="criterion" minOccurs="1" maxOccurs="unbounded" type="criterion"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criterion
Annotations
Definition of a criterion. The id attribute is mandatory.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#criterion_description XMCDA-4_0_0_xsd.tmp#criterion_active
Used by
Model
Children active, description
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="criterion">
  <xs:annotation>
    <xs:documentation>Definition of a criterion. The id attribute is mandatory.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="active" type="xs:boolean" minOccurs="0" default="true">
      <xs:annotation>
        <xs:documentation>Indicates whether a criterion is active or not in the calculations. By default, if the tag is not present, the criterion is considered to be active (true).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributesIDRequired"/>
</xs:complexType>
Complex Type criteriaSets
Annotations
Definition of criteria sets.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSets_description XMCDA-4_0_0_xsd.tmp#criteriaSets_criteriaSet
Used by
Model
Children criteriaSet, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSets">
  <xs:annotation>
    <xs:documentation>Definition of criteria sets.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="criteriaSet" type="criteriaSet" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaSet
Annotations
A set of criteria, where the elements can be valued. An empty set of criteria can also be represented when no element is present.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#criteriaSet_description XMCDA-4_0_0_xsd.tmp#criteriaSet_element
Used by
Model
Children description, element
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="criteriaSet">
  <xs:annotation>
    <xs:documentation>A set of criteria, where the elements can be valued. An empty set of criteria can also be represented when no element is present.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="element" minOccurs="0" maxOccurs="unbounded">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="criterionID" type="xs:string"/>
          <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributesIDRequired"/>
</xs:complexType>
Complex Type performanceTable
Annotations
A crosstable alternatives x criteria showing the performances of the alternatives on the criteria.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#performanceTable_description XMCDA-4_0_0_xsd.tmp#performanceTable_alternativePerformances
Used by
Model
Children alternativePerformances, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="performanceTable">
  <xs:annotation>
    <xs:documentation>A crosstable alternatives x criteria showing the performances of the alternatives on the criteria.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" minOccurs="0" type="description"/>
    <xs:element name="alternativePerformances" minOccurs="0" maxOccurs="unbounded" type="alternativeOnCriteriaPerformances"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativeOnCriteriaPerformances
Annotations
The performances of an alternative on the criteria. Corresponds to a "row" in a performancetable.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativeOnCriteriaPerformances_alternativeID XMCDA-4_0_0_xsd.tmp#alternativeOnCriteriaPerformances_performance
Used by
Model
Children alternativeID, performance
Source
<xs:complexType name="alternativeOnCriteriaPerformances">
  <xs:annotation>
    <xs:documentation>The performances of an alternative on the criteria. Corresponds to a "row" in a performancetable.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="alternativeID" minOccurs="1" maxOccurs="1" type="xs:string"/>
    <xs:element name="performance" minOccurs="1" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Evaluation of an alternative on a criterion. If the evaluation is not available, put NA.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="description" minOccurs="0" type="description"/>
          <xs:element name="criterionID" minOccurs="1" maxOccurs="1" type="xs:string"/>
          <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type categories
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categories_description XMCDA-4_0_0_xsd.tmp#categories_category
Used by
Model
Children category, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categories">
  <xs:sequence>
    <xs:annotation>
      <xs:documentation>Definition of the categories.</xs:documentation>
    </xs:annotation>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="category" type="category" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type category
Annotations
Definition of a category. The id attribute is mandatory.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#category_description XMCDA-4_0_0_xsd.tmp#category_active
Used by
Model
Children active, description
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="category">
  <xs:annotation>
    <xs:documentation>Definition of a category. The id attribute is mandatory.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="active" type="xs:boolean" minOccurs="0" default="true">
      <xs:annotation>
        <xs:documentation>Indicates whether a category is active or not in the calculations. By default, if the tag is not present, the category is considered to be active (true).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributesIDRequired"/>
</xs:complexType>
Complex Type categoriesSets
Annotations
A sequence of categories sets.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSets_description XMCDA-4_0_0_xsd.tmp#categoriesSets_categoriesSet
Used by
Model
Children categoriesSet, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesSets">
  <xs:annotation>
    <xs:documentation>A sequence of categories sets.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="categoriesSet" type="categoriesSet" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoriesSet
Annotations
A set of categories, where each element can possibly be valued. An empty set of categories is obtained when no element is present.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#categoriesSet_description XMCDA-4_0_0_xsd.tmp#categoriesSet_element
Used by
Model
Children description, element
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="categoriesSet">
  <xs:annotation>
    <xs:documentation>A set of categories, where each element can possibly be valued. An empty set of categories is obtained when no element is present.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="element" minOccurs="0" maxOccurs="unbounded">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="categoryID" type="xs:string"/>
          <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributesIDRequired"/>
</xs:complexType>
Complex Type alternativesAssignments
Annotations
A sequence of assignments of alternatives to categories.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesAssignments_description XMCDA-4_0_0_xsd.tmp#alternativesAssignments_alternativeAssignment
Used by
Model
Children alternativeAssignment, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesAssignments">
  <xs:annotation>
    <xs:documentation>A sequence of assignments of alternatives to categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="alternativeAssignment" type="alternativeAssignment" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativeAssignment
Annotations
An assignment of an alternative or a set of alternatives to a category, a set of categories or an interval of categories.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativeAssignment_description XMCDA-4_0_0_xsd.tmp#alternativeAssignment_alternativeID XMCDA-4_0_0_xsd.tmp#alternativeAssignment_categoryID XMCDA-4_0_0_xsd.tmp#alternativeAssignment_categoriesSetID XMCDA-4_0_0_xsd.tmp#alternativeAssignment_categoriesInterval XMCDA-4_0_0_xsd.tmp#alternativeAssignment_values
Used by
Model
Children alternativeID, categoriesInterval, categoriesSetID, categoryID, description, values
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativeAssignment">
  <xs:annotation>
    <xs:documentation>An assignment of an alternative or a set of alternatives to a category, a set of categories or an interval of categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="alternativeID" type="xs:string"/>
    <xs:choice>
      <xs:element name="categoryID" type="xs:string"/>
      <xs:element name="categoriesSetID" type="xs:string"/>
      <xs:element name="categoriesInterval" type="categoriesInterval"/>
    </xs:choice>
    <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoriesInterval
Annotations
An interval of categories.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesInterval_description XMCDA-4_0_0_xsd.tmp#categoriesInterval_lowerBound XMCDA-4_0_0_xsd.tmp#categoriesInterval_upperBound
Used by
Model
Children description, lowerBound, upperBound
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesInterval">
  <xs:annotation>
    <xs:documentation>An interval of categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <!-- At least one among (lowerBound, upperBound), or both -->
    <xs:choice>
      <xs:sequence>
        <xs:element name="lowerBound" type="categoriesIntervalBound"/>
        <xs:element name="upperBound" type="categoriesIntervalBound" minOccurs="0"/>
      </xs:sequence>
      <xs:element name="upperBound" type="categoriesIntervalBound"/>
    </xs:choice>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoriesIntervalBound
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoriesIntervalBound_categoryID
Used by
Model
Children categoryID
Source
<xs:complexType name="categoriesIntervalBound">
  <xs:sequence>
    <xs:element name="categoryID" type="xs:string"/>
  </xs:sequence>
</xs:complexType>
Complex Type alternativesCriteriaValues
Annotations
A crosstable alternatives x criteria.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesCriteriaValues_description XMCDA-4_0_0_xsd.tmp#alternativesCriteriaValues_alternativeCriteriaValues
Used by
Model
Children alternativeCriteriaValues, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesCriteriaValues">
  <xs:annotation>
    <xs:documentation>A crosstable alternatives x criteria.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="alternativeCriteriaValues" type="alternativeCriteriaValues" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativeCriteriaValues
Annotations
A row in a crosstable alternatives x criteria.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#alternativeCriteriaValues_alternativeID XMCDA-4_0_0_xsd.tmp#alternativeCriteriaValues_criteriaValues
Used by
Model
Children alternativeID, criteriaValues
Source
<xs:complexType name="alternativeCriteriaValues">
  <xs:annotation>
    <xs:documentation>A row in a crosstable alternatives x criteria.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="alternativeID" minOccurs="1" type="xs:string"/>
    <xs:element name="criteriaValues" type="criteriaValues" minOccurs="1" maxOccurs="1"/>
  </xs:sequence>
</xs:complexType>
Complex Type criteriaValues
Annotations
A sequence of criteria-related values.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaValues_description XMCDA-4_0_0_xsd.tmp#criteriaValues_criterionValues
Used by
Model
Children criterionValues, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaValues">
  <xs:annotation>
    <xs:documentation>A sequence of criteria-related values.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="criterionValues" type="criterionValues" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criterionValues
Annotations
One or more values related to a criterion.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criterionValues_description XMCDA-4_0_0_xsd.tmp#criterionValues_criterionID XMCDA-4_0_0_xsd.tmp#criterionValues_values
Used by
Model
Children criterionID, description, values
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criterionValues">
  <xs:annotation>
    <xs:documentation>One or more values related to a criterion.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="criterionID" type="xs:string"/>
    <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativesLinearConstraints
Annotations
Linear constraints on the alternatives.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_description XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#alternativesLinearConstraints_constraints
Used by
Model
Children constraints, description, variables
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesLinearConstraints">
  <xs:annotation>
    <xs:documentation>Linear constraints on the alternatives.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="variables" type="variables" minOccurs="0"/>
    <xs:element name="constraints">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
            <xs:complexType>
              <xs:annotation>
                <xs:documentation>A linear constraint related to alternatives. It is composed of a sum of elements, each element being composed of an alternative or a variable and a coefficient. The rhs allows to specify the value of the right hand side. The values linked to each constraint can represent a credibility of this constraint in the eyes of a decision maker, for example.</xs:documentation>
              </xs:annotation>
              <xs:sequence>
                <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
                <xs:element name="elements" minOccurs="0" maxOccurs="1">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                        <xs:complexType>
                          <xs:sequence>
                            <xs:choice>
                              <xs:element name="alternativeID" type="xs:string"/>
                              <xs:element name="variableID" type="xs:string"/>
                            </xs:choice>
                            <xs:element name="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
                          </xs:sequence>
                          <xs:attributeGroup ref="defaultAttributes"/>
                        </xs:complexType>
                      </xs:element>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
                <xs:element name="operator" minOccurs="1">
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="geq"/>
                      <xs:enumeration value="eq"/>
                      <xs:enumeration value="leq"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
                <xs:element name="rhs" type="numericValue"/>
                <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
              </xs:sequence>
              <xs:attributeGroup ref="defaultAttributes"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type variables
Annotations
A compound tag to store the definitions of the variables of a linear constraints system.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#variables_variable
Used by
Model
Children variable
Source
<xs:complexType name="variables">
  <xs:annotation>
    <xs:documentation>A compound tag to store the definitions of the variables of a linear constraints system.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="variable" type="variable" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
Complex Type variable
Annotations
A variable (for linear constraints for example). The id is required to identify the variable.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired XMCDA-4_0_0_xsd.tmp#variable_description
Used by
Model
Children description
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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="variable">
  <xs:annotation>
    <xs:documentation>A variable (for linear constraints for example). The id is required to identify the variable.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributesIDRequired"/>
</xs:complexType>
Complex Type alternativesMatrix
Annotations
Matrix of values related to alternatives.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesMatrix_description XMCDA-4_0_0_xsd.tmp#alternativesMatrix_row
Used by
Model
Children description, row
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesMatrix">
  <xs:annotation>
    <xs:documentation>Matrix of values related to alternatives.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="row" minOccurs="1" maxOccurs="unbounded">
      <xs:complexType>
        <xs:annotation>
          <xs:documentation>Row of a matrix.</xs:documentation>
        </xs:annotation>
        <xs:sequence>
          <xs:element name="alternativeID" type="xs:string"/>
          <xs:element name="column" minOccurs="1" maxOccurs="unbounded">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="alternativeID" type="xs:string"/>
                <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativesValues
Annotations
Values related to alternatives. Can for example be used to store overall values of alternatives, or their rank in a ranking.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesValues_description XMCDA-4_0_0_xsd.tmp#alternativesValues_alternativeValues
Used by
Model
Children alternativeValues, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesValues">
  <xs:annotation>
    <xs:documentation>Values related to alternatives. Can for example be used to store overall values of alternatives, or their rank in a ranking.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="alternativeValues" type="alternativeValues" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativeValues
Annotations
One or more values related to an alternative. Can for example be used to store the overall value of an alternative, or its rank.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativeValues_description XMCDA-4_0_0_xsd.tmp#alternativeValues_alternativeID XMCDA-4_0_0_xsd.tmp#alternativeValues_values
Used by
Model
Children alternativeID, description, values
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativeValues">
  <xs:annotation>
    <xs:documentation>One or more values related to an alternative. Can for example be used to store the overall value of an alternative, or its rank.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="alternativeID" type="xs:string"/>
    <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativesSetsLinearConstraints
Annotations
Linear constraints on sets of alternatives.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_description XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#alternativesSetsLinearConstraints_constraints
Used by
Model
Children constraints, description, variables
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesSetsLinearConstraints">
  <xs:annotation>
    <xs:documentation>Linear constraints on sets of alternatives.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="variables" type="variables" minOccurs="0"/>
    <xs:element name="constraints">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
            <xs:complexType>
              <xs:annotation>
                <xs:documentation>A linear constraint related to sets of alternatives. It is composed of a sum of elements, each element being composed of a set of alternatives or a variable and a coefficient. The rhs allows to specify the value of the right hand side. The values linked to each constraint can represent a credibility of this constraint in the eyes of a decision maker, for example.</xs:documentation>
              </xs:annotation>
              <xs:sequence>
                <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
                <xs:element name="elements" minOccurs="0" maxOccurs="1">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                        <xs:complexType>
                          <xs:sequence>
                            <xs:choice>
                              <xs:element name="alternativesSetID" type="xs:string"/>
                              <xs:element name="variableID" type="xs:string"/>
                            </xs:choice>
                            <xs:element name="coefficient" type="numericValue" minOccurs="1" maxOccurs="1"/>
                          </xs:sequence>
                          <xs:attributeGroup ref="defaultAttributes"/>
                        </xs:complexType>
                      </xs:element>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
                <xs:element name="operator" minOccurs="1">
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="geq"/>
                      <xs:enumeration value="eq"/>
                      <xs:enumeration value="leq"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
                <xs:element name="rhs" type="numericValue"/>
                <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
              </xs:sequence>
              <xs:attributeGroup ref="defaultAttributes"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativesSetsMatrix
Annotations
Matrix of values related to sets of alternatives.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix_description XMCDA-4_0_0_xsd.tmp#alternativesSetsMatrix_row
Used by
Model
Children description, row
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesSetsMatrix">
  <xs:annotation>
    <xs:documentation>Matrix of values related to sets of alternatives.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="row" minOccurs="1" maxOccurs="unbounded">
      <xs:complexType>
        <xs:annotation>
          <xs:documentation>Row of a matrix.</xs:documentation>
        </xs:annotation>
        <xs:sequence>
          <xs:choice>
            <xs:element name="alternativeID" type="xs:string"/>
            <xs:element name="alternativesSetID" type="xs:string"/>
          </xs:choice>
          <xs:element name="column" minOccurs="1" maxOccurs="unbounded">
            <xs:complexType>
              <xs:sequence>
                <xs:choice>
                  <xs:element name="alternativeID" type="xs:string"/>
                  <xs:element name="alternativesSetID" type="xs:string"/>
                </xs:choice>
                <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativesSetsValues
Annotations
Values related to sets of alternatives. Can for example be used to store overall values of sets of alternatives, or their rank in a ranking.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSetsValues_description XMCDA-4_0_0_xsd.tmp#alternativesSetsValues_alternativesSetValues
Used by
Model
Children alternativesSetValues, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesSetsValues">
  <xs:annotation>
    <xs:documentation>Values related to sets of alternatives. Can for example be used to store overall values of sets of alternatives, or their rank in a ranking.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="alternativesSetValues" type="alternativesSetValues" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type alternativesSetValues
Annotations
One or more values related to a set of alternatives. Can for example be used to store the overall value of a set of alternatives alternative, or its rank.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#alternativesSetValues_description XMCDA-4_0_0_xsd.tmp#alternativesSetValues_alternativesSetID XMCDA-4_0_0_xsd.tmp#alternativesSetValues_values
Used by
Model
Children alternativesSetID, description, values
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="alternativesSetValues">
  <xs:annotation>
    <xs:documentation>One or more values related to a set of alternatives. Can for example be used to store the overall value of a set of alternatives alternative, or its rank.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="alternativesSetID" type="xs:string"/>
    <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaFunctions
Annotations
Functions related to criteria. For example value functions.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaFunctions_description XMCDA-4_0_0_xsd.tmp#criteriaFunctions_criterionFunctions
Used by
Model
Children criterionFunctions, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaFunctions">
  <xs:annotation>
    <xs:documentation>Functions related to criteria. For example value functions.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
    <xs:element name="criterionFunctions" type="criterionFunctions" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criterionFunctions
Annotations
Functions related to a criterion, to store for example a value function.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criterionFunctions_description XMCDA-4_0_0_xsd.tmp#criterionFunctions_criterionID XMCDA-4_0_0_xsd.tmp#criterionFunctions_functions
Used by
Model
Children criterionID, description, functions
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criterionFunctions">
  <xs:annotation>
    <xs:documentation>Functions related to a criterion, to store for example a value function.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
    <xs:element name="criterionID" type="xs:string"/>
    <xs:element name="functions" minOccurs="1" maxOccurs="1">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="function" type="function" minOccurs="1" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaHierarchy
Annotations
A hierarchy of criteria.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaHierarchy_description XMCDA-4_0_0_xsd.tmp#criteriaHierarchy_nodes
Used by
Model
Children description, nodes
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaHierarchy">
  <xs:annotation>
    <xs:documentation>A hierarchy of criteria.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="nodes" type="criteriaHierarchyNodes" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaHierarchyNodes
Annotations
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaHierarchyNodes_node
Used by
Model
Children node
Source
<xs:complexType name="criteriaHierarchyNodes">
  <xs:annotation>
    <xs:documentation/>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="node" type="criterionHierarchyNode" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
Complex Type criterionHierarchyNode
Annotations
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criterionHierarchyNode_criterionID XMCDA-4_0_0_xsd.tmp#criterionHierarchyNode_nodes
Used by
Model
Children criterionID, nodes
Source
<xs:complexType name="criterionHierarchyNode">
  <xs:annotation>
    <xs:documentation/>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="criterionID" type="xs:string" minOccurs="1" maxOccurs="1"/>
    <xs:element name="nodes" type="criteriaHierarchyNodes" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
Complex Type criteriaLinearConstraints
Annotations
Represents a set of linear constraints on the criteria.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_description XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#criteriaLinearConstraints_constraints
Used by
Model
Children constraints, description, variables
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaLinearConstraints">
  <xs:annotation>
    <xs:documentation>Represents a set of linear constraints on the criteria.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="variables" type="variables" minOccurs="0"/>
    <xs:element name="constraints">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
            <xs:complexType>
              <xs:annotation>
                <xs:documentation>A linear constraint related to criteria. It is constructed from a sum of elements, each element being composed of a reference to a criterion or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
              </xs:annotation>
              <xs:sequence>
                <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
                <xs:element name="elements" minOccurs="0" maxOccurs="1">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                        <xs:complexType>
                          <xs:sequence>
                            <xs:choice>
                              <xs:element name="criterionID" type="xs:string"/>
                              <xs:element name="variableID" type="xs:string"/>
                            </xs:choice>
                            <xs:element name="coefficient" type="numericValue"/>
                          </xs:sequence>
                          <xs:attributeGroup ref="defaultAttributes"/>
                        </xs:complexType>
                      </xs:element>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
                <xs:element name="operator" minOccurs="1">
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="geq"/>
                      <xs:enumeration value="eq"/>
                      <xs:enumeration value="leq"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
                <xs:element name="rhs" type="numericValue"/>
                <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
              </xs:sequence>
              <xs:attributeGroup ref="defaultAttributes"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaMatrix
Annotations
Generic type for a matrix on criteria.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaMatrix_description XMCDA-4_0_0_xsd.tmp#criteriaMatrix_row
Used by
Model
Children description, row
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaMatrix">
  <xs:annotation>
    <xs:documentation>Generic type for a matrix on criteria.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="row" minOccurs="1" maxOccurs="unbounded">
      <xs:complexType>
        <xs:annotation>
          <xs:documentation>A row of the matrix.</xs:documentation>
        </xs:annotation>
        <xs:sequence>
          <xs:choice>
            <xs:element name="criterionID" type="xs:string"/>
          </xs:choice>
          <xs:element name="column" maxOccurs="unbounded">
            <xs:complexType>
              <xs:annotation>
                <xs:documentation>A column of the matrix.</xs:documentation>
              </xs:annotation>
              <xs:sequence>
                <xs:element name="criterionID" type="xs:string"/>
                <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaScales
Annotations
Scales related to criteria (typically evaluation scales).
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaScales_description XMCDA-4_0_0_xsd.tmp#criteriaScales_criterionScales
Used by
Model
Children criterionScales, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaScales">
  <xs:annotation>
    <xs:documentation>Scales related to criteria (typically evaluation scales).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="criterionScales" type="criterionScales" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criterionScales
Annotations
Evaluation scales related to a criterion.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criterionScales_description XMCDA-4_0_0_xsd.tmp#criterionScales_criterionID XMCDA-4_0_0_xsd.tmp#criterionScales_scales
Used by
Model
Children criterionID, description, scales
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criterionScales">
  <xs:annotation>
    <xs:documentation>Evaluation scales related to a criterion.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
    <xs:element name="criterionID" type="xs:string"/>
    <xs:element name="scales" minOccurs="1" maxOccurs="1">
      <xs:complexType>
        <xs:annotation>
          <xs:documentation>One or more scales related to a criterion.</xs:documentation>
        </xs:annotation>
        <xs:sequence>
          <xs:element name="description" type="description" minOccurs="0"/>
          <xs:sequence>
            <xs:choice minOccurs="1" maxOccurs="unbounded">
              <xs:element name="scale" type="scale"/>
              <xs:element name="scaleID" type="xs:string">
                <xs:annotation>
                  <xs:documentation>A reference to a scale defined anywhere in the parent criteriaScales.</xs:documentation>
                </xs:annotation>
              </xs:element>
            </xs:choice>
          </xs:sequence>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type scale
Annotations
Evaluation scale. Choice between 3 types of scales: nominal, qualitative and quantitative.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#scale_nominal XMCDA-4_0_0_xsd.tmp#scale_qualitative XMCDA-4_0_0_xsd.tmp#scale_quantitative
Used by
Model
Children nominal, qualitative, quantitative
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="scale">
  <xs:annotation>
    <xs:documentation>Evaluation scale. Choice between 3 types of scales: nominal, qualitative and quantitative.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:choice>
      <xs:element name="nominal" type="nominal"/>
      <xs:element name="qualitative" type="qualitative"/>
      <xs:element name="quantitative" type="quantitative"/>
    </xs:choice>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type nominal
Annotations
Type of nominal scales, consiting in unordered labels.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#nominal_labels
Used by
Element scale/nominal
Model
Children labels
Source
<xs:complexType name="nominal">
  <xs:annotation>
    <xs:documentation>Type of nominal scales, consiting in unordered labels.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="labels">
      <xs:complexType>
        <xs:annotation>
          <xs:documentation>The set of labels used by a nominal scale.</xs:documentation>
        </xs:annotation>
        <xs:sequence>
          <xs:element name="label" type="xs:string" minOccurs="1" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type qualitative
Annotations
Type of qualitative ordered levels. It consists in a preference direction and either classical ranked labels or fuzzy labels (via valued labels in both cases).
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#qualitative_preferenceDirection XMCDA-4_0_0_xsd.tmp#qualitative_valuedLabels
Used by
Model
Children preferenceDirection, valuedLabels
Source
<xs:complexType name="qualitative">
  <xs:annotation>
    <xs:documentation>Type of qualitative ordered levels. It consists in a preference direction and either classical ranked labels or fuzzy labels (via valued labels in both cases).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="preferenceDirection" type="preferenceDirection" minOccurs="0"/>
    <xs:choice>
      <xs:element name="valuedLabels">
        <xs:complexType>
          <xs:annotation>
            <xs:documentation>Sequence of valued labels. Could either be labels to which are associated ranks, or fuzzy labels.</xs:documentation>
          </xs:annotation>
          <xs:sequence>
            <xs:element name="valuedLabel" type="valuedLabel" minOccurs="1" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:choice>
  </xs:sequence>
</xs:complexType>
Simple Type preferenceDirection
Annotations
Preferential direction on a given quantitative or qualitative scale: either "max" for a scale where the higher values are preferred, or "min" for a scale where the lower values are preferred.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration min
enumeration max
Used by
Source
<xs:simpleType name="preferenceDirection">
  <xs:annotation>
    <xs:documentation>Preferential direction on a given quantitative or qualitative scale: either "max" for a scale where the higher values are preferred, or "min" for a scale where the lower values are preferred.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="min"/>
    <xs:enumeration value="max"/>
  </xs:restriction>
</xs:simpleType>
Complex Type quantitative
Annotations
Type of quantitative scales. It consists in a preference direction (min or max), and a minimal and maximal quantitative evaluations (both of which are optional).
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#quantitative_preferenceDirection XMCDA-4_0_0_xsd.tmp#quantitative_minimum XMCDA-4_0_0_xsd.tmp#quantitative_maximum
Used by
Model
Children maximum, minimum, preferenceDirection
Source
<xs:complexType name="quantitative">
  <xs:annotation>
    <xs:documentation>Type of quantitative scales. It consists in a preference direction (min or max), and a minimal and maximal quantitative evaluations (both of which are optional).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="preferenceDirection" type="preferenceDirection" minOccurs="0"/>
    <!--  both min & max can be omitted -->
    <xs:element name="minimum" type="numericValue" minOccurs="0"/>
    <xs:element name="maximum" type="numericValue" minOccurs="0"/>
  </xs:sequence>
</xs:complexType>
Complex Type criteriaThresholds
Annotations
Thresholds related to criteria (typically discrimination thresholds).
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaThresholds_description XMCDA-4_0_0_xsd.tmp#criteriaThresholds_criterionThresholds
Used by
Model
Children criterionThresholds, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaThresholds">
  <xs:annotation>
    <xs:documentation>Thresholds related to criteria (typically discrimination thresholds).</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="criterionThresholds" type="criterionThresholds" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criterionThresholds
Annotations
Thresholds related to a criterion, to represent for example discrimination thresholds in outranking methods. The type of the threshold is specified in the mcdaConcept attribute of each threshold, and documented in each algorithm.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criterionThresholds_description XMCDA-4_0_0_xsd.tmp#criterionThresholds_criterionID XMCDA-4_0_0_xsd.tmp#criterionThresholds_thresholds
Used by
Model
Children criterionID, description, thresholds
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criterionThresholds">
  <xs:annotation>
    <xs:documentation>Thresholds related to a criterion, to represent for example discrimination thresholds in outranking methods. The type of the threshold is specified in the mcdaConcept attribute of each threshold, and documented in each algorithm.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
    <xs:element name="criterionID" type="xs:string"/>
    <xs:element name="thresholds" minOccurs="1" maxOccurs="1">
      <xs:complexType>
        <xs:annotation>
          <xs:documentation>One or more discrimination thresholds related to a criterion.</xs:documentation>
        </xs:annotation>
        <xs:sequence>
          <xs:element name="description" type="description" minOccurs="0"/>
          <xs:element name="threshold" type="threshold" minOccurs="1" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type threshold
Annotations
Discrimination threshold (used to represent preferences on criteria).
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#threshold_constant XMCDA-4_0_0_xsd.tmp#threshold_affine
Used by
Model
Children affine, constant
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="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="numericValue" minOccurs="1" maxOccurs="1"/>
          <xs:element name="intercept" type="numericValue" minOccurs="1" maxOccurs="1"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:choice>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaSetsHierarchy
Annotations
A hierarchy of criteria sets.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetsHierarchy_description XMCDA-4_0_0_xsd.tmp#criteriaSetsHierarchy_nodes
Used by
Model
Children description, nodes
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSetsHierarchy">
  <xs:annotation>
    <xs:documentation>A hierarchy of criteria sets.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="nodes" type="criteriaSetsHierarchyNodes" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaSetsHierarchyNodes
Annotations
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaSetsHierarchyNodes_node
Used by
Model
Children node
Source
<xs:complexType name="criteriaSetsHierarchyNodes">
  <xs:annotation>
    <xs:documentation/>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="node" type="criteriaSetHierarchyNode" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
Complex Type criteriaSetHierarchyNode
Annotations
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#criteriaSetHierarchyNode_criteriaSetID XMCDA-4_0_0_xsd.tmp#criteriaSetHierarchyNode_nodes
Used by
Model
Children criteriaSetID, nodes
Source
<xs:complexType name="criteriaSetHierarchyNode">
  <xs:annotation>
    <xs:documentation/>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="criteriaSetID" type="xs:string" minOccurs="1" maxOccurs="1"/>
    <xs:element name="nodes" type="criteriaSetsHierarchyNodes" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
Complex Type criteriaSetsLinearConstraints
Annotations
Represents a set of linear constraints on the criteria.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_description XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#criteriaSetsLinearConstraints_constraints
Used by
Model
Children constraints, description, variables
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSetsLinearConstraints">
  <xs:annotation>
    <xs:documentation>Represents a set of linear constraints on the criteria.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="variables" type="variables" minOccurs="0"/>
    <xs:element name="constraints">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
            <xs:complexType>
              <xs:annotation>
                <xs:documentation>A linear constraint related to criteria. It is constructed from a sum of elements, each element being composed of a reference to a set of criteria or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
              </xs:annotation>
              <xs:sequence>
                <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
                <xs:element name="elements" minOccurs="0" maxOccurs="1">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                        <xs:complexType>
                          <xs:sequence>
                            <xs:choice>
                              <xs:element name="criteriaSetID" type="xs:string"/>
                              <xs:element name="variableID" type="xs:string"/>
                            </xs:choice>
                            <xs:element name="coefficient" type="numericValue"/>
                          </xs:sequence>
                          <xs:attributeGroup ref="defaultAttributes"/>
                        </xs:complexType>
                      </xs:element>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
                <xs:element name="operator" minOccurs="1">
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="geq"/>
                      <xs:enumeration value="eq"/>
                      <xs:enumeration value="leq"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
                <xs:element name="rhs" type="numericValue"/>
                <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
              </xs:sequence>
              <xs:attributeGroup ref="defaultAttributes"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaSetsMatrix
Annotations
Generic type for a matrix on criteria sets.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetsMatrix_description XMCDA-4_0_0_xsd.tmp#criteriaSetsMatrix_row
Used by
Model
Children description, row
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSetsMatrix">
  <xs:annotation>
    <xs:documentation>Generic type for a matrix on criteria sets.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="row" minOccurs="1" maxOccurs="unbounded">
      <xs:complexType>
        <xs:annotation>
          <xs:documentation>A row of the matrix.</xs:documentation>
        </xs:annotation>
        <xs:sequence>
          <xs:element name="criteriaSetID" type="xs:string"/>
          <xs:element name="column" maxOccurs="unbounded">
            <xs:complexType>
              <xs:annotation>
                <xs:documentation>A column of the matrix.</xs:documentation>
              </xs:annotation>
              <xs:sequence>
                <xs:element name="criteriaSetID" type="xs:string"/>
                <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaSetsValues
Annotations
A sequence of criteria sets-related values.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetsValues_description XMCDA-4_0_0_xsd.tmp#criteriaSetsValues_criteriaSetValues
Used by
Model
Children criteriaSetValues, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSetsValues">
  <xs:annotation>
    <xs:documentation>A sequence of criteria sets-related values.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="criteriaSetValues" type="criteriaSetValues" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type criteriaSetValues
Annotations
One or more values related to a set of criteria.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#criteriaSetValues_description XMCDA-4_0_0_xsd.tmp#criteriaSetValues_criteriaSetID XMCDA-4_0_0_xsd.tmp#criteriaSetValues_values
Used by
Model
Children criteriaSetID, description, values
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="criteriaSetValues">
  <xs:annotation>
    <xs:documentation>One or more values related to a set of criteria.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="criteriaSetID" type="xs:string"/>
    <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoriesLinearConstraints
Annotations
Represents a set of linear constraints on the categories.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_description XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#categoriesLinearConstraints_constraints
Used by
Model
Children constraints, description, variables
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesLinearConstraints">
  <xs:annotation>
    <xs:documentation>Represents a set of linear constraints on the categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="variables" type="variables" minOccurs="0"/>
    <xs:element name="constraints">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
            <xs:complexType>
              <xs:annotation>
                <xs:documentation>A linear constraint related to categories. It is constructed from a sum of elements, each element being composed of a reference to a category or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
              </xs:annotation>
              <xs:sequence>
                <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
                <xs:element name="elements" minOccurs="0" maxOccurs="1">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                        <xs:complexType>
                          <xs:sequence>
                            <xs:choice>
                              <xs:element name="categoryID" type="xs:string"/>
                              <xs:element name="variableID" type="xs:string"/>
                            </xs:choice>
                            <xs:element name="coefficient" type="numericValue"/>
                          </xs:sequence>
                          <xs:attributeGroup ref="defaultAttributes"/>
                        </xs:complexType>
                      </xs:element>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
                <xs:element name="operator" minOccurs="1">
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="geq"/>
                      <xs:enumeration value="eq"/>
                      <xs:enumeration value="leq"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
                <xs:element name="rhs" type="numericValue"/>
                <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
              </xs:sequence>
              <xs:attributeGroup ref="defaultAttributes"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoriesMatrix
Annotations
A matrix of values related to categories.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesMatrix_description XMCDA-4_0_0_xsd.tmp#categoriesMatrix_row
Used by
Model
Children description, row
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesMatrix">
  <xs:annotation>
    <xs:documentation>A matrix of values related to categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="row" minOccurs="1" maxOccurs="unbounded">
      <xs:complexType>
        <xs:annotation>
          <xs:documentation>A row of a matrix.</xs:documentation>
        </xs:annotation>
        <xs:sequence>
          <xs:element name="categoryID" type="xs:string"/>
          <xs:element name="column" maxOccurs="unbounded">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="categoryID" type="xs:string"/>
                <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoriesProfiles
Annotations
A sequence of category profiles
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesProfiles_description XMCDA-4_0_0_xsd.tmp#categoriesProfiles_categoryProfile
Used by
Model
Children categoryProfile, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesProfiles">
  <xs:annotation>
    <xs:documentation>A sequence of category profiles</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="categoryProfile" minOccurs="0" maxOccurs="unbounded" type="categoryProfile"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoryProfile
Annotations
Description of a category by a bounding profile or a central profile.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoryProfile_description XMCDA-4_0_0_xsd.tmp#categoryProfile_categoryID XMCDA-4_0_0_xsd.tmp#categoryProfile_central XMCDA-4_0_0_xsd.tmp#categoryProfile_bounding
Used by
Model
Children bounding, categoryID, central, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoryProfile">
  <xs:annotation>
    <xs:documentation>Description of a category by a bounding profile or a central profile.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="categoryID" type="xs:string"/>
    <xs:choice>
      <xs:element name="central">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="alternativeID" type="xs:string"/>
            <xs:element name="values" type="values" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="bounding">
        <xs:complexType>
          <!-- At least one among (lowerBound, upperBound), or both -->
          <xs:choice>
            <xs:sequence>
              <xs:element name="lowerBound" type="categoryProfileBound"/>
              <xs:element name="upperBound" type="categoryProfileBound" minOccurs="0"/>
            </xs:sequence>
            <xs:element name="upperBound" type="categoryProfileBound"/>
          </xs:choice>
        </xs:complexType>
      </xs:element>
    </xs:choice>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoryProfileBound
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#categoryProfileBound_alternativeID XMCDA-4_0_0_xsd.tmp#categoryProfileBound_values
Used by
Model
Children alternativeID, values
Source
<xs:complexType name="categoryProfileBound">
  <xs:sequence>
    <xs:element name="alternativeID" type="xs:string"/>
    <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
  </xs:sequence>
</xs:complexType>
Complex Type categoriesValues
Annotations
A sequence of values related to categories.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesValues_description XMCDA-4_0_0_xsd.tmp#categoriesValues_categoryValues
Used by
Model
Children categoryValues, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesValues">
  <xs:annotation>
    <xs:documentation>A sequence of values related to categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="categoryValues" type="categoryValues" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoryValues
Annotations
A value or values related to a category.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoryValues_description XMCDA-4_0_0_xsd.tmp#categoryValues_categoryID XMCDA-4_0_0_xsd.tmp#categoryValues_values
Used by
Model
Children categoryID, description, values
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoryValues">
  <xs:annotation>
    <xs:documentation>A value or values related to a category.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="categoryID" type="xs:string"/>
    <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoriesSetsLinearConstraints
Annotations
Represents a set of linear constraints on sets of categories.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_description XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_variables XMCDA-4_0_0_xsd.tmp#categoriesSetsLinearConstraints_constraints
Used by
Model
Children constraints, description, variables
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesSetsLinearConstraints">
  <xs:annotation>
    <xs:documentation>Represents a set of linear constraints on sets of categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="variables" type="variables" minOccurs="0"/>
    <xs:element name="constraints">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="constraint" minOccurs="1" maxOccurs="unbounded">
            <xs:complexType>
              <xs:annotation>
                <xs:documentation>A linear constraint related to sets of categories. It is constructed from a sum of elements, each element being composed of a reference to a category set or a variable, and a multiplicative coefficient. The right hand side is specified separately, and the operator is either geq, leq or eq. Values can also be assigned to each constraint, to represent, e.g., a credibility of the constraint.</xs:documentation>
              </xs:annotation>
              <xs:sequence>
                <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
                <xs:element name="elements" minOccurs="0" maxOccurs="1">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
                        <xs:complexType>
                          <xs:sequence>
                            <xs:choice>
                              <xs:element name="categoriesSetID" type="xs:string"/>
                              <xs:element name="variableID" type="xs:string"/>
                            </xs:choice>
                            <xs:element name="coefficient" type="numericValue"/>
                          </xs:sequence>
                          <xs:attributeGroup ref="defaultAttributes"/>
                        </xs:complexType>
                      </xs:element>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
                <xs:element name="operator" minOccurs="1">
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="geq"/>
                      <xs:enumeration value="eq"/>
                      <xs:enumeration value="leq"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
                <xs:element name="rhs" type="numericValue"/>
                <xs:element name="values" type="values" minOccurs="0" maxOccurs="1"/>
              </xs:sequence>
              <xs:attributeGroup ref="defaultAttributes"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoriesSetsMatrix
Annotations
A matrix of values related to sets of categories.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSetsMatrix_description XMCDA-4_0_0_xsd.tmp#categoriesSetsMatrix_row
Used by
Model
Children description, row
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesSetsMatrix">
  <xs:annotation>
    <xs:documentation>A matrix of values related to sets of categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="row" minOccurs="1" maxOccurs="unbounded">
      <xs:complexType>
        <xs:annotation>
          <xs:documentation>A row of a matrix.</xs:documentation>
        </xs:annotation>
        <xs:sequence>
          <xs:element name="categoriesSetID" type="xs:string"/>
          <xs:element name="column" maxOccurs="unbounded">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="categoriesSetID" type="xs:string"/>
                <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoriesSetsValues
Annotations
A sequence of values related to sets of categories.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSetsValues_description XMCDA-4_0_0_xsd.tmp#categoriesSetsValues_categoriesSetValues
Used by
Model
Children categoriesSetValues, description
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesSetsValues">
  <xs:annotation>
    <xs:documentation>A sequence of values related to sets of categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="categoriesSetValues" type="categoriesSetValues" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type categoriesSetValues
Annotations
A value or values related to a set of categories.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#categoriesSetValues_description XMCDA-4_0_0_xsd.tmp#categoriesSetValues_categoriesSetID XMCDA-4_0_0_xsd.tmp#categoriesSetValues_values
Used by
Model
Children categoriesSetID, description, values
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="categoriesSetValues">
  <xs:annotation>
    <xs:documentation>A value or values related to a set of categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="categoriesSetID" type="xs:string"/>
    <xs:element name="values" type="values" minOccurs="1" maxOccurs="1"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type programParameters
Annotations
Input parameters for a program.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#programParameters_description XMCDA-4_0_0_xsd.tmp#programParameters_programParameter
Used by
Model
Children description, programParameter
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="programParameters">
  <xs:annotation>
    <xs:documentation>Input parameters for a program.</xs:documentation>
  </xs:annotation>
  <xs:sequence minOccurs="0" maxOccurs="unbounded">
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="programParameter" type="programParameter" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type programParameter
Annotations
A parameter for a program.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#programParameter_description XMCDA-4_0_0_xsd.tmp#programParameter_values
Used by
Model
Children description, values
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="programParameter">
  <xs:annotation>
    <xs:documentation>A parameter for a program.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0" maxOccurs="1"/>
    <xs:element name="values" type="values"/>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Complex Type programExecutionResult
Annotations
Output of programs.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#programExecutionResult_description XMCDA-4_0_0_xsd.tmp#programExecutionResult_status XMCDA-4_0_0_xsd.tmp#programExecutionResult_messages
Used by
Model
Children description, messages, status
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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="programExecutionResult">
  <xs:annotation>
    <xs:documentation>Output of programs.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="status" type="executionStatus" minOccurs="0"/>
    <xs:element name="messages" minOccurs="0" maxOccurs="1">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="message" type="message" minOccurs="0" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="defaultAttributes"/>
</xs:complexType>
Simple Type executionStatus
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration ok
enumeration warning
enumeration error
enumeration terminated
Used by
Source
<xs:simpleType name="executionStatus">
  <xs:annotation/>
  <xs:restriction base="xs:string">
    <xs:enumeration value="ok"/>
    <xs:enumeration value="warning"/>
    <xs:enumeration value="error"/>
    <xs:enumeration value="terminated"/>
  </xs:restriction>
</xs:simpleType>
Complex Type message
Annotations
XMCDA generic method message structure.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes XMCDA-4_0_0_xsd.tmp#message_level XMCDA-4_0_0_xsd.tmp#message_description XMCDA-4_0_0_xsd.tmp#message_text
Used by
Model
Children description, text
Attributes
QName Type Default Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
level messageLevel info optional
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="message">
  <xs:annotation>
    <xs:documentation>XMCDA generic method message structure.</xs:documentation>
  </xs:annotation>
  <xs:all>
    <xs:element name="description" type="description" minOccurs="0"/>
    <xs:element name="text" type="xs:string"/>
  </xs:all>
  <xs:attributeGroup ref="defaultAttributes"/>
  <xs:attribute name="level" type="messageLevel" default="info"/>
</xs:complexType>
Simple Type messageLevel
Annotations
.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration debug
enumeration info
enumeration warning
enumeration error
Used by
Attribute message/@level
Source
<xs:simpleType name="messageLevel">
  <xs:annotation>
    <xs:documentation>.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="debug"/>
    <xs:enumeration value="info"/>
    <xs:enumeration value="warning"/>
    <xs:enumeration value="error"/>
  </xs:restriction>
</xs:simpleType>
Attribute defaultAttributes / @id
Annotations
The id attribute allows to identify and reference the underlying piece of data.
Type xs:string
Properties
use optional
Used by
Attribute Group defaultAttributes
Source
<xs:attribute name="id" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>The id attribute allows to identify and reference the underlying piece of data.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute defaultAttributes / @name
Annotations
The name attribute contains the human readable name of the object or concept.
Type xs:string
Properties
use optional
Used by
Attribute Group defaultAttributes
Source
<xs:attribute name="name" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>The name attribute contains the human readable name of the object or concept.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute defaultAttributes / @mcdaConcept
Annotations
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.
Type xs:string
Properties
use optional
Used by
Attribute Group defaultAttributes
Source
<xs:attribute name="mcdaConcept" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>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.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute defaultAttributesIDRequired / @id
Annotations
The mandatory id attribute allows to identify and reference the underlying piece of data.
Type xs:string
Properties
use required
Used by
Attribute Group defaultAttributesIDRequired
Source
<xs:attribute name="id" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>The mandatory id attribute allows to identify and reference the underlying piece of data.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute defaultAttributesIDRequired / @name
Annotations
The name attribute contains the human readable name of the object or concept.
Type xs:string
Properties
use optional
Used by
Attribute Group defaultAttributesIDRequired
Source
<xs:attribute name="name" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>The name attribute contains the human readable name of the object or concept.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute defaultAttributesIDRequired / @mcdaConcept
Annotations
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.
Type xs:string
Properties
use optional
Used by
Attribute Group defaultAttributesIDRequired
Source
<xs:attribute name="mcdaConcept" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>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.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute nillableEndPoint / @open
Annotations
If false (the default), the end point is included in the segment, otherwise it is not part of the segment.
Type xs:boolean
Properties
default false
Used by
Complex Type nillableEndPoint
Source
<xs:attribute name="open" type="xs:boolean" default="false">
  <xs:annotation>
    <xs:documentation>If false (the default), the end point is included in the segment, otherwise it is not part of the segment.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute endPoint / @open
Annotations
If false (the default), the end point is included in the segment, otherwise it is not part of the segment.
Type xs:boolean
Properties
default false
Used by
Complex Type endPoint
Source
<xs:attribute name="open" type="xs:boolean" default="false">
  <xs:annotation>
    <xs:documentation>If false (the default), the end point is included in the segment, otherwise it is not part of the segment.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute intervalBound / @open
Annotations
If false (the default), the value is included within the interval, otherwise it is not.
Type xs:boolean
Properties
default false
Used by
Complex Type intervalBound
Source
<xs:attribute name="open" type="xs:boolean" default="false">
  <xs:annotation>
    <xs:documentation>If false (the default), the value is included within the interval, otherwise it is not.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute message / @level
Type messageLevel
Properties
default info
Facets
enumeration debug
enumeration info
enumeration warning
enumeration error
Used by
Complex Type message
Source
<xs:attribute name="level" type="messageLevel" default="info"/>
Attribute Group defaultAttributes
Annotations
Group of attributes used for all the main tags.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributes_id XMCDA-4_0_0_xsd.tmp#defaultAttributes_name XMCDA-4_0_0_xsd.tmp#defaultAttributes_mcdaConcept
Used by
Complex Types alternativeAssignment, alternativeValues, alternatives, alternativesAssignments, alternativesCriteriaValues, alternativesLinearConstraints, alternativesMatrix, alternativesSetValues, alternativesSets, alternativesSetsLinearConstraints, alternativesSetsMatrix, alternativesSetsValues, alternativesValues, bibliography, categories, categoriesInterval, categoriesLinearConstraints, categoriesMatrix, categoriesProfiles, categoriesSetValues, categoriesSets, categoriesSetsLinearConstraints, categoriesSetsMatrix, categoriesSetsValues, categoriesValues, categoryProfile, categoryValues, criteria, criteriaFunctions, criteriaHierarchy, criteriaLinearConstraints, criteriaMatrix, criteriaScales, criteriaSetValues, criteriaSets, criteriaSetsHierarchy, criteriaSetsLinearConstraints, criteriaSetsMatrix, criteriaSetsValues, criteriaThresholds, criteriaValues, criterionFunctions, criterionScales, criterionThresholds, criterionValues, function, message, performanceTable, programExecutionResult, programParameter, programParameters, scale, threshold, value
Elements alternativesLinearConstraints/constraints/constraint, alternativesLinearConstraints/constraints/constraint/elements/element, alternativesSetsLinearConstraints/constraints/constraint, alternativesSetsLinearConstraints/constraints/constraint/elements/element, categoriesLinearConstraints/constraints/constraint, categoriesLinearConstraints/constraints/constraint/elements/element, categoriesSetsLinearConstraints/constraints/constraint, categoriesSetsLinearConstraints/constraints/constraint/elements/element, criteriaLinearConstraints/constraints/constraint, criteriaLinearConstraints/constraints/constraint/elements/element, criteriaSetsLinearConstraints/constraints/constraint, criteriaSetsLinearConstraints/constraints/constraint/elements/element
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify and reference the underlying piece of data.
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:attributeGroup name="defaultAttributes">
  <xs:annotation>
    <xs:documentation>Group of attributes used for all the main tags.</xs:documentation>
  </xs:annotation>
  <xs:attribute name="id" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>The id attribute allows to identify and reference the underlying piece of data.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="name" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>The name attribute contains the human readable name of the object or concept.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="mcdaConcept" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>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.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:attributeGroup>
Attribute Group defaultAttributesIDRequired
Annotations
Group of attributes used for all the main tags. The id attribute is mandatory.
Diagram
Diagram XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired_id XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired_name XMCDA-4_0_0_xsd.tmp#defaultAttributesIDRequired_mcdaConcept
Used by
Attributes
QName Type Use Annotation
id xs:string required
The mandatory id attribute allows to identify and reference the underlying piece of data.
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:attributeGroup name="defaultAttributesIDRequired">
  <xs:annotation>
    <xs:documentation>Group of attributes used for all the main tags. The id attribute is mandatory.</xs:documentation>
  </xs:annotation>
  <xs:attribute name="id" type="xs:string" use="required">
    <xs:annotation>
      <xs:documentation>The mandatory id attribute allows to identify and reference the underlying piece of data.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="name" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>The name attribute contains the human readable name of the object or concept.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="mcdaConcept" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>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.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:attributeGroup>