[dotNetRDF-Develop] Issue CORE-365 has a new comment

[<tr...@do...>]

<p>A new comment has been added to the following issue.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Datetime comparison on different time-zones</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>Date:</b></td>
    <td>2013-06-19 06:35 PM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	I have looked at this at a bit and I know why I did this originally (the specs say that dates with timezones and those without are incomparable) but clearly this check is over-zealous wrt this. &nbsp;However the more I look at this the more it looks like we may need to abandon use of DateTimeOffset and move back to DateTime because DateTimeOffset does not allow us to distinguish between dates without timezones and those with time zones.</p>
<p>
	Parsing an XML date time without any time zone information results in a DateTimeOffset which is indistinguishable from one using the Z or 0 offset. &nbsp;Really we need to be using DateTime and inspecting Kind as appropriate in order to properly rectify this issue.</p>
<p>
	This makes this a non-trivial refactor since it requires a breaking change to the IValuedNode APIs and all the machinery around evaluating date time operations in SPARQL.</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=365" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=365</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>