discontinued / server · Files

index.html 104 KB
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
    "http://www.w3.org/TR/REC-html40/loose.dtd">
<HTML>
<HEAD><TITLE>Time Ontology in OWL</TITLE>
<STYLE type=text/css>.inlineCode {
	FONT-FAMILY: "courier new"; BACKGROUND-COLOR: #ddf
}
PRE.code {
	BORDER-RIGHT: #999999 1pt solid; PADDING-RIGHT: 0.5em; BORDER-TOP: #999999 1pt solid; PADDING-LEFT: 0.5em; PADDING-BOTTOM: 0.5em; BORDER-LEFT: #999999 1pt solid; PADDING-TOP: 0.5em; BORDER-BOTTOM: #999999 1pt solid; FONT-FAMILY: "courier new"; BACKGROUND-COLOR: #eef
}
PRE.code2 {
	BORDER-RIGHT: #999999 1pt solid; PADDING-RIGHT: 0.5em; BORDER-TOP: #999999 1pt solid; PADDING-LEFT: 0.5em; PADDING-BOTTOM: 0.5em; BORDER-LEFT: #999999 1pt solid; PADDING-TOP: 0.5em; BORDER-BOTTOM: #999999 1pt solid; FONT-FAMILY: "courier new"; BACKGROUND-COLOR: #ffa
}
.ednote {
	FONT-STYLE: italic
}
PRE.clientmsg {
	BORDER-RIGHT: #999 1px solid; PADDING-RIGHT: 2px; BORDER-TOP: #999 1px solid; PADDING-LEFT: 2px; BACKGROUND: #eee; PADDING-BOTTOM: 2px; MARGIN: 0px; BORDER-LEFT: #999 1px solid; PADDING-TOP: 2px; BORDER-BOTTOM: #999 1px solid
}
PRE.servermsg {
	BORDER-RIGHT: #999 1px solid; PADDING-RIGHT: 2px; BORDER-TOP: #999 1px solid; PADDING-LEFT: 2px; BACKGROUND: #eee; PADDING-BOTTOM: 2px; MARGIN: 5px 0px 0px; BORDER-LEFT: #999 1px solid; PADDING-TOP: 2px; BORDER-BOTTOM: #999 1px solid; TEXT-ALIGN: left
}
P.msg {
	PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px; TEXT-ALIGN: center
}
DIV.interaction {
	BORDER-RIGHT: #999 1px solid; PADDING-RIGHT: 5px; BORDER-TOP: #999 1px solid; PADDING-LEFT: 5px; PADDING-BOTTOM: 5px; BORDER-LEFT: #999 1px solid; PADDING-TOP: 5px; BORDER-BOTTOM: #999 1px solid
}
DIV.interaction H4 {
	MARGIN: 0px 0px 10px
}
DIV.interaction P {
	MARGIN: 0px
}
DIV.test {
	BORDER-RIGHT: #999 1px solid; PADDING-RIGHT: 5px; BORDER-TOP: #999 1px solid; PADDING-LEFT: 5px; PADDING-BOTTOM: 5px; BORDER-LEFT: #999 1px solid; PADDING-TOP: 5px; BORDER-BOTTOM: #999 1px solid
}
DIV.test H4 {
	MARGIN: 0px 0px 10px
}
</STYLE>
<LINK 
href="http://www.w3.org/StyleSheets/TR/W3C-WD" 
type="text/css" rel="stylesheet">
</HEAD>
<BODY>
<DIV class=head><A href="http://www.w3.org/"><IMG height=48 alt=W3C 
src="http://www.w3.org/Icons/w3c_home" width=72></A> 
<H1>Time Ontology in OWL <BR></H1>
<H2>W3C Working Draft 27 September 2006</H2>
<DL>
  <DT>This version: 
  <DD>
  <a href="http://www.w3.org/TR/2006/WD-owl-time-20060927/"
   >http://www.w3.org/TR/2006/WD-owl-time-20060927/</a>
<DT>Latest version: 
  <DD><A 
  href="http://www.w3.org/TR/owl-time">http://www.w3.org/TR/owl-time</A> 

  <DT>Previous versions: 
  <DD>(this is the first public version)
  <DT>Editors: 
  <DD><A href="http://www.isi.edu/~hobbs/">Jerry R. Hobbs</A>, University of 
  Southern California / Information Sciences Institute<BR><A 
  href="http://www.isi.edu/~pan/">Feng Pan</A>, University of Southern 
  California / Information Sciences Institute&nbsp; </DD></DL>

<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2006 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>

<HR>
</DIV><!-- end of head -->
<H2 class=notoc><A id=abstract name=abstract>Abstract</A></H2>
<P>This document presents an ontology of temporal concepts, OWL-Time (formerly 
DAML-Time) [<a href="#ref-4">4</a>,<a href="#ref-10">10</a>], 
for describing the temporal content of Web pages and the temporal properties of 
Web services. The ontology provides a vocabulary for expressing facts about 
topological relations among instants and intervals, together with information 
about durations, and about datetime information. We also demonstrate in detail, 
using the Congo.com and Bravo Air examples from OWL-S [<a href="#ref-11">11</a>], 
how this time ontology can be used to support OWL-S, including use cases for defining input parameters and (conditional) output parameters. A use case for 
meeting scheduling is also shown. In the appendix we also describe a time zone 
resource in OWL we developed for not only the US but also the entire world, 
including the time zone ontology, the US time zone instances, and the world time 
zone instances. <BR></P>
<H2 id=Status>Status of this Document</H2>
<P><EM>This section describes the status of this document at the time of its 
publication. Other documents may supersede this document. A list of current W3C 
publications and the latest revision of this technical report can be found in 
the <A href="http://www.w3.org/TR/">W3C technical reports index</A> at 
http://www.w3.org/TR/.</EM></P>
<P>This document was prepared by the 
<a href="http://www.w3.org/2001/sw/BestPractices/OEP/">Ontology Engineering and 
Patterns Task Force</a> of the <A href="http://www.w3.org/2001/sw/BestPractices/">Semantic Web 
Best Practices and Deployment Working Group</A> (SWBPD). This work is part of 
the <A href="http://www.w3.org/2001/sw/Activity">W3C Semantic Web 
Activity</A>.</P>

<P>This document is a W3C First Public Working Draft published to solicit 
comments from interested parties. This Working Draft is not expected to
become a W3C Recommendation.  Comments on this document are
encouraged and may be sent to <A 
href="mailto:public-swbp-wg@w3.org">public-swbp-wg@w3.org</A>; please include 
the text "comment" in the subject line. All messages received at this address 
are viewable in a <A 
href="http://lists.w3.org/Archives/Public/public-swbp-wg/">public archive</A>. 

<P>At the time of publication the charter of the Semantic Web Best
Practices and Deployment Working Group is expiring.  A new Working
Group, the <A href="http://www.w3.org/2006/07/SWD/">Semantic Web Deployment</A>
(SWD) Working Group, is commencing.
The charter of the SWD Working Group permits it to choose to take up this
document and consider further work.  At the time of publication
no decision has been made by the SWD Working Group regarding further
work in this area.</P>
 
<P>This document was produced by a group operating under the <A 
href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C 
Patent Policy</A>. 
The group does not expect this document to become a W3C Recommendation.
W3C maintains a <A 
href="http://www.w3.org/2004/01/pp-impl/35495/status">public list of any patent 
disclosures</A> made in connection with the deliverables of the group;
that page also includes instructions for disclosing a patent.
An individual who has actual knowledge of a patent which the individual
believes contains
<A href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential"
>Essential Claim(s)</A> must disclose the information in
accordance with
<A href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure"
>section 6</A> of the W3C Patent Policy.</P>

