http://ontologydesignpatterns.org/index.php?action=history&feed=atom&title=Submissions_talk%3ATimeInterval 2026-04-29T14:54:34Z Revision history for this page on the wiki MediaWiki 1.25.6 http://ontologydesignpatterns.org/index.php?title=Submissions_talk:TimeInterval&diff=7568&oldid=prev 2010-02-25T10:03:51Z

<p></p> <table class='diff diff-contentalign-left'> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr style='vertical-align: top;'> <td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td> <td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 10:03, 25 February 2010</td> </tr><tr><td colspan="2" class="diff-lineno" id="L1" >Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class='diff-marker'>&#160;</td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>While I agree with the general points of and the need for a standardised way of describing how to model time and intervals of time, I am curious as to why the W3C standard time ontology is not used instead (http://www.w3.org/2006/time, described at http://www.w3.org/TR/owl-time/). It seems to me that using this standard would further interoperability more than reinventing the wheel by defining our own TimeInterval class and related properties, only for use within the ontologydesignpatterns.org pattern repository. Is there any particular reason as to why you've chosen to go this route?</div></td><td class='diff-marker'>&#160;</td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>While I agree with the general points of and the need for a standardised way of describing how to model time and intervals of time, I am curious as to why the W3C standard time ontology is not used instead (http://www.w3.org/2006/time, described at http://www.w3.org/TR/owl-time/). It seems to me that using this standard would further interoperability more than reinventing the wheel by defining our own TimeInterval class and related properties, only for use within the ontologydesignpatterns.org pattern repository. Is there any particular reason as to why you've chosen to go this route?</div></td></tr> <tr><td colspan="2">&#160;</td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2">&#160;</td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">/Karl Hammar</ins></div></td></tr> <tr><td colspan="2">&#160;</td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2">&#160;</td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">Having discussed with Eva Blomqvist, I now understand the origins of a lot of the ontologydesignpatterns.org patterns come from various upper level ontologies (DOLCE and DUL were mentioned), and if this is the case, it is of course natural that the way that time is modeled is also from one of these sources and therefore perhaps incompatible with the previously mentioned W3C Time ontology.</ins></div></td></tr> <tr><td colspan="2">&#160;</td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2">&#160;</td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">However, being interested in interoperability, I will when my current project is through look into creating some patterns that replicate the functions and features of the patterns in this repository, but use the W3C time classes instead. I think that a little bit of such unification could prove to be quite useful to the community.</ins></div></td></tr> <tr><td class='diff-marker'>&#160;</td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'>&#160;</td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr> <tr><td class='diff-marker'>&#160;</td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>/Karl Hammar</div></td><td class='diff-marker'>&#160;</td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>/Karl Hammar</div></td></tr> </table>

KarlHammar http://ontologydesignpatterns.org/index.php?title=Submissions_talk:TimeInterval&diff=7530&oldid=prev 2010-02-24T15:08:02Z

<p></p> <table class='diff diff-contentalign-left'> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr style='vertical-align: top;'> <td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td> <td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 15:08, 24 February 2010</td> </tr><tr><td colspan="2" class="diff-lineno" id="L1" >Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class='diff-marker'>&#160;</td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>While I agree with the general points of and the need for a standardised way of describing how to model time and intervals of time, I am curious as to why the W3C standard time ontology is not used instead (http://www.w3.org/2006/time, described at http://www.w3.org/TR/owl-time/). It seems to me that using this standard would further interoperability more than reinventing the wheel by defining our own TimeInterval class and related properties, only for use within the ontologydesignpatterns.org pattern repository. Is there any particular reason as to why you've chosen to go this route?</div></td><td class='diff-marker'>&#160;</td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>While I agree with the general points of and the need for a standardised way of describing how to model time and intervals of time, I am curious as to why the W3C standard time ontology is not used instead (http://www.w3.org/2006/time, described at http://www.w3.org/TR/owl-time/). It seems to me that using this standard would further interoperability more than reinventing the wheel by defining our own TimeInterval class and related properties, only for use within the ontologydesignpatterns.org pattern repository. Is there any particular reason as to why you've chosen to go this route?</div></td></tr> <tr><td colspan="2">&#160;</td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2">&#160;</td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">/Karl Hammar</ins></div></td></tr> </table>

KarlHammar http://ontologydesignpatterns.org/index.php?title=Submissions_talk:TimeInterval&diff=7529&oldid=prev 2010-02-24T15:07:24Z

<p>New page: While I agree with the general points of and the need for a standardised way of describing how to model time and intervals of time, I am curious as to why the W3C standard time ontology is...</p> <p><b>New page</b></p><div>While I agree with the general points of and the need for a standardised way of describing how to model time and intervals of time, I am curious as to why the W3C standard time ontology is not used instead (http://www.w3.org/2006/time, described at http://www.w3.org/TR/owl-time/). It seems to me that using this standard would further interoperability more than reinventing the wheel by defining our own TimeInterval class and related properties, only for use within the ontologydesignpatterns.org pattern repository. Is there any particular reason as to why you've chosen to go this route?</div>

KarlHammar