Monday, July 19, 2004

XQuery, XDS and Oracle

Integrating Data Using XML Data Synthesis "XDS provides an easy-to-use declarative framework to plug-in and query across the information sources. Instead of writing custom applications to access information from disparate information sources, customers have a choice of using XDS to build their information integration applications."

"There's a lot of similarity between the technologies Andrew links to, together with what Oracle are trying to achieve with XDS and XQuery, and what we're trying to do with business intelligence, data warehousing and data mining. It wouldn't suprise me if we start to hear more about XML, XQuery, RDF and so on in a business intelligence context in the future, and I fully expect these sorts of technologies making their way into Oracle's BI & knowledge management products over the next few years."

I've mentioned Oracle's recent interest in RDF here and here.

Saturday, July 17, 2004

SW is Vietnam

Johnson and FDR "I'm thinking of course of the great commander-in-chief of the Semantic Web, Tim Berners-Lee. Like Johnson, he had a vision for a great society, the HTML web, but let it languish while he fought a no-way-to-win war in Semantic Web Land".

So when did the French try the Semantic Web?

That was quick

Explanation of the Network Inference DAWG Strawman Objection "...the working group outright rejected any requirement or objective which expressed any commitment, at any level, to XQuery.

We believe that the DAWG working group is making an egregious error by rejecting any level of commitment to XQuery at this critical juncture."

"Regardless of outcome, Network Inference will remain devoted to our customer feedback by continuing our XQuery support for query-driven inferencing across RDF and OWL data inside our Cerebra Server product family."

Friday, July 16, 2004

Semantic Web and MDA

The July edition of the MDA Journal "...the only thought I had as to the potential for integrating the Semantic Web and MDA was the idea a rather obvious one to MDA aficionados that MOF metamodels of the Semantic Web languages would help to integrate ontologies into the MDA world. I did not appreciate the role that reasoning could play in making MDA more scalable."

"As ontologies move into industry they need to coexist with industrial metadata. We do not want ontologies to become yet another silo in a fragmented metadata landscape. Since much enterprise tooling is moving toward MOF-based metadata management, a minimal goal would be to make it possible for MOF-based tools to physically manage ontologies using the common MOF mechanisms."

"In order to achieve the goal of using MDA and the Semantic Web together, the OMG issued an RFP that calls for standardizing the following:
* A MOF metamodel for ontology definition
* A UML profile for ontology definition
* A mapping between the UML profile and the MOF metamodel".

Found by “Semantic Web” applied.

RDF Querying going to the DAWGs

The most recent DAWG face-to-face raised some interesting issues with respect to using XQuery for querying RDF. Jim Hendler has a response:

"You show RDFS/OWL/Rule query langauges as somehow being more easy inXquery, but again I think that is because you are assuming these things will be kept in their RDF/XML documents, or in APIs that respect the "boundaries" of those. I already see many applications moving towards multiontologies w/linking, and that seems to me to argue that we simply don't know yet which of these models are better."

The original proposal suggests that we're going to need a query language for OWL, Rules and RDF, which probably won't happen and it's suggested without proof. It also suggests that because RDF can be serialized in XML that it has something in common with XQuery, which is untrue. The standard RDF/XML serialization can have multiple forms of the same RDF graph. The same RDF query will work across different RDF/XML serializations, because it is operating on the same data model, this isn't true for XQuery.

It reminded me of the recent anti-XQuery article, "If You Liked SQL,You'll Love XQUERY".

Fabian is saying that the relational model was a simplification of graph theory. In this respect relational theory and RDF have much in common, much more in common than XML.

At a syntactic level, query languages like RDQL, iTQL and other SQL-like RDF query languages are leveraging off a legacy of SQL, Datalog and other similar languages. This is something that XQuery lacks as well. Do we really want FLWOR and Conditional Expressions in our query language?

Fabian also mentions NULLs, a continual pet peeve of the anti-SQL crowd, it's good to see XQuery avoids this. Something that I hope an RDF query language avoids as well.

Interestingly, Don Chamberlin's XQuery tutorial is quoted both by Fabian and in Jeff's proposal.

Andrae is also blogging some of this as well, "Jumping the gun".

Thursday, July 15, 2004

New co-Chair of SW Best Practices

"This is to inform you that as of 14 July 2004, David Wood of Tucana Technologies joins Guus Schrieber of Ibrow as co-Chair of the Semantic Web Best Practices and Deployment Working Group (SWBPD) [1]. We wish to express our thanks to David and Tucana and to Guus and Ibrow for their generous support of the Semantic Web Activity."

Fwd: W3C Announcement: David Wood, New Co-Chair of the Semantic Web Best Practices and Deployment Working Group

Querying with Rules

ISWC 2004 Research Track: Accepted Papers the first paper titled "Query Answering for OWL-DL with Rules", when plugged into Google gave two interesting papers:
* Answering DL Queries using Deductive Database Techniques and
* Rules and Queries with Ontologies: a Unified Logical Framework.

This is appropriate for our current TKS work, see Paul's blog for more details.

Everything New is Old Again

A short while ago I wrote, Accessing vs Naming Models. I was unaware that @semantics had done a presentation called "A naming mechanism for the RDF model" which lists the RFCs: 3401, 3402, 3403 and 3404 (both interesting) and 3405.

There's also the older, yet still relevant THTTP specification for encoding resolution into a HTTP request.

I was aware of the Handle System, which is for documents, and has its own RFCs including RFC 3650.

I think I got rid of all the times I tried to type RFC and my hand spat out RDF.

Wednesday, July 14, 2004

Supersonik

MOLVANIA DISQUALIFIED FROM EUROVISION! "The tiny Eastern European republic of Molvania was disqualified from the Eurovision Song Contest this year.

Zladko “Zlad” Vladcik was to perform his very popular techno-ballad, “Elektronik – Supersonik” - described as “a melodic fusion combining hot disco rhythms with cold war rhetoric”."

"Hey baby, wake up from your asleep
We have arrived on to the future,
And the whole world has become...
Electronic... Supersonic...
Supersonic... Electronic"

Champagne comedy indeed...by Working Dog.

Via Metafilter.

Discretization

semantic what? "people don't want to manage. people want to interact. applications that want users to enter metadata that enable management, at least in the consumer marketplace, are doomed to failure."

And while a little unreadable, The unbearable inevitability of discretization is an interesting rant about the Semantic Web and all things in general:
"Evolutive efficiency also applies to the Semantic Web. Luckily for us, it benefits from two distinct evolutionary avenues. It indeed gains effectiveness both from cleverer agents and from semiotically-complete ontology representation formats (relational databases, XML/RDF, OWL, UML, etc.). Therefore, with some site correctly implementing the Semantic Web-enabling technologies, one is right to argue that the Web already shows some signs of semantic intelligence.
Discretization is the fundamental mechanism behind any form of cognition. Solve et coagula-based computing rules!"

For XML Users

An no-nonsense guide to Semantic Web specs for XML people (Part I) "The Semantic Web has a serious problem: the XML people don't understand it.

They think it's an utterly complex way to write metadata that you can do with simple namespaces. The two worlds (despite being both hosted inside W3C) don't talk very much. Many (if not all) W3C folks are all in the RDF camp (and have been there for a while) and they see XML as a half-baked attempt to solve issues that RDF already solves. Unfortunately, not having been in the XML camp at all, they have no way to communicate with the other side.

The XML camp, on the other hand, thinks that they know how to build things that work, while the RDF people are all sitting in their ivory towers telling them that what they are doing is wrong, but without understanding their real-world needs.

As it normally happens in a debate, both are right and both are wrong. "

Tuesday, July 13, 2004

Nature nuturing Oracle

A presenation by Nature Publishing Group looking at Oracle's NDM as an RDF store, the last slide:
"NPG and Oracle investigating the suitability of the NDM to store and query
RDF-encoded information
o Storage looks OK
o Can hold directed labelled graphs
o Allows URIs, literals and blank nodes
o Can include provenance information

Querying may need more development:
o Can extract sub-graphs but performance and scalability need to be tested
o RDF/XML import and export would be desirable
o Support for RDFS- and OWL-based inferencing"

Mentions Urchin.

Monday, July 12, 2004

Ontologies for the Web

Leveraging Ontologies: The Intersection of Data Integration and Business Intelligence, Part 2 "The real significance of ontologies - leveraging the reusable aspects - is within vertical domains where the use of common meta data, services and processes has the most worth. Once we get semantics under control within vertical systems (more often, a collection of systems), data integration, or linking a common set of semantics to back-end systems, won't be as daunting as this process is today. What's more, the application of standards such as Semantic Web and OWL will make ontologies that much more attractive."

