Showing:

Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Used by
Element xmcda:categoriesSetsValues / description
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Complex_Type_xmcda_description.tmp#description_author XMCDA-3_1_1_xsd_Complex_Type_xmcda_description.tmp#description_comment XMCDA-3_1_1_xsd_Complex_Type_xmcda_description.tmp#description_keyword XMCDA-3_1_1_xsd_Complex_Type_xmcda_description.tmp#description_bibliography XMCDA-3_1_1_xsd_Complex_Type_xmcda_description.tmp#description_creationDate XMCDA-3_1_1_xsd_Complex_Type_xmcda_description.tmp#description_lastModificationDate XMCDA-3_1_1_xsd_Complex_Type_xmcda_description.tmp#description
Type xmcda:description
Properties
content complex
minOccurs 0
Model
Children author, bibliography, comment, creationDate, keyword, lastModificationDate
Instance
 
<description>
  <author>{0,unbounded}</author>
  <comment>{0,1}</comment>
  <keyword>{0,unbounded}</keyword>
  <bibliography id="" mcdaConcept="" name="">{0,1}</bibliography>
  <creationDate>{0,1}</creationDate>
  <lastModificationDate>{0,1}</lastModificationDate>
</description>
Source
 
<xs:element name="description" type="xmcda:description" minOccurs="0"/>
Element xmcda:categoriesSetsValues / categoriesSetValue
Namespace No namespace
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetValue.tmp#categoriesSetValue_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetValue.tmp#categoriesSetValue_categoriesSetID XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetValue.tmp#categoriesSetValue_values XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetValue.tmp#categoriesSetValue
Type xmcda:categoriesSetValue
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children categoriesSetID, description, values
Instance
 
<categoriesSetValue id="" mcdaConcept="" name="">
  <description>{0,1}</description>
  <categoriesSetID>{1,1}</categoriesSetID>
  <values>{1,1}</values>
</categoriesSetValue>
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="categoriesSetValue" type="xmcda:categoriesSetValue" minOccurs="1" maxOccurs="unbounded"/>
Complex Type xmcda:categoriesSetsValues
Namespace http://www.decision-deck.org/2019/XMCDA-3.1.1
Annotations
 
A sequence of values related to sets of categories.
Diagram
Diagram XMCDA-3_1_1_xsd_Attribute_Group_xmcda_defaultAttributes.tmp#defaultAttributes XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsValues.tmp#categoriesSetsValues_description XMCDA-3_1_1_xsd_Complex_Type_xmcda_categoriesSetsValues.tmp#categoriesSetsValues_categoriesSetValue
Used by
Model
Children categoriesSetValue, description
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:complexType name="categoriesSetsValues">
  <xs:annotation>
    <xs:documentation>A sequence of values related to sets of categories.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="description" type="xmcda:description" minOccurs="0"/>
    <xs:element name="categoriesSetValue" type="xmcda:categoriesSetValue" minOccurs="1" maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:attributeGroup ref="xmcda:defaultAttributes"/>
</xs:complexType>