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

Re: POI data model examples serialised as JSON, XML, HTML5 & KML

From: Alex Hill <ahill@gatech.edu>
Date: Thu, 29 Sep 2011 11:49:07 -0400
Cc: "public-poiwg@w3.org" <public-poiwg@w3.org>
Message-Id: <9FB5A4C9-E8A9-4CE6-B18B-8D692BF4576A@gatech.edu>
To: roBman@mob-labs.com

On Sep 29, 2011, at 11:29 AM, Rob Manson wrote:

> Based on the discussion on the conf call I've updated a few things in my
> draft of example02 http://mob-labs.com/poiwg/example02/index.html 
> 
> I've moved the created/updated from elements to attributes.
> 
> In the json example this doesn't really change anything.
> 
> In the xml example it's a simple change.
> 
> In the html5 embedded example I think the best way to achieve this is
> using the data-* custom attribute model.
> http://dev.w3.org/html5/spec/Overview.html#extensibility 
> http://dev.w3.org/html5/spec/Overview.html#embedding-custom-non-visible-data-with-the-data-attributes
> 
> In the kml example there doesn't seem to be a suitable way to do this.

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

> http://code.google.com/apis/kml/documentation/extendeddata.html
> So I've left them as namespace based elements.  I'd be happy to hear
> other suggestions/options here.
> 
> I also removed the published elements/attributes as suggested by
> Karl/Raj.
> 
> And I've changed title to label as defined in the UML Data Model
> documentation as suggested by Alex.
> 
> I also looked at adding the use of "term" to these simple examples just
> to see how that would work across the different serialisations...but
> when I get to kml I'm not quite sure how that would fit in.  
> Any suggestions here?

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

> 
> roBman
> 
> 
> On Wed, 2011-09-28 at 07:59 -0500, Seiler, Karl wrote:
>> I agree providing for "updatedOn" and "deletedOn" are key. "createdOn" is a nice to have. Not essential.
>> 
>> _______________________________
>> 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: Wednesday, September 28, 2011 7:47 AM
>> To: roBman@mob-labs.com
>> Cc: public-poiwg@w3.org
>> Subject: Re: POI data model examples serialised as JSON, XML, HTML5 & KML
>> 
>> feedback on example02:
>> description: I like the idea of having a long, narrative field for rich descriptions
>> rights: use this or <link rel="license" ... /> ??
>> author: I like it, especially if you can put VCard info in there. I don't like <link rel="author" .. /> (see link note in next email)
>> published: don't like it. I think the idea of published is not as important to POIs as it is to Atom feeds where the primary use case is news stories that are published, then may be updated. In the POI world, the original publication date has no extra importance.
>> updated: I like it -- see above.
>> 
>> ---
>> Raj
>> The OGC: Making location count...
>> http://www.opengeospatial.org/contact
>> 
>> 
>> On Sep 26, at 2:20 PM, Rob Manson wrote:
>> 
>>> I've created an example02 draft to integrate some of the feedback and to
>>> make some updates on things that didn't quite look right.
>>> 
>>> http://mob-labs.com/poiwg/example02/index.html
>>> 
>>> I've changed the json example to add a top level key called pois and
>>> turned what was the pois array into a poi object were each poi inside it
>>> is keyed by id.  Some people like to repeat the id inside the object
>>> too.  This seems like data duplication to me but I'd be interested in
>>> people's thoughts here.
>>> 
>>> I've updated the html5 embedded example to make the location elements
>>> work in what looks like a better way.  Let me know what you think of
>>> this new structure.
>>> 
>>> And I've tidied up the kml example by adding a poi: namespace too which
>>> had already been used for poi:title.  I think this would be a pretty
>>> simple namespace, but this is probably more correct to separate them out
>>> into pois and poi.  Thoughts?
>>> 
>>> I'll leave this as a standalone draft until I've received feedback and
>>> had a chance to see if there's any other things that still need a bit of
>>> refinement.  Then I'll merge the changes into the examples on the wiki.
>>> http://www.w3.org/2010/POI/wiki/Data_Model_Examples
>>> 
>>> 
>>> 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.
>> 
>> 
> 
> 

Alex Hill Ph.D.
www.alexshill.com
Received on Thursday, 29 September 2011 15:49:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 September 2011 15:49:43 GMT