Friday, April 01, 2005

Uniqueness and an Open World

Unique Name Assumption "He cites an OWL Flight paper that caused me quite some headache a few weeks ago (cause there was so little in it that I found to like)...There was an OWL requirement that gives a short rationale for the UNA, but it seems it is not yet stated obvious enough."

The main problem was that the expression of this did not seem to be sufficiently addressed - especially as it is such a basic concept and that there wasn't a simple concrete example (unlike the Cain/Kain and Able one given).

The initial problem was cardinality and OWL Flight attempts to solve the problem with cardinality. Paul put it succinctly: "So what is the point of statements with the owl:minCardinality predicate? They can't ever be false, so they don't tell you anything! It's kind of like a belt and braces when your belt is unbreakable."

"OWL-Flight and proponents of UNA actually forgot that it's a Semantic Web, not just a Semantic Knowledge Base. If you want UNA, take your Prolog-engine. The Semantic Web is more. And therefore it has to meet some requirements, and UNA is an astonishingly basic requirement of the Semantic Web. Don't forget, you can create local unique names if needed. But the other way would be much harder."

The statement of the problem and a solution seems to be better explained elsewhere and I did comment that the resolution, local unique names using AllDifferent, didn't actually seem to solve the problem well enough (without consideration for scalability for example). I have a feeling that context is a better solution to this problem (that might just be my golden hammer though).

"Still, Andrews arguments lead to a very important question: taking for granted that Andrew is an intelligent guy with quite some experience with this kind of stuff, how probable is it, that Joe Random User will have really big problems with grasping such concepts as non-UNA? How should the primers be written? How should the tools work in order to help users deal with this stuff - without requiring the user to study these ideas in advance?

Still a long way to go."

I would agree - this was my main problem - how do you explain to Joe (and Andrew) that all his CDs are the same rather than different. In Joe's experience things are usually different until you start comparing them and then he finds similarities (or like Ernie putting away toys). This is a good example of why the Semantic Web is not AI - it's not trying to emulate the way people think.

Thursday, March 31, 2005

You are the Same, Just Like Everybody Else

Two follow-ups from today's post:
* OWL Cardinality "If minimum cardinality means nothing in an open world, then there was very little point in including it in the OWL language. Whoever did so probably forgot about the open world assumption at the time. I can't blame them, as I find it very easy to forget. So I think I should assume that the intent was for this to operate in a closed world assumption. Similarly, I have to assume the same about the intent of maximum cardinality."

* An inconsistency or not? "As you can see from the above sentences, Harry is a Person.
And, by r1, Harry can have exactly one value for hasFather property.
But, it is asserted that Harry has two different
values, John & Johnny, for hasFather property.

I can't decide which of the following is true.

A. John and Johnny are actually the same individual.
B. The above sequence of sentences are inconsistent."

Why Different Things are the Same

I was reading what I think is a good introductory book, "A Semantic Web Primer" at the same time reading "OWL and Cardinality".

In the Primer book it states: "...the non-unique-names assumption is the most plausible one to make on the World Wide Web..." Which I didn't think made sense.

In Cardinality: "The difficulty in checking this for consistency is that an <owl:sameAs> statement can make it all valid:
<ns:firstPropertyObject> <owl:sameAs> <ns:secondPropertyObject>" Which did make sense.

The thing that eventually struck me was that the assumption Paul makes, and I have made, is something very common - names are unique. However, this is not the case in OWL: "Just because two names are different does not mean they refer to different individuals."

So using cardinality restrictions, systems can infer that if you have two values for a property when the ontology defines you should have one, it's not that you've broken cardinality, it's that those values are actually the same/equal. In Paul's example sameAs isn't required - firstPropertyOne and firstPropertyTwo are the same. This seems weird, completely backwards and very non-intuitive.

Looking around I found Pellet: An OWL DL Reasoner which says: "In general, a Semantic Web reasoner should handle individuals (provide ABox reasoning), should not make the Unique Name Assumption..."

It doesn't really say, though, why you need non-unique names. It does seem perverse that the basis for this, the URI, is unique.

In fact, the opposite case seems to be well stated in "OWL Flight vs. OWL DL": "We argue that very few equalities can actually be resolved with reasoning and that many derived equalities are actually faulty. Thus, it makes more sense in our opinion to either resolve equalities beyond the logical language or to make strong assumptions on the available knowledge, i.e. assume that each identifier in the knowledge base uniquely identifies an individual..."

It was resolved as an issue by the Web Ontology group by having to use AllDifferent. Where a collection is used hold all your distinct items. This seems like a decision to make the usual case more difficult and less scalable.

Saturday, March 12, 2005

Making Money from the Long Tail

The long tail of software. Millions of Markets of Dozens. "You know the real reason Excite went out of business? We couldn’t figure out how to make money from 97% of our traffic. We couldn’t figure out how to make money from the long tail – from those queries asked only once a day."

"57% of Amazon’s sales come from books you can’t even buy at a Barnes and Noble (to be fair, there is some skepticism around this number voiced here). This runs totally counter to the traditional 80/20 rule in retailing – that 80% of your sales come from 20% of your inventory. In Amazon’s case, 57% of their book revenue comes from 0% of Barnes and Nobles inventory."

"iTunes has over one million songs in it’s catalog. You know how many have been bought at least once?

Every one."

Promising Project

A scalable environment for the Semantic Web "Taking a bottom-up approach to the development of the Semantic Web, a scalable and modular Knowledge Management system has been successfully validated on two university websites.

Created by the IST program funded project MOSES, which ends this month, it enhances the possibilities for ‘knowledge mining’ by providing users with a natural-language query interface that offers direct responses to specific questions. Most significantly, the MOSES system creates a modular and scalable environment allowing content to be automatically updated, while interlinking ontologies from different academic websites in different languages.

“The biggest achievement I think was being able to combine different ontologies from different websites into a single application,” explains project coordinator Alfredo Ricchi at Finsa Consulting in Italy. “The system has had some encouraging results.”"

Mentioned as part of Grid Start.

Example OWL Ontologies and Cooking for the Semantic Web
OWL and Topic Map Pudding
.

Wednesday, March 09, 2005

Bunch of Links

* Too Darned Big to Test - Make it smaller.
* XForms Editor in OpenOffice.org and A First Look at OpenOffice.org 2.0.
* Why REST is Better - Part 3 - Links to Push and Pull Message Delivery in the PSB Architecture.
* Open Source Profilers for Java. Also mentions the free but not open source JFuild.

Using the Semantic Web to Handle Petascale Datasets

Scientific Data Management in the Coming Decade "Increasingly, the datasets are so large, and the application programs are so complex, that it is much more economical to move the end-user’s programs to the data and only communicate questions and answers rather than moving the source data and its applications to the user‘s local system."

"If the data is to be analyzed by generic tools, the tools need to “understand” the data. You cannot just present a bundle-of-bytes to a tool and expect the tool to intuit where the data values are and what they mean. The tool will want to know the metadata."

"In addition to standardization, computer-usable ontologies will help build the Semantic Web: applications will be semantically compatible beyond the mere syntactic compatibility that current-generation of Web services offer with type matching interfaces. However, it will take some time before high-performance general-purpose ontology engines will be available and integrated with data analysis tools...The XML integration in modern Database Management Systems (DBMS) opens the door for existing standards like RDF and OWL."

This would be something that I would disagree with - existing DBMS are not flexible enough to handle things like RDF. And OWL is even more crucially effected where you need the indexing available from something like Kowari. Other systems like Sesame and Jena are both adding tree structures to store their RDF. Some of that is maintenance and setup but also performance.

"As file systems grow to petabyte-scale archives with billions of files, the science community must create a synthesis of database systems and file systems. At a minimum, the file hierarchy will be replaced with a database that catalogs the attributes and lineage of each file. Set-oriented file processing will make file names increasingly irrelevant – analysis will be applied to “all data with these attributes” rather than working on a list of file/directory names or name patterns."

This is very similar to the TMex V2 architecture that I worked on.

Also Distributed Computing Economics "Computing economics are changing. Today there is rough price parity between (1) one database access, (2) ten bytes of network traffic, (3) 100,000 instructions, (4) 10 bytes of disk storage, and (5) a megabyte of disk bandwidth.".

Via Peta-scale Data Centers - a Trio of Great Jim Gray Papers (from: Kevin Schofield’s Weblog).

Tuesday, March 08, 2005

Watching the Watchers

Test your tests with Jester "Any statements that are not executed at least once are not being tested.