Sunday, July 11, 2004

N3QL

N3QL - RDF Data Query Language "N3QL is an implementation of an N3-based query language for RDF. It treats RDF as data and provides query with triple patterns and constraints over a single RDF model. The target usage is for scripting and for experimentation in information modelling languages. The language is derived from Notation3.and RDQL."

Part of CWM.

WebMethods and RDF

WebMethods, for One, Believes in UDDI " But UDDI doesn’t paint the whole development picture, which Glass believes may partially explain why its adoption has been slow. “In its current version, UDDI is not well suited for metadata about everything. If you’re building an application out of parts, Web services is only one portion.” Others might include portals, portlets, schemas and business processes, among other things.

Glass said WebMethods has been looking at specifications for publishing metadata of other types, such as the W3C’s Resource Definition Framework (RDF). “This looks promising as a way to represent a broader array of metadata than simply that of Web services. And in [the forthcoming] UDDI version 4, there’s a lot of work on leveraging RDF.”"

Friday, July 09, 2004

Pay me!

Eternal Refactoring "Some may consider Semantic Web developers to be very much concerned with the abstract, but a recent thread shows that good old materialism is as good a driver for progress on the Semantic Web as anywhere.

Many of us, no doubt, employ the wishlist facility on Amazon to communicate our birthday needs to distant relatives. The decentralization of this seems like a natural target for RDF-savvy developers."

More metadata than data (again)

Anyone who has done any work on RDFS/OWL won't be surprised by this, Behind the Scenes at Yahoo Labs, Part 2:

"I would claim that there is more implied data (or inferable meta-data) than "raw" data on the web, and that we are barely scratching the surface of it. Today, all search engines are scraping for some simple forms of implied data: language, locality, etc. What's missing from this list is a nearly infinite collection of relationships that are obvious to most any human reader but extremely difficult to infer from a single document. The reason why implied data is so hard to identify is because, in the aggregate, it forms our collective cultural wisdom."

Thursday, July 08, 2004

Oracle's RDF Store

Create a logical Network Data Model in Oracle and it would be great to store RDF. That was what I thought after reading "Re: Chemistry and the Semantic Web".

The attached document is based on articles available from Oracle. An indepth description is available in "Network Data Model Overview" (free registration required).

There are various schemas defined for storing networks which includes:
"NODE_NAME VARCHAR2(32) Name of the node.
NODE_TYPE VARCHAR2(24) User-defined string to identify the node type."

The schema is obviously not designed to store RDF unlike other RDBMS mappings.

One difference is their flexibility in storing different graphs and giving links a "cost".

Another difference is their nodes and links are typed as strings; this looks like it would limit the effectiveness of data type operations. Querying for all nodes that are numbers between two values or dates between two ranges is going to be costly compared to dedicated data type handling. That's apart from the obvious difficulty in trying to put everything into a VARCHAR2(24).

Unless they have optimised the query layer specifically for the task, which might be case, it will also incur the costs of joining against the same table many 10s or 100s of times.

It does have some neat operations (like shortest-path), a Java API, PL/SQL integration and of course it integrates well with existing Oracle databases.

Tuesday, July 06, 2004

Kowari 1.0.4 Released

New in this release (links to kowari.org will be inside a frame):
* Walk and transitive constraints.
* Backup individual models.
* Automatic reconnect of the iTQL Swing UI when the server restarts.
* Constructing Jena and JRDF with sessions rather than databases to allow multiple access.
* Sub-queries and the greater-than/less-than constraints are much faster.

Download here.

Monday, July 05, 2004

A Simpler Time

I read recently that someone thought animation was the key to Java's early success. JAVA TECHNOLOGY: THE EARLY YEARS "Next, Gosling and Gage pushed the audience over the edge with an animated line-sorting algorithm that Gosling had written.

In each of three sets of horizontal lines of random lengths, the demo sorted the collection by size, from shortest to longest, by actually moving them up and down in the browser. The audience had never seen anything but static images in a browser before this: The lines were moving, as if being sorted by unseen hands!

Suddenly, everyone in the room was rethinking the potential of the Internet. Far from the crash-and-burn scenario Gosling had first envisioned, his demo had jolted a very influential audience off their seats, and they were delivering enthusiastic applause. And within this technology-entertainment crowd, word would spread quickly."

That draw dropping demo still runs, too.

Sunday, July 04, 2004

Java Rules

The Mandarax Project "Mandarax is based on backward reasoning. This fits perfectly in a computing landscape based on a pull model (e.g. a transaction initiated from a web site). Data (e.g., from relational databases) can be integrated on the fly at query time, no replication is necessary (see the manual for a more detailed discussion of "Mandarax vs. RETE")."

The manual says: "The mandarax inference engine uses backward reasoning, and the reference implementation uses an object ­oriented version of backward reasoning similar to the algorithm used in Prolog. On the other hand, most commercial rule systems such as ILOG and popular open source solutions like CLIPS and JESS use forward reasoning, in particular an algorithm called RETE. This algorithm keeps the derivation structure in memory and propagates changes in the rule and fact base."

A description of the RETE algorithm is here.

Desktop Metadata

RDF For Desktop Metadata? "There is an article "Metadata for the desktop" that suggests that RDF should be used to describe data in desktop environments. This is an interesting idea. RDF is already used by Creative Commons to attach license metadata to its works. Mozilla also supports it. RDF was designed for the web, but can it also find its way to the desktop? And what metadata is most important to describe?""

Comments link to: WinFS is not filesystem, Spotlight, rdf semweb winfs, Haystack, Questions about Longhorn, Pike and libferris.

Friday, July 02, 2004

Blast from the Past

The Ur-Quan Masters "The project started in August 2002, when Toys For Bob released the partially ported sources of Star Control 2 3DO version to the fan community. Our goal is to port this wonderful game to current personal computers and operating systems. It is and will remain 100% free of charge, and anyone can contribute to the project and thus help make it even better."

Many wasted hours spent playing this the first time...

Thursday, July 01, 2004

Updated Kowari Site

The new kowari.org web site is up. The only negative is that it's now framed based; the website equivalent of SOAP. The positive is that it's now more up-to-date and includes documentation for Kowari 1.0.4. There's more to come including the Javadoc and the Jena tutorial.

Word! The DOPE Project

A recent IEEE article, Exploring Large Document Repositories with RDF Technology: The DOPE Project "(Drug Ontology Project for Elsevier) explores ways to provide access to multiple life-science information sources through a single interface."

"Current per-formance problems stem mostly from query procedures between the Sesame system and the Collexis-SOAP interface. We plan to address these problems by expanding DOPE with other data sources and thesauri."

Download and project page here.

FOAF next for Feedster?

An Interview With Feedster’s Scott Rafer, Part II "All this semantic web stuff is derived from a file format called RDF. RSS is a very simple version of that. The next one to gain any popularity is FOAF, which stands for “friend of a friend.” Under the hood, several of the social networks, LinkedIn, Tribe, maybe a couple of the others, are FOAF-based, and it’s very easy for them to start turning all those relationships into feeds, if they want. And that’s what I personally want, given my own habits. I know a lot of people in my “second degree” in LinkedIn. If I could have a feed of my second degree, as it increases, so I could go into my RSS aggregator and just hit links for “Yes, I know that guy” or “No, don’t know him,” they would end up with a much richer database, knowing more about me and my network. It would be really time efficient, and I’d be even more likely to pay for their service when they start charging."

RDF Query Languages

Design Evaluations Links Includes: SeRQL, RDQL, REX, iTQL, Algae2, and TriQL. Also links to Versa, BRQL and XsRQL (interesting given a recent anti-XQuery link).

RDF - Just don't mention the Semantic Web

Metadata for the desktop "My premise then is that more metadata is required to create a usable desktop for users and manage the increasing volume of information stored in our homes. That's a conclusion other people are agreeing with, too. Microsoft's next-generation operating systems will ultimately include WinFS, a file system supporting the attachment of arbitrary metadata to files. Mac OS X is acquiring similar functionality. ReiserFS has been trying to do it for ages. Closer to GNOME, there are projects like Dashboard, Storage and iFolder."