<P>Publication as a Working Draft does not imply endorsement by the W3C 
Membership. This is a draft document and may be updated, replaced or obsoleted 
by other documents at any time. It is inappropriate to cite this document as 
other than work in progress.</P>
<H2 id=toc>Table of Contents</H2>
<OL>
  <LI><A 
  href="#general">General 
  issues</A> 
  <LI><A 
  href="#examples">Use 
  case examples</A> 
  <LI><A 
  href="#syntax">Syntax 
  for code</A> 
  <LI><A 
  href="#relations">Topological 
  Temporal Relations</A> 
  <LI><A 
  href="#duration">Duration 
  Description</A> 
  <LI><A 
  href="#timezones">Time 
  Zones</A> 
  <LI><A 
  href="#calclock">DateTime 
  Description</A>
	<LI><A 
  href="#ref-time-in-owl-s">Use 
  Cases for Web Services</A>
	<OL>
		<LI><A 
    href="#input">Use 
    Cases for Input Parameters</A>
		<LI><A 
    href="#output">Use 
    Cases for (Conditional) Output Parameters</A> </LI>
	</OL>
	<LI><A 
  href="#scheduling">A 
  Use Case for Scheduling</A>
	<LI><a href="#summary">Appendix A. Summary of Classes and Properties in the Time Ontology </a> </LI>
	<LI><a href="#timezone">Appendix B. Time Zone Resource in OWL</a> </LI>
	<LI><A 
  href="#references">References</A>
	<LI><a href="#ack">Acknowledgments</a></OL>
<HR>

<H2><A name=general></A>General issues</H2>
<P>Temporal information is so common that it’s hard to find a real world Web 
service without it. For example, whenever you place an online order, the order 
date is always part of your order. When you reserve a car at a car rental site, 
you have to specify the dates you need it. In response to this need, a temporal 
ontology, OWL-Time (formerly DAML-Time), has been developed for describing the 
temporal content of Web pages and the temporal properties of Web services. Its 
development is being informed by temporal ontologies developed at a number of 
sites and is intended to capture the essential features of all of them and make 
them and their associated resources easily available to a large group of Web 
developers and users.&nbsp;Although it can be used independently, we have made 
sure it works well with OWL-S. Advantages of OWL-Time over XML Schema datatype 
<CODE>duration</CODE> and <CODE>dateTime</CODE> will be discussed.</P>
<P>This document only presents the OWL encodings of the ontology. For a 
first-order logic axiomatization of the ontology, see [<a href="#ref-4">4</a>,<a href="#ref-10">10</a>]. 
In an extension of the time ontology [<a href="#ref-5">5</a>,<a href="#ref-9">9</a>], 
we also allow temporal predicates to apply directly to events, should the user 
wish, but here we restrict our treatment to temporal entities. </P>
<H2><A name=examples></A>Use case examples</H2>
<P>A simple use case example: "Suppose someone has a telecon scheduled for 
6:00pm EST on November 5, 2006. You would like to make an appointment with him 
for 2:00pm PST on the same day, and expect the meeting to last 45 minutes.&nbsp; 
Will there be an overlap?" In this use case we can specify the facts about the 
telecon and the meeting using our ontology in OWL that will allow a temporal 
reasoner to determine whether there is a conflict. See [<A 
href="#scheduling">A 
Use Case for Scheduling</A>] section for details.</P>
<P>More examples: "Someone who does a Web search trying to find a place to buy a 
book needed before next Tuesday may or may not be able to use an online 
bookstore that promises delivery within five business days." </P>
<P>"Someone doing a genealogical search may want to specify that the birthdate 
of a person is between 15 and 45 years before a known marriage date."</P>
<P>More use case examples will be described in detail in [<A 
href="#ref-time-in-owl-s">Use 
Cases for Web Services</A>] section below. </P>
<H2 id=codesyntax><A name=syntax></A>Syntax for code</H2>
<P>In keeping with SWBP policy, the code within the body of the note is in N3. 
Most of the code was generated by Prot&eacute;g&eacute; from the original OWL code in RDF/XML. 
Details in alternative syntaxes are given by links.</P>
<HR>

<H2><A name=relations></A>Topological Temporal Relations</H2>
<P>There are two subclasses of <CODE>TemporalEntity</CODE>: <CODE>Instant</CODE> 
and <CODE>Interval</CODE>, and they are the only two subclasses of 
<CODE>TemporalEntity</CODE>:</P><PRE>:Instant
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; owl:Class ;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rdfs:subClassOf :TemporalEntity .</PRE><PRE>:Interval
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; owl:Class ;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rdfs:subClassOf :TemporalEntity .</PRE><PRE>:TemporalEntity
      a       owl:Class ;
      rdfs:subClassOf :TemporalThing ;
      owl:equivalentClass
              [ a       owl:Class ;
                owl:unionOf (:Instant :Interval)
              ] .</PRE>
<P>Intervals are, intuitively, things with extent and instants are, intuitively, 
point-like in that they have no interior points. It is generally safe to think 
of an instant as an interval with zero length, where the beginning and end are 
the same.</P>
<P><CODE>hasBeginning</CODE> and <CODE>hasEnd</CODE> are relations between 
instants and temporal entities, and the beginnings and ends of temporal 
entities, if they exist, are unique. In some approach to infinite intervals, a 
positively infinite interval has no end, and a negatively infinite interval has 
no beginning. Hence, we use the relations <CODE>hasBeginning</CODE> and 
<CODE>hasEnd</CODE> in the ontology, rather than defining functions 
<CODE>beginningOf</CODE> and <CODE>endOf</CODE>, since the functions would not 
be total. <CODE>hasBeginning</CODE>, for example, can be specified as:</P><PRE>:hasBeginning
      a       owl:ObjectProperty ;
      rdfs:domain :TemporalEntity ;
      rdfs:range :Instant .</PRE>
<P><CODE>inside</CODE> is a relation between an instant and an interval, and it 
is not intended to include beginnings and ends of intervals.&nbsp;There is a 
<CODE>before</CODE> relation on temporal entities, which gives directionality to 
time. If a temporal entity <CODE>T<SUB>1</SUB></CODE> is before another temporal 
entity <CODE>T<SUB>2</SUB></CODE>, then the end of <CODE>T<SUB>1</SUB></CODE> is 
before the beginning of <CODE>T<SUB>2</SUB></CODE>. Thus, before can be 
considered to be basic to instants and derived for intervals.&nbsp;</P>
<P>Allen and Furgerson [<A 
href="#ref-1">1</A>,<A 
href="#ref-2">2</A>] 
have developed a calculus of binary relations on intervals (e.g., meets, 
overlaps) for representing qualitative temporal information and address the 
problem of reasoning about such information. The relations between intervals 
defined in their calculus can be defined in a relatively straightforward fashion 
in terms of <CODE>before</CODE> and identity on the beginning and end points. 
The standard interval calculus assumes all intervals are proper, and we do that 
here too. Proper intervals are ones whose beginning and end are different. It 
can be specified as:</P><PRE>:ProperInterval
      a       owl:Class ;
      rdfs:subClassOf :Interval ;
      owl:disjointWith :Instant .</PRE>
<P>OWL-Time provides the interval relations: <CODE>intervalEquals</CODE>, 
<CODE>intervalBefore</CODE>, <CODE>intervalMeets</CODE>, 
<CODE>intervalOverlaps</CODE>, <CODE>intervalStarts</CODE>, 
<CODE>intervalDuring</CODE>, <CODE>intervalFinishes</CODE>, and their reverse 
interval relations: <CODE>intervalAfter</CODE>, <CODE>intervalMetBy</CODE>, 
<CODE>intervalOverlappedBy</CODE>, <CODE>intervalStartedBy</CODE>, 
<CODE>intervalContains</CODE>, <CODE>intervalFinishedBy</CODE>. For example, the 
specification of <CODE>intervalEquals</CODE> is:</P><PRE>:<CODE>interval</CODE>Equals
      a       owl:ObjectProperty ;
      rdfs:domain :ProperInterval ;
      rdfs:range :ProperInterval .</PRE>
<H2><A name=duration></A>Duration Description</H2>
<P>The duration of an interval (or temporal sequence) can have many different 
descriptions. An interval can be 1 day 2 hours, or 26 hours, or 1560 minutes, 
and so on. It is useful to be able to talk about these descriptions in a 
convenient way as independent objects, and to talk about their equivalences. We 
do this first in terms of a predicate called <CODE>durationOf</CODE> that takes 
eight arguments, one for a temporal thing, and one each for years, months, 
weeks, days, hours, minutes, and seconds. Then we will define a specific kind of 
individual called a "duration description", together with a number of functions 
relating the duration description to the values of each of the eight arguments. 
Thereby we convert the 8-ary predicate <CODE>durationOf</CODE> into eight binary 
relations that are more convenient for description logic-based markup languages, 
such as OWL:</P><PRE>:DurationDescription
      a       owl:Class ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :seconds
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :minutes
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :hours
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :days
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :weeks
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :months
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :years
              ] .</PRE>