This approach, taken by tools like Clover and EMMA (see Resources), is valuable for finding untested statements -- but it's not enough. Knowing that a statement isn't executed by the test suite proves that it isn't being tested. However, the inverse is not true. If a line of code is executed, it doesn't necessarily follow that it's tested. It's entirely possible that the test doesn't check whether the line of code produces the correct result."

"Because Jester recompiles the code base and reruns the test suite for each change it makes, it runs orders of magnitude more slowly than more traditional tools like Clover. It's therefore important to pay some attention to performance. You can use a number of techniques to speed up Jester runs."

A list of useful OS tools from Thoughtworks (who have contributed to Jester) is: ThoughtWorks Open Source Java.

Kowari Changes since Pre-Release 2

Here's what's been committed so far (further updates will be put here):
* Transaction Timeout configurable. SR
* Client JRDF modifications - client side API now handles blank nodes, currently memory bound. AN
* KModel modifications - modified with changes to client JRDF and added RMI versions of API. Have to finish blank node client side changes. AN
* MP3 Content handler - changed to use different library. AN
* JRDF's RDF/XML parser (based on RIO) passes all tests. AN/DM
* UUID changes for blank node generation in JRDF and Kowari. RT/AN
* Fulltext acceptance tests now work without making changes to the OS environment. AN
* xsd:dateTime now millisecond accurate - also now using thread safe version to parser/format dates. ES/AN
* Refactoring of Tuples layer. More to come to remove duplication, reduce coupling and possibly adding features. AN

Sunday, March 06, 2005

Powerbook for Top Guns

The PowerBook Sudden Motion Sensor "This example creates a window displaying a bicycle wheel. The window i "stable" in the sense that if you rotate the PowerBook left or right, th window compensates by rotating itself by an equal amount in the opposit direction in an attempt to remain in its original orientation with respect to th ground. The bicycle wheel rotates too — independently of the window."

"While the PowerBook only uses the AMS as a defensive measure to prevent accidental damage to the disk drive, suc sensors could have a variety of uses. In particular, they have been considered as alternative input methods in use interfaces for video game controllers, phones, PDAs, and other mobile devices. While it is to be seen if they will b successful in these areas, such use at least has a novelty value"

Friday, March 04, 2005

ODA not OOD or OP

Grady Booch and others have written Ontology Driven Architectures and Potential Uses of the Semantic Web in Software Engineering. Anything that begins with: "Throughout the history of computing..." must be good.

"Having raised the idea of using of the Semantic Web in Software Engineering, a commonly asked question arises, namely; how does one broadly characterise the Semantic Web in terms of Systems or Software' Engineering use?"

"As a 'classification', merely to group together related tools and techniques for modeling rigorous semantics during specification and design stages of the Software Lifecycle."

"As a 'mechanism' for strongly identifying, discovering and sharing artifacts amongst discrete subsystems, systems and systems' design teams both during design and at runtime"

This second use is very similar to Ontological Programming and Lisp (better is better and Ontology-Oriented Design and Programming). Where developers/customers/analysts/etc share and maintain ontologies and develop solutions against these ontologies.

"Given that The Semantic Web uses triple-based data representation and that this is merely a minimalisation of the representation employed in relational database technologies, the attraction of considering the Semantic Web as a specialised relational framework has been recognised for some time."

Thursday, March 03, 2005

REST vs the Rest

Web Resources and WS-Resources " Now I can still only really talk from the point of view of first impressions, but it seems to me that the WS-Resource approach seems generally more concrete than the resource abstraction of RDF. I think it likely that WS-Resource constructs could be modelled in RDF. However, the emphasis of WS-Resource is very much on the protocol, so this isn’t really comparing like with like."

"I can see how state can be managed using WS-Resources, but what I having discovered is why the assumption is made that because SOAP++ messaging is usually done statelessly, it has to be that way. State can (and often is) maintained at both client and server sides of communications. If state that is global across client and server is needed then that can be maintained using one of the many reliable messaging protocols possible on top of HTTP."

Another XML UI Framwork

XUI: Finally, a Java GUI Framework You Can Love "From experience, it is almost always the case that the UI description and the functionality and business logic are mixed up within the Java classes.

With XUI, separating them isn't just easy, it's automatic. Using the XUI editor, you select an item, associate the name of the event that processes that item, and XUI will create a separate Java class containing the stubs for running that event."

HyperJournal

HyperJournal "HyperJournals versus “core journals”. By clicking on an author’s name, the HyperJournal system automatically searches the entire HyperJournal network and produces a citation list that includes all the articles written by the author, all the articles the author has cited, and all the articles that cite the author. Comprehensive bibliometric lists can thereby be composed without the need to rely on the manual consultation of a small set of “core journals,” often exclusively in English. In this system, by contrast, it will be the actual give-and-take of academic discourse, registered automatically on the network through citations, which will signal the prestige of a journal (even of small niche journals written in so-called minor languages) and establish the reputation of scholars. In addition, through the use of (semantic web) RDF describers, bibliometric lists can be constructed that distinguish, for example, between positive and negative citations."

Wednesday, March 02, 2005

Fedora 2.0 and Kowari

Fedora 2.0 Release Notes "Fedora 2.0 includes significant new features and improvements including the introduction of the Fedora Object XML (FOXML) schema as the new internal storage format for objects, introduction of the Resource Index that provides enhanced search capability, introduction of a Batch Modify utility, upgrades of all third party libraries, performance enhancements, and a number of bug fixes."

Kowari is mentioned in "Fedora: An Architecture for Complex Objects and their Relationships": "Fedora expresses relationships by defining a base relationship ontology using RDFS [17] and provides a slot in the digital object abstraction for RDF expression of relationships based on this ontology. Assertions from other ontologies may also be included along with the base Fedora relationships. All relationships are reflected in a native RDF triple-store using Kowari [44]. The query interface to this triple-store is exposed as a web service, providing a rich information foundation for external services."

Looks like there's some Trippi work too.

Chris Wilper and Edwin Shin both have contributed back to Kowari too. Most recently, with changes to the DateTime datetypes in the post-Kowari Pre-Release 2.

Agile Services

I'm probably just combining two buzz words to appear like a consultant, but it's more like RDF for Agile Services.

When You Sit Down To Write A Description "...you discover that doing so is unnecessary."

"In a REST-style service, we want an analogy to the self describing hypermedia we have in the HTML scenario. First let's assume we'll use some form of XML as our hypermedia. It's easy to imagine a XML document. Maybe even more machine friendly would be an RDF document -- a bunch of RDF statements. Your client invokes GET on the well known URL of the service, and receives an RDF form. The RDF form describes the names of parameters and how to serialize them. So just as in the user driven HTML case, the client needs no foreknowledge of what the neccessary parameters do, or even what their names are. But we still need an automated "user" to fill out those parameters. Since the RDF form describes the parameters in RDF, your client can map the RDF types of those parameters to elements in its data model. Your client has to "understand" the service's ontology, sure. But that is a one-time mapping of ontology elements to, say, SQL queries."

Follow-up.

Throw Away Your Hierarchies of Knowledge

Taxonomies and Tags: From Trees to Piles of Leaves "But traditional taxonomic trees aren’t something we can throw away without a thought. They are an amazingly efficient way of organizing complexity because they enable us to focus on one aspect (e.g., that’s an apple) while keeping a universe of context (it’s a fruit, part of a plant, a type of living thing) in the background, ready for access. Tree structures are built into our institutions. They may even be built into our genes. So we are in a confusing and fertile period as we try to sort out what works and what doesn’t. Without trees, how would we organize college curricula, business org charts, the local library, and the order of species? How will we organize knowledge itself?"

"Faceted classification still presents users with a hierarchical tree, making it easy for them to browse to what they want. But unlike traditional trees, faceted systems don’t decide beforehand how the branches are arranged. For example, if an ice cream stand organized its “customer experience” around a traditional hierarchical taxonomy – a tree – it might have a customer first choose between two flavors, then among three sizes, and finally between a cup or cone."

"Tagging systems are possible only if people are motivated to do more of the work themselves, for individual and/or social reasons. They are necessarily sloppy systems, so if it’s crucial to find each and every object that has to do with, say, apples, tagging won’t work. But for an inexpensive, easy way of using the wisdom of the crowd to make resources visible and sortable, there’s nothing like tags."

Another Way

I heard about this before I saw it (as I now have to prioritize what I do), first ant game. I guess I'm the only one who pines for declarative Ant.

Saturday, February 26, 2005

Message focus for AXIS 2.0

