discontinued / server · Files

index.html 74 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 
<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
<html lang="en" dir="ltr">
<head>
    <title>Points of Interest Core</title>
    <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
    <!-- 
      === NOTA BENE ===
      For the three scripts below, if your spec resides on dev.w3 you can check them
      out in the same tree and use relative links so that they'll work offline,
     -->
    
    
  <style type="text/css">
/*****************************************************************
 * ReSpec CSS
 * Robin Berjon (robin at berjon dot com)
 * v0.05 - 2009-07-31
 *****************************************************************/


/* --- INLINES --- */
em.rfc2119 { 
    text-transform:     lowercase;
    font-variant:       small-caps;
    font-style:         normal;
    color:              #900;
}

h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
    border: none;
}

dfn {
    font-weight:    bold;
}

a.internalDFN {
    color:  inherit;
    border-bottom:  1px solid #99c;
    text-decoration:    none;
}

a.externalDFN {
    color:  inherit;
    border-bottom:  medium dotted #ccc;
    text-decoration:    none;
}

a.bibref {
    text-decoration:    none;
}

code {
    color:  #ff4500;
}


/* --- WEB IDL --- */
pre.idl {
    border-top: 1px solid #90b8de;
    border-bottom: 1px solid #90b8de;
    padding:    1em;
    line-height:    120%;
}

pre.idl::before {
    content:    "WebIDL";
    display:    block;
    width:      150px;
    background: #90b8de;
    color:  #fff;
    font-family:    initial;
    padding:    3px;
    font-weight:    bold;
    margin: -1em 0 1em -1em;
}

.idlType {
    color:  #ff4500;
    font-weight:    bold;
    text-decoration:    none;
}

/*.idlModule*/
/*.idlModuleID*/
/*.idlInterface*/
.idlInterfaceID {
    font-weight:    bold;
    color:  #005a9c;
}

.idlSuperclass {
    font-style: italic;
    color:  #005a9c;
}

/*.idlAttribute*/
.idlAttrType, .idlFieldType {
    color:  #005a9c;
}
.idlAttrName, .idlFieldName {
    color:  #ff4500;
}
.idlAttrName a, .idlFieldName a {
    color:  #ff4500;
    border-bottom:  1px dotted #ff4500;
    text-decoration: none;
}

/*.idlMethod*/
.idlMethType {
    color:  #005a9c;
}
.idlMethName {
    color:  #ff4500;
}
.idlMethName a {
    color:  #ff4500;
    border-bottom:  1px dotted #ff4500;
    text-decoration: none;
}

/*.idlParam*/
.idlParamType {
    color:  #005a9c;
}
.idlParamName {
    font-style: italic;
}

.extAttr {
    color:  #666;
}

/*.idlConst*/
.idlConstType {
    color:  #005a9c;
}
.idlConstName {
    color:  #ff4500;
}
.idlConstName a {
    color:  #ff4500;
    border-bottom:  1px dotted #ff4500;
    text-decoration: none;
}

/*.idlException*/
.idlExceptionID {
    font-weight:    bold;
    color:  #c00;
}

.idlTypedefID, .idlTypedefType {
    color:  #005a9c;
}

.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
    color:  #c00;
    font-weight:    normal;
}

.excName a {
    font-family:    monospace;
}

.idlRaises a.idlType, .excName a.idlType {
    border-bottom:  1px dotted #c00;
}

.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
    width:  45px;
    text-align: center;
}
.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }

.idlImplements a {
    font-weight:    bold;
}

dl.attributes, dl.methods, dl.constants, dl.fields {
    margin-left:    2em;
}

.attributes dt, .methods dt, .constants dt, .fields dt {
    font-weight:    normal;
}

.attributes dt code, .methods dt code, .constants dt code, .fields dt code {
    font-weight:    bold;
    color:  #000;
    font-family:    monospace;
}

.attributes dt code, .fields dt code {
    background:  #ffffd2;
}

.attributes dt .idlAttrType code, .fields dt .idlFieldType code {
    color:  #005a9c;
    background:  transparent;
    font-family:    inherit;
    font-weight:    normal;
    font-style: italic;
}

.methods dt code {
    background:  #d9e6f8;
}

.constants dt code {
    background:  #ddffd2;
}

.attributes dd, .methods dd, .constants dd, .fields dd {
    margin-bottom:  1em;
}