<P>An interval can have multiple duration descriptions (e.g., 2 days, 48 hours), 
but can only have one duration. </P>
<P>We use two different sets of properties for <CODE>DateTimeDescription</CODE> 
and <CODE>DurationDescription</CODE>, because their ranges are different. For 
example, <CODE>year</CODE> (in <CODE>DateTimeDescription</CODE>) has a range of 
<CODE>xsd:gYear</CODE>, while <CODE>years</CODE> (in 
<CODE>DurationDescription</CODE>) has a range of <CODE>xsd:decimal</CODE> so 
that you can say duration of 2.5 years.</P>
<P>iCalendar [<a href="#ref-3">3</a>] 
is a widely supported standard for personal data interchange. It provides the 
definition of a common format for openly exchanging calendaring and scheduling 
information across the Internet. The representation of temporal concepts in this 
time ontology can be straightforwardly mapped to iCalendar. For example, 
duration of 15 days, 5 hours and 20 seconds is represented in iCalendar as 
P15DT5H0M20S, which can be represented in the time ontology as:</P><PRE>:duration
      a       :DurationDescription ;
      :seconds 20 ;
      :hours 5 ;
      :days 15 .
</PRE>
<P><A name=ref-duration></A>The relation <CODE>hasDurationDescription</CODE> is 
used to specify a duration description for a temporal entity:</P><PRE>:hasDurationDescription
      a       owl:ObjectProperty ;
      rdfs:domain :TemporalEntity ;
      rdfs:range :DurationDescription .</PRE>
<P>Other duration concepts can be straightforwardly defined. For example, 
duration "Year" can be defined as a subclass of "DurationDescription" with the 
restrictions that the "years" property is required (with "cardinality" of 1) and 
all other properties (e.g., "hours", "months") should not be present (with 
"cardinality" of 0):<BR><PRE>:Year
      a       owl:Class ;
      rdfs:subClassOf :DurationDescription ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:cardinality 1 ;
                owl:onProperty :years
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:cardinality 0 ;
                owl:onProperty :months
              ] ;
      ...

      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:cardinality 0 ;
                owl:onProperty :seconds
              ] .
</PRE>Here we use "cardinality = 0" instead of restricting the values of days, 
etc. to 0. The reason is that using "cardinality = 0" means all those 
properties/fields (days, etc.) should not be specified (i.e., the granularity is 
"year"), while restricting all those values to 0 means they all have a fixed 
value of 0 (i.e., x years 0 months 0 days ...) and the granularity is actually 
"second", which is not the correct semantics of "year".
<P>It's worth pointing out that there is a distinction between a year as a 
duration and a calendar year. The year from December 22, 2006 to December 21, 
2007 is the former but not the latter.</P>
<P></P>
<H2><A name=timezones></A>Time Zones</H2>
<P>What hour of the day an instant is in is relative to the time zone. This is 
also true of minutes, since there are regions in the world, e.g., central 
Australia, where the hours are not aligned with UTC hours, but are, e.g., offset 
half an hour. Seconds are not relative to the time zone.</P>
<P>Days, weeks, months and years are also relative to the time zone, since, 
e.g., 2006 began in the Eastern Standard time zone three hours before it began 
in the Pacific Standard time zone. Thus, predications about all datetime 
intervals except seconds are relative to a time zone. </P>
<P>We have been referring to time zones, but in fact it is more convenient to 
work in terms of what we might call the "time standard" that is used in a time 
zone. That is, it is better to work with the Pacific Standard Time (PST) as a 
legal entity than with the PST zone as a geographical region. A time standard is 
a way of computing the time, relative to a world-wide system of computing time. 
For each time standard, there is a zone, or geographical region, and a time of 
the year in which it is used for describing local times. Where and when a time 
standard is used have to be axiomatized, and this involves interrelating a time 
ontology and a geographical ontology. These relations can be quite complex. Only 
the entities like PST and EDT, the time standards, are part of the time 
ontology.</P>
<P>If we were to conflate time zones (i.e., geographical regions) and time 
standards, it would likely result in problems in several situations. For 
example, the Eastern Standard zone and the Eastern Daylight zone are not 
identical, since most of Indiana was on Eastern Standard time all year. The state 
of Arizona and the Navajo Indian Reservation, two overlapping geopolitical 
regions, have different time standards during the daylight saving times -- one 
is Pacific and the other is Mountain.</P>
<P>Time standards that seem equivalent, like Eastern Standard and Central 
Daylight, should be thought of as separate entities. Whereas they function the 
same in the time ontology, they do not function the same in the ontology that 
articulates time and geography. For example, it would be false to say those 
parts of Indiana shifted in April from Eastern Standard to Central Daylight 
time.</P>
<P>See [<a href="#timezone">Appendix B</a>] for the details about a 
time zone resource we developed in OWL. </P>
<H2><A name=calclock></A>DateTime Description</H2>
<P>A datetime description has the following properties/fields: 
<CODE>unitType</CODE>, <CODE>year</CODE>, <CODE>month</CODE>, <CODE>week</CODE>, 
<CODE>day</CODE>, <CODE>dayOfWeek</CODE>, <CODE>dayOfYear</CODE>, 
<CODE>hour</CODE>, <CODE>minute</CODE>, <CODE>second</CODE>, and 
<CODE>timeZone</CODE>. The property <CODE>unitType</CODE> specifies the temporal 
unit type of the datetime description, and its domain is 
<CODE>TemporalUnit</CODE>:</P><PRE>:TemporalUnit
      a       owl:Class ;
      owl:equivalentClass
              [ a       owl:Class ;
                owl:oneOf (:unitSecond :unitMinute :unitHour :unitDay :unitWeek :unitMonth :unitYear)
              ] .
</PRE>
<P>For example, the temporal unit type of 10:30 is minute 
(<CODE>unitMinute</CODE>), and the temporal unit type of March 20, 2006 is day 
(<CODE>unitDay</CODE>). The unit type is required. With a given temporal unit 
type, all the fields/properties for smaller units will be ignored. For instance, 
if the temporal unit type is day (<CODE>unitDay</CODE>), the values of the 
field/property hour, minute, and second, if present, will be ignored. Since 
datetime description is for describing datetime intervals, we defined a 
property, called <CODE>hasDateTimeDescription</CODE> with 
<CODE>DateTimeDescription</CODE> as the range, for datetime intervals. To 
represent "March 12 in 2006", for example, using datetime description, we need 
an instance of <CODE>DateTimeDescription</CODE> that has values only for 
<CODE>unitType</CODE>(<CODE>unitDay</CODE>), <CODE>year</CODE>(2006), 
<CODE>month</CODE>(3), and <CODE>day</CODE>(12). 
<CODE>DateTimeDescription</CODE> and <CODE>hasDateTimeDescription</CODE> are 
defined in OWL as:</P><PRE>:DateTimeDescription
      a       owl:Class ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:cardinality 1 ;
                owl:onProperty :unitType
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :second
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :minute
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :hour
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :day
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :dayOfWeek
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :dayOfYear
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :week
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :month
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :year
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :timeZone
              ] .
              
:hasDateTimeDescription
      a       owl:ObjectProperty ;
      rdfs:domain :DateTimeInterval ;
      rdfs:range :DateTimeDescription .
