Introduction

ReqIF based export / import operations may fail, if the content does not comply with ReqIF Specifications or XML Standard. Such failures are reported in the Export / Import Report. This document provides information about some of the commonly seen messages, and how to resolve them.

Error code - cvc-id.1

There is no ID/IDREF binding for IDREF

The error "cvc-id.1" in an XML file typically indicates a problem with the XML Schema Definition (XSD) or the XML document itself. The "cvc-id.1" error specifically relates to an issue with the ID or IDREF attribute in the XML document.

Use Case 1:

Exporting ReqIF definition may fail with schema validation related error.

Symptom:

Error exporting artifact: The given URI [https://:/rm/web/dojo/resources/blankgif][web] was not a recognized Fronting URI or Storage URI.

ReqIF ID XXXXXXXXX

URI https://:/rm/resources/BI_3wcYpoo1HMm2R8AxNeYV5A

OR

Exported file failed ReqIF schema validation. Reason(s) :

[Error] line: 217675 message: cvc-id.1: There is no ID/IDREF binding for IDREF '_58a4009d-d655-4956-805c-47216d2f236c'.

Error exporting artifact: The given URI [https://rtcdnggmcom:9443/rm/web/dojo/resources/blankgif][web] was not a recognised Fronting URI or Storage URI.

Cause:

This error mostly occurs when there are broken wrapper resources or malformed links to the artifacts. To identify the issue, navigate to the artifact mentioned in the error message https://:/rm/resources/BI_3wcYpoo1HMm2R8AxNeYV5A and then look for any broken wrapper resources or any malformed links.

Resolution

Simply navigate to the artifact mentioned in the error message, remove the malformed links/ broken wrapper resource and either re-add the link or if no longer needed, remove them. This should allow for successful export.

Use Case 2:

Symptom:

Exported file failed ReqIF schema validation. Reason(s) :

[Error] line: 363767 message: cvc-id.1: There is no ID/IDREF binding for IDREF '_9808a493-538d-4b20-868a-5b5b00b8e219'.

Export failed due to a violation of the ReqIF specification - modules and artifacts cannot use the same type. Please assure the following artifacts do not share types with any modules before exporting

Cause:

This error can also occur if any artifact in the module uses a type which has the same artifact format as the module type. For example, you may have a module called ‘Customer requirements’ of type “Specification” and inside the module, you have artifacts of type ‘Specification’. Though such usage of artifact types is not restricted within DNG, this is not complaint with the ReqIF standard.

Resolution:

The error can be fixed by manually modifying the type of the artifact to another type which has a text format.

Usecase-3:

Cause:

The export can also fail with no symptom with just the error message “Warning: Exported file failed ReqIF schema validation. Please refer to the report for details. "Exported file failed ReqIF schema validation. Reason(s) : [Error] line: 255585 message: cvc-id.1: There is no ID/IDREF binding for IDREF '_d989ce16-ff4a-4c96-9d22-1ee3f837a246'."

Resolution:

When there is no explanation included along with the error, we’ve seen this to be likely caused due to issue with module’s internal structure representation. Such module structure issues can be detected and also resolved using one of the internal debug tools – MAT (Module Analyse Tool). We recommend you use this tool to first analyze if such issues exist. If any issues are detected, contact IBM Support for further assistance. Follow the steps below to use MAT, to identify any potential problems:

Navigate to /rm/admin > Debug

Click on Modules

Choose the stream where the module exists.

Click on List modules.

Find the module that you are trying to export and click on Analyse.

Once the analyze is complete, save the results and share it in a support case and we will revert with the repair steps to fix the error.

Use Case 4:

Symptom:

Exported file failed ReqIF schema validation. Reason(s) : [Error] line: 225463 message: cvc-id.1: There is no ID/IDREF binding for IDREF '_c141357f-9ee3-4e8d-a800-f64f8ba0a527'.

Error exporting artifact: Propagated exception; original message [BadRequestException: com.ibm.rdm.fronting.server.exception.BadRequestException] 　　

ReqIF ID _584340ab-4e25-42e2-ae7d-004a8b26ebdd 　　

URI https:///rm/resources/BI_0U7jkSqmEe6_ErRiq0h3Vw

Cause:

This error is mostly seen when content of the artifact contains invalid hyperlinks

Steps to reproduce:

1. Create new module

2. Create a new Artifact in the module, write "https://(fqdn)/" in the body and save.

3. Create new ReqIF and add this module

4. Export created ReqIF

Resolution:

As per SPARQL 1.1 Query Language specification, The URI must comply with the RFC 3986 syntax which is the reason behind few special character are allowed or considered as safe.

Error code - cvc-attribute.3:

The CVC-attribute.3 error specifically indicates that an attribute value is not valid according to the defined data type in the XML Schema. This error occurs when the attribute value does not conform to the constraints specified in the schema, such as length, pattern, or enumeration.

Use Case 1:

Symptom:

The value '_bc191823-3ec1-4f79-a94e-9a10cdc2d491_EXPORTED_LAYOUT_DXL_04-V&VREQIFEXPORT_3' of attribute 'IDENTIFIER' on element 'ATTRIBUTE-DEFINITION-STRING' is not valid with respect to its type, 'ID'. [Fatal Error] line: 634 message: The reference to entity "VREQIFEXPORT_3" must end with the ';' delimiter.

Cause: -

When exporting specific DN Table, ReqIF fails schema validation fails

"Exported file failed ReqIF schema validation. Reason(s) : [Error] line: 1008 message: cvc-complex-type.2.4.b: The content of element 'table' is not complete. One of '{"http://www.w3.org/1999/xhtml":caption, "http://www.w3.org/1999/xhtml":col, "http://www.w3.org/1999/xhtml":colgroup, "http://www.w3.org/1999/xhtml":thead, "http://www.w3.org/1999/xhtml":tfoot, "http://www.w3.org/1999/xhtml":tbody, "http://www.w3.org/1999/xhtml":tr}' is expected."

Resolution:

there is a

This is not allowed according to the ReqIF Standard / ReqIF schema

This issue has been identified as a defect and is fixed in version 702 IFix031 / 703 IFix009 and future releases

Use Case 2:

Symptom:

"Exported file failed ReqIF schema validation. Reason(s) : [Error] line: 15375 message: cvc-id.2: There are multiple occurrences of ID value '_8407907c-b3e3-4c9c-a634-5aeacbe5c93f'. [Error] line: 15375 message: cvc-attribute.3: The value '_8407907c-b3e3-4c9c-a634-5aeacbe5c93f' of attribute 'IDENTIFIER' on element 'SPECIFICATION' is not valid with respect to its type, 'ID'."

Cause:

The problem is that the ReqIF definition has two occurrences of the same module, thus there are two SPECIFICATION elements having same ReqIF identifier. This is not allowed.

Resolution:

Removing the duplicate module entry from the ReqIF definition will fix the issue.

Use Case 3:

Symptom:

Error importing Artifact into module _c3f4b448-0073-4d74-8c42-13c608bcf988: cvc-attribute.3:

The value 'YPERLINK "https:///xx/item/19009009" Testing/ Development object'

of attribute 'href' on element 'a' is not valid with respect to its type, 'URI'. cvc-datatype-valid.1.2.1: 'YPERLINK

Cause:

The ReqIF files were exported from a third party tool which added many reqif-xhtml:a elements with empty href attribute in the defintion that is, href=""""

Resolution:

Removing the reqif-xhtml:a elements from the file will fix the issue.

Error Code: cvc-complex-type.2.3

The error “CVC-complex-type.2.3” is related to XML Schema validation. It indicates that there is an issue with the structure or content of a complex data type within an XML document, which does not conform to the expected format as defined by the schema.

Usecase 1:

Symptom:

Error importing Artifact into Module _c3827365-aca5-42bb-9066-3092904f3b63:

csv-complex-type.2.3: Element 'tbody' cannot have character [children], because the type's content type is element-only.

cvc-complex-type.2.3: Element 'tr' cannot have character [children], because the type's content type is element-only.

cvc-complex-type.2.3: Element 'table' cannot have character [children], because the type's content type is element-only.

Cause:

The issue is caused by unwanted spaces in the source

Resolution:

After removing unwanted spaces between HTML tags (

) artifacts will be successfully imported Error code: cvc-complex-type.2.4.a: The CVC-complex-type.2.4.a error code is related to XML Schema validation. It indicates that there is an issue with the structure or content of a complex data type within an XML document, specifically related to the sequence of child elements. Usecase 1: Symptom: While importing a reqIF , user could see the below error cvc-complex-type.2.4.a: Invalid content was found starting with element 'font'. One of '{"http://www.w3.org/1999/xhtml":a, "http://www.w3.org/1999/xhtml":br, "http://www.w3.org/1999/xhtml":span, "http://www.w3.org/1999/xhtml":bdo, "http://www.w3.org/1999/xhtml":map, "http://www.w3.org/1999/xhtml":object, "http://www.w3.org/1999/xhtml":img, "http://www.w3.org/1999/xhtml":u, "http://www.w3.org/1999/xhtml":tt, "http://www.w3.org/1999/xhtml":i, "http://www.w3.org/1999/xhtml":b, "http://www.w3.org/1999/xhtml":big, "http://www.w3.org/1999/xhtml":small, "http://www.w3.org/1999/xhtml":em, "http://www.w3.org/1999/xhtml":strong, "http://www.w3.org/1999/xhtml":dfn, "http://www.w3.org/1999/xhtml":code, "http://www.w3.org/1999/xhtml":q, "http://www.w3.org/1999/xhtml":samp, "http://www.w3.org/1999/xhtml":kbd, "http://www.w3.org/1999/xhtml":var, "http://www.w3.org/1999/xhtml":cite, "http://www.w3.org/1999/xhtml":abbr, "http://www.w3.org/1999/xhtml":acronym, "http://www.w3.org/1999/xhtml":sub, "http://www.w3.org/1999/xhtml":sup, "http://www.w3.org/1999/xhtml":input, "http://www.w3.org/1999/xhtml":select, "http://www.w3.org/1999/xhtml":textarea, "http://www.w3.org/1999/xhtml":label, "http://www.w3.org/1999/xhtml":button, "http://www.w3.org/1999/xhtml":ins, "http://www.w3.org/1999/xhtml":del}' is expected. Cause: This issue was because of incorrect usage of the font tag by third party tools which violates the XML standard. For example: SOME TEXT. Resolution: This issue has to be fixed by the third party tool so that the tags are correctly used as per the XML standard. As a temporary workaround , we can change it to instead which is inline with the standards. Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r8 | r6 < r5 < r4 < r3 | More topic actions... Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use. Please read the following disclaimer. Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.