table.parameters, table.exceptions {
    border-spacing: 0;
    border-collapse:    collapse;
    margin: 0.5em 0;
    width:  100%;
}
table.parameters { border-bottom:  1px solid #90b8de; }
table.exceptions { border-bottom:  1px solid #deb890; }

.parameters th, .exceptions th {
    color:  #fff;
    padding:    3px 5px;
    text-align: left;
    font-family:    initial;
    font-weight:    normal;
    text-shadow:    #666 1px 1px 0;
}
.parameters th { background: #90b8de; }
.exceptions th { background: #deb890; }

.parameters td, .exceptions td {
    padding:    3px 10px;
    border-top: 1px solid #ddd;
    vertical-align: top;
}

.parameters tr:first-child td, .exceptions tr:first-child td {
    border-top: none;
}

.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
    width:  100px;
}

.parameters td.prmType {
    width:  120px;
}

table.exceptions table {
    border-spacing: 0;
    border-collapse:    collapse;
    width:  100%;
}

/* --- TOC --- */
.toc a {
    text-decoration:    none;
}

a .secno {
    color:  #000;
}

/* --- TABLE --- */
table.simple {
    border-spacing: 0;
    border-collapse:    collapse;
    border-bottom:  3px solid #005a9c;
}

.simple th {
    background: #005a9c;
    color:  #fff;
    padding:    3px 5px;
    text-align: left;
}

.simple th[scope="row"] {
    background: inherit;
    color:  inherit;
    border-top: 1px solid #ddd;
}

.simple td {
    padding:    3px 10px;
    border-top: 1px solid #ddd;
}

.simple tr:nth-child(even) {
    background: #f0f6ff;
}

/* --- DL --- */
.section dd > p:first-child {
    margin-top: 0;
}

.section dd > p:last-child {
    margin-bottom: 0;
}

.section dd {
    margin-bottom:  1em;
}

.section dl.attrs dd, .section dl.eldef dd {
    margin-bottom:  0;
}

/* --- EXAMPLES --- */
pre.example {
    border-top: 1px solid #ff4500;
    border-bottom: 1px solid #ff4500;
    padding:    1em;
    margin-top: 1em;
}

pre.example::before {
    content:    "Example";
    display:    block;
    width:      150px;
    background: #ff4500;
    color:  #fff;
    font-family:    initial;
    padding:    3px;
    font-weight:    bold;
    margin: -1em 0 1em -1em;
}

/* --- EDITORIAL NOTES --- */
.issue {
    padding:    1em;
    margin: 1em 0em 0em;
    border: 1px solid #f00;
    background: #ffc;
}

.issue::before {
    content:    "Issue";
    display:    block;
    width:  150px;
    margin: -1.5em 0 0.5em 0;
    font-weight:    bold;
    border: 1px solid #f00;
    background: #fff;
    padding:    3px 1em;
}

.note {
    margin: 1em 0em 0em;
    padding:    1em;
    border: 2px solid #cff6d9;
    background: #e2fff0;
}

.note::before {
    content:    "Note";
    display:    block;
    width:  150px;
    margin: -1.5em 0 0.5em 0;
    font-weight:    bold;
    border: 1px solid #cff6d9;
    background: #fff;
    padding:    3px 1em;
}

.editorsnote::before {
    
    content:    "Editor's Note";
    display:    block;
	width:      150px;
    background: #F30023;
    color:  #fff;
    margin: -1.5em 0 0.5em 0;
    font-weight:    bold;
    border: 1px solid #cff6d9;
    padding:    3px 1em;
}
.editorsnote {
    margin: 1em 0em 0em;
    padding:    1em;
    border: 2px solid #cff6d9;
}


/* --- Best Practices --- */
div.practice {
    border: solid #bebebe 1px;
    margin: 2em 1em 1em 2em;
}

span.practicelab {
    margin: 1.5em 0.5em 1em 1em;
    font-weight: bold;
    font-style: italic;
}

span.practicelab   { background: #dfffff; }

span.practicelab {
    position: relative;
    padding: 0 0.5em;
    top: -1.5em;
}

p.practicedesc {
    margin: 1.5em 0.5em 1em 1em;
}

@media screen {
    p.practicedesc {
        position: relative;
        top: -2em;
        padding: 0;
        margin: 1.5em 0.5em -1em 1em;
}

</style>

<link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8"></head>

<body style="display: inherit; ">
<div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p>
<h1 class="title" id="title">Points of Interest Core</h1>
<h2 id="w3c-editor-s-draft-12-may-2011">W3C Working Draft 12 May 2011</h2>
<dl>
<dt>This version:</dt>
<dd><a href="http://www.w3.org/TR/2011/WD-poi-core-20110512/">http://www.w3.org/TR/2011/WD-poi-core-20110512/</a></dd>
<dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/poi-core/">http://www.w3.org/TR/poi-core/</a></dd>
<dt>Previous version:</dt>
<dd>none</dd>
<dt>Editor:</dt>
<dd><span>Matt Womer</span></dd>
</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><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>
    <div id="abstract" class="introductory section"><h2>Abstract</h2>
	This document describes a data model and XML syntax for representing  information about points of interest (POI) on the World Wide Web.  
    </div>
	<div id="sotd" class="introductory section">
	<h2>
	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 published by the <a href="http://www.w3.org/2010/POI/">Points of Interest Working Group</a> as a First Public Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-poiwg@w3.org">public-poiwg@w3.org</a> (<a href="mailto:public-poiwg-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-poiwg/">archives</a>). All feedback is welcome.
	</p>
	<p>As a First Public Working Draft, this document is intended to encourage discussion and should not be considered complete. Within the document there are Editor's notes formatted thusly:
	</p>
	<p class="editorsnote">This is an example of an Editor's Note</p>
	<p>These notes reflect areas that need particular attention, an issue raised about in the <a href="/2010/POI/track/issues/raised">POI tracker</a> or may not have been written at all.  Feedback on these areas is particularly appreciated.</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>
	<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>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/45386/status" rel="disclosure">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 of the W3C Patent Policy</a>.
	</p>
	</div>


<div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">2. </span>Terminology</a></li><li class="tocline"><a href="#poi-data-model" class="tocxref"><span class="secno">3. </span>POI Data Model</a><ul class="toc"><li class="tocline"><a href="#geo-reference" class="tocxref"><span class="secno">3.1 </span>Geo-reference</a><ul class="toc"><li class="tocline"><a href="#center" class="tocxref"><span class="secno">3.1.1 </span>Center</a></li><li class="tocline"><a href="#navigation-point" class="tocxref"><span class="secno">3.1.2 </span>Navigation Point</a></li><li class="tocline"><a href="#address" class="tocxref"><span class="secno">3.1.3 </span>Address</a></li><li class="tocline"><a href="#route" class="tocxref"><span class="secno">3.1.4 </span>Route</a></li><li class="tocline"><a href="#area" class="tocxref"><span class="secno">3.1.5 </span>Area</a></li><li class="tocline"><a href="#object" class="tocxref"><span class="secno">3.1.6 </span>Object</a></li><li class="tocline"><a href="#undetermined" class="tocxref"><span class="secno">3.1.7 </span>Undetermined</a></li><li class="tocline"><a href="#relative" class="tocxref"><span class="secno">3.1.8 </span>Relative</a></li><li class="tocline"><a href="#map" class="tocxref"><span class="secno">3.1.9 </span>Map</a></li></ul></li><li class="tocline"><a href="#location" class="tocxref"><span class="secno">3.2 </span>Location</a><ul class="toc"><li class="tocline"><a href="#contains" class="tocxref"><span class="secno">3.2.1 </span>Contains</a></li></ul></li><li class="tocline"><a href="#relationship-primitive" class="tocxref"><span class="secno">3.3 </span>Relationship primitive</a><ul class="toc"><li class="tocline"><a href="#contained-within" class="tocxref"><span class="secno">3.3.1 </span>contained-within</a></li><li class="tocline"><a href="#contains-1" class="tocxref"><span class="secno">3.3.2 </span>contains</a></li><li class="tocline"><a href="#adjacent-to" class="tocxref"><span class="secno">3.3.3 </span>adjacent-to</a></li></ul></li><li class="tocline"><a href="#string-primitive" class="tocxref"><span class="secno">3.4 </span>string primitive</a></li><li class="tocline"><a href="#label-primitive" class="tocxref"><span class="secno">3.5 </span>Label primitive</a></li><li class="tocline"><a href="#id-primitive" class="tocxref"><span class="secno">3.6 </span>ID primitive</a></li><li class="tocline"><a href="#categorization-primitive" class="tocxref"><span class="secno">3.7 </span>Categorization primitive</a></li><li class="tocline"><a href="#meta-data-primitive" class="tocxref"><span class="secno">3.8 </span>meta data primitive</a></li><li class="tocline"><a href="#time-primitive" class="tocxref"><span class="secno">3.9 </span>Time primitive</a></li></ul></li><li class="tocline"><a href="#xml-syntax" class="tocxref"><span class="secno">4. </span>XML Syntax</a><ul class="toc"><li class="tocline"><a href="#xml-notation" class="tocxref"><span class="secno">4.1 </span>XML Notation</a></li><li class="tocline"><a href="#pois--element" class="tocxref"><span class="secno">4.2 </span><code>&lt;pois&gt;</code> element</a></li><li class="tocline"><a href="#poi--element" class="tocxref"><span class="secno">4.3 </span><code>&lt;poi&gt;</code> element</a></li><li class="tocline"><a href="#representing-coordinates" class="tocxref"><span class="secno">4.4 </span>Representing coordinates</a><ul class="toc"><li class="tocline"><a href="#point--element" class="tocxref"><span class="secno">4.4.1 </span><code>&lt;point&gt;</code> element</a></li></ul></li><li class="tocline"><a href="#location--element" class="tocxref"><span class="secno">4.5 </span><code>&lt;location&gt;</code> element</a><ul class="toc"><li class="tocline"><a href="#center--element" class="tocxref"><span class="secno">4.5.1 </span><code>&lt;center&gt;</code> element</a></li><li class="tocline"><a href="#address--element" class="tocxref"><span class="secno">4.5.2 </span><code>&lt;address&gt;</code> element </a></li><li class="tocline"><a href="#navigation-point--element" class="tocxref"><span class="secno">4.5.3 </span><code>&lt;navigation-point&gt;</code> element</a></li><li class="tocline"><a href="#area--element" class="tocxref"><span class="secno">4.5.4 </span><code>&lt;area&gt;</code> element</a></li><li class="tocline"><a href="#object--element" class="tocxref"><span class="secno">4.5.5 </span><code>&lt;object&gt;</code> element</a></li><li class="tocline"><a href="#undetermined--element" class="tocxref"><span class="secno">4.5.6 </span><code>&lt;undetermined&gt;</code> element</a></li><li class="tocline"><a href="#relative--element" class="tocxref"><span class="secno">4.5.7 </span><code>&lt;relative&gt;</code> element</a></li><li class="tocline"><a href="#map--element" class="tocxref"><span class="secno">4.5.8 </span><code>&lt;map&gt;</code> element</a></li></ul></li><li class="tocline"><a href="#relationship--element" class="tocxref"><span class="secno">4.6 </span><code>&lt;relationship&gt;</code> element</a></li><li class="tocline"><a href="#label--element" class="tocxref"><span class="secno">4.7 </span><code>&lt;label&gt;</code> element</a></li><li class="tocline"><a href="#id-representation" class="tocxref"><span class="secno">4.8 </span>id representation</a></li><li class="tocline"><a href="#category--element" class="tocxref"><span class="secno">4.9 </span><code>&lt;category&gt;</code> element</a></li><li class="tocline"><a href="#meta-data" class="tocxref"><span class="secno">4.10 </span>Meta-data</a></li><li class="tocline"><a href="#time--element" class="tocxref"><span class="secno">4.11 </span><code>&lt;time&gt;</code> element</a></li><li class="tocline"><a href="#xml-example" class="tocxref"><span class="secno">4.12 </span>XML Example</a></li><li class="tocline"><a href="#xml-schema" class="tocxref"><span class="secno">4.13 </span>XML Schema</a></li></ul></li><li class="tocline"><a href="#use-cases" class="tocxref"><span class="secno">A. </span>Use Cases</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">B. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
    
    <div id="introduction" class="section">
      <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
      <p>In general terms, a "point of interest" is a location about which information is available.  A POI can be as simple as a set of coordinates and an identifier, or more complex such as a three dimensional model of a building with names in various languages, information about open and closed hours, and a civic address.  POI data has many uses including augmented reality browsers, location-based social networking games, geocaching, mapping, and navigation systems.</p>
	<p>POI data has traditionally been exchanged in proprietary formats via various transports.  This specification defines a flexible, lightweight, extensible POI data model, and one normative syntax for the data model.  This will enable content publishers to effectively describe and efficiently serve and exchange POI data.  In addition to the data model and format, this specification includes best practices for how to organize and serve POIs on the Web.
	</p>
	<p>To achieve these goals, this document describes a generic data model and one normative format.  This format is based on XML and is likely insufficient to cover all POI use cases, therefore, it is expected that the data model will be mapped to other formats, such as JSON, GML, RDF, GeoRSS, or  HTML.
	</p>
	<p class="editorsnote">This section will be fleshed out in more detail for the next draft</p>
	</div>
	<div id="terminology" class="section">
		<!--OddPage--><h2><span class="secno">2. </span>Terminology</h2>
	<p>The term <dfn id="dfn-points-of-interest">points of interest</dfn> is used in a broad sense in this specification to refer to a loosely coupled and inter-related set of terms: locations, POIs and places.
	</p>
	<p class="editorsnote">This section is primarily based on the <a href="http://www.w3.org/2010/POI/wiki/Main_Page">wiki home page definition of POI</a>.
	</p>
	
	
	<dl>
		<dt>Location</dt>
	<dd>
		The term <dfn id="dfn-location">location</dfn> is used to refer to a geographical construct, a physically fixed point, typically on the surface of the Earth (relative to WGS-84), though locations can be relative to another coordinate system.  Locations can be a single point, a centroid, a minimum bounding rectangle, or a set of vectors.  A location should be persistent over time and does not change.

			<p class="editorsnote">OGC <a href="http://lists.w3.org/Archives/Public/public-poiwg/2011May/0028">has suggested</a> the following changes to the definition of location:<br />
				<em>"FYI, Point of Interest is defined in the OGC Open Location Services standard as:
		<br>
				A location (with a fixed position) where one can find a place, product or service, typically identified by name rather than by address and characterized by type, which may be used as a reference point or a target in a location based service request, e.g., as the destination of a route.
		<br>
				The definition for “Location” should be harmonized with ISO standards terms and definitions. Also, a specified coordinate reference system (WGS 84) should not be mentioned in a definition. The specification and handling of CRS should be later in the document. So, the definition of Location becomes:
		<br>
				Location: Identifiable geographic place . Typically a location is a physically fixed point, typically on the surface of the Earth, though locations can be relative to other, non-earth centric coordinate reference systems. Locations can be a single point, a centroid, a minimum bounding rectangle, or a set of vectors. A location should be persistent over time and does not change.
				"</em>
				</p>
	</dd>

	<dt>Points of Interest</dt>
	
	<dd>
		Unlike the term location, the term <dfn id="dfn-poi">POI</dfn> is a human construct.  POIs describe information about locations such as name, category, unique identifier, or civic address.
	</dd>
	<dt>Places</dt>
	<dd>A <dfn id="dfn-place">place</dfn> is also a human construct which typically has a coarse level of spatial granularity. Places are generally larger scale administrative constructs, either informally or formally defined. Countries, states, counties, districts, neighborhoods and postal codes or telephone area codes are all places. Places are also informally or colloquially defined, such as the Home Counties in the United Kingdom and the Bay Area in the United States.</dd>
	<dd>
		Places have spatial relationships; with parents, children, adjacencies and contained by semantics. Places also have the same attribute set as POIs, although with differing interpretations based on scale; for example, the address of a Place or its URI would refer to the address of the administrative or governing body of the place.
		</dd>
	<dd>
	A place typically contains multiple POIs and can also be coterminous with a POI. In the former case, a place, such as a city or a neighborhood, will contain multiple POIs. In the latter case, a place and a POI will occupy the same position and extent, such as in the case of Yellowstone National Park, which is both a Place and a POI.
	</dd>
	<dt>Primitive</dt>
	<dd>
		The term <dfn id="dfn-primitive">primitive</dfn> refers to the basic components of a POI.  For example, a POI could be a collection of location and category primitives.
	</dd>
	<dt>Coordinate</dt>
	<dd>
	The term <dfn id="dfn-coordinate">coordinate</dfn> refers to one of a sequence of n numbers designating the position of a point in n-dimensional space .
	</dd>
	<dt>Coordinate Reference System</dt>
	<dd>
	The term <dfn id="dfn-coordinate-reference-system">coordinate reference system</dfn> refers to a coordinate system that is related to an object by a datum .
	</dd>

	<dt>Coordinate System</dt>
	<dd>The term <dfn id="dfn-coordinate-system">coordinate system</dfn> refers to a set of mathematical rules for specifying how coordinates are to be assigned to points .
	</dd>

	<dt>Datum</dt>
	<dd>
	The term <dfn id="dfn-datum">datum</dfn> refers to a parameter or set of parameters that define the position of the origin, the scale, and the orientation of a coordinate system .
	</dd>

	<dt>Geolocation</dt>
	<dd>
		The term <dfn id="dfn-geolocation">geolocation</dfn> refers to the identification of the real world geographic location of an object.
	</dd>

	<dt>Point</dt>
	<dd>
	The term <dfn id="dfn-point">point</dfn> refers to a 0-dimensional geometric primitive, representing a position . 
	</dd>

	<dt>Position</dt>
	<dd>
		The term <dfn id="dfn-position">position</dfn> refers to a data type that describes a point or geometry potentially occupied by an object or person .
	</dd>


	<dt>Route</dt>
	<dd>
	The term <dfn id="dfn-route">route</dfn> refers to a sequence of links and / or partial links that describe a path, usually between two positions, within a network .
	</dd>

	
	</dl>
	
	
	
    </div>

    <div id="poi-data-model" class="section">
	<!--OddPage--><h2><span class="secno">3. </span>POI Data Model</h2>
	<p>The following primitives can be combined to represent a POI.</p>
	<p class="editorsnote">This section will have a graphic representing the data model for next draft</p>
	
	<div id="geo-reference" class="section">
		<h3><span class="secno">3.1 </span>Geo-reference</h3>
		<p class="editorsnote">Geo-references are used a lot and were difficult to introduce just in the middle of the location primitive, so it got a promotion, even though it only appears in the location primitive.</p>
		<p>A <dfn id="dfn-geo-reference">geo-reference</dfn> is a reference to a location.  A geo-reference can represent location in a variety of ways, such as the geospatial coordinates for the center of the POI, a civic address, an area (simple bounding box, or a polygon, or a 3d object), relative to a particular map or other geo-reference or undetermined.  Geo-references are used in the <a href="#location">location primitive</a>.
		</p>
		<p>A geo-reference is of one of the following types:</p>
		<div id="center" class="section">
		<h4><span class="secno">3.1.1 </span>Center</h4>
		<p>The <dfn id="dfn-center">Center</dfn> geo-reference locates the center point of the POI.  This type is largely used for display purposes.</p>
		<h6 id="contains-2">Contains</h6>
		<table class="simple">
			<thead>
				<tr><th>Name</th>
				<th>Required</th>
				<th>Details</th>
			</tr></thead>
			<tbody>
				<tr><td>Coordinates</td>
				<td>required</td></tr>
				<tr><td>System</td>
				<td>optional</td> <td>If not specified WGS 84 is assumed</td></tr>
				<tr><td>Longitude</td>
				<td>required</td><td></td></tr>
				<tr><td>Latitude</td>
				<td>required</td><td></td></tr>
				<tr><td>Altitude</td>
				<td>optional</td><td>Defines the height in meters above or below sea level</td></tr>
			</tbody>
			
		</table>
		<p class="editorsnote">OGC has recommended the term geolocation instead of georeference:<br>
			Georeference – While geo-reference is a valid term, geo-reference typically indicates that a geometry or an image has coordinate reference system metadata. The suggested term is geolocation as this term is used extensively in other standards work, including the work of the W3C.
		</p></div>
		<div id="navigation-point" class="section">
		<h4><span class="secno">3.1.2 </span>Navigation Point</h4>
			<p>A <dfn id="dfn-navigation-point">Navigation Point</dfn> geo-reference is to a point that is the logical destination for routing.  For example, this may be a reference to the entrance of parking lot POI.</p>
		<h6 id="contains-3">Contains</h6>
		<table class="simple">
			<thead>
				<tr><th>Name</th>
				<th>Required</th>
				<th>Details</th>
			</tr></thead>
			<tbody>
				<tr><td>Coordinates</td><td>required</td><td></td></tr>
			</tbody>
		</table>
		</div>
		<div id="address" class="section">
			<h4><span class="secno">3.1.3 </span>Address</h4>
			<p class="editorsnote"><b>Note:</b>Support for addresses in the XML syntax has been dropped for the FPWD, but reminds here in the data model.</p>
			<p>An <dfn id="dfn-address">Address</dfn> geo-reference is a civic address, such as a mailing address or a street address.</p>
		<h6 id="contains-4">Contains</h6>
		<table class="simple">
			<thead>
				<tr><th>Name</th>
				<th>Required</th>
				<th>Details</th>
			</tr></thead>
			<tbody>
				
				<tr><td>Country</td>
				<td>required</td><td>ISO country code (ISO 3166-1 alpha-3 country code)</td></tr>
				<tr><td>Language</td>
				<td>required</td><td>xml:lang Language Code</td></tr>
				<tr><td>Street</td>
				<td>optional</td><td> Can contain a variable mix of house number prefix, suffix, street base name and or street type</td></tr>
				<tr><td>Floor</td>
				<td>optional</td><td> +/- number</td></tr>
				<tr><td>Suite</td>
				<td>optional</td><td></td></tr>
				<tr><td>Region</td>
				<td>optional</td><td>Repeating: can contain a variable mix of administrative regions, neighborhood, city, state, etc.</td></tr>
				<tr><td>Postal-code</td>
				<td>optional</td><td></td></tr>

			</tbody>
		</table>
		<p class="editorsnote">This is our first reference to language tags, should we use ISO 3166-1 or BCP 47/IETF RFC 5646?  It's been suggested to use xmllang, but do we need to specify this in the data model?  Probably, as we do want interchangeability between formats.</p>
		</div>
		<div id="route" class="section">
			
			<h4><span class="secno">3.1.4 </span>Route</h4>
			<p class="editorsnote">This section needs reworking.  Within the XML syntax there's a notion of a list of points, as well as a point type that is reused. In the Wiki draft Routes and Areas both have point lists, we should extract the point list concept out so it can be shared.</p>
			
			<p>Optional.   Represents routes and traces.</p>
			<h6 id="contains-5">Contains</h6>
			<dl>
		<dt>Point</dt>
		<dd>Required.   Repeating for a directed linked list of points</dd>
		<dt>Type</dt>
	<dd>Required.  One of : Start/End/way point</dd>
		<dt>Coordinates</dt>
	<dd>Required.</dd>
		</dl>
		</div>
		<div id="area" class="section">
		<h4><span class="secno">3.1.5 </span>Area</h4>
		<p>An <dfn id="dfn-area">Area</dfn> geo-reference represents a line-bounded area.  The area is described by an ordered list of coordinates, where the first and last are the same.</p>
		<p class="editorsnote">I changed this one a bit, instead of introducing Points, I just made it have Coordinates, and mention that it is an ordered list of them where the first and last are the same.  I figure the ordering can occur however such things happen in desired syntax (XML could be as they appear in document order or with an 'order' attribute, JSON may represent it as an array,etc)</p>

		<h6 id="contains-6">Contains</h6>
		<table class="simple">
			<thead>
				<tr><th>Name</th>
				<th>Required</th>
				<th>Details</th>
			</tr></thead>
			<tbody>
				<tr><td>Coordinates</td><td>required</td><td>An ordered list of Coordinates, minimum of three, first and last must be the same.</td></tr>
			</tbody>
		</table>

		</div>
	<div id="object" class="section">
		<h4><span class="secno">3.1.6 </span>Object</h4>
		<p class="editorsnote">The following paragraphs are adapted from <a href="http://lists.w3.org/Archives/Public/public-poiwg/2011Jan/0022.html">Christine Perey's email</a>.  Parts of this are related to collections of POIs/objects and is thus also related to <a href="http://www.w3.org/2010/POI/track/issues/28">ISSUE-28</a>.  <b>This section needs serious attention.</b>
		</p>
		<p>The <dfn id="dfn-object">Object</dfn> primitive provides a rich and flexible description of an object, which decouples the description of an object from where it is located.
		</p>
		<p>An Object <em class="rfc2119" title="may">may</em> have one location at a (temporary-duration undefined) specific point in time but does not have one fixed point over time.</p>
		<p>An Object of Interest can be a parent to other Objects each with its own description to allow for the representation of complex objects that are the aggregate of a collection of Objects (a car, boat, or airplane).
			</p>
		<p>It should not be inferred that each of the elements within the object primitive are not spatially synonymous, but do refer to the same object.</p>
		
		<p>Represents a 3D object, building, etc.</p>
		<h6 id="contains-7">Contains</h6>
		<table class="simple">
			<thead>
				<tr><th>Name</th>
				<th>Required</th>
				<th>Details</th>
			</tr>
			</thead>
			<tbody><tr><td><b>TBD</b></td</tr></tbody>
		</table>

	</div>
		<div id="undetermined" class="section">
			<h4><span class="secno">3.1.7 </span>Undetermined</h4>
	<p>An <dfn id="dfn-undetermined">Undetermined</dfn> geo-reference represents a location that as of yet is undetermined.  This can be used to describe a Place prior to the final location being resolved.</p>
	<p>There are no members for an Undetermined geo-reference.</p>
		</div>
		
		<div id="relative" class="section">
		<h4><span class="secno">3.1.8 </span>Relative</h4>
		<p class="editorsnote">I made relative a member of geo-reference rather than a sub-member of the map geo-reference, as it seems useful outside of the map scope</p>
		<p>A <dfn id="dfn-relative">Relative</dfn> geo-reference is described in terms of distance from and bearing to another location.</p>
		<table class="simple">
			<thead>
				<tr><th>Name</th>
				<th>Required</th>
				<th>Details</th>
			</tr></thead>
			<tbody>
				<tr><td>Relative-Location-Object</td>
				<td>required</td><td>ID or location object (ID) this relative reference refers to</td></tr>
				<tr><td>Distance-From</td><td>required</td><td></td></tr>
				<tr><td>Bearing-To</td><td>required</td><td></td></tr>
				<tr><td>Relative height</td><td>optional</td><td></td></tr>

			</tbody>
		</table>
	</div>
		<div id="map" class="section">
			<h4><span class="secno">3.1.9 </span>Map</h4>
			<p class="editorsnote">Map georeference type has been dropped from the FPWD until it is better understood.</p>
<!--			
			<p>The <dfn>Map</dfn> geo-reference allows points to be associated to maps.</p>
			<h6>Contains</h6>
			<table class="simple">
			<thead>
				<th>Name</th>
				<th>Required</th>
				<th>Details</th>
			</thead>
			<tbody>
			
				<tr><td>Supplier</td>
			<td>required</td><td>The supplier of the map</td></tr>
				<tr><td>Version</td>
			<td>required</td><td>The version of the map</td></tr>
				<tr><td>Map-Object-ID</td><td>required</td><td>A unique identifier for the map</td></tr>
				<tr><td>Side</td>
			<td>optional</td><td>side of street, left / right / end</td></tr>
				<tr><td>Spot</td><td>optional</td><td> % distance from the Map object’s reference end-point</td>

				<tr><td>Relative</td>
			<td>optional</td><td>repeating. For representing a relative reference as opposed to an absolute geo-spatial location</td></tr>
				<tr><td>Reference-type</td>
			<td>required</td><td>One of the geo-references, excluding Map</td></tr>
			</tr>
			</tbody>
			</table>
			-->
			</div>

	</div>
	
	<div id="location" class="section">
	<h3><span class="secno">3.2 </span>Location</h3>
	<p>
		The <dfn id="dfn-location-1">location</dfn> primitive provides a rich and flexible description of the location of a POI.  A location is a required part of a POI.
	</p>
	<div id="contains" class="section">
		<h4><span class="secno">3.2.1 </span>Contains</h4>
		
		<table class="simple">
			<thead>
				<tr><th>Name</th>
				<th>Required</th>
				<th>Details</th>
			</tr></thead>
			<tbody>

	<tr><td>Identifier</td><td>required</td><td>A unique identifier for this location.</td></tr>
	<tr><td>Geo-reference</td><td>required</td><td>A reference to the actual location
	</td></tr>
	</tbody>
</table>
	<p class="editorsnote">I didn't follow the definition of a location identifier, so details were removed</p>
</div>
</div>
	
	<div id="relationship-primitive" class="section">
	<h3><span class="secno">3.3 </span>Relationship primitive</h3>
	<p>
		The <dfn id="dfn-relationship">relationship</dfn> primitive establishes 1-to-1 or 1-to-many relationships between POIs.
	</p>
	<p>A relationship may be one of the following:</p>
	<dl>
		<dt>contained-within</dt>
		<dd>A POI which is entirely contained within another POI, e.g. a POI describing a store may state that it is contained within a shopping mall</dd>
		
		<dt>contains</dt>
		<dd>A POI which entirely contains another POI, e.g. a POI describing a mall may state that it contains POIs for each store that is within the mall</dd>
		
		<dt>adjacent-to</dt>
		<dd>A POI which is physically adjacent to another POI, e.g. a POI representing a store within a mall may state that it is next door to another POI which represents the store next door</dd>
		<dt>...</dt>
		<dd><p class="editorsnote">Need more relationship types</p>
	</dd></dl>
	<p class="editorsnote">Should the details of the various relationship types themselves be in this section? Assuming yes for now</p>
	
	<div id="contained-within" class="section">
	<h4><span class="secno">3.3.1 </span>contained-within</h4>
	<p class="editorsnote">todo</p>
	</div>
	
	<div id="contains-1" class="section">
	<h4><span class="secno">3.3.2 </span>contains</h4>
	<p class="editorsnote">todo</p>
	</div>
	
	<div id="adjacent-to" class="section">
	<h4><span class="secno">3.3.3 </span>adjacent-to</h4>
	<p class="editorsnote">todo</p>
	</div>
	
	</div>

	<div id="string-primitive" class="section">
		<h3><span class="secno">3.4 </span>string primitive</h3>
		<p class="editorsnote">Dropped per our discussion at f2f</p>
	</div>
	<div id="label-primitive" class="section">
		<h3><span class="secno">3.5 </span>Label primitive</h3>
		<p>POIs may have zero or more label primitives which represent a human readable label.</p>
		<p class="editorsnote">At F2F2 we decided to rename the name primitive to "label", and to allow labels to be marked as primary for each language represented.</p>
	</div>
	<div id="id-primitive" class="section">
		<h3><span class="secno">3.6 </span>ID primitive</h3>
		<p>POI must have an "id" primitive. It unambiguously identifies a POI within a particular implementation.</p>
		<p class="editorsnote">At F2F2 we discussed using URI fragments as IDs, as in XML.  Using XML Base we could build a full URI that could then be used to identify the entire POI.</p>
	</div>
	
	<div id="categorization-primitive" class="section">
		<h3><span class="secno">3.7 </span>Categorization primitive</h3>
		<p>POI <em class="rfc2119" title="may">may</em> have a "categorization" primitive, with one or more category identifiers.</p>
		<p class="editorsnote">Todo</p>
	</div>
	<div id="meta-data-primitive" class="section">
		<h3><span class="secno">3.8 </span>meta data primitive</h3>
		<p class="editorsnote">Todo.  We haven't decided how this would work, and why this wouldn't just be covered by our extensibility story.  Please see: <a href="http://www.w3.org/2010/POI/track/issues/18">ISSUE-18</a>.</p>
	</div>
	<div id="time-primitive" class="section">
		<h3><span class="secno">3.9 </span>Time primitive</h3>
		<p>POI <em class="rfc2119" title="may">may</em> have one or more time primitives that represent an individual point in time, a span of time, or a recurring time or time span.</p>
	</div>
		
	</div> <!-- end Data Model section -->
	
	
	
	
	
	
	
	
	
	<div id="xml-syntax" class="section">
		<!--OddPage--><h2><span class="secno">4. </span>XML Syntax</h2>
		<p class="editorsnote">Even more so than the rest of this document, this section is a <a href="http://en.wikipedia.org/wiki/Straw_man_proposal"><b>straw man</b></a>  proposal, so please treat it as such!<br>
			</p>
		<p>This section describes an XML syntax to represent the data model.</p>
		<div id="xml-notation" class="section">
			<h3><span class="secno">4.1 </span>XML Notation</h3>
			<p>The following data types are from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema, Part 2: Datatypes</a> [XMLSCHEMA11-2].  The meanings are provided here as a convenience, for more complete information refer to the XML Schema, Part 2: Datatypes Recommendation.</p>
			<table class="simple">
				<thead> <tr> <th>Notation</th> <th>Meaning</th> </tr> </thead>
				<tbody>			
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#boolean">boolean</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#boolean"></a></td><td>has the ·value space· required to support the mathematical concept of binary-valued logic: {true, false}</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#decimal">decimal</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#decimal"></a></td><td>a subset of the real numbers, which can be represented by decimal numerals</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#float">float</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#float"></a></td><td>patterned after the IEEE single-precision 32-bit floating point type [IEEE 754-1985].</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#double">double</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#double"></a></td><td>atterned after the IEEE double-precision 64-bit floating point type [IEEE 754-1985]. </td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#duration">duration</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#duration"></a></td><td>represents a duration of time.</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#dateTime">dateTime</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#dateTime"></a></td><td> may be viewed as objects with integer-valued year, month, day, hour and minute properties, a decimal-valued second property, and a boolean timezoned property. Each such object also has one decimal-valued method or computed property, timeOnTimeline, whose value is always a decimal number; the values are dimensioned in seconds, the integer 0 is 0001-01-01T00:00:00 and the value of timeOnTimeline for other dateTime values is computed using the Gregorian algorithm as modified for leap-seconds</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#time">time</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#time"></a></td><td>represents an instant of time that recurs every day</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#date">date</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#date"></a></td><td> consists of top-open intervals of exactly one day in length on the timelines of dateTime, beginning on the beginning moment of each day (in each timezone), i.e. '00:00:00', up to but not including '24:00:00' (which is identical with '00:00:00' of the next day)</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#gYearMonth">gYearMonth</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#gYearMonth"></a></td><td>represents a specific gregorian month in a specific gregorian year.</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#gYear">gYear</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#gYear"></a></td><td>represents a gregorian calendar year</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#gMonthDay">gMonthDay</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#gMonthDay"></a></td><td>a  gregorian date that recurs, specifically a day of the year such as the third of May</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#gDay">gDay</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#gDay"></a></td><td>a gregorian day that recurs, specifically a day of the month such as the 5th of the month</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#gMonth">gMonth</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#gMonth"></a></td><td>gregorian month that recurs every year</td></tr>
				<tr><td><em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#anyURI">anyURI</a></em><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#anyURI"></a></td><td>represents a Uniform Resource Identifier Reference (URI). An anyURI value can be absolute or relative, and may have an optional fragment identifie</td></tr>
				</tbody>
				
			</table>
			
			
			<p class="editorsnote">We need to figure out: xml id/xml:base, xml:lang, units of measurement</p>

		</div> <!-- end notation section-->
		<div id="pois--element" class="section">
			<h3><span class="secno">4.2 </span><code>&lt;pois&gt;</code> element</h3>
			<p>
				The root element for an POI in XML syntax is the <code>pois</code> element.  The <code>&lt;pois&gt;</code> element <em class="rfc2119" title="must">must</em> contain one or more <code>&lt;poi&gt;</code> elements.
				</p>
			<h6 id="attributes">Attributes</h6>
			<p>
				The <code>&lt;pois&gt;</code> element has <b>TBD</b> attributes.</p>
			<p class="editorsnote">We may not allow for collections of POIs, in which case there will be no pois element.</p>
			<p>The pois element could have attributes such as xml:lang and an id, but is there a case for more?  What's the right way to represent text-wise that lang and id's can be on all elements?</p>
		
		</div> <!-- end of POIs element section -->
		
		
		
		<div id="poi--element" class="section">
			<h3><span class="secno">4.3 </span><code>&lt;poi&gt;</code> element</h3>
			<p>The <code>&lt;poi&gt;</code> element encompasses all information about a single POI. The <code>&lt;poi&gt;</code> element <em class="rfc2119" title="must">must</em> contain one or more <code>&lt;location&gt;</code> elements, and <em class="rfc2119" title="may">may</em> contain one or more <code>&lt;label&gt;</code> and <code>&lt;category&gt;</code> elements.</p>
			
			<h6 id="attributes-1">Attributes</h6>
			
			<p class="editorsnote">see above note in the <code>&lt;pois&gt;</code> element about lang and id</p>
		</div> <!-- end of POI element section -->

	
		<div id="representing-coordinates" class="section">
			<h3><span class="secno">4.4 </span>Representing coordinates</h3>
			<p>Many of the elements described below rely on a coordinates as attributes.  In the interest of not repeating the definition, the following attributes are inferred whenever the <code>coordinate attributes</code> are referenced below.</p>
			
			<h6 id="attributes-2">Attributes</h6>
			<table class="simple">
				<thead>
					<tr><th>Name</th><th>Required</th><th>Type</th><th>Default value</th><th>Details</th>
				</tr></thead>
				<tbody>
					<tr><td>srsname</td><td>optional</td><td>anyURI</td><td>urn:ogc:def:crs:EPSG:6.6:4326</td><td>A URN as defined in OGC Definition identifier URNs in OGC namespace [OGC-07-092r1] of the geodetic system to which the latitude and longitude and altitude are relative</td></tr>
					<tr><td>longitude</td><td>required</td><td>number</td><td>None</td><td></td></tr>
					<tr><td>latitude</td><td>required</td><td>number</td><td>None</td><td></td></tr>
					<tr><td>altitude</td><td>optional</td><td>number</td><td>?? sea level relative to system?</td><td></td></tr>

				</tbody>

			</table>
			<p class="editorsnote">Is there an official geode tagging scheme, e.g. "wgs84", or "etrs89"? Apparently yes: http://portal.opengeospatial.org/files/?artifact_id=24045
			<br>
			Now tracked as issue: <a href="http://www.w3.org/2010/POI/track/issues/21">ISSUE-21</a>.
			<br>
			How does this effect the altitude attribute?
			</p>
			
			<div id="point--element" class="section">
			<h4><span class="secno">4.4.1 </span><code>&lt;point&gt;</code> element</h4>
			<p>The <code>&lt;point&gt;</code> element is used in many different geo-reference types below.  It represents a single set of coordinates, and can be ordered relative to other <code>&lt;point&gt;</code> elements within the parent element via the <code>order</code> attribute.</p>
			<p>The <code>&lt;point&gt;</code> element has no character data.</p>
			<h6 id="attributes-3">Attributes</h6>
			<p>The <code>&lt;point&gt;</code> element uses the <code>coordinate attributes</code>, and an <code>order</code> attribute.</p>
			<table class="simple">
				<thead>
					<tr><th>Name</th><th>Required</th><th>Type</th><th>Default value</th><th>Details</th>
				</tr></thead>
				<tbody>
					<tr><td>order</td><td>optional</td><td>unsigned-number</td><td>None</td><td>Applies only when a list of points is needed.  Within the parent element containing the point list, there must be one <code>&lt;point&gt;</code> with the order attribute set to '0', other <code>&lt;point&gt;</code> element's order attribute <em class="rfc2119" title="must">must</em> be unique and contiguous integers.  Each point element within a point list <em class="rfc2119" title="must">must</em> have the <code>order</code> attribute set.</td></tr>
					
				</tbody>
			</table>
			<p class="editorsnote">Do we want to use an order attribute?  Document order?  A single attribute with a list of comma separated coordinates?
				<br>
				Now tracked as: <a href="http://www.w3.org/2010/POI/track/issues/19">ISSUE-19: how should we represent points?</a> and a related issue: <a href="http://www.w3.org/2010/POI/track/issues/36">ISSUE-36: do we want to rely on document order?</a>.
				</p>
			</div> <!-- end of point element section -->

			</div> <!-- end of representing coordinates element section -->



			
		<div id="location--element" class="section">
			
			<h3><span class="secno">4.5 </span><code>&lt;location&gt;</code> element</h3>
			<p>The <code>&lt;location&gt;</code> element contains one or more geo-references elements (see below), and has no attributes or character data.</p>
			
			<h3 id="geo-reference-elements">Geo-reference elements</h3>
			<p>The following elements are the XML mapping for the geo-references outlined in the data model.  Geo-references are used only with in the <code>&lt;location&gt;</code> element.
			</p>
			<div id="center--element" class="section">
			<h4><span class="secno">4.5.1 </span><code>&lt;center&gt;</code> element</h4>
			<p>The <code>&lt;center&gt;</code> element has no character data, and only the <code>coordinate attributes</code>.</p>
			</div>
			
			
			<div id="address--element" class="section">
				<h4><span class="secno">4.5.2 </span><code>&lt;address&gt;</code> element </h4>
				<p class="editorsnote">Representing addresses is a tricky business, see Geolocation WG and IETF geopriv.<br>
					As such address will be moved to TBD in this draft.  This issue is now tracked as <a href="http://www.w3.org/2010/POI/track/issues/40">ISSUE-40</a>
				</p>
				
				<p class="editorsnote">Should there be a way to assign languages to addresses or parts of addresses?</p>
				<!--
				<p>The <code>&lt;address&gt;</code> element may contain one or more <code>&lt;region&gt;</code> elements.</p>
			
				
				<h6>Attributes</h6>
				<table class="simple">
					<thead>
						<th>Name</th><th>Required</th><th>Type</th><th>Default value</th><th>Details</th>
					</thead>
					<tbody>
						<tr><td>country</td><td>required</td><td>string</td><td>None</td><td>ISO country code (ISO 3166-1 alpha-3 country code)</td></tr>
						<tr><td>lang</td>
						<td>required</td><td>string</td><td>defaults to the language of the XML document</td><td></td></tr>
						<tr><td>street</td>
						<td>optional</td><td>string</td><td>None</td><td> Can contain a variable mix of house number prefix, suffix, street base name and or street type</td></tr>
						<tr><td>floor</td>
						<td>optional</td><td>string</td><td>None</td><td> +/- number</td></tr>
						<tr><td>suite</td><td>optional</td><td>string</td><td>None</td><td></td></tr>
						<tr><td>postal-code</td>
						<td>optional</td><td>string</td><td>None</td><td></td></tr>
						
					</tbody>
				</table>
				<section>
					<h5><code>&lt;region&gt;</code> element</h5>
					<p>The <code>&lt;region&gt;</code> element has no attributes and contains character data that...??</p>
				</section>
				-->
				
			</div> <!-- end of address section-->
			
			<div id="navigation-point--element" class="section">
				<h4><span class="secno">4.5.3 </span><code>&lt;navigation-point&gt;</code> element</h4>
				<p>The <code>&lt;navigation-point&gt;</code> element has no character data and only the <code>coordinate attributes</code>. 
			</p></div>
			
			<div id="area--element" class="section">
			<h4><span class="secno">4.5.4 </span><code>&lt;area&gt;</code> element</h4>
			<p>The <code>&lt;area&gt;</code> element <em class="rfc2119" title="must">must</em> contain three or more <code>&lt;point&gt;</code> elements.  The first and last points in an area point list must have the same latitude, longitude and altitude. The area element has no attributes.</p>
			</div>
		<div id="object--element" class="section">
			<h4><span class="secno">4.5.5 </span><code>&lt;object&gt;</code> element</h4>
			<p class="editorsnote">This geo-reference hasn't been written yet</p>

			<h6 id="attributes-4">Attributes</h6>
			<table class="simple">
				<thead>
					<tr><th>Name</th>
					<th>Required</th>
					<th>Type</th><th>Default value</th>
				</tr></thead>
				<tbody><tr><td><b>TBD</b></td</tr></tbody>
				
			</table>

		</div>
		
		<div id="undetermined--element" class="section">
			<h4><span class="secno">4.5.6 </span><code>&lt;undetermined&gt;</code> element</h4>
			<p>The <code>&lt;undetermined&gt;</code> element has no character data and no attributes. </p>
		</div>

		<div id="relative--element" class="section">
		<h4><span class="secno">4.5.7 </span><code>&lt;relative&gt;</code> element</h4>
		<p>The <code>&lt;relative&gt;</code> element has no character data.</p>
		<h6 id="attributes-5">Attributes</h6>
		<table class="simple">
			<thead>
				<tr><th>Name</th><th>Required</th><th>Type</th><th>Default value</th><th>Details</th>
			</tr></thead>
			<tbody>
				<tr><td>location-id</td><td>required</td><td>idref (not really, more of a xsd:anyURI as it can be external too)</td><td>None</td><td>The fragment identifier or URI of the object to which this location is relative.</td></tr>
				<tr><td>distance-from</td><td>required</td><td>integer</td><td>None</td><td>The distance this object is from the object referred to in the location-id attribute</td></tr>
				<tr><td>bearing-to</td><td>required</td><td>decimal</td><td>None</td><td>?? radians? degrees?</td></tr>
				<tr><td>relative-height</td><td>optional</td><td>integer</td><td>None</td><td></td></tr>
				
			</tbody>
		</table>
		</div>
			<div id="map--element" class="section">
				<h4><span class="secno">4.5.8 </span><code>&lt;map&gt;</code> element</h4>
				<p class="editorsnote">Map georeference type has been dropped from the FPWD until it is better understood, so the map element has been dropped as well.</p>
				<!--
				
				<p> The <code>&lt;map&gt;</code> element contains no character data and may contain one or more <code>&lt;relative&gt;</code> elements.</p>
				<h6>Attributes</h6>
				<table class="simple">
					<thead>
						<th>Name</th><th>Required</th><th>Type</th><th>Default value</th><th>Details</th>
					</thead>
					<tbody>
							<tr><td>supplier</td>
						<td>required</td><td>string</td><td>None</td><td></td></tr>
							<tr><td>version</td>
						<td>required</td><td>string</td><td>None</td><td></td></tr>
							<tr><td>map-ref</td><td>required</td><td>URI</td><td>None</td><td></td><td></td></tr>
							<tr><td>side</td>
						<td>optional</td><td>string</td><td>None</td><td></td></tr>
							<tr><td>spot</td><td>optional</td><td>string</td><td>None</td><td></td></tr>

							<tr><td>reference-type</td>
						<td>required</td><td>string</td><td>None</td><td>Must be one of: center, address, navigation-point, area, or object</td></tr>
						</tr>
						
					</tbody>
				</table>
				-->
				
			</div>

		</div>

		<div id="relationship--element" class="section">
		<h3><span class="secno">4.6 </span><code>&lt;relationship&gt;</code> element</h3>
		<p> The <code>&lt;relationship&gt;</code> element contains no character data.</p>
		
		<h6 id="attributes-6">Attributes</h6>
		<table class="simple">
			<thead>
				<tr><th>Name</th><th>Required</th><th>Type</th><th>Default value</th><th>Details</th>
			</tr></thead>
			<tbody>
				<tr><td>type</td><td>required</td><td>string</td><td>None</td><td><em class="rfc2119" title="must">must</em> be one of: "contained-within","adjacent-to", or "contains"</td></tr>
				<tr><td>relative-to</td><td>required</td><td>URI</td><td>None</td><td></td></tr>
			</tbody>
		</table>
		</div>

		<div id="label--element" class="section">
			<h3><span class="secno">4.7 </span><code>&lt;label&gt;</code> element</h3>
			<p class="editorsnote">Todo.  At the f2f we agreed it would be label instead of name, and that multiples can exist, and one per language can be marked as primary</p>
			
		</div>
		<div id="id-representation" class="section">
			<h3><span class="secno">4.8 </span>id representation</h3>
			<p class="editorsnote">At F2F2 we discussed using URI fragments as IDs, as in XML.  Using XML Base we could build a full URI that could then be used to identify the entire POI.</p>
		</div>

		<div id="category--element" class="section">
			<h3><span class="secno">4.9 </span><code>&lt;category&gt;</code> element</h3>
			<p>The <code>&lt;category&gt;</code> element is a child of the &lt;poi&gt; element.  It is used to identify a category scheme and a category within that scheme, as well as one or more labels for the category.</p>
			<p>The <code>&lt;category&gt;</code> element <em class="rfc2119" title="must">must</em> contain one or more &lt;label&gt; elements, and zero or more &lt;association&gt; elements.</p>
			<p class="editorsnote">
				See <a href="http://www.w3.org/2010/POI/track/issues/24">ISSUE-24</a>.<br>
				I adjusted the Atom category element, to support multiple human readable labels via label sub elements and I try to give some meaning to the term attribute when there is no scheme.
			</p>
			<h6 id="attributes-7">Attributes</h6>
			
			<table class="simple">
				<thead>
					<tr><th>Name</th><th>Required</th><th>Type</th><th>Default value</th><th>Details</th>
				</tr></thead>
				<tbody>
					<tr><td>scheme</td><td>optional</td><td>URI</td><td>None</td><td>URI that identifies the categorization scheme, does not need to be dereferencable </td></tr>
					<tr><td>term</td><td>required</td><td>string</td><td>None</td><td>The name of the category, in the context of the scheme, or when scheme is missing, it is relevant only as an opaque string to identify the category.</td></tr>
					
			</tbody></table>
		</div>
		<div id="meta-data" class="section">
			<h3><span class="secno">4.10 </span>Meta-data</h3>
			<p class="editorsnote">TBD.  See <a href="http://www.w3.org/2010/POI/track/issues/18">ISSUE-18</a>.</p>
		</div>
		<div id="time--element" class="section">
			<h3><span class="secno">4.11 </span><code>&lt;time&gt;</code> element</h3>
			<p class="editorsnote">We discussed at F2F2 basing this on other standards' time representations.  <br>
				This section now represents times as defined in XML Schema Datatypes.<br>
				This is <a href="http://www.w3.org/2010/POI/track/issues/26">ISSUE-26</a>.
			</p>
			<p>
				</p><h6 id="attributes-8">Attributes</h6>

				<table class="simple">
					<thead>
						<tr><th>Name</th><th>Required</th><th>Type</th><th>Default value</th><th>Details</th>
					</tr></thead>
					<tbody>
						<tr><td>scheme</td><td>optional</td><td>URI</td><td>None</td><td>URI that identifies the categorization scheme, does not need to be dereferencable </td></tr>
						<tr><td>term</td><td>required</td><td>string</td><td>None</td><td>The name of the category, in the context of the scheme, or when scheme is missing, it is relevant only as an opaque string to identify the category.</td></tr>

				</tbody></table>
				
		</div>
	<div id="xml-example" class="section">
		<h3><span class="secno">4.12 </span>XML Example</h3>
		<p class="editorsnote">This example was just something I generated while thinking through the XML syntax, it hasn't been updated to be in sync with what is in the document, so it may differ.</p>
		 <div><pre class="example">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;pois&gt;
	&lt;poi id="StataCenter" xml:lang="en-US" &gt;

		&lt;label primary="true" xml:lang="en-US"&gt;Stata Center&lt;/label&gt;
		&lt;label primary="true" xml:lang="es"&gt;Stata Centro&lt;/label&gt;
		&lt;label&gt;Ray and Maria Stata Center&lt;/label&gt;
		&lt;label&gt;Building 32&lt;/label&gt;
		&lt;label&gt;Gates Tower&lt;/label&gt;
		&lt;label&gt;Dreyfoos Tower&lt;/label&gt;
		
		&lt;location id="location1"&gt;
			&lt;point latitude="42.360890561289295" longitude="-71.09139204025269"/&gt;

			&lt;point id="mainpoint" latitude="27.174799" longitude="78.042111" altitude="10m"/&gt;
			
			&lt;center latitude="27.174799" longitude="78.042111"/&gt;
			
			
			&lt;route&gt;
				&lt;point order="0" latitude="42.360890561289295" longitude="-71.09139204025269"/&gt;
				&lt;point order="1" latitude="42.361176" longitude="-71.09018"/&gt;
				&lt;point order="2" latitude="42.36272976137689" longitude="-71.09049081802368"/&gt;
				&lt;point order="3" latitude="42.36318955298668" longitude="-71.09677791595459"/&gt;
				&lt;point order="4" latitude="42.363617631805496" longitude="-71.10156297683716"/&gt;
				
			&lt;/route&gt;

			&lt;area&gt;
				&lt;point order="0" latitude="42.360890561289295" longitude="-71.09139204025269"/&gt;
				&lt;point order="1" latitude="42.361176" longitude="-71.09018"/&gt;
				&lt;point order="2" latitude="42.36272976137689" longitude="-71.09049081802368"/&gt;
				&lt;point order="3" latitude="42.36318955298668" longitude="-71.09677791595459"/&gt;
				&lt;point order="4" latitude="42.363617631805496" longitude="-71.10156297683716"/&gt;
				&lt;point order="5" latitude="42.360890561289295" longitude="-71.09139204025269"/&gt;
			&lt;/area&gt;
			
			&lt;undetermined/&gt;
			
			&lt;relative location-id="mainpoint" distance-from="10m" bearing-to="20" relative-height="10m"/&gt;

		&lt;/location&gt;
		&lt;category scheme="http://www.census.gov/cgi-bin/sssd/naics/naicsrch?search=2007%20NAICS%20Search&amp;code=611310"&gt;
			&lt;name xml:lang="en-US"&gt;Colleges, Universities, and Professional Schools&lt;/name&gt;
			&lt;association type="child-of" reference="http://www.census.gov/cgi-bin/sssd/naics/naicsrch?search=2007%20NAICS%20Search&amp;code=6113"/&gt;

		&lt;/category&gt;

	&lt;/poi&gt;
	&lt;poi id="w3c"&gt;
		&lt;label primary="true"&gt;World Wide Web Consortium&lt;/label&gt;
		&lt;label&gt;W3C&lt;/label&gt;
		&lt;label&gt;W3&lt;/label&gt;
		&lt;location&gt;
			
		&lt;/location&gt;
		
		&lt;relation type="contained-by" id="#StataCenter"/&gt;
		
		&lt;!-- category using a scheme --&gt;
		&lt;category scheme="http://www.census.gov/cgi-bin/sssd/naics/naicsrch?search=2007%20NAICS%20Search&amp;code=813920" term="NAICS/611310"&gt;
			&lt;label xml:lang="en-US"&gt;Standards review committees, professional&lt;/label&gt;
			&lt;label xml:lang="es"&gt;Normas de los comités de revisión, profesional&lt;/label&gt;
			&lt;association type="child-of" reference="http://www.census.gov/cgi-bin/sssd/naics/naicsrch?search=2007%20NAICS%20Search&amp;code=8139"/&gt;
		&lt;/category&gt;
		&lt;!-- category, no scheme --&gt;
		&lt;category term="WebStandardsOrg"&gt;
			&lt;label xml:lang="en-US"&gt;Web Standards Organization&lt;/label&gt;
		&lt;/category&gt;
		
	&lt;/poi&gt;
&lt;/pois&gt;</pre></div>
	</div>
	<div id="xml-schema" class="section">
		<h3><span class="secno">4.13 </span>XML Schema</h3>
		<p class="editorsnote">
			This is a very rough RELAX NG schema for the XML syntax.  It is not guaranteed to work or be in sync with the rest of the document for now.
		</p>
			<div><pre>start = element pois { poi* }

poi = element poi {
   id?,
   lang?,
   label+,
   location,
   relation?,
   category*,
   association
}

center = element center {
   system?, latitude, longitude,
}

address = element address {
   attribute country { ISO-3166-ALPHA-3 },
   attribute floor { text },
   attribute language { MARC-ALPHA-3 },
   attribute postalcode { text },
   attribute street { text },
   attribute suite { text }?,
   element region { text }+
}

area = element area { point+ }  # minimum of 3; first and last must be the same.

object = element object { empty } # TBD

undetermined = element undetermined { empty }

relative = element relative {
   attribute location-id { xsd:NCName },
   attribute bearing-to { BEARING },
   attribute distance-from { DISTANCE },
   attribute relative-height { HEIGHT_IN_METERS }?
}

label = element label {
   attribute primary { xsd:boolean }?,
   lang?,
   text
}

route = element route { point+ }


location = element location {
   id?,
   (point | center | address | route | area | undetermined | map | relative)+
}

association = element association {
   attribute reference { xsd:anyURI },
   attribute type { xsd:NCName }
}

relation = element relation {
   id?,
   attribute relative-to { xsd:IDREF },
   attribute type { "contained-within" | "adjacent-to" | "contains" }
}

category = element category {
   attribute source { xsd:anyURI },
   label+
}

point = element point {
   id?,
   attribute altitude { HEIGHT_IN_METERS }?,
   latitude,
   longitude,
   attribute order { xsd:nonNegativeInteger }?
}

# common types
HEIGHT_IN_METERS = xsd:decimal 
DISTANCE = xsd:string { pattern = "[\+]?(\d+(\.\d{1,2})?)(m|km|mi|ft)?" }
BEARING = xsd:decimal { minInclusive="0" maxExclusive="360" }
ISO-3166-ALPHA-3 = xsd:string { pattern = "[A-Z][A-Z][A-Z]" }
MARC-ALPHA-3 = xsd:string { pattern = "[A-Z][A-Z][A-Z]" }
PERCENTAGE = xsd:integer { minInclusive="0" maxInclusive="100" }

# common attributes
id = attribute id { xsd:ID }
lang = attribute xml:lang { xsd:language }
latitude = attribute latitude { xsd:decimal { minInclusive="-90" maxInclusive="90" } }
longitude = attribute longitude { xsd:decimal { minInclusive="-180" maxInclusive="180" } }
system = attribute system { "WGS84" | text }
</pre></div>
		</div>
	</div> <!-- end XML syntax section -->
	
	<div class="appendix section" id="use-cases">
			<!--OddPage--><h2 id="use-cases-h2"><span class="secno">A. </span>Use Cases</h2>
		 	<div>
		<p class="editorsnote">This section reflects the contents of the <a href="http://www.w3.org/2010/POI/wiki/Use_Cases">page</a> on the <a href="http://www.w3.org/2010/POI/wiki/">POI wiki</a> at the time of publication.<br />Please discuss any proposed edits on the public-poiwg mailing list before editing the wiki directly.</p>

	<h4 id="use-cases-subsec"> <span> Use Cases </span></h4>
	<p>Please put here any and all use cases that are relevant to the WG discussions. In time we should pick a standard format for describing them but for now just upload the original files, preferably with an accompanying description.
	</p>
	<h5 id="use-case-checkin"> <span> Check in services </span></h5>
	<ul><li> TBD
	</li></ul>
	<h5 id="use-case-ar"> <span> AR Use Cases </span></h5>
	<p><a href="http://www.perey.com/ARStandards/Three_Use_Cases.pdf" class="external text">Three Use Cases for AR Standards Discussion</a>
	</p>
	<pre>  This file captures contributions of the participants of <a href="http://www.perey.com/ARStandardsMeeting.html" class="external text">International AR Standards Meeting</a> conducted Oct 11-12 in Seoul. 
	  Added to this wiki page Oct 26, 2010
	</pre>
	<p><a href="/2010/POI/wiki/File:DERI_-_Linked_AR_proof-of-concept_1_pager.pdf">DERI Linked AR PoC</a>
	</p>
	<pre> This file describes use case where all manner of historical content is related to relevant locations and viewed through a mobile AR browser.
	 Added to this wiki page on Oct 28, 2010
	</pre>
	<h5 id="use-case-generic"> <span> Generic Points of Interest Use Cases </span></h5>
	<h5 id="use-case-search"> <span>Search</span></h5>
	<ol><li><b> What is there to do here?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, Categories, Tags, Time, Events
	</li></ul>
	</li><li><b> Where is a 4 star Italian restaurant near me that is still open?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, Categories, Tags, Time, Events 
	</li></ul>
	</li><li><b> Where can I find a new battery for my phone?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, Brand associations, inventory 
	</li></ul>
	</li><li><b> What movies are playing now near me?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, Categories, Time, Event 
	</li></ul>
	</li><li><b> Where is the cheapest available parking near the theater?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, Categories, Historical pricing info
	</li></ul>
	</li><li><b> What shoes stores are in this mall?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, Categories, Local group associations
	</li></ul>
	</li><li><b> How much is the entrance fee for the museum?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, Categories, Pricing info
	</li></ul>
	</li></ol>
	<h5  id="use-case-LBS-advertising"> <span>Location-Based Advertising</span></h5>
	<ol><li><b> What special offers are around here?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, Location-based Advertising, Offer System
	</li></ul>
	</li><li><b> What are the specials at nearby restaurants?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, Location-based Advertising, Offer System
	</li></ul>
	</li><li><b> Let me know of any shoe sales I might pass as I walk around the city shopping.</b>
	<ul><li> Persona: End-User, Interconnected systems
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, Location-based Advertising, Offer System
	</li></ul>
	</li></ol>
	<h5  id="use-case-destination"> <span>Destination Selection</span></h5>
	<ol><li><b> Take me to this café…</b>
	<ul><li> Persona: End-User
	</li><li> Elements: POI attribute search, location, route calc
	</li></ul>
	</li><li><b> Take me to the place with this phone number…</b>
	<ul><li> Persona: End-User
	</li><li> Elements: POI attribute search, location, route calc
	</li></ul>
	</li><li><b> Take me on a scenic wine tour</b>
	<ul><li> Persona: End-User
	</li><li> Elements: POI group associations, POIs, tags, route calc
	</li></ul>
	</li><li><b> Take me to the office of my next appointment</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Calendar, Contacts, locations, route calc
	</li></ul>
	</li><li><b> If I want to go to Macy's in this mall at what entrance should I park?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: POI group associations, location, location associations, route calc
	</li></ul>
	</li></ol>
	<h5 id="use-case-b2b"> <span>B2B</span></h5>
	<ol><li><b> Associate together these similar business by categories and associations</b>
	<ul><li> Persona: Interconnected systems
	</li><li> Elements: POI group associations, POIs, categories, tags
	</li></ul>
	</li><li><b> Convert these POI listings descriptions to 12 major languages</b>
	<ul><li> Persona: Interconnected systems
	</li><li> Elements: POIs, translation service
	</li></ul>
	</li><li><b> Share this specific set of Yellow Pages with this business partner</b>
	<ul><li> Persona: Interconnected systems
	</li><li> Elements: POIs, source identification, tags, fullfillment services, distribution services
	</li></ul>
	</li><li><b> Sweep these web sites and normalize the data to a standard exchange format</b>
	<ul><li> Persona: Interconnected systems
	</li><li> Elements: web scraping, standard format, language/tag processing service
	</li></ul>
	</li><li><b> Accurately geolocate these places of business</b>
	<ul><li> Persona: Interconnected systems
	</li><li> Elements: locations, geocoding service, map
	</li></ul>
	</li></ol>
	<h5 id="use-case-info"> <span> Informational</span></h5>
	<ol><li><b> What is the history of this building?</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, Building cartography, POIs+Locations, Historical data
	</li></ul>
	</li><li><b> What is the name of this neighborhood?</b>
	<ul><li> Persona: End-User, Interconnected systems
	</li><li> Elements: Geo-spatial proximity, area cartography, Named areas
	</li></ul>
	</li><li><b> Tell me about this house…</b>
	<ul><li> Persona: End-User, Interconnected systems
	</li><li> Elements: Geo-spatial proximity, Building cartography, POIs+Locations, Real estate data
	</li></ul>
	</li><li><b> What kind of businesses are in this building?</b>
	<ul><li> Persona: End-User, Interconnected systems
	</li><li> Elements: Geo-spatial proximity, Building cartography, POIs+Locations, Building to POI associations
	</li></ul>
	</li><li><b> Take me on a tour...</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POI group associations, POIs, tags, route calc
	</li></ul>
	</li><li><b> I want to leave a trail of my experiences for others to find and enjoy</b>
	<ul><li> Persona: End-User
	</li><li> Elements: Geo-spatial proximity, POIs+Locations, route calc, social data servcies
	</li></ul>
	</li></ol>
	<h5 id="use-case-ar2"> <span>Augmented Reality</span></h5>
	<ol><li><b> Guide</b>
	<ul><li> A system which leads the user through a process involving real world
	</li></ul>
	</li><li><b> Create</b>
	<ul><li> A system with which the user attaches/contributes a digital content “object” to or in the real world
	</li></ul>
	</li><li><b> Play</b>
	<ul><li> A system which supports bi-directional interaction between users and the real world
	</li></ul>
	</li></ol>

</div>
	</div>
    <div class="appendix section" id="acknowledgements">
      <!--OddPage--><h2><span class="secno">B. </span>Acknowledgements</h2>
      <p>
      </p>
    </div>
  

<div id="references" class="appendix section"><!--OddPage--><h2><span class="secno">C. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">C.1 </span>Normative references</h3><p>No normative references.</p></div><div id="informative-references" class="section"><h3><span class="secno">C.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>