Showing:

Annotations
Attributes
Diagrams
Properties
Source
Used by
Attribute xmcda:defaultAttributes / @id
Namespace No namespace
Annotations
 
The id attribute allows to identify the underlying piece of data by a program.
Type xs:string
Properties
use optional
Used by
Attribute Group xmcda:defaultAttributes
Source
 
<xs:attribute name="id" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>The id attribute allows to identify the underlying piece of data by a program.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute xmcda:defaultAttributes / @name
Namespace No namespace
Annotations
 
The name attribute contains the human readable name of the object or concept.
Type xs:string
Properties
use optional
Used by
Attribute Group xmcda:defaultAttributes
Source
 
<xs:attribute name="name" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>The name attribute contains the human readable name of the object or concept.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute xmcda:defaultAttributes / @mcdaConcept
Namespace No namespace
Annotations
 
The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.
Type xs:string
Properties
use optional
Used by
Attribute Group xmcda:defaultAttributes
Source
 
<xs:attribute name="mcdaConcept" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute Group xmcda:defaultAttributes
Namespace http://www.decision-deck.org/2019/XMCDA-3.1.1
Annotations
 
Group of attributes used for all the main tags.
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes_id XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes_name XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes_mcdaConcept
Used by
Complex Types xmcda:alternativeAssignment, xmcda:alternativeValue, xmcda:alternatives, xmcda:alternativesAssignments, xmcda:alternativesCriteriaValues, xmcda:alternativesLinearConstraints, xmcda:alternativesMatrix, xmcda:alternativesSetValue, xmcda:alternativesSets, xmcda:alternativesSetsLinearConstraints, xmcda:alternativesSetsMatrix, xmcda:alternativesSetsValues, xmcda:alternativesValues, xmcda:bibliography, xmcda:categories, xmcda:categoriesInterval, xmcda:categoriesLinearConstraints, xmcda:categoriesMatrix, xmcda:categoriesProfiles, xmcda:categoriesSetValue, xmcda:categoriesSets, xmcda:categoriesSetsLinearConstraints, xmcda:categoriesSetsMatrix, xmcda:categoriesSetsValues, xmcda:categoriesValues, xmcda:categoryProfile, xmcda:categoryValue, xmcda:criteria, xmcda:criteriaFunctions, xmcda:criteriaHierarchy, xmcda:criteriaLinearConstraints, xmcda:criteriaMatrix, xmcda:criteriaScales, xmcda:criteriaSetValue, xmcda:criteriaSets, xmcda:criteriaSetsHierarchy, xmcda:criteriaSetsLinearConstraints, xmcda:criteriaSetsMatrix, xmcda:criteriaSetsValues, xmcda:criteriaThresholds, xmcda:criteriaValues, xmcda:criterionFunction, xmcda:criterionScale, xmcda:criterionThreshold, xmcda:criterionValue, xmcda:function, xmcda:message, xmcda:performanceTable, xmcda:programExecutionResult, xmcda:programParameter, xmcda:programParameters, xmcda:scale, xmcda:threshold, xmcda:value
Elements xmcda:alternativesLinearConstraints/constraints/constraint, xmcda:alternativesLinearConstraints/constraints/constraint/elements/element, xmcda:alternativesSetsLinearConstraints/constraints/constraint, xmcda:alternativesSetsLinearConstraints/constraints/constraint/elements/element, xmcda:categoriesLinearConstraints/constraints/constraint, xmcda:categoriesLinearConstraints/constraints/constraint/elements/element, xmcda:categoriesSetsLinearConstraints/constraints/constraint, xmcda:categoriesSetsLinearConstraints/constraints/constraint/elements/element, xmcda:criteriaLinearConstraints/constraints/constraint, xmcda:criteriaLinearConstraints/constraints/constraint/elements/element, xmcda:criteriaSetsLinearConstraints/constraints/constraint, xmcda:criteriaSetsLinearConstraints/constraints/constraint/elements/element
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:attributeGroup name="defaultAttributes">
  <xs:annotation>
    <xs:documentation>Group of attributes used for all the main tags.</xs:documentation>
  </xs:annotation>
  <xs:attribute name="id" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>The id attribute allows to identify the underlying piece of data by a program.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="name" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>The name attribute contains the human readable name of the object or concept.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="mcdaConcept" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>The mcdaConcept attribute allows to specify to what mcda concept a tag is related. It is used by an algorithm to make choices which will have an influence on the output. The documentation of the program should therefore specify, if necessary, what mcdaConcept should be used for the input data. In particular, if an algorithm requires, among other things, twice the same input tag, they can be differenciated by the mcdaConcept (this is even mandatory if they are present in the same file, but should be optional if the two tags can be in different input files, or originate from two different programs). The algorithm should therefore not be too strict on these mcdaConcepts, as this will reduce the compatibility between the various programs.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:attributeGroup>