Friday, April 23, 2004
Metaweb Graph Updated
New Version of My "Metaweb" Graph -- The Future of the Net "Many people have requested this graph and so I am posting my latest version of it. The Metaweb is the coming "intelligent Web" that is evolving from the convergence of the Web, Social Software and the Semantic Web. The Metaweb is starting to emerge as we shift from a Web focused on information to a Web focused on relationships between things --- what I call "The Relationship Web" or the "Relationship Revolution.""
Semaview Interview
What Is The Semantic Web? "The Semantic Web provides the foundation on which we can build more intelligent Internet applications. It will help everyone find, organize, collect, use and share information more easily."
"My company, Semaview has developed an application called eventSherpa. eventSherpa is making it simple to create and organize schedules and share them over the Internet. Our application automatically creates Semantic Web content transparently without the end user knowing it...Aside from reducing the complexity issue...I believe the largest challenge is convincing application developers to make their data available in semantic format. However it is "a chicken and egg problem" -- the more content available in a semantic format, the more applications that will be developed to take advantage of it; and vice versa."
"My company, Semaview has developed an application called eventSherpa. eventSherpa is making it simple to create and organize schedules and share them over the Internet. Our application automatically creates Semantic Web content transparently without the end user knowing it...Aside from reducing the complexity issue...I believe the largest challenge is convincing application developers to make their data available in semantic format. However it is "a chicken and egg problem" -- the more content available in a semantic format, the more applications that will be developed to take advantage of it; and vice versa."
Knobot
Reto was trying to get Kowari going. Hopefully it will get used for this project. Documentation gives download links and installation instructions.
From Danny Ayers: Knobot PlanetRDF Demo.
From Danny Ayers: Knobot PlanetRDF Demo.
XML 2004
The State of XML "As a software developer I feel increasingly unhappy with the development of a monolithic mass of technology building up, only reasonably accessible behind a Java or .NET API. In contrast, the REST model of composed, simple interactions seems more controllable and containable and you can still see the angle brackets in order to check that things are working. There is still plenty of work and experimentation to be done yet with the notion of more document-oriented web services."
"Consequently, even at the low level of operating systems vendors are seeing the need and advantages of implementing metadata storage and manipulation.
This is good. We have the tools to support this, whichever way you swing on the technology issues. RDF & OWL, Topic Maps, W3C XML Schema: all have the right machinery. Unfortunately that's not the biggest issue. The main problem is which terms, schemas, and ontologies to use. That's just not clear right now for most if not all metadata applications. At best, we'll get inconsistently classified information, which defeats the promise of interoperability. More typically, we'll end up with little tagged metadata and islands of de facto proprietary information."
"As an RDF fan, the realization of this truth causes me some pain. The way out is to stop thinking of RDF as an XML application, and look to easier syntaxes such as Turtle and N3."
"Consequently, even at the low level of operating systems vendors are seeing the need and advantages of implementing metadata storage and manipulation.
This is good. We have the tools to support this, whichever way you swing on the technology issues. RDF & OWL, Topic Maps, W3C XML Schema: all have the right machinery. Unfortunately that's not the biggest issue. The main problem is which terms, schemas, and ontologies to use. That's just not clear right now for most if not all metadata applications. At best, we'll get inconsistently classified information, which defeats the promise of interoperability. More typically, we'll end up with little tagged metadata and islands of de facto proprietary information."
"As an RDF fan, the realization of this truth causes me some pain. The way out is to stop thinking of RDF as an XML application, and look to easier syntaxes such as Turtle and N3."
Wednesday, April 21, 2004
Unix Job Ad
Unix Specialist "Ah, Unix. Its cheapass cousin, Linux, is what all Microsoft users turn to just as their sanity reaches a crossroads. Did you know that Microsoft Word stills spellchecks ‘Unix’ as ‘UNIX’? Man, how 80’s does that look? I can imagine something like that flickering on the screen of a computer you assembled yourself from a crystal radio kit."
"But the point of all that is, Unix is basically a sort of secret society where you either know it, or you don’t. And since most people just really can’t be bothered going through the agonies of learning it, it’s why we have jobs like this: “Unix Specialist”. Of course that means nothing, or at least it means about as much as “Car Specialist” or “Bread Specialist”. Bread Specialist? What the hell is that? What kind of bread? White, multigrain, mixed grain, wholemeal, sourdough? Sliced or unsliced? If sliced, sliced for sandwiches or for toast? Crusty or soft? No matter! Just eat your bread!"
"But the point of all that is, Unix is basically a sort of secret society where you either know it, or you don’t. And since most people just really can’t be bothered going through the agonies of learning it, it’s why we have jobs like this: “Unix Specialist”. Of course that means nothing, or at least it means about as much as “Car Specialist” or “Bread Specialist”. Bread Specialist? What the hell is that? What kind of bread? White, multigrain, mixed grain, wholemeal, sourdough? Sliced or unsliced? If sliced, sliced for sandwiches or for toast? Crusty or soft? No matter! Just eat your bread!"
RDF Engine
RDF Engine "The program RDFEngine was developed as a part of the master thesis of Guido Naudts. It was build on the example of Euler, the program of Jos De Roo. The original version was made with Haskell. It was then rewritten in Python. Purpose of the program was to implement a logic program for the Semantic Web initiative. Concerning compatibility the program is meant to be compatible with CWM in the sense that sources that work with CWM will also work with RDFEngine but not vice versa.(I like to do some experiments of my own (-: ). For input and output Notation 3 is used. See also the Notation 3 tutorial."
Tuesday, April 20, 2004
80/20 REST to SOAP
XMLEurope, Monday "The keynotes were by Jeff Barr of Amazon and Steven Pemberton from W3C. Interesting to hear some detail about the Amazon Web Services, including the 80/20 split between developer use of REST and SOAP interfaces to the Amazon catalogue, and the business case for making the catalogue available in machine-processible format: essentially the value is not in their catalogue per se, and they have a business model for third party sellers and affiliates, so WS access just makes this relationship easier. The output example he gave looked to me very close to RDF; with Amazon's XSLT service it could be transformed to it very easily I think."
Monday, April 19, 2004
Phew
Kowari 1.0.2 is now released - much better than the last one. Even available in a bite sized 14MB version. Unfortunately, we didn't get the anonymous node bug in our Jena implementation fixed in time. The next release should be within the next 2-4 weeks depending on the progress of the currently outstanding bugs.
BTW, you can now do things like: "select $s $p $o from <http://www.w3c.org/2000/08/w3c-synd/home.rss> where $s $p $o ;". You can combine local and remote (via file or http) models by using "and" and "or" in the FROM clause.
BTW, you can now do things like: "select $s $p $o from <http://www.w3c.org/2000/08/w3c-synd/home.rss> where $s $p $o ;". You can combine local and remote (via file or http) models by using "and" and "or" in the FROM clause.
Bloom Filters in Social Networks
Building a Bloom Filter in Perl "One drawback of existing social network schemes is that they require participants to either divulge their list of contacts to a central server (Orkut, Friendster) or publish it to the public Internet (FOAF), in both cases sacrificing a great deal of privacy. By exchanging Bloom filters instead of explicit lists of contacts, users can participate in social networking experiments without having to admit to the world who their friends are. A Bloom filter encoding someone's contact information can be checked to see whether it contains a given name or email address, but it can't be coerced into revealing the full list of keys that were used to build it. It's even possible to turn the false-positive rate, which may not sound like a feature, into a powerful tool."
"If any one of the filters is intercepted, it will register the full 50% false-positive rate. So I am able to hedge my privacy risk across several interactions, and have some control over how accurately other people can see my network. My friends can be sure with a high degree of certainty whether someone is on my contact list, but someone who manages to snag just one or two of my filters will learn almost nothing about me."
"Additionally, you can combine two Bloom filters that have the same length and hash functions with the bitwise OR operator to create a composite filter."
"If any one of the filters is intercepted, it will register the full 50% false-positive rate. So I am able to hedge my privacy risk across several interactions, and have some control over how accurately other people can see my network. My friends can be sure with a high degree of certainty whether someone is on my contact list, but someone who manages to snag just one or two of my filters will learn almost nothing about me."
"Additionally, you can combine two Bloom filters that have the same length and hash functions with the bitwise OR operator to create a composite filter."
Sunday, April 18, 2004
Save Our Software
Save Our Software "During the Internet boom, the traditional companies most obviously affected were bricks-and-mortar bookstores and travel agents...But in 2004, the businesses under direct financial assault by the broadband consumer Internet are not toothless independent bookstores. Instead, they are the major music labels, movie studios, and broadcasters."
"First, the FCC is conducting a proceeding to set the guidelines for what it calls 'software defined radio...in the near future, it will be possible use spectrum more efficiently and to increase competition in a space that's now the sole domain of incumbent operators. But only if we keep the FCC from regulating these technologies."
"Second...the FCC generally approved a mandate called the 'broadcast flag,' which would require that digital TV broadcasts include an anti-theft code to prevent consumers from recording programs off the air."
"First, the FCC is conducting a proceeding to set the guidelines for what it calls 'software defined radio...in the near future, it will be possible use spectrum more efficiently and to increase competition in a space that's now the sole domain of incumbent operators. But only if we keep the FCC from regulating these technologies."
"Second...the FCC generally approved a mandate called the 'broadcast flag,' which would require that digital TV broadcasts include an anti-theft code to prevent consumers from recording programs off the air."
Thursday, April 15, 2004
WebFountain posting
WebFountain, the Long Version "So how does WebFountain make answers to such complex and specific queries possible? Short answer: A lot of hardware and a shitload of metatags. Longer answer: WebFountain does more than index the web, then serve up results based on keyword matches and some clever algorithms. Sure, it indexes the web, but once the pages are crawled, WebFountain goes several steps beyond consumer search engines, classifying those pages across any number of crucial semantic categories. (Yes, IBM is active in the semantic web conversation, and has published several specs on this in the public domain). Using natural language and machine learning technology, along with a host of structured data cross-references (such as public company databases or, perhaps, a client’s proprietary database of industry terminology), WebFountain basically re-structures the web, making it accessible to a client’s queries."
"As I mentioned earlier, IBM’s model for WebFountain is platform-based. Assuming they can pay the freight, most anyone can develop for it, using a standard API that leverages simple web services. IBM won’t disclose most of its customers, but two it will mention are Semagix, which has a (pretty damn frightening) money laundering application, and Factiva, which has developed a “reputation manager” - think of it as Technorati on steroids for the serious corporate marketing or legal department. (Imagine being able to find any mention of your product or service anywhere on the web and create custom filters for the context, location, date, author, and relationships attached to those mentions, in near real time.)"
"As I mentioned earlier, IBM’s model for WebFountain is platform-based. Assuming they can pay the freight, most anyone can develop for it, using a standard API that leverages simple web services. IBM won’t disclose most of its customers, but two it will mention are Semagix, which has a (pretty damn frightening) money laundering application, and Factiva, which has developed a “reputation manager” - think of it as Technorati on steroids for the serious corporate marketing or legal department. (Imagine being able to find any mention of your product or service anywhere on the web and create custom filters for the context, location, date, author, and relationships attached to those mentions, in near real time.)"
History of Treemaps
Treemaps for space-constrained visualization of hierarchies "During 1990, in response to the common problem of a filled hard disk, I became obsessed with the idea of producing a compact visualization of directory tree structures. Since the 80 Megabyte hard disk in the HCIL was shared by 14 users it was difficult to determine how and where space was used. Finding large files that could be deleted, or even determining which users consumed the largest shares of disk space were difficult tasks.
Tree structured node-link diagrams grew too large to be useful, so I explored ways to show a tree in a space-constrained layout. I rejected strategies that left blank spaces or those that dealt with only fixed levels or fixed branching factors. Showing file size by area coding seemed appealing, but various rectangular, triangular, and circular strategies all had problems. Then while puzzling about this in the faculty lounge, I had the Aha! experience of splitting the screen into rectangles in alternating horizontal and vertical directions as you traverse down the levels. This recursive algorithm seemed attractive, but it took me a few days to convince myself that it would always work and to write a six line algorithm."
I especially liked PhotoMesa.
Tree structured node-link diagrams grew too large to be useful, so I explored ways to show a tree in a space-constrained layout. I rejected strategies that left blank spaces or those that dealt with only fixed levels or fixed branching factors. Showing file size by area coding seemed appealing, but various rectangular, triangular, and circular strategies all had problems. Then while puzzling about this in the faculty lounge, I had the Aha! experience of splitting the screen into rectangles in alternating horizontal and vertical directions as you traverse down the levels. This recursive algorithm seemed attractive, but it took me a few days to convince myself that it would always work and to write a six line algorithm."
I especially liked PhotoMesa.
Wednesday, April 14, 2004
RSS on the TV
NewsGator Media Center Edition Provides Access to Syndicated Content on TV Sets; 'Living Room' Interface Allows Users to Read Selected Content, or Watch On-Demand Video Content "NewsGator Technologies launched NewsGator Media Center Edition today, which allows users to read syndicated content feeds on their TV with Windows XP Media Center Edition. Both text and multimedia content is supported, with an interface designed to be used with a remote control from across the room. NewsGator Media Center Edition shows information that has not already been viewed on another device by synchronizing user subscriptions with NewsGator Online Services."
You know your technology has reached maturity when someone tries to put it on the television. A good followup posting with links to screenshots.
You know your technology has reached maturity when someone tries to put it on the television. A good followup posting with links to screenshots.
DSpace presentations
DSpace User Group Meeting 2004 Presentations A bunch of Powerpoint presentations on DSpace.
42...What was the question?
Abracadabra, 42, Curator "The Hitchhiker's Guide to the Galaxy,1 those afflicted with 42 fever argue that "UML" is actually the correct answer. The classical symptom of those afflicted with 42 fever in the sphere of software engineering is to have an a priori delusion that UML is the solution for all software-engineering problems."
Part of a larger set of articles on UML Fever.
"The entertaining tenor of "Death by UML Fever" should not be inferred to suggest that UML fever is an imaginary ailment. It is genuinely real, it is thriving, and its presence is causing cost and schedule trauma on many software programs right now. Furthermore, the root causes of this fever, in general, have nothing to do with the UML itself: Rather, this fever and its various manifestations are largely symptoms of deeper ills in an organization's software development practices. Software organizations should consider launching self-diagnosis campaigns to assess the presence or extent of UML fever on their programs and plan rehabilitation strategies as necessary. Developing good software is a difficult enough task without having to endure the preventable and often painful complications of the dreaded UML fever."
Part of a larger set of articles on UML Fever.
"The entertaining tenor of "Death by UML Fever" should not be inferred to suggest that UML fever is an imaginary ailment. It is genuinely real, it is thriving, and its presence is causing cost and schedule trauma on many software programs right now. Furthermore, the root causes of this fever, in general, have nothing to do with the UML itself: Rather, this fever and its various manifestations are largely symptoms of deeper ills in an organization's software development practices. Software organizations should consider launching self-diagnosis campaigns to assess the presence or extent of UML fever on their programs and plan rehabilitation strategies as necessary. Developing good software is a difficult enough task without having to endure the preventable and often painful complications of the dreaded UML fever."
We all Agree
As We May Hack "I can walk into any meeting anywhere in the world with a piece of paper in hand, and I can be sure that people will be able to read it, mark it up, pass it around, and file it away. I can't say the same for electronic documents. I can't annotate a Web page or use the same filing system for both my email and my Word documents, at least not in a way that is guaranteed to be interoperable with applications on my own machine and on others. Why not? - A Manifesto for Collaborative Tools
Yawp after me - "RDF! RDF!". But seriously, the answer to "why not?""
From Yawping!. The collaborative tools manifesto has been mentioned several times recently it's worth a look.
Yawp after me - "RDF! RDF!". But seriously, the answer to "why not?""
From Yawping!. The collaborative tools manifesto has been mentioned several times recently it's worth a look.
Monday, April 12, 2004
Another RSS library for Java
RSSLib4J is a set of Java API to parse and retrieve information from a RSS Feed. It supports RSS version 0.9x ,1.0 and 2.0 specification with Doublin Core and Syndication namespace.
Sunday, April 11, 2004
Querying Use Cases and Features
Data Access Working Group User Cases: WORKING DRAFT "Because there are no formal standards in these areas, developers in industry and in open source projects have created a wide variety of query languages for RDF data...These languages lack both a common syntax and a common semantics; there is, in fact, a wide variety of semantics: from declartive, SQL-like languages, to path languages, to rule or production-like systems. The existing languages also exhibit a range of extensibility features and builtin capabilities, including inferencing, distributed query, and domain-specific semantics."
Some of the features being considered include: optional triples, disjunction, queries with paths of length two or more edges, able to indicate whether the query response includes entailment from the graph or treats the graph as a fixed object, expressing arbitrary RDF datatypes, queries expressible as a URL, user specifiable query result formats and query results in RDF (closure).
Some of the features being considered include: optional triples, disjunction, queries with paths of length two or more edges, able to indicate whether the query response includes entailment from the graph or treats the graph as a fixed object, expressing arbitrary RDF datatypes, queries expressible as a URL, user specifiable query result formats and query results in RDF (closure).
Saturday, April 10, 2004
Librarians and the Semantic Web
People at work think that I have a fetish for girls in glasses or something I think. But actually I think that librarians are going to be an important part of the Semantic Web. Oh and chicks in glasses are dead sexy...err...anyway a recent posting "thinking about the semantic web" links to a series of postings along these lines (librarians not glasses):
* Extreme! "I want people to leave understanding that the Semantic Web didn’t come out of nowhere, that there’s a good century (at least!) of work coming to terms with infoglut that Semantic Web technologies build on. I want them to start thinking critically about website information architecture, about information management in general, about metadata, about problems with (and hopes for!) search engines.",
* More on metadata "Well, I have news. Everything Cory says is true. But it doesn’t matter. Hear me? It doesn’t matter. Because all those arguments aren’t arguments against a Semantic Web—they’re arguments against a populist Semantic Web.", and
* Metadata and authority "This means, quite simply, that a lot of current Semantic Web pipe dreaming will founder on authority and representation-convention problems. Heck, it’s already foundering."
One day, when I categorize this blog there will definitely be a "librarians" section.
* Extreme! "I want people to leave understanding that the Semantic Web didn’t come out of nowhere, that there’s a good century (at least!) of work coming to terms with infoglut that Semantic Web technologies build on. I want them to start thinking critically about website information architecture, about information management in general, about metadata, about problems with (and hopes for!) search engines.",
* More on metadata "Well, I have news. Everything Cory says is true. But it doesn’t matter. Hear me? It doesn’t matter. Because all those arguments aren’t arguments against a Semantic Web—they’re arguments against a populist Semantic Web.", and
* Metadata and authority "This means, quite simply, that a lot of current Semantic Web pipe dreaming will founder on authority and representation-convention problems. Heck, it’s already foundering."
One day, when I categorize this blog there will definitely be a "librarians" section.
SASDO
Semantically Adapted Service Data Objects "...is a prototype extension to the base Service Data Objects implementation provided in the ETTK. Specifically, it adds the ability to use RDF and the W3C Web Ontology Language (OWL) as a means of attaching a semantic metamodel to an SDO DataGraph and use that model to navigate and query the DataGraph independent of it's structural model, without requiring any changes to the SDO API or running any transformations on the data."
From GRDDL.
From GRDDL.
Gnowsis
Gnowsis is a project lead by Leo Sauermann. I've read about it before but apparently never blogged it. Many of the ideas like the Semantic Desktop are worth noting. This type of application is something that seems to be coming up again and again.
He gave a list of features to add: optional triples, update language, protocol on the web and a protocol on the desktop (ODBC like). The first two are handled by iTQL although the second is more elegant than first. Kowari/TKS has always had a driver. The Kowari Lite client, currently the executable iTQL jar, is only about 1MB and doesn't include things like Jena.
why I love Patrick Sticklers URIQA approach "Building RDF aggregators is not an easy task. I have tried it in many different ways, and had varying forms of success. If you want an easy approach that does it, think about concise bounded descriptions."
I do think that the resolver idea, using the FROM clause, views and defining caching and updates, is going to be an easy way to do RDF aggregation.
He gave a list of features to add: optional triples, update language, protocol on the web and a protocol on the desktop (ODBC like). The first two are handled by iTQL although the second is more elegant than first. Kowari/TKS has always had a driver. The Kowari Lite client, currently the executable iTQL jar, is only about 1MB and doesn't include things like Jena.
why I love Patrick Sticklers URIQA approach "Building RDF aggregators is not an easy task. I have tried it in many different ways, and had varying forms of success. If you want an easy approach that does it, think about concise bounded descriptions."
I do think that the resolver idea, using the FROM clause, views and defining caching and updates, is going to be an easy way to do RDF aggregation.
Thursday, April 08, 2004
Regime Change
U.S. Terrorism Policy Spawns Steady Staff Exodus "Since the Sept. 11 attacks, the Bush administration has faced a steady exodus of counterterrorism officials, many disappointed by a preoccupation with Iraq they said undermined the U.S. fight against terrorism."
""I'm kind of hoping for regime change," one official who quit told Reuters."
""Iraq has been a distraction from the whole counterterrorism effort," said the former official, adding the policy had frustrated many in the White House anti-terrorism office, about two-thirds of whom have left and been replaced since Sept. 11."
"Roger Cressey, who served under Clarke in the White House counterterrorism office, said: "Dick accurately reflects the frustration of many in the counterterrorism community in getting the new administration to take the al Qaeda issue seriously.""
Oh and for something cool with photo-mosaics:
War President "Below is a small version of an image I made. It's a mosaic composed of the photos of the American service men and women who have died in Iraq. No photograph is used more than three times." From here.
If it's broken:
http://randomfoo.net/junk/200404/warpresident/warpres.jpg
An OS tool to do mosaics (includes Tux mosaic - I thought it was something else when I first looked at it):
http://www.stud.uni-hannover.de/~michaelt/juggle/
""I'm kind of hoping for regime change," one official who quit told Reuters."
""Iraq has been a distraction from the whole counterterrorism effort," said the former official, adding the policy had frustrated many in the White House anti-terrorism office, about two-thirds of whom have left and been replaced since Sept. 11."
"Roger Cressey, who served under Clarke in the White House counterterrorism office, said: "Dick accurately reflects the frustration of many in the counterterrorism community in getting the new administration to take the al Qaeda issue seriously.""
Oh and for something cool with photo-mosaics:
War President "Below is a small version of an image I made. It's a mosaic composed of the photos of the American service men and women who have died in Iraq. No photograph is used more than three times." From here.
If it's broken:
http://randomfoo.net/junk/200404/warpresident/warpres.jpg
An OS tool to do mosaics (includes Tux mosaic - I thought it was something else when I first looked at it):
http://www.stud.uni-hannover.de/~michaelt/juggle/
Is WiX a trick?
MS Open-Source Move is Straight from Playbook "Looking more closely, WiX enables developers to translate programs from Windows Installer Databases (.msi/.msm) formats to a text-based, XML-file format. XML is an open standard, but to work with MSI/MSM, those XML files have a very specific format. Now, what company has already sought patent protection for specific expressions of XML code? The answer is, of course, Microsoft, with its Office XML formats.
Has Microsoft done this with WiX's XML formats yet? I don't know. But if the pros from Redmond haven't yet, they will. They did it for Office XML document formats; they'll do it for this. Thus, Microsoft's open-source code will work only on Microsoft-proprietary XML to produce Microsoft-proprietary installation programs. With open source like this, who needs proprietary programs?"
"Now, while it may look like Microsoft is doing something new, or perhaps even something helpful to the open-source community, it's not. What Microsoft is really doing is putting more of the Halloween memo's plans into action. Why shouldn't it? The Halloween plans are just an elaboration of Microsoft's time-tested embrace-and-extend technique The only embrace Microsoft is really giving the open-source community is a stranglehold. "
Has Microsoft done this with WiX's XML formats yet? I don't know. But if the pros from Redmond haven't yet, they will. They did it for Office XML document formats; they'll do it for this. Thus, Microsoft's open-source code will work only on Microsoft-proprietary XML to produce Microsoft-proprietary installation programs. With open source like this, who needs proprietary programs?"
"Now, while it may look like Microsoft is doing something new, or perhaps even something helpful to the open-source community, it's not. What Microsoft is really doing is putting more of the Halloween memo's plans into action. Why shouldn't it? The Halloween plans are just an elaboration of Microsoft's time-tested embrace-and-extend technique The only embrace Microsoft is really giving the open-source community is a stranglehold. "
Tuesday, April 06, 2004
The Power of Free
The Profitability of Free Code "Some thought that open source meant non-commercial or even anti-commercial.' At the time, I wondered how far open source could go and in that posting I identified three criteria for success with open source:
• the user community must be vast
• the product scope must be well defined
• a viable business model must exist.
Today, I think that people are starting to understand that open source is more than just a development approach—it's a business model. What evidence is there to support this? Just follow the money: the OSBC conference was packed with venture capitalists and lawyers; techies were outnumbered ten-to-one. Even long time veterans of the closed source software world, like Ray Lane (previously of Oracle) and Chris Stone of Novell are focused on leveraging the power of open source in their businesses.
And why not? That's the nice thing about capitalism. It has a built-in Darwinian efficiency. If open source allows companies to deliver better products at a cheaper price, then it will be used to do just that. We see many of the most competitive companies in the world, like Amazon, Charles Schwab, Cisco, Corporate Express, FedEx, GE, Merrill Lynch, Motorola, Nokia, Sabre, SAP, and UPS using open source software as a platform for building new applications. Many companies that have been successful with Linux are now looking at deploying an entire open source stack, known as LAMP (Linux, Apache, MySQL, PHP/Perl/Python).
These days, it's easier than ever before for an ambitious developer to download all the software he or she needs to build a product—or even to build a business—on top of commodity hardware and open source software. Some of today's hottest pre-IPO companies, including billion-dollar-babies Salesforce.com and Google, as well as emerging social networking companies like AlwaysOn's Zaibatsu, Friendster, and Tribe.net, are all using open source software."
• the user community must be vast
• the product scope must be well defined
• a viable business model must exist.
Today, I think that people are starting to understand that open source is more than just a development approach—it's a business model. What evidence is there to support this? Just follow the money: the OSBC conference was packed with venture capitalists and lawyers; techies were outnumbered ten-to-one. Even long time veterans of the closed source software world, like Ray Lane (previously of Oracle) and Chris Stone of Novell are focused on leveraging the power of open source in their businesses.
And why not? That's the nice thing about capitalism. It has a built-in Darwinian efficiency. If open source allows companies to deliver better products at a cheaper price, then it will be used to do just that. We see many of the most competitive companies in the world, like Amazon, Charles Schwab, Cisco, Corporate Express, FedEx, GE, Merrill Lynch, Motorola, Nokia, Sabre, SAP, and UPS using open source software as a platform for building new applications. Many companies that have been successful with Linux are now looking at deploying an entire open source stack, known as LAMP (Linux, Apache, MySQL, PHP/Perl/Python).
These days, it's easier than ever before for an ambitious developer to download all the software he or she needs to build a product—or even to build a business—on top of commodity hardware and open source software. Some of today's hottest pre-IPO companies, including billion-dollar-babies Salesforce.com and Google, as well as emerging social networking companies like AlwaysOn's Zaibatsu, Friendster, and Tribe.net, are all using open source software."
Kowari 1.0.2 Soon
We've fixed all the known bugs; that just leaves the unknown ones. We've got JRDF, Jena, and our own RDQL implementation. The loading and query speed has also improved considerably - there's none of the problems associated previously with 32 bit systems. Kowari lite is down to 11MB; which considering that Jena and related jars are over 2MB that's pretty good. Querying is now totally disk backed - you can do a completely unconstrained query over arbitrarily large data sets.
It's now at the stage of what to do next. Some of them are fairly obvious like full data type support, scripting (possibly Groovy) and inferencing. But we've also got zeroconf and MAYBE. There's also a large refactoring underway to make Lucene, the triple store, ontology models and others as plugins exposed via a resolver interface. This should allow just about anything to be queried in the FROM clause of iTQL. In the short term, this means extending the querying of file and http RDF sources to include other metadata formats such as MP3 tags, iCal, vCard and XML based RSS. It will allow models to be typed and configured. Using views you could easily create an RSS aggregator. Other, more difficult resolver implementations will be available in TKS.
JRDF has been a little neglected. The next things to be worked on is transactions and a ResultSet like interface.
It's now at the stage of what to do next. Some of them are fairly obvious like full data type support, scripting (possibly Groovy) and inferencing. But we've also got zeroconf and MAYBE. There's also a large refactoring underway to make Lucene, the triple store, ontology models and others as plugins exposed via a resolver interface. This should allow just about anything to be queried in the FROM clause of iTQL. In the short term, this means extending the querying of file and http RDF sources to include other metadata formats such as MP3 tags, iCal, vCard and XML based RSS. It will allow models to be typed and configured. Using views you could easily create an RSS aggregator. Other, more difficult resolver implementations will be available in TKS.
JRDF has been a little neglected. The next things to be worked on is transactions and a ResultSet like interface.
Your Life in a Wal-Mart Database
What to do with all that information "[Wal-Mart] the largest in the world, now also maintains the world's largest database, 280 Terabytes, as it seeks to better understand how to efficiently serve its customers. For instance, it increasingly uses Radio Frequency ID tags -- tiny 25-cent data-holders affixed to a box of razors and other goods. Wal-Mart uses RFID to track its inventory through much of the supply chain. Soon the tags will only cost pennies and start going on the razors themselves. Talk about increasing the amount of data to store and analyze! (I listened in the cool new $10 shirt I bought Sunday at a local Wal-Mart store.)"
"And in the not too distant future, data may be able to interact with other data without human intervention. That was the message of Web inventor Tim Berners-Lee. He talked about the glorious future of something called the "semantic web," a concept that most people aside from programmers will probably never understand. His talk here didn't help. One hopeful journalist from the Economist asked Berners-Lee to give an example of how companies could make or save money using it, but he didn't have an answer. He doesn't have to. He's an academic. Businesspeople here assured me this is a big deal we'll hear more about. "
I thought I'd read this before but couldn't find it in a previous entry. Although I did find a previous claim that the biggest database was France Telecom's at 30 TB.
"And in the not too distant future, data may be able to interact with other data without human intervention. That was the message of Web inventor Tim Berners-Lee. He talked about the glorious future of something called the "semantic web," a concept that most people aside from programmers will probably never understand. His talk here didn't help. One hopeful journalist from the Economist asked Berners-Lee to give an example of how companies could make or save money using it, but he didn't have an answer. He doesn't have to. He's an academic. Businesspeople here assured me this is a big deal we'll hear more about. "
I thought I'd read this before but couldn't find it in a previous entry. Although I did find a previous claim that the biggest database was France Telecom's at 30 TB.
Monday, April 05, 2004
Two Quick Projects
* ruby-rdf Very timely. "A project to advance ruby in the semantic web realm. Specifically, this will be an attempt to port the Redland RDF framework to ruby in an object oriented manner."
* ROWL "The system enables users to frame rules in RDF/XML syntax using an ontology in OWL. Using XSLT stylesheets, the rules in RDF/XML are transformed into forward-chaining defrules in JESS. We make use of two more stylesheets to transform ontology and instance files into Jess undordered facts..."
* ROWL "The system enables users to frame rules in RDF/XML syntax using an ontology in OWL. Using XSLT stylesheets, the rules in RDF/XML are transformed into forward-chaining defrules in JESS. We make use of two more stylesheets to transform ontology and instance files into Jess undordered facts..."
Chimney Sweeps
The Next Job for the W3C "People will start to feel that when they access some data that they didn’t really think was relevant, they hadn’t thought was relevant to the problem at hand, and suddenly, their problem gets connected to some other things."
"To answer questions within a company, you’ve got to reach across boundaries. You’ve got stovepipes of information. You have HR information. You have totally separate information for bug reports and customer satisfaction.
You might have another, for example, for documentation. We find that we were tracking a customer’s problem, but most of those documents left the company, and when we left the company, we should have kept them. So let’s find out who else has written documents which are being used by people who are tracking bug reports for processing customers who have this problem.
At the moment, what we’re looking at for this is huge monster applications like the pre-Web, which are document databases. That didn’t work because everyone wanted to operate it a certain way. It’s much better to let each part of a company have a Web site, and they’re linked to each other. Let the financial folks organize things how they want, and let manufacturing control people organize their things how they want, and then merge them. Where they have things in common like people or times or places—they have to be able to connect them."
"To answer questions within a company, you’ve got to reach across boundaries. You’ve got stovepipes of information. You have HR information. You have totally separate information for bug reports and customer satisfaction.
You might have another, for example, for documentation. We find that we were tracking a customer’s problem, but most of those documents left the company, and when we left the company, we should have kept them. So let’s find out who else has written documents which are being used by people who are tracking bug reports for processing customers who have this problem.
At the moment, what we’re looking at for this is huge monster applications like the pre-Web, which are document databases. That didn’t work because everyone wanted to operate it a certain way. It’s much better to let each part of a company have a Web site, and they’re linked to each other. Let the financial folks organize things how they want, and let manufacturing control people organize their things how they want, and then merge them. Where they have things in common like people or times or places—they have to be able to connect them."
Lisp
Better is better: improving productivity through programming languages "This is one reason why Lisp and functional programming folks are a bit cool on stuff like Object and Aspect orientation. They can extend to Aspects or Objects using the language constructs directly. To most of us working in popular languages these are paradigm shifting ways of thinking about programming. But we can't use Java directly to support something like aspects or generics. There's whole communities working on language and compiler extensions, open source libraries, as well as that all important vendor support - J2EE app servers are being renegineered just to support aspects. To a Lisp person these are just constructs expressed as macros (which are written in Lisp itself), something you do on a rainy weekend. What's the fuss about?"
"It's something a running joke in the Lisp community that all language efforts are doomed to reinvent Lisp."
"It's corny to say the worst thing about Lisp is a Lisp programmer. But there's some truth in it. Work long enough in this industry and you'll run into a Lisp bigot...I think Lisp never traditionally emphasized libraries because the language is so flexible you can build one on your own, but then you have the twin nightmares of integration and reuse lying in wait for you."
I have been thinking about Lisp and aspect programming recently. The other is ontological programming or programming against an ontology.
"It's something a running joke in the Lisp community that all language efforts are doomed to reinvent Lisp."
"It's corny to say the worst thing about Lisp is a Lisp programmer. But there's some truth in it. Work long enough in this industry and you'll run into a Lisp bigot...I think Lisp never traditionally emphasized libraries because the language is so flexible you can build one on your own, but then you have the twin nightmares of integration and reuse lying in wait for you."
I have been thinking about Lisp and aspect programming recently. The other is ontological programming or programming against an ontology.
Blast from the past
Another catch up post:
* Ercim News posting in 2002 mentioned both Corese and Notio. Their API uses strings to define concepts, relations and attributes. Apparently, it's now available for download (via PlanetRDF). It uses Jena's ARP but has its own CG interface.
* Sleepycat for Java Released under the same licence as the C version.
* Platypus Wiki Again, using Jena and looks good.
* Not in RDF The difficulties of NOT in RDF. I think Kowari/TKS lacks NOT because it was initially hard to do in our implementation; there's now no reason not to do NOT.
* Fixing the Java Memory Model, Part 2 Includes double checked locking, changes to volatile and initialization safety.
* Blog-Bleary? Try (What Else?) a Blog on kinja. Another review.
* RSS Versions Syndic8 is reporting that RSS 1.0 is now 46.4% of all RSS feeds with RSS 2.0 and 0.91 (combined) taking up 49.9%. Will RSS 1.0 take the lead soon?
* Ercim News posting in 2002 mentioned both Corese and Notio. Their API uses strings to define concepts, relations and attributes. Apparently, it's now available for download (via PlanetRDF). It uses Jena's ARP but has its own CG interface.
* Sleepycat for Java Released under the same licence as the C version.
* Platypus Wiki Again, using Jena and looks good.
* Not in RDF The difficulties of NOT in RDF. I think Kowari/TKS lacks NOT because it was initially hard to do in our implementation; there's now no reason not to do NOT.
* Fixing the Java Memory Model, Part 2 Includes double checked locking, changes to volatile and initialization safety.
* Blog-Bleary? Try (What Else?) a Blog on kinja. Another review.
* RSS Versions Syndic8 is reporting that RSS 1.0 is now 46.4% of all RSS feeds with RSS 2.0 and 0.91 (combined) taking up 49.9%. Will RSS 1.0 take the lead soon?
Wednesday, March 31, 2004
D2RQ
RE: mapping a relational database as RDF "I'm currently working on an extended version of D2R MAP called D2RQ, which will allow the general rewriting of RDQL and find(s,p,o) queries to database specific SQL queries.
I have attached the current language specification and an example mapping which shows how the ISWC ontology (http://www.wiwiss.fu-berlin.de/suhl/bizer/d2rmap/iswc.daml.xml) is mapped
to a corresponding application specific relational schema (http://www.wiwiss.fu-berlin.de/suhl/bizer/d2rmap/iswc.sql.txt). The example also shows how D2RQ deals with taxonomical class structures in the ontology and many-to-many relationships in the data base.
D2RQ is currently implemented as a plug-in for Jena 2.1. The first prototype will be released sometime in May under an open source license."
I have attached the current language specification and an example mapping which shows how the ISWC ontology (http://www.wiwiss.fu-berlin.de/suhl/bizer/d2rmap/iswc.daml.xml) is mapped
to a corresponding application specific relational schema (http://www.wiwiss.fu-berlin.de/suhl/bizer/d2rmap/iswc.sql.txt). The example also shows how D2RQ deals with taxonomical class structures in the ontology and many-to-many relationships in the data base.
D2RQ is currently implemented as a plug-in for Jena 2.1. The first prototype will be released sometime in May under an open source license."
Tuesday, March 30, 2004
Microsoft Goes Blogging
Microsoft to launch news, blog search services "The new services, called MSN Newsbot and MSN Blogbot, up the ante in the battle for Internet search market share. Microsoft already said that it is working on its own general Internet search engine, expected to be launched this year, to go head-to-head with Google. The Friday announcements were made at a Microsoft meeting for online advertisers, Microsoft said in a statement."
I hadn't looked at Newsbot, I'm sure any similarities (even the "Beta") to Google News is purely coincidental.
I hadn't looked at Newsbot, I'm sure any similarities (even the "Beta") to Google News is purely coincidental.
Wallop and FOAF
The truth about why I hate Friendster "Look, I want to say to the Friendsters of the world, we already invented a social network for friends and strangers. It's called the Internet. Why are you privatizing it? Why do we need a proprietary sub-network to do what the Internet has already done in an open way?"
"FOAF and LOAF add value to the Net, enriching it with voluntarily disclosed information about who we are and who we know. In this they are unlike Artificial Social Networks that capture the conversations between us but make them inaccessible to other applications.
The trade-off is high, however. Just take a look at Wallop and you'll see what I mean. "
Wallop was announced last year.
"FOAF and LOAF add value to the Net, enriching it with voluntarily disclosed information about who we are and who we know. In this they are unlike Artificial Social Networks that capture the conversations between us but make them inaccessible to other applications.
The trade-off is high, however. Just take a look at Wallop and you'll see what I mean. "
Wallop was announced last year.
Monday, March 29, 2004
Jabberwocky and Adenosine
Jabberwocky "Jabberwocky represents a shift towards interoperability of RDF-based systems. Up until now, for all RDF was promoted as the basis of the new, semantic, web, information has remained locked behind propriatory, incompatible storage and query systems. Jabberwocky aims to set a standard for the distributed sharing and search and use of RDF-based semantics."
Adenosine "Adenosine is a language designed both to work on, and be distributed over, the semantic web. The language exploits the expressiveness of RDF whilst adopting a clean syntax based on a combination of Notation3 and ECMAScript."
Adenosine "Adenosine is a language designed both to work on, and be distributed over, the semantic web. The language exploits the expressiveness of RDF whilst adopting a clean syntax based on a combination of Notation3 and ECMAScript."
Snippets, security and contexts
A pragmatic approach to storing and distributing RDF in context using Snippets "Snippets provide the means to represent a set of statements made about a particular subject and in a particular context. They may be stored conventionally using a bag of reified statements, or in a non-standard compact form using a much smaller number of triples. This compact representation is somewhat analogous to the use of quads to represent individual reified statements. The difference is that, while quads fall completely outside the specification, snippets may still be queried and transported in their compact form."
Sunday, March 28, 2004
Friday, March 26, 2004
Upcoming Papers for the WWW2004 Conference
Selected Search and Search-Related Papers Authors include researchers from UCLA, Intel, IBM and the University of Washington.
Semantic Web Dream
A maiden's dream "The most sophisticated (and the most bleeding edge) is to use the Web Ontology Language, which allows you to define an ontology. Literally, "ontology" is the science or study of being, particularly in a metaphysical sense. It is not therefore, numerable and should not be preceded by the indefinite article...Now, the Web Ontology Language is a W3C (World Wide Web Consortium) standard and, in practice, it is an extension to UML. This gives the clue to how you create an ontology: you model it.
This also gives an indication of Unicorn's approach and why it tries not to talk about semantics too much. Unicorn aims to provide your computers with the ability to understand that customers and clients are the same thing but does so without forcing you to adopt a formal semantic approach. Thus, for example, you can do the relevant modelling using E-R (entity relationship) diagrams if you wish."
The second article covers Network Inference: "Network Inference is much more committed to new developments in the area of semantic information architectures, whereas Unicorn takes a more evolutionary approach. In particular, Network Inference is strongly committed to OWL, the Web Ontology Language (whose letters don't match because that is how Owl spelled his name - WOL - in Winnie the Pooh)...The big argument in favour of this approach is that OWL is a standard. So are XQuery, SOAP, UDDI, WSDL and the other standards that Network Inference supports. In principle, this is a significant step forward in the integration space (whether EAI or EII) because, while existing solutions make use of standards, they are not, with the arguable exception of pure XML solutions, standards-based. That is, there is no standard way of expressing a virtual schema or database to underpin these integrations."
This also gives an indication of Unicorn's approach and why it tries not to talk about semantics too much. Unicorn aims to provide your computers with the ability to understand that customers and clients are the same thing but does so without forcing you to adopt a formal semantic approach. Thus, for example, you can do the relevant modelling using E-R (entity relationship) diagrams if you wish."
The second article covers Network Inference: "Network Inference is much more committed to new developments in the area of semantic information architectures, whereas Unicorn takes a more evolutionary approach. In particular, Network Inference is strongly committed to OWL, the Web Ontology Language (whose letters don't match because that is how Owl spelled his name - WOL - in Winnie the Pooh)...The big argument in favour of this approach is that OWL is a standard. So are XQuery, SOAP, UDDI, WSDL and the other standards that Network Inference supports. In principle, this is a significant step forward in the integration space (whether EAI or EII) because, while existing solutions make use of standards, they are not, with the arguable exception of pure XML solutions, standards-based. That is, there is no standard way of expressing a virtual schema or database to underpin these integrations."
Java OWL-S API
OWL-S API provides a Java API for programmatic access to read, execute and write OWL-S (formerly known as DAML-S) service descriptions. The API supports to read different versions of OWL-S (OWL-S 1.0, OWL-S 0.9, DAML-S 0.7) descriptions. The API provides an ExecutionEngine that can invoke AtomicProcesses that has WSDL or UPnP groundings, and CompositeProcecesses that uses control constructs Sequence, Unordered, and Split. Executing processes that relies on conditionals such as If-Then-else and RepeatUntil is not supported in the default implementation. But this implementation can be extended to handle these constructs if the application that uses the OWL-S descriptions has a custom syntax and evaluation procedure for the conditions."
AI Fun and Relationship Fun
RELATIONSHIP: Two Worldviews Something I can finally agree with. Except that it's really a problem.
Fun with Topic Maps
Metadata? Thesauri? Taxonomies? Topic Maps! "Topic maps are organized around topics, which represent subjects. That is, in a topic map you find topics. Every topic you find represents a subject out in the real world that it is a symbol or stand-in for in the topic map. The definition of subject is essentially "anything whatsoever". What this means is that from the point of view of a topic map, objects are just a special kind of subject.
What this means is that the whole machinery we have created to describe the concepts in a subject-based classification is also available to describe the objects being classified. Thus, we can create a topic type for objects ("document", perhaps), and express the metadata using names, occurrences, and associations. The topic types let us keep track of what is a document and what is a concept, but we no longer need different technologies for metadata and classification.
And once we have everything in a single representation we can start to cross the boundaries by for example describing the authors of a paper further, and connecting them with the terms from the subject-based classification. Effectively what has happened is that the straightjacket has been removed, and we can now say anything we want to. The technology is no longer the limiting factor; instead the limits are set by our imagination and by how much information we are able to maintain within the economic constraints of our projects."
What this means is that the whole machinery we have created to describe the concepts in a subject-based classification is also available to describe the objects being classified. Thus, we can create a topic type for objects ("document", perhaps), and express the metadata using names, occurrences, and associations. The topic types let us keep track of what is a document and what is a concept, but we no longer need different technologies for metadata and classification.
And once we have everything in a single representation we can start to cross the boundaries by for example describing the authors of a paper further, and connecting them with the terms from the subject-based classification. Effectively what has happened is that the straightjacket has been removed, and we can now say anything we want to. The technology is no longer the limiting factor; instead the limits are set by our imagination and by how much information we are able to maintain within the economic constraints of our projects."
Java Fun
* JBoss Cache Released "Supports local, synchronous replication, and asynchronous replication transaction. Works with JTA transaction manager. Support transaction isolation levels." Check out the TreeCacheAop documentation.
* FishEye "Fisheye delivers a unified view of your repository that provides easy navigation, powerful search, historical reporting, configurable file annotation and diff views, changeset analysis, RSS feeds, and integration with your issue tracker. Many more features and enhancements are also under development." And Australian too.
* Joott - Use OpenOffice to convert to different document types and the like.
* Blocks In Java Trying to hack Java to do closures.
* FishEye "Fisheye delivers a unified view of your repository that provides easy navigation, powerful search, historical reporting, configurable file annotation and diff views, changeset analysis, RSS feeds, and integration with your issue tracker. Many more features and enhancements are also under development." And Australian too.
* Joott - Use OpenOffice to convert to different document types and the like.
* Blocks In Java Trying to hack Java to do closures.
Thursday, March 25, 2004
IBM announces use of Aspects
IBM touts new 'aspect' for software coding "The public commitment to aspect-oriented programming is meant to indicate that IBM believes the technology is ready for use in business development, rather than academic scenarios. Only a few commercial software companies, such as Intentional Software and JBoss Group, use aspect-oriented technologies.
"We believe these concepts are viable; they can deliver real value and help us transform ourselves to be more flexible and improve quality," Berry said.
Before aspect orientation can become mainstream, programmers need to be trained in the techniques and development tools, according to analysts. IBM, for one, will be working on "wizards" that can walk people through the process of creating aspects.
"The tooling support is absolutely essential for this to take off," Berry said.
Berry said he expected that in the next two or three years, development tools will commonly have aspects integrated within them. Further along, IBM is looking at melding its work on model-driven software development with aspect orientation, he said.
Also at the conference, IBM will discuss another research project, called Concern Manipulation Environment. The project, which uses work developed in IBM research, is designed to provide a path to aspect-oriented programming with tools that work with existing software written in different languages. "
The different languages included C++ and C#.
"We believe these concepts are viable; they can deliver real value and help us transform ourselves to be more flexible and improve quality," Berry said.
Before aspect orientation can become mainstream, programmers need to be trained in the techniques and development tools, according to analysts. IBM, for one, will be working on "wizards" that can walk people through the process of creating aspects.
"The tooling support is absolutely essential for this to take off," Berry said.
Berry said he expected that in the next two or three years, development tools will commonly have aspects integrated within them. Further along, IBM is looking at melding its work on model-driven software development with aspect orientation, he said.
Also at the conference, IBM will discuss another research project, called Concern Manipulation Environment. The project, which uses work developed in IBM research, is designed to provide a path to aspect-oriented programming with tools that work with existing software written in different languages. "
The different languages included C++ and C#.
Another monopoly case
Newly Released Documents Shed Light on Microsoft Tactics "Even as Microsoft prepares to face penalties from the European Union, which accuses the company of abusing the Windows monopoly, new details about the tactics Microsoft used to secure a dominant position in software markets for nearly two decades are emerging in a state courthouse in Minneapolis...Among the documents introduced in court this week was a letter from June 1990 in which Bill Gates, Microsoft's chairman, told Andrew S. Grove, the chief executive of Intel at the time, that any support given to the Go Corporation, a Silicon Valley software company, would be considered an aggressive move against Microsoft."
The book Start-up : A Silicon Valley Adventure is definately a good, if one-sided, read. Just in time for the 10 year anniversary.
The book Start-up : A Silicon Valley Adventure is definately a good, if one-sided, read. Just in time for the 10 year anniversary.
Users make bad Security Decisions
Disappearing .Net Brand Invites Assimilation "Importantly, she then noted, "If you remember 'Hailstorm,' Microsoft's personal Web services technologies, a number of them are set to manifest in Indigo." Why position something as a pervasive set of user services that might frighten off privacy-sensitive consumers, when you can position it instead as a developer productivity tool that will be comfortably buried inside end-user applications and tasks?"
"Personally, I'm in a pretty grouchy mood at the moment about end users' apparent willingness to live with bad choices that developers make: specifically, choices that favor developer convenience over security and reliability and other boring issues. For example, I'll soon be sharing with eWEEK readers my comments on Greg Hoglund's and Gary McGraw's new book, "Exploiting Software: How to Break Code"; one comment from that book seems apropos. The specific subject is PHP, which the book calls "a study in bad security. … The mantra 'don't make the developer go to any extra work to get stuff done' applies in all cases." And yet, PHP is widely used, creating widespread vulnerabilities.
Likewise the developer and user convenience features of Internet Explorer and the Windows platform, which still pave the way for costly attacks. "
"Personally, I'm in a pretty grouchy mood at the moment about end users' apparent willingness to live with bad choices that developers make: specifically, choices that favor developer convenience over security and reliability and other boring issues. For example, I'll soon be sharing with eWEEK readers my comments on Greg Hoglund's and Gary McGraw's new book, "Exploiting Software: How to Break Code"; one comment from that book seems apropos. The specific subject is PHP, which the book calls "a study in bad security. … The mantra 'don't make the developer go to any extra work to get stuff done' applies in all cases." And yet, PHP is widely used, creating widespread vulnerabilities.
Likewise the developer and user convenience features of Internet Explorer and the Windows platform, which still pave the way for costly attacks. "
Wednesday, March 24, 2004
Aspects can be slow
Measuring the Dynamic Behaviour of AspectJ Programs "The conventional wisdom that AspectJ does not introduce overheads seems to be explained by typical aspect usage. First, advice generally applies to user code, yet typical Java programs spend most of their time in library calls. As a percentage of the total execution time, the cost of advice is therefore insignificant in such applications. The Tetris benchmark illustrates this phenomenon. Some of our benchmarks (in particular DCM) show the opposite behaviour,where the advice is so expensive that the overheads of applying it are dwarfed."
"Contrary to popular belief, we did however also find significant overheads. This has led to the following guidelines for AspectJ usage, as well as promising areas for future compiler research:
* Loose pointcuts. It is easy to write a pointcut that matches too many join points...
* Advice that is too generic. When using the very generic form of around, this causes a significant amount of boxing and unboxing to convert arguments to the right form...
* Unwarranted use of around. Because of the above, it is generally preferable to eschew around in favour of after returning when possible...
* Pertarget. The use of per clauses to control aspect creation carries a non-negligible overhead..."
"Contrary to popular belief, we did however also find significant overheads. This has led to the following guidelines for AspectJ usage, as well as promising areas for future compiler research:
* Loose pointcuts. It is easy to write a pointcut that matches too many join points...
* Advice that is too generic. When using the very generic form of around, this causes a significant amount of boxing and unboxing to convert arguments to the right form...
* Unwarranted use of around. Because of the above, it is generally preferable to eschew around in favour of after returning when possible...
* Pertarget. The use of per clauses to control aspect creation carries a non-negligible overhead..."
Monday, March 22, 2004
Interesting Query Use Cases
There are definately a large variety of use cases being kicked around that you wouldn't always think people would want or expect.
* Federated Searching: "Actor/User Agent needs to seamlessly query/access/integrate related chunks/pieces of data coming from a set of decentralized heterogeneous sources, and get presented an unified view over a the whole result-set/data-set."
* Temporal querying.
* Regular Expressions.
* Discover functionality of server: "Abelard's client software connects to each RDF storage server and determines whether it supports one of the three query languages it knows about. Abelard's client software chooses, based on priorities set by Abelard, to send different queries to different servers."
They seem to be missing security - probably required in the federated searching use case.
* Federated Searching: "Actor/User Agent needs to seamlessly query/access/integrate related chunks/pieces of data coming from a set of decentralized heterogeneous sources, and get presented an unified view over a the whole result-set/data-set."
* Temporal querying.
* Regular Expressions.
* Discover functionality of server: "Abelard's client software connects to each RDF storage server and determines whether it supports one of the three query languages it knows about. Abelard's client software chooses, based on priorities set by Abelard, to send different queries to different servers."
They seem to be missing security - probably required in the federated searching use case.
Saturday, March 20, 2004
OASIS goes Semantic
Network Inference Joins OASIS Consortium "Network Inference will participate in ebXML and other OASIS Technical Committees to help advance the application of OWL, OWL-DL, OWL-S, and RDF into business environments. The Cerebra Server™ product suite from Network Inference provides market-leading support for the Web Ontology Language and is the basis of the company's deep expertise with the emerging semantic web languages."
Hairy Computers
Web ontologies: problems, benefits "Computers are insanely, hair-tearingly, stupid - they have to be told everything in precise detail...using ontology with computers can't possibly be worse than the in-code truth functions we use today. Legions of programmers are writing down things like isBossOf all the time (myself included). It's their job. Except they don't call them relations, or predicates, they call them methods and those methods capture what most of us call business logic. [Nor do they call themselves ontologists.] So it's pretty far from logic but good enough for business - until the time comes to change the logic where the cost of using all that code becomes apparent. It's a long held truism that we'd be all much better off if we could get such logic out of code."
"For my part, the raison d'etre of declaring such relations is reducing code complexity while increasing flexibility."
Bill also suggests a reading list of: Data and Reality: Bill Kent, Knowledge Representation: John Sowa, Programming in Prolog: Clocksin and Mellish Philosophy of Artificial Intelligence: ed Margaret Boden.
For those wanting to really look at vocabularies "Vocabulary Mapping for Terminology Services" which describes how combining different vocabularies can increase usefulness.
"For my part, the raison d'etre of declaring such relations is reducing code complexity while increasing flexibility."
Bill also suggests a reading list of: Data and Reality: Bill Kent, Knowledge Representation: John Sowa, Programming in Prolog: Clocksin and Mellish Philosophy of Artificial Intelligence: ed Margaret Boden.
For those wanting to really look at vocabularies "Vocabulary Mapping for Terminology Services" which describes how combining different vocabularies can increase usefulness.
DL-XML Mapper
Integrating DL and XML "Semantic Web Service concepts like DAML-S or the MCM Semantic Web Service Matchmaker provide means for storage and retrieval of web services far beyond text or UDDI based search. These concepts use Description Logics as a means to express the semantics of services. However, these Description Logic formats (e.g. the "RDF/XML"-serialization of DAML+OIL) are not directly compatible with the XML formats used by today's Web Services. In other words, the lingua franca of the Web is still XML, the advantages of Description Logics notwithstanding.
In order to gain some level of interoperation between Semantic Web Service concepts and traditional XML based Web Service concepts (and between Semantic Web and Web in general!), it is necessary to provide bridges between the (RDF/DAML/OWL based) concept description community and the XML/SOAP style of message passing."
Download and more information.
In order to gain some level of interoperation between Semantic Web Service concepts and traditional XML based Web Service concepts (and between Semantic Web and Web in general!), it is necessary to provide bridges between the (RDF/DAML/OWL based) concept description community and the XML/SOAP style of message passing."
Download and more information.
Friday, March 19, 2004
Album sales at record high
Forget the spin! It's a record record. "Total sales (in all formats) climbed to a record high in 2003: 65.6 million, easily topping the previous record of 63.9 million set in 2001.
And the sales of actual CD albums climbed above 50 million for the first time (well above 50 million actually).
It's a real cause for celebration. Back before the advent of Napster and home CD burning the industry was selling fewer than 40 million CD albums per year."
Other stories: ARIA's press release, Sound of cash registers is music to the ears, Radio interview with Peter Martin and MUSIC INDUSTRY NEAR COLLAPSE IN FILE-SHARE FRENZY - No, Wait, That's Not Right….
Or the Slashdot article.
And the sales of actual CD albums climbed above 50 million for the first time (well above 50 million actually).
It's a real cause for celebration. Back before the advent of Napster and home CD burning the industry was selling fewer than 40 million CD albums per year."
Other stories: ARIA's press release, Sound of cash registers is music to the ears, Radio interview with Peter Martin and MUSIC INDUSTRY NEAR COLLAPSE IN FILE-SHARE FRENZY - No, Wait, That's Not Right….
Or the Slashdot article.
Thursday, March 18, 2004
Practical Calendaring
Making a date with the Semantic Web " Chris Sukornyk has an answer to the question "Is there any practical application for the W3C Semantic Web concept?"
Semaview Inc., Sukornyk's Toronto-based start-up, is offering a Semantic Web-based event calendaring application called eventSherpa. It is designed to give individuals and businesses a shareable calendar with the semantic search capabilities envisioned by the W3C. "
Semaview Inc., Sukornyk's Toronto-based start-up, is offering a Semantic Web-based event calendaring application called eventSherpa. It is designed to give individuals and businesses a shareable calendar with the semantic search capabilities envisioned by the W3C. "
Wednesday, March 17, 2004
Vocabularies
RELATIONSHIP: A vocabulary for describing relationships between people "The RELATIONSHIP list should make it obvious that explicit linguistic clarity in human relations is a pipe dream. It probably won't though the madness of the age is to assume that people can spell out, in explicit detail, the messiest aspects of their lives, and that they will eagerly do so, in order to provide better inputs to cool new software."
From the comments: "I have been lurking around the FOAF list for a while and know these guys have been at it for a long while. The questions raised by Clay have been brought up and debated to death...here comes a reputable guy, who probably has not been involved in the effort, who without really knowing the issues, "fires a rocket at it". This rocket causes a lot of waste of energy because it is just a basic instinct kind of a rocket. Not really thought through."
Clay Shirky on RELATIONSHIP "...he still managed to overlook the raison d'etre for the relationship. Indeed it's the raison d'etre for all vocabularies."
Most of the other comments are humorous and worth a read. Another case of the metadata being more interesting and thought provoking than the data.
From the comments: "I have been lurking around the FOAF list for a while and know these guys have been at it for a long while. The questions raised by Clay have been brought up and debated to death...here comes a reputable guy, who probably has not been involved in the effort, who without really knowing the issues, "fires a rocket at it". This rocket causes a lot of waste of energy because it is just a basic instinct kind of a rocket. Not really thought through."
Clay Shirky on RELATIONSHIP "...he still managed to overlook the raison d'etre for the relationship. Indeed it's the raison d'etre for all vocabularies."
Most of the other comments are humorous and worth a read. Another case of the metadata being more interesting and thought provoking than the data.
Tuesday, March 16, 2004
Not FOAF
The Opposite of FOAF "One of my friends is breaking new ground with semantic web; he set up a directory of annoying salespeople, and he’s naming names."
HP iTunes
HP Music Complete with annoying background loop. Links to Apple's iTunes download page for HP.
RDF Schema Editor
Mark Choate has released an early version of RDF Schema Editor for download. Giving it a quick run, it seems fairly intuitive for those who are used to RDF.
Schema Editor update "There is nothing like a real project when it comes to learning something new. The most problematic part of RDF from a user's perspective is handling namespaces. It's a hassle. But I also think that it's a hassle that can be overcome, and not one that really needs to intrude on the user experience. Improving the usability of tools that create metadata is important if the Semantic Web is ever to grow beyond speculation."
Schema Editor update "There is nothing like a real project when it comes to learning something new. The most problematic part of RDF from a user's perspective is handling namespaces. It's a hassle. But I also think that it's a hassle that can be overcome, and not one that really needs to intrude on the user experience. Improving the usability of tools that create metadata is important if the Semantic Web is ever to grow beyond speculation."
Monday, March 15, 2004
The Prevalence of Prevalyer
Continuing Prevalence "Brief run-down on two significant paradigms that have been becoming a lot more visible, presumably because they're good at...". As long as you define "it" in the strictest sense of what you're doing. If it's anything like persistently storing data (not objects, data) then Prevalyer isn't it. That being said, it's a finalist in the Jolt Awards.
Here's a bunch of links:
* Prevayling Stupidity,
* The Prevayler,
* Object Prevalence: Get Rid of Your Database?, and
* The first message on the AJUG maling list on Prevalyer. It includes replies like, "Prevayler serializes incoming transactions but not the result of executing each transaction. You don't have change (before or after) images. Undoing a failing transaction cannot be accomplished."
Revisiting the DBDebunk web site:
* MORE ON THE STATE OF THE INDUSTRY AND SQL.
* To O OR to R: IS THIS A DATABASE QUESTION?.
We've been considering adding to iTQL the MAYBE operator, to reduce the complexity of writing joins when querying RDF data (more on the MAYBE operator by Date).
Here's a bunch of links:
* Prevayling Stupidity,
* The Prevayler,
* Object Prevalence: Get Rid of Your Database?, and
* The first message on the AJUG maling list on Prevalyer. It includes replies like, "Prevayler serializes incoming transactions but not the result of executing each transaction. You don't have change (before or after) images. Undoing a failing transaction cannot be accomplished."
Revisiting the DBDebunk web site:
* MORE ON THE STATE OF THE INDUSTRY AND SQL.
* To O OR to R: IS THIS A DATABASE QUESTION?.
We've been considering adding to iTQL the MAYBE operator, to reduce the complexity of writing joins when querying RDF data (more on the MAYBE operator by Date).
Saturday, March 13, 2004
Digging Against the Internet
Advice to Microsoft regarding commodity software "Digging in against open source commoditization won't work - it would be like digging in against the Internet, which Microsoft tried for a while before getting wise. Any move towards cutting off alternatives by limiting interoperability or integration options would be fraught with danger, since it would enrage customers, accelerate the divergence of the open source platform, and have other undesirable results. Despite this, Microsoft is at risk of following this path, due to the corporate delusion that goes by many names: "better together," "unified platform," and "integrated software." There is false hope in Redmond that these outmoded approaches to software integration will attract and keep international markets, governments, academics, and most importantly, innovators, safely within the Microsoft sphere of influence. But they won't ."
Friday, March 12, 2004
EMail Classification
Xerox Scientists Invent Software That Automatically Indexes, Categorizes, Routes Electronic Documents "Scientists at Xerox Corporation have invented powerful software that's clever enough to "read" an electronic document, decide how it should be classified by subject, then route it to the right person's e-mail address or online document management system ? all completely automatically.
The software, which is a categorizing tool, is intended to help businesses keep their e-document collections orderly and easily accessible, and it is available for licensing from Xerox.
"A misshelved book in a library might as well be lost. It's the same with documents that haven't been properly categorized; the document itself may have to be recreated," said Eric Gaussier, a research scientist at the Xerox Research Centre Europe in Grenoble, France. "Our new software can help save time and money and increase productivity. It will ensure that documents are properly classified for future retrieval and that the right information gets into the right hands as quickly as possible.""
The software, which is a categorizing tool, is intended to help businesses keep their e-document collections orderly and easily accessible, and it is available for licensing from Xerox.
"A misshelved book in a library might as well be lost. It's the same with documents that haven't been properly categorized; the document itself may have to be recreated," said Eric Gaussier, a research scientist at the Xerox Research Centre Europe in Grenoble, France. "Our new software can help save time and money and increase productivity. It will ensure that documents are properly classified for future retrieval and that the right information gets into the right hands as quickly as possible.""
Updates, Books and Referrers
Some quick updates:
* A Lot To Digest - A glowing summary of the Cannes Technical Plenary and WG Meeting Week.
* From duct tape to chewing gum and baling wire - A review of the RDF in XHTML proposal.
* A Semantic Web Primer. Also from MIT Press From Logic to Logic Programming and Dynamic Logic.
* Also closed the RFEs in Kowari for RDQL (which we implemented using SableCC and our own query layer) and Jena Support (still lots to optimize).
* In my referrer log: [Babelfish translation] "The semantic Web, you use it and you will use it more and more without the knowledge. And it is very well like that. RDF, OWL, Semantic Web" from La Grange.
* A Lot To Digest - A glowing summary of the Cannes Technical Plenary and WG Meeting Week.
* From duct tape to chewing gum and baling wire - A review of the RDF in XHTML proposal.
* A Semantic Web Primer. Also from MIT Press From Logic to Logic Programming and Dynamic Logic.
* Also closed the RFEs in Kowari for RDQL (which we implemented using SableCC and our own query layer) and Jena Support (still lots to optimize).
* In my referrer log: [Babelfish translation] "The semantic Web, you use it and you will use it more and more without the knowledge. And it is very well like that. RDF, OWL, Semantic Web" from La Grange.
Thursday, March 04, 2004
SWIG Summary
Semantic Web Interest Group "Just about every tool in the Adobe arsenal is now able to embed RDF into their primary artifacts. It's ironic, of course, that a core web technology, RDF, still isn't really embeddable into the core web data format, HTML; but it can easily be embedded into Adobe artifacts...there are two reasons why Adobe customers want metadata embedded in digital artifacts. The first, obvious, reason is to support automated workflow. If you've ever worked in a graphics shop or design house, you know that workflow management is absolutely critical to profitability. The second, less obvious, reason is intelligent syndication. What a real-time OWL-powered pub-sub application needs, of course, is rich RDF metadata attached or linked to artifacts of the Web: images, video and sound files, as well as XHTML documents."
"...we're at the point now where the basic knoweldge representational mechanisms -- RDF and OWL -- are formalized; where mechanisms for the creation of RDF and OWL are coming online and into place; and where there is increasing awareness of and interest in the SW. What we need, then, is the "uniform means of interaction" for the SW that HTTP provides for the Web. What we need is a reasonable specification that we can give both to RDF tool makers and to to Python and Perl and Java and C# and Ruby programmers; and we need to say to them, "implement this specification in your tool or your language; then your users and programmers will be able to uniformly access resource representations on the Semantic Web". That will be a happy day, indeed."
Also talks about how Boeing are using OWL in the battlefield.
"...we're at the point now where the basic knoweldge representational mechanisms -- RDF and OWL -- are formalized; where mechanisms for the creation of RDF and OWL are coming online and into place; and where there is increasing awareness of and interest in the SW. What we need, then, is the "uniform means of interaction" for the SW that HTTP provides for the Web. What we need is a reasonable specification that we can give both to RDF tool makers and to to Python and Perl and Java and C# and Ruby programmers; and we need to say to them, "implement this specification in your tool or your language; then your users and programmers will be able to uniformly access resource representations on the Semantic Web". That will be a happy day, indeed."
Also talks about how Boeing are using OWL in the battlefield.
The Other Tim on the SW
Bill Gates, Edd Dumbill, and the Semantic Web "This idea of making the data smarter is absolutely central. I have been speaking about this myself for some time. As we move to a network-based software platform, where applications don't live on the local machine but are distributed between rich client front ends and huge database back ends, "open source" alone won't really solve our problems. It's open data we're going to be fighting about."
We 0wnz0r Facts
Hands Off! That Fact Is Mine "Ostensibly, the Database and Collections of Information Misappropriation Act (HR3261) makes it a crime for anyone to copy and redistribute a substantial portion of data collected by commercial database companies and list publishers. But critics say the bill would give the companies ownership of facts -- stock quotes, historical health data, sports scores and voter lists. The bill would restrict the kinds of free exchange and shared resources that are essential to an informed citizenry, opponents say."
"Under the terms of the broadly written bill, a public-health website could be deemed in violation of the law for gathering a list of the latest health headlines and providing links to them on its home page."
"An encyclopedia site not only could own the historical facts contained in its online entries, but could do so long after the copyright on authorship of the written entries had expired. Unlike copyright, which expires 70 years after the death of a work's author, the Misappropriation Act doesn't designate an expiration date."
"Under the terms of the broadly written bill, a public-health website could be deemed in violation of the law for gathering a list of the latest health headlines and providing links to them on its home page."
"An encyclopedia site not only could own the historical facts contained in its online entries, but could do so long after the copyright on authorship of the written entries had expired. Unlike copyright, which expires 70 years after the death of a work's author, the Misappropriation Act doesn't designate an expiration date."
Free T-Shirt!
Trust on the Semantic Web "This project is designed to build and maintain a trust network on the semantic web. Using an ontology that extends FOAF, you can assign trust ratings to people you know.
The network generated in this project will serve as the foundation for a dissertation on the topic of Trust on the web. By becoming part of the network, your data will be used as the foundation for Trustbot, Trustmail, and some future applications."
Current top 10 and visualization of the graph.
The network generated in this project will serve as the foundation for a dissertation on the topic of Trust on the web. By becoming part of the network, your data will be used as the foundation for Trustbot, Trustmail, and some future applications."
Current top 10 and visualization of the graph.
Wednesday, March 03, 2004
Faceted Metadata
Faceted interfaces "Yes, the alternative is so-called faceted metadata. Like the facets on the diamond, faceted metadata allow you to look from different sides to the same information. Faceted metadata have the information organized on several dimensions (facets). The information has values on each of the facets. Readers find information by chosing values on each of the facets."
Faceted Metadata Search and Browse "Examples of faceted metadata include:
* Music store: songs have attributes such as artist, title, length, genre, date...
* Recipes: cuisine, main ingredients, cooking style, holiday...
* Travel site: articles have authors, dates, places, prices...
* Regulatory documents: product and part codes, machine types, expiration dates...
* Image collection: artist, date, style, type of image, major colors, theme..."
Both have screenshots of the faceted approach, although the second is a little more clear. Flamenco is often cited too. For example, Flamenco Fine Arts Search.
Faceted Metadata Search and Browse "Examples of faceted metadata include:
* Music store: songs have attributes such as artist, title, length, genre, date...
* Recipes: cuisine, main ingredients, cooking style, holiday...
* Travel site: articles have authors, dates, places, prices...
* Regulatory documents: product and part codes, machine types, expiration dates...
* Image collection: artist, date, style, type of image, major colors, theme..."
Both have screenshots of the faceted approach, although the second is a little more clear. Flamenco is often cited too. For example, Flamenco Fine Arts Search.
Tuesday, March 02, 2004
Balloons don't scale
Balloons and Ribbon as Social Networking Visualization "Artist/curator friend Mark Soo did a piece for one of the Infest openings where he visualized the curators' social network using balloons with people's names printed on them as the nodes and ribbons tying them together as the edges (the data comes from "invites" he got the curators to send to one another).
This was a great, inviting, tactile "graph manipulaton interface". But the reason I liked it so much was that it really brought out the problems of social networks visualizations as a way of learning about the networks being visualized: too confusing!"
This was a great, inviting, tactile "graph manipulaton interface". But the reason I liked it so much was that it really brought out the problems of social networks visualizations as a way of learning about the networks being visualized: too confusing!"
The Bleeding Semantic Edge
Semantics: a new beginning? "The reason for all this continual mapping is that the source data has no meaning in any real sense of the word. That is, it has no context. What the new interest in semantics is looking to do is to provide that meaning. Unfortunately, there is no indication that database vendors (the leading ones at least) are going to provide this contextual information any time soon. However, there are moves afoot within the semantic community to try to establish semantic rules and ontologies that can be used across the enterprise and then, using appropriate tools, you can start to automate the process of creating these transformations and mappings rather than having to do it manually via a mapping tool.
There are a number of vendors already in this space. For example, Unicorn is an Israeli company that has moved its headquarters to the States, Contivo is completely American, and Network Inference started in the UK but is currently following Unicorn to the US.
Now, although all of these companies have a number of installations already, this is really bleeding edge stuff and I confess to not having fully got to grasps with it. However, I am in the process of arranging briefings with all of these companies and I will report back when I have more information and can explain it more simply. In the meantime the technology appears to have potential, not just for data integration but also other areas like EAI. Watch this space."
There are a number of vendors already in this space. For example, Unicorn is an Israeli company that has moved its headquarters to the States, Contivo is completely American, and Network Inference started in the UK but is currently following Unicorn to the US.
Now, although all of these companies have a number of installations already, this is really bleeding edge stuff and I confess to not having fully got to grasps with it. However, I am in the process of arranging briefings with all of these companies and I will report back when I have more information and can explain it more simply. In the meantime the technology appears to have potential, not just for data integration but also other areas like EAI. Watch this space."
Friday, February 27, 2004
Time for Phase 2
I was noticing the current increase in activity and general buzz with the Semantic Web. Recently, development work like: RDF in XHTML and Nokia's Semantic Web Server. It's obvious now, we've reached Phase 2 - the fun phase.
"W3C announced the launch of Phase 2 of the Semantic Web Activity. Two new Working Groups have been formed; the Best Practices and Deployment WG (charter) and the RDF Data Access Working Group (charter). These join the RDF Core and Web Ontology WGs, the Semantic Web Interest Group, and the Semantic Web Coordination Group."
"The aim of this Semantic Web Best Practices and Deployment (SWBPD) Working Group is to provide hands-on support for developers of Semantic Web applications. With the publication of the revised RDF and the new OWL specification we expect a large number of new application developers. Some evidence of this could be seen at the last International Semantic Web Conference in Florida, which featured a wide range of applications, including 10 submissions to the Semantic Web Challenge (see http://challenge.semanticweb.org/).This working group will help application developers by providing them with "best practices" in various forms, ranging from engineering guidelines, ontology / vocabulary repositories to educational material and demo applications."
http://www.w3.org/2003/12/swa/swbpd-charter
"The RDF data model is a directed, labeled graph with edges labeled with URIs and nodes that are either unidentified, literals, or URIs (please see the RDF Primer for further explanation). The principal task of the RDF Data Access Working Group is to gather requirements and to define an HTTP and/or SOAP-based protocol for selecting instances of subgraphs from an RDF graph. The group's attention is drawn to the RDF Net API submission. This will involve a language for the query and the use of RDF in some serialization for the returned results. The query langauge may have aspects of a path language similar to XPath (used for XML in XSLT and XQuery) and various RDF experimental path syntaxes."
http://www.w3.org/2003/12/swa/dawg-charter.
"W3C announced the launch of Phase 2 of the Semantic Web Activity. Two new Working Groups have been formed; the Best Practices and Deployment WG (charter) and the RDF Data Access Working Group (charter). These join the RDF Core and Web Ontology WGs, the Semantic Web Interest Group, and the Semantic Web Coordination Group."
"The aim of this Semantic Web Best Practices and Deployment (SWBPD) Working Group is to provide hands-on support for developers of Semantic Web applications. With the publication of the revised RDF and the new OWL specification we expect a large number of new application developers. Some evidence of this could be seen at the last International Semantic Web Conference in Florida, which featured a wide range of applications, including 10 submissions to the Semantic Web Challenge (see http://challenge.semanticweb.org/).This working group will help application developers by providing them with "best practices" in various forms, ranging from engineering guidelines, ontology / vocabulary repositories to educational material and demo applications."
http://www.w3.org/2003/12/swa/swbpd-charter
"The RDF data model is a directed, labeled graph with edges labeled with URIs and nodes that are either unidentified, literals, or URIs (please see the RDF Primer for further explanation). The principal task of the RDF Data Access Working Group is to gather requirements and to define an HTTP and/or SOAP-based protocol for selecting instances of subgraphs from an RDF graph. The group's attention is drawn to the RDF Net API submission. This will involve a language for the query and the use of RDF in some serialization for the returned results. The query langauge may have aspects of a path language similar to XPath (used for XML in XSLT and XQuery) and various RDF experimental path syntaxes."
http://www.w3.org/2003/12/swa/dawg-charter.
Wednesday, February 25, 2004
RDQLPlus
"RDQLPlus is a tool for querying RDF graphs, featuring graphical results in a zoomable user interface (ZUI). It can work with existing RDF files, Jena2 RDF databases, and a native-Java database called Mckoi (included)."
The UI has similar scaling problems to IsaViz (with displaying hundreds of statements). Good to see a pure Java implementation.
The UI has similar scaling problems to IsaViz (with displaying hundreds of statements). Good to see a pure Java implementation.
Sunday, February 22, 2004
Metadata Mac
Next Mac OS X to be Metadata-driven? "The (unconfirmed) info says that Mac OS X 10.4 will go "further than anticipated", introducing not only a "database-driven" new Finder (possibly similar to BeOS' Tracker) --although the file system itself will still be HFS+-- but also a wide support for file metadata. Please note that both the BeFS (and quite possibly this Apple implementation) is not similar to Longhorn's WinFS (apples & oranges). All this is not a surprise for us, as the people who were behind the same realization on BeOS --Dominic Giampaolo and Pavel Cisler-- today work at key positions at Apple Computer in the file system and Finder areas respectively."
I had previously mentioned another suggestion for metadata in OS X.
I had previously mentioned another suggestion for metadata in OS X.
Marusha
Marusha: Using semantic web concepts to create your own private DJ and a more recent update.
"I ran into a number of serious scaling issues on Friday. Adding the 16 million tracks from freedb.org to the parser's database really was the straw that broke the camel's back. Lesson learnt: There are types of queries that a relational database will never be able to run in acceptable time."
"I ran into a number of serious scaling issues on Friday. Adding the 16 million tracks from freedb.org to the parser's database really was the straw that broke the camel's back. Lesson learnt: There are types of queries that a relational database will never be able to run in acceptable time."
Saturday, February 21, 2004
Mangrove
Mangrove: An Evolutionary Approach to the Semantic Web "The Mangrove project seeks to create an environment in which users are motivated to create semantic content because of the existence of useful semantic services that exploit that content and because the process of generating such content is as close as possible to existing techniques for generating HTML documents. Our goal is to facilitate the simple annotation and subsequent extraction and querying of the enormous amount of information that already exists within the WWW's billions of HTML pages, rather than requiring the creation of new content from scratch. Our approach thus seeks to faciliate the gradual transformation of the current web into the semantic web."
Very similar to the ideas expressed recently in "interview followup". Semantic Tagger is an interesting example of this (the schema is an XML schema).
Very similar to the ideas expressed recently in "interview followup". Semantic Tagger is an interesting example of this (the schema is an XML schema).
Future of MS Search
Robert Scoble On The Future Of Search Engine Technology "If we're talking about your local hard drive, searching for files on your local hard drive is still awful and getting worse...It's easier to create files now than it is to find them. "
"...to really make search work well search engines need metadata and metadata that's added by the system keeping track of your usage of files, as well as letting application developers add metadata into the system itself. In a lot of ways, weblogs are adding metadata to websites. When a weblog like mine links to a web site, we usually add some more details about that site. We might say it's a "cool site" for instance. Well, Google puts those words into its engine. That's metadata."
"Developers distrust Microsoft's intentions here. They also don't want to open up their own applications to their competitors. If you were a developer at AOL, for instance, do you see opening up your contact system with, say, Yahoo or Google or Microsoft? That's scary stuff for all of us.
But, if the industry works together on common WinFS schemas (not just for contacts either, but other types of data too), we'll come away with some really great new capabilities. It really will take getting developers excited about WinFS's promise and getting them to lose their fears about opening up their data types. "
"...to really make search work well search engines need metadata and metadata that's added by the system keeping track of your usage of files, as well as letting application developers add metadata into the system itself. In a lot of ways, weblogs are adding metadata to websites. When a weblog like mine links to a web site, we usually add some more details about that site. We might say it's a "cool site" for instance. Well, Google puts those words into its engine. That's metadata."
"Developers distrust Microsoft's intentions here. They also don't want to open up their own applications to their competitors. If you were a developer at AOL, for instance, do you see opening up your contact system with, say, Yahoo or Google or Microsoft? That's scary stuff for all of us.
But, if the industry works together on common WinFS schemas (not just for contacts either, but other types of data too), we'll come away with some really great new capabilities. It really will take getting developers excited about WinFS's promise and getting them to lose their fears about opening up their data types. "
AUIML
AUIML "AUIML is an XML dialect that is a platform and a technology-neutral representation of panels, wizards, property sheets, etc. AUIML captures relative positioning information of user interface components and delegates their display to a platform-specific renderer. Depending on the platform or device being used, the renderer decides the best way to present the user interface to the user and receive user input.
The AUIML XML is created using the Eclipse-based AUIML VisualBuilder, which allows a developer to quickly build and preview user interfaces in the Java Swing and HTML Renderers. The AUIML VisualBuilder can also automatically create data beans, event handlers, and help system skeletons for the user interface. Since it plugs into Eclipse, building the user interface and application code is an integrated proces"
Interesting that IBM are support Swing here and not SWT.
The AUIML XML is created using the Eclipse-based AUIML VisualBuilder, which allows a developer to quickly build and preview user interfaces in the Java Swing and HTML Renderers. The AUIML VisualBuilder can also automatically create data beans, event handlers, and help system skeletons for the user interface. Since it plugs into Eclipse, building the user interface and application code is an integrated proces"
Interesting that IBM are support Swing here and not SWT.
Ontological Programming
Semantic Integration "Basically semantic integration seems to involve using RDF/OWL to define mappings between XML vocabularies.
Recently I've been involved in co-ordinating a number of large scale data migrations to help integrate several systems. This inevitably involved exploring the business models in the affected applications to define a mapping layer to allow the data to be cleanly migrated. Also inevitably this mapping ends up being expressed as a bunch of (hairy!) procedural code. It would have been nice to have been able to express that mapping in a more declarative way, if no other reason than it's easier to understand and debug possible problems. An example of not being able to see the wood for the trees."
There are many way to declaratively map different schemas - SQL, OO and XML all have their own tools. The value that RDF has is that you can program to a single ontology and map all of these different data sources to it.
With RDF there's not only the ability to map between XML vocabularies but to program to an ontology rather than a schema. In this case, the problem goes from MxN to M+N (or even just M).
One of the articles that highlights this issue is The Impedance Imperative Tuples + Objects + Infosets =Too Much Stuff!.
Recently I've been involved in co-ordinating a number of large scale data migrations to help integrate several systems. This inevitably involved exploring the business models in the affected applications to define a mapping layer to allow the data to be cleanly migrated. Also inevitably this mapping ends up being expressed as a bunch of (hairy!) procedural code. It would have been nice to have been able to express that mapping in a more declarative way, if no other reason than it's easier to understand and debug possible problems. An example of not being able to see the wood for the trees."
There are many way to declaratively map different schemas - SQL, OO and XML all have their own tools. The value that RDF has is that you can program to a single ontology and map all of these different data sources to it.
With RDF there's not only the ability to map between XML vocabularies but to program to an ontology rather than a schema. In this case, the problem goes from MxN to M+N (or even just M).
One of the articles that highlights this issue is The Impedance Imperative Tuples + Objects + Infosets =Too Much Stuff!.
Friday, February 20, 2004
US Government Understands the Semantic Web
Taxonomy’s not just design, it’s an art "If anyone understands the acronym soup of Web services, it’s Michael C. Daconta. He’s director of Web and technology services for systems integrator APG McDonald Bradley Inc. of McLean, Va. As part of that job, Daconta is chief architect of the Defense Intelligence Agency’s Virtual Knowledge Base, a project to compile a directory of Defense Department data through Extensible Markup Language ontologies. "
"GCN: Will everyone use a single taxonomy for one big semantic Web, or will organizations build their own semantic Webs?
DACONTA: There clearly will not be just one semantic Web. A lot of people are looking at taxonomies, so they have to be careful. "
"GCN: Will everyone use a single taxonomy for one big semantic Web, or will organizations build their own semantic Webs?
DACONTA: There clearly will not be just one semantic Web. A lot of people are looking at taxonomies, so they have to be careful. "
Thursday, February 19, 2004
Google Won
Search For Tomorrow ""For a lot of kids today, the world started in 1996," says librarian and author Gary Price.
And yet Berkeley professor Peter Lyman points out that traditional sources of information, such as textbooks, are heavily filtered by committees, and are full of "compromised information." He's not so sure that the robotic Web crawlers give results any worse than those from more traditional sources. "There's been a culture war between librarians and computer scientists," Lyman says.
And the war is over, he adds.
"Google won.""
""A generation ago, reference librarians -- flesh-and-blood creatures -- were the most powerful search engines on the planet. But the rise of robotic search engines in the mid-1990s has removed the human mediators between researchers and information. Librarians are not so sure they approve. Much of the material on the World Wide Web is wrong, or crazy, or of questionable provenance, or simply out of date (odd to say this about a new technology, but the Web is full of stale information).
"How do you authenticate what you're looking at? How do you know this isn't some kind of fly-by-night operation that's put up this Web site?" asks librarian Patricia Wand of American University.""
""He needs one that knows that he's a big-brain tech guru and not an eighth-grader with a paper due.
"The field is called user modeling," says Dan Gruhl of IBM. "It's all about computers watching interactions with people to try to understand their interests and something about them."
Imagine a version of Google that's got a bit of TiVo in it: It doesn't require you to pose a query. It already knows! It's one step ahead of you. It has learned your habits and thought processes and interests. It's your secretary, your colleague, your counselor, your own graduate student doing research for which you'll get all the credit.
To put it in computer terminology, it is your intelligent agent.""
And yet Berkeley professor Peter Lyman points out that traditional sources of information, such as textbooks, are heavily filtered by committees, and are full of "compromised information." He's not so sure that the robotic Web crawlers give results any worse than those from more traditional sources. "There's been a culture war between librarians and computer scientists," Lyman says.
And the war is over, he adds.
"Google won.""
""A generation ago, reference librarians -- flesh-and-blood creatures -- were the most powerful search engines on the planet. But the rise of robotic search engines in the mid-1990s has removed the human mediators between researchers and information. Librarians are not so sure they approve. Much of the material on the World Wide Web is wrong, or crazy, or of questionable provenance, or simply out of date (odd to say this about a new technology, but the Web is full of stale information).
"How do you authenticate what you're looking at? How do you know this isn't some kind of fly-by-night operation that's put up this Web site?" asks librarian Patricia Wand of American University.""
""He needs one that knows that he's a big-brain tech guru and not an eighth-grader with a paper due.
"The field is called user modeling," says Dan Gruhl of IBM. "It's all about computers watching interactions with people to try to understand their interests and something about them."
Imagine a version of Google that's got a bit of TiVo in it: It doesn't require you to pose a query. It already knows! It's one step ahead of you. It has learned your habits and thought processes and interests. It's your secretary, your colleague, your counselor, your own graduate student doing research for which you'll get all the credit.
To put it in computer terminology, it is your intelligent agent.""
Tuesday, February 17, 2004
Monday, February 16, 2004
XSLT for everything
On Semantic Integration and XML "In conclusion, it is clear that Semantic Web can be used to map between XML vocabularies however in non-trivial situations the extra work that must be layered on top of such approaches tends to favor using XML-centric techniques such as XSLT to map between the vocabularies instead. "
Radar Networks Triple Store
Okay, not much sleuthing here, it's the 4th hit on Google or something, still interesting.
"2 November, 2003. A short and somewhat formal description of the Radar Networks Triple Store, which is the system that handles the semantic metadata for this website. An essay by Jack Rusher.
Introduction
A triple store is designed to store and retrieve identities that are constructed from triplex collections of strings (sequences of letters). These triplex collections represent a subject-predicate-object relationship that more or less corresponds to the definition put forth by the RDF standard.
The problem space of storing this sort of data has been explored by the graph database, object database, PROLOG language and, more recently, semantic web communities. A more thorough backgrounder is provided by the work on Datalog, Jena, Dave Beckett’s Redland, the AT&T Research Communities of Interest project, Ora Lassila’s Wilbur, and the activities of the W3C Semantic Web project, among others."
Triple Store
Oh and then there's this blog (which I've read before without seeing the Radar Network postings).
"2 November, 2003. A short and somewhat formal description of the Radar Networks Triple Store, which is the system that handles the semantic metadata for this website. An essay by Jack Rusher.
Introduction
A triple store is designed to store and retrieve identities that are constructed from triplex collections of strings (sequences of letters). These triplex collections represent a subject-predicate-object relationship that more or less corresponds to the definition put forth by the RDF standard.
The problem space of storing this sort of data has been explored by the graph database, object database, PROLOG language and, more recently, semantic web communities. A more thorough backgrounder is provided by the work on Datalog, Jena, Dave Beckett’s Redland, the AT&T Research Communities of Interest project, Ora Lassila’s Wilbur, and the activities of the W3C Semantic Web project, among others."
Triple Store
Oh and then there's this blog (which I've read before without seeing the Radar Network postings).
The Dangers of Caffeine
Coffee-breaks sabotage employees' abilities "St Claire and Rogers decided to investigate caffeine's effects on work stress after hearing an anecdote at a stress workshop. A man described how he and a group of normally cohesive colleagues went on a business trip to the US.
Unlike in the UK, coffee was freely available and the team over-indulged. Within days their stress levels had escalated and they believe the extra caffeine had disrupted their working relationships, and impaired their working ability.
The Bristol team tested caffeine's effects on 32 coffee-drinkers. They told them they would be given a caffeinated coffee that would boost their performance, or a caffeinated coffee which causes stress-like side-effects, or decaffeinated coffee. However, unknown to the volunteers, only half the drinks contained 200 mg of caffeine and the other half contained none. The subjects then carried out two stressful tasks."
""Certainly in our experience of people drinking coffee there's a tendency for all sorts of personal interactions to get a little more intense. If there was a stressful situation there would be more shouting, yelling, louder talking," he told New Scientist. "This is very interesting confirmation.""
Beware of taking Bristolites to cafes with bottomless cups of coffee - violence, mayhem and talking louder could ensue.
Unlike in the UK, coffee was freely available and the team over-indulged. Within days their stress levels had escalated and they believe the extra caffeine had disrupted their working relationships, and impaired their working ability.
The Bristol team tested caffeine's effects on 32 coffee-drinkers. They told them they would be given a caffeinated coffee that would boost their performance, or a caffeinated coffee which causes stress-like side-effects, or decaffeinated coffee. However, unknown to the volunteers, only half the drinks contained 200 mg of caffeine and the other half contained none. The subjects then carried out two stressful tasks."
""Certainly in our experience of people drinking coffee there's a tendency for all sorts of personal interactions to get a little more intense. If there was a stressful situation there would be more shouting, yelling, louder talking," he told New Scientist. "This is very interesting confirmation.""
Beware of taking Bristolites to cafes with bottomless cups of coffee - violence, mayhem and talking louder could ensue.
Sunday, February 15, 2004
GiST and MTrees
MTree Project "The M-tree is an index structure that can be used for the efficient resolution of similarity queries on complex objects to be compared using an arbitrary metric, i.e. a distance function d that satisfies the positivity, symmetry, and triangle inequality postulates. For instance, with the M-tree you can index a set of strings and organize them according to their edit distances (the minimal number of character changes needed to transform one string into another)."
MTree Applet (also part of XXL).
GiST: A Generalized Search Tree for Secondary Storage "The GiST is a balanced tree structure like a B-tree, containing pairs. But keys in the GiST are not integers like the keys in a B-tree. Instead, a GiST key is a member of a user-defined class, and represents some property that is true of all data items reachable from the pointer associated with the key. For example, keys in a B+-tree-like GiST are ranges of numbers ("all data items below this pointer are between 4 and 6"); keys in an R-tree-like GiST are bounding boxes, ("all data items below this pointer are in Calfornia"); keys in an RD-tree-like GiST are sets ("all data items below this pointer are subsets of {1,6,7,9,11,12,13,72}"); etc. To make a GiST work, you just have to figure out what to represent in the keys, and then write 4 methods for the key class that help the tree do insertion, deletion, and search."
Report on implementing GiST in Java (framed).
Other trees (or multi-dimensional access methods).
MTree Applet (also part of XXL).
GiST: A Generalized Search Tree for Secondary Storage "The GiST is a balanced tree structure like a B-tree, containing
Report on implementing GiST in Java (framed).
Other trees (or multi-dimensional access methods).
Saturday, February 14, 2004
Problems with Java Generics
Generics in C#, Java, and C++ "...with Java generics, you don't actually get any of the execution efficiency that I talked about, because when you compile a generic class in Java, the compiler takes away the type parameter and substitutes Object everywhere. So the compiled image for List is like a List where you use the type Object everywhere...Of course, if you now try to make a List, you get boxing of all the ints. So there's a bunch of overhead there. Furthermore, to keep the VM happy, the compiler actually has to insert all of the type casts you didn't write."
"When you apply reflection to a generic List in Java, you can't tell what the List is a List of. It's just a List. Because you've lost the type information, any type of dynamic code-generation scenario, or reflection-based scenario, simply doesn't work."
With 1.3 casting used to be a fairly big overhead, with 1.4 this isn't an issue. Running the trove4j benchmarks in 1.4 you can still see the performance difference of objects vs primitives.
The second issue, and it's the same with autoboxing, seems to highlight how the syntax gives the illusion of consistency when there is none.
"When you apply reflection to a generic List in Java, you can't tell what the List is a List of. It's just a List. Because you've lost the type information, any type of dynamic code-generation scenario, or reflection-based scenario, simply doesn't work."
With 1.3 casting used to be a fairly big overhead, with 1.4 this isn't an issue. Running the trove4j benchmarks in 1.4 you can still see the performance difference of objects vs primitives.
The second issue, and it's the same with autoboxing, seems to highlight how the syntax gives the illusion of consistency when there is none.
Trust Visualization
Trust on the Semantic Web has some examples of visualization. I recently found, again, the visualization of newsgroups by Microsoft Research called Netscan. I was reminded about this after reading unstruct.org's "Ouch! This is a red hot topic...".
New Sesame Home
"The openRDF.org site is a community site that is the center for all Sesame-related development. Here, developers and users can meet and discuss, ask questions and submit problem reports. The latest news about Sesame will be posted here."
Friday, February 13, 2004
Kowari 1.0.1
After some feedback about problems with building Kowari we've decided to release a new version that will compile and build successfully - this was due to problems with Barracuda. The upshot of this, though, is that all the bugs we fixed and the features we've been working on like Jena and JRDF support, RDQL, improvements in resource allocation and handling, and a Swing based iTQL UI get released.
We're also having fun loading millions of triples on an Opteron system running Linux. It gets about 4,000 triples/second after 13 million triples - which isn't quite fast enough, of course it's never fast enough.
Kowari project page.
We're also having fun loading millions of triples on an Opteron system running Linux. It gets about 4,000 triples/second after 13 million triples - which isn't quite fast enough, of course it's never fast enough.
Kowari project page.
Brain Dead Farting - I Don't Think in Triples
There looks to be a nice response on TriX. I was fairly aware that what I wrote I'd hoped it was what people would've thought of before. Had a simple "here's the XSLT you boob" and be done with it. I guess it's time to read those 39 odd emails.
Okay, that doesn't seem have been enlightening - especially when there's no response to your mail. It's not supposed to be human readable but someone has to write the XSLT for the "user".
Eric Jain has had a similar experience with the RDF/XML syntax that I have : "Interestingly, when presented with the choice of working with an XML or an RDF/XML representation of the same data, our developers (somewhat familiar with XML, not RDF) choose to use the RDF version (to my great relief :-). The data is relatively complex, with lots of cross-referencing, which the RDF/XML syntax can handle in a simple and consistent way."
Alberto Reggiori said: "but the real point here is how much work a user/programmer has to put into writing and managing RDF descriptions - even though RDF is supposed to be for machines, the poor users will have most of time mark-up their data into their templates of scripts, JSP, ASP and so on. TriX is definitively a step ahead compared to RDF/XML - added DTD, XMLSchema (then kinda "deterministic" markup) and named graphs are very cool - but still too complicated for the average human being to use, due he/she has to think in terms of statements, subjects, predicates, objects, collections, reification and so on. Definitively, such an "assembly like language" is very good for general purpose RDF toolkits and frameworks, and more experienced users. But the major part of XML folks out there do not have a clue (or few) why they have to "denormalize" their data all the time into RDF constructs."
After reading the TriX paper again, I still wonder what is the exact problem that's trying to be solved. I don't think it's made the problem of converting RDF to XML any easier, it is significently more verbose than RDF/XML or N3, some of the small things like named graphs are useful but not by themselves. Using XQuery to query it would be slow and rather cumbersome, it's much better to use a triple store.
Okay, that doesn't seem have been enlightening - especially when there's no response to your mail. It's not supposed to be human readable but someone has to write the XSLT for the "user".
Eric Jain has had a similar experience with the RDF/XML syntax that I have : "Interestingly, when presented with the choice of working with an XML or an RDF/XML representation of the same data, our developers (somewhat familiar with XML, not RDF) choose to use the RDF version (to my great relief :-). The data is relatively complex, with lots of cross-referencing, which the RDF/XML syntax can handle in a simple and consistent way."
Alberto Reggiori said: "but the real point here is how much work a user/programmer has to put into writing and managing RDF descriptions - even though RDF is supposed to be for machines, the poor users will have most of time mark-up their data into their templates of scripts, JSP, ASP and so on. TriX is definitively a step ahead compared to RDF/XML - added DTD, XMLSchema (then kinda "deterministic" markup) and named graphs are very cool - but still too complicated for the average human being to use, due he/she has to think in terms of statements, subjects, predicates, objects, collections, reification and so on. Definitively, such an "assembly like language" is very good for general purpose RDF toolkits and frameworks, and more experienced users. But the major part of XML folks out there do not have a clue (or few) why they have to "denormalize" their data all the time into RDF constructs."
After reading the TriX paper again, I still wonder what is the exact problem that's trying to be solved. I don't think it's made the problem of converting RDF to XML any easier, it is significently more verbose than RDF/XML or N3, some of the small things like named graphs are useful but not by themselves. Using XQuery to query it would be slow and rather cumbersome, it's much better to use a triple store.
Thursday, February 12, 2004
13 Things to Fix about EJBs
"In particular developers appear to be most interested in the following:
1. Ditch CMP or make it simpler like Hibernate or JDO
2. Use a POJO programming model
3. Add support for Interceptors/filters/AOP.
4. Eliminate/Consolidate the component interfaces (remote, local and endpoint).
5. Make deployment descriptors more like XDoclet
6. Instance-level authentication/entitlement.
7. Replace the JNDI ENC with Dependency Injection (a.k.a. IoC).
8. Add a Mutable Application Level Context
9. Support development and testing outside the container system.
10. Define cluster-wide singletons for EJB.
11. Clearly specify and standardize class loading requirements.
12. Standardize the deployment directory structure for EJBs.
13. Support Inheritance."
13 improvements for EJB.
1. Ditch CMP or make it simpler like Hibernate or JDO
2. Use a POJO programming model
3. Add support for Interceptors/filters/AOP.
4. Eliminate/Consolidate the component interfaces (remote, local and endpoint).
5. Make deployment descriptors more like XDoclet
6. Instance-level authentication/entitlement.
7. Replace the JNDI ENC with Dependency Injection (a.k.a. IoC).
8. Add a Mutable Application Level Context
9. Support development and testing outside the container system.
10. Define cluster-wide singletons for EJB.
11. Clearly specify and standardize class loading requirements.
12. Standardize the deployment directory structure for EJBs.
13. Support Inheritance."
13 improvements for EJB.
Wednesday, February 11, 2004
IoC
I was looking for more information about this today and found this (Martin Fowler has an eariler article and so does Michael Yuan):
"The best way to describe what IoC is about, and what benefits it can provide, is to look at a simple example. The following JDBCDataManger class is used to manage our application's accessing of the database. This application is currently using raw JDBC for persistence. To access the persistence store via JDBC, the JDBCDataManger will need a DataSource object. The standard approach would be to hard code this DataSource object into the class, like this:
public class JDBCDataManger {
public void accessData() {
DataSource dataSource = new DataSource();
//access data
...
}
Given that JDBCDataManger is handling all data access for our application, hard coding the DataSource isn't that bad, but we may want to further abstract the DataSource, perhaps getting it via some system-wide property object:
public class JDBCDataManger {
public void accessData() {
DataSource dataSource =
ApplciationResources.getDataSource();
}
In either case, the JDBCDataManger has to fetch the DataSource itself.
IoC takes a different approach — with IoC, the JDBCDataManger would declare its need for a DataSource and have one provided to it by an IoC framework. This means that the component would no longer need to know how to get the dependency, resulting in cleaner, more focused, and more flexible code."
A Brief Introduction to IoC
"The best way to describe what IoC is about, and what benefits it can provide, is to look at a simple example. The following JDBCDataManger class is used to manage our application's accessing of the database. This application is currently using raw JDBC for persistence. To access the persistence store via JDBC, the JDBCDataManger will need a DataSource object. The standard approach would be to hard code this DataSource object into the class, like this:
public class JDBCDataManger {
public void accessData() {
DataSource dataSource = new DataSource();
//access data
...
}
Given that JDBCDataManger is handling all data access for our application, hard coding the DataSource isn't that bad, but we may want to further abstract the DataSource, perhaps getting it via some system-wide property object:
public class JDBCDataManger {
public void accessData() {
DataSource dataSource =
ApplciationResources.getDataSource();
}
In either case, the JDBCDataManger has to fetch the DataSource itself.
IoC takes a different approach — with IoC, the JDBCDataManger would declare its need for a DataSource and have one provided to it by an IoC framework. This means that the component would no longer need to know how to get the dependency, resulting in cleaner, more focused, and more flexible code."
A Brief Introduction to IoC
Subscribe to:
Posts (Atom)