Jody Garnett wrote:
> > - structures seems to be datastore then feature type? We have had one
> > case where geoserver was configured to "combine" data from two
> > cascaded WFS's were combined into the same published featuretype. Do
> > we need to consider namespace/featureType as representing the publish
> > to WFS (similar to how layer represents publish to WMS)
>
> If I get you right, you're suggesting that we keep the current
> /layers/{layername} endpoint and add a parallel hierarchy for each
> service (/publishedcoverages/{coverageid}
> and /publishedfeaturetypes/{featuretypeid})
>
>
> I was focused on separating the data access from the data publication. I
> wanted to view publishing the vector falvour of a data set as a seperate
> concern (similar to the idea of how a layer is defined).
>
> To define a layer we bring together data resource and style. There are a
> few more steps like giving the result a title and description.
>
> To define a published feature type we need to bring together a data
> resource and some information about namespace/typeName (the same steps
> of giving the result a title and description apply).
>
> There are however some more steps that are on our roadmap:
> - we can have the result be the aggregation of two data sources (my
> example earlier)
> - the result can be generated according to a simple restriction (ie
> filter) or a more complicated mapping (ie community schemas)
> - some operations (ie WPS) may be allowed on this resource
When talking about WPS remember it's on the roadmap, but without
funding, so it might become good enough to be turned into an
extension in two months, or in two years. I haven't had time to work
on it since late November, things might change in the short term,
or maybe not (no crystal ball here).
So it does not seem wise to get rest work, which is basically ready
for wider consumption today, stuck on something (WPS)
that does not have a short term integration plan?
> How to do wps is fairly clear from the ESRI stuff .... it shows up in
> your configuration as what operations you allow for a particular feature
> type. And then when you make a page for the feature collection you can
> have links to the allowed operations.
How do you account for processes that do not take just one fc as input,
or those that do not require geographic information at all? (after all
wps pretty much allows one to do basically everything).
Cheers
Andrea
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
