From: <tr...@do...> - 2013-02-22 19:26:43
|
<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>Support configurable culture for parsing and serializing literals</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.1</td> </tr> <tr> <td><b>Category:</b></td> <td>Core API</td> </tr> <tr> <td><b>Priority:</b></td> <td>High</td> </tr> <tr> <td><b>Type:</b></td> <td>Improvement</td> </tr> <tr> <td><b>Description:</b></td> </tr> <tr> <td colspan="2"><p> Currently dotNetRDF uses the invariant culture for parsing and serializing literals where appropriate. This is primarily required because the RDF and SPARQL specifications defer to XML Schema Datatypes for typed literal encodings which is heavily tied to invariant culture style encodings.</p> <p> </p> <p> However for some users it may be desireable to work with data in their culture throughout their system and so they would like to override this behaviour. This should be possible to add as a configurable option, note that this will be <b>user beware </b>because changing to a custom culture will often mean that data will not be fully interoperable with other standards compliant RDF and SPARQL software.</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=316" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=316</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> |