"First introduced in 1998, the W3C's Resource Description Framework is a computer-processible way of describing things. And that's about as simple as it gets. Despite being mired for some time in controversy over an awkward XML expression, the current view and consensus over RDF is in terms of its data model. The data model is simple and expressive, and is the best starting point for understanding RDF."

Tuesday, June 29, 2004

Jena Ported to .NET

JenaNet "This is a port of the Jena2 Semantic Web API to the .NET framework. We will be converting the Java API into the .NET framework so as to gain the best Semantic Web engine possible."

Sun sponsored XML for Swing

JDNC At last.

Spotlight - Metadata Done Right?

Mac OS X Tiger: Search Technologies "The metadata engine makes searching smarter, more flexible and powerful by indexing the descriptive informational items already saved within your files and documents. Metadata describes the “what, when and who” of every piece of information saved on your Mac: the kind of content, the author, edit history, format, size and many more details. Most documents, including Microsoft Word documents, Photoshop images and emails, already contain rich metadata items. By using this indexed information for searching, you can tap into tremendous power and accuracy for refining search results."

The list of file formats are fairly standard but the cool stuff is probably the API layers. Part of Spotlight. See also, Does Spotlight == BFS?.

The example screen shots show rendering Slashdot's RSS feed and they also claim support for Adobe Photoshop. So that seems to suggest a limited support support of RDF - RSS 1.0 and perhaps XMP. Back in 2003 I found mention of metadata in OS X; it's a shame it's taken this long ;-).

And the new 30" monitors save you money. Buy 10, buy 100...

Monday, June 28, 2004

Radar Networks Decloaks

Minding the Planet: From Semantic Web to Global Mind "As the global mind develops it will initially be focused around making information more useable. But that will be just the beginning. Already a new generation of tools that will bring the power of distributed intelligence to the desktop and the enterprise are being developed in labs such as HP, Cycorp and Network Inference. In addition to these projects, my company,Radar Networks has developed a complete platform in Java for developing and deploying Semantic Web applications for the desktop, enterprise and Web – most of our platform will be released as open-source code in 2005 as part of a research project we are working on for SRI (more news about this project in the future!). Following the initial open-source release, we plan to offer a commercial version of the Radar Platform as well as related applications, services, solutions and support for enterprises and developers."

"Of course for this to work lots of new infrastructure is required. There are also numerous issues that arise as soon as one digs deeper into the subject -- issues related to data synchronization, privacy and security, ontology integration, policies and many other subjects. My company, Radar Networks' software platform (to be released as LGPL in 2005) will provide an open-source framework that solves many of these problems and will enable the open community to collaborate to solve any that remain or are found in the future."

Danny beat me to it.

Accessing vs Naming Models

We recently had a use case where the directory where the triples were persisted moved to a different machine or where the host name of the machine frequently changed (moving from network to network).

Our existing scheme for naming models takes the form:
protocol://hostname/servername#modelname

Which usually becomes:
rmi://www.kowari.org/server1#model1

This is pretty brittle given the above use case. We've known for quite some time that our model naming scheme confused two distinctive properties:
* How to access the model, and
* The name of the model.

By ignoring this issue we could get around to adding views, security and the iTQL FROM and IN clause.

However, we now have the need to uniquely identify the model as well as continuing to support the old naming scheme. The currently proposed idea is to first map the URL of a model to a URN so that:
<rmi://fully.qualified.hostname/server1#model1>

Becomes:
<urn:fully-qualified-hostname:server1:model1>

This also allows us some added flexibility such that you can now have names for RSS feeds and external models that can be described using:
<urn:slashdot-org:news-rss> <access> <http://slashdot.org/news.rss>
<urn:my-com:server1:hr> <access> <rmi://localhost/server1>

The second entry refers to a local copy, which can be changed to:
<urn:my-com:server1:hr> <access> <rmi://my.com/server1#hr>

Which will access the live version of the database. It will break some of the current functionality in iTQL. This is where it creates a model on the fly if it happens to use an external model. For example:
select $s $p $o
from <http://slashdot.org/rss.xml>
where $s $p $o ;

This downloads the RDF and puts it in a model. Subsequent calls will be done against the local model. Also, iTQL doesn't implicitly have a default host so you must give it another way of giving the connection.

The simplest way is to create the mapping when creating a model:
create <urn:slashdot-org:rss-feed> <http://slashdot.org/rss.xml>

In the future, resolvers will have configuration settings so you could make statements such as:
<urn:slashdot-org:rss-feed> <updateOnlyIfChanged> <every 5 minutes>

Once created, it can then be accessed in the FROM:
select $s $p $o
from <urn:my-com:server1:hr> and <urn:slashdot-org:rss-feed> <rmi://my.com/server1>
where $s $p $o ;

This will do a set operation over the two listed models as defined in the Kowari/TKS server at "my.com".

However, this can get verbose so we'll probably borrow something from RDQL and the like and add a USING clause:
select $s $p $o
from <urn:my-com:hr> and <urn:pi-com:cal>
where $s $p $o
using <rmi://my.com/server1> ;

Or alternatively, we could set the server before doing a query using:
set server <rmi://localhost/server1> ;

To turn it from a local query to a distributed query (a TKS only feature):
set server <rmi://my.com/server1> for <urn:my-com:hr> ;
set server <rmi://pi.com/server1> for <urn:pi-com:cal> ;

Sunday, June 27, 2004

Illegal iPod

Dirty rotten inducers - the law the IT world deserves? "It may soon be possible to carry around an AK-47 assault rifle and an iPod with you down the street - and be arrested for carrying the iPod."

Prelude to a Fake Complaint "Apple's iPod music player seemed particularly vulnerable to attack. Any major record label could bring a strong lawsuit against Apple for "intentionally inducing" infringement under this new law with the iPod, both because it's plausible to argue that having an iPod enhances the lure of using P2P to download music (gotta fill all that space!) and because all the major record labels still believe that private sharing of songs from your CDs with friends is copyright infringement. We still disagree with the labels on these points, but the reality is that no court has yet convinced them that their legal theories are flawed. We also threw in Toshiba for making the iPod's hard drive and CNET for showing people how to move the iPod's music files."

Saturday, June 26, 2004

Jena Jumble

* SWeDe "...OWL editor [and] integrates existing tools like the OWL Validator, Kazuki (OWL to Java code generator), and DumpOnt (Ontology Visualizer)." See also, using Kazuki (requires Jena).
* Introduction to Jena "RDF is increasingly recognized as an excellent choice for representing and processing semi-structured data. In this article, Web Developer Philip McCarthy shows you how to use the Jena Semantic Web Toolkit to exploit RDF data models in your Java applications."
* BRQL "This document describes the Bristol RDF Query Language, or BRQL (pronounced 'burkol'), designed to meet the requirements and design objectives described in the W3C RDF Data Access Working Group (DAWG) document RDF Data Access Use Cases and Requirements (and its working version). This query language is based on RDQL Member Submission."

Friday, June 25, 2004

Kowari Bloggers

Kowari "Even though I’ve never tried it, I already have quite an attachment for the Kowari triplestore, due to reading More News from Andrew Newman and Paul Gearon’s remarkable Working Notes - perhaps the most special-interest blog I’ve come across (recently featuring their battle with unclosed Tuples…)"

This seems like the ideal time to mention that Andrae is joing the Kowari blogging craze with Etymon.

Kowari on XML.com

A First Look at the Kowari Triplestore "Kowari is a solid tool created by an enthusiastic, knowledgeable team. That said, it's not for everyone: the architecture of the application is clearly focused on the server, and developers looking for an embeddable RDF store for desktop apps will likely want to look elsewhere, unless they are willing to add several megs to their applications. Kowari's dependence on Java is another possible sticking point for those developing tools using other frameworks. Documentation is brief and unfinished, but what's there is useful for the adventurous."

Updated documentation is going to be released to coincide with 1.0.4. Hopefully, this should make it a little more accessible to most.

"According to Tom Adams, "Our triplestore is really a quad store, the 4th tuple being the group/model that a triple belongs to.""

Apparently, I made this quote but it doesn't matter.

Paul said, "a better name might be "platypus"" - that was already taken by a previous project.

Thursday, June 24, 2004

Semantic Clarity

Two related pieces dealing with integration and the Semantic Web.

Triple-based Computing "[Johanson & Fox, 2004] expect ubiquitous computing as the “killer app” for tuplespace-based computing because of the model’s portability, extensibility, flexibility, and ability to deal with heterogeneous environments...Since applications are decoupled in reference, time, and space many issues in protocol and process alignment disappear because they are provided by the underlying middleware that implements the tuplespace."

