Daniel Nüst

Can you list the specific tasks that need to be done? From the text above it seems `primaryFile` is not the only critical aspect of the class.

Currently under development in https://github.com/nuest/WPS/tree/wps4r/feature/metadata-annotation

There is an open issue here: URLs that contain a `=` character break during parsing. Solution probably is encoding the URL in the script, but then it must be decoded...

## Next generation metadata annotation - use role attributes in a pragmatic way to add semantics to `ows:Metadata` links - Example of "current" way via http://wps1.glues.geo.tu-dresden.de/wps/WebProcessingService?service=WPS&version=1.0.0&request=DescribeProcess&identifier=org.n52.wps.server.r.glues.systemarchetypes ``` ``` - distinguish...

Why should there be licensing issues with the parent pom?

The API: I think that would be useful! The skeleton project would then not need the 52N repo anymore: https://github.com/52North/WPS-Extension-Skeleton

They are located in the script directory which you can configure as describe here: https://wiki.52north.org/bin/view/Geostatistics/WPS4RDocumentation#Configuration_parameters

@ridoo Is this still the case with the latest WPS?

Good points. And yes, the idea would be that every algorithm execution runs it it's own process. Please not this is just an idea that came up in a discussion...

There already is a version attribute - this should override the filename based version if both are present, see https://github.com/52North/WPS/blob/master/52n-wps-webapp/src/main/webapp/R/scripts/demo_uniform-table.R