</PRE>
<P><CODE>DateTimeInterval</CODE> is a subclass of <CODE>ProperInterval</CODE>. 
Any <CODE>TemporalEntity</CODE> has a duration, but only 
<CODE>DateTimeInterval</CODE> can have <CODE>DateTimeDescription</CODE> (e.g., 
May 8 has a <CODE>DateTimeDescription</CODE>, but the interval from 1:30pm, May 
8, to 1:30pm, May 9, does not. Both have a duration of a day. A 
<CODE>DateTimeDescription</CODE> is always a description of an interval 
(<CODE>DateTimeInterval</CODE>), not an instant, which can be described 
by&nbsp;<CODE>inDateTime</CODE> and <CODE>inXSDDateTime</CODE>, as described 
later in the section.
<P>The domain of the property <CODE>dayOfWeek</CODE> is the class 
<CODE>DayOfWeek</CODE>:<PRE>:DayOfWeek
      a       owl:Class ;
      owl:equivalentClass
              [ a       owl:Class ;
                owl:oneOf (:Sunday :Monday :Tuesday :Wednesday :Thursday :Friday :Saturday)
              ] .
</PRE>
<P><A name=calclock></A>Other datetime concepts can be straightforwardly defined. 
For example, "January" can be defined as a a subclass of 
<CODE>DateTimeDescription</CODE> with the restrictions that the 
<CODE>unitType</CODE> property has <CODE>allValuesFrom</CODE> unitMonth and 
property <CODE>month</CODE> <CODE>hasValue</CODE> of 1:<BR><PRE>:January
      a       owl:Class ;
      rdfs:subClassOf :DateTimeDescription ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:onProperty :unitType
                owl:hasValue :unitMonth
              ] ;
     rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:onProperty :month
                owl:hasValue --01 ;
              ] .
</PRE>
<P>In order to specify that an instant is in a datetime interval, an 
<CODE>inDateTime</CODE> property/relation is defined similarly to 
<CODE>hasDateTimeDescription</CODE> as follows:</P><PRE>:inDateTime
      a       owl:ObjectProperty ;
      rdfs:domain :Instant ;
      rdfs:range :DateTimeDescription .
</PRE>
<P>With this <CODE>inDateTime</CODE> relation, we can say that an instant 
happens at a specific time. For example, the beginning of a meeting, which is an 
instant, is at 6:00pm which is actually in a datetime interval of [6:00:00, 
6:01:00). With <CODE>inDateTime</CODE> you do not describe instants; you only 
approximate them by confining them within an interval. This should generally be 
adequate. Where it is not, you can always define an instant in a roundabout way 
as the beginning of an interval.</P>
<P><A name=ref-datetime></A>We also defined in OWL two simpler relations, 
<CODE>xsdDateTime</CODE> and <CODE>inXSDDateTime</CODE>. The only difference 
between these two relations and the above <CODE>hasDateTimeDescription</CODE> and 
<CODE>inDateTime</CODE> relations is their ranges: these two simpler relations 
use the XML Schema datatype <CODE>dateTime</CODE> as their ranges, while the 
above uses <CODE>DateTimeDescription</CODE>:</P><PRE>:xsdDateTime
      a       owl:DatatypeProperty ;
      rdfs:domain :DateTimeInterval ;
      rdfs:range xsd:dateTime .

:inXSDDateTime
      a       owl:DatatypeProperty ;
      rdfs:domain :Instant ;
      rdfs:range xsd:dateTime .
</PRE>
<P>To illustrate more clearly the difference between using 
<CODE>DateTimeDescription </CODE>and using the XML datatype 
<CODE>dateTime</CODE>, let’s look at a concrete example: an instant that 
represents the start of a meeing, called <CODE>meetingStart</CODE>, happens at 
10:30am EST on 01/01/2006 can be expressed using both <CODE>inXSDDateTime</CODE> 
and <CODE>inDateTime</CODE> in OWL as:</P><PRE>:meetingStart
      a       :Instant ;
      :inDateTime
              :meetingStartDescription ;
      :inXSDDateTime
              2006-01-01T10:30:00-5:00 .

:meetingStartDescription
      a       :DateTimeDescription ;
      :unitType :unitMinute ;
      :minute 30 ;
      :hour 10 ;
      :day 1 ;
      :dayOfWeek :Sunday ;
      :dayOfYear 1 ;
      :week 1 ;
      :month 1 ;
      :timeZone tz-us:EST ;
      :year 2006 .</PRE>
<P>We can see from this example that it’s much more concise to use the XML 
Schema datatype <CODE>dateTime</CODE>. However, the advantage of using 
<CODE>DateTimeDescription </CODE>is that it can express more information than 
<CODE>dateTime</CODE>, such as "week", "day of week" and "day of year", so in 
the above example, we can also know that 01/01/2006 is Sunday, on the first 
day of the year, and in the first week of the year. </P>
<P>The namespace “tz-us” points to our US time zone data [<A 
href="#ref-17">17</A>]. 
Moreover, each field of <CODE>DateTimeDescription </CODE>is separate so that 
it's easier to extract the value of some fields for the later use and easier to 
reason about.</P>
<H4 id="time-ontology-code">OWL code for the time ontology </H4>
<P>[<A href="/2006/time">RDF/XML</A>] </P>
<H2><A name=ref-time-in-owl-s></A>Use Cases for Web Services</H2>
<P>Congo.com and Bravo Air are the two examples used in the OWL-S 0.9 draft 
release [<A 
href="#ref-12">12</A>] 
(the most recent release is OWL-S 1.1 [<A 
href="#ref-13">13</A>], 
and we use code in 0.9 draft release here for illustrative purpose). Congo.com 
is a fictitious book-selling service site, and Bravo Air is a fictitious 
airline-ticketing service site. We use these two examples to demonstrate in 
detail how the time ontology can be used to support OWL-S, including use cases 
for defining input parameters and (conditional) output parameters. </P>
<H3><A name=input></A>Use Cases for Input Parameters</H3>
<P>In the profile of the Congo.com example (i.e. CongoProfile.owl), for example, 
our time ontology is currently used for describing the input parameter 
<CODE>CreditCardExpirationDate</CODE>:</P><PRE>profile:CreditCardExpirationDate
      a       profile:ParameterDescription ;
      profile:parameterName
              creditCardExpirationDate ;
      profile:restrictedTo
              time:<B>Instant</B> ;
      profile:referTo
              congoProcess:creditCardExpirationDate .</PRE>
<P>The namespace “time” points to the location of the OWL code for the time 
ontology. In this example <CODE>Instant</CODE> is used to describe 
<CODE>CreditCardExpirationDate</CODE>, because the expiration date is actually 
an instant -- the midnight, of the day the credit card expires. </P>
<P>In the Bravo Air example, our time ontology can be used to describe the 
existing input parameters, <CODE>DepartureDate</CODE> and 
<CODE>ArrivalDate</CODE>. We will change this to the more appropriate 
<CODE>DepartureTime</CODE> and <CODE>ArrivalTime</CODE>. We can define 
<CODE>DepartureTime</CODE> in the profile of the Bravo Air example (i.e. 
BravoAirProfile.owl) as: </P><PRE>profile:DepartureTime
      a       profile:ParameterDescription ;
      profile:parameterName
              DepartureTime ;
      profile:restrictedTo
              time:<B>Instant</B> ;
      profile:referTo
              ba_process:outboundDate_In .</PRE>
<P><CODE>DepartureTime</CODE> is defined as <CODE>Instant</CODE>. With this 
definition, as we discussed in the previous datetime description section, an 
instance of <CODE>DepartureTime</CODE> can has either an 
<CODE>inXSDDateTime</CODE> property/relation pointing to a specific value of XML 
Schema datatype dateTime, say 2006-01-01T10:30:00-5:00, or an 
<CODE>inDateTime</CODE> object-property/relation pointing to an instance of 
<CODE>DateTimeDescription</CODE> class specifying a specific time, say 10:30am 
EST on 01/01/2006, Sunday. It would be the user’s decision to define the time 
in either way based on the trade-offs discussed in the previous section.</P>
<H3><A name=output></A>Use Cases for (Conditional) Output Parameters</H3>
<P>In fact, there is much more that our time ontology can do to support OWL-S. 
In the Congo.com and Bravo Air examples, the time ontology is not used for any 
output parameters. However, in the real world many service outputs are 
time-related. For example, in the Congo.com example we can add two outputs that 
are very common in real world book-selling sites: process time and delivery 
duration.</P>
<H4 id="ProcessTime">Adding a <CODE>ProcessTime</CODE> output parameter</H4>
<P><CODE>ProcessTime</CODE> is a conditional output parameter that specifies how 
long before the book will be ready for delivery, say, 24 hours, which depends on 
whether the book is in stock. In this use case, the process time is returned 
only if the book is in stock. It can be defined in the process model of the 
Congo.com example (i.e. CongoProcess.owl) as:</P><PRE>:ProcessTime
      a       owl:Class ;
      rdfs:subClassOf time:<B>Interval</B> .

