It's all about the answers!

Ask a question

403-Forbidden exception while importing reqif in 6.0.6 ifix009


Pavithra Shivalingappa (128219) | asked Jul 03 '19, 6:13 a.m.
Hi All,

    An exception occured while importing reqif file in DNG 606 ifix 009 server. Below is the exception details:

Could not create entry for _31f4392a-eb1e-4aef-a7c6-e0088cb4e6ff using service types; 403 Propagated exception; original message [ForbiddenException: CRRRS8601E You cannot change [http://www.w3.org/2002/07/owl#sameAs] to [http://xxxx/dng/attribute-data-values/abc_asil_levels/QM(B)].

What i understood from the exception is one of the rdf uri for a data type attribute contains special characters like "(" , ")", spaces. SO, while importing the reqif file it throws the above exception.

So, any idea on which all special characters are restricted while creating an rdf uri from 6.0.6 ifix009 ?
And also please share the link provided  by IBM if any regarding the special character restriction


Thanks in advance

Regards,
Pavithra S


<style> &amp;lt;!-- /* Font Definitions */ @font-face {font-family:&amp;quot;Cambria Math&amp;quot;; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:&amp;quot;Segoe UI&amp;quot;; panose-1:2 11 5 2 4 2 4 2 2 3;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin-top:0in; margin-right:0in; margin-bottom:8.0pt; margin-left:0in; line-height:107%; font-size:11.0pt; font-family:&amp;quot;Calibri&amp;quot;,sans-serif;} .MsoChpDefault {font-family:&amp;quot;Calibri&amp;quot;,sans-serif;} .MsoPapDefault {margin-bottom:8.0pt; line-height:107%;} /* Page Definitions */ @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --&amp;gt; </style>

Accepted answer


permanent link
Rakesh S (39112) | answered Jul 03 '19, 7:12 a.m.

Hi,
Error 403-Forbidden is the expected behaviour while importing the ReqIF in 6.0.6 ifix009 as the RDF uri for a data type attribute contains special characters.


"The RDF URI must contain valid characters and its format must comply with the RFC 3986 standard, for example, http://www.example.com/type1. The URI must not contain spaces, and the last character in the URI must be a letter or a number: it cannot be a punctuation mark or symbol.

Restrictions/Limitations:
1. The URI must not contain spaces.
2. The URI must not end in a trailing slash.
3. The last segment of the URI must not contain only numbers.
4. The last segment of the URI must not contain only non-alphabetical characters.
5. The final character of the URI must be a letter or a number except in the case of a hyphen, period, or underscore.



Pavithra Shivalingappa selected this answer as the correct answer

Comments
Pavithra Shivalingappa commented Jul 04 '19, 4:54 a.m.

How to handle existing rdf uri that already contains special characters?

Your answer


Register or to post your answer.


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.