requisis_logo _reqif.properties database

Comparing tool compatibility

Formal Mind: formalmind Studio 1.0 
Polarion Requirements 3.10.0 (2016) 

Show also Properties, that are considered to be compatible.

PropertyStatusExportImport
ID: 3 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The Document contains more than one SPECIFICATION element.
Explanation: More than one specification is contained in the ReqIF-file
OKWill always occurImported correctly
ID: 9 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The XML-attribute LONG-NAME is used.
Explanation: The specification has a name.
OKWill always occurImported, with comment
During the import the user has to choose the name of the document to import the data into.
ID: 10 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The XML-attribute LONG-NAME is not used.
Explanation: The specification has no name.
OKWill always occurImported, with comment
During the import the user has to choose the name of the document to import the data into.
ID: 11 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The XML-attribute LONG-NAME contains ANSI characters.
Explanation: The name contains ANSI characters.
OKWill always occurImported, with comment
During the import the user has to choose the name of the document to import the data into.
ID: 12 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The XML-attribute LONG-NAME contains Unicode characters.
Explanation: The name contains Unicode characters.
OKWill always occurImported, with comment
During the import the user has to choose the name of the document to import the data into.
ID: 13 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The XML-attribute LONG-NAME is empty.
Explanation: The specification name is an empty string.
OKWill always occurImported, with comment
During the import the user has to choose the name of the document to import the data into.
ID: 14 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The XML-attribute DESC is used.
CRITICALWill always occurSome data is lost, without warning
The content of the DESC attribute can not be imported, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 15 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The XML-attribute DESC is not used.
OKWill always occurNot relevant
ID: 16 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The XML-attribute DESC contains ANSI characters.
OKWill always occurNot relevant
ID: 17 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The XML-attribute DESC contains Unicode characters.
OKWill always occurNot relevant
ID: 18 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION /
The XML-attribute DESC is empty.
OKWill always occurNot relevant
ID: 2002 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION / VALUES /
Contains VALUES
Explanation: Contains Attribute-Values on Specification Level
CRITICALWill always occurSome data is lost, without warning
The values are not imported.
ID: 26 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION / TYPE /
Two or more SPECIFICATION elements reference to the same SPECIFICATION-TYPE element.
Explanation: Two specifications are of the same type, i.e. they share a set of attribute definitions.
CRITICALWill always occurSome data is lost, without warning
Specification attributes are not imported, but Polarion will preserve any attribute definition in the ReqIF-file in a round trip.
ID: 27 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION / TYPE /
Two or more SPECIFICATION elements do each reference to different SPECIFICATION-TYPE element.
Explanation: Not all modules in the ReqIF-file are of the same type, i.e. they do not share one set of attribute definitions.
CRITICALWill always occurSome data is lost, without warning
Specification attributes are not imported, but Polarion will preserve any attribute definition in the ReqIF-file in a round trip.
ID: 47 REQ-IF-CONTENT / SPECIFICATIONS / SPECIFICATION / CHILDREN / SPEC-HIERARCHY /
The XML-attribute IS-TABLE-INTERNAL is used and set to true.
Explanation: If set to true, the element is the root of a table containing requirements. These tables are used by some requirements authoring Tools.
CRITICALWill always occurSome data is lost, without warning
Tables composed of spec-object elements cannot be represented as tables in Polarion, but it will preserve the XML-attribute in the ReqIF-file in a round trip. The spec-objects are imported as normal work items.
ID: 68 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
The XML-attribute LONG-NAME is used.
Explanation: The spec-object has a name.
CRITICALWill always occurSome data is lost, without warning
The name cannot be imported, but Polarion will preserve the XML-attribute in the ReqIF-file in a round trip.
ID: 72 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
The XML-attribute LONG-NAME is not used.
Explanation: The spec-object has no name.
OKWill always occurImported correctly
ID: 73 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
The XML-attribute LONG-NAME contains ANSI characters.
Explanation: The name contains ANSI characters.
OKWill always occurNot relevant
ID: 74 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
The XML-attribute LONG-NAME contains Unicode characters.
Explanation: The name contains Unicode characters.
OKWill always occurNot relevant
ID: 75 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
The XML-attribute LONG-NAME is empty.
Explanation: The spec-object name is an empty string.
OKWill always occurNot relevant
ID: 76 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
The XML-attribute DESC is used.
CRITICALWill always occurSome data is lost, without warning
The content of the DESC attribute can not be imported, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 77 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
The XML-attribute DESC is not used.
OKWill always occurNot relevant
ID: 78 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
The XML-attribute DESC contains ANSI characters.
OKWill always occurNot relevant
ID: 79 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
The XML-attribute DESC contains Unicode characters.
OKWill always occurNot relevant
ID: 80 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
The XML-attribute DESC is empty.
OKWill always occurNot relevant
ID: 81 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
There are two or more SPEC-OBJECT elements with the same value for the XML-attribute LONG-NAME.
Explanation: Two or more spec-objects in the ReqIF-file share the same name.
OKWill always occurNot relevant
ID: 82 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
A SPEC-OBJECT element is not referenced by any SPEC-HIERARCHY element in the document.
Explanation: A spec-object is not assigned to any specification, i.e. it is not part of any hierarchy tree.
CRITICALWill always occurSome data is lost, without warning
The spec-object is not imported.
ID: 83 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
A SPEC-OBJECT element is referenced by two or more SPEC-HIERARCHY elements that are contained in the same SPECIFICATION element.
Explanation: A spec-object is used more than once within the hierachy tree of a specification.
ABORTEDWill always occurImport aborted
ID: 84 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT /
A SPEC-OBJECT element is referenced by two or more SPEC-HIERARCHY elements that are contained in different SPECIFIATION elements.
Explanation: A spec-object is used within the hierachy trees of two or more different specifications.
CRITICALWill always occurSome data is lost, without warning
The Spec-Object is imported twice: an independent work item (with a unique ID) is created in each Module.
ID: 94 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT / TYPE /
Not all SPEC-OBJECT elements contained in SPEC-OBJECTS are of the same SPEC-OBJECT-TYPE.
Explanation: Not all spec-objects in the ReqIF-file are of the same type, i.e. they do not share the same set of attributes.
OKWill always occurImported correctly
ID: 95 REQ-IF-CONTENT / SPEC-OBJECTS / SPEC-OBJECT / TYPE /
There are two or more SPEC-OBJECT elements that reference to the same SPEC-OBJECT-TYPE, each of these SPEC-OBJECT elements is referenced by a SPEC-HIERARCHY element, whereby the SPEC-HIERARCHY elements are contained in different SPECIFIATION elements.
Explanation: A SPEC-OBJECT-TYPE element is used in several specifications.
OKWill always occurImported correctly
ID: 97 REQ-IF-CONTENT / SPEC-RELATION /
The XML-attribute LONG-NAME is used.
Explanation: The spec-relation has a name.
CRITICALWill always occurSome data is lost, without warning
The name cannot be import, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 98 REQ-IF-CONTENT / SPEC-RELATION /
The XML-attribute LONG-NAME is not used.
Explanation: The spec-relation has no name.
OKWill always occurImported correctly
ID: 99 REQ-IF-CONTENT / SPEC-RELATION /
The XML-attribute LONG-NAME contains ANSI characters.
Explanation: The name contains ANSI characters.
OKWill always occurNot relevant
ID: 100 REQ-IF-CONTENT / SPEC-RELATION /
The XML-attribute LONG-NAME contains Unicode characters.
Explanation: The name contains Unicode characters.
OKWill always occurNot relevant
ID: 101 REQ-IF-CONTENT / SPEC-RELATION /
The XML-attribute LONG-NAME is empty.
Explanation: The name of the spec-relation is an empty string.
OKWill always occurNot relevant
ID: 102 REQ-IF-CONTENT / SPEC-RELATION /
The XML-attribute DESC is used.
CRITICALWill always occurSome data is lost, without warning
The content of the DESC attribute can not be imported, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 103 REQ-IF-CONTENT / SPEC-RELATION /
The XML-attribute DESC is not used.
OKWill always occurNot relevant
ID: 104 REQ-IF-CONTENT / SPEC-RELATION /
The XML-attribute DESC contains ANSI characters.
OKWill always occurNot relevant
ID: 105 REQ-IF-CONTENT / SPEC-RELATION /
The XML-attribute DESC contains Unicode characters.
OKWill always occurNot relevant
ID: 106 REQ-IF-CONTENT / SPEC-RELATION /
The XML-attribute DESC is empty.
OKWill always occurNot relevant
ID: 107 REQ-IF-CONTENT / SPEC-RELATION /
There are two or more SPEC-RELATION elements with the same value for the XML-attribute LONG-NAME.
Explanation: Two spec-relations share the same name.
OKWill always occurNot relevant
ID: 108 REQ-IF-CONTENT / SPEC-RELATION /
There is a RELATION-GROUP element that references to the SPEC-RELATION element.
Explanation: Spec-Relation is part of a relation-group.
OKWill always occurImported correctly
ID: 109 REQ-IF-CONTENT / SPEC-RELATION /
There is no RELATION-GROUP element that references to the SPEC-RELATION element.
Explanation: Spec-Relation is not part of a Relation-Group.
OKWill always occurImported correctly
ID: 117 REQ-IF-CONTENT / SPEC-RELATION / TYPES /
Not all SPEC-RELATION elements contained in SPEC-RELATIONS reference to the same SPEC-RELATION-TYPE element.
Explanation: Not all spec-relations are of the same type, i.e. they do not share the same set of attributes.
OKWill always occurImported correctly
The information cannot be import, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 119 REQ-IF-CONTENT / SPEC-RELATION / SOURCE /
The referenced SPEC-OBJECT element exisits within the ReqIF document but is not contained in any SPECIFICATION.
Explanation: The source of the spec-relation is an spec-object within the ReqIF document that is not assigned to any specification.
WARNWill always occurSome data is lost, with warning
The link is not imported.
ID: 120 REQ-IF-CONTENT / SPEC-RELATION / SOURCE /
The referenced SPEC-OBJECT element is not contained in the ReqIF document.
Explanation: The source of the spec-relation is an spec-object that is not present in the ReqIF-file. The spec-object is either contained in another ReqIF-file or has not been exported.
OKWill always occur
The ID of the referenced SpecObject will be maintained.
Imported, with comment
The link is imported, if the spec-object was imported previously in the same project in another module.
ID: 123 REQ-IF-CONTENT / SPEC-RELATION / TARGET /
The referenced SPEC-OBJECT element exisits within the ReqIF document but is not contained in any SPECIFICATION.
Explanation: The target of the spec-relation is a spec-object that is not assigned to any specification.
CRITICALWill always occurSome data is lost, without warning
The link is not imported.
ID: 124 REQ-IF-CONTENT / SPEC-RELATION / TARGET /
The referenced SPEC-OBJECT element is not contained in the ReqIF document.
Explanation: The source of the spec-relation is an spec-object that is not present in the ReqIF-file. The spec-object is either contained in another ReqIF-file or has not been exported.
OKWill always occur
The ID of the referenced SpecObject will be maintained.
Imported, with comment
The link is imported, if the spec-object was imported previously in the same project in another module.
ID: 126 REQ-IF-CONTENT / SPEC-RELATION / SOURCE/TARGET /
The SOURCE and TARGET elements reference to SPEC-OBJECT elements that are contained in the same SPECIFICATION.
Explanation: The spec-relation represents a link within a specification.
OKWill always occurImported correctly
ID: 127 REQ-IF-CONTENT / SPEC-RELATION / SOURCE/TARGET /
The SOURCE and TARGET elements reference to SPEC-OBJECT elements that are contained in different SPECIFICATIONs.
Explanation: The spec-relation represents a link across two specifications.
OKWill always occurImported correctly
ID: 130 REQ-IF-CONTENT / RELATION-GROUPS / RELATION-GROUP /
The XML-attribute LONG-NAME contains ANSI characters.
Explanation: LONG-NAME is mandatory for relation-groups. The name contains ANSI characters.
OKWill always occurNot relevant
ID: 131 REQ-IF-CONTENT / RELATION-GROUPS / RELATION-GROUP /
The XML-attribute LONG-NAME contains Unicode characters.
Explanation: LONG-NAME is mandatory for relation-groups. The name contains Unicode characters.
OKWill always occurNot relevant
ID: 132 REQ-IF-CONTENT / RELATION-GROUPS / RELATION-GROUP /
The XML-attribute LONG-NAME is empty.
Explanation: LONG-NAME is mandatory for relation-groups. The name of the relation-group is an empty sting.
OKWill always occurNot relevant
ID: 133 REQ-IF-CONTENT / RELATION-GROUPS / RELATION-GROUP /
The XML-attribute DESC is used.
CRITICALWill always occurSome data is lost, without warning
The content of the DESC attribute can not be imported, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 134 REQ-IF-CONTENT / RELATION-GROUPS / RELATION-GROUP /
The XML-attribute DESC is not used.
OKWill always occurNot relevant
ID: 135 REQ-IF-CONTENT / RELATION-GROUPS / RELATION-GROUP /
The XML-attribute DESC contains ANSI characters.
OKWill always occurNot relevant
ID: 136 REQ-IF-CONTENT / RELATION-GROUPS / RELATION-GROUP /
The XML-attribute DESC contains Unicode characters.
OKWill always occurNot relevant
ID: 137 REQ-IF-CONTENT / RELATION-GROUPS / RELATION-GROUP /
The XML-attribute DESC is empty.
OKWill always occurNot relevant
ID: 138 REQ-IF-CONTENT / RELATION-GROUPS / RELATION-GROUP /
There are two or more RELATION-GROUP elements with the same value for the XML-attribute LONG-NAME.
Explanation: Two or more relation-groups share the same name.
OKWill always occurNot relevant
ID: 147 REQ-IF-CONTENT / RELATION-GROUPS / TYPES /
The referenced RELATION-GROUP-TYPE element does contain AttributeDefinition elements.
Explanation: It is recommended NOT to add any AttributeDefinition element, since due to a bug in the ReqIF-specification it is not possible to specify values.
OKWill always occurNot relevant
ID: 148 REQ-IF-CONTENT / RELATION-GROUPS / TYPES /
Not all RELATION-GROUP elements contained in RELATION-GROUPS reference to the same RELATION-GROUPS-TYPE element.
Explanation: Not all relation-groups are of the same type, i.e. they do not share the same set of attributes.
OKWill always occurNot relevant
ID: 150 REQ-IF-CONTENT / RELATION-GROUPS / SOURCE-SPECIFICATION /
The referenced SPECIFICATION element is not contained in the ReqIF document.
Explanation: The source specification may be contained in another ReqIF-file or it has not been exported.
OKWill always occur
The ID of the referenced element will be maintained.
Not relevant
ID: 152 REQ-IF-CONTENT / RELATION-GROUPS / TARGET-SPECIFICATION /
The referenced SPECIFICATION element is not contained in the ReqIF document.
Explanation: The target specification may be contained in another ReqIF-file or it has not been exported.
OKWill always occur
The ID of the referenced element will be maintained.
Not relevant
ID: 154 REQ-IF-CONTENT / RELATION-GROUPS / SOURCE-SPECIFICATION/TARGET-SPECIFICATION /
The SOURCE-SPECIFICATION and TARGET-SPECIFICATION elements reference to the same SPECIFICATION element.
OKWill always occurNot relevant
ID: 155 REQ-IF-CONTENT / RELATION-GROUPS / SOURCE-SPECIFICATION/TARGET-SPECIFICATION /
The SOURCE-SPECIFICATION and TARGET-SPECIFICATION elements reference to different SPECIFICATION elements.
OKWill always occurNot relevant
ID: 157 REQ-IF-CONTENT / RELATION-GROUPS / SPEC-RELATIONS /
SPEC-RELATIONS does not contain any SPEC-RELATION element or is not specified.
Explanation: The spec-relation-group is not referencing to any spec-relation.
OKWill always occurNot relevant
ID: 158 REQ-IF-CONTENT / RELATION-GROUPS / SPEC-RELATIONS /
There are two or more SPEC-RELATION elements with the same value for the XML-attribute LONG-NAME.
Explanation: Two spec-relations referenced by a realtion-group share the same name.
OKWill always occurNot relevant
ID: 159 REQ-IF-CONTENT / RELATION-GROUPS / SPEC-RELATIONS /
Not all SPEC-RELATION elements contained in SPEC-RELATIONS reference to the same SPEC-RELATION-TYPE element.
Explanation: The realtion-group references to spec-relations of different types, i.e. the spec-relations do not share the same set of attributes.
OKWill always occurNot relevant
ID: 161 REQ-IF-CONTENT / SPEC-TYPES /
There are two or more SpecType elements with the same value for the XML-attribute LONG-NAME.
Explanation: The names of SpecType elements are not unique.
OKWill always occurImported correctly
ID: 163 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
The XML-attribute LONG-NAME is used.
Explanation: The specification-type has a name.
CRITICALWill always occurSome data is lost, without warning
The name of the specification-type canot be imported.
ID: 164 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
The XML-attribute LONG-NAME is not used.
Explanation: The specification-type has no name.
OKWill always occurNot relevant
ID: 165 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
The XML-attribute LONG-NAME contains ANSI characters.
Explanation: The name contains ANSI characters.
OKWill always occurNot relevant
ID: 166 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
The XML-attribute LONG-NAME contains Unicode characters.
Explanation: The name contains Unicode characters.
OKWill always occurNot relevant
ID: 167 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
The XML-attribute LONG-NAME is empty.
Explanation: The name of the specification-type is an empty string.
CRITICALWill always occurSome data is lost, without warning
The document types (corresponds to specification-types) have to be created manually in Polation prior to the import. During the import the types must than be mapped manually.
ID: 168 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
The XML-attribute DESC is used.
CRITICALWill always occurSome data is lost, without warning
The content of the DESC attribute can not be imported, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 169 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
The XML-attribute DESC is not used.
OKWill always occurNot relevant
ID: 170 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
The XML-attribute DESC contains ANSI characters.
OKWill always occurNot relevant
ID: 171 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
The XML-attribute DESC contains Unicode characters.
OKWill always occurNot relevant
ID: 172 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
The XML-attribute DESC is empty.
OKWill always occurNot relevant
ID: 173 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
There are two or more SPECIFICATION-TYPE elements contained in SPEC-TYPES with the same value for the XML-attribute LONG-NAME.
Explanation: The specification-type elements do not have unique names.
CRITICALWill always occurSome data is lost, without warning
The name of the specification cannot be imported.
ID: 174 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE /
A SPECIFICATION-TYPE element is not referenced by any SPECIFICATION element in the document.
Explanation: The specification-type is not used.
CRITICALWill always occurSome data is lost, without warning
A specification-type element cannot be imported.
ID: 182 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE / SPEC-ATTRIBUTES /
There is one or more AttributeDefinition elements contained in SPEC-ATTRIBUTES.
Explanation: The type does define attributes.
CRITICALWill always occurSome data is lost, without warning
The attribute definitions cannot be imported.
ID: 183 REQ-IF-CONTENT / SPEC-TYPES / SPECIFICATION-TYPE / SPEC-ATTRIBUTES /
There are two or more AttributeDefinition elements contained in SPEC-ATTRIBUTES with the same value for the XML-attribute LONG-NAME.
Explanation: The attributes defined by this type do not have unique names.
OKWill always occurNot relevant
ID: 186 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
The XML-attribute LONG-NAME is used.
Explanation: The spec-object-type has a name.
OKWill always occurImported, with comment
The work item types (corresponds to spec-object-types) have to be created manually in Polation prior to the import. During the import the types must than be mapped manually.
ID: 187 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
The XML-attribute LONG-NAME is not used.
Explanation: The spec-object-type has no name.
OKWill always occurImported, with comment
The work item types (corresponds to spec-object-types) have to be created manually in Polation prior to the import. During the import the types must than be mapped manually. In Polarion a work item type must have a name.
ID: 188 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
The XML-attribute LONG-NAME contains ANSI characters.
Explanation: The name contains ANSI characters.
OKWill always occurImported correctly
ID: 189 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
The XML-attribute LONG-NAME contains Unicode characters.
Explanation: The name contains Unicode characters.
OKWill always occurImported correctly
ID: 190 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
The XML-attribute LONG-NAME is empty.
Explanation: The name of the spec-object-type is an empty string.
WARNWill always occurSome data is lost, with warning
The work item types (corresponds to spec-object-types) have to be created manually in Polation prior to the import. During the import the types must than be mapped manually. In Polarion a work item type must have a name.
ID: 191 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
The XML-attribute DESC is used.
CRITICALWill always occurSome data is lost, without warning
The content of the DESC attribute can not be imported, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 192 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
The XML-attribute DESC is not used.
OKWill always occurNot relevant
The information is not imported.
ID: 193 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
The XML-attribute DESC contains ANSI characters.
OKWill always occurNot relevant
ID: 194 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
The XML-attribute DESC contains Unicode characters.
OKWill always occurNot relevant
ID: 195 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
The XML-attribute DESC is empty.
OKWill always occurNot relevant
ID: 196 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
There are two or more SPEC-OBJECT-TYPE elements contained in SPEC-TYPES with the same value for the XML-attribute LONG-NAME.
Explanation: The spec-object-types do not have unique names.
OKWill always occurImported correctly
ID: 197 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
A SPEC-OBJECT-TYPE element is not referenced by any SPEC-OBJECT element in the document.
Explanation: The spec-object-type is not used.
OKWill always occurImported, with comment
The work item definitions (correspond to spec-object-types) have to be created manually in Polation prior to the import. During the import the atttributes must be mapped manually. Work item definitions, that are not used can be created.
ID: 206 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE /
Two or more SPEC-OBJECT elements, contained in the SpecHierarchy tree of different SPECIFICATION elements, reference the same SPEC-OBJECT-TYPE element.
Explanation: The spec-object-type is used in more than one specification.
OKWill always occurImported correctly
ID: 204 REQ-IF-CONTENT / SPEC-TYPES / SPEC-OBJECT-TYPE / SPEC-ATTRIBUTES /
There are two or more AttributeDefinition elements contained in SPEC-ATTRIBUTES with the same value for the XML-attribute LONG-NAME.
Explanation: The attributes defined by this type do not have unique names.
OKWill always occurImported correctly
ID: 208 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
The XML-attribute LONG-NAME is used.
Explanation: The spec-relation-type has a name.
OKWill always occurImported correctly
The "work item linke role" definitions (corresponds to spec-relation-types) have to be created manually in Polation prior to the import. During the import the relation types must be mapped manually.
ID: 209 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
The XML-attribute LONG-NAME is not used.
Explanation: The spec-relation-type has no name.
WARNWill always occurSome data is lost, with warning
The "work item linke role" definitions (corresponds to spec-relation-types) have to be created manually in Polation prior to the import. During the import the relation types must be mapped manually. A "work item link role" must have a name.
ID: 210 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
The XML-attribute LONG-NAME contains ANSI characters.
Explanation: The name contains ANSI characters.
OKWill always occurImported correctly
ID: 211 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
The XML-attribute LONG-NAME contains Unicode characters.
Explanation: The name contains Unicode characters.
OKWill always occurImported correctly
ID: 212 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
The XML-attribute LONG-NAME is empty.
Explanation: The name of the spec-relation-type is an empty string.
WARNWill always occurSome data is lost, with warning
The "work item linke role" definitions (corresponds to spec-relation-types) have to be created manually in Polation prior to the import. During the import the relation types must be mapped manually. A "work item link role" must have a name.
ID: 213 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
The XML-attribute DESC is used.
CRITICALWill always occurSome data is lost, without warning
The content of the DESC attribute can not be imported, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 214 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
The XML-attribute DESC is not used.
OKWill always occurNot relevant
ID: 215 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
The XML-attribute DESC contains ANSI characters.
OKWill always occurNot relevant
ID: 216 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
The XML-attribute DESC contains Unicode characters.
OKWill always occurNot relevant
ID: 217 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
The XML-attribute DESC is empty.
OKWill always occurNot relevant
ID: 218 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
There are two or more SPEC-RELATION-TYPE elements contained in SPEC-TYPES with the same value for the XML-attribute LONG-NAME.
Explanation: The spec-relation-types do not have unique names.
OKWill always occurImported, with comment
The link types (corresponds to spec-relation-types) have to be created manually in Polation prior to the import. During the import the types must than be mapped manually.
ID: 219 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE /
A SPEC-RELATION-TYPE element is not referenced by any SPEC-RELATION element in the document.
Explanation: The spec-relation-type is not used.
OKWill always occurImported, with comment
The "work item linke role" definitions (corresponds to spec-relation-types) have to be created manually in Polation prior to the import. During the import the relation types must be mapped manually. It is possible to define a "work item link role" that is
ID: 227 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE / SPEC-ATTRIBUTES /
There is one or more AttributeDefinition element contained in SPEC-ATTRIBUTES.
Explanation: The type does define attributes.
CRITICALWill always occurSome data is lost, without warning
Relations cannot have attributes in Polarion.
ID: 228 REQ-IF-CONTENT / SPEC-TYPES / SPEC-RELATION-TYPE / SPEC-ATTRIBUTES /
There are two or more AttributeDefinition elements contained in SPEC-ATTRIBUTES with the same value for the XML-attribute LONG-NAME.
Explanation: The attributes defined by this type do not have unique names.
OKWill always occurImported, with comment
The work item types (corresponds to spec-object-types) have to be created manually in Polation prior to the import. During the import the types must than be mapped manually.
ID: 230 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
The XML-attribute LONG-NAME is used.
Explanation: The relation-groups-type has a name.
OKWill always occurNot relevant
ID: 231 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
The XML-attribute LONG-NAME is not used.
Explanation: The relation-groups-type has no name.
OKWill always occurNot relevant
ID: 232 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
The XML-attribute LONG-NAME contains ANSI characters.
Explanation: The name contains ANSI characters.
OKWill always occurNot relevant
ID: 233 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
The XML-attribute LONG-NAME contains Unicode characters.
Explanation: The name contains Unicode characters.
OKWill always occurNot relevant
ID: 234 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
The XML-attribute LONG-NAME is empty.
Explanation: The name of the relation-groups-type is an empty string.
OKWill always occurNot relevant
ID: 235 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
The XML-attribute DESC is used.
CRITICALWill always occurSome data is lost, without warning
The content of the DESC attribute can not be imported, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 236 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
The XML-attribute DESC is not used.
OKWill always occurNot relevant
ID: 237 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
The XML-attribute DESC contains ANSI characters.
OKWill always occurNot relevant
ID: 238 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
The XML-attribute DESC contains Unicode characters.
OKWill always occurNot relevant
ID: 239 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
The XML-attribute DESC is empty.
OKWill always occurNot relevant
ID: 240 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
There are two or more RELATION-GROUP-TYPE elements contained in SPEC-TYPES with the same value for the XML-attribute LONG-NAME.
Explanation: The relation-group-types do not have unique names.
OKWill always occurNot relevant
ID: 241 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE /
A RELATION-GROUP-TYPE element is not referenced by any RELATION-GROUP element in the document.
Explanation: The relation-group-type is not used.
OKWill always occurNot relevant
ID: 249 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE / SPEC-ATTRIBUTES /
There is one or more AttributeDefinition elements contained in SPEC-ATTRIBUTES.
Explanation: The type does define attributes.
OKWill always occurNot relevant
ID: 250 REQ-IF-CONTENT / SPEC-TYPES / RELATION-GROUP-TYPE / SPEC-ATTRIBUTES /
There are two or more AttributeDefinition elements contained in SPEC-ATTRIBUTES with the same value for the XML-attribute LONG-NAME.
Explanation: The attributes defined by this type do not have unique names.
OKWill always occurNot relevant
ID: 257 REQ-IF-CONTENT / DATATYPES /
A DatatypeDefinition element is not referenced by any AttributeDefinition element in the document.
Explanation: The DatatypeDefinition element is not used.
OKWill always occurNot relevant
DatatypeDefinition elements (DATATYPE-DEFINITION-* elements) cannot be imported. Only the build-in datatypes can be used.
ID: 258 REQ-IF-CONTENT / DATATYPES /
Two or more AttributeDefinition elements reference to the same DatatypeDefinition.
Explanation: The DatatypeDefinition element is used more than once.
OKWill always occurNot relevant
DatatypeDefinition elements (DATATYPE-DEFINITION-* elements) cannot be imported. Only the build-in datatypes can be used.
ID: 260 REQ-IF-CONTENT / DATATYPES /
Two or more SpecType elements of different types (SPECIFICATION-TYPE, SPEC-OBJECT-TYPE, SPEC-RELATION-TYPE or SPECIFIATION-GROUP-TYPE) reference to the same DatatypeDefinition.
OKWill always occurNot relevant
DatatypeDefinition elements (DATATYPE-DEFINITION-* elements) cannot be imported. Only the build-in datatypes can be used.
ID: 261 REQ-IF-CONTENT / DATATYPES /
Two or more SpecType elements of the same type (SPECIFICATION-TYPE, SPEC-OBJECT-TYPE, SPEC-RELATION-TYPE or SPECIFIATION-GROUP-TYPE) reference to the same DatatypeDefinition.
Explanation: The DatatypeDefinition element is used more than once, by one kind of SpecType elements (e.g. by SPEC-OBJECT-TYPE elements).
OKWill always occurNot relevant
DatatypeDefinition elements (DATATYPE-DEFINITION-* elements) cannot be imported. Only the build-in datatypes can be used.
ID: 274 REQ-IF-CONTENT / DATATYPES /
There are two or more DATATYPE-DEFINITION-* elements contained in DATATYPES with the same value for the XML-attribute LONG-NAME.
Explanation: Some datatypes share the same name.
OKWill always occurNot relevant
DATATYPE-DEFINITION-* elements cannot be imported, but Polarion preserves Datatype definitions in the ReqIF-file in roundtrips.
ID: 264 REQ-IF-CONTENT / DATATYPES /
A XML-attribute LONG-NAME in DATATYPE-DEFINITION-* is used.
Explanation: The datatype has a name.
OKWill always occurNot relevant
DATATYPE-DEFINITION-* elements cannot be imported, but Polarion preserves Datatype definitions in the ReqIF-file in roundtrips.
ID: 265 REQ-IF-CONTENT / DATATYPES /
A XML-attribute LONG-NAME in DATATYPE-DEFINITION-* is not used.
Explanation: The datatype has no name.
OKWill always occurNot relevant
DATATYPE-DEFINITION-* elements cannot be imported, but Polarion preserves Datatype definitions in the ReqIF-file in roundtrips.
ID: 266 REQ-IF-CONTENT / DATATYPES /
A XML-attribute LONG-NAME in DATATYPE-DEFINITION-*contains ANSI characters.
Explanation: The name contains ANSI characters.
OKWill always occurNot relevant
DATATYPE-DEFINITION-* elements cannot be imported, but Polarion preserves Datatype definitions in the ReqIF-file in roundtrips.
ID: 267 REQ-IF-CONTENT / DATATYPES /
A XML-attribute LONG-NAME in DATATYPE-DEFINITION-*contains Unicode characters.
Explanation: The name contains Unicode characters.
OKWill always occurNot relevant
DATATYPE-DEFINITION-* elements cannot be imported, but Polarion preserves Datatype definitions in the ReqIF-file in roundtrips.
ID: 268 REQ-IF-CONTENT / DATATYPES /
A XML-attribute LONG-NAME in DATATYPE-DEFINITION-* is empty.
Explanation: The name of the datatype is an empty string.
OKWill always occurNot relevant
DATATYPE-DEFINITION-* elements cannot be imported, but Polarion preserves Datatype definitions in the ReqIF-file in roundtrips.
ID: 269 REQ-IF-CONTENT / DATATYPES /
The XML-attribute DESC in DATATYPE-DEFINITION-* is used.
OKWill always occurNot relevant
ID: 270 REQ-IF-CONTENT / DATATYPES /
The XML-attribute DESC in DATATYPE-DEFINITION-*is not used.
OKWill always occurNot relevant
DATATYPE-DEFINITION-* elements cannot be imported, but Polarion preserves Datatype definitions in the ReqIF-file in roundtrips.
ID: 271 REQ-IF-CONTENT / DATATYPES /
The XML-attribute DESC in DATATYPE-DEFINITION-* contains ANSI characters.
OKWill always occurNot relevant
DATATYPE-DEFINITION-* elements cannot be imported, but Polarion preserves Datatype definitions in the ReqIF-file in roundtrips.
ID: 272 REQ-IF-CONTENT / DATATYPES /
The XML-attribute DESC in DATATYPE-DEFINITION-*contains Unicode characters.
OKWill always occurNot relevant
DATATYPE-DEFINITION-* elements cannot be imported, but Polarion preserves Datatype definitions in the ReqIF-file in roundtrips.
ID: 273 REQ-IF-CONTENT / DATATYPES /
The XML-attribute DESC in DATATYPE-DEFINITION-* is empty.
OKWill always occurNot relevant
DATATYPE-DEFINITION-* elements cannot be imported, but Polarion preserves Datatype definitions in the ReqIF-file in roundtrips.
ID: 263 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-BOOLEAN /
One or more DATATYPE-DEFINITION-BOOLEAN elements are contained in DATATYPES.
Explanation: The datatype "boolean "is used.
OKImported correctly
ID: 281 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-DATE /
One or more DATATYPE-DEFINITION-DATE elements are contained in DATATYPES.
Explanation: The datatype "date "is used.
OKWill always occurImported correctly
ID: 299 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-INTEGER /
One or more DATATYPE-DEFINITION-INTEGER elements are contained in DATATYPES.
Explanation: The datatype "integer "is used.
OKWill always occurImported correctly
ID: 3002 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-INTEGER /
The XML-attribute MIN is used.
Explanation: The integer datatype has a minimum value.
TAKE_CARESome data is lost, with warning
No range can be specified for an integer attribute.
ID: 3003 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-INTEGER /
The XML-attribute MAX is used.
Explanation: The integer datatype has a maximum value.
TAKE_CARESome data is lost, with warning
No range can be specified for an integer attribute.
ID: 317 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-REAL /
One or more DATATYPE-DEFINITION-REAL elements are contained in DATATYPES.
Explanation: The datatype "real "is used.
OKWill always occurImported correctly
ID: 3004 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-REAL /
The XML-attribute MIN is used.
Explanation: The real datatype has a minimum value.
TAKE_CARESome data is lost, with warning
No range can be specified for a real attribute.
ID: 3005 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-REAL /
The XML-attribute MAX is used.
Explanation: The real datatype has a maximum value.
TAKE_CARESome data is lost, with warning
No range can be specified for a real attribute.
ID: 335 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-STRING /
One or more DATATYPE-DEFINITION-STRING elements are contained in DATATYPES.
Explanation: The datatype "string "is used.
OKWill always occurImported correctly
ID: 371 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION /
One or more DATATYPE-DEFINITION-ENUMERATION elements are contained in DATATYPES.
Explanation: The datatype "enumeration "is used.
OKWill always occurImported correctly
ID: 389 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES /
The element SPECIFIED-VALUES is empty
Explanation: The enumeration element has no literals.
OKWill always occurImported correctly
ID: 3001 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
In case of a second export/import, the ReqIF-File contains a new enumeration literal, that has not existed in prior export/imports.
OKWill always occurImported, with comment
Literal needs to be added manual to datatype and mapped in Polarion first.
ID: 391 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
The XML-attribute LONG-NAME is used.
Explanation: The literal has a name.
OKWill always occurImported, with comment
Enumeration attributes have to be created manually prior to an initial ReqIF import.
ID: 392 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
The XML-attribute LONG-NAME is not used.
Explanation: The literal has no name.
WARNWill always occurSome data is lost, with warning
Enumeration attributes have to be created manually prior to an initial ReqIF import. Enumeration items must have a name.
ID: 393 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
The XML-attribute LONG-NAME contains ANSI characters.
Explanation: The name contains ANSI characters.
OKWill always occurImported correctly
ID: 394 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
The XML-attribute LONG-NAME contains Unicode characters.
Explanation: The name contains Unicode characters.
OKWill always occurImported correctly
ID: 395 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
The XML-attribute LONG-NAME is empty.
Explanation: The name of the literal is an empty string.
WARNWill always occurSome data is lost, with warning
Enumeration attributes have to be created manually prior to an initial ReqIF import. Enumeration items must have a name.
ID: 396 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
The XML-attribute DESC is used.
CRITICALWill always occurSome data is lost, without warning
The content of the DESC attribute can not be imported, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 397 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
The XML-attribute DESC is not used.
OKWill always occurNot relevant
ID: 398 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
The XML-attribute DESC contains ANSI characters.
OKWill always occurNot relevant
ID: 399 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
The XML-attribute DESC contains Unicode characters.
OKWill always occurNot relevant
ID: 400 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
The XML-attribute DESC is empty.
OKWill always occurNot relevant
ID: 401 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE /
There are two or more ENUM-VALUE elements contained in SPECIFIED-VALUES with the same value for the XML-attribute LONG-NAME.
Explanation: Two literals share the same name.
OKWill always occurImported correctly
ID: 742 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE / PROPERTIES / EMBEDDED-VALUE /
The XML-attribute KEY contains ANSI characters.
WARNWill always occurSome data is lost, with warning
This value is always a number in Polarion. Enumeration types have to be created manually in Polation prior to the import. During the import the types must than be mapped manually.
ID: 743 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE / PROPERTIES / EMBEDDED-VALUE /
The XML-attribute KEY contains Unicode characters.
WARNWill always occurSome data is lost, with warning
This value is always a number in Polarion. Enumeration types have to be created manually in Polation prior to the import. During the import the types must than be mapped manually.
ID: 744 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE / PROPERTIES / EMBEDDED-VALUE /
The XML-attribute KEY is empty.
Explanation: There value for "key" is an empty string.
WARNWill always occurSome data is lost, with warning
This value is always a number in Polarion. Enumeration types have to be created manually in Polation prior to the import. During the import the types must than be mapped manually.
ID: 409 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE / PROPERTIES / EMBEDDED-VALUE /
The XML-attribute OTHER-CONTENT contains ANSI characters.
OKWill always occurImported, with comment
Corresponds to the "Color" propertiy in Polarion.
ID: 410 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE / PROPERTIES / EMBEDDED-VALUE /
The XML-attribute OTHER-CONTENT contains Unicode characters.
OKWill always occurImported correctly
ID: 411 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE / PROPERTIES / EMBEDDED-VALUE /
The XML-attribute OTHER-CONTENT is empty.
Explanation: There value for "other-content" is an empty string.
OKWill always occurImported correctly
ID: 740 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE / PROPERTIES / EMBEDDED-VALUE /
There are two or more ENUM-VALUE elements contained in ENUM-VALUES, the have the value for the XML-Attribute KEY in their EMBEDDED-VALUE element.
Explanation: Two literals use the same value for KEY.
WARNWill always occurSome data is lost, with warning
This value is always a number in Polarion, that is unique within the enumeration. Enumeration types have to be created manually in Polation prior to the import. During the import the types must than be mapped manually.
ID: 741 REQ-IF-CONTENT / DATATYPES / DATATYPE-DEFINITION-ENUMERATION / SPECIFIED-VALUES / ENUM-VALUE / PROPERTIES / EMBEDDED-VALUE /
There are two or more ENUM-VALUE elements contained in ENUM-VALUES, the have the value for the XML-Attribute OTHER-CONTENT in their EMBEDDED-VALUE element.
Explanation: Two literals use the same value for OTHER-CONTENT.
OKWill always occurImported correctly
ID: 748 General-Attribute-Properties / SPEC-ATTRIBUTES /
The XML-attribute LONG-NAME in ATTRIBUTE-DEFINITION-* is used.
Explanation: The attribute has a name.
OKWill always occurImported correctly
ID: 749 General-Attribute-Properties / SPEC-ATTRIBUTES /
The XML-attribute LONG-NAME ATTRIBUTE-DEFINITION-* is not used.
Explanation: The attribute has no name.
WARNWill always occurSome data is lost, with warning
The custom fields for work items (corresponds to attribute-definition-* elements) have to be created manually in Polation prior to the import. During the import the types must than be mapped manually. In Polarion a custom field must have a name.
ID: 750 General-Attribute-Properties / SPEC-ATTRIBUTES /
The XML-attribute LONG-NAME ATTRIBUTE-DEFINITION-*contains ANSI characters.
Explanation: The name contains ANSI characters.
OKWill always occurImported correctly
ID: 751 General-Attribute-Properties / SPEC-ATTRIBUTES /
The XML-attribute LONG-NAME ATTRIBUTE-DEFINITION-*contains Unicode characters.
Explanation: The name contains Unicode characters.
OKWill always occurImported correctly
ID: 752 General-Attribute-Properties / SPEC-ATTRIBUTES /
The XML-attribute LONG-NAME ATTRIBUTE-DEFINITION-* is empty.
Explanation: The name of the attribute is an empty string.
WARNWill always occurSome data is lost, with warning
The custom fields for work items (corresponds to attribute-definition-* elements) have to be created manually in Polation prior to the import. During the import the types must than be mapped manually. In Polarion a custom field must have a name.
ID: 753 General-Attribute-Properties / SPEC-ATTRIBUTES /
The XML-attribute DESC ATTRIBUTE-DEFINITION-* is used.
OKWill always occurImported, with comment
The content of the DESC attribute can not be imported, but Polarion preserves the value in the ReqIF-file in roundtrips.
ID: 754 General-Attribute-Properties / SPEC-ATTRIBUTES /
The XML-attribute DESC ATTRIBUTE-DEFINITION-* is not used.
OKWill always occurImported correctly
ID: 755 General-Attribute-Properties / SPEC-ATTRIBUTES /
The XML-attribute DESC ATTRIBUTE-DEFINITION-*contains ANSI characters.
OKWill always occurNot relevant
ID: 756 General-Attribute-Properties / SPEC-ATTRIBUTES /
The XML-attribute DESC ATTRIBUTE-DEFINITION-* contains Unicode characters.
OKWill always occurNot relevant
ID: 757 General-Attribute-Properties / SPEC-ATTRIBUTES /
The XML-attribute DESC in ATTRIBUTE-DEFINITION-* is empty.
OKWill always occurNot relevant
ID: 758 General-Attribute-Properties / SPEC-ATTRIBUTES /
There are two or more ATTRIBUTE-DEFINITION-* elements contained in SPEC-ATTRIBUTES with the same value for the XML-attribute LONG-NAME.
Explanation: Some attributes share the same name.
OKWill always occurImported correctly
ID: 770 General-Attribute-Properties / SPEC-ATTRIBUTES / DEFAULT-VALUE /
The DEFAULT-VALUE in ATTRIBUTE-DEFINITION-*element is used.
Explanation: The attribute has a default value.
OKWill always occurImported correctly
ID: 771 General-Attribute-Properties / SPEC-ATTRIBUTES / DEFAULT-VALUE /
The DEFAULT-VALUE element in ATTRIBUTE-DEFINITION-* is not used.
Explanation: The attribute has no default value.
OKWill always occurImported correctly
ID: 773 General-Attribute-Properties / SPEC-ATTRIBUTES / ATTRIBUTE-DEFINITION-DATE /
One or more ATTRIBUTE-DEFINITION-DATE elements are contained in SPEC-ATTRIBUTES.
Explanation: The "date"-attribute is used.
OKWill always occurImported correctly
ID: 799 General-Attribute-Properties / SPEC-ATTRIBUTES / ATTRIBUTE-DEFINITION-INTEGER /
One or more ATTRIBUTE-DEFINITION-INTEGER elements are contained in SPEC-ATTRIBUTES.
Explanation: The "integer"-attribute is used.
OKWill always occurImported correctly
ID: 825 General-Attribute-Properties / SPEC-ATTRIBUTES / ATTRIBUTE-DEFINITION-REAL /
One or more ATTRIBUTE-DEFINITION-REAL elements are contained in SPEC-ATTRIBUTES.
Explanation: The "real"-attribute is used.
OKImported correctly
ID: 851 General-Attribute-Properties / SPEC-ATTRIBUTES / ATTRIBUTE-DEFINITION-STRING /
One or more ATTRIBUTE-DEFINITION-STRING elements are contained in SPEC-ATTRIBUTES.
Explanation: The "string"-attribute is used.
OKImported correctly
ID: 877 General-Attribute-Properties / SPEC-ATTRIBUTES / ATTRIBUTE-DEFINITION-XHTML /
One or more ATTRIBUTE-DEFINITION-XHTML elements are contained in SPEC-ATTRIBUTES.
Explanation: The XHTML-attribute is used.
OKImported correctly
ID: 747 General-Attribute-Properties / SPEC-ATTRIBUTES / ATTRIBUTE-DEFINITION-BOOLEAN /
One or more ATTRIBUTE-DEFINITION-BOOLEAN element is contained in SPEC-ATTRIBUTES.
Explanation: The "boolean"-attribute is used.
OKImported correctly
ID: 903 General-Attribute-Properties / SPEC-ATTRIBUTES / ATTRIBUTE-DEFINITION-ENUMERATION /
One or more ATTRIBUTE-DEFINITION-ENUMERATION elements are contained in SPEC-ATTRIBUTES.
Explanation: The enumeration-attribute is used.
OKImported correctly
ID: 918 General-Attribute-Properties / SPEC-ATTRIBUTES / ATTRIBUTE-DEFINITION-ENUMERATION /
The XML-attribute MULTI-VALUED is set to true.
Explanation: More than one value of the enumeration may be selected.
OKImported correctly
ID: 919 General-Attribute-Properties / SPEC-ATTRIBUTES / ATTRIBUTE-DEFINITION-ENUMERATION /
The XML-attribute MULTI-VALUED is set to false.
Explanation: It is not allowed to select more than one value of the enumeration.
OKImported correctly
ID: 1309 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML /
The XML-attribute IS-SIMPLIFIED is set to true.
Explanation: The element THE-VALUE contains a simplified version of the formatted string. The original formatted string is stored in the element THE-ORIGINAL-VALUE.
CRITICALWill always occurSome data is lost, without warning
The information is not imported.
ID: 1310 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML /
The XML-attribute IS-SIMPLIFIED is not used or set to false.
OKWill always occurImported correctly
ID: 1317 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <br>
Explanation: Contains the XHTML-tag <br> from Text Module: Forced line break
OKWill always occurImported correctly
ID: 1318 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <span>
Explanation: Contains the XHTML-tag <span> from Text Module: Generic language/style container
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1319 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <em>
Explanation: Contains the XHTML-tag <em> from Text Module: Indicates emphasis
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1320 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <strong>
Explanation: Contains the XHTML-tag <strong> from Text Module: Indicates stronger emphasis
OKWill always occurImported correctly
ID: 1321 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <dfn>
Explanation: Contains the XHTML-tag <dfn> from Text Module: Indicates that this is the defining instance of the enclosed term
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1322 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <code>
Explanation: Contains the XHTML-tag <code> from Text Module: Designates a fragment of computer code
OKWill always occurImported correctly
ID: 1323 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <q>
Explanation: Contains the XHTML-tag <q> from Text Module: Short inline quotation
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1324 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <samp>
Explanation: Contains the XHTML-tag <samp> from Text Module: Designates sample output from programs, scripts, etc.
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1325 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <kbd>
Explanation: Contains the XHTML-tag <kbd> from Text Module: Indicates text to be entered by the user
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1326 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <var>
Explanation: Contains the XHTML-tag <var> from Text Module: Indicates an instance of a variable or program argument
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1327 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <cite>
Explanation: Contains the XHTML-tag <cite> from Text Module: Contains a citation or a reference to other sources
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1328 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <abbr>
Explanation: Contains the XHTML-tag <abbr> from Text Module: Indicates an abbreviated form
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1329 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <acronym>
Explanation: Contains the XHTML-tag <acronym> from Text Module: Indicates an acronym
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1330 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <h1>, <h2>, <h3>, <h4>, <h5> or <h6>
Explanation: Contains the XHTML-tag <h1>, <h2>, <h3>, <h4>, <h5> or <h6> from Text Module: Heading
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting. A linebreak is added before the text.
ID: 1331 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <pre>
Explanation: Contains the XHTML-tag <pre> from Text Module: Preformatted text
CRITICALWill always occurSome data is lost, without warning
The text inside the tag is not imported! Instead a linebreak is added.
ID: 1332 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <blockquote>
Explanation: Contains the XHTML-tag <blockquote> from Text Module: Long quotation
OKWill always occurImported correctly
ID: 1333 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <address>
Explanation: Contains the XHTML-tag <address> from Text Module: Information on author
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1334 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <p>
Explanation: Contains the XHTML-tag <p> from Text Module: Paragraph
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting. A linebreak is added after the text.
ID: 1335 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <div>
Explanation: Contains the XHTML-tag <div> from Text Module: Generic language/style container
OKWill always occurImported correctly
A linebreak is added after the text.
ID: 1336 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <object>
Explanation: Contains the XHTML-tag <object> from Object Module: Generic embedded object
OKWill always occurNot relevant
ID: 1337 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <param>
Explanation: Contains the XHTML-tag <param> from Object Module: Named property value
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1338 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <tt>
Explanation: Contains the XHTML-tag <tt> from Presentation Module: Teletype or monospaced text style
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1339 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <i>
Explanation: Contains the XHTML-tag <i> from Presentation Module: Italic text style
OKWill always occurImported correctly
ID: 1340 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <b>
Explanation: Contains the XHTML-tag <b> from Presentation Module: Bold text style
OKWill always occurImported correctly
ID: 1341 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <big>
Explanation: Contains the XHTML-tag <big> from Presentation Module: Large text style
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1342 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <small>
Explanation: Contains the XHTML-tag <small> from Presentation Module: Small text style
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1343 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <sub>
Explanation: Contains the XHTML-tag <sub> from Presentation Module: Subscript
OKWill always occurImported correctly
ID: 1344 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <sup>
Explanation: Presentation Module: Superscript
OKWill always occurImported correctly
ID: 1345 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <hr>
Explanation: Presentation Module: Horizontal rule
OKWill always occurImported correctly
ID: 1346 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <ins>
Explanation: Edit Module: Inserted text
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1347 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <del>
Explanation: Edit Module: Deleted text
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1348 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <a>
Explanation: Hypertext Module: Anchor
OKWill always occurImported correctly
ID: 1349 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <ul>
Explanation: List Module: Unordered list
OKWill always occurImported correctly
ID: 1350 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <ol>
Explanation: List Module: Ordered list
OKWill always occurImported correctly
ID: 1351 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <dl>
Explanation: List Module: Definition list
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1352 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <li>
Explanation: List Module: List item
OKWill always occurImported correctly
ID: 1353 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <dt>
Explanation: List Module: Definition term
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1354 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <dd>
Explanation: List Module: Definition description
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1355 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <table>
Explanation: Basic Tables Module: Used to describe tables
OKWill always occurImported correctly
ID: 1356 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <caption>
Explanation: Basic Tables Module: Table caption
CRITICALWill always occurSome data is lost, without warning
Text is imported without formatting.
ID: 1357 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <tr>
Explanation: Basic Tables Module: Table row
OKWill always occurImported correctly
ID: 1358 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <th>
Explanation: Basic Tables Module: Table header cell
OKWill always occurImported correctly
ID: 1359 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the XHTML-tag <td>
Explanation: Basic Tables Module:Table data cell
OKWill always occurImported correctly
ID: 1314 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains an embedded object of type OLE, the specified MIME type is "application/oleobject".
Explanation: An <object> element, whose XML-attribute "type" (specifies the MIME-type) is "application/oleobject".
OKWill always occurImported, with comment
The preview image is shown. The OLE object cannot be opened, but it can be downloaded.
ID: 1366 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains an embedded object of type OLE, the specified MIME type is "application/x-oleobject".
Explanation: An <object> element, whose XML-attribute "type" (specifies the MIME-type) is "application/x-oleobject".
OKWill always occurImported, with comment
The preview image is shown. The OLE object cannot be opened, but it can be downloaded.
ID: 1315 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains an embedded object of type RTF, the specified MIME type is "text/rtf".
Explanation: An <object> element, whose XML-attribute "type" (specifies the MIME-type) is "text/rtf".
OKWill always occurImported correctly
ID: 1367 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains an embedded object of type RTF, the specified MIME type is "application/rtf".
Explanation: An <object> element, whose XML-attribute "type" (specifies the MIME-type) is "application/rtf".
OKWill always occurImported correctly
ID: 1368 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains an embedded object of type RTF, the specified MIME type is "application/x-rtf".
Explanation: An <object> element, whose XML-attribute "type" (specifies the MIME-type) is "application/x-rtf".
OKWill always occurImported correctly
ID: 1316 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains an embedded object of a type that is not OLE or RTF.
Explanation: An <object> element, whose XML-attribute "type" (specifies the MIME-type) is neither "application/oleobject" nor "text/rtf".
OKWill always occurImported correctly
ID: 1369 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains an embedded object of a file whose suffix is ".ole".
Explanation: An <object> element, that references to a file with the suffix ".ole".
OKWill always occurImported, with comment
The preview image is shown. The OLE object cannot be opened, but it can be downloaded.
ID: 1370 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains an embedded object of a file whose suffix is ".rtf".
Explanation: An <object> element, that references to a file with the suffix ".rtf".
OKWill always occurImported correctly
ID: 1371 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains an embedded object of a file whose suffix is neither ".ole" nor ".rtf".
Explanation: An <object> element, that references to a file whose suffix is neither ".ole" nor ".rtf".
OKWill always occurImported correctly
ID: 3006 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the Tag <span> with the XML-Attribut "style=color".
Explanation: Text ist marked as colored, using the Tag <span> in combination with the XML-Attribute "style=color". e.g.: <span style=color:#FF000>
OKImported correctly
ID: 3007 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the Tag <span> with the XML-Attribut "style=background-color".
Explanation: Text ist marked as having a background color, using the Tag <span> in combination with the XML-Attribute "style=background-color". e.g.: <span style=background-color:#FF000>
OKImported correctly
ID: 3008 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the Tag <span> with the XML-Attribut "style=font-size".
Explanation: The font size is set for text, using the Tag <span> in combination with the XML-Attribute "style=font-size". e.g.: <span style=font-size:10>
OKImported correctly
ID: 3009 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-XHTML / THE-VALUE / XHTML-CONTENT /
Contains the Tag <span> with the XML-Attribut "style=font-family".
Explanation: The font-family is set for text, using the Tag <span> in combination with the XML-Attribute "style=font-family". e.g.: <span style=font-family:Georgia, serif>
OKImported correctly
ID: 1364 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-ENUMERATION / VALUES /
There is no reference to an ENUM-VALUE element specified.
Explanation: No literal is selected.
OKWill always occurImported correctly
ID: 1365 General-Attribute-Properties / VALUES / ATTRIBUTE-VALUE-ENUMERATION / VALUES /
There are two or more references to ENUM-VALUE elements specified.
Explanation: More than one literal is selected.
CRITICALWill always occurSome data is lost, without warning
For an enumeration only a single value can be selected.