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