Points of Interest Core

3.1 Geo-reference

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.

A geo-reference 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 location primitive.

A geo-reference is of one of the following types:

3.2 Location

The location primitive provides a rich and flexible description of the location of a POI. A location is a required part of a POI.

3.3 Relationship primitive

The relationship primitive establishes 1-to-1 or 1-to-many relationships between POIs.

A relationship may be one of the following:

contained-within

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

contains

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

adjacent-to

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

...

Need more relationship types

Should the details of the various relationship types themselves be in this section? Assuming yes for now

3.4 string primitive

Dropped per our discussion at f2f

3.5 Label primitive

POIs may have zero or more label primitives which represent a human readable label.

At F2F2 we decided to rename the name primitive to "label", and to allow labels to be marked as primary for each language represented.

3.6 ID primitive

POI must have an "id" primitive. It unambiguously identifies a POI within a particular implementation.

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.

3.7 Categorization primitive

POI can have a "categorization" primitive, with one or more category identifiers.

Todo

3.8 meta data primitive

Todo. Not sure how this would work, and why this wouldn't just be covered by our extensibility story

3.9 Time primitive

POI can have one or more time primitives that represent an individual point in time, a span of time, or a recurring time or time span.

We discussed at F2F2 basing this on other standards' time representations

4.1 XML Notation

Borrowed from MathML.

We need to figure out: xml id/xml:base, xml:lang, units of measurement

4.2 pois and poi elements

The root element for an POI in XML syntax is the pois element. It contains one or more poi elements.

poi/pois section is all TBD

4.3 Representing coordinates

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 coordinate attributes are referenced below.

Attributes

Is there an official geode tagging scheme, e.g. "wgs84", or "etrs89"?

4.4 <location> element

The <location> element contains one or more geo-references elements (see below), and has no attributes or character data.

Geo-reference elements

The following elements are the XML mapping for the geo-references outlined in the data model. Geo-references are used only with in the <location> element.

4.5 <relationship> element

The <relationship> element contains no character data.

Attributes

4.6 <label> element

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

4.7 id representation

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.

4.8 <category> element

Todo

4.9 meta data tags...

TBD

4.10 <time> element

We discussed at F2F2 basing this on other standards' time representations

4.11 XML Example

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.

<?xml version="1.0" encoding="UTF-8"?>
<pois>
	<poi id="StataCenter" xml:lang="en-US" >

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

			<point id="mainpoint" latitude="27.174799" longitude="78.042111" altitude="10m"/>
			
			<center latitude="27.174799" longitude="78.042111" radius="10m"/>
			
			<address language="en-US" country="USA" street="32 Vassar St." floor="5" suite="19" postalcode="02139">
				 <region>Cambridge</region>
				 <region>Boston</region>
				 <region>Massachusetts</region>
			</address>
			
			<route>
				<point order="0" latitude="42.360890561289295" longitude="-71.09139204025269"/>
				<point order="1" latitude="42.361176" longitude="-71.09018"/>
				<point order="2" latitude="42.36272976137689" longitude="-71.09049081802368"/>
				<point order="3" latitude="42.36318955298668" longitude="-71.09677791595459"/>
				<point order="4" latitude="42.363617631805496" longitude="-71.10156297683716"/>
				
			</route>

			<area>
				<point order="0" latitude="42.360890561289295" longitude="-71.09139204025269"/>
				<point order="1" latitude="42.361176" longitude="-71.09018"/>
				<point order="2" latitude="42.36272976137689" longitude="-71.09049081802368"/>
				<point order="3" latitude="42.36318955298668" longitude="-71.09677791595459"/>
				<point order="4" latitude="42.363617631805496" longitude="-71.10156297683716"/>
				<point order="5" latitude="42.360890561289295" longitude="-71.09139204025269"/>
			</area>
			
			<undetermined/>
			
			<map supplier="TeleTEQ" version="9" object-id="foobar" side="left" spot="2%"/>
			
			<relative location-id="mainpoint" distance-from="10m" bearing-to="20" relative-height="10m"/>

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

		</category>

	</poi>
	<poi id="w3c">
		<label primary="true">World Wide Web Consortium</label>
		<label>W3C</label>
		<label>W3</label>
		<location>
			<address language="en-US" country="USA" street="32 Vassar St." floor="5" postalcode="02139">
				 <region>Cambridge</region>
				 <region>Boston</region>
				 <region>Massachusetts</region>
			</address>
		</location>
		
		<relation type="contained-by" id="#StataCenter"/>
		
		<category source="http://www.census.gov/cgi-bin/sssd/naics/naicsrch?search=2007%20NAICS%20Search&code=813920">
			<name xml:lang="en-US">Standards review committees, professional</name>
			<name xml:lang="es">Normas de los comités de revisión, profesional</name>
			</identification>
			<association type="child-of" reference="http://www.census.gov/cgi-bin/sssd/naics/naicsrch?search=2007%20NAICS%20Search&code=8139"/>

		</category>
	</poi>
</pois>