Semantic Web bringing clarity to the Universal Server concept "I would also like to conclude that what we know today, as the monolithic "point of presence" on the web called a "Web Site" (which infers browsing and page serving), is naturally going to morph into a different kind of "point of presence" that is capable of delivering the following from a single process:

1. Serve up Semantic Data from existing data sources
2. Provide execution endpoints for Web Services
3. Provide an instigation point for events that trigger Service Orchestratio

This is what Virtuoso is all about, and why it is described as a "Universal Server"; a server instance that speaks many protocols, delivering a plethora of functionality (Database, Web Services Platform, Orchestration Engine, and more)."

Wednesday, June 23, 2004

D2RQ

D2RQ - Treating Non-RDF Databases as Virtual RDF Graphs "Using D2RQ you can:
* access information in a non-RDF database using the Jena model API.
* query a non-RDF database using RDQL or find(spo).
* do RDFS and OWL inferencing over the content of a non-RDF database using the Jena ontology API.
* publish the content of a non-RDF database on the Semantic Web using the Joseki RDF server."

D2R is already integrated into TKS 2.0 and hopefully we'll get D2RQ in there. Good to see it using RDF for configuration.

Tuesday, June 22, 2004

News Services go RDF

Adobe and IPTC Collaborate on the Implementation of Metadata Standards for News Organizations " Adobe Systems Incorporated (Nasdaq:ADBE) today announced that it is collaborating with the International Press Telecommunications Council (IPTC) to extend the capabilities of IPTC metadata through use of the open-standard, Adobe XMP (Extensible Metadata Platform). Based on World Wide Web Consortium (W3C) standards, XMP is a specification expressed in XML that provides a standardized framework to capture and manage metadata, the information that describes files.

Photographers and news services around the world use IPTC metadata schemas to embed identifying characteristics such as captions, credits, location and time and dates within digital photos and scans. This information can be read by content management systems, used by virtually every newspaper publisher, to review and identify photos they want to publish to accompany a story. Adobe and IPTC also announced plans to develop future implementations that will be accessible via the Adobe(R) Creative Suite, and related point products including Photoshop(R) CS, through a customizable metadata user interface. This is intended to streamline the data capture process and allow relevant IPTC metadata to be preserved as the file is utilized across news and derivative workflows. "

Eve of Sleepycat

Apache Leader: Berkeley DB Java Edition Eases Hand-Rolling "In the case of the Apache Directory Project, Karasulu says the project members are so convinced that Sleepycat's pure-Java database will become the "de facto standard Java API for manipulating B-tree databases" that they're basing the project's pure-Java LDAP directory server, called Eve, on back-ends built using Berkeley DB Java Edition."

"Who's building applications in Java? Does it span the spectrum?

I think so. People can use a B-tree anywhere a fast, relatively constant time lookup is needed, regardless of the size of the data. This happens all over the place.

We're actually in the process of building an embeddable, pure-Java LDAP server called Eve. She's a beaut, introducing triggers and stored procedures to the world of LDAP. "

" What do you think of Berkeley DB Java Edition's performance capabilities?

It uses NIO [new input/output], which should have a considerable effect on performance due to the way memory is accessed. The NIO packages are new APIs that allow Java to have the power of C where IO is concerned. These APIs are new in the 1.4 JDK and make Java-based servers much more effective. Furthermore, a binding API makes mapping objects to records very intuitive while avoiding the overheads in serialization.

Other implementations often leave this up to users, who often use serialization and wind up paying for it with a massive performance hit. "

There was also a recent comparison between C++ and Java showing Java is faster in all but three tests.

The Next Web - Web Services

The Third Web "Web services represent the third attempt to rebuild enterprise IT on the standards-based foundation conceived by Tim Berners-Lee. To realize that vision, vendors and IT pros must resist some familiar temptations and avoid some traditional mistakes...But it would be a sad repetition of past errors if IT vendors seized upon the success of Web services as their latest excuse for locking customers into product stacks—perversely building proprietary structures from standards-based components, for example, by devising proprietary XML schemas for their applications and documents."

Scaling Taxonomies

Verity Announces New Content Classifier (with screenshot) "VCC is based on roles and rules. Roles include taxonomy experts, subject matter experts within the organization (e.g., chemists, engineers, human resources staff, etc.), editors, and publishers. The company says the workflow feature allows taxonomy and classification management to be distributed to subject matter experts who know the content, as well as to knowledge engineers who know and understand taxonomy development. Different people who serve different roles are assigned different permissions to alter categories. The company claims that VCC is the only software that enables such real-time collaboration between knowledge workers and subject experts.

VCC uses rules to define how documents should be classified. Once taxonomies have been set up, VCC automatically classifies new documents as spiders discover them. The customer can control automatic classification by defining how well VCC thinks a document matches a category. For instance, if VCC’s confidence level for a candidate category exceeds 70 percent, then automatically publish it into that category; if not, route the decision to an assigned knowledge worker. Verity calls this “automated classification with manual oversight.”

Verity worked with DuPont to develop VCC. Whitney said the company uses VCC to manage a 25,000 node taxonomy. Internal users include “everyone from a bench chemist to a knowledge engineer—whoever.” He said VCC provides DuPont with “frictionless review between highly specialized knowledge workers, many with PhDs, and the knowledge engineering staff.”"

Monday, June 21, 2004

Semantic Web for 5th Graders

This was an interesting find using the Google Catalog to search for the Semantic Web.

It says: "Twenty-two lessons show students how to build a vocabulary...(KWL, SQ3R, semantic web making, outlining)...". Of course, it doesn't look like it's *the* Semantic Web.

Searching for Java by itself reveals some interesting results. Searching for Java in the Computers category reveals no hits; the category function seems to be broken.

Thursday, June 17, 2004

Global Scalability

Semantic Web: Hype-Bubble or an interesting research area? Links to a comment made by on the SUO list "In 6 years (1998 to 2004) with ENORMOUS hype and funding, the semantic web has evolved from Tim BL's book to a few prototype applications, which are less advanced than technologies of the 1970s such as SQL, Prolog, and expert systems -- and they're doing it with XML, which is far less advanced than LISP, which was developed in the 1950s."

There are many interesting responses in the thread including one from Frederick Kintanar: "...I do think the Web makes a big difference between earlier knowledge representation efforts and Semantic Web initiative. A big one is global scalability, where the key element is URI's (and their already deployed global acceptance). Hypertext was already a relatively mature technology in the research community, when Tim Berners-Lee hit upon what is needed to make it scalable: global identification..."

And no this isn't scaling a single agreed upon ontology across the Web.

Spicy Searching

IBM expands search push with Masala "The computing giant, based in Armonk, N.Y., is gearing up to release Masala, a new version of its DB2 Information Integrator software that will let corporate employees retrieve information from databases, applications and the Web at the same time. Subsequent improvements will include a data-mining component code-named Criollo."

"Microsoft, though, isn't standing still. It is working on its own distributed search plan with Longhorn and a new release of its SQL Server database, code-named Yukon, and plans to build its own Internet search service. BEA Systems and others are working on similar technology."

"Information Integrator is a software layer than can pull data from different software--Oracle databases, Microsoft Excel, IBM's own DB2 and Lotus databases--with a single query. IBM and other companies are touting this "federated" database approach, in which searches tap into spread-out data sources, as a potentially cheaper alternative to shipping and storing large amounts of information in a single database."

Ruined by Developers

How Microsoft Lost the API War Most of this is standard "how the Web has won" but there were a couple of interesting snippets.

"WinFS, advertised as a way to make searching work by making the file system be a relational database, ignores the fact that the real way to make searching work is by making searching work. Don't make me type metadata for all my files that I can search using a query language. Just do me a favor and search the damned hard drive, quickly, for the string I typed, using full-text indexes and other technologies that were boring in 1973."

"RSS became fragmented with several different versions, inaccurate specs and lots of political fighting, and the attempt to clean everything up by creating yet another format called Atom has resulted in several different versions of RSS plus one version of Atom, inaccurate specs and lots of political fighting. When you try to unify two opposing forces by creating a third alternative, you just end up with three opposing forces. You haven't unified anything and you haven't really fixed anything."

Sunday, June 13, 2004

Loom and Drools

