SQI Infrastructure Platforms

Jeff Elpern

Table of Contents



This book presents a number of "horizontal" technology platform crafted by SQI is the process of developing the Client Interface Environment (CLI). These technologies address requirements faced by anyone building web-based business applications and thus provide a way to accelerate the development process by buying existing components.

An interesting aspect of this book is the usage of many of the components presented in its development.

How to Use This Book

The most current version of this book is available at current version SQI Infrastructure Platforms in both web view and PDF print ready. And, we do mean the most current as every author edit to a chapter immediately produces an updated web page of the chapter, an updated PDF for the chapter, and an updated PDF for the book. We referrer to this immediate publication in various formates an microPublishing.

microPublishing - Direct and Instant Updating

The SQI DocBook System combines the power of our Knowledge Base technology - direct input from content authors, continuous improvement, instants publishing, and extensive search - with the power of DocBook technology - extensive specialized markup for technical publication and multichannel publishing. The result is a on-demand environment where content experts can update material at any time, these enhancements are instantly published, updated material is instantly re-indexed, and html for the Web and PDF for printed output are simultaneously produced.

SQI Commitment to Instant PublishingThis book is an statement, and a working example, of the SQI philosophy of instant publishing. This book is a work-in-progress. All of the material is in draft form (some in rough draft form). Some of the How-To sections have example code with little of the description provided. But all of the material fulfills the SQI concept that any insight or new knowledge has value and needs to be quickly shared

Temporary Authoring Matters

[Note]Customization ToDo

The role attribute in the <inlinemediaobject> is not working - see the markup inside the para tag below. Both the html and fo use the first <imageobject>.

This para should have an inline Google logo in HTML and an inline Lexus logo in PDF.

However we are getting the Google logo in both HTML and PDF.

[Note]Customization ToDo

The font size for <code> - an inline tag - is now to small. I think it is picking up the changes in font size made to <programlisting>. The <code> font should be the same size as the default text.

Also, in the HTML this is not getting an inline layout (looks like a block treatment). The layout is fine in PDF

[Note]Customization ToDo

The subsections in the Preface, even in the techbook document style, should not be numbered.

[Note]Customization ToDo

The admonitions - <note>, <important>, and <warning> - need to have teh same layout and graphic in both the HTML and PDF views.


Authors Add. The document structure is here: Document Settings

InfraComps (last edited 2008-11-15 01:12:45 by jeff)