Begin the Intro Tour or Advanced Tour.
Jon Udell posts a Flash demo too.
This joins other Wiki technologies like SnipSnap and XWiki.
Friday, October 08, 2004
Web of the Future
Tomorrow's Semantic Web: Understanding What We Mean "We're moving to a web where I know what was meant instead of I know what was input, where the web can understand the meaning of the terms on the page instead of just the text size and color that it should present those words in. It knows a little bit about the user background. We're facilitating interoperability so you don't have to have all these stand-alone applications that don't understand each other. The web is moving to be programmable by normal people instead of just geeks like me."
"Analyses from Gartner and Forrester say that expectation citing is critical for applications. And one of the ways you can do that is exposing the top levels of your hierarchy about what your site covers. You also see things like umbrella upper-level structures; I gave an example of the UNSPSC, which provides the top five layers for business-to-business ontologies. They don't really expect to have enough information for any one application in the business space to function, but they say if you're going to do B2B applications, come use our top levels of integration terms so that if you're using a certain kind of widget, we know where that fits in our hierarchy."
The Semantic Web "Although search engine services will still play a big role in locating information for people across the Web, the foundations set by the Semantic Web will lower the entry barrier for applications to utilize a wide array of software agents for the purposes of information retrieval and mining."
"Analyses from Gartner and Forrester say that expectation citing is critical for applications. And one of the ways you can do that is exposing the top levels of your hierarchy about what your site covers. You also see things like umbrella upper-level structures; I gave an example of the UNSPSC, which provides the top five layers for business-to-business ontologies. They don't really expect to have enough information for any one application in the business space to function, but they say if you're going to do B2B applications, come use our top levels of integration terms so that if you're using a certain kind of widget, we know where that fits in our hierarchy."
The Semantic Web "Although search engine services will still play a big role in locating information for people across the Web, the foundations set by the Semantic Web will lower the entry barrier for applications to utilize a wide array of software agents for the purposes of information retrieval and mining."
Thursday, October 07, 2004
1.5's Executor
Put JDK 1.5's Executor to Work for You "The new java.util.concurrent package that is part of JDK 1.5 (Tiger) contains a host of concurrency utilities that are designed to make developing concurrent applications easier. The package provides the Executor framework, which is a collection of classes for managing asynchronous task execution. One way to execute a task asynchronously is to simply fire off a new thread:
new Thread(aRunnable).start();
While this approach is convenient, it has a number of serious drawbacks. Thread creation on some platforms is relatively expensive, and starting a new thread for each task could limit throughput. Even if thread creation were free, in a server application, or any application that will likely be executing many asynchronous tasks, there is no way to bind the number of threads created. This situation can cause the application to crash with OutOfMemoryException, or perform poorly because of resource exhaustion. A stable server application needs a policy to govern how many requests it can be processing at once. A thread pool is an ideal way to manage the number of tasks executing concurrently.
The Executor framework simplifies the management of asynchronous tasks and decouples task submission and management from task execution. The various implementations of Executor in java.util.concurrent can support thread-per-task execution, a single background thread for executing tasks, or thread pooling (and it would even be possible to write an Executor that executes the Runnable in another Java Virtual Machine). It can provide for execution policies such as before-execution and after-execution hooks, saturation policies, queuing policies, and so on."
There's a 1.4 backport of the concurrent library available. The CopyOnWriteArrayList and ConcurrentHashMap would be useful for JRDF. A more general article on the new 1.5 features is online as well.
new Thread(aRunnable).start();
While this approach is convenient, it has a number of serious drawbacks. Thread creation on some platforms is relatively expensive, and starting a new thread for each task could limit throughput. Even if thread creation were free, in a server application, or any application that will likely be executing many asynchronous tasks, there is no way to bind the number of threads created. This situation can cause the application to crash with OutOfMemoryException, or perform poorly because of resource exhaustion. A stable server application needs a policy to govern how many requests it can be processing at once. A thread pool is an ideal way to manage the number of tasks executing concurrently.
The Executor framework simplifies the management of asynchronous tasks and decouples task submission and management from task execution. The various implementations of Executor in java.util.concurrent can support thread-per-task execution, a single background thread for executing tasks, or thread pooling (and it would even be possible to write an Executor that executes the Runnable in another Java Virtual Machine). It can provide for execution policies such as before-execution and after-execution hooks, saturation policies, queuing policies, and so on."
There's a 1.4 backport of the concurrent library available. The CopyOnWriteArrayList and ConcurrentHashMap would be useful for JRDF. A more general article on the new 1.5 features is online as well.
Medical Metadata
ADL (Archetype Definition Language) is a developing standard that is part of the Open Electronic Health Records site. A screenshot of the archetype editor shows a familiar ontology editor interface.
This looks like it is being converted to OWL by the Mayo Clinic and the University of Manchester.
RE: OWL vs. ADL "We at Mayo are working with OpenEHR to produce a set of Java methods to create Archetypes which can be represented in OWL. These Archetypes are output in the abstract syntax which is loaded into memory as Java objects which are exposed for your use. Then we have a set of routines to output these objects as OWL:rdf, which is the exchange syntax for the semantic web. This output of Archetypes will be linked to higher level models such as the CDA and a terminology model (expressed as an archetype)."
See the previous message in this thread as well.
A paper explaining what archetypes are is available here. From the paper, "In this approach [interoperable knowledge methodology], the single, hard-coded software model has become a small reference object model (ROM), while domain concepts are expressed in a separete formalism and maintained in a concept library. Accordingly, software development can proceed separately from domain modelling.
Since the software is an implementation of the ROM, it has no direct dependency on domain concepts; i.e., if new concept models are introduced, the system does not need to be altered."
Seems similar to ontology based programming or meta-programming.
This looks like it is being converted to OWL by the Mayo Clinic and the University of Manchester.
RE: OWL vs. ADL "We at Mayo are working with OpenEHR to produce a set of Java methods to create Archetypes which can be represented in OWL. These Archetypes are output in the abstract syntax which is loaded into memory as Java objects which are exposed for your use. Then we have a set of routines to output these objects as OWL:rdf, which is the exchange syntax for the semantic web. This output of Archetypes will be linked to higher level models such as the CDA and a terminology model (expressed as an archetype)."
See the previous message in this thread as well.
A paper explaining what archetypes are is available here. From the paper, "In this approach [interoperable knowledge methodology], the single, hard-coded software model has become a small reference object model (ROM), while domain concepts are expressed in a separete formalism and maintained in a concept library. Accordingly, software development can proceed separately from domain modelling.
Since the software is an implementation of the ROM, it has no direct dependency on domain concepts; i.e., if new concept models are introduced, the system does not need to be altered."
Seems similar to ontology based programming or meta-programming.
Wednesday, October 06, 2004
Kowari 1.0.5 Released
From the release notes:
* iTQL now supports the having clause, exclude constraints, repeated variables in a where constraint, improved subqueries and empty select clauses:
o The having clause allows restrictions to be placed on aggregate functions, such as count.
o exclude imposes a logically opposite match on the graph to normal constraints.
o Repeated variables in the where clause allow, for example, the ability to find statements with the same subject and object values.
o Subqueries now support the use of trans, walk and exclude.
o An empty select clause returns true if the items in the where clause exist in the given graph.
* The existing string pool was rewritten to allow support to add new hard-coded datatypes. The caching was also moved closer to the string pool implementation, increasing load speed by up to 50%.
* Complete rewrite of the Jena support layer. Multiple Jena models/graphs can be created and accessed independently on multiple machines. Fastpath support allows RDQL queries to make use of Kowari's native query handling. A client/server API is added allowing client access to a Jena Model or Graph backed by Kowari. There are also bugs fixes and further enhancements to performance, such as reading RDF files.
* Enhanced JRDF support including a client/server interface, similar to Jena's. A new OWL API, called SOFA is also available. This can operate on any JRDF compliant implementation. Currently this can be in-memory or Kowari.
* N3 file support for importing and exporting of models.
* Improved RMI support including the ability to load or save data from a client to a remote server or from a remote server to a client.
It's been a long time between releases. A Kowari 1.1 preview release should be along next, followed by a Kowari 1.0.6 release.
* iTQL now supports the having clause, exclude constraints, repeated variables in a where constraint, improved subqueries and empty select clauses:
o The having clause allows restrictions to be placed on aggregate functions, such as count.
o exclude imposes a logically opposite match on the graph to normal constraints.
o Repeated variables in the where clause allow, for example, the ability to find statements with the same subject and object values.
o Subqueries now support the use of trans, walk and exclude.
o An empty select clause returns true if the items in the where clause exist in the given graph.
* The existing string pool was rewritten to allow support to add new hard-coded datatypes. The caching was also moved closer to the string pool implementation, increasing load speed by up to 50%.
* Complete rewrite of the Jena support layer. Multiple Jena models/graphs can be created and accessed independently on multiple machines. Fastpath support allows RDQL queries to make use of Kowari's native query handling. A client/server API is added allowing client access to a Jena Model or Graph backed by Kowari. There are also bugs fixes and further enhancements to performance, such as reading RDF files.
* Enhanced JRDF support including a client/server interface, similar to Jena's. A new OWL API, called SOFA is also available. This can operate on any JRDF compliant implementation. Currently this can be in-memory or Kowari.
* N3 file support for importing and exporting of models.
* Improved RMI support including the ability to load or save data from a client to a remote server or from a remote server to a client.
It's been a long time between releases. A Kowari 1.1 preview release should be along next, followed by a Kowari 1.0.6 release.
Sunday, October 03, 2004
Visualizing Online Social Network
Vizster "Vizster is an interactive visualization tool for online social networks, allowing exploration of the community structure of social networking services such as friendster.com [4], tribe.net [12], and orkut [10]. Such services provide means by which users can publicly articulate their mutual "friendship" in the form of friendship links, forming an undirected graph in which users are the nodes and friendship links are the edges. These services also allow users to describe themselves in a profile, including attributes such as age, marital status, sexual orientation, and various interests."
Built on prefuse.
Built on prefuse.
Saturday, October 02, 2004
Quick Complement of Links
* RIO 1.0 "Rio 1.0 is the first seperate release that supports the Terse RDF Triple Language, or Turtle, format"
* Tim Berners-Lee: Weaving a Semantic Web "The MIT Technology Review Emerging Technologies conference opened today with a keynote by Tim Berners-Lee, inventor of the World Wide Web. Promising “a one-hour talk in 30 minutes,” Berners-Lee gave an animated, rapid-fire presentation -- more like a 90-minute talk in 30 minutes -- about the Semantic Web, his latest initiative."
* Semantic Web: Funding Nascent Democracy "Semantic web enthusiasts, here's your chance! For just US$1000 a pop, you can be the proud owner of fo.af or lo.af!"
* Metadata "Metadata switch: thinking about some metadata management and knowledge organization issues in the changing research and learning landscape "
* Tim Berners-Lee: Weaving a Semantic Web "The MIT Technology Review Emerging Technologies conference opened today with a keynote by Tim Berners-Lee, inventor of the World Wide Web. Promising “a one-hour talk in 30 minutes,” Berners-Lee gave an animated, rapid-fire presentation -- more like a 90-minute talk in 30 minutes -- about the Semantic Web, his latest initiative."
* Semantic Web: Funding Nascent Democracy "Semantic web enthusiasts, here's your chance! For just US$1000 a pop, you can be the proud owner of fo.af or lo.af!"
* Metadata "Metadata switch: thinking about some metadata management and knowledge organization issues in the changing research and learning landscape "
Thursday, September 30, 2004
DAWG query language has a name
SPARQL - A Query Language for RDF from the latest DAWG minutes. Even has a Simpsons reference and possible logo, Mr Sparkle.
Kendall Clark has some ideas about whether FROM is necessary in "Re: [Fwd: FROM keyword unnecessary?]". I wish I had time to consider this more fully.
Kendall Clark has some ideas about whether FROM is necessary in "Re: [Fwd: FROM keyword unnecessary?]". I wish I had time to consider this more fully.
RDF's Rainbow
RDF Gravity (RDF Graph Visualization Tool) "RDF Gravity is a tool for visualising RDF/OWL Graphs/ ontologies. Its main features are:
* Graph Visualization
* Global and Local Filters (enabling specific views on a graph)
* Full text Search
* Generating views from RDQL Queries
* Visualising multiple RDF files"
It uses Jena and Jung.
* Graph Visualization
* Global and Local Filters (enabling specific views on a graph)
* Full text Search
* Generating views from RDQL Queries
* Visualising multiple RDF files"
It uses Jena and Jung.
Wednesday, September 29, 2004
One Persistance Framework?
Sun Proposes Single Persistence Model for Java ""Ideally I think a new JSR devoted to transparent persistence would have been more appropriate," Johnson said. "It's odd for EJB3 to be defining a persistence API applicable to J2SE. But overall I think it's promising. Everyone seems to agree that transparent persistence is important, and that POJO persistence is the future. The EJB expert group seems finally to accept that persistence should not be tied to the EJB container. Hopefully from here the focus will be on getting a good technical solution, rather than on politics.""
Good Ontologies and the Semantic Web
Judging the likely Success of an Ontology "The debate about the promised value of the Semantic Web seems to me to be missing a dispassionate examination of the success, or otherwise, of existing ontology based solutions. Clay Shirky is obviously right when he states that a single monolithic ontology will never work. His critics are equally right when they claim the Semantic web will only work if it is a melange of multiple interoperable Ontologies."
"The success or failure of any ontology should be judged primarily by it's ability to support the exchange of operational activity data between agents. This can only be confirmed after the ontology is implemented by assessing how the system performs in the context of use. To reduce the risk of failure in the early stages of specification the various components of the ontology should be assessed individually and collectively in terms of their ability to support required use cases for operational activity data."
From the same blog, Ontology Review 1. The NHS Common Basic Specification. Why top level Ontologies don't work. and Ontology Review 2: The International System of Units (SI). US Resistance to Adoption of the Metric System.
"Building a great ontology is only the first step. Getting people to adopt it is far more challenging. Adoption is not driven by the merits of the new ontology alone. Enforcement is often required. The US will not become metric until congress is prepared to enact enforceable laws that mandate the use of the metric system."
"The success or failure of any ontology should be judged primarily by it's ability to support the exchange of operational activity data between agents. This can only be confirmed after the ontology is implemented by assessing how the system performs in the context of use. To reduce the risk of failure in the early stages of specification the various components of the ontology should be assessed individually and collectively in terms of their ability to support required use cases for operational activity data."
From the same blog, Ontology Review 1. The NHS Common Basic Specification. Why top level Ontologies don't work. and Ontology Review 2: The International System of Units (SI). US Resistance to Adoption of the Metric System.
"Building a great ontology is only the first step. Getting people to adopt it is far more challenging. Adoption is not driven by the merits of the new ontology alone. Enforcement is often required. The US will not become metric until congress is prepared to enact enforceable laws that mandate the use of the metric system."
Bubbling to the top
What the Bubble Got Right Another Paul Graham essay. "So what's the connection between nerds and technology? Roughly that you can't fool mother nature. In technical matters, you have to get the right answers. If your software miscalculates the path of a space probe, you can't finesse your way out of trouble by saying that your code is patriotic, or avant-garde, or any of the other dodges people use in nontechnical fields."
"There does seem to be: that in the coming century, good ideas will count for more. That 26 year olds with good ideas will increasingly have an edge over 50 year olds with powerful connections. That doing good work will matter more than dressing up-- or advertising, which is the same thing for companies. That people will be rewarded a bit more in proportion to the value of what they create.
If so, this is good news indeed. Good ideas always tend to win eventually. The problem is, it can take a very long time."
"There does seem to be: that in the coming century, good ideas will count for more. That 26 year olds with good ideas will increasingly have an edge over 50 year olds with powerful connections. That doing good work will matter more than dressing up-- or advertising, which is the same thing for companies. That people will be rewarded a bit more in proportion to the value of what they create.
If so, this is good news indeed. Good ideas always tend to win eventually. The problem is, it can take a very long time."
Finding things in a non-semantic web
Drowned out by keywords "So here's a case for the semantic web. It's stupidly difficult to search for news of my hometown.
I live in the beautiful city of York, UK. In most search oriented applications I cannot search for my city. Why?
Because "New York" always matches a search for "York", too. Google ameliorates this a little: you can search for "York UK" or "York -New". But most search facilities aren't as good, and quite a few of my local news sources would not consider "UK" a term they should include in their metadata. "
Here's one closer to home, ISWC'04 or "International Symposium on Wearable Computers" not to be confused by ISWC 2004 or "International Semantic Web Conference". We're in trouble when 4 letter acronyms collide.
I live in the beautiful city of York, UK. In most search oriented applications I cannot search for my city. Why?
Because "New York" always matches a search for "York", too. Google ameliorates this a little: you can search for "York UK" or "York -New". But most search facilities aren't as good, and quite a few of my local news sources would not consider "UK" a term they should include in their metadata. "
Here's one closer to home, ISWC'04 or "International Symposium on Wearable Computers" not to be confused by ISWC 2004 or "International Semantic Web Conference". We're in trouble when 4 letter acronyms collide.
Not is no more
The operation still exists but it's now called "exclude". After spending too much time explaining to people how our "not" is not SQL's "not" but another type of "not" that inverts constraint values combined with the implementer occassionally getting confused between the syntax and the semantics, it lead to this new name. "Not" isn't what it used to be but then again maybe it never was.
From what I can tell so far, "exclude" and subqueries will allow you to perform set difference operations, whether it's clear is another problem. Similarly, you can do OPTIONAL queries using only subqueries but once you get to a few layers of subqueries your head explodes. In these cases it's probably better to have syntactic sugar for certain operations - how users express something and what the machinery underneath does to perform it shouldn't be so tightly coupled.
I made a mistake for the allValuesFrom restriction, here's the corrected version:
I also recently read a paper, "OWL Lite- Reasoning with Rules", which clears up the difference between range and allValuesFrom: "[it] takes into account not only the property but also the domain of the statement. For example, you can say that Stefan manages Wolf, and Wolf is of type Student entails that Stefan is of class Advisor." That's also missing from the query but that's an intentional omission. :-)
From what I can tell so far, "exclude" and subqueries will allow you to perform set difference operations, whether it's clear is another problem. Similarly, you can do OPTIONAL queries using only subqueries but once you get to a few layers of subqueries your head explodes. In these cases it's probably better to have syntactic sugar for certain operations - how users express something and what the machinery underneath does to perform it shouldn't be so tightly coupled.
I made a mistake for the allValuesFrom restriction, here's the corrected version:
select $s $p $x subquery (
select $instance $t $x subquery (
select
from <...#testexclude>
where exclude($instance $t $x))
from <...#testexclude>
where $s $p $instance and $t <tucana:#is> <rdf:type>
and exclude($instance $t $x))
from <...#testexclude>
where $r <rdf:type> <owl:Restriction>
and $r <owl:onProperty> $p
and $r <owl:allValuesFrom> $x
and $s $p $o2
order by $s ;
I also recently read a paper, "OWL Lite- Reasoning with Rules", which clears up the difference between range and allValuesFrom: "[it] takes into account not only the property but also the domain of the statement. For example, you can say that Stefan manages Wolf, and Wolf is of type Student entails that Stefan is of class Advisor." That's also missing from the query but that's an intentional omission. :-)
Tuesday, September 28, 2004
Gnowsis Alpha
Available for Download I had to prioritize downloading it or blogging it...
Installing and running it was pretty painless (just running a shell script) and I'm already going through my MP3s - it evens executes iTunes. It's good to see these ideas implemented.
Feature list :
Server Features
* Local RDF Database (Jena Model based)
* Data integration Hub. integrates different Data sources.
* Filesystem adapter
* MP3-ID3 tag adapter (using MP3 Library by Jens Vonderheide)
* Microsoft Outlook adapter
* Mozilla Thunderbird email adapter
* Mozilla Firefox bookmarks adapter
* XML/RPC API
* Java Client API
* full text indexing (using Apache Lucene)
* local webserver for experiments (using Jetty)
Browser Features
* Browse the local Semantic Desktop
* shows related information for any resource
* Manage your projects using ordinary File Folders
* full text search
* Link anything with drag-drop
* annotate photos and persons
Check out the planned features too.
Installing and running it was pretty painless (just running a shell script) and I'm already going through my MP3s - it evens executes iTunes. It's good to see these ideas implemented.
Feature list :
Server Features
* Local RDF Database (Jena Model based)
* Data integration Hub. integrates different Data sources.
* Filesystem adapter
* MP3-ID3 tag adapter (using MP3 Library by Jens Vonderheide)
* Microsoft Outlook adapter
* Mozilla Thunderbird email adapter
* Mozilla Firefox bookmarks adapter
* XML/RPC API
* Java Client API
* full text indexing (using Apache Lucene)
* local webserver for experiments (using Jetty)
Browser Features
* Browse the local Semantic Desktop
* shows related information for any resource
* Manage your projects using ordinary File Folders
* full text search
* Link anything with drag-drop
* annotate photos and persons
Check out the planned features too.
No New Ideas
Paul has blogged (under the title "Graph Data Model") about a book called "Graph Data Model and its Data Language". It explains how you would go about creating a graph based database and query language - it would've saved us some time when writing TKS/Kowari. It even suggests powerful operations you could perform on such a database such as transitive closure.
Semantic Web Services Graphically
ODE SWS "The ODE SWS framework proposes the use of Problem-Solving Methods (PSM) to describe the services at the knowledge level; that is, independently of the language in which the service will be expressed."
"The Unified Problem-solving Method Language (UPML) has been proposed to provide a high-level description of the knowledge components of a PSM:
* Tasks, describe the operation to be solved, defining its input/output roles and the pre/post-conditions that should be verified to execute the task;
* Methods, detail the control of the reasoning process needed to achieve a task, specifying, if required, the decomposition of tasks into their sub-tasks as well as the coordination of the execution of such sub-tasks to obtain the result (operational description);
* Domain models, contain the knowledge of the domain of an application;
* Ontologies, semantically describe the elements used in the definition of tasks and methods (roles), and domain models (objects); and
* Adapters, establish mappings among the other knowledge components of a PSM, enabling the reuse of the components since adapters define the conditions in which the components could be applicable each other."
The manual was convincing enough to give it a try. The main graph UI is UML like, similar to Rational Rose. Written in Java it uses Jena and JGraph. The JAR is self executing but you need Jena and the rest in the classpath for it to work. It also comes with a distribution of Minerva and WebODE.
"The Unified Problem-solving Method Language (UPML) has been proposed to provide a high-level description of the knowledge components of a PSM:
* Tasks, describe the operation to be solved, defining its input/output roles and the pre/post-conditions that should be verified to execute the task;
* Methods, detail the control of the reasoning process needed to achieve a task, specifying, if required, the decomposition of tasks into their sub-tasks as well as the coordination of the execution of such sub-tasks to obtain the result (operational description);
* Domain models, contain the knowledge of the domain of an application;
* Ontologies, semantically describe the elements used in the definition of tasks and methods (roles), and domain models (objects); and
* Adapters, establish mappings among the other knowledge components of a PSM, enabling the reuse of the components since adapters define the conditions in which the components could be applicable each other."
The manual was convincing enough to give it a try. The main graph UI is UML like, similar to Rational Rose. Written in Java it uses Jena and JGraph. The JAR is self executing but you need Jena and the rest in the classpath for it to work. It also comes with a distribution of Minerva and WebODE.
Monday, September 27, 2004
Other links
* Social Networks Connecting people with Information and Each Other "Verity K2 solutions take advantage of social network technology to automatically provide users with personalized discovery features. Through automatic analysis of the way users create, modify, locate and retrieve information, a model of the entire community..."
* Sir Tim Berners-Lee "TR: What kinds of Semantic Web applications are people making for the next phase?
B-L: Exciting things are happening in the life sciences. The big challenges such as cancer, AIDS, and drug discovery for new viruses require the interplay of vast amounts of data from many fields that overlap—genomics, proteomics, epidemiology, and so on. Some of this data is public, some very proprietary to drug companies, and some very private to a patient. The Semantic Web challenge of getting interoperability across these fields is great but has huge potential benefits."
* MG4J (Managing Gigabytes for Java) From a book I found interesting (NZDL is great). "MG4J (Managing Gigabytes for Java) is a collaborative effort aimed at providing a free Java implementation of inverted-index compression techniques; as a by-product, it offers several general-purpose optimised classes, including fast & compact mutable strings, bit-level I/O, fast unsychronised buffered streams, (possibly signed) minimal perfect hashing for very large strings collections, etc."
* Practical RDF Browser "So who’s going to do it? Awk, I wish I had time. Most of the stuff I’ve done previously along visualization lines has been from scratch using Java. But this time, for The Browser I’d go with SVG-enabled Mozilla/Firefox (or even forget the SVG, just make heavy use of CSS for a more graphic layout, or Plan C use XUL). Moz is already riddled with RDF, which should help. Its purpose would be a viewer, so I’d try and avoid having too many dependencies - a full RDF API/triplestore shouldn’t be needed, though being able to handle subclasses/properties would be very desirable, to enable approximate rendering."
* Sir Tim Berners-Lee "TR: What kinds of Semantic Web applications are people making for the next phase?
B-L: Exciting things are happening in the life sciences. The big challenges such as cancer, AIDS, and drug discovery for new viruses require the interplay of vast amounts of data from many fields that overlap—genomics, proteomics, epidemiology, and so on. Some of this data is public, some very proprietary to drug companies, and some very private to a patient. The Semantic Web challenge of getting interoperability across these fields is great but has huge potential benefits."
* MG4J (Managing Gigabytes for Java) From a book I found interesting (NZDL is great). "MG4J (Managing Gigabytes for Java) is a collaborative effort aimed at providing a free Java implementation of inverted-index compression techniques; as a by-product, it offers several general-purpose optimised classes, including fast & compact mutable strings, bit-level I/O, fast unsychronised buffered streams, (possibly signed) minimal perfect hashing for very large strings collections, etc."
* Practical RDF Browser "So who’s going to do it? Awk, I wish I had time. Most of the stuff I’ve done previously along visualization lines has been from scratch using Java. But this time, for The Browser I’d go with SVG-enabled Mozilla/Firefox (or even forget the SVG, just make heavy use of CSS for a more graphic layout, or Plan C use XUL). Moz is already riddled with RDF, which should help. Its purpose would be a viewer, so I’d try and avoid having too many dependencies - a full RDF API/triplestore shouldn’t be needed, though being able to handle subclasses/properties would be very desirable, to enable approximate rendering."
Web Based Ontology Editing
pOWL " * POWL supports viewing, editing of RDFS/OWL ontologies of arbitrary size. It is even quite fast with the largest available models (e.g. NCI Cancer Ontology containing about 28,000 classes).
* Sophisticated widgets for data editing such as widgets for editing HTML in a WYSIWIG manner or for dates are integrated.
* Questioning the knowledge base. pOWL currently offers an RDQL query builder as well as a full-text search for literals and resources.
* Plugin concept. POWL is easy extensible, unfortunately still laking exhaustive documentation on this - please have a look at the source code and pester the developers. :-)
* Powerful object oriented API. All functionality is accessible by a clean application programming interface.
* Authentification scheme. Fine grained exposition of features and model data: Privileges (view, edit) for users and groups are planned to be assigned to Models, Classes and Properties.
* Versioning. All edits of a knowledge base may be logged and rolled back (depending on time, user and edit action).
* POWL is fast. Models are stored in database tables and only those parts of the model are loaded into main memory which are actually needed. Thus POWL is scalable and fast.
* Multi language support. POWL comes with English and German translations of the user interface. If you would like to provide a translation please contact us!"
The live demo is well worth a look.
* Sophisticated widgets for data editing such as widgets for editing HTML in a WYSIWIG manner or for dates are integrated.
* Questioning the knowledge base. pOWL currently offers an RDQL query builder as well as a full-text search for literals and resources.
* Plugin concept. POWL is easy extensible, unfortunately still laking exhaustive documentation on this - please have a look at the source code and pester the developers. :-)
* Powerful object oriented API. All functionality is accessible by a clean application programming interface.
* Authentification scheme. Fine grained exposition of features and model data: Privileges (view, edit) for users and groups are planned to be assigned to Models, Classes and Properties.
* Versioning. All edits of a knowledge base may be logged and rolled back (depending on time, user and edit action).
* POWL is fast. Models are stored in database tables and only those parts of the model are loaded into main memory which are actually needed. Thus POWL is scalable and fast.
* Multi language support. POWL comes with English and German translations of the user interface. If you would like to provide a translation please contact us!"
The live demo is well worth a look.
Saturday, September 25, 2004
Load Speed
Triple Loading "What doesn’t show in the numbers is the fact that the entire load process is CPU bound, it’s not disk accesses that’s taking time. Also, the amount of triples, 473589, isn’t enough to fill up the in-memory cache MySQL maintains (here), not even importing a large dataset like Jim’s 6.7 million scuttered statements (converted into NTriples with jim2ntriples) seems to be. With bulk loading turned on, that entire process takes about 34 minutes, equivalent to about 3300 triples per second, as compared to the about 3000 triples per second for the best case above."
Subscribe to:
Posts (Atom)