Loom is now open source (a BSD-like license). "Loom is a language and environment for constructing intelligent applications. The heart of Loom is a knowledge representation system that is used to provide deductive support for the declarative portion of the Loom language. Declarative knowledge in Loom consists of definitions, rules, facts, and default rules. A deductive engine called a classifier utilizes forward-chaining, semantic unification and object-oriented truth maintainance technologies in order to compile the declarative knowledge into a network designed to efficiently support on-line deductive query processing."

An article theServerSide.com introduces "...the JSR-94 Rules Engine API and an Open Source product called Drools, the forerunner implementation of this up-and-coming technology...it can scale to incorporate and execute hundreds of thousands of rules in a manner which is an order of magnitude more efficient then the next best algorithm." Drools Homepage.

WSDL2OWL-S 1.1 Released

WSDL2OWL-S "...provides a partial translation between WSDL and OWL-S. The results of this translation are a complete specification of the Grounding, partial specification of the Process Model and Profile and Daml Class file, when at least one of the input and output messages are of XSD Complex type." Download it here.

Friday, June 11, 2004

TKS the RDF Database

The Semantic Web in the Enterprise ""RDF provides a simple model to represent logical statements in the form of subject, predicate, object," said Daconta. "While this follows a linguistic approach, that same model can also represent resource, property, and value. This triple model is a powerful underpinning of more powerful languages layered on top of it like OWL."

He referenced one of his non-RDF projects that uses explicit database tables to make certain data associations. This approach is neither scalable nor flexible. The unique nature of RDF, however, can provide a flexible mechanism that would allow far greater associative capabilities, thereby increasing the ability to query and make inferences on topic matters not explicitly hard-wired into tables.

