Showing:

Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Element xmcda:XMCDA
Namespace http://www.decision-deck.org/2019/XMCDA-3.1.1
Annotations
Root of the XMCDA tree.
Diagram
Diagram XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_alternatives XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_alternativesSets XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteria XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaSets XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_categories XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_categoriesSets XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_performanceTable XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_alternativesValues XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_alternativesSetsValues XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_alternativesLinearConstraints XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_alternativesSetsLinearConstraints XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_alternativesMatrix XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_alternativesSetsMatrix XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaFunctions XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaScales XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaThresholds XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaValues XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaSetsValues XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaLinearConstraints XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaSetsLinearConstraints XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaMatrix XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaSetsMatrix XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaHierarchy XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_criteriaSetsHierarchy XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_alternativesCriteriaValues XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_categoriesProfiles XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_alternativesAssignments XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_categoriesValues XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_categoriesSetsValues XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_categoriesLinearConstraints XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_categoriesSetsLinearConstraints XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_categoriesMatrix XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_categoriesSetsMatrix XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.tmp#XMCDA_programParameters XMCDA-3_1_1_xsd_Element_xmcda_XMCDA.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:XMCDA xmlns:xmcda="http://www.decision-deck.org/2019/XMCDA-3.1.1">
  <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>
  <categories id="" mcdaConcept="" name="">{0,1}</categories>
  <categoriesSets id="" mcdaConcept="" name="">{0,1}</categoriesSets>
  <performanceTable id="" mcdaConcept="" name="">{0,unbounded}</performanceTable>
  <alternativesValues id="" mcdaConcept="" name="">{0,unbounded}</alternativesValues>
  <alternativesSetsValues id="" mcdaConcept="" name="">{0,unbounded}</alternativesSetsValues>
  <alternativesLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</alternativesLinearConstraints>
  <alternativesSetsLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</alternativesSetsLinearConstraints>
  <alternativesMatrix id="" mcdaConcept="" name="">{0,unbounded}</alternativesMatrix>
  <alternativesSetsMatrix id="" mcdaConcept="" name="">{0,unbounded}</alternativesSetsMatrix>
  <criteriaFunctions id="" mcdaConcept="" name="">{0,unbounded}</criteriaFunctions>
  <criteriaScales id="" mcdaConcept="" name="">{0,unbounded}</criteriaScales>
  <criteriaThresholds id="" mcdaConcept="" name="">{0,unbounded}</criteriaThresholds>
  <criteriaValues id="" mcdaConcept="" name="">{0,unbounded}</criteriaValues>
  <criteriaSetsValues id="" mcdaConcept="" name="">{0,unbounded}</criteriaSetsValues>
  <criteriaLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</criteriaLinearConstraints>
  <criteriaSetsLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</criteriaSetsLinearConstraints>
  <criteriaMatrix id="" mcdaConcept="" name="">{0,unbounded}</criteriaMatrix>
  <criteriaSetsMatrix id="" mcdaConcept="" name="">{0,unbounded}</criteriaSetsMatrix>
  <criteriaHierarchy id="" mcdaConcept="" name="">{0,unbounded}</criteriaHierarchy>
  <criteriaSetsHierarchy id="" mcdaConcept="" name="">{0,unbounded}</criteriaSetsHierarchy>
  <alternativesCriteriaValues id="" mcdaConcept="" name="">{0,unbounded}</alternativesCriteriaValues>
  <categoriesProfiles id="" mcdaConcept="" name="">{0,unbounded}</categoriesProfiles>
  <alternativesAssignments id="" mcdaConcept="" name="">{0,unbounded}</alternativesAssignments>
  <categoriesValues id="" mcdaConcept="" name="">{0,unbounded}</categoriesValues>
  <categoriesSetsValues id="" mcdaConcept="" name="">{0,unbounded}</categoriesSetsValues>
  <categoriesLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</categoriesLinearConstraints>
  <categoriesSetsLinearConstraints id="" mcdaConcept="" name="">{0,unbounded}</categoriesSetsLinearConstraints>
  <categoriesMatrix id="" mcdaConcept="" name="">{0,unbounded}</categoriesMatrix>
  <categoriesSetsMatrix id="" mcdaConcept="" name="">{0,unbounded}</categoriesSetsMatrix>
  <programParameters id="" mcdaConcept="" name="">{0,unbounded}</programParameters>
  <programExecutionResult id="" mcdaConcept="" name="">{0,unbounded}</programExecutionResult>
