Opened 12 years ago

Last modified 11 years ago

#307 closed enhancement

external names should use rasdaman, not petascope — at Version 9

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 abeccati)

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 : including extensions such as WCS-T
/rasdaman/ows/wcps
/rasdaman/rasql : endpoint for the upcoming web interface to rasql

Documentation for upcoming 9.0 to be updated accordingly

Change History (9)

comment:1 by Dimitar Misev, 12 years ago

Maybe we should also change the package structure in petascope from petascope.* org.rasdaman.*

comment:2 by Peter Baumann, 12 years ago

…and rephrase the petascope default HTML page.

comment:3 by abeccati, 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 abeccati, 11 years ago

Cc: cmppri Peter Baumann Dimitar Misev added
Complexity: Easy
Description: modified (diff)
Status: newassigned

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.

comment:5 by abeccati, 11 years ago

Description: modified (diff)
Priority: minorcritical

Adding detail for wcst interface (supported by WCS). Linkning and superseding (opted for separate endpoints for now) ticket #270 (Raising priority to that of superseded one).

comment:6 by abeccati, 11 years ago

Cc: Piero Campalani added; cmppri removed

comment:7 by Peter Baumann, 11 years ago

shold we use lowercase wcs etc. for homogeneity?

comment:8 by Dimitar Misev, 11 years ago

I vote for lowercase.

I'll still say that the /ows doesn't bring anything essential but 4 redundant bytes.

comment:9 by abeccati, 11 years ago

Description: modified (diff)

Indeed all lowercase sounds good, updated

Note: See TracTickets for help on using tickets.