Daconta added that good strides have been made in commercial products supporting Semantic Web technologies, including RDF databases (such as Tucana Knowledge Server), ontology editors and inference engines (such as Network Inference's Cerebra Server), and data source integration engines (such as Unicorn System)."

The author is Ken Fromm from Loomia who are working on "a semantic technology software company building an RDF/FoaF-based identity and relationship stack".

Behind the Wall

Something Useful This Way Comes "Mike Champion offered an optimistic note, suggesting that Semantic Web technology may first flourish behind the enterprise firewall, in a way reminiscent of the earliest days of Netscape's corporate success:

The other previously missing ingredient is that real organizations have at least something approximating an implicit ontology in their database schema, standard operating procedures, official vocabularies, etc. It is at least arguable that the technologies that have emerged from the Semantic Web efforts allow all this diverse stuff to be pulled together in a useful way -- ontology editors, inferencing engines, semantic metadata repositories, etc. I'm seeing real success stories in my day job, and a coherent story is starting to be told by a number of vendors, analysts, etc.

Champion here makes a similar point to the one I argued in an article last fall ("Commercializing the Semantic Web"), namely, that there exist today several startups and fledgling ventures that are selling Semantic Web technologies to corporate clients, including Network Inference, Tucana Technologies, and others."

"Honestly, I don't know whether to laugh, because with WinFS Microsoft seems to be buying into the Semantic Web idea, or cry, because with WinFS Microsoft seems to be embracing-and-extending the Semantic Web idea. Oh well -- outside of the realm of unenforced US antitrust legislation, Microsoft is like gravity. Eventually, you just learn to work around it."

Thursday, June 10, 2004

Semantic Web Tutorial

Tutorial on basic SW Technologies Nice to get mentioned in the same breath as Sesame, Redland, etc. (not quite with Jena which got two of its own slides). Links also included: graphical editors and the Semantic Web Application Survey

WinFS and RDF to Square Off?

Questions about Longhorn, part 2: WinFS and semantics "Today's personal information systems are organized hierarchically. WinFS proposes that they be organized semantically. A number of observers have noted a family resemblance between RDF (Resource Description Framework) "triples" and WinFS relationships. An RDF triple, in geek-speak, is a subject-predicate-object relation. Sets of RDF triples can be (and Semantic Web people say must be) used to represent and organize knowledge."

Where do you get Longhorn today? RDF and schemas for RDF are available now. Taking the both bottom up and top down schemas and deployed locally and globally. Last year I asked, Should the RDF model be integrated into the File System?, the answer still seems to be 'yes'.

Danny has a good summary of part 1 of this discussion.

Wednesday, June 09, 2004

Can't get enough of the Semantic Web?

The Special Interest Group on Semantic Web and Information Systems. The first bulletin (PDF) is 75 pages of Semantic Web goodness. Includes interviews with Jim Hendler and Amit Sheth, where the SIGSEMIS is positioned, and various papers on the Semantic Web. There's also related events, an industry column (about Semagix Freedom) and book reviews.

Tuesday, June 08, 2004

Cynical Development

A fresh look at the waterfall "Analysis -> Dream, Design -> Guess and Waffle...Support -> Duck and Deny"

Monday, June 07, 2004

Sesame Speed

The KIM Platform: Performance and Scale "The result: a repository of 15M explicit statements, describing 1.2M entities, is manageable with an indicative upload speed of 1300 statements/sec...The experiment was performed on a 2xOpteron 240 (1.4GHz) server with 6GB of RAM - a $3000-worth, brandless machine. 64-bit beta-versions for Amd64 of Windows 2003 Server and JDK 1.5.0 were used."

iTQL evaluated

iTQL evaluation We do support optional match through the ugly sub-query syntax but apart from that I think Kendell has it right. Aliases allow you to shorten URIs.

Sunday, June 06, 2004

Datalog and Inferencing

Implementing OWL Lite in rule-based systems and recursion-enabled relational DBs "The semantics of negation in stratified Datalog is not compatible with the semantics of negation in Description Logics...Alternative, more compatible semantics for negation in Datalog exist, namely well-founded semantics, that also relies on such a three-valued logics. However, this is not semantics available in SQL:1999 compliant databases. Well-founded semantics only regards the minimal model when computing negation, whereas Description Logics regard all possible models. Hence, they are also incompatible."

Two other related papers: Bubo - Implementing OWL in rule-based systems and Description Logic Programs: Combining Logic Programs with Description Logic.

This maps well to 3VL and the recursive predicate functions trans and walk.

Not Relational Enough

Two recent articles about XML and database technology. One of the FAQs about Kowari is in respect to relational databases. Taking the pedantic view, the two databases mentioned are not relational but SQL. I've previously posted links about XML management systems too.

In, XML, the New Database Heresy "One of the major benefits of using XML in relational databases is that it is a lot easier to deal with fluid schemas or data with sparse entries with XML. When the shape of the data tends to change or is not fixed the relational model is simply not designed to deal with this. Constantly changing your database schema is simply not feasible and there is no easy way to provide the extensibility of XML where one can say "after the X element, any element from any namespace can appear". How would one describe the capacity to store “any data” in a traditional relational database without resorting to an opaque blob?

I do tend to agree that some people are going overboard and trying to model their data hierarchically instead of relationally which experience has thought us is a bad idea."

Edd Dumbill wrote in, Ron Bourret on XML and databases "My guess is that everything will pick up on this front in a year or two, with companies moving towards what I consider the holy grail of XML support in relational databases: native storage behind a first-class XML data type, XQuery support with extensions for (a) including relational data or SQL queries and (b) updates, SQL/XML support with extensions for embedded XQuery queries, and support for JSR 225 (see below)."

One of the aspects we've found in implementing TKS/Kowari was that it pays to stick closely to the relational model. Everything comes down to tuples and I think that the problems with putting RDF on top of SQL database is that they aren't relational or "relational enough" (whatever that means).

Actually, the DAWG is asking for comments, maybe ensuring that the queries are expressed in relational algebra. That should prevent things like NULL getting in there.

Why FOAF? Why XFN?

This is a fairly old blog entry (4 months) but I hadn't seen it before, it discusses another social software format, XFN.

Social software snippets "So Jonas poses a good question, why was FOAF invented? Perhaps an attempt to justify RDF? Is this an example of a solution looking for a problem? A clever acronym looking for a reason to exist?

Speaking of which, the biggest irony I see about FOAF is its name, which stands for "Friend of a Friend", and yet the technology has nothing to do with "friends". Like Jonas said, it's simply vCard recast in RDF, except for the "knows" relationship, which itself is quite meaningless (quite ironic for a Semantic Web effort), as it provides no more meaning than a plain hyperlink. Why work so hard for so little?

FOAF could be saved however, simply by adding an XFN module, thus enabling FOAF to finally fulfill its namesake, and represent friendship rather than just claiming to."

Friday, June 04, 2004

TCO of open source software

Weighing the costs of open source "While MySQL passed performance tests, the IT staff at the credit card processing company became concerned that MySQL didn't have enough formal support backing it up. What if the credit card processing company's databases failed, asked Tim Kelly, who serves as technical director of technology at TSYS.

"We were not prepared to deal with new support contracts and rely on an alternative database with our customer data." Tim Kelly director of technology, TSYS

"We have a procedure on how to roll back transactions when something goes wrong, but in the event that everything you try doesn't work and you look for support, there area million comments out there on the Web -- and newsgroup articles on MySQL -- but in production scenarios, you can't really rely on that," Kelly said.

Figuring out the total cost of ownership for a DBMS can be more complex than many companies expect at the outset, said Mike Schiff, vice president of data warehousing and business intelligence at Sterling, Va.-based Current Analysis.

"The cost of ownership isn't just the cost of acquisition or maintenance; it's also the vendor responsiveness when you've got a critical issue and downtime," Schiff said. "The cost of dollars to a company that has a database down can be staggering.""

Thursday, June 03, 2004

RDF Data Access Use Cases and Requirements

No keeping your bananas unbruised but some pretty important use cases:
* 2.2 Finding Information about Motorcycle Parts (Supply Chain Management)
* 2.5 Avoiding Traffic Jams (Transportation)

More seriously, they don't mention beep but I would assume that the "web" in Semantic Web will mean the protocol will be http. Aggregate queries (4.5) might mean getting a FROM clause, or something like it, in the language.

http://www.w3.org/TR/rdf-dawg-uc/

Sunday, May 30, 2004

The Semantic Web is your Friend, FOAF that is

The Semantic Web is Your Friend "...given the proliferation of data about data (metadata) that underpins the Semantic Web, it is tempting to focus in on the obvious prospect of a better-than-Google search engine...As clever and useful as this may be, it is only an evolutionary enhancement of something that is already possible on the Web today. By looking in a little more detail at what is happening on the Semantic Web today, it is possible to gain a deeper insight into where revolution is starting to occur."

"Applications like FOAF are at the vanguard of the Semantic Web, enabling a glimpse of what might be achieved."

I'm sick of FOAF being held up as the vanguard of the Semantic Web...

A Few New Semantic Web Tools and Browsers

Many of these were presented at the WWW2004 conference:

* Ganesha will be available soon for download.
* Simile and Longwell (a faceted approach using Jena and HTML).
* Haystack the next version - based on SWT and Eclipse.
* SWOOP 2.0 (which changed from using Jena to the Machester OWL API).

Saturday, May 29, 2004

Ontographics

"Ontographics is another visualization of graphs structures. It's a "...organization and presentation software. It is suitable for managing all kind of information and data: documents, projects, knowledge, and so on. Ontographics makes it easy to present, share and communicate informations to other people."

"It is a fully functional program, but is missing some features from Ontograpics Silver:

* no attachments (Word documents, images, etc) on nodes
* no installer
* no support"

Screenshot.

Goodbye New York

Paul Ford mentioned Kowari/TKS/Tucana Technologies in his writeup: WWW2004 Semantic Web Roundup.

"Many of the Semantic Web projects discussed during the conference used Jena as a backing store, but one contender to Jena's throne is Kowari, from Tucana Technologies."

"Rather than competing directly with Jena, Kowari includes support for the Jena API, as well as JRDF, an alternative RDF-management API, and adds to these APIs with a new SQL-like query language, iTQL, that can be used via a built-in interactive shell."

The TKS/Kowari presentation can be downloaded here. At the Semantic Web Developers Day Kowari got mentioned during the "Harpers.org: a Semantic Web Case Study", Simile and MINDSWAP presentations.

We should continue to make it clear that Kowari is not really going to take Jena's throne. In the short and medium term I can only see us improve Jena support. The slated FastPath and improvements in ontology speed are both things we're looking at putting into Kowari soon.

JRDF's goal is to be an API more approriate to use for our underlying triple store. With Kowari, we needed a better abstraction of using RDF triples and throwing away everything and doing Jena would've taken too long. The Jena support is basically a mapping of Jena to JRDF (and back again).

It was great to meet a lot of people face to face. And I got a lot of interesting news about various people using or evaluating Kowari. I think it'll lead to some interesting news in the near future.

Wednesday, May 19, 2004

Semantics in P2P and Grids Notes

Not having looked deeply into this in the past except at the The Semantic Grid web site I came into the workshop without much context as to what the talks were going to be about.

The first talk was about using query expansion on a peer to peer network. It extended Limewire to allow different nodes to expand the keywords using something called Keyword Relationship Databases (KRDB). Weightings are graded based on how successful the data they return is.

The second speakers presentation was about using Small World Networks (SWN) as a way to scale P2P networks. You place the data and the nodes in a k-dimensional space. The problem then is that you have to keep the number of dimensions reasonable. The speaker gave an example of flattening a 2-dimensional space into a 1-dimensional space by basically turning it into a linked list.

Bibster was the topic of the third paper. This used a combination of SeRQL, Sesame and JXTA to implement a distributed bibliographic system. It also used similarities in the metadata to route queries and remove duplicates.

The next talk focused on creating truely distributed P2P databases. It appeared that they were using something that looked liked lattices to implement schema matching between peers. This was called "correspondence rules". There was also "coordination rules" which dictacted how queries were forwarded to peers. It also used JXTA. The main feedback seemed to be that the paper gave names to these problems and but didn't really solve them.

coDB was the next topic of discussion. Which seemed to be a way of doing First Order Logic (FOL) over P2P networks. I had a problem understanding the point of this one. For example, the paper mentioned that if peers that created the result drop out then the answers from that peer should be removed. The feedback from someone else was whether it was useful in an open network to do this. The example brought up, was marriage. He was saying a peer would make the inference that if one person in a marriage was male the other would be female. And that brought up the rather topical example of gay marriages. What one peer inferred maybe different for different reasons than another peer. This was a bit beyond the scope of the paper though it seemed like a valid criticism.

The sixth talk was done by a someone from HP. This was pretty much the highlight of the morning. Because it specifically talked about RDF and OWL and they used Jena (of course). The main thing to come out of it is that they wanted to be able to calculate properties ("virtual properties") expressable in RDF/OWL. For example, server price is a funtion of software and hardware price. They created a type of TransitiveProperty called FunctionalProperty. A functional property would define a function like "foo = x * y + z". How this would be defined in OWL hasn't been defined as far as I know. It sounds similar to aggregate functions like average, sum and count but are fully configurable. I vaguely remember someone at work talking about this. Obviously, a cool idea anyway.

The last three talks were about trust, GridDB and ebXML. They were fairly short but interesting. Probably the most interesting thing I got out of it was that OASIS (who are working on ebXML) are trying to be inclusive of current technologies like Topic Maps and RDF/OWL. In fact, the speaker did say that UML was going to be expressable in RDF/OWL. I also thought that GridDB looked a lot like our current TMex product.

Anyway, apart from that I'm really enjoying the conference. Google set up a booth to try and get people to work for them - little did they know I was only after their pen.

Thursday, May 13, 2004

Pure Abstraction

RDF as data abstraction "Mozilla's central interface for dealing with data is RDF. RDF datasources can have any implementation they like behind them. However, they must provide the information through the nsIRDFDataSource interface that specifies a graph API of nodes and edges. Once this is done, any client can operate with the datasource without reference to the domain objects, methods, or underlying implementation. You just need to know how to manipulate a graph, and you're set.

This is the true potential of RDF. It's not a substitute for databases or XML. RDF is a directed labelled graph. It hides information and provides a data interface which can be used to aggregate multiple datasources that can be themselves RDF datasources. This is the purest data abstraction. Theoretically, if you weren't worried about performance you could access an RDF datasource and not know or care whether you're accessing a database, a web service, or both. The RDF datasource might even optimize its data structures based on what your queries or iteration patterns have been, in much the same way as hotspot compilation optimizes algorithms in the JVM.

A good question at this point is whether RDF is as powerful an API as JDBC. The answer is yes, or not quite. RDF is only a data structure, and there are several APIs for manipulating that data structure. The most well known implementation is Jena. Jena's API for manipulating RDF graphs is very powerful, and encompasses most things you would find in JDBC, such as transactions, a query language, and prepared statements."

The Blank Node Release

Kowari 1.0.3 is now available for download. Loading RDF/XML with blank nodes is now faster, inserting statements with blank nodes now works correctly, and blank nodes in Jena are now properly mapped. There are other things. It's annoying that RDF has named things (about) and unnamed things (blank nodes) and locally named things (blank nodes with node IDs). iTQL adds variables which are differently labelled blank nodes too.

The next release should have some inferencing and resolver work done to it which will be a major change to the architecture - unless we find some critical bug.

Paul has also updated the plans for a new triple store for Kowari/JRDF. I'm favouring the second approach but they both have positives and negatives. The ring structure has some advantages over the current structure (and the first approach) as it greatly reduces the amount of disk usage. I think bloom filters have been put on the back burner.

Wednesday, May 12, 2004

Rewerse

Reasoning on the Web with Rules and Semantics "The objective of REWERSE is to establish Europe as a leader in reasoning languages for the Web by

1. networking and structuring a scientific community that needs it, and by
2. providing tangible technological bases that do not exist today for an industrial software development of advanced Web systems and applications."

Tuesday, May 11, 2004

Bloom Filter Implementation

Based on the bloom filters post a while back it looks like Paul and DM will be doing one - hopefully with a JRDF interface.

I'll have to get JRDF up to scratch. Some recent comments from both Paul and others make me acutely aware that it's definitely not even close to being the last word in Java RDF APIs.

Danny Hillis on the Knowledge Web

"ARISTOTLE" (THE KNOWLEDGE WEB) ""I am interested in the step beyond that," he says, "where what is going on is not just a passive document, but an active computation, where people are using the Net to think of new things that they couldn't think of as individuals, where the Net thinks of new things that the individuals on the Net couldn't think of."

"In the long run, the Internet will arrive at a much richer infrastructure, in which ideas can potentially evolve outside of human minds. You can imagine something happening on the Internet along evolutionary lines, as in the simulations I run on my parallel computers. It already happens in trivial ways, with viruses, but that's just the beginning. I can imagine nontrivial forms of organization evolving on the Internet. Ideas could evolve on the Internet that are much too complicated to hold in any human mind.""

"In this regard, thanks to funding from the Markle Foundation, Danny been able to assemble a group of people to begin to discuss of the implementation of a medical application based on his ideas."

Medical application, hasn't this been done before? Only Jaron Lenier mentions the Semantic Web.

Euroweb

Europe spins the semantic web "A number of exciting new semantic web projects have been recently launched as part of Europe’s latest framework research programme. These projects are being showcased in the 1st European Semantic Web Symposium (ESWS 2004) on 10-12 May in Heraklion (http://www.esws2004.org/ )."

Securing the Semantic Web

Following a question on rdf-interest there's been two interesting links with regard of a vocabulary for describing user permissions:
* This document describes the ACL storage and query mechanisms used by W3C, as well as the availability and use of this data on the semantic web.
* Semantic Web Trust and Security Resource Guide and more specifically KAoS Policy and Domain Services:Toward a Description-Logic Approach to PolicyRepresentation, Deconfliction, and Enforcement.

Monday, May 10, 2004

kSpaces.net

kSpaces "...is a metadata-driven, distributed knowledge management platform. It was designed to be lightweight, transparent and extensible...kSpaces automatically tags files through the use of plugins. The two autotagging plugins that are included analyze a file's ID3 and EXIF headers, and then generate the appropriate RDF metadata.

Metadata associated with a file can be viewed and edited through the kSpaces Node application, supported by editor plugins. Five editor plugins have been included in the proof-of-concept, four of which are read only. These plugins allow the management of a subset of Dublin Core metadata, EXIF metadata, ID3 metadata and kSpaces-specific metadata. The Raw RDF plugin shows the raw RDF metadata associated with a knowledge asset."

Cool, an extensible metadata extrator.

Saturday, May 08, 2004

Broken Windows

Something that I've been pushing with Kowari recently.

Don't Live with Broken Windows "You don't want to let technical debt get out of hand. You want to stop the small problems before they grow into big problems. Mayor Guiliani used this approach very successfully in New York City. By being very tough on minor quality of life infractions like jaywalking, graffiti, pan handling—crimes you wouldn't think mattered—he cut the major crime rates of murder, burglary, and robbery by about half over four or five years.

In the realm of psychology, this actually works. If you do something to keep on top of the small problems, they don't grow and become big problems. They don't inflict collateral damage. Bad code can cause a tremendous amount of collateral damage unrelated to its own function. It will start hurting other things in the system, if you're not on top of it. So you don't want to allow broken windows on your project.

As soon as something is broken—whether it is a bug in the code, a problem with your process, a bad requirement, bad documentation—something you know is just wrong, you really have to stop and address it right then and there. Just fix it. And if you just can't fix it, put up police tape around it. Nail plywood over it. Make sure everybody knows it is broken, that they shouldn't trust it, shouldn't go near it. It is as important to show you are on top of the situation as it is to actually fix the problem. As soon as something is broken and not fixed, it starts spreading a malaise across the team. "Well, that's broken. Oh I just broke that. Oh well." "

Thursday, May 06, 2004

Eh

I'm really impressed by Paul's blow by blow report on our inferencing work (he also mentions Lawrence Lessig on Australian radio). We're only doing RDFS at the moment. We'll being doing at least owl tiny, we're still deciding. Without Sesame or Jena some of these architectural decisions would have been much harder. I think we've got the right mix of new ideas based upon work that's been done before.

Edd Dumbill won't be attending WWW2004 and that's a shame. Especially because I'm going to be there - hopefully to put faces to names. I think the developer's day looks good - "Doug Cutting, the leader of the Nutch open-source search engine project, and an interactive luncheon Q&A with Tim Berners-Lee." TKS will be there too. TKS is Kowari with other features such as security, related to queries, support and GUI management.

Sunday, May 02, 2004

Kowari linkers

Knowing what people are thinking is important in improving the product. With that in mind I did a quick Google for people mentioning Kowari. I'll use it here to correct anything too.

DeliverableS4Simile "Naive use of persistent store in Jena decreases performance by 100x:
* Part of the problem is limited expressivity in RDQL
* Look at performance tuning on databases
* Ryan: Look at the performance of more specialized RDF databases, cf. Kowari"

Open Source Projects That Use Java NIO "The storage engine of Kowari is a transactional triplestore known as the XA Triplestore. ll relevant fields of in-memory and on-disk data structures are 64 bits wide..."

Kowari for hundreds of millions of triples "Jim Hendler emailed me in response to my having mentioned on www-rdf-interest@w3c.org that I was surveying triple stores for use in data mining and machine learning. He mentioned a Java-based, non-relational, triple store called Kowari that is available in open source form..."

RDQLPlus "I discovered Kowari last week. The iTQL language is very similar to what I've come up with for RDQLPlus... having equally been inspired by SQL/DDL. Kowari looks like a nice database. I've downloaded it but haven't had a chance to play with it yet..."

Some Tools "Kowari is a layer on top of Jena with OWL reasoning, too"

I would say that Kowari is a layer beneath Jena - one that provides persistance. The OWL reasoning is really only offered at the moment through Jena. However, we will be getting some basic inferencing, at our own query layer, in there soon too.

[protege-discussion] Re: large data sets, bulk data acquisition "I had a really bad time with Kowari earlier this year, it wouldn't compile and then pass its own self-tests...."

This is basically problems with Windows. We develop on Linux and OS X and only do QA on Windows. Our initial release had known problems under Windows - which lead to failing unit tests but was not fatal for data storage. Anyway, it is fixed now; although Windows does have some drawbacks when it comes to using NIO.

Ontological Software Development

Semantic Mapping, Ontologies, and XML Standards ""Within an ontological framework, integration analysis naturally leads to generalization."

Considering that statement, it's also clear that application independence of ontological models makes these applications candidates for reference models. We do this by stripping the applications of the semantic divergences that were introduced to satisfy their requirements, thus creating a common application integration foundation for use as the basis for an application integration project."

"Once we define the ontologies, we must account for the semantic mismatches that occur during translations between the various terminologies. Therefore, we have the need for mapping.

Creating maps is significant work that leverages a great deal of reuse. The use of mapping requires the "ontology engineer" to modify and reuse mapping. Such mapping necessitates a mediator system that can interpret the mappings in order to translate between the different ontologies that exist in the problem domain. It is also logical to include a library of mapping and conversion functions, as there are many standards transformations employable from mapping to mapping."

Friday, April 30, 2004

Limiting Complexity

The Psychology of Ontology Harmonization "My personal experience seems to suggest the exact opposite: higher the abstraction, lower the objectivity with which people can argue and, therefore, come to an agreement.

I've spoken to people that spent several years of their lives coming up with an ontology and their perception is that the complexity over time of these models to cover a particular domain saturates, does not continue to grow.

This is a basic, but vital assumption for this entire approach to work: if the ontologies grow linearely with the amount of information they can describe, the ontology creation/maintainance process simply won't scale globally."

Intellidimension's SWS

Semantic Web Search "Semantic Web Search is a search engine for the Semantic Web. Our site can be used by both people and computers to precisely locate and gather information published on the Semantic Web."

From the FAQ:
"...using our standard search engine interface you can just type a one or more of keywords describing the information you are trying to locate. This is no more complicated than a traditional Web search engine. However like a traditional Web search engine this can lead to a large number of irrelevant results. To narrow your search you can restrict it to the specific type of resource that you are trying to locate such as a person (FOAF Person) or news article (RSS Item). If your search is still producing a large number of irrelevant results than you can refine it further by specifying one or more specific property values that the resource must have."

Browse the Semantic Web

How to Make a Semantic Web Browser "Two important architectural choices underlie the success of the Web: numerous, independently operated servers speak a common protocol, and a single type of client—the Web browser—provides point-and-click access to the content and services on these decentralized servers. However, because HTML marries content and presentation into a single representation, end users are often stuck with inappropriate choices made by the Web site designer of how to work with and view the content. RDF metadata on the Semantic Web does not have this limitation: users can access the underlying information and control how it is presented for themselves. This principle forms the basis for our Semantic Web browser—an end-user application that automatically locates metadata and assembles point-and-click interfaces from a combination of relevant information, ontological specifications, and presentation knowledge, all described in RDF and retrieved dynamically from the Semantic Web."

Some thoughts on RDF rendering had some ideas on visualizing the Semantic Web too.

The Passion of RDF

"SemanticBible is ...an emerging exploration of new applications of markup and computational linguistic technology to the study of Scripture, with an emphasis on practical tools that encourage understanding and personal transformation."

See also: The Vision of a Semantic New Testament: "Just as important as avoiding commercial barriers to sharing is the requirement that SemANT support existing and emerging standards that enable use across the Internet. To this end, SemANT will build on the Semantic Web Activity of the World Wide Web Consortium (W3C), including XML as a syntactic standard for data interchange, and RDF for ontology-based representation, and DAML/OWL for additional semantic expressiveness.".

Another example of when your technology has matured like: PCs, CDROMs, Hypertext, the Web, etc.

XUL vs XAML

Mozilla, Gnome mull united front against Longhorn "So far, XUL has failed to catch on, and Microsoft questioned whether Mozilla's technology would do much to help Gnome ward off Longhorn's promised threat.

XAML, Microsoft warned, is more potent than XUL in its ability to reflect exactly what's in the operating system.

"XUL is not the multipurpose declarative language that Gnome probably wants," said Ed Kaim, product manager for the Windows developer platform. "People say that when all you've got is a hammer, everything looks like a nail. In the same way, people are trying to figure out how to crush XUL into an OS it really wasn't designed for. The browser is great for a lot of things, but when it comes to robust client side applications, it's not the best."

Another trick will be in reconciling XUL with Gnome's existing user interface technology.

"There are ways to marry them," said Bruce Perens, an open-source consultant who serves as executive director of the Desktop Linux Consortium, a marketing organization. "But it's very difficult to get the two teams working in the same direction. They both went on a several-year tour of technical creation where they sat down and created everything they needed to do GUI [graphical user interface] applications — and they didn't create the same thing. Now to get them together it would take some number of years to resolve the technical diversions.""

Query Use Cases

Query Languages Report "A report by AIFB and Sesame and Jeen Broekstra from the Sesame crew. The Authors know what they are talking about as they are SemWeb developers themselves.

Although a little self advertisement and some missing languages, its a good thing to read. If you need info about RDF Query languages, read it.

My previous demand about "optional joins in queries" is answered by SeRQL."

The report is an excellent example of the current features required from a query language. From what I can tell iTQL implements 11 of the 14. Some of the others are fairly trival to add support for (like the data type support).

Wednesday, April 28, 2004

Will the Semantic Web Scale?

Apparently, there's going to be a debate at WWW2004 about whether the Semantic Web will scale: "However, with only a few exceptions we noticed that current research and development is focusing on creating new technologies for facilitating the Semantic Web. Available technologies from other disciplines such as databases are rarely reused and adapted. Hence, most Semantic Web systems do not scale to Web-size problems.

Lately, several researchers doubted whether the Semantic Web idea will ever scale for numerous reasons technological [But03], theoretical [van02] and practical [MS03,Sow]. Dedicated workshops on that topic [CKDE03,VDC03] have been organized recently to promote research to improve scalability. We will pick up these three categories of doubt by organizing the panel in three parts discussing each aspect: theory, technology/implementation, and practise."

I'm not sure I agree, there are very few Semantic Web systems that don't reuse existing SQL databases - they just suck at storing triples. With Kowari, and I'm sure with other native stores, the data structures and techniques used are taken directly from databases. They mention "Is the semantic web hype?" (which I responded to) and a few others. Although, there's no links to syllogism, metacrap or gnomes. BTW, I'm still not sure why you'd want an XML version of OWL.

"Network round-trips are often considerably less costly than the time taken for a transactional database operation due to the need to forcibly log transactional operations which is very costly in terms of disk performance. i.e. network round-trips aren't always the performance bottleneck." From Martin Fowler's First Law of Distribution.

As long as you keep the Semantic Web like the Web there's no real reason why it shouldn't scale.

Google Watching

What can't you find on Google? Vital statistics "Google is famous for being a confident, open company. Its clean, uncluttered search page is supposed to be a metaphor for the organisation behind it. But when you start asking questions about its technology, then the water rapidly becomes murky...One university presentation, for example, claimed that Google handled 150 million queries a day, and 1,000 per second at peak times...If the system is handling a peak load of 1,000 queries per second, he reasoned, that translates to a peak rate of 86.4 million queries per day - or perhaps 40 million queries per day...They also claim to have '4+ petabytes' of disk storage, and have let slip that each server is fitted with two 80 gigabyte hard drives. Now a petabyte is 10 to the power of 15 bytes, so if Google had only 10,000 servers, that would come to 400 Gb per server. So again the numbers don't add up."

Google Goes Public? The Rich Get Richer "People speculate. People dream. And if the numbers are to be believed, people will drool. The current prediction is that Google, if it decides to sell shares to investors this year, would probably end up with a market value of $20 billion to $25 billion by the end of its first day as a publicly traded company."

Google's Brin Talks on Gmail Future "It was interesting to me that you did finally hit on the word conversation. It seems to me that there's a synergy between the elements of the conversation in the RSS space and what you're doing in the e-mail space.

I think that's very true. Part of the things we've seen why blogs and RSS feeds are such a success is that you can actually read it—you don't have to stop, click back and forth, collect bits and pieces here and there—but it is all presented to you as one. "

Mozilla to Upgrade RDF

RDF module owner "With Benjamin Smedberg, Chase Tingley and Ben Goodger as peers, I took over the module ownership on RDF. We gonna push for both standards conformance (there are new specs out there since early 2004) and scriptability for remote web applications. This will include some serious whacking of the RDF API in Mozilla, as that is not ready for the web by a fair amount."

Tuesday, April 27, 2004

Ant is now more useful

ANT's finally a real build tool "And I can finaly call ANT a real build tool (and Maven can go play in its own cacca for all I care).

In a nutshell, the task lets you reference other build files. This means that you can create common centralized libraries of build files that other people can use on their own projects - all without copy and paste. And believe it or not, the semantics all make sense too. You can provide default tasks and properties, and the importer can override tasks and properties to customize behaviors on a case by case basis if it's required. The end result is that individual project build files are smaller and easier to understand, and common behavior can be achieved across an entire large system in a natural and non-cut-n-pasty manner (I don't know about you, but I always found pasties rather unnatural)."

Also new is macrodef: "Macrodef is a way to define a new Ant task in an Ant build itself. Macrodef allows you to define standard tasks that have attributes and elements given to them when they are called."

Paul's Blog

Paul is a guy that sits next to me at work and now is putting his development notes on a blog. So if you're interested in the inner-workings of Kowari take a look. I'll let people guess who DM, AM, and RMI are. :-)

Friday, April 23, 2004

Free Bits of Description Logic

DESCRIPTION LOGICS Includes a bunch of Postscript and PDF files (including the first couple of chapters of the DL Handbook).