Axis 2.0 - Tech Preview / Milestone "Another driving force for Axis2 is to move away from RPC oriented
Web services towards more document-oriented, message style asynchronous service interactions. The Axis2 project is centered on a new representation for SOAP messages called AXIOM (AXIs Object Model). AXIOM consists of two parts: a complete XML Infoset representation and a SOAP Infoset representation on top of that. The XML Infoset representation provides a JDOM-like simple API but is built on a deferred model via a StAX-based (Streaming API for XML) pull parsing API. A key feature of AXIOM is that it allows one to stop building the XML tree and just access the pull stream directly; thus
enabling both maximum flexibility and maximum performance. This approach allows us to support multiple levels of abstraction for consuming and offering Web services: using plain AXIOM, using generated code and statically data-bound data types and so on."

From Ajax: A New Approach to Web Applications.

Also, What if SOAP had never happened?.

Thursday, February 24, 2005

Will Link For Food

REST design question #3: meaning of a link "The second counter-example is the rise of the rel="nofollow" attribute in HTML links, partly as an attempt to counter spam in weblog comments and wiki sandboxes. If anything, this appears to vindicate the old-school hypertexters. They should be rushing into the street in disheveled clothing with a mad gleam in their eyes, shouting “Look, we were right! It took 15 years, but finally everyone sees that links do need semantic information attached!” and so on. But they’re not, probably because they’re smart enough to realize that this isn’t, quite, change the primary meaning of a link. The rel="nofollow" attribute says that the author does not endorse the link target, but it still provides a more complete version of the information."

REST design question #4: how much normalization "The project I mentioned actually was trying to use RDF [first the 1.0 WD, then the REC]; unfortunately, RDF makes an example like my third one difficult, since in 1.0 at least, a property had to have either a link or content, but not both; you end up having to create a new, inline resource for every link, which is messy. I’m not too familiar with the newer RDF version, so I don’t know if they’ve fixed that by allowing labeled links.)"

REST design question #5: the “C” word (content) "On the other hand, the lack of any kind of standard content format makes it hard actually to do anything useful with RESTful resources once you’ve retrieved them. People have put forward candidates for standard XML-encoded REST content, including RDF and XTM, but it’s unlikely that either of these will take off, especially since RDF (the leader) does not even work nicely with most other XML-based specifications like XQuery or XSLT."

Tuesday, February 22, 2005

Commercial Licences for OS Projects

Here's a few commercial tools that give you licences if you are doing OS work:
* Jira (defect tracking),
* YourKit Java Profiler (memory and CPU profiling - runs on OS X),
* IntelliJ (IDE),
* Anthill (Continuous Integration).

Friday, February 18, 2005

Comparing YARS and Kowari

Cold, Mastering OWL, Scalability, Indexing "There are two differences in their implementation to our own. The first is that they used B-trees rather than the AVL trees that Kowari uses. That is not a significant difference, and I blogged about this several times before. The main advantage of the AVL tree is that they are cheaper to write to the structure than B-trees are, though a little slower to read. They also pointed out that they wanted to use an existing library for the index, and while B-tree libraries are common, we never found a completely working AVL tree library (deletions were always buggy).