:fullCongoBuyProcessTime
      a       rdf:Property ;
      rdfs:subPropertyOf process:output ;
      rdfs:domain :FullCongoBuy ;
      rdfs:range       
	      [ a       owl:Class ;
      		rdfs:subClassOf process:ConditionalOutput ;
      		rdfs:subClassOf
              		[ a       owl:Restriction ;
                	owl:allValuesFrom :BookInStock ;
                	owl:onProperty process:coCondition
              		] ;
	      ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:allValuesFrom :<B>ProcessTime</B> ;
                owl:onProperty process:coOutput
              ] .</PRE>
<P><CODE>ProcessTime</CODE> is defined as an interval, rather than a duration. 
As discussed previously, in our time ontology durations are properties of 
intervals. Thus to talk about a duration, i.e. a quantity of time, an interval 
must be defined first. This approach may look roundabout at first glance. 
However, the process time is not purely a quantity of time; it has a location on 
the time line. The beginning of the process time is the time the user places the 
order, and the end of the process time is the time the order is shipped out. An 
advantage of defining <CODE>ProcessTime</CODE> as an interval is that if the 
relationship among the order time, the shipping time, and the process time is 
known, any one of them (e.g. the shipping time) can be computed from the other 
two (e.g. the order time and the process time) by temporal arithmetic. </P>
<H4 id="DeliveryDuration">Adding a <CODE>DeliveryDuration</CODE> output parameter</H4>
<P><CODE>DeliveryDuration</CODE> is a conditional output parameter that 
specifies how long it will take for the customer to receive the book after it is 
shipped out, which depends on the delivery type the customer selects. As defined 
in the process model of the Congo.com example (i.e. CongoProcess.owl), the 
current delivery types are FedExOneDay, FedEx2-3day, UPS, and OrdinaryMail. </P>
<P>To add this output parameter may seem similar to the above 
<CODE>ProcessTime</CODE> example. However, since an instance of 
<CODE>Condition</CODE> is a logical formula that evaluates to true or false (see 
the comment with the definition of Condition [<A 
href="#ref-14">14</A>]), 
<CODE>DeliveryType</CODE> cannot be directly used as a condition to determine 
the delivery duration. Thus one property and one condition are defined for each 
delivery type. </P>
<P><CODE>DeliveryDuration</CODE> is defined with two boundaries: one 
<CODE>minDeliveryDuration</CODE> and one <CODE>maxDeliveryDuration</CODE>. For 
example, an order with the FedEx2-3day delivery type takes 2 to 3 days, so its 
min delivery duration is 2 days, and its max delivery duration is 3 days. For 
the delivery duration of the order with FedExOneDay delivery type, the min and 
max delivery duration will both be 1 day. We can define 
<CODE>DeliveryDuration</CODE> in the process model of the Congo.com example 
(i.e. CongoProcess.owl) as:</P><PRE>:DeliveryDuration
      a       owl:Class ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:cardinality 1 ;
                owl:onProperty :maxDeliveryDuration
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:cardinality 1 ;
                owl:onProperty :minDeliveryDuration
              ] .

:maxDeliveryDuration
      a       rdf:Property ;
      rdfs:domain :DeliveryDuration ;
      rdfs:range time:<B>Interval</B> .

:minDeliveryDuration
      a       rdf:Property ;
      rdfs:domain :DeliveryDuration ;
      rdfs:range time:<B>Interval</B> .
</PRE>
<P>Both <CODE>minDeliveryDuration</CODE> and <CODE>maxDeliveryDuration 
</CODE>are defined as properties of <CODE>DeliveryDuration</CODE>. For the same 
reason discussed for the process time example, both properties use Interval as 
their ranges. The cardinality of 1 for both properties in the definition of 
<CODE>DeliveryDuration</CODE> indicates that an instance of 
<CODE>DeliveryDuration</CODE> must have one and only one property value for 
<CODE>minDeliveryDuration</CODE> and <CODE>maxDeliveryDuration 
</CODE>respectively. For example, in order to define delivery duration for 
FedEx2-3day, we have to first define a condition of FedEx2-3day being 
selected:</P><PRE>:FedEx2-3dayCondition
      a       owl:Class ;
      rdfs:subClassOf process:Condition .</PRE>
<P>Then we define an output property, called 
<CODE>deliverySelectFedEx2-3day</CODE> that is conditional on 
<CODE>FedEx2-3dayCondition</CODE> defined above:</P><PRE>:deliverySelectFedEx2-3day
      a       rdf:Property ;
      rdfs:subPropertyOf process:output ;      
      rdfs:domain :SpecifyDeliveryDetails ;
      rdfs:range 
      	      [ a       owl:Class ;
      	      	rdfs:subClassOf process:ConditionalOutput ;
      	      	rdfs:subClassOf
              	      	[ a       owl:Restriction ;
                      	owl:allValuesFrom :FedEx2-3dayDuration ;
                      	owl:onProperty process:coOutput
              	      	] ;
      	      	rdfs:subClassOf
              	      	[ a       owl:Restriction ;
                      	owl:allValuesFrom :FedEx2-3dayCondition ;
                      	owl:onProperty process:coCondition
              ] .</PRE>
<P>This definition says that <CODE>deliverySelectFedEx2-3day</CODE> is a 
conditional output, and if <CODE>FedEx2-3dayCondition</CODE> is true, an 
instance of <CODE>FedEx2-3dayDuration</CODE> class will be the output. 
<CODE>FedEx2-3dayDuration</CODE> is not defined yet. In order to define it, we 
have to define its min delivery duration, i.e. 2 days, and max delivery 
duration, i.e. 3 days. Since the range of <CODE>minDeliveryDuration</CODE> and 
<CODE>maxDeliveryDuration</CODE> is <CODE>Interval</CODE>, intervals with 
specific durations need to be created first. For 
<CODE>FedEx2-3dayDuration</CODE>, we need to define <CODE>Interval2Days</CODE> 
and <CODE>Interval3Days</CODE> first as follows:</P><PRE>:Interval2Days
      a       owl:Class ;
      rdfs:subClassOf time:<B>Interval</B> ;
      owl:subClassOf
              [ a       owl:Restriction ;
                owl:hasValue P2D ;
                owl:onProperty time:<B>durationDescriptionDataType</B>
              ] .

:Interval3Days
      a       owl:Class ;
      rdfs:subClassOf time:<B>Interval</B> ;
      owl:subClassOf
              [ a       owl:Restriction ;
                owl:hasValue P3D ;
                owl:onProperty time:<B>durationDescriptionDataType</B>
              ] .</PRE>
<P>These two definitions use <CODE>durationDescriptionDataType</CODE>, a 
relatively simpler duration property of <CODE>Interval</CODE> using the XML 
Schmea datatype <CODE>duration</CODE> as its range. <CODE>P2D</CODE> and 
<CODE>P3D</CODE> are values of the XML Schema datatype <CODE>duration</CODE>, 
meaning 2 days and 3 days.</P>
<P>Finally, <CODE>FedEx2-3dayDuration</CODE> restricts the value of 
<CODE>minDeliveryDuration</CODE> and <CODE>maxDeliveryDuration</CODE> to class 
<CODE>Interval2Days</CODE> and <CODE>Interval3Days</CODE> respectively as 
follows:</P><PRE>:FedEx2-3dayDuration
      a       owl:Class ;
      rdfs:subClassOf :DeliveryDuration ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:allValuesFrom :Interval3Days ;
                owl:onProperty :maxDeliveryDuration
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:allValuesFrom :Interval2Days ;
                owl:onProperty :minDeliveryDuration
              ] .</PRE>
