Provider: | PUT |
---|---|
Version: | 1.0 |
Finds all possible and necessary weak preference relations on the set of alternatives.
(For outputs, see below)
A list of all considered criteria. The input value should be a valid XMCDA document whose main tag is criteria.
The list of all considered alternatives. The input value should be a valid XMCDA document whose main tag is alternatives. Each alternative may be described using two attributes: id and name. While the first one denotes a machine readable name, the second represents a human readable name.
Tag: alternatives
Code:
<alternatives>
<alternative id="%1" name="%2" />
[...]
</alternatives>
Description of evaluation of alternatives on different criteria. It is required to provide the IDs of both criteria and alternatives described previously. The input value should be provided as a valid XMCDA document whose main tag is performanceTable
Tag: performanceTable
Code:
<performanceTable>
<alternativePerformances>
<alternativeID>%1</alternativeID>
<performance>
<criterionID>%2</criterionID>
<value>
<real>%3</real>
</value>
</performance>
[...]
</alternativePerformances>
[...]
</performanceTable>
Optional: yes, enabled by default
A set of values associated with the criteria. This input allows to determine what type of value function should be used for the particular criterion. For each criterion that has an associated greater than one value, a piecewise linear value function is used. In this case, the mentioned value denotes a number of characteristic points of this value function. For the criteria that are not listed in this file, or for these for which the provided values are lower than two uses a general value function. The input value should be provided as a valid XMCDA document whose main tag is criteriaValues. Each element should contain both an id of the criterion, and value tag.
Tag: criteriaValues
Code:
<criteriaValues>
<criterionValue>
<criterionID>%1</criterionID>
<value>
<integer>%2</integer>
</value>
</criterionValue>
[...]
</criteriaValues>
Optional: yes, enabled by default
A set of values associated with criteria that determine their preference direction (0 - gain, 1 - cost).
Tag: criteriaValues
Code:
<criteriaValues mcdaConcept="preferenceDirection">
<criterionValue>
<criterionID>%1</criterionID>
<value>
<integer>%2</integer>
</value>
</criterionValue>
[...]
</criteriaValues>
Optional: yes, enabled by default
Set of pairwise comparisons of reference alternatives. For a pair of alternatives three types of comparisons are supported. These are the strict preference, weak preference, and indifference. The input value should be provided as a valid XMCDA document whose main tag is alternativesComparisons. For each type of comparison, a separate alternativesComparisons tag should be used. Within these groups a mentioned types are denoted using a comparisonType tag by respectively strict, weak, and indif label. Comparisons should be provided as pairs of alternatives ids.
Tag: alternativesComparisons
Code:
<alternativesComparisons>
<comparisonType>
%1<!-- type of preference: strong, weak, or indif -->
</comparisonType>
<pairs>
<pair>
<initial>
<alternativeID>%2</alternativeID>
</initial>
<terminal>
<alternativeID>%3</alternativeID>
</terminal>
</pair>
[...]
</pairs>
</alternativesComparisons>
[...]
Optional: yes, enabled by default
Set of comparisons of intensities of preference. For a pair of preference relations three types of comparisons are supported. These are the strict preference, weak, preference, and indifference. The input value should be provided as a valid XMCDA document whose main tag is alternativesComparisons. For each type of comparison, a separate alternativesComparisons tag should be used. Within these groups aforementioned types are denoted using a comparisonType tag by respectively strict, weak, and indif label. Comparisons should be provided as pairs of two elementary sets of alternatives ids. The following form is expected:
Tag: alternativesComparisons
Code:
<alternativesComparisons>
<comparisonType>%1</comparisonType>
<pairs>
<pair>
<initial>
<alternativesSet>
<element>
<alternativeID>%2</alternativeID>
</element>
<element>
<alternativeID>%3</alternativeID>
</element>
</alternativesSet>
</initial>
<terminal>
<alternativesSet>
<element>
<alternativeID>%4</alternativeID>
</element>
<element>
<alternativeID>%5</alternativeID>
</element>
</alternativesSet>
</terminal>
</pair>
[...]
</pairs>
</alternativesComparisons>
[...]
Single boolean value. Determines whether to use sctrictly increasing (true) or monotonously increasing (false) value functions
Tag: methodParameters
Code:
<methodParameters>
<parameter name="strict">
<value>
<boolean>%1</boolean>
</value>
</parameter>
</methodParameters>
A list of all necessary weak preference relations on the set of alternatives. The returned value is an XMCDA document whose main tag is alternativesComparisons. Each relation is denoted as a pair of alternativesID
Tag: alternativesComparisons
Code:
<alternativesComparisons mcdaConcept="necessaryRelations">
<pairs>
<pair>
<initial>
<alternativeID>a01</alternativeID>
</initial>
<terminal>
<alternativeID>a01</alternativeID>
</terminal>
</pair>
[...]
</pairs>
</alternativesComparisons>
A list of all possible weak preference relations on the set of alternatives. The returned value is an XMCDA document whose main tag is alternativesComparisons. Each relation is denoted as a pair of alternativesID
Tag: alternativesComparisons
Code:
<alternativesComparisons mcdaConcept="possibleRelations">
<pairs>
<pair>
<initial>
<alternativeID>a01</alternativeID>
</initial>
<terminal>
<alternativeID>a01</alternativeID>
</terminal>
</pair>
[...]
</pairs>
</alternativesComparisons>
A list of messages generated by the algorithm.
For further technical details on the web service underlying this program, have a look at its documentation here.