This site intends to enable wider adoption of the ideas and methods illustrated here, while preventing or mitigating

• the extent to which the tech transfer imposes costs and expenses of its own
• the extent to which the tech transfer benefits private interests and not the public interest as a whole
  • thereby undermining one of the goals of standards-based technology, namely to support non-proprietary approaches along with proprietary ones

Assuming we wish to attempt technology transfer at all, these have to be assumed as factors and risks. To type this line incurs a cost. Similarly, the benefits of the technology transfer will not accrue evenly to everyone simply because certain audiences, users, and constituencies are in better positions than others. What we can do is try to ensure the proverbial level playing field by not picking favorites.

This model is intended to achieve technology transfer goals in view of these factors, and is reflected in the Maintenance and Support plan defined for the project.

"Weightless" tech transfer

The technology transfer model being adopted by this demonstration (repository and live web pages) might be termed "weightless" in the sense that it aspires to be as easy as possible by making it as lightweight as possible.

This is in keeping with the "Least Power" principle (see Controls). When nothing is needed but a transformation or mapping from a declarative syntax into an application format, nothing is provided except what is needed to make this occur and illustrate how it is done.

Accordingly:

• Everything is maintained in git and kept publicly accessible on Github for forking or cloning.
• All resources are kept open and transparent, not packaged and opaque.
• Functionality is 'level' (same for all users); there are no accounts or privileges to manage.
• Dependencies on external software libraries are kept to zero wherever possible.
  • A plain web server works fine serving files locally or over the network.
  • Since applications never save or transmit data, there is no back end to maintain either.
• The project maintenance model entails a strong focus on documentation (enabling others to build) rather than on new features of old demonstrations.
• You don't need to use the public demonstration portal: feel free to run your own copy of the XSLT Blender.
• While credit to the project must be included (as per licensing), your adaptation of the XSLT Blender does not need to follow this maintenance or tech transfer model -- adapt to your purposes.