RE: POI data model examples serialized as JSON, XML, HTML5 & KML

I think we should inherit the use of the TimeSpan and TimeStamp primitives.

TimeStamp for lastUpdated
TimeSpan for start and end of the POI

However, I still do not know how we can use what we have so far to create a usable hours-of-operations attribute block.

_______________________________
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 Rob Manson
Sent: Thursday, September 29, 2011 11:04 AM
To: public-poiwg@w3.org
Subject: Re: POI data model examples serialised as JSON, XML, HTML5 & KML

Hey Alex,

> There is a TimeSpan element in KML that allows a begin and end time:
> http://code.google.com/apis/kml/documentation/kmlreference.html#timespan


This would definitely work as native kml synonyms for pois:start
(TimeSpan begin) and pois:end (TimeSpan end).

Any ideas for created/updated?  KML has <Create> and <Update> but I
think these have a very different meaning 8/


> KML has key value pairs through the ExtendedData element:
> http://code.google.com/apis/kml/documentation/kmlreference.html#extendeddata


Yep...but that's definitely not the same as adding custom attributes
within existing elements.  So using namespaced elements is about the
same verbosity level.  They would be a good alternative to namespacing
in general for kml though.

BTW: I've updated the kml in my draft example02 to remove the atom
namespace usage and to just rely on the kml native "name" element as a
synonym for pois:label.  I think kml was the only example that really
was a bit of a mishmash and this is a bit more tidy now 8)


roBman



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, 29 September 2011 18:54:40 UTC