W3C home > Mailing lists > Public > public-poiwg@w3.org > October 2011

RE: NAVTEQ example

From: Seiler, Karl <karl.seiler@navteq.com>
Date: Tue, 4 Oct 2011 14:22:37 -0500
To: Raj Singh <rsingh@opengeospatial.org>, "roBman@mob-labs.com" <roBman@mob-labs.com>
CC: "public-poiwg@w3.org" <public-poiwg@w3.org>
Message-ID: <133ACBBC61BE0E4081B6E35E542ECE230ED6C3E4@hq-ex-mb03.ad.navteq.com>
In the UML

The abstractPOI
 - remove metadata - no longer necessary as the other primitives supersede the need at this level
 + add link as a basic optional component

 - it is valid to use category to represent such types of POIs as those that are always open via:
<category term="Open 24 hours">Yes</category>
Or another typical example to represent the type of place of worship
<category term="Place of Worship"/>
<category term="Building type">Synagogue</category>
<category term="Building type">Synagogue</category>

Karl Seiler
Director Location Technology & Services
NOKIA Location and Commerce - Chicago
(T)  +312-894-7231
(M) +312-375-5932

-----Original Message-----
From: public-poiwg-request@w3.org [mailto:public-poiwg-request@w3.org] On Behalf Of Raj Singh
Sent: Tuesday, October 04, 2011 9:38 AM
To: roBman@mob-labs.com
Cc: public-poiwg@w3.org
Subject: navteq example

note that I'm splitting up the questions to change subject lines
The OGC: Making location count...

On Oct 3, at 10:18 PM, Rob Manson wrote:

> It would be good to add a term="open" or similar to that <time>
> otherwise there's no real meaning to it.  Also, because <time> in the
> UML Data Model diagram is defined as POISimpleType it can then also
> support start/end...which seems a bit circular 8/  Maybe <time> should
> just be a POIStructuredNameType.

<time> isn't core. Let's not discuss it now. I shouldn't have played around with it at this point in time. It had been removed from the AbstractPOI type but I forgot to upload the latest version. It's correct now on:

> We don't seem to have any mechanism for people to add arbitrary tags
> like the SupplierID=3.  I think not allowing this is a real limitation.

Tracking who the POI came from fits our concept of author, so we could handle this basic example of provenance metadata like this:
   <author id="3" href="http://www.example.com/pois/authors/3">
      <value>My Favorite Supplier</value>
      <rights href="http://www.cc.com/rights/3.3/attbyrel" />

The information contained in this communication may be CONFIDENTIAL and is intended only for the use of the recipient(s) named above.  If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited.  If you have received this communication in error, please notify the sender and delete/destroy the original message and any copy of it from your computer or paper files.
Received on Tuesday, 4 October 2011 19:23:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:48:31 UTC