Page 228 of 333
The information in the present chapter on standards is somewhat outdated but is still included here as it is better than nothing.
Informally, and from the point of view of the user, Logiweb is an authoring tool like the lgc compiler.
Formally, however, Logiweb is something completely different; Logiweb is a byte code format with an associated semantics plus a protocol.
Documents stored in the Logiweb byte code format are named Logiweb vectors, and the semantics of such Logiweb vectors is defined as the actions a Logiweb compliant browser is supposed to perform when loading such a vector. Those actions are specified by the semantics.
At the time of writing, there is no stand-alone Logiweb browser. Instead, the lgc compiler is able to perform loading. Furthermore, lgc renders Logiweb pages in html, pdf, and other formats, ready for viewing in ordinary web browsers.
In previous releases, Logiweb also included a server which ran silently in the background. In the present release there is no server and the tasks of the server are taken care of by the path parameter of lgc. The server will re-appear in later releases, but in a separate package for webmasters. When the server re-appears, it will be possible to construct web-sites which provide access to all published Logiweb pages based on their references.
Logiweb documents are transferred using the Hyper Text Transport Protocol (http). Hence, Logiweb has no need for a protocol for delivery of Logiweb vectors. Rather, Logiweb servers have a need for a protocol for locating Logiweb pages given their unique references. All Logiweb servers in the world are supposed to cooperate on locating Logiweb pages, and they are supposed to do so using the Logiweb protocol. A description of the protocol formulated in the format of an Internet Draft can be found here.
Page 228 of 333
Copyright © 2009 Klaus Grue, GRD-2009-10-01