[Geojson] Assessing date/time ideas

Sean Gillies sean.gillies at gmail.com
Sat Oct 1 09:31:12 PDT 2011


Yes, Andy, Activity Streams seem to cover the feed-like and
media-carrying use cases very well, so I suggest we can mark those as
solved.

Activities seem to me to be analogous to our Features. Agreeing on a
way to extend them (as ksnabb suggests in Scope) with a geometry
property could be profitable.

On Fri, Sep 30, 2011 at 7:28 PM, andy e <virtualandy at gmail.com> wrote:
> Maybe the ActivityStreams JSON spec can help us here?
> http://activitystrea.ms/specs/json/1.0/
> Anyone see an obvious way to extend ActivityStreams to include GeoJSON "sub
> components" (don't know what that's called)?
> andy
>
>
> On Fri, Sep 30, 2011 at 3:01 PM, Kristoffer Snabb
> <kristoffer.snabb at gmail.com> wrote:
>>
>> Hi Sean,
>>
>> Expanding the domain to cover that of feeds helps,
>>
>> We use GeoJSON to carry 'soft' data of perceptions and temporary data
>> connected to a place, route or area. In this case we have been using
>> different media to describe the context of the place and specific
>> perceptions of a place. Anyway, we have survived with adding a property of
>> mimetype and url but it would be nice if there existed a standard way to do
>> this in the GeoJSON specification.
>>
>> And we also expect that the perceptions of a place change over time and in
>> that way they are created and they expire. A timestamp (feed) is also needed
>> if we create time space diagram of routes. Although when we map daily
>> activities of people they tend to stay many hours in one place in which case
>> the create and expire time is again needed.
>>
>> Hope this clarifies something,,
>>
>> Kristoffer
>>
>>
>> 2011/9/30 Sean Gillies <sean.gillies at gmail.com>
>>>
>>> Time comes up in several places in the proposal fodder section of
>>>
>>>  https://github.com/GeoJSONWG/geojson-spec/wiki/Scope
>>>
>>> Which of these are equivalent (more or less) to the Atom/RSS notions
>>> of a modification time stamp? Which are not? In combination with an id
>>> (already recommended in GeoJSON) that kind of timestamp lets you sync
>>> features between systems. With this in mind, the "adding media" bullet
>>> suggests that some of us are looking for GeoJSON to expand its domain
>>> to cover that of feeds. Is my assessment right?
>>>

-- 
Sean Gillies


More information about the Geojson mailing list