@prefix rdf: . @prefix ns1: . @prefix foaf: . ns1:this rdf:type foaf:Person . @prefix atom: . rdf:type atom:Feed . @prefix sioct: . rdf:type sioct:Weblog . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . rdf:type atom:Entry , sioct:BlogPost . @prefix dc: . dc:title "Contd: Ajax Database Connectivity Demos" ; foaf:maker ns1:this ; rdfs:label "Contd: Ajax Database Connectivity Demos" . @prefix dt: . @prefix dcterms: . dcterms:created "2006-06-01T22:48:00-04:00"^^dt:dateTime ; dcterms:modified "2006-06-22T08:56:58-04:00"^^dt:dateTime . @prefix sioc: . sioc:id "4451993f159ad0c54fe24be7dc63d780" ; sioc:link ; sioc:content "\n Last week I put out a series of screencast style demos that sought to demonstrate the core elements of our soon to be released Javascript Toolkit called OAT (OpenLink Ajax Toolkit) and its Ajax Database Connectivity layer. The screencasts covered the following functionality realms: SQL Query By Example (basic) SQL Query By Example (advanced - pivot table construction) Web Form Design (basic database driven map based mashup) Web Form Design (advanced database driven map based mashup) To bring additional clarity to the screencasts demos and OAT in general, I have saved a number of documents that are the by products of activities in the screenvcasts: Live XML Document produced using SQL Query By Example (basic) (you can use drag and drop columns across the grid to reorder and sort presentation) Live XML Document produced using QBE and Pivot Functionality (you can drag and drop the aggregate columns and rows to create your own views etc..) Basic database driven map based mashup (works with FireFox, Webkit, Camino; click on pins to see national flag) Advanced database driven map based mashup (works with FireFox, Webkit, Camino; records, 36, 87, and 257 will unveil pivots via lookup pin) Notes: \u201CAdvanced\u201D, as used above, simply means that I am embedding images (employee photos and national flags) and a database driven pivot into the map pins that serve as details lookups in classic SQL master/details type scenarios. The \u201CAjax Call In Progress..\u201D dialog is there to show live interaction with a remote database (in this case Virtuoso but this could be any ODBC, JDBC, OLEDB, ADO.NET, or XMLA accessible data source) The data access magic source (if you want to call it that) is XMLA - a standard that has been in place for years but completely misunderstood and as a result under utilized You can see a full collection of saved documents at the following locations: My Mashups demo directory (Google and Yahoo! demo variants but note these do not work with Safari or IE at the current time. IE7 issues will be resolved in the next day or so) My Pivots demo directory (other Pivots will be added as I build and save them) My Saved Queries (a collection of saved QBE generated queries) \n" ; atom:title "Contd: Ajax Database Connectivity Demos" . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container ; sioc:links_to , , , , , , , , , , , , ; atom:source ; atom:author ns1:this ; atom:published "2006-06-02T02:48:00Z" ; atom:updated "2006-06-22T12:56:58Z" . @prefix opl: . opl:isDescribedUsing . ns10:this rdf:type sioc:User . @prefix rdf: . @prefix ns1: . @prefix foaf: . ns1:this rdf:type foaf:Person ; foaf:made . @prefix atom: . rdf:type atom:Feed . @prefix sioct: . rdf:type sioct:Weblog . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . @prefix sioc: . sioc:container_of ; atom:entry ; atom:contains . @prefix ns7: . ns7:this rdf:type sioc:User ; sioc:creator_of .