Henning Bredel

version `2.x` won't have the `v1` part anymore as it lead to confusion (API will stay backwards compatible). However we have the following cases: 1. `{host}/{context}`: respond currently with `404`...

will also fix #110

we'll use "jekyll, kramdown, swagger" stack to build all documenation targets. As build process is done via travis and documentation sources are part of the project itself, the docs become...

A type `url` could make sense to differentiate from `string` as there might be parameters to URL-encode. Otherwise a client will get an invalid URL. So, yes: I think to...

for `v2.x` documentaion, first config note added in [release notes wiki](https://github.com/52North/series-rest-api/wiki/ReleaseNotes#304-flexible-prerendering-title-config-via-placeholders)

update on documentation: we decided to [integrate documentation](https://github.com/52North/series-rest-api/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aclosed%20documentation%20) via "Jekyll, Kramdown, Swagger" Stack .. so it will be [part of the sources](https://github.com/52North/series-rest-api/tree/develop/docs) The documentation of prerendering config will be part...

@zbodrosk currently there is no external trigger to update the SOS cache, just the continuous [cache update job](https://github.com/52North/SensorWebClient/blob/develop/sensorwebclient-api/src/main/java/org/n52/server/mgmt/schedule/CacheUpdateJob.java). Unfortunately, it does not read in the `sos-instances.data.xml` file again so no...

@zbodrosk saving it separatly is the best way to go. I would go for `%HOME%\.52n\sensorwebclient\sos-instances.data.xml` or `$HOME/.52n/sensorwebclient/sos-instances.data.xml` where the SOS update mechanism searches first. If not present it would read...

well, actually what I said. Both files are allowed. If the first under user's home is found the other is ignore. otherwise the one under local Web context is read....

@zbodrosk cool. Let me know if you need more input.