W3C home > Mailing lists > Public > public-poiwg@w3.org > November 2010

Re: Representing time-dependent objects in POI data model

From: Thomas Wrobel <darkflame@gmail.com>
Date: Thu, 4 Nov 2010 19:38:00 +0100
Message-ID: <AANLkTinhgbwdLiix_+eMjJes0wmKE08o+A+qs_fLVqMf@mail.gmail.com>
To: Sara-Jayne Farmer <sara-jayne.farmer@envitia.com>
Cc: public-poiwg@w3.org
I think its important to have a updated timestamp field to notify
clients of changes to data.
Specifically this is needed when data is remotely linked (for example,
a 3d file). A client will look at the timestamp and know if its cached
copy is good, or if it should be re-downloaded.
It should also be noted the location of the 3d file could change
without the file updating, and the file still shouldn't
re-download...just reposition.

So theres at least two types of updates a POI could have; a update to
the content *(3d models etc), and an update to the trigger. (location
etc)

Its not necessarily important to have either or both these types of
update fields for each POI, but it is important to make a distinction
between the two.

Likewise for "date created" - both for physical objects, the content
associated with them, and the triggers associated with that.

We need clear distinctions here, both in names used and definitions
else things will get very confusing.


On 1 November 2010 17:00, Sara-Jayne Farmer
<sara-jayne.farmer@envitia.com> wrote:
> As a point of interest, it can be important when the physical object (e.g. the camp) is created, rather than when the record was created.   It's also possible for a physical point of interest to change its state and its interestingness to each user - e.g. after a crisis, school buildings may become camps, hospitals or warehouses, hopefully for a relatively short period of time.  I'm not sure if the answer to this is to create a new point of interest in the same place, or to overload the existing point of interest that's already there.
>
> There are a whole bunch of other attributes that could be added to these types of points of interest, but I'm assuming here that we're working on the baseline POI standard and these could be added on to the standard later (e.g. by blending with the existing EDXL humanitarian data standards).
>
> Thank you,
>
>
>
> Sj.
>
> -----Original Message-----
> From: Dan Brickley [mailto:danbri@danbri.org]
> Sent: 01 November 2010 15:29
> To: Sara-Jayne Farmer
> Cc: public-poiwg@w3.org; Matt Womer
> Subject: Re: Representing time-dependent objects in POI data model
>
> On Mon, Nov 1, 2010 at 12:45 PM, Sara-Jayne Farmer <sara-jayne.farmer@envitia.com> wrote:
>> I can't get onto the POI wiki, so can I make a request please?  Many of the points of interest I deal with (in transport and crisismapping) are temporary or moving - for instance, a refugee camp may only exist for a few days or weeks.   Can we consider adding a time field to the POI data model, e.g. "date created", "date updated" to cover these please?
>
> I've added something on this to
> http://www.w3.org/2010/POI/wiki/Data_Model#POI_Administrative_metadata
>
> ...but on re-reading your message, I see it could either be the record was created/updated, or the 'refugee camp' was created. I added a section for the former but not the latter yet. Were you thinking more about administrative metadata, or about dates for short-lived spatial things?
>
> cheers,
>
> Dan
>
>
Received on Thursday, 4 November 2010 18:38:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 4 November 2010 18:38:35 GMT