<P>Properties to output delivery durations when the user selects other delivery 
types (FedExOneDay, UPS, and OrdinaryMail) can be defined similarly.</P>
<H4 id="time-in-owls-09">OWL code for these examples</H4>
<P>[<A href="time-in-owls-09">RDF/XML</A>] 
</P>
<H2><A name=scheduling></A>A Use Case for Scheduling</H2><A name=examples0></A>
<P>Suppose someone has a telecon scheduled for 6:00pm EST on November 5, 2006. 
You would like to make an appointment with him for 2:00pm PST on the same day, 
and expect the meeting to last 45 minutes.&nbsp; Will there be an overlap? </P>
<P>In this use case we can specify the facts about the telecon and the meeting 
using our ontology in OWL that will allow a temporal reasoner to determine 
whether there is a conflict:</P><PRE>:telecon
      a       :Interval ;
      :hasBeginning :teleconStart .
      
:meeting
      a       :Interval ;
      :hasBeginning :meetingStart ;
      :hasDurationDescription
              :meetingDuration .

:teleconStart
      a       :Instant ;
      :inXSDDateTime
              2006-11-05T18:00:00-5:00 .

:meetingStart
      a       :Instant ;
      :inXSDDateTime
              2006-11-05T14:00:00-8:00 .

:meetingDuration
      a       :DurationDescription ;
      :minutes 45 .
</PRE>
<P>The telecon and the meeting are defined as intervals. 
<CODE>hasBeginning</CODE> is used for specifying the start times of the 
meetings. The datetimes are specified using <CODE>inXSDDateTime</CODE>. The 
duration of the meeting is specified using the duration description class.</P>
<HR>

<H2><A id=summary></A>Appendix A. Summary of Classes and Properties in the Time Ontology</H2><A name=changes></A>
<P class=MsoNormal><B><SPAN style="FONT-SIZE: 14pt">Classes (subclass 
relations)</SPAN></B></P>
<A name=changes></A>
<UL>
  <LI>
  <P class=MsoNormal>TemporalEntity
  <UL>
    <LI>
    <P class=MsoNormal>Instant </P>
    <LI>
    <P class=MsoNormal>Interval
    <UL>
      <LI>
      <P class=MsoNormal>ProperInterval
      <UL type=disc>
        <LI>
        <P class=MsoNormal>DateTimeInterval </P></LI></UL></LI></UL></LI></UL>
  <LI>
  <P class=MsoNormal>DurationDescription </P>
  <LI>
  <P class=MsoNormal>DateTimeDescription </P>
  <LI>
  <P class=MsoNormal>TemporalUnit </P>
  <LI>
  <P class=MsoNormal>DayOfWeek<BR>&nbsp; </P></LI></UL>
<P class=MsoNormal><B><SPAN style="FONT-SIZE: 14pt">Properties</SPAN></B></P>
<TABLE class=MsoTableGrid 
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 5.4pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse" 
cellSpacing=0 cellPadding=0 border=1 id="table1">
  <TBODY>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: windowtext 1pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal><B>Property Name</B></P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: windowtext 1pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal><B>Domain</B></P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: windowtext 1pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal><B>Range</B></P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>before</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>TemporalEntity</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>TemporalEntity</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>after</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>TemporalEntity</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>TemporalEntity</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>hasBeginning</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>TemporalEntity</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>Instant</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>hasEnd</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>TemporalEntity</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>Instant</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>inside</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>Interval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>Instant</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalEquals</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalBefore</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalMeets</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalOverlaps</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalStarts</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalDuring</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalFinishes</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalAfter</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalMetBy</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalOverlappedBy</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalStartedBy</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalContains</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>intervalFinishedBy</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>ProperInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>ProperInterval</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>years</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DurationDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;decimal</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>months</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DurationDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;decimal</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>weeks</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DurationDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;decimal</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>days</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DurationDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;decimal</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>hours</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DurationDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;decimal</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>minutes</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DurationDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;decimal</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>seconds</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DurationDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;decimal</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>hasDurationDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>TemporalEntity</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>DurationDescription</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>unitType</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>TemporalUnit</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>year</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;gYear</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>month</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;gMonth</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>week</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;nonNegativeInteger</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>day</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;gDay</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>dayOfWeek</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>DayOfWeek</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>dayOfYear</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;nonNegativeInteger</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>hour</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;nonNegativeInteger</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>minute</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;nonNegativeInteger</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>second</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;decimal</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>timeZone</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>tzont;TimeZone</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>inDateTime</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>Instant</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>DateTimeDescription</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>inXSDDateTime</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>Instant</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;dateTime</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>hasDateTimeDescription</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>DateTimeDescription</P></TD></TR>
  <TR>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: windowtext 1pt solid; WIDTH: 136.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=182>
      <P class=MsoNormal>xsdDateTime</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 124.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=166>
      <P class=MsoNormal>DateTimeInterval</P></TD>
    <TD 
    style="BORDER-RIGHT: windowtext 1pt solid; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 142.85pt; PADDING-TOP: 0in; BORDER-BOTTOM: windowtext 1pt solid" 
    vAlign=top width=190>
      <P class=MsoNormal>xsd;dateTime</P></TD></TR></TBODY></TABLE>

<p></p>
<HR>
<H2><A id=timezone></A>Appendix B. Time Zone Resource in OWL</H2>
<A name=timezones-owl></A>
<P>We have developed a time zone resource [<a href="#ref-15">15</a>] in 
OWL for not only the US but also the entire world, including three parts: the 
time zone ontology file [<A 
href="#ref-16">16</A>], 
the US time zone instance file [<A 
href="#ref-17">17</A>], 
and the world time zone instance file [<A 
href="#ref-18">18</A>]. 
</P>
<P>The time zone ontology links a preliminary geographic ontology with a time 
ontology. It defines the vocabulary about regions, political regions (countries, 
states, counties, reservations, and cities), time zones, daylight saving 
policies, and the relationships between these concepts. Its instances also link 
to other existing data on the Web, such as FIPS 55 county instances [<A 
href="#ref-19">19</A>], 
and ISO country instances [<a href="#ref-20">20</a>].</P>
<P>It can handle all the usual time zone and daylight savings cases. For 
example, Los Angles uses PST, the time offset from Coordinated Universal Time 
(UTC) is -8 hours, and it observed daylight savings from April 2 to October 29 
in 2006. But it handles unusual cases as well. For example, in Idaho the 
northern part is in the Pacific zone, the southern part in the Mountain. The 
city of West Wendover, Nevada is in the Mountain time zone, while the rest of 
Nevada is in the Pacific. </P>
<H3><A name=examples1></A>Use case examples</H3>
<P id=codesyntax0>Suppose someone has a telecon scheduled for 6:00pm EST on 
November 5, 2006. You would like to make an appointment with him for 2:00pm PST 
on the same day, and expect the meeting to last 45 minutes. Will there be an 
overlap? In order to specify the facts about the telecon and the meeting and 
reason about the relation between them, a time zone ontology would be necessary 
to help a time ontology (e.g. OWL-Time) to resolve the time difference between 
EST and PST.&nbsp;[<A 
href="#ref-anti-use">Anticipated 
Use</A>] will be described in detail in a later section.&nbsp;&nbsp; &nbsp;</P>
<H3><A name=ontology></A>Time Zone Ontology</H3>
<P>We take <CODE>PoliticalRegion</CODE> to be a subclass of <CODE>Region</CODE> 
with the following properties: 
<UL>
  <LI><B>name</B>: at most one string. </LI></UL>
<UL>
  <LI><B>hasParentRegion</B>: the parent political region. </LI></UL>
<UL>
  <LI><B>hasTimeZone</B>: at most three time zones. </LI></UL>
<UL>
  <LI><B>observesDaylightSavingsTime</B>: true if the region goes on daylight 
  savings time, false otherwise. </LI></UL>
<UL>
  <LI><B>hasDaylightSavingsPolicy</B>: the daylight saving policy that the 
  region uses. </LI></UL>
<UL>
  <LI><B>exceptionalRegion</B>: exceptional sub-political-regions that have 
  different time zones and/or daylight saving time policies (e.g. West Wendover, 
  Nevada). </LI></UL>
<UL>
  <LI><B>timeZonePart</B>: sub-non-political-regions that have different time 
  zones and/or daylight saving time policies (e.g. two different time zone parts 
  in Idaho County in Idaho State). </LI></UL>
