From: <tr...@do...> - 2013-03-22 17:51:45
|
<p>The following issue has been added to a project that you are monitoring.</p> <table border="0"> <tr> <td width="90px" valign="top"><b>Title:</b></td> <td>Default Prefix may be incorrectly resolved in Turtle when the prefix is not defined but a Base URI is</td> </tr> <tr> <td><b>Project:</b></td> <td>Core Library (dotNetRDF.dll)</td> </tr> <tr> <td><b>Created By:</b></td> <td>Rob Vesse</td> </tr> <tr> <td><b>Milestone:</b></td> <td>1.0.0</td> </tr> <tr> <td><b>Category:</b></td> <td>Parsing</td> </tr> <tr> <td><b>Priority:</b></td> <td>High</td> </tr> <tr> <td><b>Type:</b></td> <td>Bug</td> </tr> <tr> <td><b>Description:</b></td> </tr> <tr> <td colspan="2"><p> This comes from an <a href="http://answers.semanticweb.com/questions/21733/turtle-dotnetrdf-base-vs-prefix">Answers question</a> and was something that Tom spotted.</p> <p> The behaviour is down to the fact that it would be correct in N3 which is a superset of Turtle and that the N3 and Turtle parsers share a QName resolution function.</p></td> </tr> </table> <p> More information on this issue can be found at <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=341" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=341</a></p> <p style="text-align:center;font-size:8pt;padding:5px;"> If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options. </p> |