SemanticSTEP Viewer (SSV) is the user interface (frontend) to access SRDB and work with ontologies. It is a sample implementation of how to access SRDB for semantic data. SSV allows adding, searching and viewing SemanticSTEP ontologies (named graphs).
A sample SemanticSTEP Viewer installation is running on top of our sample SRDB installation. The SSV can be accessed at http://srdb.s-ten.net/SSV.
SSV is a web browser application collected into a Java servlet on some web server. This frontend uses HTML, XML Stylesheet Transformations (XSLT) and JavaScript to provide the user interface. The server side of SSV serves as a file provider and performs minimal processing (applies the SSV template).
SSV relies on SRDB for data retrieval. The application is able to handle SemanticSTEP named graph ontologies.
SemanticSTEP Viewer architecture
To examine a sample SSV installation, visit http://srdb.s-ten.net/SSV. SSV can be deployed to other web servers where a SRDB installation is running.
SSV can be used to view the data stored in the SRDB. Currently it provides such features:
Named graph is presented in several views that are defined in XML Stylesheets. Those stylesheets provide a way to view overview, aspects and other information derived from the graph. The named graph overview page can be opened either by following a list from named graph list or by using the Show data functionality.
When a component link in overview page is opened, a new page displays further details about the selected product.
Currently SSV allows accessing data from a SRDB, which is hosted on the same domain as the SSV. For example, if SRDB is running at http://srdb.s-ten.net, then SSV also must be installed at http://srdb.s-ten.net. This issue is caused by the security requirements of the web browsers. There are ways to configure a web browser to ignore this limitation by configuring them for the specific SSV installation or using signed JavaScript packages. However, this solution is specific to a web browser and may be an obstacle for an easy use of SSV.
XSLT transformations used for graph ontology visualization create a lot of constraints for SSV features and performance. Further development should focus more on using JavaScript than XSLT to overcome these weaknesses.
As SSV uses the webserver minimally, this adds flexibility on deploying it. However, to get rid of security and performance issues, more server side processing could also be added to the SSV.