- From: Raj Singh <rsingh@opengeospatial.org>
- Date: Fri, 30 Aug 2013 14:10:56 -0400
- To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Cc: public-geosemweb <public-geosemweb@w3.org>, public-places <public-places@w3.org>, W3C Web Schemas Task Force <public-vocabs@w3.org>
Moving POIs is a complex topic. OGC has done much work to support the idea of things that move over time: "Sensor Observation Service" http://www.opengeospatial.org/standards/sos "OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)" https://portal.opengeospatial.org/files/?artifact_id=46170 "OGC Standard for Moving Features; Requirements" https://portal.opengeospatial.org/files/?artifact_id=51623 Whether these concepts should be put into a POI data model is debatable. I feel it would make the POI model too complex, but perhaps an extension of the core POI model could add this support by allowing the location to have a timestamp field. I hesitate to make this part of the core functionality due to the complexity, and the fact that there is a very large audience for a fixed location POI data model. --- Raj The OGC: Making location count. http://www.opengeospatial.org/ogc/organization/staff/rsingh On Aug 27, at 6:16 AM, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> wrote: > At this very moment I work on open source app which also includes *moving* POIs, have found this relevant email from Christine Perey: http://lists.w3.org/Archives/Public/public-poiwg/2011May/0050.html
Received on Friday, 30 August 2013 18:15:12 UTC