The second difference is a set of special statements which count the number of triples in parts of each of the indexes. This is certainly novel, but not an approach I would use. I believe that counting is still very efficient in Kowari (O(log(n)), and the space overhead they incurred would seem prohibitive. More importantly, writing is always the slowest operation, and their system would incur a large writing penalty for using this scheme."

Thursday, February 17, 2005

RDF/XML for Aliens

Master Foo explains XML to Aliens "Aliens: What about knowledge representation? Fundamental building blocks such as subject, predicate, object triples, you have another technology for that form of data presumably?

Master Foo: No, increasingly all that data is in XML too."

"And so the conversation between Master Foo and the Aliens continued long into the night. In the morning, Master Foo popped up his instant messenger client to tell the world of his encounter with the aliens.

'They have not invented XML', he said, 'because they do not need it.'. Instead, they have developed technologies that we would probably call CSV++, XHTML++ and N3++[1]. Looks very sensible to me. I'm going back to their place. Bye.'.

Master Foo left to live with the aliens. That surprised everyone."

Achieving WS Functionality with REST

REST design questions "REST in its now-broadened meaning is easy to explain: pieces of data (likely XML-encoded) sit out there on the web, and you manipulate them using HTTP’s GET, PUT, and DELETE methods..."

"This very simplicity should raise some alarm bells, though. RDF also has an apparently simple data model, but for RDF 1.0, at least, the model turned out to be painfully incomplete, as I found out when I implemented my RDF parsing library. Is REST hiding any of the same traps? "

REST design question #2: listing and discovering resources "The second in my series of REST design questions is how to handle listing and paging, or, in fancier jargon, resource discovery. I prefer concrete examples, so I’ll start with one that I know is flawed and then try to find ways to fix it."

Wednesday, February 16, 2005

Quick Links

* Policy-Aware Web Kickoff Meeting "The Policy-Aware Web will "a rule-based policy management system" based on Semantic Web techniques. The first paper is here."
* IE 7 "First, some basics: we’re committing to deliver a new version of Internet Explorer for Windows XP customers. Betas of IE7 will be available this summer. This new release will build on the work we did in Windows XP SP2 and (among other things) go further to defend users from phishing as well as deceptive or malicious software."
* Understanding the Place of POX, SOAP and WS-* in Building XML Web Services.

YARS

I thought I'd put a link in as well into my recent Graph and Triple Store to YARS. Lots of good stuff in there (small, HTTP interface, etc). Interestingly, they use JDBM which doesn't use NIO. I evaluated JDBM for blank node tracking but found that it was too slow for Kowari.

Tuesday, February 15, 2005

SSDL

"SSDL is a SOAP-centric description language for Web Services. It promotes message-orientation as the architectural paradigm for building distributed applications and enables protocol-based integration between Web Services. The SSDL effort is an attempt to explore ideas in the areas of contract and protocol description and Web Services implementations using message-oriented programming abstractions."

"I collaborated with a small team of people to produce a description language for Web Services that we think is exciting since it encourages us to reason in terms of messages, rather than 'operations', 'interfaces', and 'inheritance', when writing contracts...We have made available four such protocol frameworks: MEP, CSP, Rules, and SC). There are also an SSDL high-level overview document and a whitepaper available."

The SOAP Service Description Language and SSDL: The SOAP Service Description Language.

Where's the SOAP?

SOAP is boring, wake up Big Vendors or get niched "Evidence continues to mount that developers can' t be bothered with SOAP and the learning requirements associated with use of the standard for information interchange. It is often described as "lightweight", but its RPC roots keep showing.

Developers are turning their backs on the standard. Folks that is, building interesting information splicing apps--semantically rich platforms like flickr and Amazon are being accessed by RESTful methods, not IBM/MS defined "XML Web Services" calls. Now it seems the Creative Commons is responding to RESTful demand. Or more pertinently-not responding to SOAP demand because there isn't any."

"Whats a web service? Still a great question. But anyone that defines a Web Service using SOAP in the definition is missing out on where the action is. Distinctions between enterprise and "consumer" are breaking down. REST is evidently where that convergence is being played out, not WS-I."

Via Is SOAP a washout?.

Also, Interop is Hard: "If you find that you must use a toolkit to help with generating the contract, I'd recommend a technique that is similar to Steve's customer's: generate WSDL using a foreign toolkit, remove all unwarranted idioms and assumptions, and then try to import the result in the toolkit that you are using to develop the service."

Jon Udell had a very interesting post about Google's new map service (all plain XML/HTTP and XSLT where you want): Google Maps is a web of linked XML documents.

Saturday, February 12, 2005

Imagine Google on iTunes

mSpace "mSpace helps people build knowledge from exploring those relationships. mSpace does this by offering several powerful tools for organizing an information space to suit a person's interest: slicing, sorting, swapping, infoViews and preview cues."

Sourceforge page and onlie demo. Requires a Mozilla based browser - it seems as if it's using XMLHttpRequests.

What a MEST

On Interoperability and Tim Ewald's 3 Web Services Stacks "Replacing a world of distributed applications written with DCOM, CORBA, Java RMI, etc with one where they are written using the WS-* protocols is a step in the right direction. I completely agree that it leads to better interoperability across technologies produced by the big vendors who are using incompatible technologies today.

But when your plan is to reach as many parties as possible one should favor simpler Web services technologies like plain old SOAP or just plain old XML (aka POX). Plain old XML doesn't necessarily mean following the principles of REST either."

Intersecting XML threads "What the REST vs SOAP and Doc vs RPC debates miss is the subtle point at which systems become multi-celular. At some point, evolution stopped producing organisms consisting of every bigger and bigger cells, and started producing organisms consisting of multiple differentiated cells. These cells communicate exclusively via message passing."

MEST is already omni-present, if you look for it "As far as I can tell, the basic idea behind MEST is that web services developers should be thinking about message passing instead of RPC calls. I completely agree. But I disagree with the idea that that means there should be one WSDL interface with one operation “ProcessMessage”. There's no need to go there, because we're there already."

Some of the earlier MEST postings were covered in "MEST Architecture".

XAML vs SOAP vs RDF

XAML, SOAP 1.2 Part II Section 3, and RDF "All three support the notion of named properties...the notion of sequences of values...[and] the notion of atomic values."

"...RDF expects you to buy into a URI-based resource model and only added the notion of "blank nodes" recently. For data transfer applications (which are exceedingly common), there often isn't a persistent URI or ID for the data being represented. Query results that use projection are a great example where having to cons up URI is overkill.

On the upside, RDF is unique amongst the three in its ability to have properties on properties on properties on…. Being able to treat an RDF statement as a resource that itself can have properties (in addition to the object or "value" of the property) is certainly powerful and appeals to the inner modeling geek."

I think the notion of blank nodes has been around since at least 1999.

Friday, February 11, 2005

Nearly an RDF Store

LWI and Safari: A New Index Structure and Query Model for Graph Databases "Graph databases are gaining importance in several emerging applications, especially molecular biology. In many existing approaches, such databases are regarded as a ``schemaless'' collection of labeled graphs. However, there are often user-defined schemes that help in limiting the search space while answering a query and to deliver meaningful results. Techniques based only on index structures do not exploit such situations. This paper presents our work on a graph database system called GRACE, where a DML called Safari is proposed for graph databases and is closely integrated with structural indexes in the DBMS. Users may define schematic structures over a subset of graphs in the database and add them into the database as any other member graphs."

Has three data structures attribute-value index (AVI), graph location index (GLI) and label-walk index (LWI). AVI is an inverted index that stores gid values of graphs matching pecific attribute and value pairs. GLI indexes every graph entered into the system. LWI is used for structure based searches.

The AVI is string only. They claim that it's general purpose enough to do any labelled graph application.

Part of COMAD 2005.

Graph and Triple Stores

RDF and Graph DBMSs A great page listing a lot of different types of databases:
* AKT Triplestore Used by Redland.
* Sesame Java based, B-Tree indexing.
* Kowari Java based, AVL Tree and Node/String pool. A good write up of the ideas is in Kowari: A Platform for Semantic Web Storage and Analysis and Yet Another RDF Store.
* YARS Available for download. Uses Java, JDBM and only 2MB.
* RDFStore C based, even has compressed triples. See Indexing and retrieving Semantic Web resources: the RDFStore model.
* SWI-Prolog/XPCE Semantic Web Library
* ParkaSW
* GRAS "A Graph-Oriented Database System for SE Applications"
* coreSe

I'm only including native RDF stores (non-SQL based).

As these are commercial only it's hard to tell what they're based on:
* Intellidimension
* Cogito

2 KAON

dlpconvert "dlpconvert is able to convert ontologies, that are within the dlp-fragment, from one syntax - namely the OWL XML Presentation Syntax - into another, here Datalog. Thus you can just take your ontology, convert it and then use the result as your program in your Prolog-engine. Isn't that cool?"

rdf2owlxml "Another KAON2 based tool just got finished, a converter to turn RDF/XML-serialisation of an OWL-ontology into an OWL/XML Presentation Syntax document. And it even works with the Wine-ontology."

XForms XPlodes

Top 10 XForms Engines "...the XForms implementation landscape has intensified. Of the ten engines previously listed, a healthy seven make a repeat appearance, having made significant improvements. IBM's XML Forms Package narrowly missed being on the list--only because it hasn't been refreshed in a while. Even so, IBM still makes an appearance here, through their joint work on XForms-in-Mozilla. That work is part of the latest buzz in the XForms world, along with the other the new entrants.

Other new entries in this year's list are an OpenOffice implementation, a second Novell engine as an IE plugin, an updated Oracle engine that now can run inside IE, and two new approaches to implementing XForms without plugins in modern browsers. (Because of double entries, there are actually more than ten engines in this top-ten list. Go figure.) With the availability of native browsers and plugins, server solutions, and even mobile devices, XForms has a wider reach than ever."

"Also, Chiba can now run on the client in a hidden Java applet, thanks to a new technology called "convex." Look for Chiba to continue to blur the line between client and server-side processing. This is a good thing."

Adriot Management

Agile Project Management. Links to such articles as Martin Fowler's The New Methodology.

Via Agile Management which was calling to "Burn your PMBOK guide as a sacrifice to the gods of uncertainty! Melt down your iron triangle and embrace the flow of value! The Declaration of Interdependence".

Wiki World

Making the Case for a Wiki "The wiki was rather aptly described by Ward Cunningham as 'the simplest online database that could possibly work'...Generally speaking, a golden rule of successful software deployment is, 'get to know your audience'. There are any number of approaches to this goal; from the approach advocated in The Inmates Are Running the Asylum [9], thinking yourself into the user's perspective in a manner reminiscent of method acting, to Lucy Suchman's pioneering approach to ethnography in the office environment. These vary in efficacy, but it is very worthwhile attempting to fit time for such analysis, investigation, or roleplay into the early stages of any technology deployment. Knowing your audience, in computer-mediated communication, means gaining an understanding of the target community. Be warned: with only rare exceptions, if you cannot imagine your target group conversing comfortably together under normal circumstances, the chances are fairly slim that they will imagine they can either … much less online."

Seems to miss a lot of the corporate Wiki usage - like requirements gathering. A problem can be MS Office format filters - where only Word, Excel and Powerpoint are valid file types to express ideas in.

Thursday, February 10, 2005

RDF Metadata Gardening

RDF Exporter Plugin for iPhoto "My aims in writing this plugin were:
* To provide a functional example of how to write an iPhoto plugin, up-to-date as of iPhoto 4
* To allow conversion of keywords into arbitrary RDF (e.g. from “Taken by Richard” to dc:creator :Richard, for example)
* To export additional RDF, such as titles, dates, etc.
* To provide a datasource for my PhD work."

Wednesday, February 09, 2005

UDDI and RDF

Registry holds the keys to SOA success "UDDI is certainly gaining momentum, we have two customers interested in moving to UDDI; but from a metadata perspective a number of people want to go a lot further." In the meantime, too, other developments have been taking place. Blue Titan instead uses a metadata repository which can be rendered as UDDI but others are pursuing different standards proposals, such as WS-MetadataExchange, which is being proposed by IBM and Microsoft...A registry without UDDI is not going to work in an SOA. But where it lacks is the ability to map the business into the overall SOA model."

"In fact, Graham Glass, CTO of webMethods, speaking at last November's XML and Web Services conference, highlighted this disconnect with everything outside of the services environment as one of the key weaknesses in SOA. "We think UDDI is a good specification. But if you create a shopping list of all the parts of your IT infractructure — services, schemas, business processes, portlets, workflows and databases for example — if you try to do all this in UDDI it would be very hard."

Glass called for UDDI to widen its scope and embrace some of the emerging standards in the semantice web such as RDF."

"He [Lipton] concludes: "It's more complicated than to string a single thing in the middle that everybody has to go to and say: "Mother may I?" That's not very peer-to-peer or distributed — that's so 1980s client/server.""

Libraries for the Semantic Web

Developers Guide to Semantic Web Toolkits for different Programming Languages " This guide collects Semantic Web toolkits for different programming languages and gives an overview about the features of each toolkit, the strength of the development effort and the toolkit's user community."

Java and Python come up pretty well as far as choice is concerned (with 6 and 7 respectively).

Tuesday, February 08, 2005

Not Nothing

Keep Web Services on a Diet highlights the different approaches to a rule based system, ends with "The affirmative approach, "This is what you're allowed to do," and the exception-detecting approach, "This would be odd and should be reported if it happens," seem to me a much more attractive set of strategies."

Monday, February 07, 2005

The SWeb for Web Services

Web Service API and the Semantic Web "For Semantic Web services to become a reality, a markup language must be descriptive enough that a computer can automatically determine meaning. Following is a list of tasks such a language would require:

I Need to Find a Service (Discovery)
A program must first be able to automatically find, or discover, an appropriate Web service. Neither WSDL nor UDDI allows for software to determine what a Web service offers to the client. A Semantic Web service describes its properties and capabilities so that software can automatically determine its purpose.

I Need to Run a Service (Invocation)
Software must be able to automatically determine how to invoke or execute the service. For example, if executing the service is a multistep procedure, the software needs to know how to interact with the service to complete the necessary sequence. A Semantic Web service provides a descriptive list of what an agent needs to be able to do to execute and fulfill the service. This includes what the inputs and outputs of the service are.

I Need to Use a Few Services Together (Composition)
Software must be able to select and combine a number of Web services to complete a certain objective. The services have to interoperate with each other seamlessly so that the combined results are a valid solution. In this way, agent software can create entirely new services by combining existing ones on the Web.

I Need to Know What is Happening After I Run the Service (Monitoring)
Agent software needs to be able to verify the service properties as well as monitor its execution. Some services may take some time to complete, and the agent should have the ability to monitor the status of a process."

Reasoning

As a followup to Ruling a list of OWL reasoners (mainly DL) from SemWeb Central.

Via RDF IG.

Sunday, February 06, 2005

Mozilla XForms

MOZILLA FOUNDATION ANNOUNCES BETA RELEASE OF XFORMS 1.0 RECOMMENDATION "Developed in collaboration with IBM, Novell, and the open source community, XForms technology is now available as an extension to the Mozilla 1.8 and Firefox 1.1 web browsers which are currently under development. This release is intended for users in non-production environments who are interested in exploring XForms 1.0 technology ahead of the extension's general availability release later this year. The extension is available for Linux, Windows, and Macintosh platforms. Beta user feedback on this release is highly encouraged."

http://www.mozilla.org/projects/xforms.

Completed Transactions

Commons Transaction "Commons Transaction aims at providing lightweight, standardized, well tested and efficient implementations of utility classes commonly used in transactional Java programming. Initially there are implementations for multi level locks, transactional collections and transactional file access. There may be additional implementations when the common need for them becomes obvious. However, the complete component shall remain compatible to JDK1.2 and should have minimal dependencies."

Also, Tyrex, Transaction Recovery and JOTM.

Saturday, February 05, 2005

Guides, Minis and JSF

Predictions for 2005, part 1 "Also on the subject of filtering our lives, metadata becomes increasingly important, and the push is on for new ontologies. The Semantic Web, however, doesn't happen yet because there is still resistance from those who are convinced it's too complicated. (A large portion of those people will have never read the specifications, mostly because they are too complicated.)"

Also, "WS-" spec fatigue, SOA does not mean SOAP and REST APIs continue to rise. Also, Part 2.

Mac Mini: The Emperor's New Computer "So is the mini a maxi value? For me, clearly, no. When I consider that a good deal of my time is spent running applications like Disk Defragmenter, Scandisk, Norton AV, Windows Update and Ad-Aware--none of which are available for the Mac platform--it doesn't make sense for me to "switch" to a Mac at this time. But will Apple's famous marketing team be able to sell the the emperor an invisible computer anyway and turn the mini into a maxi hit? That’s the question that remains to be answered."

Using JSF technology for XForms applications (mentions XSmiles XForms editor/browser) and JSF for nonbelievers: Clearing the FUD about JSF.

Friday, February 04, 2005

Enhanced Javadoc

Documentation Enhancer for Java "The Documentation Enhancer provides the following semantic information:
* Call-graph information: for every method, what other methods may call it and what are the methods that it may call. This analysis uses sophisticated type analysis algorithms to resolve virtual calls.
* Effect information: for every field, which methods may modify or inspect it. For every method, what may it do (modify, forward, inspect) to its parameters and to static fields, and what values it may return (if applicable).
* Reference information: for every class, which classes reference it and which classes does it reference. The same information is provided for packages at the package level.
* Executable classes: classes that have a main(String[] args) method are detected and marked as such."

For Windows only.

Wednesday, February 02, 2005

URI dereferencing

For more than the first time, I'd forgotten and had to go through URI Equivalence. My feeling is that deferencing should be done by calling code. It's not the responsibility of say Java's URI object to dereference them (basically only doing string comparison). If you you are doing Scheme-based Normalization you apply it externally - mapping them consistently to the same URI. In Kowari our models can mapped from "rmi://localhost:1099/server1#..." to "rmi://localhost/server1#...". However, if the server starts on port 1199 instead then that's mapped and 1099 will be left. Tim Bray wrote something about it "Good Practice When Generating URIs".

Tags link

Stemming tags, and one website to the tune of another "So, what are you seeing in this movie? It's nothing more than a bit of DHTML trickery that imports a subset of del.icio.us functionality into an existing website...I like the immediate feedback that you can get from adding a tag to a programme. Decide that 'cello' is relevant, and within seconds you see a bunch of other cello programmes. It's common for content management systems to demand 'metadata' or 'keywords' of you when you file content, but rare that there's an easy way to get a feel for what value you've added by doing so...This was my first real attempt to wrangle the XMLHTTPRequest system, and it was a satisfying one. I did learn one or two things, including some problems with asynchronous and synchronous modes of operation."

Folksonomies Tap People Power "Dog owners would probably object. But because of Flickr's tagging system, which allows the photographers or other users to assign identifying tags to most photos on the service, we know that Flickr hosts 23,081 images tagged with "cat" or "cats" and only 17,463 with "dog" or "dogs.""

"Rubel also said he'd like to see services like Google add tags as a way to bring more user-specific context to search results. As it is, he explained, search-engine results differ from tag searches in that they are not based on user-created content.

"One of the things that's nice to see is that people are actually spending time tagging and doing it in a social environment, and following the power curve and the net effect," said Vander Wal. "The more people getting involved with it, the greater the value.""

More on Technorati tags "By allowing people to add format metadata, tags give bloggers the power to describe aspects of their posts that would not be accurately reflected by keywords selected from the content."

Closure - Code is Data

Wall, Escher and Berners Lee: An eternal golden braid On "Drawing Hands": "With my ever-present geek-glasses on, I see the hand of the left as symbolizing data. The hand on the right symbolizes code. The code is of course also data which in turn, can be viewed as code. Somebody once said that a data structure is nothing more than a poor, limited programming language. I like that. Two hands. One hand, inter-twingled in the drawing of the other hand."

"With my ever-present geek-glasses on, the hand on the left in Escher's print also belongs to Larry Wall[7], inventor of Perl[8]. Perl is a good example of a computer code format that is good at embedding computer data formats. The hand on the right belongs to Tim Berners-Lee[9]. Inventor of HTML. HTML is a good example of a computer data format that is good at embedding computer code formats. Two hands. One hand, inter-twingled in the drawing of the other hand."

Tuesday, February 01, 2005

e-mentality

e-mentality is Semantic Web Outliner "For me, this project is kind of 'technology trainer'. I'm fascinated by REST, cognition visualization, outline editors, Semantic Web, TWiki, Longhorn architecture and many other emerging technologies."

e-mentality blog and MindRaider via Danny's MindRaider.

No time

For later:
* HealthCyberMap.org
* Entrez

Monday, January 31, 2005

Ruling

Surprisingly, I might be doing something for this in my current job. So I thought I'd go through all the rules engines over the years. Paul recently blogged "I'm sure Andrew will have blogged this years ago, but I just found Jess. This is a Java implementation of the Rete algorithm." and he's right I first blogged it back in 2002 (linking to Role of Java in the Semantic Web). Like Danny mentions the licence for Jess is unusual.

Some interesting links:
* A good list of rules engine in Java Open Source Rule Engines Written In Java.
* Mandarax "Mandarax is based on backward reasoning....The easy integration of all kinds of data sources. E.g., database records can be easily integrated as sets of facts and reflection is used in order to integrate functionality available in the object model. Other data sources (like EJB, data returned by web services etc) can be integrated as well." The Mandarax blog mentions Mandarax Event Calculus Module "...a formalism for representing and reasoning about events and their effects in a logic programming framework." EC and Mandarax 3.3.2 is available from the Mandarax SF page.
* SWRL 0.7 RDF and XML concrete syntax that "...extends the set of OWL axioms to include Horn-like rules."
* Proposal for rules (including in RDF).
* ROWL "...source code and instructions to frame rules in OWL, transform them into Jess (Java Expert System Shell) rules. In addition, the page also contains a small tutorial that will help you frame rules in RDF/XML using our rule ontology."
* Rewerse - Reasoning-aware Querying "The objective of the WG is to develop, implement, and test (on selected Semantic Web applications) such a (provisionally rule-based) language at a pre-standard level."
* Pychinko "Pychinko is a Python implementation of the classic Rete algorithm (see Forgy82 for original report.)"

Sunday, January 30, 2005

Too Many Cooks

How Not to Write FORTRAN in Any Language "Style guides: I hate ’em. After all, I know which style is the best: mine! Style guides often appear to be dreary lists of arbitrary-seeming rules that limit my creativity. Reading them puts me to sleep.

When I maintain code, however, I set aside my personal style and try to match the style of the project. I want my code to look exactly like everyone else’s code, at least as far as the style guide goes. The reason for this, again, is familiarity. (Is this sounding familiar?) If you use the same coding conventions throughout a software project, the maintainers will grow accustomed to the style and it will magically become transparent to them. They will see the code, not the style.

Lack of consistency is one of the hallmarks of bad code. If 30 different people worked on a source file, I really, really don’t want to see 30 different coding styles or naming schemes when I read it. It becomes a nightmare to attempt to find structure in code like that. Coders have to be humble and accept that for code to be readable, their favorite style is not as good as the established style."

Changing Software and Legacy Code "The last consequence of avoiding change is fear. Unfortunately, many teams live with incredible fear of change and it gets worse every day. Often they aren't aware of how much fear they have until they learn better techniques and the fear starts to fade away."

Saturday, January 29, 2005

New SOFA

SOFA (Simple Ontology Framework API) New home and new release available for download. Updated support for Jena 2, new methods on OntologyModel and ThingModel discarded (will have to change this for Kowari).

Semantic Web Deployment

Piggy-Bank "The Piggy-Bank extension is designed to let users of the Mozilla Firefox browser collect and browse "semantic data" linked from ordinary web pages. Semantic data is data described using the Semantic Web project's Resource Description Framework (RDF)."

Similar to Annozilla but it comes with its own server - neat use of Firefox extensions.

"Piggy-Bank uses the HSQLDB databases, indexed using the Lucene library. Piggy-Bank insternally runs a Jetty web server to serves content retrieved from the databases, dynamically formatted using the Velocity web templating engine."

OS X users will have to use the Java Plugin to enable Java 1.4 in Firefox. But why use Firefox, it can't use ActiveX (it's 1997 all over again).

