Showing:

Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Used by
Element xmcda:point / abscissa
Namespace No namespace
Annotations
 
The abscissa of a point.
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
Type xmcda:value
Properties
content complex
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
 
<abscissa id="" mcdaConcept="" name="">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <interval>{1,1}</interval>
  <rational>{1,1}</rational>
  <label>{1,1}</label>
  <boolean>{1,1}</boolean>
  <NA>{1,1}</NA>
  <fuzzyNumber id="" mcdaConcept="" name="">{1,1}</fuzzyNumber>
  <valuedLabel>{1,1}</valuedLabel>
</abscissa>
Attributes
QName Type Use Annotation
id xs:string optional 
The id attribute allows to identify 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="abscissa" type="xmcda:value">
  <xs:annotation>
    <xs:documentation>The abscissa of a point.</xs:documentation>
  </xs:annotation>
</xs:element>
Element xmcda:point / ordinate
Namespace No namespace
Annotations
 
The ordinate of a point.
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
Type xmcda:value
Properties
content complex
Model
Children NA, boolean, fuzzyNumber, integer, interval, label, rational, real, valuedLabel
Instance
 
<ordinate id="" mcdaConcept="" name="">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <interval>{1,1}</interval>
  <rational>{1,1}</rational>
  <label>{1,1}</label>
  <boolean>{1,1}</boolean>
  <NA>{1,1}</NA>
  <fuzzyNumber id="" mcdaConcept="" name="">{1,1}</fuzzyNumber>
  <valuedLabel>{1,1}</valuedLabel>
</ordinate>
Attributes
QName Type Use Annotation
id xs:string optional 
The id attribute allows to identify 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="ordinate" type="xmcda:value">
  <xs:annotation>
    <xs:documentation>The ordinate of a point.</xs:documentation>
  </xs:annotation>
</xs:element>
Complex Type xmcda:point
Namespace http://www.decision-deck.org/2019/XMCDA-3.1.1
Annotations
 
Point defined by an abscissa and an ordinate.
Diagram
Diagram XMCDA-3_1_1_xsd_Complex_Type_xmcda_point.tmp#point_abscissa XMCDA-3_1_1_xsd_Complex_Type_xmcda_point.tmp#point_ordinate
Used by
Model
Children abscissa, ordinate
Source
 
<xs:complexType name="point">
  <xs:annotation>
    <xs:documentation>Point defined by an abscissa and an ordinate.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="abscissa" type="xmcda:value">
      <xs:annotation>
        <xs:documentation>The abscissa of a point.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="ordinate" type="xmcda:value">
      <xs:annotation>
        <xs:documentation>The ordinate of a point.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>