</xmcda:XMCDA>
Source
<xs:element name="XMCDA">
  <xs:annotation>
    <xs:documentation>Root of the XMCDA tree.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <!--				<xs:element name="description" type="xmcda:projectDescription" minOccurs="0" maxOccurs="unbounded"/>-->
      <!-- definition of the alternatives -->
      <xs:element name="alternatives" type="xmcda:alternatives" minOccurs="0" maxOccurs="1"/>
      <xs:element name="alternativesSets" type="xmcda:alternativesSets" minOccurs="0" maxOccurs="1"/>
      <!-- definition of the criteria -->
      <xs:element name="criteria" type="xmcda:criteria" minOccurs="0" maxOccurs="1"/>
      <xs:element name="criteriaSets" type="xmcda:criteriaSets" minOccurs="0" maxOccurs="1"/>
      <!-- definition of the categories -->
      <xs:element name="categories" type="xmcda:categories" minOccurs="0" maxOccurs="1"/>
      <xs:element name="categoriesSets" type="xmcda:categoriesSets" minOccurs="0" maxOccurs="1"/>
      <!-- the performance table -->
      <xs:element name="performanceTable" type="xmcda:performanceTable" minOccurs="0" maxOccurs="unbounded"/>
      <!-- a hierarchy on criteria, alternatives, attributes, categories -->
      <!-- <xs:element name="hierarchy" type="xmcda:hierarchy" minOccurs="0" maxOccurs="unbounded"/>-->
      <!-- data linked to alternatives -->
      <xs:element name="alternativesValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesValues"/>
      <xs:element name="alternativesSetsValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesSetsValues"/>
      <xs:element name="alternativesLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesLinearConstraints"/>
      <xs:element name="alternativesSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesSetsLinearConstraints"/>
      <xs:element name="alternativesMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesMatrix"/>
      <xs:element name="alternativesSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesSetsMatrix"/>
      <!-- data linked to criteria -->
      <xs:element name="criteriaFunctions" type="xmcda:criteriaFunctions" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="criteriaScales" type="xmcda:criteriaScales" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="criteriaThresholds" type="xmcda:criteriaThresholds" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="criteriaValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaValues"/>
      <xs:element name="criteriaSetsValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaSetsValues"/>
      <xs:element name="criteriaLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaLinearConstraints"/>
      <xs:element name="criteriaSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaSetsLinearConstraints"/>
      <xs:element name="criteriaMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaMatrix"/>
      <xs:element name="criteriaSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaSetsMatrix"/>
      <xs:element name="criteriaHierarchy" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaHierarchy"/>
      <xs:element name="criteriaSetsHierarchy" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaSetsHierarchy"/>
      <!-- data linked to alternatives and criteria -->
      <xs:element name="alternativesCriteriaValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesCriteriaValues"/>
      <!-- data linked to categories -->
      <xs:element name="categoriesProfiles" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesProfiles"/>
      <xs:element name="alternativesAssignments" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesAssignments"/>
      <xs:element name="categoriesValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesValues"/>
      <xs:element name="categoriesSetsValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesSetsValues"/>
      <xs:element name="categoriesLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesLinearConstraints"/>
      <xs:element name="categoriesSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesSetsLinearConstraints"/>
      <xs:element name="categoriesMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesMatrix"/>
      <xs:element name="categoriesSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesSetsMatrix"/>
      <!-- data linked to algorithms -->
      <xs:element name="programParameters" type="xmcda:programParameters" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="programExecutionResult" type="xmcda:programExecutionResult" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element xmcda:XMCDA / alternatives
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternatives.tmp#alternatives_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternatives.tmp#alternatives_alternative XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternatives.tmp#alternatives
Type xmcda:alternatives
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children alternative, description
Instance
<alternatives id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="alternatives" type="xmcda:alternatives" minOccurs="0" maxOccurs="1"/>
Element xmcda:XMCDA / alternativesSets
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSets.tmp#alternativesSets_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSets.tmp#alternativesSets_alternativesSet XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSets.tmp#alternativesSets
Type xmcda:alternativesSets
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children alternativesSet, description
Instance
<alternativesSets id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="alternativesSets" type="xmcda:alternativesSets" minOccurs="0" maxOccurs="1"/>
Element xmcda:XMCDA / criteria
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteria.tmp#criteria_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteria.tmp#criteria_criterion XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteria.tmp#criteria
Type xmcda:criteria
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children criterion, description
Instance
<criteria id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteria" type="xmcda:criteria" minOccurs="0" maxOccurs="1"/>
Element xmcda:XMCDA / criteriaSets
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSets.tmp#criteriaSets_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSets.tmp#criteriaSets_criteriaSet XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSets.tmp#criteriaSets
Type xmcda:criteriaSets
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children criteriaSet, description
Instance
<criteriaSets id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaSets" type="xmcda:criteriaSets" minOccurs="0" maxOccurs="1"/>
Element xmcda:XMCDA / categories
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categories.tmp#categories_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categories.tmp#categories_category XMCDA-3_1_1_xsd_Complex_Type_xmcda_categories.tmp#categories
Type xmcda:categories
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children category, description
Instance
<categories id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="categories" type="xmcda:categories" minOccurs="0" maxOccurs="1"/>
Element xmcda:XMCDA / categoriesSets
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSets.tmp#categoriesSets_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSets.tmp#categoriesSets_categoriesSet XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSets.tmp#categoriesSets
Type xmcda:categoriesSets
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children categoriesSet, description
Instance
<categoriesSets id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="categoriesSets" type="xmcda:categoriesSets" minOccurs="0" maxOccurs="1"/>
Element xmcda:XMCDA / performanceTable
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_performanceTable.tmp#performanceTable_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_performanceTable.tmp#performanceTable_alternativePerformances XMCDA-3_1_1_xsd_Complex_Type_xmcda_performanceTable.tmp#performanceTable
Type xmcda:performanceTable
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativePerformances, description
Instance
<performanceTable id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <alternativePerformances>{0,unbounded}</alternativePerformances>
</performanceTable>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="performanceTable" type="xmcda:performanceTable" minOccurs="0" maxOccurs="unbounded"/>
Element xmcda:XMCDA / alternativesValues
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesValues.tmp#alternativesValues_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesValues.tmp#alternativesValues_alternativeValue XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesValues.tmp#alternativesValues
Type xmcda:alternativesValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativeValue, description
Instance
<alternativesValues id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <alternativeValue id="" mcdaConcept="" name="">{1,unbounded}</alternativeValue>
</alternativesValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="alternativesValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesValues"/>
Element xmcda:XMCDA / alternativesSetsValues
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsValues.tmp#alternativesSetsValues_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsValues.tmp#alternativesSetsValues_alternativesSetValue XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsValues.tmp#alternativesSetsValues
Type xmcda:alternativesSetsValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativesSetValue, description
Instance
<alternativesSetsValues id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <alternativesSetValue id="" mcdaConcept="" name="">{1,unbounded}</alternativesSetValue>
</alternativesSetsValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="alternativesSetsValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesSetsValues"/>
Element xmcda:XMCDA / alternativesLinearConstraints
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesLinearConstraints.tmp#alternativesLinearConstraints_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesLinearConstraints.tmp#alternativesLinearConstraints_variables XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesLinearConstraints.tmp#alternativesLinearConstraints_constraints XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesLinearConstraints.tmp#alternativesLinearConstraints
Type xmcda:alternativesLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<alternativesLinearConstraints id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="alternativesLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesLinearConstraints"/>
Element xmcda:XMCDA / alternativesSetsLinearConstraints
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsLinearConstraints.tmp#alternativesSetsLinearConstraints_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsLinearConstraints.tmp#alternativesSetsLinearConstraints_variables XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsLinearConstraints.tmp#alternativesSetsLinearConstraints_constraints XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsLinearConstraints.tmp#alternativesSetsLinearConstraints
Type xmcda:alternativesSetsLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<alternativesSetsLinearConstraints id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="alternativesSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesSetsLinearConstraints"/>
Element xmcda:XMCDA / alternativesMatrix
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesMatrix.tmp#alternativesMatrix_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesMatrix.tmp#alternativesMatrix_valuation XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesMatrix.tmp#alternativesMatrix_row XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesMatrix.tmp#alternativesMatrix
Type xmcda:alternativesMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row, valuation
Instance
<alternativesMatrix id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <valuation id="" mcdaConcept="" name="">{0,1}</valuation>
  <row>{1,unbounded}</row>
</alternativesMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="alternativesMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesMatrix"/>
Element xmcda:XMCDA / alternativesSetsMatrix
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsMatrix.tmp#alternativesSetsMatrix_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsMatrix.tmp#alternativesSetsMatrix_valuation XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsMatrix.tmp#alternativesSetsMatrix_row XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesSetsMatrix.tmp#alternativesSetsMatrix
Type xmcda:alternativesSetsMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row, valuation
Instance
<alternativesSetsMatrix id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <valuation id="" mcdaConcept="" name="">{0,1}</valuation>
  <row>{1,unbounded}</row>
</alternativesSetsMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="alternativesSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesSetsMatrix"/>
Element xmcda:XMCDA / criteriaFunctions
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaFunctions.tmp#criteriaFunctions_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaFunctions.tmp#criteriaFunctions_criterionFunction XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaFunctions.tmp#criteriaFunctions
Type xmcda:criteriaFunctions
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criterionFunction, description
Instance
<criteriaFunctions id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <criterionFunction id="" mcdaConcept="" name="">{1,unbounded}</criterionFunction>
</criteriaFunctions>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaFunctions" type="xmcda:criteriaFunctions" minOccurs="0" maxOccurs="unbounded"/>
Element xmcda:XMCDA / criteriaScales
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaScales.tmp#criteriaScales_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaScales.tmp#criteriaScales_criterionScale XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaScales.tmp#criteriaScales
Type xmcda:criteriaScales
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criterionScale, description
Instance
<criteriaScales id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <criterionScale id="" mcdaConcept="" name="">{1,unbounded}</criterionScale>
</criteriaScales>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaScales" type="xmcda:criteriaScales" minOccurs="0" maxOccurs="unbounded"/>
Element xmcda:XMCDA / criteriaThresholds
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaThresholds.tmp#criteriaThresholds_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaThresholds.tmp#criteriaThresholds_criterionThreshold XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaThresholds.tmp#criteriaThresholds
Type xmcda:criteriaThresholds
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criterionThreshold, description
Instance
<criteriaThresholds id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <criterionThreshold id="" mcdaConcept="" name="">{1,unbounded}</criterionThreshold>
</criteriaThresholds>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaThresholds" type="xmcda:criteriaThresholds" minOccurs="0" maxOccurs="unbounded"/>
Element xmcda:XMCDA / criteriaValues
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaValues.tmp#criteriaValues_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaValues.tmp#criteriaValues_criterionValue XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaValues.tmp#criteriaValues
Type xmcda:criteriaValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criterionValue, description
Instance
<criteriaValues id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <criterionValue id="" mcdaConcept="" name="">{1,unbounded}</criterionValue>
</criteriaValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaValues"/>
Element xmcda:XMCDA / criteriaSetsValues
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsValues.tmp#criteriaSetsValues_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsValues.tmp#criteriaSetsValues_criteriaSetValue XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsValues.tmp#criteriaSetsValues
Type xmcda:criteriaSetsValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children criteriaSetValue, description
Instance
<criteriaSetsValues id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <criteriaSetValue id="" mcdaConcept="" name="">{1,unbounded}</criteriaSetValue>
</criteriaSetsValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaSetsValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaSetsValues"/>
Element xmcda:XMCDA / criteriaLinearConstraints
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaLinearConstraints.tmp#criteriaLinearConstraints_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaLinearConstraints.tmp#criteriaLinearConstraints_variables XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaLinearConstraints.tmp#criteriaLinearConstraints_constraints XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaLinearConstraints.tmp#criteriaLinearConstraints
Type xmcda:criteriaLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<criteriaLinearConstraints id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaLinearConstraints"/>
Element xmcda:XMCDA / criteriaSetsLinearConstraints
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsLinearConstraints.tmp#criteriaSetsLinearConstraints_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsLinearConstraints.tmp#criteriaSetsLinearConstraints_variables XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsLinearConstraints.tmp#criteriaSetsLinearConstraints_constraints XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsLinearConstraints.tmp#criteriaSetsLinearConstraints
Type xmcda:criteriaSetsLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<criteriaSetsLinearConstraints id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaSetsLinearConstraints"/>
Element xmcda:XMCDA / criteriaMatrix
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaMatrix.tmp#criteriaMatrix_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaMatrix.tmp#criteriaMatrix_valuation XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaMatrix.tmp#criteriaMatrix_row XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaMatrix.tmp#criteriaMatrix
Type xmcda:criteriaMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row, valuation
Instance
<criteriaMatrix id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <valuation id="" mcdaConcept="" name="">{0,1}</valuation>
  <row>{1,unbounded}</row>
</criteriaMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaMatrix"/>
Element xmcda:XMCDA / criteriaSetsMatrix
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsMatrix.tmp#criteriaSetsMatrix_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsMatrix.tmp#criteriaSetsMatrix_valuation XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsMatrix.tmp#criteriaSetsMatrix_row XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsMatrix.tmp#criteriaSetsMatrix
Type xmcda:criteriaSetsMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row, valuation
Instance
<criteriaSetsMatrix id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <valuation id="" mcdaConcept="" name="">{0,1}</valuation>
  <row>{1,unbounded}</row>
</criteriaSetsMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaSetsMatrix"/>
Element xmcda:XMCDA / criteriaHierarchy
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaHierarchy.tmp#criteriaHierarchy_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaHierarchy.tmp#criteriaHierarchy_nodes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaHierarchy.tmp#criteriaHierarchy
Type xmcda:criteriaHierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, nodes
Instance
<criteriaHierarchy id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <nodes>{1,unbounded}</nodes>
</criteriaHierarchy>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaHierarchy" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaHierarchy"/>
Element xmcda:XMCDA / criteriaSetsHierarchy
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsHierarchy.tmp#criteriaSetsHierarchy_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsHierarchy.tmp#criteriaSetsHierarchy_nodes XMCDA-3_1_1_xsd_Complex_Type_xmcda_criteriaSetsHierarchy.tmp#criteriaSetsHierarchy
Type xmcda:criteriaSetsHierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, nodes
Instance
<criteriaSetsHierarchy id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <nodes>{1,unbounded}</nodes>
</criteriaSetsHierarchy>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="criteriaSetsHierarchy" minOccurs="0" maxOccurs="unbounded" type="xmcda:criteriaSetsHierarchy"/>
Element xmcda:XMCDA / alternativesCriteriaValues
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesCriteriaValues.tmp#alternativesCriteriaValues_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesCriteriaValues.tmp#alternativesCriteriaValues_alternativeCriteriaValues XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesCriteriaValues.tmp#alternativesCriteriaValues
Type xmcda:alternativesCriteriaValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativeCriteriaValues, description
Instance
<alternativesCriteriaValues id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <alternativeCriteriaValues>{1,unbounded}</alternativeCriteriaValues>
</alternativesCriteriaValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="alternativesCriteriaValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesCriteriaValues"/>
Element xmcda:XMCDA / categoriesProfiles
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesProfiles.tmp#categoriesProfiles_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesProfiles.tmp#categoriesProfiles_categoryProfile XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesProfiles.tmp#categoriesProfiles
Type xmcda:categoriesProfiles
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children categoryProfile, description
Instance
<categoriesProfiles id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="categoriesProfiles" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesProfiles"/>
Element xmcda:XMCDA / alternativesAssignments
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesAssignments.tmp#alternativesAssignments_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesAssignments.tmp#alternativesAssignments_alternativeAssignment XMCDA-3_1_1_xsd_Complex_Type_xmcda_alternativesAssignments.tmp#alternativesAssignments
Type xmcda:alternativesAssignments
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children alternativeAssignment, description
Instance
<alternativesAssignments id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="alternativesAssignments" minOccurs="0" maxOccurs="unbounded" type="xmcda:alternativesAssignments"/>
Element xmcda:XMCDA / categoriesValues
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesValues.tmp#categoriesValues_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesValues.tmp#categoriesValues_categoryValue XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesValues.tmp#categoriesValues
Type xmcda:categoriesValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children categoryValue, description
Instance
<categoriesValues id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <categoryValue id="" mcdaConcept="" name="">{1,unbounded}</categoryValue>
</categoriesValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="categoriesValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesValues"/>
Element xmcda:XMCDA / categoriesSetsValues
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsValues.tmp#categoriesSetsValues_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsValues.tmp#categoriesSetsValues_categoriesSetValue XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsValues.tmp#categoriesSetsValues
Type xmcda:categoriesSetsValues
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children categoriesSetValue, description
Instance
<categoriesSetsValues id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <categoriesSetValue id="" mcdaConcept="" name="">{1,unbounded}</categoriesSetValue>
</categoriesSetsValues>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="categoriesSetsValues" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesSetsValues"/>
Element xmcda:XMCDA / categoriesLinearConstraints
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesLinearConstraints.tmp#categoriesLinearConstraints_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesLinearConstraints.tmp#categoriesLinearConstraints_variables XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesLinearConstraints.tmp#categoriesLinearConstraints_constraints XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesLinearConstraints.tmp#categoriesLinearConstraints
Type xmcda:categoriesLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<categoriesLinearConstraints id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="categoriesLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesLinearConstraints"/>
Element xmcda:XMCDA / categoriesSetsLinearConstraints
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsLinearConstraints.tmp#categoriesSetsLinearConstraints_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsLinearConstraints.tmp#categoriesSetsLinearConstraints_variables XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsLinearConstraints.tmp#categoriesSetsLinearConstraints_constraints XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsLinearConstraints.tmp#categoriesSetsLinearConstraints
Type xmcda:categoriesSetsLinearConstraints
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children constraints, description, variables
Instance
<categoriesSetsLinearConstraints id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="categoriesSetsLinearConstraints" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesSetsLinearConstraints"/>
Element xmcda:XMCDA / categoriesMatrix
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesMatrix.tmp#categoriesMatrix_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesMatrix.tmp#categoriesMatrix_valuation XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesMatrix.tmp#categoriesMatrix_row XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesMatrix.tmp#categoriesMatrix
Type xmcda:categoriesMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row, valuation
Instance
<categoriesMatrix id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <valuation id="" mcdaConcept="" name="">{0,1}</valuation>
  <row>{1,unbounded}</row>
</categoriesMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="categoriesMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesMatrix"/>
Element xmcda:XMCDA / categoriesSetsMatrix
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsMatrix.tmp#categoriesSetsMatrix_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsMatrix.tmp#categoriesSetsMatrix_valuation XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsMatrix.tmp#categoriesSetsMatrix_row XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsMatrix.tmp#categoriesSetsMatrix
Type xmcda:categoriesSetsMatrix
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, row, valuation
Instance
<categoriesSetsMatrix id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <valuation id="" mcdaConcept="" name="">{0,1}</valuation>
  <row>{1,unbounded}</row>
</categoriesSetsMatrix>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="categoriesSetsMatrix" minOccurs="0" maxOccurs="unbounded" type="xmcda:categoriesSetsMatrix"/>
Element xmcda:XMCDA / programParameters
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_programParameters.tmp#programParameters_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_programParameters.tmp#programParameters_parameter XMCDA-3_1_1_xsd_Complex_Type_xmcda_programParameters.tmp#programParameters
Type xmcda:programParameters
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, parameter
Instance
<programParameters id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <parameter id="" mcdaConcept="" name="">{1,unbounded}</parameter>
</programParameters>
Attributes
QName Type Use Annotation
id xs:string optional
The id attribute allows to identify the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="programParameters" type="xmcda:programParameters" minOccurs="0" maxOccurs="unbounded"/>
Element xmcda:XMCDA / programExecutionResult
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_programExecutionResult.tmp#programExecutionResult_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_programExecutionResult.tmp#programExecutionResult_status XMCDA-3_1_1_xsd_Complex_Type_xmcda_programExecutionResult.tmp#programExecutionResult_messages XMCDA-3_1_1_xsd_Complex_Type_xmcda_programExecutionResult.tmp#programExecutionResult
Type xmcda:programExecutionResult
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children description, messages, status
Instance
<programExecutionResult id="" mcdaConcept="" name="">
  <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 the underlying piece of data by a program.
mcdaConcept xs:string optional
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
name xs:string optional
The name attribute contains the human readable name of the object or concept.
Source
<xs:element name="programExecutionResult" type="xmcda:programExecutionResult" minOccurs="0" maxOccurs="unbounded"/>