American Remakes

test screening of HITCHHIKER'S GUIDE TO THE GALAXY "...Speaking of Trillian, needless to say, the arc of her and Arthur falling for each other felt really out of place and was entirely gratuitous."

Reminds me of the following:
* Red Dwarf USA or White Dwarf.
* Office remake 'a flop' ""Daniels makes the same mistake that Coupling did by basically copying the original so much that you might as well just ignore this and buy the DVDs from BBC Video.".
* American market adapts British TV for new audience "Even from the start, the show faced changes by crossing the Atlantic. Some of the spicier sex jokes were cut, and the half-hour episodes were shortened eight minutes to inject commercials."
* Faulty Towers "John Cleese was a bit baffled with the Amanda's: "I asked the American company how the adaptation was looking, and they told me `It's looking good - we've only made one change.' They wrote out Basil Fawlty, which I found incomprehensible.""

A list of remakes here. Doesn't look like they've attempted Press Gang, yet.

Friday, January 28, 2005

The Digital Librarian

SIMILE: Practical Metadata for the Semantic Web "Like any good system developed in collaboration with a research library, DSpace manages metadata about the content it manages and distributes on the web. However, its metadata support is currently limited to the general but relatively small Dublin Core descriptive metadata schema. In the future, DSpace needs to support additional metadata schemas for a variety of purposes: finding digital research material described in various, domain-specific ways, and managing that digital content over time in order to preserve it. As DSpace expands to use new metadata schemas, it will have to deal with the problem of interoperability.

Enter the Semantic Web and extensible metadata. The Semantic Web Core stack — RDF, RDFS, and OWL — enables people to create ontologies to describe their specialized metadata (perhaps building on existing, more general ontologies) and to make them generally reusable. But most people are not trained Semantic Web developers. They are going to need some tools for this and also to be able to assess whether they did the job correctly."

"For users, can we design faceted browsing interfaces that scale to dozens of RDF ontologies? How about improving navigation across the linkages between ontologies? How can we support searching that will start in one domain/ontology and expand into relevant related domains/ontologies?"

Kowari, Jobs and stuff

This is just an update of the crisis from a few weeks ago.

First off, Kowari development hasn't stopped. There's been code changes from Simon, David M and myself. More importantly there's been quite a lot of planning involved and more to come. It's also been encouraging to get so many potential leads for future paid work. However, unlike some of the other people from Tucana I needed to get work, for sure, by sometime about now. So with that in mind I've taken a J2EE contracting job for 3 months, it starts Monday. While working on Kowari we've taken reduced pays or no pays but the periods have been somewhat predictable, allowing me to plan ahead. Without any of that, things had to happen faster than I would've liked.

Already though, I have a chance for my first paid Kowari work. This is an article about how Kowari handles blank nodes - both in querying and through various APIs.

The next set of work I'd like to do would be OPTIONAL. There seems to be quite a lot of interest in that. So having recently added things like trans, walk, having, exclude etc. to iTQL it should be fairly straightforward to do this work. Something I could do, I think, in my spare time.

The other area of interest is of course OWL and inferencing. There's several issues involved with this and the two I'm currently most interested in is management of the graphs and handling schema changes. The first issue means there's a requirement for creating a triggering mechanism and creating logical graphs from several physical graphs. The second means reading and some how trying to validate ideas that I've already had.

If you are someone who would like to get involved in supporting contracting work for Kowari then get in touch with Software Memetics. The key benefit of this is to be able to use the pool of ex-Tucana developers. Going forward it's obvious that we need more developers and a steady supply of work - I'd especially be interested in long term contracts or full time work.

Paul has also put up what's happening to him and so has Andrae.

Bubble cars and the year of metadata

Cheap Eats at the Semantic Web Café "This event happened for me the past few weeks; an experience formed of discussions about digital identity and laws of same, LID, Technorati Tags, new and old syndication formats, Google’s nofollow, and the divide between tech and user. Especially the divide between tech and user." Wow!

Burningbird on why tagging can't violate the Second Law of Thermodynamics "My initial concern about the hype is whether we're going to get more apps that get us tagging. If we don't, then tags won't have much effect. If we do, then I simply don't know whether we're going to be able to solve the problems inherent in scaling tags: Tags work because they're so simple and because they are so connected to the human semantic context, but having billions of tags won't work because they're so simple and connected to the human semantic context."

Applications to get you tagging is covered in: I Want a Pony: Snapshots of a Dream Productivity App "Nobody cares what “metadata” means, but they for damn sure know they want their mp3s tagged correctly. Ditto for del.icio.us, where Master Joshua has shown the world that people will tag stuff that’s important in their world. Don’t like someone else’s homebrewed taxonomy? Doesn’t matter, because you don't need to like it. If I have a repeatable system for tagging the information on just my Mac and it’s working for me, that’s really all that matters."

"The upcoming Tiger release of Mail.app brings iTunes-like smart folders to your mail, and that’s so great. But I also want a Gmail-like tagging system that lets me create multiple non-destructive groupings without multiple copies or resorting to complex hacks. I want all my “stuff” to reside in a big pile, and then I want smart help to script it, organize it, and associate it however I like."

Wednesday, January 26, 2005

Kowari Roadmap and Overview

I have been asked by several people for a general roadmap or plan for future Kowari development. While it's hard with the vagaries of open source development and time/money I've released a draft version which highlights what I think should be in Kowari 1.1 Pre-Release 3. A future version will include what will make up a full 1.1 release.

Update: Modified it based on some of Paul's early feedback and removed some of the more pressing grammatical errors (still a work in progress though).

Tuesday, January 25, 2005

SeRQL+

SeRQL Extensions "Finished extensions:
- column alias (AS)
- set operators (UNION/MINUS/INTERSECT)
- query nesting (IN)
- quantification (ANY/ALL)
- grouping (GROUP BY/HAVING)"

Based on the attached PDF the only things extra to iTQL is column alias and the aggregate function SUM (we have COUNT). The syntax is different and perhaps SeRQL is better although the use of IN in iTQL leads to less verbosity. They've also got slated recursion which is similar to trans and walk. It's good to see all stores reaching a common level of functionality. We have to get OPTIONAL and some other things to catch-up too.

Monday, January 24, 2005

Removing the Crap from Metacrap

Folksonomies, Taxonomies and Metacrap "One thing that is clear to me is that personal publishing via RSS and the various forms of blogging have found a way to trample all the arguments against metadata in Cory Doctorow's Metacrap article from so many years ago. Once there is incentive for the metadata to be accurate and it is cheap to create there is no reason why some of the scenarios that were decried as utopian by Cory Doctorow in his article can't come to pass. So far only personal publishing has provided the value to end users to make both requirements (accurate & cheap to create) come true.

Postscript: Coincidentally I just noticed a post entitled Meet the new tag soup by Phil Ringnalda pointing out that emphasizing end-user value is needed to woo people to create accurate metadata in the case of using semantic markup in HTML. So far most of the arguments I've seen for semantic markup [or even XHTML for that matter] have been academic. It would be interesting to see what actual value to end users is possible with semantic markup or whether it really has been pointless geekery as I've suspected all along."

Sunday, January 23, 2005

Using RDF to improve Object-First Development

There are many ways to create systems, including a "relational-first" approach and an "object-first" approach.

The example in these two pieces are two classes: Person and Employee. Person has first name, last name and age. Employee also has an ID and salary. How do you model these objects?

"One approach would be to create two tables, PERSON and EMPLOYEE, and use a foreign-key relationship to tie rows from one to the other. This will require a join between these two tables every time we want to work with a given Employee, which requires greater work on the part of the database on every query and modification to the data. We could store both Person and Employee data into a single EMPLOYEE table, but then when we create Student (extending Person), and want to find all Persons whose last name is Smith, we'll have to search both STUDENT and EMPLOYEE tables, neither of which at a relational level have anything to do with one another. And if this inheritance layer gets any deeper, we're just compounding the problem even further, almost exponentially."

"As if the above weren't enough, more frequently than not, the enterprise developer doesn't have control over the database schema--it's one that's already in use, either by legacy systems or other J2EE systems, or the schema has been laid down by developers in other groups. So even if we wanted to build a table structure to elegantly match the object model we built above, we can't arbitrarily change the schema definitions."

To approach this problem with an RDF based system is to create extensions to these schemas - this is not a problem and is almost expected. RDF specific databases, like Kowari, can avoid joining to represent these two objects - everything is triples. Subjects that are Person classes can be made Employee classes by adding two statements: saying the subject has an ID and salary.

Another advantage to an RDF system, especially when you start using ideas like resolvers, is to enable developers to integrate existing data and to create application specific database schemas. All data can be converted and adapted to the view required by the application. Filling out objects as they need to be viewed, potentially allowing a Person object to be viewed as Employee just with missing values. This can be achieved by applying a specific semantic for missing values (not recorded, not available, etc) or inferring missing details based on other data. You can of course, approach this normally and only show objects that are valid without modification. The point is, the flexibility is there.

Using this approach avoids both the "smaller than an object" and "smaller than a row (relation)" problems. The first by creating ad-hoc objects and the second because each item in RDF can be individually picked up, at the triple level, and used.

There's a third way mentioned, "Procedural-first" creates an encapsulation layer which takes the Session facade approach where the actual way in which data in persisted is abstracted.

Apart from the normal suspects (mentioned in the above articles) I've recently come across two related ideas, there are quite a few:
* JoSQL which is like SQL meets resolvers.
* SQLObject is an object-relational mapper. It allows you to translate RDBMS table rows into Python objects, and manipulate those objects to transparently manipulate the database.

Update: Danny wrote up a schema using RDFS to represent the classes.

Friday, January 21, 2005

Prince

Printing XML: Why CSS Is Better than XSL "The disagreement starts with how best to express all this. Walsh's solution is to write a 1000-line XSL transformation that generates XSL-FO, which is subsequently turned into PDF. We will argue that it's much easier for most authors to express styling in CSS; in the case of the WebArch document, one can reuse the existing CSS stylesheets (200 lines or so) and add some print-specific lines. And, although browsers tend to focus on dynamic screens rather than on printing, products like Prince happily combine CSS with XML and produce beautiful PDF documents."

Prince.

Repairing Databases

Coherent Integration of Databases by Abductive Logic Programming
"It is well-known that in general, the task of repairing a database is not tractable, as there may be an exponential number of different ways of repairing it."

"One important aspect of data integration systems is how concepts in the independent (stand-alone) data-sources and those of the unified database are mapped to each other. A proper specification of the relations between the source schemas and the schema of the amalgamated data exempts the potential user from being aware where and how data is arranged in the sources. One approach for this mapping, sometimes called global-centric or global-as-view (Ullman, 2000), requires that the unified schema should be expressed in terms of the local schemas. In this approach, every term in the unified schema is associated with a view (alternatively, a query) over the sources. This approach is taken by most of the systems for data integration, as well as ours. The main advantage of this approach is that it induces a simple query processing strategy that is based on unfolding of the query, and uses the same terminology as that of the databases...The other approach, sometimes called sourcecentric or local-as-view (used, e.g., in Bertossi et al., 2002), considers every source as a view over the integrated database, and so the meaning of every source is obtained by concepts of the global database. In particular, the global schema is independent of the distributed ones."

"When the set of integrity constraints is given in a clause form, methods of dynamic logic programing (Alferes et al., 2000, 2002) may be useful for handling revisions. As noted in (Alferes et al., 2002), assuming that each local database is consistent (as in our case), dynamic logic programing (together with a proper language for implementing it, like LUPS (Alferes et al., 2002)) provides a way of avoiding contradictory information, and so this may be viewed as a method of updating a database by a sequence of integrity constraints that arrive at different time points."

To determine which statements to keep and which statements are determined to be invalid when integrating:
"Among the common approaches are the skeptical (conservative) one, that it is based on a ‘consensus’ among all the elements of R(UDB, ?) (see Arenas et al., 1999; Greco & Zumpano, 2000), a ‘credulous’ approach, in which entailments are determined by any element in R(UDB, ?), an approach that is based on a ‘majority vote’ (Lin & Mendelzon, 1998; Konieczny & Pino P ?erez, 2002), etc."

ASystem homepage.

Every Machine is an Island

Semantic Web: Rise of the Machines "The bottom line is that it's about helping machines to communicate more effectively by providing them with a linguisitics framework. Distributed systems are currently built without this infrastructure, resulting in disjoint "islands of integration", the machine equivalent of the Tower of Babel."

"In the next part of this series, I'll talk about vocabularies, grammars and phrasebooks in more detail."

Thursday, January 20, 2005

Tuplespace

The Blogosphere as a Tuple Space "Tuple spaces get really interesting, though, because different collectives of users of the tuple space can each agree upon different sets of meanings for tuples—and the agreements exist outside of tuple space, so the space doesn’t need reconfiguration for any particular new use."

Reminded me of Semantic Clarity and a Google search also brings up Triple-space computing: Semantic Web Services based on persistent publication of information "...the semantic web is not made unnecessary based on the tuple-spaced paradigm. The global space can help to overcome heterogeneity in communication and cooperation, however, it does not provide any answer to data and information heterogeneity. In fact, this aspect is what the semantic web is all about."

Talking to Paul recently about how we were to proceed with OWL inferencing and it became apparent to me that the previous project to Kowari that I worked on, TMex, had a very similar alogirthm for processing documents and the underlying pre/post-conditions, coupled with the use of JMS (which has it's own query language) was similar to the modified Rete algorithm proposed for Kowari, it also had some similarities to some of the parallel rules based systems (still looking into that).

Via The Blogosphere as a Tuple Space

More on Comment Spam

Well I found some of mine here, here and here.

MSN Search and MSN Blogger are supporting it too.

Tim Bray's No Follow suggests another enhancement "...which says “don’t count this link for ranking purposes, but do take its content seriously as relevant to the indicated site.”

The Other Shoe on Nofollow "I can link to something I dislike and use the power of my link in order to punish the linked, but it won’t push them into a higher search result status...It’s an abuse of the purpose of the tag, which was agreed on to discourage comment spammers. More than that, though, it’s an abuse of the the core nature of this environment, where our criticism of another party, such as a weblogger, came with the price of a link. Now, even that price is gone."

Google adds "nofollow" to link tags "This will change how I write. And it will encourage more people to link to their competitors....Oh, and, did anyone notice how Google got its competitors to do something without needing to get a standards committee involved? All within hours?"

This reminds me of Annotea, "Annotea: An Open RDF Infrastructure for Shared Web Annotations" and Mozilla package.

Wednesday, January 19, 2005

Google Tweaks the Web's Semantics

Preventing comment spam " From now on, when Google sees the attribute (rel="nofollow") on hyperlinks, those links won't get any credit when we rank websites in our search results. This isn't a negative vote for the site where the comment was posted; it's just a way to make sure that spammers get no benefit from abusing public areas like blog comments, trackbacks, and referrer lists."

If this isn't a top down schema I don't know what is. Can't work? We'll see I guess.

Tuesday, January 18, 2005

Planning for Tomorrow's Web

Tomorrow's Semantic Web: Understanding What We Mean "If you're going to trust the answers from something, you've got to be able to understand why you should trust them. The web is also moving to being explainable, more capable of filtering, and more capable of executing services."

"Once I have just simple ontologies, so just taxonomies, just the subclass-superclass relationship, I can start to empower a lot of applications in ways that I couldn't before. I get to have the benefit of a shared vocabulary. It benefits things like search engines because you see more usage of the same terms, authors use the controlled vocabulary, users get encouraged to use a controlled vocabulary, databases leverage it, programs don't have to do translation between the terms—so we're all speaking the same language."

"These days if I'm doing an application that is looking to get into those more complicated ontologies at some point down the road—possibly not today but in a year where I want to exploit that information—I typically aim to encode in OWL, the ontology web language, because it sits on top of, it extends the fairly well used vocabularies of XML and RDF, and RDFS, to have more expressive power. And it gives me the ability to encode terms in a precise language where I can count on the semantics."

Monday, January 17, 2005

Optional Support in Rasqal

Rasqal 0.9.5 - SPARQL optionals "The one feature I particularly wanted to get out was optionals. These are pretty handy when you have a somewhat unknown graph that you are querying, which could have some useful triples, ahem, optionally. So rather than do lots of queries of the form "do you have triple (?x prop1 ?y) ?" and "do you have triple (?x prop2 ?z)?" they can be just attached to the other triples in the graph pattern, marked optional, and only if they match you get a binding, otherwise, the query carries on. This is all properly explained in the Including Optional Values section of the SPARQL query draft."

This (well something like it although different in a mathematical way) has been a long standing RFE in Kowari too.

18 millions users of RDF

Of course, it's not modern RDF but RDF 1999, still eighteen million firefox 1.0 downloads where everyone can use things like the Mozilla Amazon Browser.

An upgraded version of RDF support maybe on the cards with XUL Templates - Next Steps: "OK, I think it's time to finally improve XUL templates. There have been numerous proposals out there about how to to do it, but no one can really agree on what the best approach is. There is generally consensus that there needs to be support for XML data as well as RDF, and/or other data formats. What there isn't consensus on is what the templates will look like and whether to use a different template mechanism for different kinds of data. Unfortunately, like most of Mozilla, no one is in charge of things, so while lots of ideas float around, nothing actually gets done...I'm hoping that by implementing it incremently we can see better templates sooner rather than later. In fact, I've already implemented one new feature for RDF based generation which will appear in the Linspire version of Nvu."

Points to XUL Templates on the Mozilla Wiki.

Nvu is a Frontpage/Dreamweaver like program for Linux, OS X and Windows.

Beautiful Evidence of a Spotless Presentation

Corrupt Techniques in Evidence Presentations: New Chapter from Beautiful Evidence " Here is the first of several chapters on consuming presentations, on what alert members of an audience or readers of a report should look for in assessing the credibility of the presenter. Most of Beautiful Evidence is about helpful techniques in evidence presentations; these 3 or 4 chapters, however, will describe sources of corruption."

There's also a poster demonstrating Stalin's use of PowerPoint, Gantt Charts (a particular niggle of mine) or the Pioneer message we should've sent.

Stories

Seat Belts "Anti-seat belt law advocate is killed in automobile accident...In this vein, we note with a sense of both sadness and irony a couple of articles recently called to our attention. The first is a 17 September 2004 editorial published in the Daily Nebraskan and entitled "Individual Rights Buckle Under Seat Belt Laws," by Derek Kieper, a 21-year-old senior at the University of Nebraska-Lincoln, in which the writer inveighed against mandatory seat belt laws, opining that "Uncle Sam is not here to regulate every facet of life no matter the consequences," and that "Democrats and Republicans alike should stand together to stop these laws that are incongruous with the ideals of both parties."...an article in the 4 January 2005 Lincoln Journal Star reported that Mr. Kieper not only died in a car crash, but the tragic mishap that claimed his life was the very type of accident in which seat belts have proved so effective in saving lives — preventing passengers from being ejected from vehicles..."

Saturday, January 15, 2005

SPARQL Protocol

SPARQL Protocol for RDF "This is a first Public Working Draft of the SPARQL protocol produced by the RDF Data Access Working Group, (part of the Semantic Web Activity) for review by W3C Members and other interested parties. It reflects the best effort of the editors to reflect implementation experience and incorporate input from various members of the WG, but is not yet endorsed by the WG as a whole."

Includes HTTP bindings.

Working Over Google

Four more updates to the recent Always On article:

Now on Slashdot "A research group at University of Maryland has published a blog describing the latest approach for finding and indexing Semantic Web Documents. They have published it in reaction to Peter Norvig's (director of search quality at Google) view on the Semantic Web..."

On finding semantic web documents. About who was looking for Semantic Web documents. "As of this writing, I'd guess there are at least two million SWDs accessible on the web. Most of these are FOAF or RSS documents...There are lots of other uses of RDF content: embedded RDF in HTML documents, in other document types (e.g., PDF, JPG), in databases, etc."

It'd be valid to say "the Semantic Web is 40 million triples" or something if you had to rely on everything being RDF to be useful. But things like MP3, file systems, SQL databases etc. can all be viewed as RDF - without conversion, on the fly conversion or whatever. Somethings maybe viewed as RDF but never stored as RDF.

Semantic Web: A different perspective on what works and what doesn't

"More importantly, the promise of Semantic Web is closely tied to having the tools for semantic annotations of heterogeneous content, i.e., create semantic metadata automatically. This is much easier to do when you have high quality domain ontologies that bound the scope of automatic extraction."

"Commercial technologies (example) can process millions of pages per day and extract semantic metadata, and all these can be represented as RDF (and that is a good idea because of the benefits esp. for high end semantic applications such as analytics)."

"These types of ontologies routinely have millions of instances (look at SWETO, NCI ontology, GlycO..."

What also works... (which I did a triple take - I thought Danny was linking to some new Semantic Web blog). Talks about how the Semantic Web and LSI are helpful but not tied to one another and points to Semantic Web != Text Analysis; Semantic Web != Controlled Vocabularies.

A New Startup

Bill Coleman Just Can't Stay Retired "Three years ago, it sounded as though William Coleman was planning on kicking back and enjoying his retirement. The co-founder of Internet software maker BEA Systems (BEAS ) had plans to spend time with his wife, do some skiing near his second home in Aspen, Colo., and work on fund-raising for the Coleman Center...With more than $50 million in venture funding and 115 employees, he's aiming to recreate the magic of his early days at BEA...It was like starting BEA. I have a philosophy that if you want to build mission-critical software, if you don't bring in a team that has been together for at least five years, you're not going to get it right.

At BEA, we bought the Tuxedo product line and WebLogic. You're buying a team, buying a competence. When we started this, [we looked at] this company called Unlimited Scale.... These guys had been with Cray [Computers] (CRAY ) for at least 20 years and started a stand-alone company in 2000. Basically, they broke the scale problem. So I bought that company. "

Presentation, RDF Style

Xenon: An RDF Stylesheet Ontology "In this paper we...describe a more general mechanism for enabling heterogeneous composition for user agents. We term this mechanism a “stylesheet ontology” in analogy to the use of stylesheets on the Web and for XML as a way to abstract presentation from content. If we assume that stylesheets were deemed useful in the HTML and XML contexts, we claim that RDF possesses an even stronger need for stylesheets. HTML (and to some degree XML as well, when the schema in play is simple) is designed to yield human-readable content in a browser, whereas datasets that utilize the expressive power of RDF are rarely human-readable regardless of the syntax used."

"The Xenon stylesheet language is specified as an RDF ontology. In other words, the role the abstract syntax tree (AST) usually plays in functional languages such as XSLT or Lisp is played by an RDF fragment...By representing an AST in RDF, we have therefore drawn a correspondence between the terms “language” and “ontology”: a Xenon stylesheet is RDF written with respect to the Xenon ontology."

"The Xenon ontology provides a generic framework for describing how a resource may be transformed into a presentation as well as a template matching system for supporting heterogeneous composition."

"Because templates use RDF Schema to describe their parameters, both “code” and “data” have the same form and differ only by the complexity of the domain they are describing."

Update: Some browsers have a trouble with the above link. If you use "Save As" and open it with a PDF reader then it seems to work fine, rather than relying on the browser plugin.

Thursday, January 13, 2005

Oligopsonistic

Semantic Web Oligopsonies "Aren’t search engines and browsers in a sense oligopolistic (actually oligopsonistic) consumers of web content? There are only a few of each that matter anyway.

Barring interest from Google, Microsoft, Mozilla, and Yahoo! there may be oligopsonists (or monopsonists who want their standards adopted) in niches that can drive metadata adoption in their niches."

Triple Store Connector

Trippi "Java library providing a consistent, thread-safe access point for updating and querying a triplestore. Similar in spirit to JDBC, but for RDF databases."

Found out about this from a recent kowari-general post. Contains a Kowari implementation, source availabe in CVS. The main class seems to be TriplestoreConnector which gives you access to readers and writers.