<P>This can be defined in OWL as:</P><PRE>:PoliticalRegion
      a       owl:Class ;
      rdfs:subClassOf :Region ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :name
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :hasParentRegion
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 3 ;
                owl:onProperty :hasTimeZone
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :observesDaylightSavingsTime
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :hasDaylightSavingsPolicy
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:minCardinality 0 ;
                owl:onProperty :exceptionalRegion
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:minCardinality 0 ;
                owl:onProperty :timeZonePart
              ] .</PRE>
<P>Countries, states, counties, cities, and reservations are all subclass of 
political regions with different range types for the 
<CODE>hasParentRegion</CODE> property.<BR><BR>For example, <CODE>Country</CODE> 
and <CODE>State</CODE> can be defined in OWL as:</P><PRE>:Country
      a       owl:Class ;
      rdfs:subClassOf :PoliticalRegion .</PRE><PRE>:State
      a       owl:Class ;
      rdfs:subClassOf :PoliticalRegion ;
      owl:subClassOf
              [ a       owl:Restriction ;
               owl:onProperty :hasParentRegion ; 
               owl:allValuesFrom :Country                 
              ] .</PRE>Time zones have two properties: 
<UL>
  <LI><B>name</B>: at most one string. </LI></UL>
<UL>
  <LI><B>GMToffset</B>: an XML Schema duration between -12 and +14 
hours.</LI></UL>
<P>This can be defined in OWL as:</P><PRE>:TimeZone
      a       owl:Class ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :name
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :GMToffset
              ] .</PRE>
<P>We assume default reasoning is used for this ontology. When a political 
region lacks one of its properties, we will use the one from its parent region. 
Thus all political sub-regions of the United States get their 
<CODE>DaylightSavingsPolicy</CODE> values from that of the United States, 
provided their <CODE>observesDaylightSavingsTime</CODE> property is true. All 
counties in California get their <CODE>hasTimeZone</CODE> values from 
California, whereas the <CODE>hasTimeZone</CODE> value is specified for each 
county in Kentucky and not for the state as a whole, since it is split between 
the Eastern and Central time zones. When most of a region is in one time zone, 
and only some exceptional sub-regions are in different time zones or have 
different daylight savings time policies, we use <CODE>exceptionalRegion</CODE> 
to point to each exceptional sub-region, e.g. West Wendover, which is in the 
Mountain time zone, is an exception in Nevada, which is otherwise in the Pacific 
time zone. <A name=ref-west-wen></A>Here is the OWL code of Nevada and West 
Wendover in the US time zone instance file [<a href="#ref-17">17</a>]:</P><PRE>:us-states:NV
      a       :State ;
      :hasParentRegion iso:US;
      :hasTimeZone :<B>PST</B> ;
      :observesDaylightSavingsTime true ;
      :<B>exceptionalRegion</B> :<B>NVWestWendoverCity</B> .

:NVWestWendoverCity
      a       :City ;
      :name "West Wendover City" ;
      :stateOf us-states:NV ;
      :hasTimeZone :<B>MST</B> ;
      owl:sameIndividualAs
              &lt;<A href="http://www.daml.org/2003/02/fips55/NV.owl#p83730">http://www.daml.org/2003/02/fips55/NV.owl#p83730</A>&gt; .</PRE>
<P>When different parts of the same county are in different time zones, the 
<CODE>hasTimeZone</CODE> is not specified for the county. Instead the 
<CODE>hasTimeZone</CODE> is specified for each part with different time zones, 
and the <CODE>timeZonePart</CODE> property is used to point to the parts from 
the county instance, e.g. the two different time zone parts in Idaho County, 
Idaho. Here is the OWL encoding of Idaho County, Idaho in our US time zone 
instance file [<a href="#ref-17">17</a>]:</P><PRE>:IDIdaho
      a       :County ;
      :name "Idaho County" ;
      :hasParentRegion
              us-states:ID ;
      :<B>timeZonePart</B>
              :<B>IDIdahoPST</B> , :<B>IDIdahoMST</B> ;
      owl:sameIndividualAs
              &lt;http://www.daml.org/2003/02/fips55/ID.owl#c049&gt; .</PRE><A 
name=ontology0></A><CODE>DaylightSavingsPolicy</CODE> has one property: 
<UL>
  <LI><B>lastUpdated</B>: the time that the daylight savings policy was updated. 
  </LI></UL>
<P><CODE>EnumeratedDaylightSavingsPolicy</CODE>, a subclass of 
<CODE>DaylightSavingsPolicy</CODE>, has the following properties:</P>
<UL>
  <LI><B>DLSstartDate</B>: the date the region goes on daylight savings time. 
  </LI></UL>
<UL>
  <LI><B>DLSendDate</B>: the date the region goes off daylight savings 
time.</LI></UL>
<P>This can be defined in OWL as:</P><PRE>:EnumeratedDaylightSavingsPolicy
      a       owl:Class ;
      rdfs:subClassOf :DaylightSavingsPolicy ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :DLSendDate
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:maxCardinality 1 ;
                owl:onProperty :DLSstartDate
              ] .</PRE>
<P><CODE>DLSstartDate</CODE> and <CODE>DLSendDate</CODE> properties have the 
range of xsd:date. In the current instance 
files, different daylight saving policies were only defined for year 2006 as 
instances of <CODE>EnumeratedDaylightSavingsPolicy</CODE>, e.g. 
<CODE>USA2006DLS</CODE> for the United States, and <CODE>EU2006DLS</CODE> for 
the European Union.&nbsp;</P>
<P><A name=ref-temp-agg-eg></A>Alternatively, a temporal aggregates ontology in 
OWL-Time can be used to describe the daylight saving policies. For example, in 
the US daylight saving starts on "the first Sunday of every April", which can be 
expressed in OWL as:</P><PRE>:tseq
      a       :TemporalSeq ;
      :hasTemporalAggregateDescription
              :firstSunEveryApril .</PRE><PRE>:tseq-everyApril
      a       :TemporalSeq ;
      :hasTemporalAggregateDescription
              :everyApril .</PRE><PRE>:everyApril
      a       :TemporalAggregateDescription ;
      :hasTemporalUnit
              :unitMonth ;
      :hasithTemporalUnit 4 .

:firstSunEveryApril
      a       :TemporalAggregateDescription ;
      :hasContextTemporalSeq
              :tseq-everyApril ;
      :hasContextTemporalUnit
              :unitMonth ;
      :hasithTemporalUnit 7 ;
      :hasTemporalUnit
              :unitDay ;
      :hasPosition 1 .</PRE>
