Details

Kingsley Uyi Idehen
Lexington, United States

Subscribe

Post Categories

Subscribe

E-Mail:

Recent Articles

Display Settings

articles per page.
order.
Web-enable Your Business Intelligence Using XML/A and ASP.NET

Don't you sometimes wish that accessing database data were easier, and you didn't have to deal with such things as OLE DB, ODBC, and JDBC—that you could use just one uniform approach to access the data regardless of the location and type?

Yes, but I don't see how any of the data access mechanisms listed have anything to do with the problem as each serves a different application domain.

Well, guess what? You won't have to wait too much longer to see this dream become reality. All major vendors are not only working on this issue seriously but have already started releasing SDKs for exactly this purpose. The point of commonality between them is XML. Like it or not, XML is becoming a standard part of programmers' lives because it's simple and easy to understand structure make it a suitable format for transferring data between disparate applications and platforms. But the real power of XML lies in its ability to not only extend itself, but also define itself.

This is all well and good but it is XML, yes a uniforming technology, but the opening paragraph undermines the pont!

XML For Analysis is just another addition to the pool of data access mechanisms, it is an XML./SOAP based data access mechanism for Tabular and Mulitdimensional Data and without our implementation XMLA simply offers little to anyone trying to get at tabular data (SQL Data) as many of the current implementers fall into the OLAP camp, and there is no standard query language for persistenf CUBES (MDX from Microsoft is de facto at best). Thus, without Virtuoso tabular data (where the real data actually resides) is out of the picture.

So we say goodbye to ODBC, JDBC, OLE DB to get what exactly? From our perspective, another showcase opportunity, but for the innocent readers of this article I haven't got the faintest idea.

 

# PermaLink Comments [0]
05/29/2003 16:01 GMT-0500 Modified: 06/22/2006 08:56 GMT-0500
Web-enable Your Business Intelligence Using XML/A and ASP.NET

Don't you sometimes wish that accessing database data were easier, and you didn't have to deal with such things as OLE DB, ODBC, and JDBC—that you could use just one uniform approach to access the data regardless of the location and type?

Yes, but I don't see how any of the data access mechanisms listed have anything to do with the problem as each serves a different application domain.

Well, guess what? You won't have to wait too much longer to see this dream become reality. All major vendors are not only working on this issue seriously but have already started releasing SDKs for exactly this purpose. The point of commonality between them is XML. Like it or not, XML is becoming a standard part of programmers' lives because it's simple and easy to understand structure make it a suitable format for transferring data between disparate applications and platforms. But the real power of XML lies in its ability to not only extend itself, but also define itself.

This is all well and good but it is XML, yes a uniforming technology, but the opening paragraph undermines the pont!

XML For Analysis is just another addition to the pool of data access mechanisms, it is an XML./SOAP based data access mechanism for Tabular and Mulitdimensional Data and without our implementation XMLA simply offers little to anyone trying to get at tabular data (SQL Data) as many of the current implementers fall into the OLAP camp, and there is no standard query language for persistenf CUBES (MDX from Microsoft is de facto at best). Thus, without Virtuoso tabular data (where the real data actually resides) is out of the picture.

So we say goodbye to ODBC, JDBC, OLE DB to get what exactly? From our perspective, another showcase opportunity, but for the innocent readers of this article I haven't got the faintest idea.

 

# PermaLink Comments [0]
05/29/2003 16:01 GMT-0500 Modified: 06/22/2006 08:56 GMT-0500
Weblog API Multiplexer
Weblog API Multiplexer After reading this article by Ben Hammersley, it stuck me that what the weblog community needs is a Weblog API Multiplexer service. This would be a service that would accept a ping containing some posting info, e.g. the entry's trackback... [via Internet Alchemy]
 
I smell new Virtuoso Blog features here. This article sheds light on the fundamental value of Web Services, and its intersection with emerging blog section of the SemWeb (Semantic Web), without explicity seeking to do so (based on my reading).
 
At the time making this blog entry, it would be nice if I could create a metadata entry that references this article (make a statement about the article in general, and then make a specific statement about "intersection" as used above).  Yes, "intersection", what does this mean (as used in my paragraph above)? That where ontologies come into play, the use of "intersection" means something to me (but not the the SemWeb client that pick of the statement from my metadata repository; RDF doc for instance).
 
So we need to have standard annotation terms (ontologies) when persisting metadata statements (RDF).
# PermaLink Comments [0]
05/29/2003 12:25 GMT-0500 Modified: 06/22/2006 08:56 GMT-0500
Weblog API Multiplexer
Weblog API Multiplexer After reading this article by Ben Hammersley, it stuck me that what the weblog community needs is a Weblog API Multiplexer service. This would be a service that would accept a ping containing some posting info, e.g. the entry's trackback... [via Internet Alchemy]
# PermaLink Comments [0]
05/29/2003 12:25 GMT-0500 Modified: 06/22/2006 08:56 GMT-0500
         
Powered by OpenLink Virtuoso Universal Server
Running on Linux platform
The posts on this weblog are my personal views, and not those of OpenLink Software.