Opened 5 years ago

Closed 4 years ago

#278 closed task (fixed)

Definition of available functionality with respect to standards and software

Reported by: abeccati Owned by: pbaumann
Priority: critical Milestone: 8.4
Component: petascope Version: 8.3
Keywords: Cc:
Complexity:

Description (last modified by abeccati)

As part of the public interface definition for the upcoming release adopting semantic version numbering there is a need to provide specification about:
Features available
Standards implemented with conformance level

Users would like to know which parts of the standards are actually implemented/supported by versions of rasdaman when they are released.
In addition it would be useful to know whether unimplemented parts are being worked on or are intended to be worked on (this is suited for feature requests and "feature" or "enhancement" type tickets).

Where full conformance is not achieved, a clear description of the exception should be prominently stated as part of the specification.

Change History (6)

comment:1 Changed 5 years ago by abeccati

  • Description modified (diff)

comment:2 Changed 5 years ago by mase@…

For example, the WCPS 1.0 standard has various getMetaDataExpr expressions in 7.1.10 which are not currently supported (at least with the version I last tested). So we would like to know which parts of the standards are currently implemented by versions of rasdaman when they are released. In addition it would be useful to know whether unimplemented parts are being worked on or are intended to be worked on. If there are parts which may not realistically get implemented then the standards may need to be re-defined to have certain functionality defined in optional profiles so that implementations can say which profile of the standard they are supporting.

Another example, not quite so straightforward, is the crsTransformExpr in 7.1.28. I believe from email discussions that the open source version of rasdaman is not going to support crs transforms, just the enterprise version, although the enterprise version doesn't implement the WCPS syntax to execute crs transforms yet either (?). Of course, even if supported there will be a restriction on which CRS's are supported so there could be a services that supported the expression but that only supported one CRS I suppose :-) The standard could perhaps be written to define a bit more explicitly what a service has to support to be compliant with it.

The basic request is for the software releases to say which parts of the standards they are currently implementing.

comment:3 Changed 5 years ago by abeccati

  • Description modified (diff)
  • Priority changed from major to critical
  • Type changed from defect to task
  • Version set to 8.3

Thank you for providing detailed information about requested functionality specification, I added that to the description.

Please note however that this tracker is only concerned with the rasdaman community open source project. For inquiries regarding rasdaman enterprise please refer to rasdaman GmbH at www.rasdaman.com

comment:4 Changed 5 years ago by dmisev

It would be good to implement this straight into the code as well, e.g. a help function in rasql which would print all functions available, with description and note if it's a deprecated function. Similarly petascope would do for the standards.

comment:5 Changed 5 years ago by dmisev

Opened further ticket regarding rasql #293

comment:6 Changed 4 years ago by pbaumann

  • Resolution set to fixed
  • Status changed from new to closed

an updated, more detailed feature matrix has been provided in the wiki, see feature list.

Note: See TracTickets for help on using tickets.