Schema documentation for component preferenceDirection

content	simple
minOccurs	1

enumeration	min
enumeration	max

<xs:element name="preferenceDirection" type="xmcda:preferenceDirection" minOccurs="1"/>

content	complex
minOccurs	0

(integer | real | rational | NA)

<minimum id="" mcdaConcept="" name="">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</minimum>

QName

Type

Use

Annotation

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.

<xs:element name="minimum" type="xmcda:numericValue" minOccurs="0"/>

content	complex
minOccurs	0

(integer | real | rational | NA)

<maximum id="" mcdaConcept="" name="">
  <integer>{1,1}</integer>
  <real>{1,1}</real>
  <rational>{1,1}</rational>
  <NA>{1,1}</NA>
</maximum>

QName

Type

Use

Annotation

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.

<xs:element name="maximum" type="xmcda:numericValue" minOccurs="0"/>

Scale type which is quantitative. It is described by a preference direction (min or max), and a minimal and maximal quantitative evaluation.

<xs:complexType name="quantitative">
  <xs:annotation>
    <xs:documentation>Scale type which is quantitative. It is described by a preference direction (min or max), and a minimal and maximal quantitative evaluation.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="preferenceDirection" type="xmcda:preferenceDirection" minOccurs="1"/>
    <xs:element name="minimum" type="xmcda:numericValue" minOccurs="0"/>
    <!--  both min & max can be omitted -->
    <xs:element name="maximum" type="xmcda:numericValue" minOccurs="0"/>
  </xs:sequence>
</xs:complexType>

Showing: