Opened 12 years ago
Last modified 11 years ago
#307 closed enhancement
external names should use rasdaman, not petascope — at Version 4
| Reported by: | Peter Baumann | Owned by: | abeccati |
|---|---|---|---|
| Priority: | major | Milestone: | 9.0 |
| Component: | petascope | Version: | 8.3 |
| Keywords: | Cc: | Piero Campalani, Peter Baumann, Dimitar Misev, abeccati | |
| Complexity: | Easy |
Description (last modified by )
In many places "petascope" is used, eg, war files, in WPS ("petascope.wps.n52.ProcessCoverages"). This is confusing for the users of rasdaman, branding should be uniform - in the end, petascope is just one out of many rasdaman components. Hence, in all code the naming should be replaced accordingly.
Endpoints are to be renamed as follows:
/rasdaman (landing page with desctiption of server and pointers to available endpoints)
/rasdaman/ows (landing page for OGC Web Services, with pointers to second level ones)
/rasdaman/ows/WPS
/rasdaman/ows/WMS
/rasdaman/ows/WCS
/rasdaman/ows/WCPS
/rasdaman/rasql : endpoint for the upcoming web interface to rasql
Change History (4)
comment:1 by , 12 years ago
comment:3 by , 12 years ago
Looks related to #270
There we had different endpoints but we can resume to have a single "rasdaman" root
/rasdaman (landing page with desctiption of server and pointers to available endpoints)
/rasdaman/ows : single endpoint for all OGC web services interfaces (WCS, WMS, WCPS, etc)
/rasdaman/rasql : endpoint for the upcoming web interface to rasql
comment:4 by , 11 years ago
| Cc: | added |
|---|---|
| Complexity: | → Easy |
| Description: | modified (diff) |
| Status: | new → assigned |
As the codebase stands now, we'd like to avoid checking which service request is for which service type but want to keep them grouped so we can change our mind in future without having a new (common endpoint to define = ows).
Updating accordingly, that will be the 9.0 endpoint definition.
Maybe we should also change the package structure in petascope from petascope.* org.rasdaman.*