From: <tr...@do...> - 2013-04-29 20:41:19
|
<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>RDF/XML parser should allow element names with xml: prefix</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>Unassigned</td> </tr> <tr> <td><b>Category:</b></td> <td>Parsing</td> </tr> <tr> <td><b>Priority:</b></td> <td>Normal</td> </tr> <tr> <td><b>Type:</b></td> <td>Bug</td> </tr> <tr> <td><b>Description:</b></td> </tr> <tr> <td colspan="2"><p> A StackOverflow question highlighted a bug in the RDF/XML parser - http://stackoverflow.com/questions/16285690/unable-to-parse-this-rdf-xml-since-system-xml-was-unable-to-parse-the-document</p> <p> The bug is that element names in the XML namespace should be allowed where currently there are not, the fix should be relatively trivial since we simply need to always define the xml namespace at the start of parsing</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=358" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=358</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> |