Showing:

Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Used by
Element xmcda:interval / lowerBound
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_integer XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_real XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_interval XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_rational XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_label XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_boolean XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_NA XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_fuzzyNumber XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_valuedLabel XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value XMCDA-3_1_1_xsd_Complex_Type_xmcda_intervalBound.tmp#intervalBound_open XMCDA-3_1_1_xsd_Complex_Type_xmcda_intervalBound.tmp#intervalBound
Type xmcda:intervalBound
Type hierarchy
Properties
content complex
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
 
<lowerBound id="" mcdaConcept="" name="" open="">
  <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 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.
open xs:boolean optional
Source
 
<xs:element name="lowerBound" type="xmcda:intervalBound"/>
Element xmcda:interval / upperBound
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_integer XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_real XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_interval XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_rational XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_label XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_boolean XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_NA XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_fuzzyNumber XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value_valuedLabel XMCDA-3_1_1_xsd_Complex_Type_xmcda_value.tmp#value XMCDA-3_1_1_xsd_Complex_Type_xmcda_intervalBound.tmp#intervalBound_open XMCDA-3_1_1_xsd_Complex_Type_xmcda_intervalBound.tmp#intervalBound
Type xmcda: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="">
  <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 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.
open xs:boolean optional
Source
 
<xs:element name="upperBound" type="xmcda:intervalBound" minOccurs="0"/>
Complex Type xmcda:interval
Namespace http://www.decision-deck.org/2019/XMCDA-3.1.1
Annotations
 
Interval via a lower and an upper bound, which are values. The lower and the upper bounds are not mandatory, which allows to specify "infinite" bounds.
Diagram
Diagram XMCDA-3_1_1_xsd_Complex_Type_xmcda_interval.tmp#interval_lowerBound XMCDA-3_1_1_xsd_Complex_Type_xmcda_interval.tmp#interval_upperBound
Used by
Model
Children lowerBound, upperBound
Source
 
<xs:complexType name="interval">
  <xs:annotation>
    <xs:documentation>Interval via a lower and an upper bound, which are values. The lower and the upper bounds are not mandatory, which allows to specify "infinite" bounds.</xs:documentation>
  </xs:annotation>
  <!-- At least one among (lowerBound, upperBound), or both -->
  <xs:choice>
    <xs:sequence>
      <xs:element name="lowerBound" type="xmcda:intervalBound"/>
      <xs:element name="upperBound" type="xmcda:intervalBound" minOccurs="0"/>
    </xs:sequence>
    <xs:element name="upperBound" type="xmcda:intervalBound"/>
  </xs:choice>
</xs:complexType>