RE: Proposal: The "POI as a simple collection of links" data model

Hey Karl,

I think that's a great re-phrasing.  

Much more eloquent 8)


roBman


On Thu, 2011-08-04 at 09:15 -0500, Seiler, Karl wrote:
> I like the ideas of:
> POI is a collection of links
> POI needs some base primitives for easier use (label, links, locations, time)
> POI support triples (a-v's) for unordered collections of facts
> 
> Thanks works for me from my daily use and implementation perspective
> 
> _______________________________
> Karl Seiler
> Director Location Technology & Services
> NAVTEQ - Chicago
> (T)  +312-894-7231
> (M) +312-375-5932
> www.navteq.com
> 
> 
> -----Original Message-----
> From: public-poiwg-request@w3.org [mailto:public-poiwg-request@w3.org] On Behalf Of Dan Brickley
> Sent: Thursday, August 04, 2011 9:02 AM
> To: Raj Singh
> Cc: roBman@mob-labs.com; public-poiwg@w3.org
> Subject: Re: Proposal: The "POI as a simple collection of links" data model
> 
> On 4 August 2011 15:56, Raj Singh <rsingh@opengeospatial.org> wrote:
> > I love the "POI as a simple collection of links" data model in theory. It's very clean conceptually, and that's the way I've been thinking of the larger POI "picture" also. However, I don't think it's the best way to implement.
> >
> > I think we still need a few primitives. The only things that are in the model now that don't fit your links model are the label, some time fields, and the location. The label and the time fields are so natural to just stick in there. That brings us to location. The data URI seems awkward to me and likely to turn people off of the spec. However, I'm open to other opinions.
> 
> I like it too. Seems pretty much isomorphic to RDF, btw. Can it be
> written out explicitly as a set of triples, eg. an unordered
> collection of factoids that take one of these forms:
> 
> <thing1-URI> <propertytype-URI> "value " .
> 
> and
> 
> 
> <thing1-URI> <propertytype-URI> <thing2-URI>.
> 
> ...?
> 
> If so, it should be possible to write out this datamodel using any RDF
> notation, store/query it in any RDF database, etc.
> 
> cheers,
> 
> Dan
> 
> 
> 
> 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 Thursday, 4 August 2011 15:37:41 UTC