Arnulf, that's exactly what the OGC Geosynchronization spec describes! Servers
advertise their changes in a GeoRSS feed -- where the element
describes the change in WFS-T XML. It's nicely loosely coupled, because as you
eloquently state, clients can decide what they want to do with the "suggest
Hi,
Yes Smallworld did a lot of innovation in the area of version management and
long transactions some 20 years ago, I was quite involved in all that. The
technical paper you mention is at archive.org, a great resource for finding
web pages that have disappeared!
http://web.archive.org/web/200805
I'm a bit surprised no-one mentions Smallworld. Weren't they at the forefront
of version management almost 20 years ago?
The following link to an interesting technical paper isn't currently working,
but maybe it'll come back later:
http://cfis.savagexi.com/pages/technical_paper_4
Steve
> On
This might be too far off the original idea... But: It might be
interesting to look into a more disconnected way of "managing"
geospatial data with the Web. As in having "servers" advertize latest
changes in geometry and attributes using GeoRSS and "clients" picking
these up and integrating the
Ragi,
I agree. I think that we have a way to go yet to have something comparable to
the ArcSDE / ArcGIS Multi-versioning and version conflict detection
functionality.
The advantage that the ArcSDE solution has is that edits are made directly
within the database. This works well within an Enter
