Semantische Virtuelle Umgebungen RDF used to describe 3D environments. Presentation slides and paper (in English).
"There are a number of open issues regarding RDF modeling, particularly in the areas of inter-environment linking, coordinate systems, and event design. Other issues concern consistency and security in the presence of multiple channels. These are more grave as we cannot change the underlying protocols, and have to work solely with information already available."
Monday, August 30, 2004
Using Kowari's QueryHandler
I've recently been putting builds of Kowari 1.0.5 onto SF's CVS server. This has lead to some good feedback; after some initial bug fixing. It's focused what to work on and the practical up shot is that you can now do RDQL queries (found in org.kowari.store.jena):
RdqlQuery q = new RdqlQuery("select ?x ?y ?z WHERE (?x ?y ?z)");
q.setSource(model);
QueryExecution qe = new KowariQueryEngine(q);
QueryResults results = qe.exec();
This converts the Jena-based query object to Kowari objects, which are then processed by Kowari's query layer and returned as Jena objects.
The only query that it currently doesn't handle, although it soon will, is repeated variables in the constraint like:
select ?x
where (?x ?x ?x)
There's also recent work on client/server JRDF and Jena, N3 input and output, file upload/download from an iTQL client to/from the server, NOT (unstated) constraint, and other improvements.
RdqlQuery q = new RdqlQuery("select ?x ?y ?z WHERE (?x ?y ?z)");
q.setSource(model);
QueryExecution qe = new KowariQueryEngine(q);
QueryResults results = qe.exec();
This converts the Jena-based query object to Kowari objects, which are then processed by Kowari's query layer and returned as Jena objects.
The only query that it currently doesn't handle, although it soon will, is repeated variables in the constraint like:
select ?x
where (?x ?x ?x)
There's also recent work on client/server JRDF and Jena, N3 input and output, file upload/download from an iTQL client to/from the server, NOT (unstated) constraint, and other improvements.
Sunday, August 29, 2004
Blogging on RDF
Some recent blogs on RDF:
* Template Languages "There's been some discussion lately about how to improve XUL templates...Some proposals include using an SQL-like language which generates results. This is suitable for database-backed data, and a query language for RDF is being developed."
* HyperRDF: Using XHTML Authoring Tools with XSLT to produce RDF Schemas "XML syntax is a little tedious, but lots of people are evidently willing and able of editing it by hand. RDF adds another layer of tedium, but there are still a few folks willing to write it by hand. I make heavy use of reification/quoting in my representation of logical formulas in RDF. This adds another layer of tedium that I find unmanageable..."
* GUMP + RDF "Ok, so I used RDFLIB to allow Gump to generate some RDF"
* Template Languages "There's been some discussion lately about how to improve XUL templates...Some proposals include using an SQL-like language which generates results. This is suitable for database-backed data, and a query language for RDF is being developed."
* HyperRDF: Using XHTML Authoring Tools with XSLT to produce RDF Schemas "XML syntax is a little tedious, but lots of people are evidently willing and able of editing it by hand. RDF adds another layer of tedium, but there are still a few folks willing to write it by hand. I make heavy use of reification/quoting in my representation of logical formulas in RDF. This adds another layer of tedium that I find unmanageable..."
* GUMP + RDF "Ok, so I used RDFLIB to allow Gump to generate some RDF"
Databases for free
The Economics of Software "...doesn't it strike you as odd that your operating system is essentially free, but your database is still costing you forty grand per CPU? Is a database infinitely more difficult to write than an operating system? (Answer: no.) If not, why the enormous pricing discrepancy?"
"The tendency towards open source is especially strong when companies profit not directly from the right-to-use of the software, but rather from some complementary good: support, services, other software, or even hardware...To put this in retail terms, open source software has all of the properties of a loss-leader -- minus the loss, of course."
"Will either of these [MaxDB and Ingres] be able to start taking serious business away from Oracle and IBM?...The economics of software tells us that, in the long run, this is likely the case: either the demand-side will ultimately force sufficient improvements to the existing open source databases, or the supply-side will force the open sourcing of one of the viable competitors."
"The tendency towards open source is especially strong when companies profit not directly from the right-to-use of the software, but rather from some complementary good: support, services, other software, or even hardware...To put this in retail terms, open source software has all of the properties of a loss-leader -- minus the loss, of course."
"Will either of these [MaxDB and Ingres] be able to start taking serious business away from Oracle and IBM?...The economics of software tells us that, in the long run, this is likely the case: either the demand-side will ultimately force sufficient improvements to the existing open source databases, or the supply-side will force the open sourcing of one of the viable competitors."
The Pillars of Longhorn Crumbling?
There used to be three pillars. With the news of WinFS being dropped there's now two.
The WinFS datamodel had a lot going for it, in as much as its similarity to RDF. Cairo's promise still seems a way off. Metadata in the file system continues its tortious path.
The WinFS datamodel had a lot going for it, in as much as its similarity to RDF. Cairo's promise still seems a way off. Metadata in the file system continues its tortious path.
Friday, August 27, 2004
Infoculturists
Collaborative knowledge gardening "Conventional wisdom holds that people will never assign metadata tags to content. It just isn’t on the path of least resistance, the story goes, and those few who do step off the path succeed only in creating unwieldy taxonomies. (Do you file the revised XML Schema specification under xml/specifications or specifications/xml? We can never agree, and many good minds are sacrificed in the vain attempt.) Yet somehow, users of Flickr and del.icio.us do routinely tag content, and those tags open new dimensions of navigation and search. It’s worth pondering how and why this works.
Abandoning taxonomy is the first ingredient of success. These systems just use bags of keywords that draw from — and extend — a flat namespace. In other words, you tag an item with a list of existing and/or new keywords. Of course, that idea’s been around for decades, so what’s special about Flickr and del.icio.us? Sometimes a difference in degree becomes a difference in kind. The degree to which these systems bind the assignment of tags to their use — in a tight feedback loop — is that kind of difference."
"The success of Flickr and del.icio.us won’t necessarily translate to the intranet. You can import the global-hive mind, but you can’t export the local-hive mind. That asymmetry defines the challenge we face as enterprise knowledge gardeners."
Abandoning taxonomy is the first ingredient of success. These systems just use bags of keywords that draw from — and extend — a flat namespace. In other words, you tag an item with a list of existing and/or new keywords. Of course, that idea’s been around for decades, so what’s special about Flickr and del.icio.us? Sometimes a difference in degree becomes a difference in kind. The degree to which these systems bind the assignment of tags to their use — in a tight feedback loop — is that kind of difference."
"The success of Flickr and del.icio.us won’t necessarily translate to the intranet. You can import the global-hive mind, but you can’t export the local-hive mind. That asymmetry defines the challenge we face as enterprise knowledge gardeners."
Semantic Web Tutorials
Tom has asked me to link to the SWBP&D WG Semantic Web Tutorials "This page provides a central collection of Semantic Web tutorial resources for interested readers and is maintained by the Semantic Web Best Practices and Deployment Working Group."
Specifically, he's after more good tutorials.
Specifically, he's after more good tutorials.
Ringfencing
I've linked to The Missing Webs before, here's another good quote:
"A big decision is whether the world model should be open or closed. If closed, we're in effect saying our system knows all it needs to know. If open, what's not specified is unknown. The real world is full of unknowns, but this does not sit altogether comfortably alongside the closed world of traditional relational DBs or the negation by failure of Prolog. A key aspect of the Semantic Web vision is the open world assumption...This doesn't throw out the possibility of using closed-world reasoning on Semantic Web data, as a locally closed world can be defined if required, by harvesting or ringfencing the statements of interest. But conversely filling a relational database with nulls will hamper its capabilities, and query responses can be a more accurate "don't know” rather than a rigid "false”."
"A big decision is whether the world model should be open or closed. If closed, we're in effect saying our system knows all it needs to know. If open, what's not specified is unknown. The real world is full of unknowns, but this does not sit altogether comfortably alongside the closed world of traditional relational DBs or the negation by failure of Prolog. A key aspect of the Semantic Web vision is the open world assumption...This doesn't throw out the possibility of using closed-world reasoning on Semantic Web data, as a locally closed world can be defined if required, by harvesting or ringfencing the statements of interest. But conversely filling a relational database with nulls will hamper its capabilities, and query responses can be a more accurate "don't know” rather than a rigid "false”."
Typed Literals and Language
RDF literals: "Plain literals have a lexical form and optionally a language tag as defined by [RFC-3066], normalized to lowercase.
Typed literals have a lexical form and a datatype URI being an RDF URI reference."
Why isn't xml:lang information represented within the RDF data model? "The WG subsequently resolved that typed literals would not have a language tag."
Interpretation properties "...they express the relationship between one value and that value interpreted (or processed in the imagination) in a specific way."
Fwd: Typed literals in RDF: "On Friday RDF Core changed the definition of a literal, so that a literal can be one of the following:
A lexical form
A lexical form paired with a language tag
A lexical form paired with a datatype URI"
This is old news (over a year).
Typed literals have a lexical form and a datatype URI being an RDF URI reference."
Why isn't xml:lang information represented within the RDF data model? "The WG subsequently resolved that typed literals would not have a language tag."
Interpretation properties "...they express the relationship between one value and that value interpreted (or processed in the imagination) in a specific way."
Fwd: Typed literals in RDF: "On Friday RDF Core changed the definition of a literal, so that a literal can be one of the following:
A lexical form
A lexical form paired with a language tag
A lexical form paired with a datatype URI"
This is old news (over a year).
Thursday, August 26, 2004
Findability on the Cheap
The Low-Cost Cure For 'Bad Search' "The answer, we're told, is either a massive taxonomy and classification initiative, a six-figure investment in a new search engine or the next release of the Windows operating system."
"Good foldering and file-naming practices focus on subject or function (rather than owner/author, creation/edit dates or other values available as metadata). Names should be consistent and concise (with eight or fewer characters) for easy navigation. Avoid repeating information available at a higher or lower level of the hierarchy (you don't need to use "contract" in the file name, for example, if it's in a "Contracts" folder)."
"Better search engines, classification tools and taxonomies have their place — particularly in large organizations that have been through mergers and reorganizations. But don't let big investments become a Band-Aid for poor training and a lack of best practices. With $31 billion in productivity at stake, an ounce of prevention is worth a lot of money. E-mail your best tips, practices and horror stories, and we'll publish the standouts in an upcoming issue."
"Good foldering and file-naming practices focus on subject or function (rather than owner/author, creation/edit dates or other values available as metadata). Names should be consistent and concise (with eight or fewer characters) for easy navigation. Avoid repeating information available at a higher or lower level of the hierarchy (you don't need to use "contract" in the file name, for example, if it's in a "Contracts" folder)."
"Better search engines, classification tools and taxonomies have their place — particularly in large organizations that have been through mergers and reorganizations. But don't let big investments become a Band-Aid for poor training and a lack of best practices. With $31 billion in productivity at stake, an ounce of prevention is worth a lot of money. E-mail your best tips, practices and horror stories, and we'll publish the standouts in an upcoming issue."
Urchin-Kowari project
ADTF: Urchin-Kowari "The Urchin-Kowari project replaces the mySQL database with the specialized RDF triple store Kowari. This takes advantage of the fact that all data in Urchin are RDF statements and Kowari is a specialized RDF database. Urchin and Kowari communicate via SOAP, and can be running on different machines. This decoupling of interface and storage allows users the freedom to access any available Kowari server on the Web. In Urchin-Kowari, the core Urchin functionalities are preserved as much as possible. The Web interface retains its look, but query syntax has been modified. Raw iTQL queries to the storage replace the RCQL queries. Many Urchin keywords are being developed. Administrative control of the channels is also preserved."
I don't want to get into one of these GNU/Linux type debates but surely it should be Kowari-Urchin. :-)
I don't want to get into one of these GNU/Linux type debates but surely it should be Kowari-Urchin. :-)
Tuesday, August 24, 2004
RDF Defined
Eric Jain defines RDF using Wikipedia's RDF definition: "Those close [...] become passionately committed to possibly insane projects, without regard to the practicality of the implementation or competitive forces in the marketplace."
Also, the Wikipedia definition of Resource Description Framework:
"A collection of RDF statements represents a labeled oriented pseudograph. As such, an RDF-based data model is more naturally suited to certain kinds of knowledge representation than the relational model and other ontological models traditionally used in computing today, although RDF data is often stored in relational databases, and as OWL demonstrates, ontologies can be built upon RDF."
And a pseudograph has: "...both multiple edges and loops. When stated without any qualification, a graph is almost always assumed to be simple."
Also, the Wikipedia definition of Resource Description Framework:
"A collection of RDF statements represents a labeled oriented pseudograph. As such, an RDF-based data model is more naturally suited to certain kinds of knowledge representation than the relational model and other ontological models traditionally used in computing today, although RDF data is often stored in relational databases, and as OWL demonstrates, ontologies can be built upon RDF."
And a pseudograph has: "...both multiple edges and loops. When stated without any qualification, a graph is almost always assumed to be simple."
If you really read it just for the articles
While searching the SEC for smut I found that the SEC has the Google Playboy interview. This has other interesting details like Google's position in the market, details on AdSense, etc. And the mission statement: "...our fundamental goal is to connect people to relevant information and conversely to connect that relevant information to the people who need it."
Java + SW = Jena
How Big Is Your Store? "The repository will end up holding metadata about more than 16 million articles (plus their associated authors, affiliations, publications, etc) and as you'd imagine thats going to end up exploding into a large number of triples."
"I'd be interested to hear about how big a store people have worked with, including which APIs, etc they've been using.
To give a bit more context, as we're mainly a Java shop I've begun by considering any store that can be plugged into Jena. So the Jena persistence model support would be my baseline, with Kowari being another candidate. I see that RDFStore may be adding Jena support so we may explore that too."
16 million triples shouldn't be a problem for many stores.
I find that Jena does impose some limitations on scalability in that it tends to want to use in memory Models for a lot of things. It also tends to over use iterators. It's also a terribly complicated thing for something, RDF, that is quite simple.
I've been recently thinking that JRDF, Sesame's RIO, Kowari store and SOFA for OWL inferencing would make a small, scalable solution (around 5MB). Is anyone interested in that though?
"I'd be interested to hear about how big a store people have worked with, including which APIs, etc they've been using.
To give a bit more context, as we're mainly a Java shop I've begun by considering any store that can be plugged into Jena. So the Jena persistence model support would be my baseline, with Kowari being another candidate. I see that RDFStore may be adding Jena support so we may explore that too."
16 million triples shouldn't be a problem for many stores.
I find that Jena does impose some limitations on scalability in that it tends to want to use in memory Models for a lot of things. It also tends to over use iterators. It's also a terribly complicated thing for something, RDF, that is quite simple.
I've been recently thinking that JRDF, Sesame's RIO, Kowari store and SOFA for OWL inferencing would make a small, scalable solution (around 5MB). Is anyone interested in that though?
Monday, August 23, 2004
Java vs Perl
Java Regex Wrangling "So then I ran it again without the output, just counting the tokens, and yowie zowie, Perl was at 8 minutes 47 seconds, Java back at 3 minutes 4 seconds. So I re-ran on a nearby Debian box, on the theory that the OS X versions of Java and Perl might not be representative of their kind. There are all sorts of variations around I/O and so on, but my finding is that for this problem, the Java 1.4.2 regex processing is somewhere around twice as fast as Perl 5.8.1. Frankly, I’m astounded."
I wrote up a JavaOne presentation on this in 2001. While I couldn't go and it wasn't presented this is pretty much what I found too.
I wrote up a JavaOne presentation on this in 2001. While I couldn't go and it wasn't presented this is pretty much what I found too.
The best of REST
Implementing REST Web Services: Best Practices and Guidelines " The architecture represented above has a pipe-and-filter style, a classical and robust architectural style used as early as in 1944 by the famous physicist, Richard Feynman, to build the first atomic bomb in his computing team. A request is processed by a chain of filters and each filter is responsible for a well-defined unit of work. Those filters are further classified as two distinct groups: front-end and back-end. Front-end filters are responsible to handle common Web service tasks and they must be light weight. Before or at the end of front-end filters, a response is returned to the invoking client...Most notably, the filters can be considered as a standard form of computing and new filters can be added or extended from existing ones easily. This architecture has good user-perceived performance because responses are returned as soon as possible once a request becomes fully processed by lightweight filters. This architecture also has good security and stability because security breakage and errors can only propagate a limited number of filters."
Web Services: REST in Peace? "The advantages of conceptualising an application in terms of services and messages, rather than in terms of APIs (either RESTful or RPC oriented varieties) are clear: it enables super-loose coupling both for composing services into applications and in the implementation of a service itself."
Web Services: REST in Peace? "The advantages of conceptualising an application in terms of services and messages, rather than in terms of APIs (either RESTful or RPC oriented varieties) are clear: it enables super-loose coupling both for composing services into applications and in the implementation of a service itself."
Ontaria
"Ontaria is a searchable and browsable directory of semantic web data. Our focus is RDF vocabularies with OWL ontologies, but all the RDF data we index is visible. The site is primarily intended for people creating RDF content who want to better understand which vocabularies are available and how they are being used. Beyond this, Ontaria may be useful for finding and exploring arbitrary RDF content."
Current Database: Last Updated: 29 April, Triples: 18172, Sources: 70.
Current Database: Last Updated: 29 April, Triples: 18172, Sources: 70.
Friday, August 20, 2004
Radio RDF
RDF Radio "So what's RDF Radio? Mostly vapour right now, but it's a concept Matt Croydon and I have been tossing around for a few weeks. The basic ideas of which are a little similar to Nokia's much touted but equally vapourous Visual Radio.
The main tenet of both is to provide some additional metadata about an existing "Radio" audio stream on a side channel. Visual Radio appears to be quite tightly constrained around proving visual (wap/html based?) user oriented information over GPRS as an adjunct to FM radio. RDF Radio on the other hand is intended to provide timely pure RDF/XML metadata that supplements any broadcast stream; FM, AM, webcast and much more."
The main tenet of both is to provide some additional metadata about an existing "Radio" audio stream on a side channel. Visual Radio appears to be quite tightly constrained around proving visual (wap/html based?) user oriented information over GPRS as an adjunct to FM radio. RDF Radio on the other hand is intended to provide timely pure RDF/XML metadata that supplements any broadcast stream; FM, AM, webcast and much more."
Resting on SOFA
I've recently been part of taking a closer look at SOFA (I haven't been doing most of the work though). Initially, it looks too good to be true, OWL in 5 classes. Surely it can't be that easy? It's basically an object model for OWL and RDFS. It includes: Concept, Ontology, Relation, Restriction and Thing. A Concept represents a classification item (class) and a Thing represents a knowledge item (instance). Relations are transitive, symmetric or an inversion. Restrictions are by cardinality or value. It can read and write both OWL and RDFS.
Other features:
* Provides inferencing.
* Support for Java types. This includes mapping to 10 Java datatypes, like String to xsd:string. Other Java objects are base64 encoded - which is a strange feature but kind of cool.
* Events and event listeners (when Things are added, removed or modified).
* Uses URI objects.
* Supports checked exceptions and throws them when you do something wrong.
* Interfaces all the way through.
* DOTWriter which represents an ontology as a directed graph described by Graphviz DOT language syntax.
* Unit tests.
Because it is so small it should be fairly easy to integrate into other stores and APIs.
More information is available here.
Other features:
* Provides inferencing.
* Support for Java types. This includes mapping to 10 Java datatypes, like String to xsd:string. Other Java objects are base64 encoded - which is a strange feature but kind of cool.
* Events and event listeners (when Things are added, removed or modified).
* Uses URI objects.
* Supports checked exceptions and throws them when you do something wrong.
* Interfaces all the way through.
* DOTWriter which represents an ontology as a directed graph described by Graphviz DOT language syntax.
* Unit tests.
Because it is so small it should be fairly easy to integrate into other stores and APIs.
More information is available here.
RDFStore 0.5
"RDFStore version 0.50 has been released and available on CPAN. This is major release of the toolkit after 3 years - most of the code has been re-written in pure ANSI C and a new native indexing model for RDF has been built in. Several RDF based shallow Semantic Web applications has been successfully built using the toolkit from Asemantics S.r.l and its partners."
"Future developments will include support for upcoming DAWG/BRQL query language, pure C query interface, ODBC and JDBC APIs. Together with a Jena / Java and PHP front-ends."
Available for download.
From the CHANGE LOG: "A brand new indexing model for RDF data has been developed in this release - such a indexing model allows to store quite efficienty "pedantic" RDF descriptions by leveraging on compression of the index of triples using a custom RLE+VLE compression algorithm written in C and XS. It is under investigation the real need to have a custom compression algorithm for RDFStore instead of using one in the public domain; some tests showed that general purpose algorithms like LZO or LZF perfom worse in the specific case of RDFStore where the sparse matrix contains well-known patterns."
"Future developments will include support for upcoming DAWG/BRQL query language, pure C query interface, ODBC and JDBC APIs. Together with a Jena / Java and PHP front-ends."
Available for download.
From the CHANGE LOG: "A brand new indexing model for RDF data has been developed in this release - such a indexing model allows to store quite efficienty "pedantic" RDF descriptions by leveraging on compression of the index of triples using a custom RLE+VLE compression algorithm written in C and XS. It is under investigation the real need to have a custom compression algorithm for RDFStore instead of using one in the public domain; some tests showed that general purpose algorithms like LZO or LZF perfom worse in the specific case of RDFStore where the sparse matrix contains well-known patterns."
Subscribe to:
Posts (Atom)