<P>This defines the desired temporal sequence <CODE>tseq</CODE> of class 
<CODE>TemporalSeq</CODE> which has a 
<CODE>hasTemporalAggregateDescription</CODE> property that points to a temporal 
aggregate description <CODE>firstSunEveryApril</CODE> that describes the 
temporal sequence. In order to describe this two-layered temporal sequence ("the 
first Sunday" of "every April"), the outside layer ("every April"), i.e. the 
context temporal sequence (<CODE>tseq-everyApril</CODE>), needs to be defined 
first. This context temporal sequence also has its own 
<CODE>hasTemporalAggregateDescription</CODE> property that points to 
<CODE>everyApril</CODE> which describes that it is the every 4th 
(<CODE>hasithTemporalUnit</CODE> of 4) month (<CODE>hasTemporalUnit</CODE> of 
<CODE>unitMonth</CODE>). The desired temporal sequence is then defined as "the 
first (<CODE>hasPosition</CODE> of 1) Sunday (<CODE>hasithTemporalUnit</CODE> of 
7 and <CODE>hasTemporalUnit</CODE> of <CODE>unitDayOfWeek</CODE>) of every April 
(<CODE>hasContextTemporalSeq</CODE> of <CODE>tseq-everyApril</CODE> and 
<CODE>hasContextTemporalUnit</CODE> of <CODE>unitMonth</CODE>)".</P>
<P>For details about the temporal aggregates ontology and its use case examples, 
please see [<a href="#ref-6">6</a>,<a href="#ref-7">7</a>].</P>
<H4 id="timezone-ont">OWL code for the time zone ontology </H4>
<P>[<A href="/2006/timezone">RDF/XML</A>] 
</P>
<H3><A name=ref-anti-use></A>Anticipated Use</H3>
<P>The expected input to the ontology is a location, e.g. a city, and the output 
will be its current time offset, say -6 hours, from the Greenwich Mean Time 
(GMT).<BR><BR>The ontology would be used as follows: given an input location, we 
first find in the ontology the lowest-level political region containing this 
location, say a county, then go up along the political region hierarchy based on 
the <CODE>hasParentRegion</CODE> property to the top of the hierarchy, usually a 
country. Along the path to the top, we get all the available information from 
each node (region) in order to calculate the time offset from the GMT. The 
information includes the time zone this location is in, whether it uses Daylight 
Savings (DLS) time, and if it does, what the start and end dates are. </P>
<P>However, flexible inputs and more efficiency are supported by using the 
<CODE>exceptionalRegion</CODE> and <CODE>timeZonePart</CODE> properties, i.e. 
the location input does not have to be as detailed as the lowest-level political 
region, especially because usually only the information about what state it is 
in would be enough to calculate the time offset from the GMT for the input 
location. </P>
<P>If the input only says it's a location of a state without specifying the 
county or city it is in, then we can first go to its state and see whether we 
can find all the information we need there, i.e. time zone and daylight savings 
information. If the state doesn't have any <CODE>exceptionalRegion</CODE>’s, 
then we don't need any more inputs for this location, and can safely go up along 
the political region hierarchy to the top of the hierarchy, e.g. the country US, 
and get all the information we need along the way to calculate the time offset 
from the GMT for this location. If the state does have any 
<CODE>exceptionalRegion</CODE>’s, however, we have to check each exceptional 
region to see whether this location is in it or not, at this checking phase, 
more detailed information about this location may be needed, i.e. which 
county/city/reservation it is in. If it's in an exceptional county that further 
has <CODE>timeZonePart</CODE>’s, then even more detailed information is needed 
from the input, i.e. which time zone part the location is in within this county. 
When reaching a sub-region with no <CODE>exceptionalRegion</CODE>’s or 
<CODE>timeZonePart</CODE>’s, we know for sure that no more input location 
information is needed and it's safe to go up along the political region 
hierarchy to the top, and get all the information we need to calculate the time 
offset from the GMT for this location. <BR><BR>For example, suppose the input 
location is a location in West Wendover, Nevada, but at first we only know it's 
in Nevada (please see the OWL code [<A 
href="#ref-west-wen">in the 
previous section</A>]). In the ontology, we first find Nevada state, from which 
we see one exceptional region pointing to West Wendover City, then we ask for 
further input location information: which city is this location in? Say we get 
West Wendover City. Since it matches the exceptional region, we then go to the 
West Wendover City instance to get its time zone information, which is the 
Mountain time zone. Since there is no <CODE>exceptionalRegion</CODE>’s or 
<CODE>timeZonePart</CODE>’s in the West Wendover City instance, it's now safe 
for us to go up along the hierarchy to the top, the United States. Along the 
path, at Nevada State we learn this location uses DLS time, then at its parent 
region, the US, we learn the DLS policy used is USA2006DLS which specifies the 
start date of the DLS in 2006 is 04/02/2006 and the end date is 10/29/2006. 
Based on our current time, e.g. 1:50pm on 09/06/2006, we know the current time 
offset from the GMT at this location is -7 hours. </P>
<HR>

<A name=examples2></A>

<H2 id=references>References</H2>
<P><A name=ref-1></A>[1] Allen, J. F. 1984. Towards a general theory of action 
and time. <I>Artificial Intelligence </I>23, pp. 123-154.<BR><BR><A 
name=ref-2></A>[2] Allen, J. F. and Ferguson, G. 1997. Actions and events in 
interval temporal logic. In <I>Spatial and Temporal Reasoning</I>. O. Stock, 
ed., Kluwer, Dordrecht, Netherlands, 205-245.</P>
<P><A 
name=ref-3></A>[3] Dawson, F. and Stenerson, D. 1998. Internet Calendaring and Scheduling Core Object 
Specification (iCalendar), RFC2445. <A 
href="http://www.ietf.org/rfc/rfc2445.txt">http://www.ietf.org/rfc/rfc2445.txt</A></P>
<P><A name=ref-4></A>[4] 
Hobbs, J. R. and Pan, F. 2004. An Ontology of Time for the Semantic Web. <I>ACM 
Transactions on Asian Language Processing (TALIP): Special issue on Temporal 
Information Processing</I>, Vol. 3, No. 1, March 2004, pp. 66-85. </P>
<P><A 
name=ref-5></A>[5] Pan, F and Hobbs, J. R. 2004. Time in OWL-S. In 
<I>Proceedings of the AAAI Spring Symposium on Semantic Web Services</I>, 
Stanford University, CA, pp. 29-36.</P>
<P><A name=ref-6></A>[6] Pan, F and Hobbs, J. R. 2005. Temporal Aggregates in OWL-Time. In <i>
Proceedings of the 18th International Florida Artificial Intelligence Research 
Society Conference (FLAIRS)</i>, Clearwater Beach, Florida, pp. 560-565, AAAI Press.
<P><A name=ref-7></A>
[7] Pan, F. 2005. A Temporal Aggregates Ontology in OWL for the Semantic Web. In
<i>Proceedings of the AAAI Fall Symposium on Agents and the Semantic Web</i>, 
Arlington, Virginia, pp. 30-37.&nbsp;</P>
<P><A 
name=ref-8></A>[8] OWL code of the time ontology. <A 
href="http://www.w3.org/2006/time">http://www.w3.org/2006/time</A><BR><BR><A 
name=ref-9></A>[9] OWL code of the entry sub-ontology of time. <A 
href="http://www.w3.org/2006/time-entry">http://www.w3.org/2006/time-entry</A></P>
<P><A name=ref-10></A>[10] OWL-Time Homepage: <A 
href="http://www.isi.edu/~pan/OWL-Time.html">http://www.isi.edu/~pan/OWL-Time.html</A><BR><BR>
<A 
name=ref-11></A>[11] OWL-S homepage. <A 
href="http://www.daml.org/services/owl-s/">http://www.daml.org/services/owl-s/</A></P>
<P><A 
name=ref-12></A>[12] OWL-S 0.9 release. <A 
href="http://www.daml.org/services/daml-s/0.9/">http://www.daml.org/services/daml-s/0.9/</A></P>
<P><A 
name=ref-13></A>[13] OWL-S 1.1 release. <A 
href="http://www.daml.org/services/owl-s/1.1/">http://www.daml.org/services/owl-s/1.1/</A><BR><BR><A 
name=ref-14></A>[14] The process file of the OWL-S 0.9 release. <A 
href="http://www.daml.org/services/owl-s/0.9/Process.owl">http://www.daml.org/services/owl-s/0.9/Process.owl</A></P>
<P><A 
name=ref-15></A>[15] The homepage of the time zone resource in OWL. <A 
href="http://www.isi.edu/~pan/timezonehomepage.html">http://www.isi.edu/~pan/timezonehomepage.html</A><BR><BR><A 
name=ref-16></A>[16] The time zone ontology file. <A 
href="http://www.w3.org/2006/timezone">http://www.w3.org/2006/timezone</A><BR><BR><A 
name=ref-17></A>[17] The US time zone instance file.<B> </B><A 
href="http://www.w3.org/2006/timezone-us">http://www.w3.org/2006/timezone-us</A><BR><BR><A 
name=ref-18></A>[18] The world time zone instance file. <A 
href="http://www.w3.org/2006/timezone-world">http://www.w3.org/2006/timezone-world</A><BR><BR><A 
name=ref-19></A>[19] FIPS 55 County instance file. <A 
href="http://www.daml.org/2003/02/fips55/">http://www.daml.org/2003/02/fips55/</A><BR><BR><A 
name=ref-20></A>[20] ISO Country instance file. <A 
href="http://www.daml.org/2001/09/countries/iso">http://www.daml.org/2001/09/countries/iso</A></P>
<HR>


<A name=examples3></A>

<H2 id=ack>Acknowledgements</H2>
<p>The editors would like to thank Deborah McGuinness, Chris Welty, and the 
reviewers of the earlier versions of the doucment, i.e., Jeremy Carroll, John 
McClure, Libby Miller, and Guus Schreiber, for their very helpful feedbacks and 
comments to the document.</p>


</BODY></HTML>