Class vocabulary

Legacy Bootstrap buttons (btn, btn-primary, btn-large) become the ac-btn intent, appearance and size\n vocabulary: ac-btn in-primary ap-solid sz-md. The stylesheets page lists the axes and the classes on each.

pull-left and pull-right have no replacement, because the design system lays out with flex and grid. A stylesheet that extends\n the removed vocabulary can be diffed against ldh.css, the one app layer LinkedDataHub loads over the vendored design kits.

Template modes

Every bs2: mode takes its design-system component name. This is the change that makes the release a major one: an override of a\n bs2: mode still compiles, never fires, and reports nothing.

Parameters and functions

The $ac:langs and $ac:lang parameters become the ac:langs() and ac:langs()[1] functions. An\n xsl:with-param left behind is silently ignored. A stylesheet still declaring xmlns:lapp compiles and silently binds nothing.

Removed libraries

Overrides depending on bootstrap.js, jQuery, WYMEditor or the sprite icons need rewriting. IXSL templates drive the dropdowns and modals,\n the msi font draws the icons, and the RDFa editor edits rdf:XMLLiteral content.

Triplestore

One fuseki service replaces fuseki-admin and fuseki-end-user, holding an end-user and an admin TDB2 dataset per\n dataspace, declared in config/fuseki/config.ttl and persisted under fuseki/<dataset>/. Datasets are named after the\n dataspace origin with the deployment host dropped and the role appended: end-user, admin,\n northwind-traders.demo.end-user.

An existing deployment moves its two TDB2 directories under the new dataset names, points every lds:service in\n config/system.trig at http://fuseki:3030/<dataset>/, and merges the two stores heap settings and mem_limit.\n varnish-admin and varnish-end-user stay as they were. The triplestores page describes the\n resulting layout.

Client-side package composition

Composing package stylesheets into the client SEF needs the new sef-compiler service. A deployment with its own compose file adds it, the\n platform service's depends_on on it, and the ./sef bind mount at /var/www/linkeddatahub/sef.\n SEF_ROOT and SEF_COMPILER are optional: without them, packages compose server-side only, as in 5.10.0.

CLIENT_STYLESHEET names the client stylesheet the SEF is composed from, and defaults to the platform's client.xsl. A deployment\n bootstrapping its own sets it to that stylesheet's webapp path. Such a stylesheet must import the platform's client.xsl directly, and its\n layout prefers ldh:client-stylesheet() over its own SEF.

Package directory

A deployment with its own compose file adds the ./packages bind mount at /var/www/linkeddatahub/packages\n (PACKAGE_ROOT), where copies of imported package stylesheets survive a redeploy.

OAuth grants

The oauth2-login and oauth2-authorize grants move from the administration store to the end-user application's\n namespace-ontology.trig.template, as acl:accessTo on the login and callback URLs. An existing deployment re-seeds or migrates\n them.