Do we need this within the POI itself?
The data source distributing the POIs could give the dynamic
properties itself - (in our case, we are streaming updates to clients,
allowing POIs to move by their location co-ordinates been
changed....actually a quite like a IRC bots work). Meanwhile if a
webpage distributes a POI either PHP or Javascript could be used to
create/manipulate it.
I think a POI should be seen as just a way to position data - not as a
source of manipulation itself.
(ie, if we are thinking POIs should have "onclick" and such this,
imho, is the wrong road - the item being positioned by the POI might
have all manor of functionality, but the POI should really just be a
data standard for the positioning).
Animation meanwhile is easy - the data your linking too should be animated ;)
(ie, a animated 3d mesh format)
On 11 May 2011 22:43, Points of Interest Working Group Issue Tracker
<sysbot+tracker@w3.org> wrote:
>
> ISSUE-17 (dynamic-pois): How are POIs with dynamic properties represented?
>
> http://www.w3.org/2010/POI/track/issues/17
>
> Raised by: Matt Womer
> On product:
>
> From: roBman@mob-labs.com
> Date: Tue May 03 06:17:01 2011
> Archived: http://lists.w3.org/Archives/Public/public-poiwg/2011May/0004.html
>
> [[
> How would you see dynamic aspects like interaction, scripting and
> animation being integrated into this data model?
>
> At the moment it's a completely static model with no scope I can see for
> extension in this direction (except perhaps related to "time").
> ]]
>
>
>
>