Skip to content

How Web Client works

Martynas Jusevičius edited this page Aug 5, 2016 · 3 revisions

See also how AtomGraph Processor works on the server side.

User interface

On the presentation layer, XSLT transforms the RDF/XML loaded by the processor into XHTML, if that is what was requested. The stylesheet combines RDF payload with metadata from vocabularies and ontologies to build a Bootstrap-based layout. Web-Client includes a default layout as well as vocabulary-specific stylesheets that attempt to provide the best user experience.

Declarative Web components

Web-Client applications only need to override XSLT templates in order to change UI layout for specific resources or data shapes, but the bulk of the fine-grained default templates in the Web-Client XSLT library can still be reused. In a similar fashion, Processor enables configuration of custom Linked Data Templates and queries in the application sitemap, but often the default ones can be reused. Furthermore, all of the templates can be reused across Web-Client applications, and we hope to build an ecosystem and a community around them.

Dependencies

Web-Client depends on AtomGraph Core and on Saxon which is used to perform XSLT transformations. Twitter Bootstrap is used as CSS/JavaScript layout framework.

Clone this wiki locally