Gap Data

New Gap Data application: CPI

2010-09-17T08:22:00.004-04:00

The Cognitive Profile Inventory is available online at cpi.cognitiveprofile.com, and in sources at cpi.googlecode.com.

See also Yet another version of the Cognitive Profile.

Example app Astro

2010-02-13T23:27:00.003-05:00

Gap Data Astro is a live doc for another application example for Gap Data.

Cube Sat Web

2010-02-13T07:56:00.003-05:00

A fun thought experiment into some Gap Data work, the Cube Sat Web could be called the Gap Sat Web.

The hapax3 has moved

2009-12-02T15:55:00.011-05:00

The current development branch of Gap Data included a rollout of an initial version of Hapax3.

The LXL project has reassembled this work into something lighter, lxl-hapax3 in support of evolutions toward Fv3.

For Fv3, lxl-hapax3 templating will be used as to generate far plainer bean source code.

Fv3 is a desktop editor + browser programming framework for JOGL-2. Fv3 is planned as motivation for a lighter, less web more application, version of Gap Data.

Unlike Gap Data -- which created appengine data store beans -- Fv3 will use plain old java data beans as GL world configuration and programming..

..as TKX did, but lighter.

Cut to web site

2009-11-02T21:44:00.000-05:00

Gap Data will be very good at community sites. Being designed with an Atom Publishing / Open Social model, and for browser based content and programming, it will give its users a wiki like experience.

For the moment, installing Gap Data is a developer- centric process. But it's still in development and not very useful yet.

In future, an executable jar file could be built to install Gap Data from the desktop into your own Google Appengine space.

Push into frame

2009-11-02T21:01:00.004-05:00

The global frame of the problem that syntelos and gap-data pursue is web editing, collaboration and automation. This frame is contained by interaction, a subject perhaps best illuminated by Peter Wegner and Dina Goldin.

Within the gap-data frame is first appengine. A servlet container with a collection of APIs for scalable applications' development.

The first most important API in appengine would be the Datastore, a protobuf client for BigTable. BigTable is... a partitioned (sharded) sorted list (array) of strongly typed, structured data objects.

Gap Data generates and compiles java sourcecode for persistent application data structures over the Datastore API on BigTable.

These data structures are defined in an IDL-like schematic that abstracts from the code to be generated. The ODL schematic has a text representation as in the following example.

package gap.data;
path /templates;
  
child Template version 2
      parent Resource
      implements LastModified
      implements HasName
{
      Key key;
      *unique String id;
      *hash-unique String name;
      Long lastModified;
      Text templateSourceHapax;
      List.Short<TemplateNode> templateTargetHapax;
}

This example illustrates the web tools centricity of Gap Data's ODL, most specifically in the required qualified fields *unique and *hash-unique for the "/templates/310ab222bd" style of Web API that ultimately results. The unique field is the public web ID, and one or more hash-unique fields are required to produce (project) an ID for the class.

This example also illustrates the parent- child relationship. The class declaration headline shows that the Template class is declared as a child of the Resource class. We can see the use of another parent- child relationship in the case of the TemplateNode class as a child of the Template class. This relationship is declared as "short" in the field named "templateTargetHapax".

There are two kinds of parent- child relationships among these network data structures: long and short. The long relation is suitable for large numbers of the child class in the relation, and the short is suitable for small numbers of instances of the child class in the relation. The short is an entity group, while the long is not. The entity group requires all of its elements to be contained within one BigTable shard or partition. Typically one has designed with a theoretical upper bound of ten or a perhaps a hundred objects in an entity group.

In the particular case of the Template and its parsed GapData/Hapax3 TemplateNodes, we're pushing the entity group into relatively large numbers (e.g. a thousand instance objects in the list) for another reason. The coherency of this list is very particular as the parse tree of the field of type Text named templateSourceHapax.

And we're doing that -- persistenting a parse tree -- in service of our design program for federated collaboration and automated modification. In doing so, we've found a structure for the problem- solution set for collaboration and modification in terms of interaction: an otherwise messy problem is conceived in a crisp and clean interactive coulple

The Template class description has a few more features. The class declaration "headline" includes an "implements" keyword for java binding programming language interfaces into the generated class. The interfaces in the example describe the fields lastModified and name. And finally, the "path" feature identifies the Web API path element for the class, it's leading slash is merely notational.

From these schematic object descriptions, Gap Data generates java source code for a class that implements persistent and network data binding. Common application programming functions are generated as static methods for creating, retrieving, updating and deleting instances and lists of the class with respect to storage. And instance methods are generated for binding data to supported network I/O formats.

These classes are generated via Hapax3/CTemplate, so features are readily added and classes regenerated.

What it is

2009-11-02T15:37:00.001-05:00

Gap Data applies the Syntelos idea set to Google Appengine,

The essential syntelos idea is for complete server side configuration and programming in the web browser. It's an idea that's been a part of the web since its inception. Tim Berners-Lee wrote about content editing in the browser in his original road map for future directions. The CGI interface implemented by some servers would naturally extend content editing to scripts editing.

However it's an idea that has yet only barely emerged. Entrants into the field of online app creation are few, and include Zoho Creator, Salesforce, DabbleDb, WyaWorks, QuickBase, YadaShare, and Rollbase.

The syntelos and gap-data approach is in open source. Making it markedly different from the commercial solutions.

More importantly, the syntelos / gap-data development includes its relations in Computer Science from Federated Systems to Artificial Intelligence.

One of the classic problems in Federated Systems is the shared editor. Multiple people working on the same live- shared resource at the same time. Examples of the shared editor can be found in the Google Apps.

The relation to Artificial Intelligence is a conception of a network automaton's software as modified across network peers.

The lessons learned from these various studies are incorporated into the development of web tools that are good for machines, and good for people, too.